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

Checklist to address changes due to move to OpenJS Foundation #311

Closed
1 of 11 tasks
mhdawson opened this issue Mar 12, 2019 · 13 comments
Closed
1 of 11 tasks

Checklist to address changes due to move to OpenJS Foundation #311

mhdawson opened this issue Mar 12, 2019 · 13 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Mar 12, 2019

There are a number of things we need to address due to the move to the OpenJS Foundation.
In particular based on the governance in:

  • Agree on how we will elect representatives to the CPC. There are 2 for the Node.js project. My
    initial proposal is that we mirror what we do for existing Board representation and have one from
    the TSC and one from the Community Committee. We could adjust that if we think it makes sense
    though so potentially worth some thought/discussion.

  • Agree on timeline for electing CPC representatives

  • Confirm the process/timelime for selection of Board representative. Node.js should likely
    have one for the first year although this needs to be confirmed after formation of the CPC.
    the CPC guidance says

    • the Node.js project will elect one Board representative from either the TSC or Community
      Committee. The representative will be selected through a vote of the members of the Node.js
      organization.
  • Update TSC Charter and governance

  • Update CommComm Charter and governance

  • Update Code of conduct references

  • Update moderation policy to reflect escalation as outline in
    FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md

  • Figure out travel fund administration in the new foundation and update https://github.com/nodejs/admin/blob/master/MEMBER_TRAVEL_FUND.md

  • Transition for individual membership program to be under CPC?

  • will continue to build out list but saving so I don't lose what I have so far :)

  • Update any references to the Node.js Foundation in our docs.

@Trott
Copy link
Member

Trott commented Mar 12, 2019

@mhdawson
Copy link
Member Author

@Trott, thanks added to list above

@mcollina
Copy link
Member

Should we schedule a meeting to tackle those issues? They seems very broad tasks.

@nodejs nodejs deleted a comment from nobodydevrus Mar 13, 2019
@mhdawson
Copy link
Member Author

mhdawson commented Mar 13, 2019

@mcollina I thought we could start to discuss in the TSC meeting today and figure out some next steps.

EDIT (of note nobodydevrus was me, just logged in as wrong user, so deleted that comment and re-did as me)

@joesepi
Copy link
Member

joesepi commented Mar 13, 2019

Individual Membership should move from the CommComm to new Foundation work nodejs/community-committee#423

@WaleedAshraf
Copy link
Contributor

WaleedAshraf commented Mar 21, 2019

maybe update the title of Node.js Foundation account on

@keywordnew
Copy link
Contributor

The OpenJS Foundation has it's own Github and Twitter.

We'll continue to own those. But maybe we'll want to not reference the Node.js Foundation ;)

@Trott
Copy link
Member

Trott commented Mar 28, 2019

Mentioned/briefly-discussed at today's TSC meeting. Removing the tsc-agenda label. Feel free to add it back if it should stay.

@mhdawson
Copy link
Member Author

mhdawson commented Apr 2, 2019

@mcollina scheduling a meeting to discuss moving forward on these makes sense. Do you want to do that? If not I'll try to set it up once I get a chance.

@mcollina
Copy link
Member

mcollina commented Apr 2, 2019

@mhdawson I'm going to propose Wednesday 10 🚀 or Thursday 18th at 17:00 UTC 🎉 . Please vote.

cc @nodejs/tsc @nodejs/community-committee

@amiller-gh
Copy link
Member

Also removed the cc-agenda label since we discussed it last time. We'll add it back if there are action items from the dedicated meeting.

@mhdawson
Copy link
Member Author

mhdawson commented Apr 2, 2019

Both times work for me but I'd prefer Wednesday 10th (closer to now)

@Trott
Copy link
Member

Trott commented Jul 5, 2019

It seems like this checklist is not being used so I'll close this, but feel free to re-open if we're going to start using it again.

@Trott Trott closed this as completed Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants