Hi,

even if I have no time to manage this idea, I would like to provide
you with the server infrastructure and software installation. 
Just tell me which wiki engine you prefer and we can install it.

The existing server has enough resources and we should keep all
project related information together.

bye
        Waldemar

On Wed, 09 May 2007 at 12:31 +0200, Johnny Halfmoon wrote:
> Hiya,
> 
> I would like to join the wiki attempt. I didn't immediately want to
> sugest doing it myself, because I know how easily I get distracted,
> especially since I'm going to be a daddy in about 6 weeks and I try not
> to start things I can't finish. But I find the project interresting and
> profitable enough (in a knowledge way) to give it a try. Unless people
> have some very good arguments against trying this, I would say let's
> give it a shot. Any other people technical and serious enough about
> this, with enough spare time, to give it a shot? @Lothar: We could start
> be exchanging some ideas about how to tackle this. Things like the
> project's goals, which servers to use, which software, who would like to
> do what etc... If it turns out it's not feasable or useful enough, or
> we're to lazy to finish what we started, then we can at least say we
> tried :)
> 
> Greetings,
> 
> Johnny
> 
> 
> Lothar Gesslein wrote:
> > Hi,
> >
> > Thank you for bringing up this topic!
> >
> > On Mon, 2007-05-07 at 22:22 +0200, Johnny Halfmoon wrote:
> >   
> >> For
> >> the time being I'll be doing some research on how to minimize wiki-spam
> >> and the maintanance time it consumes. Perhaps there are some people on
> >> this mailinglist that have ideas about how to handle the issue?
> >>     
> >
> > There are quite efficient ways to catch automated spam, the real problem
> > in a wiki is, imho, bad human-generated content. This can only be
> > "filtered" by humans, so we have to team up to maintain the wiki. This
> > can get quite a huge task, depending on the number of contributors.
> >
> > Nevertheless, I'm willing to form such a team and move the documentation
> > off to a extra wiki. I'd not use the trac wiki but rather install some
> > "real" wiki software with a speperate namespace and more features. 
> >
> > I think a _good_ wiki is doable and viable, if we do it right right from
> > the beginning. And as soon as we notice we get too much foobar in the
> > wiki, we just make it read-only (except approved logged-in users) until
> > we catched up with our work.
> >
> > We can still extract a pdf/tex/whatever handbook-like document out of
> > reviewed and tagged wiki pages with every stable release if this is an
> > imperative requirement.
> >
> > Suggestions, fair comment and refusal welcome.
> >
> > Regards,
> > Lothar
> >
> >
> > _______________________________________________
> > freewrt-developers mailing list
> > [email protected]
> > https://www.freewrt.org/lists/listinfo/freewrt-developers
> >
> >   
> 
> -- 
> Connaissez-vous la différence entre les riches et les pauvres ?
> Les pauvres vendent de la drogue pour s’acheter des Nike alors que
> les riches vendent des Nike pour s’acheter de la drogue.
> 
> ----------------------------------------------------------------------
> Finally - A spam blocker that actually works.
> http://www.bluebottle.com
> 
> _______________________________________________
> freewrt-developers mailing list
> [email protected]
> https://www.freewrt.org/lists/listinfo/freewrt-developers

-- 
don't open your wrt, free it
http://www.freewrt.org
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers

Reply via email to