Benjamin, you're describing a corporate organisation!!!
We're a small team here.. if we have only those 3 admins you say, then
they'll be noone to code.. also, if an admin says "hey, do this", and the
guy can't because he has no time, then what ? you'll fire him ? it's only
for fun and a hobby on free time... problem is where to find that free
time...
your idea is good, if we were 100 people, all paid and we all have to work
a certain amount of time per day.. but for amsn.. it won't work at all.
KKRT
On Tue, 09 May 2006 15:40:48 -0400, Benjamin <[EMAIL PROTECTED]> wrote:
I think you should have better team organization.
For example, you have X main aspects in aMSN :
[ Main ] [ ... ]
[ GUI ] [ Protocol ] [ Core ] [ ... ]
You could have an admin per section. That admin will give jobs to coders
and
will take decision on what have to be done for next release or he will
chose
how to do something in the GUI or core. Like Youness said that Alvaro
said,
after if people complaints, then you could start a thread with much more
people than GUI team.
Protocol programmers could give idea to GUI team, but they don't have to
touch the GUI team's code. If they need something to be added in the GUI,
they will ask to Protocol team's Admin « I need those options added
somewhere for that new feature » then the Admin will ask to Admin GUI's
team
That's my 2 cents !
Sorry for bad English.
--
KaKaRoTo
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Amsn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amsn-devel
