mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 11:46:04 +00:00

Files

T

silverpill fa3c8edeb6 FEP-a4ed: Withdraw stale proposals (#543 )

FEP-a4ed requires facilitators to contact authors of a stale proposal before withdrawing it. As our experience shows, that doesn't work. In this PR I propose withdrawing stale proposals after 1 year of inactivity without contacting authors.

This is a major change. I think even if we agree on it, existing proposals should be handled according to the old procedure.

Resolves https://codeberg.org/fediverse/fep/issues/101

Reviewed-on: https://codeberg.org/fediverse/fep/pulls/543
Reviewed-by: Arnold Schrijver <circlebuilder@noreply.codeberg.org>
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>

2025-06-24 15:43:41 +02:00

tools

FEP-a4ed: Withdraw stale proposals (#543 )

2025-06-24 15:43:41 +02:00

__init__.py

Automate things (#117 )

2023-07-16 07:43:02 +00:00

.gitignore

Automate creating readme and tracking issue (#460 )

2025-01-20 10:24:00 +00:00

backmatter.md

Place FEP table after guidelines in README.md (#395 )

2024-10-23 17:38:57 +00:00

create_issue.py

Automate creating readme and tracking issue (#460 )

2025-01-20 10:24:00 +00:00

create_readme.py

Create FEP index in JSON format (#426 )

2024-12-16 08:40:56 +00:00

frontmatter.md

Make new_proposal script slightly easier to use (#456 )

2024-12-06 19:15:14 +00:00

new_proposal.py

Make new_proposal script slightly easier to use (#456 )

2024-12-06 19:15:14 +00:00

pull_request.py

Automate things (#117 )

2023-07-16 07:43:02 +00:00

README.md

Housekeeping for the scripts (#413 )

2024-11-15 11:22:01 +00:00

update_issues.py

Automate creating readme and tracking issue (#460 )

2025-01-20 10:24:00 +00:00

README.md

tools for fep facilitators

Please follow the steps in configuration before following "Merge a FEP".

Merge a FEP

Merge the Pull Request in https://codeberg.org/fediverse/fep/pulls and note the slug.

./scripts/create_issue.py $SLUG

creates the tracking issue and updates the FEP with the information. Then run

./scripts/create_readme.py

to update the table in README.md. You are now ready to commit the changes to the FEP (added trackingIssue to frontmatter) and README.md, added the new FEP.

Configuration

Add a file config.json to the directory scripts with content

{
  "repo": "fep",
  "owner": "fediverse",
  "token": "CODEBERG_API_TOKEN"
}

The API token can be obtained by visiting https://codeberg.org/user/settings/applications and generating one with scope write:issue.

Setup for running pytest

Ensure dependencies (use a virtualenv)

pip install pytest

Check validity

pytest