[Ssc-dev] hello and I'm in

[Nathan of Guardian]

Hey, Brian. I have cc'd our "SecureSmartCam" dev list where most the
discussion takes place on this project.

Everyone: Brian and I spoke at the NYTM after party thing, and he has
followed through with his interest in ObscuraCam, and begun getting his
hands dirty. He is new to Android and open-source, but I won't hold that
against him :P and generally it seems like he has a very solid technical
background.

On 01/25/2012 04:10 PM, Brian Christensen wrote:
> I'm now focusing on getting up to speed with Git and GitHub. I believe
> the next step would be for me to clone the repository and start getting
> familiar with how the application is built and what areas would need to
> be worked on.

Yes. Being able to compile, debug, etc. is definitely the next step.

> I'm wondering, do you think it would make sense for me to look into
> issue #87 or #88 or is there somewhere else I should look? Wasn't sure

If you have some ideas about those issues, you should probably comment
on what you might think the solution is, and how you are going to try to
fix it. Having the comment discussion in public, around the ticket on
github, is a key part of how open-source dev should be done. There are
no secrets :)

> if someone else is already working on those or if they already have
> known causes or if they might be too advance for a first contribution.

I can take a look and see what I think, but as I said, as a volunteer,
you are welcome to take on any work you think might be interesting,
whether it takes a week or a month.

> Also, I think I may have come up with a few issues that I didn't see
> documented, ranging from bugs to features to design ideas. This is my

Please file these as new issues on Github, and then I can triage through
them to assign priority tags, and milestone settings.

> that kind of input. Send it to you first? Just start adding issues to
> the project? Do I need any special permissions or is there an approval
> process?

Generally, issue reporting is wide open. What you should do is use the
Github "fork" command, to create your own github repo, upon which you
will be working. Once you have a bug fix or feature to commit, you can
create a "Pull Request" to the main project, which then I can review and
decide to merge into the master branch.

More on that process here:
http://help.github.com/fork-a-repo/
http://help.github.com/send-pull-requests/

> Thanks! Looking forward to contributing.

Thanks for following through, and excited about having a new volunteer.
We can figure out some time for you to come by SATELLITE (our little
hackspace) in person.

+n