hi,
i wanna know how far you people have (like davepermen and RealityMonster) have coded, like you should make the progress transparent, so that other people can join in at any time.
I believe everyone is very good at something and thus can contribute his best stuff and make this into something very big!!

what to do about the publicity that really decided "how big"?
cyanide.

the issue about where to host is not over yet...
the pro''s seem to outweigh the cons if only they can get around the 1 updater restriction. that will mean another poorsoul like nehe will have to do the updatig. anyway i think what we want is for just about anyone to post a new tutorial without going through any extra work like emailing the moderator or stuff.

can we havve more info on the gdnet system? one point is that it will as someone pointed out, take a long time to code in all the features in gdnet with the reliability required from such a system.

comments..?

The reliability is definitely an issue here. To code a reasonably useful site with support for posting tutorials and Q&A-threads to go with, supporting membership-login, multi-moderators and the like isn''t really that much of a problem. As long as you can live with a system that is unreliable (especially under high loads, if it can handle high loads at all). Which I don''t think we can. Which is why I recommend using existing software (like GDNet is kind enough to offer us). *If* it can handle multiple moderators.
If not, I''m not sure.

~Neophyte



- Death awaits you all with nasty, big, pointy teeth. -

What are you referring to in relation to moderators? For approving submissions?

---
Michael Tanczos

well michael, every registered member must be able to add a new topic to the global directory of topics without the moderator intervening. the registered user will then post his tutorial under the newly created topic. after that others must be able to add to that topic(more tutorials, bug reports, comments etc)

is this possible?

Alternatively having a submission-system for new articles, but having more than one person with the power to accept the articles for "publication".

~Neophyte

- Death awaits you all with nasty, big, pointy teeth. -

better if its automated an realtime

But then we could just as well simply create a new forum here dedicated to interactive tutorials (although we would need better support showing source-code). I think it would be better with a submission-system.

~Neophyte

- Death awaits you all with nasty, big, pointy teeth. -

On the surface this sounds like a reasonable solution. Yes, anybody can submit a problem / source snippet solution. However, a forum would serve just as well for this kind of deal.

Why do I say that? Believe it or not, not everybody has good intentions when posting data on a site like Gamedev.net. While many people do, there are always a few who tend to abuse the system.

I do not think it would be wise to create a web site of this nature, without a moderator to approve the submissions. Putting them online right away is just asking for abuse, spam, useless posts, etc.

It may be the occasion that a user has good intentions, but has about the worst solution one could possibly provide. Somebody needs to be able to filter out quality from junk, or you''re left with a site filled with a lot of junk.

---
Michael Tanczos

I e-mailed Neophyte with this, but we can definitely support more than one person being able to post/moderate articles, at the very least using a single shared account.

If you want to just allow anyone to post, we can support that too, although it does open yourselves to abuse. Still, if you have some active moderators to remove new threads that aren''t actually articles, you may be fine.

One reason to go with having a few people responsible for posting articles is that you can do some quality control. Although the idea of having anyone be able to post their work is cool, what if the information they post is wrong? What if their writing is so bad it''s almost impossible to understand? What if they are using horrible coding practices that shouldn''t be allowed to spread? You can allow all of these if you want, but it will decrease the usefulness of the effort (IMO). If you have, say, 3-4 people willing to review and post articles, the time involved should be minimal (we get 3-4 article submissions a week, from a much larger user base, on a wide range of topics, and I handle them all myself).