I wonder which collaboration model is best for us: the "Fork & Pull" or "Shared Repository Model". Is it decided on a per-repository basis? I guess you SteveD and Coby should be able to nut that one out. Either way, I thought the collaboration that Coby showed me today on real projects looked really good.
I can see that there is a learning curve, but it does not look much, even to someone that is as rusty as me. To practising coders it is probably trivial. I can certainly see the huge benefit from using it.
On Wed, Jun 20, 2012 at 10:54 PM, David B <[address removed]>
I'm starting to push some techspace related code up to Github.
Here's the first one; the PHP code that controls our door opener
Coming up next will be:
- the Arduino door opener code
- the Arduino RFID reader code
- the Android application door opener code
These need a bit more cleaning before sharing :)
Hopefully others will use this to see how the systems work and suggest improvements by "forking" the code and then issuing pull requests.
We could also use github to keep our reprap Slic3r configuration files or any custom reprap object files (eg: 3D techspace logo).
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by David B ([address removed]) from Gold Coast Techspace.
To learn more about David B, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]