#13 FEP-a4ed: Updates 3

Merged
pukkamustard merged 4 commits from pukkamustard/Fediverse-Enhancement-Proposals:list-in-readme into main 10 months ago

Updates to FEP-a4ed (see also #10) and repo:

  • Increase time to auto-withdraw from 90 days to 120 days. This is mostly due to me being away and almost missing the date for the initial FEP. a bit more of time gives more room to play.
  • Add list of FEPs in README.md
  • Add template for a tracking issue (see for example #10)
Updates to FEP-a4ed (see also #10) and repo: - Increase time to auto-withdraw from 90 days to 120 days. This is mostly due to me being away and almost missing the date for the initial FEP. a bit more of time gives more room to play. - Add list of FEPs in README.md - Add template for a tracking issue (see for example #10)
pukkamustard requested review from cjslep 10 months ago
cjslep reviewed 10 months ago
cjslep left a comment

Do we need to add the Tracking Issue requirement as an explicit step in feps/fep-a4ed.md?

cjslep started working 10 months ago
pukkamustard commented 10 months ago
Owner

I’d prefer not adding it as a requirement in the FEP itself. My hope is that eventually there will be better (and de-centralized) tools that can do the “Tracking Issue” thing.

If we explicitly require a specific way of doing the “tracking issue” in the FEP it will be impossible to change that. This is also an issue if we want to move this GitTea instance to git.activitypub.rocks or similar.

Just added some notes on the tracking issue in the README (dc1c4e208d).

I admit this is a bit weird. The entire process should be described in the FEP itself. But this seperation allows a certain degree of hosting agility (and allows for more decentralized ways of doing this in the future).

I'd prefer not adding it as a requirement in the FEP itself. My hope is that eventually there will be better (and de-centralized) tools that can do the "Tracking Issue" thing. If we explicitly require a specific way of doing the "tracking issue" in the FEP it will be impossible to change that. This is also an issue if we want to move this GitTea instance to `git.activitypub.rocks` or similar. Just added some notes on the tracking issue in the README (https://git.activitypub.dev/ActivityPubDev/Fediverse-Enhancement-Proposals/commit/dc1c4e208d0c2ec5756dd15bd1f658d8b1c25c8e). I admit this is a bit weird. The entire process should be described in the FEP itself. But this seperation allows a certain degree of hosting agility (and allows for more decentralized ways of doing this in the future).
cjslep commented 10 months ago
Owner

SGTM! Ty!

SGTM! Ty!
cjslep approved these changes 10 months ago
pukkamustard merged commit 49e1412b89 into main 10 months ago
pukkamustard deleted branch list-in-readme 10 months ago

Reviewers

cjslep approved these changes 10 months ago
The pull request has been merged as 49e1412b89.
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

Loading…
There is no content yet.