Create a new Plan Approved template

[DBees]

Do not merge until OpenHW staff review

[MikeOpenHWGroup]

This is a great document @DBees. I have only one suggestion and it is a big one. To minimize the risk of a project stalling after passing PA, we could define a minimum acceptance criteria to take a PA document to a vote. Let's define the PA gate as a means for member companies to demonstrate that they understand the scope of the effort, are committed to drive the project to completion and have obtained commitments from other members to work on the project.

This could be captured in a separate document, or we could amend the PA document as follows:

• Under Resources:
  • a "code owner" for the associated GitHub repository or repositories should be named.
  • specify a plan to identify and promote Committers, if needed.
  • all "Areas of Focus" should have a named Contributor.
  • consider adding a sub-heading Resourcing Plan which would specify how additional Contributors will be recruited.
• Under Work Breakdown Structure:
  • the tasks should be assigned to Contributors from at least two member companies.
  • at least 50% of the identified tasks should be allocated to a named Contributor.

I'm not wed to all of the specific bullet points above, but I am to the idea of using the PA gate as a gate.

[rickoco]

Looks good @DBees and I agree with @MikeOpenHWGroup comments if you see an easy way of incorporating them. Launch when ready.

[DBees]

Sounds good Mike. Stay tuned and I'll incorporate these ideas. Thanks. The committers is an especially good catch.

[DBees]

@MikeOpenHWGroup updated after talk today. Suggest to merge if you are reasonably happy with it, we can keep updating