All good points, and I definitely agree that having a flat access structure is very nice. Perhaps we can keep it even if we use a CMS? Worth looking into.
But, here are some arguments FOR a CMS: 1. We except articles to be written not by devs, but by users. I.E. People who are not technical enough to fiddle with CVS, or even HTML. They are good at writing and they can use a word processor. We shouldn't create a barrier of entry for these people. 2. It automatically provides all the things a website needs. Many of which are lacking in the current site. For example: Search, RSS feeds for posts, flexible templates & styles, wysiwyg editors & previews, taxonomy. Additionally a few CMSes also provide modules for integrating our other systems (wiki, bugs, etc) into the site. 3. Module support. Most big CMSes have support for modules. This means, they have a large library of 3rd party modules already, and its relatively easy to whip up our own. This means we can integrate all our other systems into the main e.org website. We could put the latest wiki articles on the front page, or the highest rated themes from exchange, or the latest CVS commits. Of course, we could write all of these things ourselves and stick 'em into CVS, but having a nice module api definitely helps speed up development. And some of these modules already exist. As far as the wiki being the place for articles, it definitely is the place for how-tos and tutorials, but its no place for news articles, articles on new features (wikis have a very poor sense of time) and articles that just show off EFL & E. On Sat, Aug 2, 2008 at 2:47 AM, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote: > On Sat, 2 Aug 2008 00:18:23 -0500 "Nathan Ingersoll" <[EMAIL PROTECTED]> > babbled: > > i agree here. i like our fairly flat (and lax) access structure. if we trust > you to go writing bits of e.org's website - we trust you to write code - if > that is your skill, or to just know to keep your hands off what you aren't > good > at. people make mistakes and if someone who was given access in order to do > www > goes and starts screwing with code so it breaks - a few reprimands on the > mailing lists should cure that really fast, and if it doesn't - access to cvs > can be removed (and will be) as if we can't trust them - why keep access to > www? > > i like our own and flat trust structure. it's simple. it works as we are not a > massive organisation. it allows or fluid movement and help wherever it is > needed quickly. it shows we have faith in our fellow humans :) > >> On Fri, Aug 1, 2008 at 5:27 PM, The Rasterman Carsten Haitzler >> <[EMAIL PROTECTED]> wrote: >> > >> > so eventually went back to an old original method. www lives in cvs - u >> > want to work on it, u get cvs access. committing means it auto-updates. if >> > u need to test the php locally setting up a local apache and mod-php, allow >> > symlinks outside of the www doc dir to point to your homedir's cvs checkout >> > of the www site, worsk just fine. it's simple and works. the php is also >> > very simple. the main www site is meant to be simple and relatively static >> > - the wiki, and other sites (trac, bugzilla etc.) are where the dynamic >> > stuff happens... >> >> There is another advantage to keeping the site in CVS: you avoid >> segmenting the community into artificial sub-communities, or trying to >> place technical barriers around social structures. There is a flat >> hierarchy of trust, either you've earned it enough to get access or >> you haven't. There is no temptation to give people access to the >> website since it's "only the website", and anyone with CVS access >> should know how interact within the project. >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> enlightenment-devel mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > enlightenment-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
