Write up project board guidelines

[binnes]

No description provided.

[elmiko]

after hammering through some of the details around working with the project board, i'm starting to develop opinions XD

i definitely agree that we should come up with a standard process for the working group/community to interact with our issue and planning boards.

just to add a little more detail, and i think @binnes might have covered some of this in his review of the planning board at the last meeting, it seems like github wants us to drive activity using issues. once an issue is created it can easily be brought into a board. at that point it appears that any linked pull requests can also be easily associated. so, i'm thinking we might take a stance of asking for an issue to begin with, and the we can bring issues into the planning board as needed.

to summarize, something like this:

1. community member would like to see a change in okd or the community
2. creates an issue in the appropriate repo with their thoughts
3. issue get an "untriaged" label, or similar
4. working group members review the issue, perhaps at a community meeting and decide to accept the issue
5. if accepted, the issue is brought into a board for planning and whatnot
6. if rejected, discussion is left on the issue and depending on followups different things might happen.

just my thoughts o/

[JaimeMagiera]

An initial attempt at visualizing what this would look like to a community member...

https://github.com/okd-project/working-group/blob/planning_26/participation-guidelines.md

[JaimeMagiera]

• If existing item, add user to project card
• If new item, put in a discussion item in OKD Top level as "Idea"
• Must have GitHub account
• We will invite to community meeting
• Add text that we want participation to be as easy as possible.