So we have: https://agones.dev/site/docs/contribute/agones-feature-proposal/
Which to be fair, not many people take advantage of. This might be for a few reasons - but some of them could be:
- The AFP process is https://agones.dev/site/docs/contribute/agones-feature-proposal/ - which is nowhere near the contributing guide.
- If you file an AFP it gets caught up in whole Agones CI -- which is a lot.
So I'm proposing a few things:
- We move the AFP process folder into its own
proposals repository in our org, since it doesn't need much in the way of backing infrastructure.
- We move the documentation for AFP into the readme for that project
- We link to it from the contributing guide.
- We update the Agones site to be replace the AFP proposal to have a "Code Contribution" page that points to the contributing and development guide in the Agones repository.
Thoughts?
So we have: https://agones.dev/site/docs/contribute/agones-feature-proposal/
Which to be fair, not many people take advantage of. This might be for a few reasons - but some of them could be:
So I'm proposing a few things:
proposalsrepository in our org, since it doesn't need much in the way of backing infrastructure.Thoughts?