Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate project-status repo back here #1374

Open
tobie opened this issue Oct 10, 2024 · 6 comments
Open

Migrate project-status repo back here #1374

tobie opened this issue Oct 10, 2024 · 6 comments

Comments

@tobie
Copy link
Contributor

tobie commented Oct 10, 2024

We should migrate https://github.com/openjs-foundation/project-status back to this repo and clean it up.

Would make maintenance of a number of cross repo documents easier.

Would make it easier for us to keep up to date with the status of the different projects.

@tobie
Copy link
Contributor Author

tobie commented Oct 15, 2024

Notes from today's CPC call:

  • it would be great to have an issue board to better keep track of things
  • might be nice to clean-up repo before moving it
  • moving shouldn’t be too much work
  • lukewarm consensus to migrate repos

@tobie
Copy link
Contributor Author

tobie commented Nov 1, 2024

Notes from this week's CPC call:

Working session on this next week

@tobie
Copy link
Contributor Author

tobie commented Nov 5, 2024

Notes from this week's working session call:

  • Identify maintainers (and champions where appropriate) for each project
  • if there are open questions, answer the question and tag them
  • else, tag maintainers in a message asking them to update the checklist to reflect the current state of things

@tobie
Copy link
Contributor Author

tobie commented Nov 6, 2024

Started a project board to get us organized here: https://github.com/orgs/openjs-foundation/projects/9 (and asked @bensternthal to make it public).

@tobie
Copy link
Contributor Author

tobie commented Nov 6, 2024

Separately from the catching up work that's needed here, I still believe we should merge both repositories. Here's the rationale:

  1. We're duplicating content across repos and keeping that content in sync is a drag (notably the checklists in PROJECT_PROGRESSION.md are copied in the issue templates).
  2. Some CPC issues end-up in this repository (e.g. Should GOVERNANCE.md be required of all projects? project-status#47) and then get promptly forgotten.
  3. Content in the project status repo (like the GROWTH plans) gets forgotten from CPC repo refactoring.

@bensternthal
Copy link
Contributor

@tobie the board is already public :) Let me know if you need anything additional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants