New Op1st community project checklist

[quaid]

Describe what is missing from the handbook

We need a checklist for contributors to use when starting a new project, repository, etc. within the Op1st community.

If the documentation is for a task, have you discovered a solution?

Yes, we can fork from this bigger list, trim it down, and add any parts specific or unique to our community. (We can submit any useful changes back to the Open Source Way upstream.)

If you've discovered a solution, would you be willing to contribute it to the handbook?

Yes, but it will need review and changes by others to be accurate,

Additional Info

None

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.