My thoughs on the lacking features of Coranto

[msbzdragn]

The only way anything can be done with the script is with a tightly controlled, exclusive group of programmers, or even just one programmer. Someone has to hold control over the script the way Linus Torvalds acts as a de facto commander in chief of Linux kernel development.

I have to say I strongly agree with that sentiment. Sorry to hear you can't take a larger part, plushpuffin, but I also understand and am glad you're even taking the time to comment here...

[SrNupsen]

I saw myself mentioned earlier in this thread as a possible contributor, and I would like to stress again that I have no interest in any further development of Coranto or Coranto addons. I also think the senate idea is stupid. It failed horribly before, and the Coranto community doesn't have the talent or motivation it did a year ago. The only way anything can be done with the script is with a tightly controlled, exclusive group of programmers, or even just one programmer. Someone has to hold control over the script the way Linus Torvalds acts as a de facto commander in chief of Linux kernel development.

Well we do try our very best both as to talent and motivation. Sad to hear you've had enough, but a perfectly valid attitude. And, might I add, one of the reasons Coranto development will necessarily have ups and downs - everybody wants to spend a certain amuount of time on it, then the interest fade away (or disappear for other reasons).

The Linus Torvalds of Coranto would naturally be elvii, but he' s not around anymore. So we'll have to stick to making updates to a script we don't own, ready to surrender it all in case the original author should stop by during the next 50 (or 75) years.

Actually, every person that spends some of her/his talent and motivation here makes me happy!

SrNupsen

[neostasis]

I have got to say, coming from the same kind of background as muttly that I agree with many of his points. I may have some technical background, but not a hell of alot and much of what I read around the forums assumes members are all developers.

Ialso have to sat\y that homepage is in a definate need of a serious overhaul.

i used newspro bacjk in its heyday and I swear the homepage wasn't that different all the way back then.

the overhaul doesnt need to be huge, but certainly an update in look and feel is needed to something a little more clean cut and proffesional.

[msbzdragn]

i used newspro bacjk in its heyday and I swear the homepage wasn't that different all the way back then.

Considering NewsPro was on a complete different site with a bright orange and red background and no graphics whatsoever, I can promise you the homepage was very different back then. This is also the second - possibly third - site design that this site has had since Mark Olson set it up years ago.

[Parahead]

I have got to say, coming from the same kind of background as muttly that I agree with many of his points. I may have some technical background, but not a biscuits of alot and much of what I read around the forums assumes members are all developers.

Yes, muttly has some good points, I agree! Most of his points concern tutorials (or lack of) and just recently a documentation project has been started by Dale Ray to cure this! The problem is that the majority of the people that is actually dedicating time to Coranto are developers, and most developers suck at writing documentation (I am no exception!), and when we do write it often becomes to technical. Yes, pointing out what is missing and giving feedback is ofcourse great, but there is only one real solution, more non-developers must take active roles and actually help out to produce tutorials/HowTos/FAQ/documents.

Regarding the site design, you are not the only one that think this site needs a small face lift and reorganization of the content... I think SrNupsen have many plans he will kick into action this automn...

[msbzdragn]

Developers do have the advantage that they're familiar with the core and its potential though. My ideal would be to have a developer draft the documentation, and then a writer clean it up.

[VZey]

great. now who is going to write the draft?

[Parahead]

Developers do have the advantage that they're familiar with the core and its potential though. My ideal would be to have a developer draft the documentation, and then a writer clean it up.

I agree! With the addition of the developer getting input at the very start of what it is that actually needs explaining, much like in the way that muttly have done his suggestions.

great. now who is going to write the draft?

I think we where talking in general terms of documentation and draft, not a particular one? Dale Ray is in charge of the documentation project and currently he tries to collect all available docs around on different sites. I also know he has a base structure he would like to fill with content, the availble docs may fill some gaps in that structure, the rest will have to be written... So I think we have to wait a while and then get back to exactly which ones already exists (but may need polishing?) and which ones need to be written...

But if anyone has an urge to write documention in any area right now, I will of course not try to stop that person in any way, but instead would encourage him/her! I would suggest taking contact with Dale Ray so that things can be syncronized though...