[Arm-netbook] KiCAD based A10 break out / prototyping PCB finished

luke.leighton luke.leighton at gmail.com
Wed Feb 6 23:36:25 GMT 2013

On Wed, Feb 6, 2013 at 11:00 PM, jm <joem at martindale-electric.co.uk> wrote:
> On Wed, 2013-02-06 at 17:43 +0000, luke.leighton wrote:
>> jm can you please submit a patch against git.hands.com/eoma.git so
>> that the files can be maintained where they should be: in a git
>> repository, not random tarball drops.  if you prefer not to do this
>> please can i ask you to set up your own git repository and manage it.
>> tarballs are absolutely fine for end-users but make software
>> development and contributions absolute hell on earth.  if that's what
>> you want to happen then obviously i will not stand in your way, but
>> from experience i know that you will get very few contributors if you
>> do not follow standard free software practices.
>> l.
> Apologies - will try later this weekend.

 nonono, there's no need to apologise: if you even should be
apologising, it should be to yourself :)

 what i'm saying is that, from experience, if you drop tarballs at
people then you can only expect *users* to pick them up.  if however
you wish to engage other experienced free software developers who work
to specific working practices which aid, assist and empower them to
work efficiently and conveniently with others, then you should learn -
fast - and follow those exact same practices.

 in fact, you should be working with git *all the time*.  you should
NOT be going "oh, let's make another tarball to make a backup of this
work".  every time you hit "save" you should *automatically* be going
"it's time to do a git commit".

 so you shouldn't be saying "i'll try this weekend" - you should be
doing a 30-second command named "git push", which will do all the hard
work for you.

 in fact, by the time you get to the end of this message, you will
have taken more time than it *would* have taken you to do that "git
push" and make all the hard work you've done available to everyone...
including revision history and critical development comments.

does that help at all?  is it clear that there are real benefits to
working to industry-standard software development practices [which
happen to also be beneficial to team development]?


More information about the arm-netbook mailing list