Cleaning house

[nidzieko]

We need to add comments and/or a directory structure to mark whether something is:

1. a duplicate of a process from someone else's repo
2. a modification of someone else's code
3. working or in development

[sgillen]

I agree with giving credit where credit is due, we could consider having a separate directory for third party apps, but that will complicate the build process. I think it's probably enough to give credit in the comment header, the readme, and the description on GitHub.
I believe you can make a repo private for free if we host it on one of our individual accounts. I think a good idea is to have a clean public branch on the hpl page, and have a private testing branch on one of our own pages. When we finish polishing a feature we can push it to the public repo. Not quite sure how to do this, but one of the features git seems to advertise is that it makes this easy. So I'll look into setting something like that up.

-Sean Gillen

On Jan 9, 2015, at 1:04 PM, Nick Nidzieko [email protected] wrote:

Since this is a public repo (and I'm too cheap to pay for the private version at $25/month...) we should consider a couple of things. 1) Make clear which things have come from from someone else's repo (like iGPSd or the YellowSub stuff). 2) Remove or mark stuff that was just trial-and-error, like xRelay_test.

I guess what I'm thinking is that we want to try and put forward as polished a look as possible. (Maybe I should find a way to pony up a few hundred bucks to keep things private until we get the details ironed out?) I just want to avoid pimping other people's work without giving credit and also want to make it easy for others to use our stuff.

—
Reply to this email directly or view it on GitHub.