Create a website team

[rvagg]

Just like we're doing for build and streams, we need a website team with some form of structure. Could we start some discussion amongst interested individuals about how this might work. Ideally there should be semi-regular broadcast Hangouts On Air that we can put on the iojs calendar and let others tune in to (real-time or the recordings), so it needs a facilitator of some kind to make that happen.

The governance guidelines for io.js allow for other parties to occasionally join in on TC meetings, we already have that for the build project but I'm going to suggest that the TC regularly have non-TC representatives of streams and website on too.

[Fishrock123]

👍

[snostorm]

I'm going to lurk on this project's existing issues/general state before chiming in more, but this seems like a good suggestion to me.

There are a few ways io.js, as a project and community, may be able to really establish itself to the broader JS/node community through a strong website effort. In addition to providing some clean documentation (by this I mean "guides", on top of the existing API docs), there's a great opportunity to put the spotlight on the open governance model the team has started to put in place.

This can be communicated through regular blogging, advertising the sub-project/committees (and their respective scheduled events/progress updates), linking to those component projects, etc.

Also, earlier in the "how io.js might manage the release cycle" type discussions I linked to https://developer.mozilla.org/en-US/Firefox/Releases as an example a direction of where the project could go (assuming we were to maintain a production / beta / nightly, pre-scheduled release process.) I specifically mentioned this style as I like how the version pages include details on what's upcoming.

By reading ahead to something like https://developer.mozilla.org/en-US/Firefox/Releases/36 I know a) when to expect these features in a stable sense; b) what to test against now when running the beta/alpha; c) I can mentally prepare for upcoming API changes, deprecations, feature flag removals, etc.

[klaemo]

I'm interested in helping out with the website in any way possible.
Setting up hosting, build tools, frontend work...whatever's needed.

[laosb]

I can help when free, too. I can also create a Chinese translation.

[iamphill]

Happy to offer my services for any frontend work 👍

[Fishrock123]

Proposing Myself, @mikeal, @therebelrobot, @snostorm, and @zeke for the "team", if all are willing.

#22 is basically why this is useful haha.

[therebelrobot]

I'm game :)

[snostorm]

👍 @Fishrock123

[rvagg]

make it so! @Fishrock123 how about you take lead in organising a first "meeting" some time this month, do a hangouts on air and we'll share it via the io.js calendar and promote it like TC meetings

[zeke]

I'm in!

[snostorm]

FYI there's a lot of sensible typo fixes, etc. coming in to this branch as more eyes are now hitting the new site. I'd like us to be able to respond/merge some of these sooner than later. Any chance my suggested team "membership" could be expedited (by that I mean GitHub access?)

I was actually thinking (but forgot) I wanted to open an Issue today re: finding a time for our first team (public) hangout / meeting, so I'm glad for the reminder @rvagg.

Note: I'm in UTC+1.

[rvagg]

Adding @therebelrobot, @snostorm, and @zeke to the Website team for this org, you'll get an invite but it's up to you whether you accept or not. You can start managing issues and landing fixes at will, I'd suggest reading https://github.com/iojs/io.js/blob/v1.x/COLLABORATOR_GUIDE.md, specifically about the approach to (a) taking responsibility but balanced with (b) a team leadership approach. Ultimately it's up to this team to come up with a sensible way of working together as long as it's in the same spirit as the rest of the io.js project (e.g. I hate the strict git rules in iojs/io.js so am not imposing the same on iojs/build) and it'll also have to submit to the TC's leadership (where there is any--I think I'd expect the TC to remain relatively distant from the website effort).

[jeffshaver]

Would be interested in helping with front-end stuff in my free time for sure

[Fishrock123]

I still don't like the github "merge pr" button very much. Just makes things confusing.

[mikeal]

First website working group meeting is being scheduled https://doodle.com/nzkegz5mk3k5ucpd#admin

[zeke]

Bummer. I have an appointment I cannot miss during that time. Pretty much any other time would work. If the meeting happens at that time and I miss it, I will share a list of questions/ideas I wanted to discuss.

[snostorm]

@zeke going to try to get us a few more options on dates/times. We'll continue this on #59

[therebelrobot]

Now that we've added new collaborators, is this taken care of now? Can we close this issue?

[indexzero]

Yes. I think we're good here except one thing, do we want to document it somewhere?

[jeffshaver]

I am in. I posted elsewhere. Don't know if it was seen

[therebelrobot]

@indexzero, yeah, we should have a list somewhere... maybe a CONTRIBUTORS doc in the repo? or a page on the site? That should probably be discussed at the next meeting.

[Fishrock123]

Let's close this once we actually have a meeting.

[rvagg]

go for the README.md IMO, see the one in iojs/io.js where we are starting to list collaborators, I hope for this list to grow much longer but promoting it on the README is a good way to give kudos to those that actually put in the hard work

[therebelrobot]

commit by @mikeal fixes this. closing.