Confusing snippet in CHARTER.md

[jchestershopify]

In this segment of the CHARTER.md template, there appears to be a standalone item that somehow got rolled into a previous item.

I'm also surprised that it talks about voting membership of the TAC; that doesn't seem compatible with the TAC's charter and operations.

I think the easiest answer would be to just snip it out.

[lukehinds]

the section link is not jumping to any specific text, could you just copy / paste the part into your comment?

[jchestershopify]

It's at 2(f):

f. The TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC. **The TSC Chair, or any other TSC member so designated by the TSC, will serve as the Technical Initiative’s voting representative on the OpenSSF’s Technical Advisory Council (the "TAC").

[dlorenc]

The charters are definitely confusing and inconsistent. I don't think they can really be just filled in, we might need to take a pass at generating a new template.

[jchestershopify]

Any thoughts about timing? For the mooted Securing Software Repos WG, our aim was to have our ducks in a row by the TAC meeting on April 19th (meaning we'd need to adopt a charter at our next call on the 13th).

[jchestershopify]

I hate to be a pest but this is currently a blocker for setting up the workgroup. I'll go ahead and snip out what seems to me like the stray text; if that's not acceptable then we can amend it when it comes before TAC.

[bobcallaway]

While I agree with @dlorenc that we may need to revisit the template, I think the prudent thing to do for now to unblock progress on the pending charters is to snip the 2(f) text referred to by @jchestershopify

[jorydotcom]

+1; we can address & patch for other WGs as well

[jchestershopify]

This showed up again in preparing the charter for the Critical Software Projects group.

[jchestershopify]

Going through my old issues. Is this still something folks want to do, or should I close it to tidy the backlog?