I forgot to mention that the checkout (now clone) shell script has been updated.

wget http://github.com/seam/build/raw/master/checkout.sh
chmod 755 checkout.sh
./checkout.sh

That is intended primarily for developers that want to track master and build snapshots.

If you are hacking on a module, you should first clone it into your github.com account and work from there. When you are ready to commit a change to master, you send a pull request. This forking process is laid out very clearly in the github.com help pages.

http://help.github.com/forking

I haven't worked out yet how to add members to the Seam organization. I think it's because I'm not the owner, that would be Pete. So we'll get back to you on that.

-Dan

On Sat, Oct 16, 2010 at 4:41 PM, Dan Allen <dan.j.allen@gmail.com> wrote:
On Sat, Oct 16, 2010 at 4:36 PM, Jason Porter <lightguard.jp@gmail.com> wrote:
Dan is also forgetting Pro Git [1]. 

Oh, it's up there in my head somewhere, you can be sure of that :) Great resource indeed.

-Dan
 
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen



--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen