Technical-NGO

This organization is under development but that doesn't mean you can't know who we are...

Who are we?

We are bunch of people who happened to share a common dream of developing for the Web.

How did this diverse cast come to be? Well, all credits for that goes to the Google Reskilling India Scholarship provided by Udacity which brought us all under one big umbrella (or tree, if you prefer coding terms)

Our aim?

Plain and simple - get proficient in web development. No mysteries there.

But why a organization though? Well, as Gobber from How To Train Your Dragon says, we believe in "Learning on the job".

Confused? Basically, what we aim to do is learn web development by designing and developing websites for NGOs and other non-profits.

This benefits both as:

1. they get an awesome website (for free)
2. we get practice (lots of it)

So, win-win for both...

How de we ensure quality while still learning?

Not all of us are in learning phase, we among us also have people from the industry who have been doing this for a while. They ensure that we learn best practices, and the end result reflects quality and perfection.

Can I contribute ?

Update: Read our extensive contribution guideline

Well of course you can, we will make sure that each issue will have label showing the difficulty level of that issue. It can be Easy, Medium, Hard. Easy labeled issues can be taken up by those who are new to Github and want to contribute something. We highly recommend contributors to leave easy issues for others, only if you think you can take Medium or higher level issues.

Also make sure that if you are working on any issue then make one comment saying that you want to work on it so that others may know that this issue is already assigned to someone and he/she is already working on it. Try not to break these rules as it will maintain healthy behaviour among us.

Best practices for contributition

Anyone can contribute to our open source project so feel free to do it. But make sure that you follow best practices which we have:

1. Make sure that git commit message is meaningful and easy to understand
2. While solving any issue make sure you reference it in commit message by mentioned issue id (#1, #2 etc)
3. Make sure you squash your commit if there are more than 2 commits while making any Pull Request. In case of difficulties feel free to ask for any assistance.
4. While making any Pull Request for UI make sure you attach one screenshot showing the final result or the bug which you have solved.
5. While creating any issue make sure you mention all the procedure required to generate that bug/error and have one brief description about that bug.

New to Github ?

If you are new to this community and don't know how this works then you can go throught this link