Dr. Hipp,
On 17 February 2015 at 15:43, Richard Hipp <d...@sqlite.org> wrote:
> I have switched the default Fossil repo over to using the San
> Francisco Modern skin.  Everybody seems to think it looks a lot
> better, and I agree.
>

I like the switch!

I noticed there is no download in the menu bar and the download link
on the main page directs to the legacy skin:
http://www.fossil-scm.org/download.html

I don't know if either/both of these are intentional, just reporting
what's different.

> I think the next step of the ongoing Fossil makeover should be to
> improve the homepage:
> https://www.fossil-scm.org/fossil/doc/trunk/www/index.wiki
>
> Suggestions and especially mockups of how this front page should look
> are welcomed.
>
>

Regarding the main page, perhaps consideration on re-organization of
the numbered list. I think the fact that Fossil is self contained is
highly appealing BECAUSE it auto-syncs, inbuilt web interface, DB
backed, etc. I do like the list numbered and the features bold--easy
to follow the flow.

I like Michai's response on merging some items and moving many of the
link under 'Links For Fossil Developer' elsewhere but I also like 'A
Technical Overview Of Fossil.' displayed (by the way, drop that
period, ;) and here too 'Thoughts On The Design Of Fossil.')

It looks like this page can be updated (referred from /index.wiki):
http://www.fossil-scm.org/fossil/doc/trunk/www/hints.wiki

Unfortunately, I don't know either VCS well enough to know if we can
update this page:
http://www.fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wiki

But the news/blog can be updated to tech-notes now.

It seems 'Quick Start' and 'Up and running in 5 minutes as a single
user' could be merged.

IME, license pages are /LICENSE or /license. Here, it's:
/COPYRIGHT-BSD2.txt


Suggested correction:
https://www.fossil-scm.org/fossil/doc/trunk/www/faq.wiki

> How do I create a private branch that won't get pushed back to the main 
> repository.

How do I create a private branch that won't get pushed back to the
main repository?

Maybe could have a FAQ on drive-by patching, too!

Is there a 'why did you create fossil' page? If not, you could list
out the seven items from /index.wiki and explain that as well as CVS
wasn't suiting your needs, etc.

FAQ is on /index.wiki twice.

Maybe on the FAQ (or homepage) information on how to create new users
and discuss roles. For git, I don't know how access to repos is
accomplished. I think people have to exchange ssh keys or something.
Maybe that can be a bullet point on /fossil-v-git.wiki Creating
accounts in SVN is not easy and with fossil, its like making an email
account.

If people are looking for a VCS, they'll either be using one already
or looking for a new one. I think making the switch would be very easy
if the page for SVN > fossil, git > fossil, CVS> fossil were easy to
find.
So maybe something like that can be on the index.wiki page.


Put /sitemap and timeline.rss on the /index.wiki since it's absent.



 I'll probably suggest more later!

>
> Thank you all for your attention and your contributions.
>

Thank you for creating Fossil!

>
> --
> D. Richard Hipp
> d...@sqlite.org

-- 
-------
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to