Skip to content

Guiding principles, concerns, general operations#9

Closed
jasnell wants to merge 1 commit into
openjs-foundation:masterfrom
jasnell:getting-started
Closed

Guiding principles, concerns, general operations#9
jasnell wants to merge 1 commit into
openjs-foundation:masterfrom
jasnell:getting-started

Conversation

@jasnell

@jasnell jasnell commented Oct 15, 2018

Copy link
Copy Markdown

This is a proposed alternative to the takes in #7, #1, and #4 ...

This takes a first stab at connecting the discussions that are happening now with the principles that guided the launch of the foundation in the first place; establishes a process for identifying who is a part of this committee and how decisions are made; and begins to address some of the community concerns that have been raised.

Comment thread README.md Outdated
and provide specific feedback on:

1. Whether the merger should proceed
2. What the overall structure of a merged Foundation should look like

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we label each item 1. github markdown will automate numbering. Good way to future proof.

Comment thread README.md Outdated
2. What the overall structure of a merged Foundation should look like
3. How projects should be organized within a merged Foundation
4. What representation projects should have on a merged Foundation's Board of
Directors

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe add what the name of the organization should be

Comment thread README.md Outdated
### Contributing to this repository

Anyone may contribute to this repository via pull request. All individuals
holding commit rights to any Node.js Foundatioon or JS Foundation project may

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Foundatioon/Foundation

Comment thread README.md Outdated
Anyone may contribute to this repository via pull request. All individuals
holding commit rights to any Node.js Foundatioon or JS Foundation project may
participate in the Node+JS Bootstrap Committee and may request commit access
to this repository.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should have an explicit +1 from someone representing the JSF for this. I don't see any conflicts, but would be good to have explicit buy in

perhaps @dmethvin or jorydotcom

Comment thread README.md
Comment thread README.md
Comment thread README.md Outdated
### Committee Co-Chairs

Committee Co-Chairs should be selected by vote of the available Committee
Membership.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As Committee Membership above is described as all members with commit rights to any Node.js or JSF project how will we be able to properly manage a vote?

Should we allow open membership to anyone meeting that criteria and the vote would be help by active members?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other aspect that should be covered here is who can volunteer? If it is any member then we should say that specifically.

Comment thread README.md
Comment thread README.md
Comment thread README.md
Comment thread README.md
Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread README.md
The Committee does not vote. Should it become impossible to determine consensus
on a given issue, each of the contending positions should be documented within
the repository with the arguments for and against each clearly documented for
further consideration.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From your comments, what you suggest is that the final decisions will be made by the board/foundation staff. If that is the case then I think you should state that here clearly. ie if the bootstrap committee cannot come to a consensus then we document the divergent opinions and the board/foundation staff will make the decision.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is still not clear from the suggested text.

@MylesBorins

Copy link
Copy Markdown
Contributor

@jasnell #7 has moved forward a bunch and governance is being fleshed out in #19

Would you be up to breaking out the other parts, specifically the guiding principles and historical documentation into their own doc? The bits from the readme that are most useful could be merged into #7

@jasnell

jasnell commented Nov 2, 2018

Copy link
Copy Markdown
Author

I'll review those over the next couple of days and will see what updates can be made here. It's going to take some time because of the travel and prep for nodeconfeu

@MylesBorins

MylesBorins commented Nov 2, 2018 via email

Copy link
Copy Markdown
Contributor

@MylesBorins

Copy link
Copy Markdown
Contributor

@jasnell are you open to removing the bootstrap-agenda label until you've had a chance to review the other open PRs?

@jasnell

jasnell commented Nov 7, 2018

Copy link
Copy Markdown
Author

Yes that's fine

@MylesBorins

Copy link
Copy Markdown
Contributor

@jasnell are you still planning to pursue this or can it be closed?

@jasnell jasnell closed this Dec 11, 2018
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

Successfully merging this pull request may close these issues.

5 participants