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

Website owner #21

Closed
mikeal opened this issue Jan 8, 2015 · 4 comments
Closed

Website owner #21

mikeal opened this issue Jan 8, 2015 · 4 comments

Comments

@mikeal
Copy link
Contributor

mikeal commented Jan 8, 2015

Heya,

Per the last TC meeting I've been reluctantly put "in charge" of the website.

After taking a quick look through the Issues and PRs I can see that we do need an owner/facilitator and, for the time being, that has fallen on me.

My immediate plan is to get something up that we can use for the launch next week. After that I want something in place that is easily updatable for each weekly release.

From there I'm going to reach out to proper designers to get involved and once we have some experienced people around I want to hand over the this owner/facilitator role to them.

Unless there are any strong objections I'll be merging the redesign PR and use that as a starting point.

@indexzero
Copy link
Contributor

+1. I've been loosely following the PRs coming in, let me know if I can help.

@snostorm
Copy link
Contributor

snostorm commented Jan 8, 2015

FYI the PR above refers to #17

I'm all for doing a quick release to get the ball rolling. We can iterate fast off of a simple static HTML/template base as needed. (We're far away from dealing with a mountain of content or polished marketing materials, and the project is still very young.)

By the way I say we as I intend to help where I can.

@Fishrock123
Copy link
Contributor

My immediate plan is to get something up that we can use for the launch next week. After that I want something in place that is easily updatable for each weekly release.

Absolutely. I'd like to work on this more but daytime work kinda burns me out, hopefully I'll be able to contribute more this weekend.

From there I'm going to reach out to proper designers to get involved and once we have some experienced people around I want to hand over the this owner/facilitator role to them.

I'm willing to own some, but only some.

Unless there are any strong objections I'll be merging the redesign PR and use that as a starting point.

Go ahead. I personally would prefer if PR's are merged io.js core style, aka no merge commits when possible. We should discuss this.

Please also see #14, and I'd really like to see #19 happen.

@Fishrock123
Copy link
Contributor

So I really have no clue what is going on here or what we need.

@mikeal mikeal closed this as completed Jan 12, 2015
snostorm pushed a commit that referenced this issue Feb 27, 2015
Oversett resten av FAQ-en til norsk
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