Development Groups formation
Moderator: Transport Empire Moderators
- uzurpator
- Transport Empire Moderator
- Posts: 2178
- Joined: 10 Jan 2003 12:21
- Location: Katowice, Poland
Well - the main group would be design - and all members would belong to it...
The best choice would be:
Code and technical (coders)
Multimedia (artists)
Publicity (websites)
The best choice would be:
Code and technical (coders)
Multimedia (artists)
Publicity (websites)
All art and vehicle stats I authored for TT and derivatives are as of now PUBLIC DOMAIN! Use as you see fit
Just say NO to the TT fan-art sprite licensing madness. Public domain your art as well.
Just say NO to the TT fan-art sprite licensing madness. Public domain your art as well.
I miss something important in your list, uzurpator. You translated Steve's 'Everything else FOR the game' as publicity but I think there's more to do FOR the game than just advertising it. Who's gonna manage this project i.e.? Each dev. group should do his own group management IMO but there needs to be something above that too. It's always good to have a '3rd party' keeping an eye on progress and chasing you out of your lazy chair when needed.
Code Group (CG
Technical Group (TG) or Content Groupp (CtG) or ...
Management Group (MG)
#1 and #3 isn't much of a problem, but #2 is more difficult. Becuse it is a wide group with things from art to i18n to coding standards to usability. So probably we have to use a wide name as technical group, Content group is probably to narrow, as a coding standord is not content.
Hyronymus: remember that multimedia is a sort of content.
Technical Group (TG) or Content Groupp (CtG) or ...
Management Group (MG)
#1 and #3 isn't much of a problem, but #2 is more difficult. Becuse it is a wide group with things from art to i18n to coding standards to usability. So probably we have to use a wide name as technical group, Content group is probably to narrow, as a coding standord is not content.
Hyronymus: remember that multimedia is a sort of content.
My OpenTTD contributions (AIs, Game Scripts, patches, OpenTTD Auto Updater, and some sprites)
Junctioneer (a traffic intersection simulator)
Junctioneer (a traffic intersection simulator)
The reason is to separate coders from the standard. There are two points to this:Steve wrote:Why don't the coding standards go in the coding group?
It seems a bit weird for one group to tell the other group how to do their job like that. Unless i don't understand what coding standards consist of.
1. If you have the same people writing the standard and then applying it, you run the risk of attachment and short-sightedness. If only some coders are working on it, then the other coders may be more effective in spotting the problems as they go, and policy writers not involved in the coding may see something emerging in the code that the coders don't see.
2. If a newcomer finds something is missing in the standard, they will do one of two things. Either they raise an issue - "Hey, what's your policy on xxx?" - or they adopt their own standard for it. If everyone adds their own little bits to the standard, you get a situation such as IRC II (some 300 standards were cobbled together, most implementations are non-compliant in some way).
Of course, people on the code standard working group need to have some knowledge of software engineering, and there's nothing to stop a small number of people from various coding sub-groups working on the code standard working group.
In the end, coding standards are a policy, and it would probably be a good idea to keep all policy work together. Remember that the big three are work areas rather than solid groups. If you have a "technical group", this implies (=>) that there are people in that group => technical work is done only by technical people => some technical people might not have work. With a "technical work area", => that there is some work of a given kind around. My initiial idea with the structure was to separate work rather than people. In an office environment, you have a given set of resources to use. You may often find that you have to find work to give to people. Since what we're doing is voluntary, we need to find people to set to work.
I can't make that point strongly enough. Of course, I could be being short-sighted and too attached to the original idea, but then other people could at the same time be too attached to traditional methods of thinking - remember that we're not a traditional software project.
Probably in a similar way, if they've any sense
My experience working with people in and around GNOME threw up a large number of small, focused teams (one per app, backporting teams, several to look after bugzilla, policy teams, multiple release teams, the beta teams from the major distributors, etc.), though certainly that's on a very much larger scale than what we'll be doing. Having a large, unfocused group doesn't really make a lot of sense, and remember that large unfocused groups is not what I'm proposing - a few people seem to have misunderstood this.
My experience working with people in and around GNOME threw up a large number of small, focused teams (one per app, backporting teams, several to look after bugzilla, policy teams, multiple release teams, the beta teams from the major distributors, etc.), though certainly that's on a very much larger scale than what we'll be doing. Having a large, unfocused group doesn't really make a lot of sense, and remember that large unfocused groups is not what I'm proposing - a few people seem to have misunderstood this.
But why can't we have four main groups?
- Coding
- Content creation
- Technical management
- Non-technical management
As I understand it, Chris is making the point that several small and better focused groups is better than a few less focused groups, so if we have trouble making a simple definition for one group, it's probably because it's already too wide, and should rather be split into two or more groups.
Also, people should remember that any group can always decide to internally have several sub-groups.
- Coding
- Content creation
- Technical management
- Non-technical management
As I understand it, Chris is making the point that several small and better focused groups is better than a few less focused groups, so if we have trouble making a simple definition for one group, it's probably because it's already too wide, and should rather be split into two or more groups.
Also, people should remember that any group can always decide to internally have several sub-groups.
Who is online
Users browsing this forum: No registered users and 4 guests