A Nexuiz development blog

[[-z-]]

The community has more than enough methods of communication available already. Maybe a dev sticky could be maintained in the appropriate forum?

Creating a forum sticky for it would be a poor solution. A blog is much more than just a few news updates. The databases are usually filled with goodies to increase your SEO and help promote whatever it is you're writing about.

By the classic look of the forum, I'd assume many users are unaware of RSS save the savvy firefox users who understand the RSS icon in their address bar. Blogs usually flaunt it to attract more users.

[Fisume!]

good idea

[pavlvs327]

I think this is the best idea I have heard in a long time. I would definitely be willing to write for it, too, pulling the important bits from the SVN logs.

[John Galt]

I would love to see a Dev blog. I'd follow it religiously

[esteel]

Well, i'll try to find some time to update the dev wiki a bit..
But basicly currently a LOT of stuff is moved over to use CSQC (client side quakec) which will reduce network load, make things smoother, less load on the server and maybe more control on the client. Things like a new hud, better way to transmit centerprints, some effects like the hook beam, zoom(!) are now done via CSQC. Besides some fixes, new menu skins, a few texture tweaks, new player sounds, race game mode, on screen map for ONS game mode.. such stuff.

[divVerent]

You could read the svn commit messages on the nexuiz-2.0 branch (NOT on the trunk). That should have much less noise from the "fixes-for-the-fixes" as I only merge changes over when I think they are stable.

As for a blog - I already write commit messages, why should I write the same work AGAIN? I certainly wouldn't post there.

[halogene]

You could read the svn commit messages on the nexuiz-2.0 branch (NOT on the trunk).

Sorry to ask such a noob question, but could you provide a link?

[HarryButt]

Sorry to ask such a noob question, but could you provide a link?

Anyway, imo the development status should be available from the website, so that noobs (and me ) don't have to look that much in the depths of the forums. It's quite common to provide that kind of information, so I don't see why Nexuiz doesn't.

[Dokujisan]

As for a blog - I already write commit messages, why should I write the same work AGAIN? I certainly wouldn't post there.

Well, the problem is that there are too many places for development information, and none if it is provided in a summarized fashion.

As I said before, think of the blog concept as a funnel and filter. Perhaps there could be someone who would perform the task of upkeeping the blog. Then this person (or people) would know where to look for dev updates, and to ask the devs for more clarity on topics when needed.

Maybe a few of us from the community can work together to maintain it, but it really should be on the Nexuiz website, or at least linked from it. Otherwise, we could just do this on the nexuizninjaz.com site, but then a lot of people wouldn't see it.

[Fisume!]

Adding the blog into the nexuiz website sounds good for me.