How Github Organizations Help Freelance Developers Collaborate
You’re an adept, professional and fortunate freelance developer. As such, you’ve got loads of work on and everyone wants a part of you. But like all things, too much of something can also be a curse.
Early in your career, when your freelance business was smaller, and had only a handful of clients, life was simpler. You didn’t need an intense workflow to manage your projects from inception to delivery. But now all of that’s changed; you’re busy and it’s taking its toll.
Perhaps you, regularly, ask yourself some of these questions:
- Where does my time go?
- How can I spend more time in development and less time in administration?
- Why do I
wastespend so much time administering projects instead of building and billing them? - How can I simplify my workflow?
- How can I do what I do, but simpler, quicker, easier?
Well, there are a number of great resources available, but I want to focus on just one. If you’re familiar with Github (or even if you’re not) then today you’re in for a treat. A while ago Github introduced a new feature called Organizations and it’s a real godsend for us freelance developers.
The basic setup is quite good. The personal features allow us to share and collaborate fairly well. But the permission structure is, well to say the least, simple.
For example, recently I wanted to give a client view access only to one of my projects. Unfortunately, given that it was under a personal profile, they could either get full access or nothing. There was no middle ground. But organizations changes all that and I’m sure you’re going to love it. Here’s why:
