We need another meeting!

[Qard]

We are way overdue for another meeting. 4.x has been out for awhile now, and @nodejs/website has the keys to nodejs.org now. We need to coordinate with the Website WG to get what we've got onto the website and do something about the collaboration-unfriendly state the repo is currently in.

I've put together a doodle to find a time next week: http://doodle.com/poll/8wwpw97f62gpawrx

The agenda doc is here, please suggest more stuff to discuss:

https://docs.google.com/document/d/1TdP8dKDy24nM3Scv9I-NN-RsFbuveX8Foys01SCh-bw/edit?usp=sharing

@nodejs/documentation @nodejs/website

[mikeal]

We shouldn't default to a meeting when things aren't moving along. Ideally
meetings are held to resolve disagreement when it exists but the issues
you've brought up have just started being discussed and may be able to be
resolved without a meeting. I'm not saying you won't need a meeting at some
point but you should enter the meeting with competing solutions to the
problems you're raising and I haven't seen those proposals in the issues
yet. I'm pretty sure you have some ideas on how to fix these and I think
you should post them as new issues, referencing the issues where the
problems have been discussed. If there is no disagreement with those
solutions then we can implement them w/o a meeting ;)

On Tuesday, October 6, 2015, Stephen Belanger notifications@github.com
wrote:

We are way overdue for another meeting. 4.x has been out for awhile now,
and @nodejs/website https://github.com/orgs/nodejs/teams/website has
the keys to nodejs.org now. We need to coordinate with the Website WG to
get what we've got onto the website and do something about the
collaboration-unfriendly state the repo is currently in.

I've put together a doodle to find a time next week:
http://doodle.com/poll/8wwpw97f62gpawrx

The agenda doc is here, please suggest more stuff to discuss:

https://docs.google.com/document/d/1TdP8dKDy24nM3Scv9I-NN-RsFbuveX8Foys01SCh-bw/edit?usp=sharing

@nodejs/documentation https://github.com/orgs/nodejs/teams/documentation
@nodejs/website https://github.com/orgs/nodejs/teams/website

—
Reply to this email directly or view it on GitHub
#43.

[Qard]

True, but I feel like we really need to get everyone on the same page. There was a bunch of activity and then silence for awhile. The problem with async communication like github issues is that it's too easy to procrastinate responding/acting. My hope is that, by planning a meeting, I can get people on a call together and sort through the issues all at once.

What do you think? A time-boxed issue might also work.

[mikeal]

Maybe start with a time boxed issue because if you cant get engagement on
that I doubt you can get the doodle filled out for a meeting :(

On Tuesday, October 6, 2015, Stephen Belanger notifications@github.com
wrote:

True, but I feel like we really need to get everyone on the same page.
There was a bunch of activity and then silence for awhile. The problem with
async communication like github issues is that it's too easy to
procrastinate responding/acting. My hope is that, by planning a meeting, I
can get people on a call together and sort through the issues all at once.

What do you think? A time-boxed issue might also work.

—
Reply to this email directly or view it on GitHub
#43 (comment).