Skip to content
This repository has been archived by the owner on Aug 31, 2018. It is now read-only.

What does this mean for Node.js collaborators? #13

Closed
benjamingr opened this issue Aug 23, 2017 · 3 comments
Closed

What does this mean for Node.js collaborators? #13

benjamingr opened this issue Aug 23, 2017 · 3 comments

Comments

@benjamingr
Copy link
Contributor

Hi, thanks for inviting me into the repository to raise concerns I have.

  • Do pull requests I make in nodejs/node get landed here?
  • How will Ayo deal with breaking changes with Node.js? (disagreements on APIs etc)
  • How will Ayo deal with reviewing code and handling issues? Is there any overlap between existing Node.js collaborators and Ayo?
@addaleax
Copy link
Contributor

Do pull requests I make in nodejs/node get landed here?

We’re figuring this out in #9, but presumably we’re going to want to include upstream patches to some degree, yes.

Is there any overlap between existing Node.js collaborators and Ayo?

If you go by the list in https://github.com/nodejs/node/#collaborators, I think that’s me, Jeremiah, maybe Alexey?

I don’t think we have figured out answers/discussion venues for the other questions

@zkat
Copy link
Contributor

zkat commented Aug 23, 2017

@benjamingr my responses as just one member (please don't take them as authoritative):

  1. The way I'm thinking about it is that for the time being, we just mirror changes from Node over here.
  2. For the time being, simply by mirroring them to preserve drop-in-ability. Eventually, I have no interest in retaining compatibility with Node Core at all, because that would involve participating in and interacting with a community with deeply dysfunctional governance.
  3. There's already plenty of overlap. In fact, most folks who are part of this repository are current or former collaborators on the Node project, including multiple current-and-former TSC and CTC members.

@varjmes
Copy link

varjmes commented Sep 11, 2017

i think this has been answered well enough! if you have any more queries, please feel free to open a new issue <3

@varjmes varjmes closed this as completed Sep 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants