Website Review (Was: thanks and suggestion)

[Alaa Salman]

Hey Guys,

In response to the email thread below. These are my initial observations.

-doc.bazaar-vcs.org/bzr.dev/tutorial.htm has a TODO section that needs to be
written, and perhaps we can add some features that were added after this was
written. I can only think of tagging but i am sure there are others.

-bazaar-vcs.org/Olive needs an overhaul to correct some information and
remove some old info

-bazaar-vcs.org/FirstUseTutorial   this also needs a review, but i also
think we can remove this node alltogether since this same info exists in the
tutorial in a better format

-bazaar-vcs.org/BazaarBook  this is old and quite incomplete with the
reference part just copying bzr help

-bazaar-vcs.org/BzrPlugins  this page is too long i think and also needs a
review if some plugins are dead or are no longer needed and so on

General:
In general, i think that the layout can be modified somewhat. Perhaps like
Martin said, a formal website that advertises bzr and a pointer to the wiki
which would include information and whatnot. The information on the wiki
needs to be reviewed so that we don't repeat the same info in several
places. I also suggest using the tutorial.htm(first point) as the official
"book" and reviewing that after each release to ensure accuracy. This way
the users know exactly where to go when first learning. I also believe we
also need to review the different workflows(which i worked on before) and
better display them since they ease the transition if any.


This is after an initial overview, so i am sure there is more so please
everybody chip in. There are also some documents that i could only reach
through the search engine(which needs some work i think) but i am not sure
if this is just me not finding the links.


Let me know who can do what and how we could go and then we can start
working if people are ready to help.

Regards,
Alaa Salman


On 7/4/07, Martin Pool <mbp at sourcefrog.net> wrote:
>
> On 7/4/07, Alaa Salman <alaasalman at gmail.com> wrote:
> > Hey Guys,
> >
> > This is probably a little late since i have been using bzr for about a
> year
> > now. But recently i had to work on windows, and i appreciated the fact
> that
> > it is making my job easier even on windows. I know this is the work of
> > Python, but i am talking about the general experience and not the
> platform
> > issue.
> >
> > So thanks. I realize this is probably the least used word in free
> software
> > today.
>
> Thanks, that's really good to hear.
>
> > I also have a suggestion about the website. I read recently about some
> plans
> > for the website. Currently, in my opinion the website doesn't reflect
> the
> > product that it is trying to sell(sell in the abstract sense). That of
> > stability, flexibility and ease of use and so on...I never actually
> liked
> > the use of wikis, but this is not the issue. I suggest an overhaul of
> the
> > website now that bzr itself is doing some good work on the performance
> > issues which should increase adoption rates.
> >
> > The work would probably be some organization work, some re-writes of the
> > existing content and...oh yeah..please let us remove some of the old
> content
> > that goes back to something like 0.8(i stumbled across one doc like
> that).
> >
> > I previously did some review for some documentation on the website. And
> so i
> > would like to volunteer again. And this would be much better if
> everybody
> > contributed.
>
> I appreciate the suggestion and I agree that we should make it more
> polished as Bazaar gets more polished.  If you'd like to help we would
> appreciate it.  There are several things you could do:
>
> - If there are things that you're sure are out of date, just go ahead
> and remove them.  If you're not sure, you can ask here on the list, or
> in #bzr on freenode.
> - You can also suggest things that other people should do, whether
> that is reorganizing material, changing the layout, rewriting things -
> it is remarkable what people will do if you point out what needs to be
> done.
> - If you think we need a better plan for how things are laid out we
> can discuss that too.
>
> We've talked previously about having a clearer separation between the
> formal web site and a developer and support-oriented wiki.  I think
> it's probably about content rather than tools at this point but if
> using a different tool would help I'm open to it.
>
> --
> Martin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20070704/39398eb1/attachment.htm