FreeLists / haiku-web / [haiku-web] Re: Trac (reevaluated)

["Mikael Jansson (mailing lists)" <lists@xxxxxxxxxxxxxxxxx>]

"John Drinkwater" <jdrinkwater@xxxxxxxxx>:
>
> I've been reading since the list opened, and I'm normally quite 
> quiet
> 
> On 6/10/06, Waldemar Kornewald <wkornew@xxxxxxx> wrote:
> > Jorge G. Mare (a.k.a. Koki) wrote:
> > > I could write reasonably good copy (although English is not my 
> > > mother
> > > tongue); I am also sure that there is talent out there that could 
> > > do a
> > > good job; you may need more than one person.
> >
> > The biggest problem is that we don't have good end-user 
> > documentation. The
> > website is really a minor issue compared to this problem. If you 
> > want you can
> > take over that task and organize a complete team to work on the 
> > documentation.
> > A few people started the (unofficial) Haiku documentation here:
> > http://en.wikibooks.org/wiki/Haiku
> > It could become the official Haiku documentation.
> 
> If it does, can it move to our site/wiki ? I understand that it has
> already been started there, but it would be nice if everything wasn't
> distributed. Depending on reply and/or contact with the authors, I'll
> do that "work".
> 
> > We also need people working on the HaikuBook (API documentation).
> 
> I haven't seen much of the documentation team recently; i've seen 
> lots
> of talk in the past about them doing a lot of work on the DocBook
> system, have they folded?
> I can offer to help here if the 'team' needs to be reformed.
> 
> > I don't always have enough time to watch everything, so I fear that 
> > it
> > could get
> > out of control and people start adding overloaded content to the 
> > wiki
> > and in the
> > end we remove 90% of it, so everyone gets frustrated and stops 
> > adding content
> > (over-exaggerated scenario).
> 
> Which is why we should encourage users to contribute, some of which
> will inevitably become "managers" of the wiki. You can never stop
> people treading on each others toes, but as long as everyone knows 
> the
> rough rules and etiquette, things should be fine. The next thing to 
> do
> is some Wiki guidelines maybe? Something short and simple that users
> can read before their first edit.
> 
I think it would be useful for us to step back and see how the other 
open-source operating system web sites deal with their content. We 
should be able to learn something from them.

> >
> > Charlie and Mikael are Python and Trac developers. It would not 
> > make a lot of
> > sense to put them on a Rails project. We want to switch to 
> > something better
> > than Bugzilla, anyway (there's even a bug report for this). We 
> > don't lose
> > anything if they work on Trac.
> 
> Has Haiku picked Trac now? Would it be an idea to learn Python in 
> case?
> Is it going to be CMS+Trac? (does that mean RailFrog+Trac?)
> Maybe we can ask for donations to support our server hosting the SVN,
> it would at least motivate the upgrade to Trac.
>
Mirroring the repository once a day to get the Subversion changeset 
timeline working would be enough, can still have the actual repository 
at BerliOS.

-- Mikael
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Well, I'll tell you what happens: half the time, you get a
 Doubleton or a Tripleton, unless you're a synchronization
 expert, and having a Tripleton is about as desirable as
 having three Balrogs show up at your tea party."       -- Steve Yegge

-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List