Initial revisions of project lifecycle

[bensternthal]

This is an initial attempt to rework the project lifecycle process.

Note that once this is merged I will work on renaming the repo from TSC to TAC and adjusting all the links.

[bensternthal]

Looks like the templates are hardcoded into check_projects_syntax.py, Ill have to work on that and file an updated pr.

[cetola]

This looks good, and in alignment with what we discussed at the TAC.

[bensternthal]

Yikes, OK the content and therefore process is tightly coupled to the code. This makes updates pretty hard, once I get this merged, perhaps we can chat about decoupling TAC process from the code that generates the website.

[bensternthal]

I filed chipsalliance/chips-alliance-website#118 to address the path change I submitted in this PR.

I'd like @mgielda to review before I merge these.

[bensternthal]

@mgielda I know you are super busy, but given the changes in this PR, it would be great to have your eyes on it before we merge.

[mgielda]

Hi Ben, as mentioned in the latest TAC meeting, I was travelling to EW and then EOSS / CHIPS open HW event / LatchUp. If you want my review, you may have to ping me using another channel, as I have thousands of emails from GitHub. I was simply not aware of this PR. Overall, I believe the entirety of the TAC should have been made aware that the template is being changed by an email to the mailing list.

The code to build the website was specifically tied to the project templates to avoid discrepancies, so I would definitely oppose decoupling them again.

[bensternthal]

@mgielda noted, I will send out notifications to the TAC mail list from now on for anything this substantial.

Understood about keeping things coupled.