Hey Guys,<br><br>In response to the email thread below. These are my initial observations.<br><br>-<a href="http://doc.bazaar-vcs.org/bzr.dev/tutorial.htm">doc.bazaar-vcs.org/bzr.dev/tutorial.htm</a> 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.
<br><br>-<a href="http://bazaar-vcs.org/Olive">bazaar-vcs.org/Olive</a> needs an overhaul to correct some information and remove some old info<br><br>-<a href="http://bazaar-vcs.org/FirstUseTutorial">bazaar-vcs.org/FirstUseTutorial
</a> 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<br><br>-<a href="http://bazaar-vcs.org/BazaarBook">bazaar-vcs.org/BazaarBook
</a> this is old and quite incomplete with the reference part just copying bzr help<br><br>-<a href="http://bazaar-vcs.org/BzrPlugins">bazaar-vcs.org/BzrPlugins</a> 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
<br><br>General:<br>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.
<br><br><br>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.
<br><br><br>Let me know who can do what and how we could go and then we can start working if people are ready to help.<br><br>Regards,<br>Alaa Salman<br><br><br><div><span class="gmail_quote">On 7/4/07, <b class="gmail_sendername">
Martin Pool</b> <<a href="mailto:mbp@sourcefrog.net">mbp@sourcefrog.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 7/4/07, Alaa Salman <<a href="mailto:alaasalman@gmail.com">alaasalman@gmail.com</a>> wrote:<br>> Hey Guys,<br>><br>> This is probably a little late since i have been using bzr for about a year<br>> now. But recently i had to work on windows, and i appreciated the fact that
<br>> it is making my job easier even on windows. I know this is the work of<br>> Python, but i am talking about the general experience and not the platform<br>> issue.<br>><br>> So thanks. I realize this is probably the least used word in free software
<br>> today.<br><br>Thanks, that's really good to hear.<br><br>> I also have a suggestion about the website. I read recently about some plans<br>> for the website. Currently, in my opinion the website doesn't reflect the
<br>> product that it is trying to sell(sell in the abstract sense). That of<br>> stability, flexibility and ease of use and so on...I never actually liked<br>> the use of wikis, but this is not the issue. I suggest an overhaul of the
<br>> website now that bzr itself is doing some good work on the performance<br>> issues which should increase adoption rates.<br>><br>> The work would probably be some organization work, some re-writes of the
<br>> existing content and...oh yeah..please let us remove some of the old content<br>> that goes back to something like 0.8(i stumbled across one doc like that).<br>><br>> I previously did some review for some documentation on the website. And so i
<br>> would like to volunteer again. And this would be much better if everybody<br>> contributed.<br><br>I appreciate the suggestion and I agree that we should make it more<br>polished as Bazaar gets more polished. If you'd like to help we would
<br>appreciate it. There are several things you could do:<br><br> - If there are things that you're sure are out of date, just go ahead<br>and remove them. If you're not sure, you can ask here on the list, or<br>
in #bzr on freenode.<br> - You can also suggest things that other people should do, whether<br>that is reorganizing material, changing the layout, rewriting things -<br>it is remarkable what people will do if you point out what needs to be
<br>done.<br> - If you think we need a better plan for how things are laid out we<br>can discuss that too.<br><br>We've talked previously about having a clearer separation between the<br>formal web site and a developer and support-oriented wiki. I think
<br>it's probably about content rather than tools at this point but if<br>using a different tool would help I'm open to it.<br><br>--<br>Martin<br></blockquote></div><br>