Cross-project-council: Create admin repo

[MylesBorins]

What should be included?

• Project progression
• Charter
• Code of Conduct
• Moderation Policy
• Mailing list policy

???

[obensource]

@MylesBorins I concur that the suggestions you listed should be included in this repo, and beyond adding a license and readme – other documents we might consider are:

• Transferring a repo into the OpenJS org
• GitHub Org Management Policy
• Member Expectations Policy
• Working Group Requirements

[obensource]

🎉 WAHOO! 🎉

Seeded the openjs-foundation/admin repo. Everyone in /bootstrap has admin access. Topped-off with a few PRs and issues. 👍

[obensource]

👉 Looks like our member access privileges are set to read regardless, so in any case – everyone should have the access they need now. 🎷😎

[MylesBorins]

In retrospect I'm not 100% if we need an admin repo, opened https://github.com/openjs-foundation/admin/issues/14

[obensource]

After discussing admin/#14, the bootstrap team determined in today's meeting that the admin repository isn't relevant at this time as we only have one Top Level Committee and we'll be renaming the bootstrap repo to cross-project-council soon – which will handle any concerns the admin repo was intended to address.

I'll be deleting the existing admin repo and migrating any relevant issues to the /bootstrap repository.

Given the above, I'm closing this issue. 👍

[obensource]