Tweet
After a long discussion with Senethro past Saturday (which was interrupted by badly timed cIV delivery 
), we have news.
Senethro has asked me earlier to help him as project leader. He can’t be available at all times so this is a reasonable step. None of us can be available at all times due to our academic pursuits, but it is likely that one of us will always be around.
We do not intend to make design decisions – it is up to group to decide. Our function will be to organise and coordinate the effort for greater efficiency.
It is up to C4:AC members to decide if they wish to comply with this leadership – there are two poll option with which you can express your opinion. Please do not vote if you are not a C4:AC member.
As proposed long ago by BinTravkin, the C4:AC needs to get efficient. And the best way to do this is by dividing ourselves to taskgroups. More taskgroups and subtaskgroups may be added in future, but for now this is the list of taskgroups:
[C4:AC][SOUNDS]
[C4:AC][GRAPHICS]
[C4:AC][COMMUNICATION]
[C4:AC][WIKI]
[C4:AC][FEEDBACK]
[C4:AC][PROGRAMMING]
Tasks shall be given to each group. There may be additional tasks that will be awarded to several groups or the team membership as a whole.
A task given to a sounds group shall be marked as [C4:AC][SOUNDS][taskname]
A task given to two groups shall be marked as [C4:AC][COMMUNICATION][PROGRAMMING]. Both groups should coordinate and handle it.
A task given to all members shall bear no additional name markers.
Every member is encouraged to apply to taskgroups they can help with. The next step is choosing the taskgroup manager who will coordinate his taskgroup. His responsibility would be maintaining the taskgroup thread in which would be listed all pending and completed tasks for his group.
Project leadership will have regular meetings (every two weeks). Every taskgroup should send it’s coordinator or replacement delegate. Other members are also welcome, as well as nonmembers. In these regular meetings there would be reports on progress of various tasks and discussion about the future course of the project. Chat logs will be available for download to all those who couldn’t attend meetings.
The meetings will be held at #c4ac at Apolyton Civilization Site. For information how to use it, see this: http://apolyton.net/misc/chat/ Note that java chatroom is operational again.
For now, I suggest scheduling first such meeting for three weeks. Details shall follow.
), we have news.Subject A: Leadership.
Senethro has asked me earlier to help him as project leader. He can’t be available at all times so this is a reasonable step. None of us can be available at all times due to our academic pursuits, but it is likely that one of us will always be around.
We do not intend to make design decisions – it is up to group to decide. Our function will be to organise and coordinate the effort for greater efficiency.
It is up to C4:AC members to decide if they wish to comply with this leadership – there are two poll option with which you can express your opinion. Please do not vote if you are not a C4:AC member.
Subject B: Creation of taskgroups
As proposed long ago by BinTravkin, the C4:AC needs to get efficient. And the best way to do this is by dividing ourselves to taskgroups. More taskgroups and subtaskgroups may be added in future, but for now this is the list of taskgroups:
[C4:AC][SOUNDS]
[C4:AC][GRAPHICS]
[C4:AC][COMMUNICATION]
[C4:AC][WIKI]
[C4:AC][FEEDBACK]
[C4:AC][PROGRAMMING]
Tasks shall be given to each group. There may be additional tasks that will be awarded to several groups or the team membership as a whole.
A task given to a sounds group shall be marked as [C4:AC][SOUNDS][taskname]
A task given to two groups shall be marked as [C4:AC][COMMUNICATION][PROGRAMMING]. Both groups should coordinate and handle it.
A task given to all members shall bear no additional name markers.
Every member is encouraged to apply to taskgroups they can help with. The next step is choosing the taskgroup manager who will coordinate his taskgroup. His responsibility would be maintaining the taskgroup thread in which would be listed all pending and completed tasks for his group.
Subject C: Coordination
Project leadership will have regular meetings (every two weeks). Every taskgroup should send it’s coordinator or replacement delegate. Other members are also welcome, as well as nonmembers. In these regular meetings there would be reports on progress of various tasks and discussion about the future course of the project. Chat logs will be available for download to all those who couldn’t attend meetings.
The meetings will be held at #c4ac at Apolyton Civilization Site. For information how to use it, see this: http://apolyton.net/misc/chat/ Note that java chatroom is operational again.
For now, I suggest scheduling first such meeting for three weeks. Details shall follow.
Comment