iToto's Blog

A Montreal based full-stack web developer who loves learning and trying out new things. This blog is my attempt to document my work as well as a place to discuss ideas or topics that I find interesting. Feel free to follow me on linked social networks.

Filtering by Tag: api

Ready For Collaboration

Finally got around to setting up all the repositories on Github for Party Stream. There are several parts to the system and I'm really happy to say I have already received volunteers to work on some of them.

Here is a list of projects that are open for collaboration:

  • Web App
  • iOS App
  • Phonegap App
If you are interested in contributing to either of these projects, please send me an email with your Name, Github account name, Dropbox associated email and which project you want to work on. You will be invited to a shared Dropbox folder that will be used for the diagrams and artwork.

Guidelines

If you are working on any of these projects, there are some guidelines that I would like to follow:

Fork

First thing's first, please work off your forked copy of the repository. Do no work directly on the repository on my account. If you are new to Github, here is a introduction to Forking.

Git Flow

If you haven't been using a good workflow with git, may I introduce: Git flow, the only workflow you'll ever need to know about! I use this religiously as it helps keep source control simple and easy - especially for collaborations. I will be using this on each of the projects and I suggest you use it on your forks as well. It will keep it simple when it comes time to create your pull requests. If you use Source Tree it actually incorporates git flow – which is really helpful. They have both windows and mac versions.

Pull Requests

When you're done working on a feature and are ready to bring it to the main repository, please make your pull requests to the Develop branch. Nothing should ever be merged into the master branch as it is reserver for stable releases (see git flow).

That's it for now, I will add more as the project progresses. Thanks ahead of time for all those interested in the collaborations.

Happy Hacking :)

Update

Once you're setup and ready to start contributing, we need to let everyone else know what you're working on. For this, we will use GitHub Issues.

If you see an issue that you'd like to work on, assign it to yourself. Otherwise, simply create an issue specifying what you are implementing and assign it to yourself.

Quick update

Hey all. Just wanted to post a quick update on my progress.

After my last post, Amazon had announced that it has now supported Node.js with AWS. I was relieved to see that as I wasn't too thrilled about using a a library that may or may not be maintained in the short term. 

The GitHub project for the SDK is pretty good. I've been able to painlessly upload test files to my S3 storage from my application and have already begun creating my module. To all those that were looking to integrate AWS with their Node.js application, it's now a npm command away.

Aside from API development, I have decided to begin working on a front-end website that will give a preview of the app so that I can start announcing it to the world and see if there is any demand for it. As of now I'm going to be using Twitter's Bootstrap along with LaunchRock for the initial sign-ups for people who want to get into the beta when it is available in 2013. I will post the link to the website once it's ready, so keep an eye out.