New Viscans Group Structure


Use of this text
This explains an idea on how Viscans will be organized in the future, hopefully providing  transparancy of the administration, and an adequate release-rate, resulting in members to be more content with our work.

Thesis:
Viscans has a great diversity of members (and their preferences regarding what they read etc.) and projects

To not loose this, while being a rather big group, we can't put all organisational work on just one person. We tried out a system having project managers and translators set on their projects, while everyone else jumped between the projects. This resulted in project managers 'stealing' members, people paused working on one thing to do another.
To stop this, every project should have all positions set, a new project will just be picked, if the person who wants to do so gets a cleaner, a translator, a qcer etc. to work on it. The one who suggested the project will be the project manager.
Since typesetters and proofers need people to have already translated/cleaned and proofed the chapter, they can just do more projects.

	'One of our old projects has noone willing to e.g. clean it, what to do?'

Given that situation, the people working on it will ask around, should they not find anyone, the project will be dropped.

To prevent our projects being stalled thanks to one person working on it vanishing, everyone will be required to join the staff channel at least once every two weeks, shouldn't they have noted down, that they're going on vacation e.g. Anyone who doesn't follow that rule will loose his position working on a certain project, be set on MIA status at the website and, after another 2 weeks, be deoped.

People who have lost their work will search for a new project to work on, or just jump around if there isn't any.


The competences and responsibilities of a project manager

Project managers will not be required to work on the project. They aren't neccessarily qcers. The main quest for a project manager is to keep track of his/her series and make the set people work on it. This will require them to be on irc quite much. We are an IRC-based group, so keep it irc!


How managers do release

We'll set up a folder at the FTP called 'ready to release'. Once per day, or when one got a release ready himself, an admin will check the folder and release everything.


How to handle newbies

Newbies will be required to jump around for 5 chaps. The deadline for those chaps is 1 week for anyone besides proofers, for them it will be 3 days. For that there will be 2 projects with little to no priority, one with furigana, one without them.


How announcements are made

We'll set up site staffers are supposed to check at least twice per week. On this we'll add all important news, project related or not.


Other:
tling and proofing standarts will be added.

1. All scripts should have a clear format like

panel1
	bubble1 – tralala
	bubble2 -tralalalala
panel2

and so on.
The rest: will come later