Post-Bootstrap work to be managed by CPC

[mhdawson]

**** CURRENTLY MANAGED IN PROJECT BOARDS ****

• BOOTSTRAP [closed] - https://github.com/openjs-foundation/bootstrap/projects/2
• POST-BOOTSTRAP - https://github.com/openjs-foundation/bootstrap/projects/3

HISTORICAL DATA

Issue to build list of checkboxed items we need to work on/progress

• Bootstrapping

  • New GitHub organization
  • Update all governance docs to reflect the name selected for the Foundation. (doc: Updated references to foundation #126)
  • Initial email lists - #134
  • Confirm list of initial Impact projects and land as PROJECTS.md
  • Land Common Code of Conduct in OpenJS Foundation org - PR doc: update to reflect planned CoC #147
  • Target for Initial CPC meeting (collaborator summit) #125
  • Checklist for projects (refs to OpenJS Foundation, changes for moderation etc.) #121
  • Work with projects to identify initial CPC representatives (deadline May 1?) #152
  • Create admin repo and land initial governance docs there [155] (Create admin repo #155) (Task done, deemed unnecessary, renaming the bootstrap repo to CPC and landing docs there)

• Post-bootstrap

  • Ask projects to start updating references to docs in admin repo (ex coc etc.)
  • New Zoom, Youtube etc.
  • Document/define initial process for handling reports to report@openjsf.org (Manil has volunteered to make a first draft)
  • Review Foundation infrastructure and rethink how we manage it.
  • Move/update JSF cla-bot (see Update/move jsf-clabot for new fdn #124)
  • Project Directed Funding (Project Directed Funding #90)
  • Complete language for project exit clause (draft proposal: language for project exit clause #96)
  • draft initial process for electing voting members from the non-impact projects. Nick/Michael to
  • Add entry point for projects wanting to join on README.md and review project progression (Jory will help with this one)
    work on that together.

[MylesBorins]

Attempted to document this in a board

--> https://github.com/openjs-foundation/bootstrap/projects/2

LMK if this should be close or if it makes sense to keep both

[mhdawson]

I'm ok with using the board, but I think we might want to keep an open issue that points to the board so that we get an issue added to the agenda as a reminder that we should go through it.

[MylesBorins]

@mhdawson lets just keep this issue open then

[obensource]

@mhdawson updated your admin repo task definition to reflect priority changes. 👍

[obensource]

@mhdawson also this is as good a place as any to ask: I'm not sure how acceptable it is to edit another member's issue definition (as a matter of principal) – it just seemed easier in this case to update it to reflect current changes. Lmk if that's not ok. Thanks Michael! 👍

[mhdawson]

Updating is good with me :) Thanks for keeping it up to date.

[MylesBorins]

The CPC is officially boostraped !!!

Renaming issue to keep it for tracking

[obensource]

@MylesBorins WAHOO! So amazing to see this come together! Fantastic work everyone! 👏👏👏

[joesepi]

There were only two remaining issues that are actively being worked on ([#185] & [#90]) and one languishing issue ([#96]) that I've added the cpc-agenda label to and we can track them individually. Here's to closing out the Post-Bootstrap work issue 🎉