Hi everyone, Let me present my opinion as well :-)
The Release Manager position was introduced by Elpidio almost one year ago. After evaluating the possibilities he decided to promote me. I was new to Care2x and could not tell if this is for good or bad that time. I accepted because this was an opportunity for me to get more deeply into the project and get some real experience on working in open source project. There is no better teacher than working on real problem. Turning back now I would say that all this was for good. I introduced some new things in Care2x and helped others to do the same. It was clear from the very beginning that I can be on this position no more than one year. So, I will not feel insulted in any way for I cannot make another year on this position. Actually, I like the idea different people to change on a position. For several reasons: - we defined rules. Let's follow them. If they are not perfect, let's improve them and not just ignore them. - it is an opportunity for other people to get more involved with the project. - it is an opportunity for the project to get new and fresh ideas and improvement on this topic from a new Release Manager. - it is an opportunity for me to spend this time for new things around the project. I am sure a new Release Manager will introduce new good things on top of what is at the moment. On course, as an ex-Release Manager, I can keep an eye that everything is doing well and give hand when help is needed. I am sure there are people in this community that will add new value to the project if they are promoted to the Release Manager position. If I am not on the Release Manager position any more, this does not mean that I will not work for Care2x. I will spend the time to do other things for the projects. Nothing bad in this. Let's have more people involved officially doing certain tasks. Finally, > An really open and transparent process where people can say to ALL why > they want to be "<something> Mantainer" and what are their proposals > to be achieved during their mandate? Even if this could stir some mroe > flamed discussions? This is something that has to be certainly done. We are community, aren't we? Let's act as such ;-) Let's this be a kick-off for everyone in this community to express its vision if he/she can define concrete position that will be responsible for certain tasks. And, as well, let anyone say if he/she wants take responsibility to take such position. Greetings Kaloyan On Wed, 2006-08-02 at 23:49 +0100, Lopo Lencastre de Almeida wrote: > Hi Elpídio and all, > > First let me congrat once again Kaloyan Raev for is very good job > done. > Also to all developers that made the bug squashing and several > aditions in such a short amount of time since the last stable > release. > > I red here at the list that the "mantainer" positions are supposed to > change from time to time. > > At the time of that discussion one year ago I was with problems with > my email and it may have missed me. > > The case is that, if I understood well, the "Release Mantainer" is > supposed to forceably change after an year, right? I must say that I > strongly disagree with that provision. > > The seul conditions for that change should be: > 1. Incompatibilities with the rest of the developer team > 2. Incompetence and missing to fullfil its proposed obligations > 3. Excessiv arguing with the community generating with that a > tense situation > 4. Tiresome. This can be too demanding on ones shoulders. > 5. The nominee willing to pull back for any personal and private > reason > I don't know if Kaloyan Raev fullfils the 4. and 5. items above but, > for what I saw this last months I can only say good things on his > behalf: > 1. He has good relations with other developers and is very kind > and helpful on his relations with them > 2. We see more releases and bug squashing than ever in this > project. He even proposes ideias. > 3. He is a peacemaker and I see him several times trying to calm > us down > Is there a real need to forcing him to step down if he don't mind to > bare this burden for a little more time? Good Release Mantainer don't > drop from trees. > > Another issue, that may be more critical, is: > > Shouldn't this be choosen like they are choosed in other FOSS > Projects? > > > An really open and transparent process where people can say to ALL why > they want to be "<something> Mantainer" and what are their proposals > to be achieved during their mandate? Even if this could stir some mroe > flamed discussions? > It could be even done in another maillist and not the one everyone > uses: developers or mere users (well, with Care2x no one can be *just* > a user ;) > > Just my two cents. > > > A small not just for Elpídio: You really *must* update the website > information regarding the version and features and also the software > version running on the Foundry demo site or else this effort is a > little bit deminished, don't you agree? > > Best regards to all. > > Lopo > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ Care2002-developers mailing > list Care2002-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/care2002-developers ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
