Skip to content

Commit 99e7c58

Browse files
mikealrvagg
authored andcommitted
doc: add TC notes from october 29th
PR-URL: node-forward/node#41 Reviewed-By: Ben Noordhuis <[email protected]> @rvagg: cherry-picked 2c7847b and e7dec60 from master to v0.12
1 parent 26b11d5 commit 99e7c58

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed

doc/tc-meetings/2014-10-29.md

+33
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
* Update on Build
2+
* @rvagg is working on getting the builds consistently green
3+
before moving on to more complicated things.
4+
* @issacs brought up the Joyent Advisory board
5+
* Some confusion out there about Node Forward vs. Advisory Board
6+
* @mikeal updated the messaging on the website to be clearer
7+
* The website has clearer calls to action for the community
8+
* Libuv move
9+
* The libuv contributors want to move to the libuv org.
10+
* @mikeal will email @indutny and other libuv contributors to ask them
11+
to log an issue about this on their repo for transparency and so that
12+
this is not a surprise to Joyent
13+
* Update on "release buckets"
14+
* doesn't make sense while we're private, we'll wait until it is public again
15+
* `node-forward/node` going public
16+
* when we made the repo private it was messaged as only being for "four weeks"
17+
* "four weeks" is up on November 8th
18+
* someone on the Advisory Board needs to remind Joyent of this in the
19+
next advisory board meeting so they aren't suprised by it even though
20+
it was communicated to them when it was first made public.
21+
* @mikeal will work on the messaging in the README to make it clear this is
22+
a "soft" fork and not a "hard" fork.
23+
* ramifications of going public will be discussed in next week's TC meeting as
24+
well
25+
* @mikeal proposed a change in TC meeting process
26+
* it's impossible to schedule all the timezones involved in every meeting
27+
* every Monday create a "Weekly TC Agenda" Issue people can contribute to
28+
* the TC members who care about that Agenda will state they want to be in the
29+
meeting
30+
* @mikeal will work to schedule the TC members who care for a hangout
31+
* people are using and liking gitter
32+
* we'll consider moving from IRC to gitter once the repo is public again
33+
* yes, gitter has IRC integration (you can login to gitter from an IRC client)

0 commit comments

Comments
 (0)