A Nexuiz development blog

[Mute Print]

It's a blog integrated with the main site, not a remotely-hosted wordpress.org/nexuizdev type of thing? By all means, then, captain.

[[-z-]]

I'm not trying to be a debbie downer but this requires setup / system integration / maintenance and additional attention (time) from the devs that they could be spending writing code. Sure integrating the blog with the website sounds like a great idea but I estimate it to be ~8 hours worth of work. For a project div has already expressed his lack of interest in.

The svn has an RSS bot in the IRC channel... so maybe a feasible solution would be to parse these commits daily into 'blog posts' that are edited by a reviewer(s).

[C.Brutail]

I agree with [-z-].
If there's an auto generated pre-feed some volunteers can edit and publish, as for the news freak I am, I'd be more then happy to take part in this.

[Dokujisan]

but this requires setup / system integration / maintenance and additional attention (time) from the devs that they could be spending writing code.

Setup, sure. But I think it's worth the setup time/effort.

With proper use, I actually think it will save some of the developers time, Think of the time wasted on making changes to the crylink that they will end up having to change again later due to community outcry. That time could have been saved.

The contribution and maintenance of the blog can be done by volunteers that aren't the developers. So divVerent doesn't have to change anything that he's doing aside from occasionally explaining something with more clarity when asked (which he does already) because often the SVN notes don't make much sense to a casual observer.

The difference is that he would only need to explain something once. I see Div spending time on the IRC channels explaining things a lot and updating people on various aspects of Nexuiz. In theory, he would need to update only one person instead of 20 people.

[ai]

Or, why not ask a bunch of volunteers to do that work for them? Kind of like reporters. They ask the devs what's going on from time to time, and as they explain the reporters write it down, possibly simplify if there are lots of technical stuff and post it in a blog. Thus the devs won't waste too much time doing all this extra work, only the time they are on IRC and talk anyway about stuff. A good observant reporter could just quietly (if you want that) observe a conversation between the devs whenever he/she have the time and will.
Kinda like a Nexuiz Frontier, or something that reports what's going on. lool

[Dokujisan]

[ai]

I don't get the point, but it was surprisingly entertaining

[Dokujisan]

simple summary

1) Doku's favorite game is Nexuiz

2) Doku tries to use words he doesn't understand.

3) There are so many options for getting info on Nexuiz development! Yay!

4) Doku attempts to get info

5) Crap... too many options... can't find the info that I want.

6) Omg, Britney Spears is gonna eat me! Ahh!!!

[ai]

5) Crap... too many options... can't find the info that I want.

Choose one option, read through that, choose another, read through that and so on.
I always thought that the more places you can get info the better, as then you can verify some information with other places and find the info a lot faster. You have to be the first one that I've run into who has problem with too many options

[esteel]

Well that ( http://svn.icculus.org/nexuiz/branches/ ... s?view=log ) would be a first starting point for info about changes. I think i already gave a quick overview of what was changed and as DivVerent in not having time to do more then coding and doing changelogs it will be up to others to make something nice out of it. I'll see to find some time for that but the commit logs are quite understandable already..