Hi Flagon Devs, I'd like to surface issues with tags to make it clear what components might be easier to address, and/or where newcomer help would be especially welcome. This is in service towards getting practices/thoughts on list :-)
Some projects have issues tied to each individual component/repo, and others use a GH Issue list for ALL project related issues. I wonder whether we believe there are sufficient benefits for having a single repo [ probably https://github.com/apache/flagon ] so we can use some tags to have issues that might be especially 'easy' or 'for newbies'. If we want to maintain multiple lists, per repo that invites some questions: * Anyone have a good way to be able to provide a single view of #easy issues for people to contribute to the project? * In the event of using issues in each GH repo: if new components might involve the potential creation of a new repos -- where would an issue get filed about those new features/components [ since it might not be tied to an existing repo ]? Happy to hear your thoughts, Thanks, Austin
