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

[Waldemar Kornewald <wkornew@xxxxxxx>]

John Drinkwater wrote:
> > 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".

Yes, that's a good idea. Thanks.

> > 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.

A few developers planned to use DocBook, but I don't know anything specific.
It's a dead project.

> 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

Good. We just need people who we can rely on to keep the website very simple
(improve new content, etc.).

> Maybe something like:
> * Keep things short and simple.
> * Only cover technology in detail if it is needed. Otherwise links are
> good! We'd love to appeal to everyone.
> * If you make a mistake, things can always be correctly.
> * Read discussion (Talk:) pages before edits, people might have
> decided not to do what you're about to.

Sounds good.

> > I once proposed something that the leadership liked. The wiki has an 
> > improved
> > version of this.
>
> And I doubt the wiki contributers can't improve upon it still.

I'm open for suggestions and improvements.

> 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.

Well, I hope that Michael and Charlie get finished more quickly than you can
learn Python. ;)
BTW, thanks a LOT! I'm very happy about your work:
http://ezri.nextraweb.com/examples/js/haiku/
and
http://ezri.nextraweb.com/examples/js/haiku/trac.html
(FYI, the latter is a "fake" demo. not a running system)
BTW, maybe we can at least integrate that one into the official Trac?

Charlie, so you're using RelationalTrac? I hope you will always keep it
up-to-date.

> People *are* trying to help, we're just not making it easy for them.

I added some information to the wiki (feel free to improve it) and posted
"HELP!" on the forum.

Bye,
Waldemar Kornewald


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