Can we have some decent documentation?

Asked by Redge

I like loggerhead: very slick. Only problem is I can't find decent documentation on it anywhere. As a result, I'm not really clear on some of the concepts of the program, or how it works. I'm not really sure of what is possible with it and what is not. I don't know how to properly configure it, or personalize the interface.

Is there a Loggerhead manual? If not, I'd advice you to create one: it will definitely save you time in the feature from having to answer questions (like this one).

Many thanks for your hard work.

Redge

Question information

Language:
English Edit question
Status:
Expired
For:
loggerhead Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Redge (redgetrek) said :
#1

Excuse the double posting: launchpad's interface is a bit confusing.

Revision history for this message
Russel Winder (russel) said :
#2

I'm afraid I'll have to second this point -- that Loggerhead is not well documented.

Using Google doesn't help as there isn't much out there, and what there is is old.

Revision history for this message
Sergey Ponomarev (stokito) said :
#3
Revision history for this message
Redge (redgetrek) said :
#4

> http://wiki.flexion.org/LoggerheadServer.html

Already outdated. We need a more permanent sollution.

Revision history for this message
Russel Winder (russel) said :
#5

Looks like Loggerhead, despite being a potentially great product, is in the "the documentation is the source code, so read it" category :-(

Revision history for this message
Launchpad Janitor (janitor) said :
#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Russel Winder (russel) said :
#7

And it seems no-one is interested in answering questions about Loggerhead either :-(

Revision history for this message
Robert Collins (lifeless) said :
#8

What do you mean? There was a discussion here. 'Questions' are not a good way to get changes to a product made - thats what bugs generally lead into. I think it would be great to have more docs - are you interested in writing them perhaps? Either way, this is really something to have as a bug, not a question.

The key thing here is that developers generally don't look at the questions area when planning/doing some work, and so things that need developer (vs peer users) input are best registered as bugs or on the mailing list.

Revision history for this message
Russel Winder (russel) said :
#9

There does seem to be something of a disconnect between what Launchpad documentation puts forward as "the right thing to do" and what teams actually do and find best as a process. For most projects, Questions appear to be a waste of time.

There doesn't seem to be a way to transform a Question to a Bug Report, unless "Create Bug report" does that, though I suspect ti will start a new one. I'll try it anyway.