From: Bernd E. <eid...@we...> - 2005-06-06 08:52:18
|
Hi, _please_ excuse the delay for bringing up the homepage. There is a first version at www.servercult.com now. Feel free to bring up everything you like or dislike. This is just a proposal (and also work in progress). In my opinion some very basic texts describing the 'why' and 'where to go' of the project should be made available for the community; also I agree with you to keep the content low to focus work on the more important areas! Until direct login is possible for you please send me any content you like to add, see, change! Regards, Bernd. |
From: Stephen D. <sd...@gm...> - 2005-06-13 08:00:31
|
On 6/6/05, Bernd Eidenschink <eid...@we...> wrote: >=20 > Hi, >=20 > _please_ excuse the delay for bringing up the homepage. There is a first > version at www.servercult.com now. Don't worry about it, it took me just as long to reply... :-) > Feel free to bring up everything you like or dislike. This is just a prop= osal > (and also work in progress). >=20 > In my opinion some very basic texts describing the 'why' and 'where to go= ' of > the project should be made available for the community; also I agree with= you > to keep the content low to focus work on the more important areas! >=20 > Until direct login is possible for you please send me any content you lik= e to > add, see, change! >=20 > Regards, > Bernd. How does everyone feel about using a wiki? Take a look at this:=20 http://psplinux.sourceforge.net/ -- These folks are using MediaWiki, the software behind the WikiPedia project, on their Source Forge hosted web site. Now take a look at this site: http://hula-project.org -- This is the exact same software with a different template running the main website for Novell's new Hula mail/calendar server software. Looks nice. I've looked at MediaWiki briefly. It comes with half a dozen templates which can be used as a starting point to achieve the look and feel that Bernd's developed. I think we'd run it slightly differently than the AOLserver wiki we're already familiar with. We'd auto-generate Zoran's fancy new docs from CVS as static pages, maybe using the wiki for comments. Also, we'd auto-generate a list of modules straight out of CVS so that it's always up-to-date. So, how about it? I think it would be an easy, low maintenance way to get a lot of people participating quickly. |
From: Vlad S. <vl...@cr...> - 2005-06-13 15:01:32
|
I like auto-generating idea:-))) Stephen Deasey wrote: > On 6/6/05, Bernd Eidenschink <eid...@we...> wrote: > >>Hi, >> >>_please_ excuse the delay for bringing up the homepage. There is a first >>version at www.servercult.com now. > > > > Don't worry about it, it took me just as long to reply... :-) > > > >>Feel free to bring up everything you like or dislike. This is just a proposal >>(and also work in progress). >> >>In my opinion some very basic texts describing the 'why' and 'where to go' of >>the project should be made available for the community; also I agree with you >>to keep the content low to focus work on the more important areas! >> >>Until direct login is possible for you please send me any content you like to >>add, see, change! >> >>Regards, >>Bernd. > > > > How does everyone feel about using a wiki? Take a look at this: > http://psplinux.sourceforge.net/ -- These folks are using MediaWiki, > the software behind the WikiPedia project, on their Source Forge > hosted web site. > > Now take a look at this site: http://hula-project.org -- This is the > exact same software with a different template running the main website > for Novell's new Hula mail/calendar server software. Looks nice. > > I've looked at MediaWiki briefly. It comes with half a dozen > templates which can be used as a starting point to achieve the look > and feel that Bernd's developed. > > I think we'd run it slightly differently than the AOLserver wiki we're > already familiar with. We'd auto-generate Zoran's fancy new docs from > CVS as static pages, maybe using the wiki for comments. Also, we'd > auto-generate a list of modules straight out of CVS so that it's > always up-to-date. > > So, how about it? I think it would be an easy, low maintenance way to > get a lot of people participating quickly. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |
From: Zoran V. <zv...@ar...> - 2005-06-13 15:19:15
|
Am 13.06.2005 um 10:00 schrieb Stephen Deasey: > On 6/6/05, Bernd Eidenschink <eid...@we...> wrote: > >> >> Hi, >> >> _please_ excuse the delay for bringing up the homepage. There is a >> first >> version at www.servercult.com now. >> > > > Don't worry about it, it took me just as long to reply... :-) > > > >> Feel free to bring up everything you like or dislike. This is just >> a proposal >> (and also work in progress). >> >> In my opinion some very basic texts describing the 'why' and >> 'where to go' of >> the project should be made available for the community; also I >> agree with you >> to keep the content low to focus work on the more important areas! >> >> Until direct login is possible for you please send me any content >> you like to >> add, see, change! >> >> Regards, >> Bernd. >> > > > How does everyone feel about using a wiki? Take a look at this: > http://psplinux.sourceforge.net/ -- These folks are using MediaWiki, > the software behind the WikiPedia project, on their Source Forge > hosted web site. > > Now take a look at this site: http://hula-project.org -- This is the > exact same software with a different template running the main website > for Novell's new Hula mail/calendar server software. Looks nice. > > I've looked at MediaWiki briefly. It comes with half a dozen > templates which can be used as a starting point to achieve the look > and feel that Bernd's developed. > > I think we'd run it slightly differently than the AOLserver wiki we're > already familiar with. We'd auto-generate Zoran's fancy new docs from > CVS as static pages, maybe using the wiki for comments. Also, we'd > auto-generate a list of modules straight out of CVS so that it's > always up-to-date. > > So, how about it? I think it would be an easy, low maintenance way to > get a lot of people participating quickly. > What infrastructure would be needed to run MediaWiki? Do we have time/knowledge to set it up (I don't). OTOH, the fact that everybody can freely participate (wiki) appeals to me because it eases the burden of maintenance. Both projects you quoted look pretty nice, BTW. Zoran |
From: Zoran V. <zv...@ar...> - 2005-06-13 20:51:06
|
Am 13.06.2005 um 17:19 schrieb Zoran Vasiljevic: > What infrastructure would be needed to run MediaWiki? Ehm: Prerequisite tools To install MediaWiki you need four components: MySQL - an SQL database to store the Wiki text, user list etc. Apache - a web server to serve the HTML web pages PHP - the programming language that MediaWiki is written in. Fedora/ Redhat users will also need the PHP-Mysql package. MediaWiki itself, which is a suite of programs written in PHP I do not know where should we get all these things? Does SourceForce offer this is part of their services? Zoran |
From: Stephen D. <sd...@gm...> - 2005-06-14 07:19:05
|
On 6/13/05, Zoran Vasiljevic <zv...@ar...> wrote: >=20 > Am 13.06.2005 um 17:19 schrieb Zoran Vasiljevic: >=20 > > What infrastructure would be needed to run MediaWiki? >=20 > Ehm: > Prerequisite tools >=20 > To install MediaWiki you need four components: >=20 > MySQL - an SQL database to store the Wiki text, user list etc. > Apache - a web server to serve the HTML web pages > PHP - the programming language that MediaWiki is written in. Fedora/ > Redhat users will also need the PHP-Mysql package. > MediaWiki itself, which is a suite of programs written in PHP >=20 > I do not know where should we get all these things? > Does SourceForce offer this is part of their services? They do. I wasn't sure how hard it would be to set up, so I gave it a try. Behold: http://naviserver.sourceforge.net ! It wasn't so hard.=20 The source is checked into CVS: http://cvs.sourceforge.net/viewcvs.py/naviserver/website/htdocs/wiki/ I still need to set up an auto-update script to cvs up the website every hour or so. I configured it so that you have to log in to edit pages. If y'all create accounts with your sourceforge name I'll give you sysop privs, with which you can delete pages, ban users etc. So, have a play with it, see if you think this will work for us.=20 There's some documentation on the software here: http://meta.wikimedia.org/wiki/MediaWiki_FAQ |
From: Bernd E. <eid...@we...> - 2005-06-13 09:02:58
|
> > Until direct login is possible for you please send me any content you > > like to add, see, change! I forgot to mention that this is just because we decided to rewrite the frontend display stuff so that it uses tdom/xml/xslt and now just have to bring our existing cms forms step by step into the xslt world :-) Nothing against a Wiki, nothing against templates, nothing against even a totally different homepage look if you like. I just like the idea of having a project homepage that actually runs the software it promotes and somehow can imagine situations where a little bit more control or programming power (TCL/Naviserver) would be nice to have. Importing documentation should be no problem, also exporting can be done via xml. What about discussion boards or newsletters with Wikis? We can provide such apps, xslt-comments from above apply. On the other hand I can understand if you all like more direct control over that stuff as would the Sourceforge solution provide. May the majority decide! Bernd. |
From: Stephen D. <sd...@gm...> - 2005-06-14 07:30:30
|
On 6/13/05, Bernd Eidenschink <eid...@we...> wrote: > > > Until direct login is possible for you please send me any content you > > > like to add, see, change! >=20 > I forgot to mention that this is just because we decided to rewrite the > frontend display stuff so that it uses tdom/xml/xslt and now just have to > bring our existing cms forms step by step into the xslt world :-) >=20 > Nothing against a Wiki, nothing against templates, nothing against even a > totally different homepage look if you like. >=20 > I just like the idea of having a project homepage that actually runs the > software it promotes and somehow can imagine situations where a little bi= t > more control or programming power (TCL/Naviserver) would be nice to have. The thing is, our website isn't the best vehicle for showing off what the software can do because the requirements of our website are minimal. One of the most important things is that we're able to just forget about it and get on with developing the software. It would be really nice to have some info on the website showing how people are using the technology in real projects. Some code examples and behind the scenes info would surely interest people more than the finished, redered page. > Importing documentation should be no problem, also exporting can be done = via > xml. What about discussion boards or newsletters with Wikis? We can provi= de > such apps, xslt-comments from above apply. Source Forge provides news and discussion forums. I turned off the forums to keep the tiny user base all on the mailing list. We've had no news, as yet :-) > On the other hand I can understand if you all like more direct control ov= er > that stuff as would the Sourceforge solution provide. >=20 > May the majority decide! >=20 > Bernd. |
From: Bernd E. <eid...@we...> - 2005-06-14 08:24:05
|
Hi Stephen, > The thing is, our website isn't the best vehicle for showing off what > the software can do because the requirements of our website are > minimal. One of the most important things is that we're able to just > forget about it and get on with developing the software. year, thats true. Let's focus, content like tutorials, help and examples is by far more important for the project than an underlying webserver. btw, the code standards page really looks great! Regards, Bernd. |
From: Zoran V. <zv...@ar...> - 2005-06-14 07:51:04
|
Am 14.06.2005 um 09:19 schrieb Stephen Deasey: > > They do. I wasn't sure how hard it would be to set up, so I gave it a > try. Behold: http://naviserver.sourceforge.net ! It wasn't so hard. > The source is checked into CVS: > http://cvs.sourceforge.net/viewcvs.py/naviserver/website/htdocs/wiki/ Is there a word on MediaWiki on the SF site where you got the info how to set it up? Zoran |
From: Stephen D. <sd...@gm...> - 2005-06-14 08:03:35
|
On 6/14/05, Zoran Vasiljevic <zv...@ar...> wrote: >=20 > Am 14.06.2005 um 09:19 schrieb Stephen Deasey: >=20 > > > > They do. I wasn't sure how hard it would be to set up, so I gave it a > > try. Behold: http://naviserver.sourceforge.net ! It wasn't so hard. > > The source is checked into CVS: > > http://cvs.sourceforge.net/viewcvs.py/naviserver/website/htdocs/wiki/ >=20 > Is there a word on MediaWiki on the SF site where you got the info > how to set it up? There is, but I didn't see it until after I completed the install... You'll want to look at the Source Forge docs to see how the project web hosting works: http://sourceforge.net/docman/display_doc.php?group_id=3D1&docid=3D4297 The install of Mediawiki is pretty easy -- the INSTALL doc in the tarball is short and it comes with a web interface where you fill in some forms and it creates the config file for you. Here's the Source Forge specific installation docs: http://meta.wikimedia.org/wiki/Running_MediaWiki_on_Sourceforge.net |