I did import the user guide into github earlier this year when I was first learning git: http://github.com/pcutler/foresight-user-guide/tree/master
Though knowing what I know now, I would have used gitorious. Good to see some more Mallard adoption, though I don't have any time currently to commit to the user guide. To get a feeling for the syntax and usage, I recommend checking out Empathy in GNOME 2.28 which is the first project to have help in Mallard. Paul On Thu, Sep 3, 2009 at 1:38 PM, Martin Bähr < mba...@email.archlab.tuwien.ac.at> wrote: > On Thu, Sep 03, 2009 at 02:28:23PM -0400, Og Maciel wrote: > > I'd like to ask the opinion of you guys about moving the > > foresight-user-guide-2 source code from our Hg setup to Gitorious. My > > objective is to allow for easier consumption by collaborators and avoid > > the need of adding new ssh keys for every person we want to grant commit > > access. Also, people can easily fork and request merges from Gitorious. > > doesn't that in the long run apply to every project hosted on our hg > server? if so, maybe we need to rethink the way the whole hg server is > handled. (no ssh access but some less intrusive access method (i am sure > there is an equivalent to git-server) > > greetings, martin. > -- > cooperative communication with sTeam - caudium, pike, roxen and > unix > searching contract jobs: programming, training and administration - > anywhere > -- > pike programmer working in china > community.gotpike.org > foresight developer foresightlinux.org > open-steam.org > unix sysadmin iaeste.(tuwien.ac|or).at > caudium.org > Martin Bähr > http://www.iaeste.or.at/~mbaehr/<http://www.iaeste.or.at/%7Embaehr/> > is.schon.org > _______________________________________________ > Foresight-devel mailing list > Foresight-devel@lists.rpath.org > http://lists.rpath.org/mailman/listinfo/foresight-devel > _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
