Onboarding new FEP hosts

An on-topic question to @devnull @bumblefudge and @trwnh … you are all very active in AS/AP including the FEP’s. Can we sign any of you up as FEP facilitator to help @silverpill with the work?

1 Like

TBH, I would have already volunteered if I had the bandwidth or funding to do it well. I am currently running a similar community venue that runs out of grant funding soon. But I’ll consider it if it falls within scope for any grants I can secure?

1 Like

it depends on what exactly this role involves and whether it would create any conflicts of interest as the author of several feps.

1 Like

I think that @silverpill might answer best. But there should be no conflicts of interest, as this does not involve value judgments. PR reviews involve checking whether the FEP procedures are followed. There are a number of manual tasks, but some tasks have already been automated to an extent by earlier work of @silverpill and @helge.

1 Like

Do you need anything from me to onboard @trwnh or are you fine?

1 Like

If @trwnh agrees to be a FEP facilitator, please add them to fep.hosts group.

eh sure i guess i agree

2 Likes

Here is a quick overview of what we’re doing:

  • Overall, the process goes smoothly and doesn’t require much attention.
  • The most important part is processing updates and new submissions. This is done as described in FEP-a4ed. Updates can be merged quicky, but new submissions need to be reviewed more carefully because they often have incorrect or missing metadata.
  • When working with submissions, I use python scripts developed by @helge to create tracking issues and update the FEP index.
  • There are several open issues with suggestions to improve the process: Issues - fediverse/fep - Codeberg.org. Nothing urgent, but sooner or later we will need to tackle them.
  • Example of a PR that addresses one of those issues: #395 - Place FEP table after guidelines in README.md - fediverse/fep - Codeberg.org. Pull requests that modify FEP-a4ed or other important files require approvals from at least two facilitators and shouldn’t be merged until 1 month passess since the last update.
  • If proposal becomes stale (no activity for more than 1 year), we need to ping authors and change the status to WITHDRAWN if they are not responding. We haven’t done this for a long time, that’s why there are so many DRAFTs.
3 Likes

I gave @silverpill ownership of @fep.hosts and added @trwnh.

4 Likes