Skip to content

Commit 4168198

Browse files
committed
doc: add TC meeting 2015-01-28 minutes
PR-URL: #699 Reviewed-By: Jeremiah Senkpiel <[email protected]>
1 parent c4b1019 commit 4168198

File tree

1 file changed

+179
-0
lines changed

1 file changed

+179
-0
lines changed

doc/tc-meetings/2015-01-28.md

+179
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,179 @@
1+
# io.js TC Meeting 2015-01-28
2+
3+
## Links
4+
5+
* **Google Hangouts Video**: http://www.youtube.com/watch?v=k27NObxy0ps
6+
* **GitHub Issue**: https://github.com/iojs/io.js/issues/565
7+
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1IIfubVivCORgP0nQfo8Mf4gXhwBrndRm9cwmNGBXmtE
8+
9+
## Agenda
10+
11+
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
12+
13+
* governance: Add new Collaborators [#234](https://github.com/iojs/io.js/issues/234) / feedback and more contribs / @chrisdickinson
14+
* Stabilization and Release Cycles and Process [#405](https://github.com/iojs/io.js/issues/405) / further discussion / @iojs/tc
15+
- doc: add releases document detail release cycle [#630](https://github.com/iojs/io.js/issues/630) / proposal from @chrisdickinson
16+
* dgram: implicit binds should be exclusive [#325](https://github.com/iojs/io.js/issues/325) / minor version bump / @bnoordhuis
17+
* buffer: implement `iterable` interface [#525](https://github.com/iojs/io.js/issues/525) / minor version bump / @bnoordhuis
18+
* replace util.isType() with typeof [#607](https://github.com/iojs/io.js/issues/607) / general use of util.is*() in core re perf
19+
* docs: lower the maximum stability level to "stable" [#633](https://github.com/iojs/io.js/pull/633)
20+
* maintain our own package registries for io.js related packages [#640](https://github.com/iojs/io.js/issues/640#issuecomment-71882645)
21+
* Working Groups PR [#599](https://github.com/iojs/io.js/pull/599)
22+
* Remove “unstable” from messaging [#108](https://github.com/iojs/website/issues/108)
23+
24+
## Minutes
25+
26+
### Present
27+
28+
* Ben (TC)
29+
* Bert (TC)
30+
* Chris (TC)
31+
* Colin (TC)
32+
* Fedor (TC)
33+
* Isaac (TC)
34+
* Mikeal
35+
* Rod
36+
37+
Apologies from:
38+
39+
* Trevor (TC)
40+
* Domenic
41+
42+
### Mini stand-up
43+
44+
* Ben: Reviewed/landed pull requests, fixed bugs, the usual
45+
* Bert: Same as Ben, but not as much
46+
* Chris: On-boarding stuff
47+
* Colin:
48+
* Fedor: working on pyg (gyp alternative in C)
49+
* Rod: ARMv6 builds, fixing persistent bug on Ubuntu 10.04, yay!
50+
* Isaacs: Only doing npm CEO stuff
51+
* Mikeal: social media stuff for io.js, PR, roadmap, feedback from Big Cos.
52+
53+
### Review of last meeting
54+
55+
* Invite Domenic Denicola to the TC Meetings (https://github.com/iojs/io.js/issues/403)
56+
* Governance: Add new collaborators (https://github.com/iojs/io.js/issues/234)
57+
* Stabilization and Release Cycles and Process (https://github.com/iojs/io.js/issues/405)
58+
* also: the state of ES6 on io.js (re: V8 upgrade policy) (https://github.com/iojs/io.js/issues/251)
59+
* doc: bump punycode api stability to ‘stable’ (https://github.com/iojs/io.js/issues/470)
60+
* Working group reports
61+
* Streams
62+
* Website
63+
* ICU
64+
65+
### governance: Add new Collaborators
66+
67+
[#234](https://github.com/iojs/io.js/issues/234) / feedback and more contribs / @chrisdickinson
68+
69+
* Chris: Onboarded 2 groups of 4 new collaborators last week. (first group: @vkurchatkin, @micnic, @seishun, @brendanashworth, second group: @evanlucas, @Fishrock123, @Qard, @thlorenz)
70+
- 30 min summary of how everything works, gov, git, etc.
71+
- took exit poll to get reactions
72+
- notes here: https://gist.github.com/chrisdickinson/80df88b9089c19e0459e
73+
* Rod: how do we iterate?
74+
* Chris: Do it again next week with ~4 more
75+
* Discussed timezones and how that works
76+
77+
### Stabilization and Release Cycles and Process
78+
79+
[#405](https://github.com/iojs/io.js/issues/405) / further discussion / @iojs/tc
80+
81+
***Also:*** doc: add releases document detail release cycle [#630](https://github.com/iojs/io.js/issues/630) / proposal from @chrisdickinson
82+
83+
Moved straight to Chris’ proposal:
84+
85+
* Chris discussed thoughts in his proposal @ https://github.com/iojs/io.js/issues/630
86+
* Mikeal: would rather not have a static number/list of supported versions, let that be dynamic as people & companies step up to help support them
87+
* Ben: “stable” and “next” would be easiest to reason about
88+
* Chris: “dev” is for ad-hoc semver releases, replaces nightlies with a better train system.
89+
* Chris: branches will be “master” - development happens here, maintain “v1.x”, “v2.x” etc. for major releases. Ideally LTS would be from major versions.
90+
* Fedor asked about communication to users and how much fragmentation this would cause
91+
* Ben: how do you keep the delta between dev and stable from getting too big
92+
* Chris: at most there would be a 2-week lag between something hitting dev and something going out on stable
93+
* Bert: suggested that we need a better batching mechanism, particularly for breaking changes, so we’re not constantly bumping major.
94+
95+
### dgram: implicit binds should be exclusive
96+
97+
[#325](https://github.com/iojs/io.js/issues/325) / minor version bump / @bnoordhuis
98+
99+
* Ben: this is about minor version bump, that’s been decided and we’re doing a 1.1.0 so this is being merged and released
100+
101+
### buffer: implement `iterable` interface
102+
103+
[#525](https://github.com/iojs/io.js/issues/525) / minor version bump / @bnoordhuis
104+
105+
* Ben: same as previous issue, resolved
106+
107+
### replace util.isType() with typeof
108+
109+
[#607](https://github.com/iojs/io.js/issues/607) / general use of util.is*() in core re perf
110+
111+
* Bert: find with direct comparisons and checks where it makes sense (undefined, simple stuff)
112+
* Isaac: hate it all, they are difficult to inline so manually inline--pick one and use it across all
113+
* Colin: working on a PR to do the replacement already
114+
* Chris volunteered to PR a style-guide into docs
115+
* Isaac: better linter would be great
116+
117+
### Doc-tool - Should we merge with the joyent/node version?
118+
119+
* Isaac: Robert Kowalski reached out to me to ask about this.
120+
- Seems silly to have two nearly-identical tools for this.
121+
- Delegate to doc working group?
122+
- Suggested that he just pick one from io.js or joyent/node and send a PR for that
123+
* Mikeal: Website WG is meeting next week, will pull in Robert to that discussion
124+
125+
### docs: lower the maximum stability level to "stable"
126+
127+
[#633](https://github.com/iojs/io.js/issues/633)
128+
129+
* General disagreement about this
130+
* Mikeal suggested moving things that are likely to change into vendored packages (like streams)
131+
* Motivation was to set some things (frozen/locked) as unchangable because they would break too much stuff
132+
* Bert: we effectively have 4 levels: strict-deprecation, soft-deprecation, moving, pretty-much-done
133+
* Mikeal: proposed punting this for a few weeks
134+
* Isaac: the labels are useful for guiding people on where best to contribute and where to not bother
135+
136+
### maintain our own package registries for io.js related packages
137+
138+
[#640](https://github.com/iojs/io.js/issues/640)
139+
140+
* Mikeal: each distro (Homebrew, Debian, etc.) has their own conception of “stable”, suggestion is to maintain them under io.js and instruct people how to do this. e.g. using our own custom Homebrew end-point and instruct people how to use it with `brew`. Also could bring in complicated packages from the community.
141+
* Mikeal: Should come under the Build WG for now, ideally a single repo where external projects can put in a single PR to update their stuff.
142+
143+
### Working Groups PR
144+
145+
[#599](https://github.com/iojs/io.js/issues/599)
146+
147+
* Mikeal introduced his proposal: if you’re going to do the work in a WG then you can spin that up as a separate concern
148+
* Ben asked for clarification about whether WGs get a free-pass in core
149+
- Mikeal: no, they are isolated from core
150+
* Rod: clarification about relationship to TC
151+
- TC has charter-revocation powers, beyond that they don’t have control over the activities of a WG
152+
* Consensus reached, Mikeal will put in the suggested fixes (in the PR) into the docs and merge
153+
154+
### Remove “unstable” from messaging
155+
156+
[#108](https://github.com/iojs/io.js/issues/108)
157+
158+
* Remove “unstable” from the website but not say it’s “stable”
159+
* Bert: big +1, use semver, don’t try and message something else, only concern is the version of V8 we are using
160+
* Discussed V8 4.1 and how “stable” it is
161+
162+
### Node.js and io.js should not break each other (no, they shouldn't)
163+
164+
[#631](https://github.com/iojs/io.js/issues/631)
165+
166+
Rod brought this up for quick discussion and draw attention to TC members for possible input.
167+
* Mikeal suggested that this should be taken to the website WG for better documentation
168+
169+
### Working group reports
170+
171+
* Streams
172+
- first WG meeting this week
173+
* Website
174+
- meeting next week
175+
176+
### Next meeting
177+
178+
* 4th of February
179+

0 commit comments

Comments
 (0)