| |
STE'86
Registered: Jul 2009
Posts: 274 |
CSDB as a "released at" field?
right,
Celtic has asked me to post the following for further discussion on here:
in the same manner as the Compunet entry has been added as a "released at" option, another addition could be made as "CSDB" to denote the modern entries that have been/will be first released directly onto CSDB and not the web/scene/parties/compos. to reflect CSDBs position in the current scene as CNET was in the past.
DISCUSS PLEASE
the admins will make a decision based on the discussion.
i will abstain from the discussion because i raised the question.
Steve |
|
... 23 posts hidden. Click here to view all posts....
|
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
No matter if one likes it or not, and no matter what the rules say, it is a fact that people have used CSDb as a major release site for ages by now. |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
Not to completely derail the thread, but this discussion is one of many about functionality in CSDB.
The mods/admin, Perff etc. have limited time to code and redesign, and often the same and the same "do this, or why not ?" discussions pop up.
We have 10 years of CSDB now, and any system has a life cycle, that includes, to be effecttive, that it be redesign, based on the years of experience with it, those learned from that period.
By doing a new design, mainly what functionalities are available, take the 10 years of learned experience, AND moving the whole stuff to implementation in an open source CMS (Joomla, Drupal etc.) - those with initiative and time, could help to maintain, build and improve a CSDB 2.0 in the future.
Doing a rebuilded CSDB, by hand code, requires a dedicated developer, and maintaining after that. If an overhauled CSDB is made in an open source CMS, it becomes easier for everybody. Same way as people make demos on a pc, because crossdev is easier/mor effective, i think its time to move away from systems, that only 1-2 persons know everything about, and are the only ones that can maintain and improve.
My 2 cents :)
If this would happen, i would be glad to spend a lot of time learning to use and master such a CMS.
Remember, even if its a CMS, like Joomla, a php coder, can always do his own code in it. Its not a limitation, its an opportunity to do more things, faster and more "this is not a hack" way. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11384 |
using joomla would be more like the "this is how to get hacked" way though =) |
| |
CreaMD
Registered: Dec 2001
Posts: 3057 |
Moving from custom code tailored to the needed speed and functionality to open-source cms? How that would help? Even the best opensource cms would have to be heavily modified for the main part of this project, that is the DATA and various ways of using it. Of course the idea isn't completely stupid, if we talk about frameworks. Recoding this to some decent framework would proably be good, but still this is not a money-making project, and rework of such scale would need investment of many unpaid hours. It could help maybe, if the database was open for data mining, then some team of developers using the decided framework could make a new frontend around it. But I'm not saying this is needed. Only thing there is really need for is speed up optimization of CSDB, it sometimes slows down. |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
once again i made a constructive suggestion, and once again the only answer we get from groepaz is just negative, not discussing it at all just saying "its to be hacked" etc.
how in any way are people supposed to discuss solutions and angles on anything, when he does this every time ?
this is the last constructive idea i will ever give, i will waste no more time ever on that.
from now im just a user, and all my creative ideas and inputs, are no more, not on csdb anyway.
Creamd's answer is more fair, he "discuss", reply to what was said.
firing groepaz is the best you can do.
the end
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11384 |
Quote:this is the last constructive idea i will ever give, i will waste no more time ever on that.
from now im just a user, and all my creative ideas and inputs, are no more, not on csdb anyway.
and this time you really mean it? |
| |
STE'86
Registered: Jul 2009
Posts: 274 |
Hasn't taken a certain moderator long to drop back into his old ways tho has it?
after all furore he caused 2 weeks ago.
nothing constructively discussed, just dismissed offhand as usual.
tut tut. BAD groepaz! |
| |
Moloch
Registered: Jan 2002
Posts: 2928 |
Quoting SIDwavethis is the last constructive idea i will ever give, i will waste no more time ever on that.
my prayers to the StatueTardis have been answered! \o/
Quoting SIDwavefiring groepaz is the best you can do.
Please "hire" more like groepaz, this place needs more moderators with a steady head and less whining. |
| |
Martin Piper
Registered: Nov 2007
Posts: 722 |
Quoting Groepazand this time you really mean it?
Your reply is off topic, you should delete it. If you cannot post constructive on topic comments then you shouldn't be posting.
*On topic*
The root cause of the problem brought up by the original post is the code running the site. Moving to a more well known CMS where the bugs have been fixed makes sense when there is a growing backlog of changes in the existing code or where the existing code is having to be patched by someone with limited resources. In that case it makes sense to utilise more than one person who can do the job. So from a software design and maintenance point of view it makes sense. |
| |
Martin Piper
Registered: Nov 2007
Posts: 722 |
Following on from my previous post...
I cannot see any harm in releasing the database for this site along with source code.
Obviously some tables need to be removed for account information and private messages. But I would wager a large proportion of the database and most of the database hits are for the publicly available information anyway.
It would be very instructive to see where the slow code for this site is. As CreaMD says " it sometimes slows down".
Certainly releasing the source with the public database information would allow any prospective developer using a CMS of their choice to run performance tests and compare the current code with new CMS code.
Page access logs, excluding IPs and certain private pages, would need to be made public too. To help build a picture of the expected load for the site, to help any performance testing efforts.
Two heads are better than one and all that.
Can anyone provide a good reason not to release all the public information as described above?
|
| Previous - 1 | 2 | 3 | 4 - Next |
