Sign in to follow this  

Regular Team Projects

Recommended Posts

DareDeveloper    1018

There are quite a few of those threads where people want to learn in a group and start simple projects.

Probably some (most? all?) of them belong in the classifieds.



I wonder if it would make sense to have a regular, self organizing study group feature, maybe as a simple forum.

For example:

  • New projects start at the 1st of each month
  • If 3 or more people agree to work together they can start a team (there are many people with different interests, but if enough people are interested there should be enough overlap)
  • Teams can start 1 month, 3 month or 1 year projects (not sure if 1 month makes a lot of sense, though)

Learning in a group just makes sense. There could be rules as guidance ...

... the efforts would be documented and experienced people could write helpful advice and point the group members in the right direction.



It would not even have to be for absolute beginners only. It could be combined with a gamedev workshop effort.

People could write what they would like to see developed (libraries, tools or games), the teams could work on one of those things.

The code could be hosted on Github.

Maybe game design study groups could come up with game concepts and programming groups could try to realize the best one.



Finding tutors and getting feedback is underrated and could maybe be encouraged that way.

Share this post

Link to post
Share on other sites
Orymus3    18821

I think the flaw with this is you'd end up with too many chieves.

The current problem I feel with hobbyist development is that everyone has a vision, but very few are interested in jumping on someone else's ideas. 

Most of the people with the necessary maturity tend to work for hire by now, and very few can muster the time to jump on said team.


A few years back, I jumped in the "reasonable game project" that drafted heavily from this community (I believe SunandShadow was on the same team as I). The the project was defunct before the first line of code was ever written, the process through which the project scope was determined was a potential solution to organizing what you are suggesting. However it underlined something critical: you still need just one person in charge of the vision.


In other words, if you want to have a hobbyist team assemble at regular intervals, you need to have key recurring people that will have specific roles, one of which should be the vision holder. He doesn't need to be a tyrant, but he needs to be able to make the calls and avoid anarchy.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this