Skip to content
This repository was archived by the owner on Jul 20, 2018. It is now read-only.

The io.js Built Team WG Proposal #29

Closed
retrohacker opened this issue Feb 19, 2015 · 9 comments
Closed

The io.js Built Team WG Proposal #29

retrohacker opened this issue Feb 19, 2015 · 9 comments

Comments

@retrohacker
Copy link
Contributor

We are putting together a governance model for the io.js build team, and are proposing that the docker-iojs team be a sub-working group of that team. To be part of this conversation, check out: nodejs/build#49

@retrohacker retrohacker changed the title The IOJS The IOJS Built Team WG Proposal Feb 19, 2015
@retrohacker retrohacker changed the title The IOJS Built Team WG Proposal The io.js Built Team WG Proposal Feb 19, 2015
@pesho
Copy link
Contributor

pesho commented Feb 19, 2015

I'd like to limit my involvement to just docker-iojs for now, so a separate sub-group sounds good 👍

@Starefossen
Copy link
Member

Is there a list of members of the docker-iojs sub-working group some where?

@retrohacker
Copy link
Contributor Author

@Starefossen not at the moment. We are still trying to iron out what it means to be a sub-working group.

We could do a pull request to our own README.md with those actively involved in dev.

@Starefossen
Copy link
Member

Cool, thanks. I guess I'll hang around and see where it goes 😄

@pesho
Copy link
Contributor

pesho commented Mar 7, 2015

@wblankenship btw what is the rationale for the docker-team being a sub-WG of Build? I don't think they are really related.

@mikeal
Copy link

mikeal commented Mar 7, 2015

FYI, we don't have a provision for "sub-WG" in the governance model. Informally the term has been used for working groups that are basically being bootstrapped out of another WG (this happened with evangelism spinning out of the website WG).

While this behavior isn't documented the working group doc does set the expectation that working groups are basically already running and getting things done prior to being chartered so it's all fine :)

@pesho
Copy link
Contributor

pesho commented Mar 7, 2015

Thanks @mikeal

I think we should at least have a separate GitHub team (@iojs/docker). Not sure if this requires a separate WG as well.

@mikeal
Copy link

mikeal commented Mar 7, 2015

Good idea, either @rvagg or I can set that up whenever you like :)

@pesho
Copy link
Contributor

pesho commented Apr 7, 2015

Closing as #39 was implemented instead

@pesho pesho closed this as completed Apr 7, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants