Follow

Hello Fediverse!

This is call for feedback and comments on the initial Fediverse Enhancement Proposal (FEP):

FEP-a4edc7b: The Fediverse Enhancement Proposal Process
(git.activitypub.dev/ActivityPu)

FEPs are intended to be documents that provide information that improves interoperability and general well-being of the Fediverse.

This may include technical things but also social and cultural best-practices and experiences.

This initial FEP describes the format and process of publishing FEPs.

This was something that was worked on during the ActivityPubConf 2020 Hackathon by @lain, @cj and myself.

The FEP publishing process is a peer-review system where **you** are the peers!

Your comments are extremely valuable and an essential part of the process. If you have questions, comments or doubts please post. If you think this is a good idea, pleas also express your support.

Hello Fediverse!

It's been more than 60 days since "FEP-a4ed: The Fediverse Enhancement Proposal Process" was received.

I kindly request final comments before the proposal is finalized.

If there are no objections the proposal will be finalized in two weeks (on 18th of January).

See also the ongoing discussion on SocialHub: socialhub.activitypub.rocks/t/

Thank you!

@pukkamustard thanks for this initiative!
I'm afraid I'm finding it very difficult to understand what has been proposed and where to find the latest versions... could you help me out?
For instance I'd like to see discussions about making migration across Fediverse platforms possible (e.g. between Masto, Pleroma, Friendica, or Zot) by normalizing things like followers/blocks/moved-to...
But I don't know whether this has already been proposed or not.

@tfardet Hey! Currently there is no official "pretty" interface to the FEP proposals yet.

There is a list in the FEP Git repository: git.activitypub.dev/ActivityPu

And there is a topic on the SocialHub forum that lists FEP proposals: socialhub.activitypub.rocks/t/

Ideas and initiatives to make a "pretty" interface to FEP proposals are very welcome!

Maybe a static site generator? @cj has been working on a "ActivityPub Dev Library" (library.activitypub.dev/) that might serve as a good basis.

@tfardet

> For instance I'd like to see discussions about making migration across Fediverse platforms possible

That is a great topic for a FEP proposal.

Currently there is no such proposal submitted.

There is a list of ideas for FEPs on SocialHub (socialhub.activitypub.rocks/t/). Maybe you can post your idea there? You might be able to find somebody to collaborate on such a proposal...

@pukkamustard OK, thanks for your answer!
I'm afraid I wont have time to coordinate such a FEP but I know who to ping (hopefully they are still interested) so I'll post a message on discourse 👍

@pukkamustard @lain @cj Heh, check out these commits to friend camp (not hometown, just to my own instance) that add a loop toggle to Mastodon's audio player and make audio loop by default if the hashtag is present :)

github.com/friendcamp/mastodon

github.com/friendcamp/mastodon

pukkamustard, this reminds me of IETF RFCs. Isn't one of the first RFCs about the format and publishing process of RFCs?

@grishka Yes, there is a "meta RFC". In fact there are two that I am aware of: RFC 8729 (February 2020) which obsoletes RFC 4844 (July 2007) - the previous "meta RFC". I don't know if this line goes back to one of the first RFCs.

For many other "community RFCs" it is customary for the first document to be the one that describes the process itself. For example: bittorrent.org/beps/bep_0001.h or python.org/dev/peps/pep-0001/ or github.com/NixOS/rfcs/blob/mas now, also FEPs!

@pukkamustard would be great to have pleroma's chat messages standardized like this..
Sign in to participate in the conversation
chaos.social

chaos.social – a Fediverse instance for & by the Chaos community