Comment 106 for bug 240067

Hi Geoff,

I read the LEP. It's good.

> As a developer of an open source software project I want a wiki so that I can provide documentation to my users and plan my features more easily.

This is true, but perhaps the LEP will be easier to reason about if
rather than just "I want a wiki" we talk about what they want to do,
not how, in the As-A section. The word "wiki" has many associations
such as being publicly writable, and we should be clear about whether
we mean that or not, or this just gets circular, and jumps to
implementation. Wikis are _not_ an ideal answer for all jobs for all
projects; we can possibly do better.

It does get into that a bit, further down: a homepage, documentation,
feature planning, announcements, etc.

I can definitely see how people would want richer formatting in
announcements. It's not obvious to me that people want to put their
announcements into Bazaar branches just to get wiki formatting in
them.

I wonder about splitting this into several parts, probably done in this order:

 * rich formatting of user text into html, probably coming from
Markdown (or maybe ReST): this would allow announcements, bugs,
project descriptions, etc to look a bit better
 * do this also for the contents of branches, especially for their
README and similar files
   - tangentially, show those files within the main lp ui
 * through-the-web-ui editing of branch files
 * wiki-type navigation within files in a branch

hth,
Martin