Hacker News Reader

Comment by pault | Hacker News Reader

I agree. Who gets push access to master?

If not too many people want to post at the start, it can always just be a volunteer or two from the initial pool of interested people.

Perhaps, at the very beginning, the submitter could just take care of all the administration (hopefully it's not too much work) and everybody could work out a system for discussing and approving posts as a group.

By the way the "big thing" isn't the hardest part of this. The most important thing is probably the review of issue/pull request, and everybody who want to help can do that ;)

That depends on how closely affiliated with HN the blog is going to be and if our ycombinator benefactors are interested in endorsing such a project. If so, it should be one of them or someone they designate from the community.

If it is not associated to HN, then this is not an easily solved problem.

I love the idea of a community blog for HN readers, but I doubt anyone wants to make it official. Maybe we just see who's interested and hand the reins over to whoever has the highest karma?

I think that just having anybody with enough time to manage would do. As long as there's a focus on community, and everything gets discussed, any power issues should be remediable at the very beginning.

Basically, we should just have a community where the person managing the github account and whatnot is more like a sysadmin than a CEO. The main goal should be to find somebody willing to do a little extra work to get everything working.

Agreed; electing a button-pusher-in-chief shouldn't be an issue until someone actually contributes something, and at this point the OP is MIA. I think you should do it.

Reply on news.ycombinator.com