Puma board for FreeEMS

[jharvey]

I got that script working, and ran it on Puma. Puma now has a mostly populated reference designator BOM. Also this script will be handy if we end up changing a part, we can use it to change a component in all sub schematics. Marcos will likely have these changes and the script included in his next git check in. There are still a couple of components that need to be finished up, mostly items that are qty 1 or qty 2, so they shouldn't be that hard to get done. It will a be a couple days before I can get a chance to finish them up. Just wanted to share the good news.

[nitrousnrg]

Amazing work hjarvey, I think tomorrow I'll be commiting the changes. Tonight I want to get the RPM circuits working :-)
Or get some sleep. Both things are useful.

[Fred]

Jared, why are you not committing these items yourself on a clone of his repo? These scripts are new/something Marcos wouldn't be touching. They should have your name on them. Also, if Marcos is doing it, he should be setting you as the author/committer and him as the via. I forget the terms.

[nitrousnrg]

mmm, none of us (jharvey and me) knows git a lot. Its a good time to learn, though. A couple of weeks ago we were doing lots of changes together without using git, because we didn't have the time to learn how to merge our work.

jharvey, I've no problem about adding your files, its pretty fast. If you want to use git, I'll join you. I guess the strong and amazing Freddie can give us a hand with it ;-) I've read (red) about it and its not hard if I don't make changes after my last commit you cloned.

[Fred]

I'd be weary about merging the actual pcb/schem files if you're both editing, that will likely end in a fail, but accessory files like scripts and so on, no problem. The schem/pcb stuff should be edited in a linear way as you've already been doing, BUT, you could still say "your turn, i'll not touch it till wednesday" and so on and so forth.

Fred.

[jharvey]

Jared, why are you not committing these items yourself on a clone of his repo?

Primarily ignorance. I've tried a couple times, and git just doesn't work the way I expect. When faced with spending my time learning a new tool that has a fairly steep learning curve, or focusing on actual dev... Well I'm sure that some day I'll get around to learning git, but spending more time learning git than I'm spending on the actual dev, seems a bit odd to me.

They should have your name on them.

They should have my name if I want credit, and I don't. I would prefer not being named, especially because these are such small scripts.

[Fred]

No, they should have your name whether you want credit or not, it is your work, not anyone else's. Copyright belongs to you, unless you assign it to someone else. Thus git commits are a good way to keep track of such things. It's not like its super public,its just there in a repo history, no big deal, no front page articles etc. If you want a crash course in git, i'm happy to help. I gave Preston/lev8n one tonight in person.

[jharvey]

Marcos can release it however he feels, I'm not really the picky about it. I'll try to find some time to explain my points. These points are shed color as far as I'm concerned, so don't hold back on a git commit because of me.

Fred, hows your TortiseGIT skills? I think that's a fair part of my learning curve.

[Fred]

I used tortoisesvn years ago, but only on windows and it's fairly straight forward. Git is just a matter of understanding concepts, knowing your goals and mapping commands to how to achieve them.

[jharvey]

How about the below part for the USB mini type B. Has through holes for rigidity, appears to have several vendors, gold plated contacts and not to crazy expensive.

http://octopart.com/partsearch/#search/ ... 54819-0519

That's molex 54819-0519