About the administration

Boriss Mejias boris.mejias at uclouvain.be
Wed Oct 18 14:56:36 CEST 2006


Dear all,

since there are no rejection to these proposal, Raph is also assuming 
the role of Admin in the project, and actually he will be the main 
contact in the following weeks because I will be away.

We will also grant "Junior Developer" role to Filip Konvicka and the 
developers of the GeOz project.

that's it for now.
cheers
Boriss

Boriss Mejias wrote:
> Dear hackers,
> 
> Next week we will be able to start using the new development 
> infrastructure. We will only have the SVN repository at first, but 
> that's already enough to discuss some important issues and I need your 
> opinion.
> 
> REPOSITORY:
> Every developer should create an account ASAP, and request to join the 
> project. I will grant the "senior developer" role to anybody who already 
> has a CVS account in Saarbrucken.
> 
> ADMINISTRATOR(S):
> At the moment, I'm the only administrator but I will need somebody 
> helping with this task. Any volunteer or suggestion?
> 
> MAILING-LISTS:
> Once the mailing list are migrated (this will be a bit delay as you read 
> in a previous email), we will need to grant admin/moderator access to 
> those who will be responsible. I think it is reasonable that the people 
> who is moderating now carry on with the task. The point is that I don't 
> know precisely who is involved. I just know Raph is taking care of some 
> of the mailing list, and probably Kevin and Denys are also related.
> 
> BUG-TRACKER:
> Here we will need the help of the community to migrate the data from the 
> current bug-tracker to the new one. Paul Dufresne already volunteer to 
> help, so I gave him "tech-support" role in the Mozart-Test1 project. I 
> would like to know what is going to be the policy to accept volunteers 
> in the real project.
> 
> NEW-DEVELOPERS:
> What is going to be the policy for granting write access to the SVN 
> repository to new developers? Do we have to submit a MEP every time 
> somebody wants to become developer? Or is it enough having a discussion 
> in the hackers-mailing list? For instance, I would like to give write 
> access to Filip Konvicka, because he has shown interest and he has 
> already contributed to the release of Mozart-1.3.2. It would be also 
> positive to grant write access to the guys working in Colombia in the 
> integration with Gecode (The GeOz project). What should be the process 
> to give the developer role to this people?
> 
> that's it for now
> cheers
> Boriss
> 
> _________________________________________________________________________________ 
> 
> mozart-hackers mailing list                           
> mozart-hackers at mozart-oz.org      
> http://www.mozart-oz.org/mailman/listinfo/mozart-hackers
> 




More information about the mozart-hackers mailing list