Re: Jakarta board Report February
I am actually maintaining that, although at a pace that makes you fall a sleep ;) Mvgr, Martin Niall Pemberton wrote: > Previous Board reports have been archived here: > > http://jakarta.apache.org/site/pmc/board-reports.html > > Would be good to continue this IMO. > > Niall > > On 2/19/07, Martin van den Bemt <[EMAIL PROTECTED]> wrote: >> >> Jakarta Board Report >> >> Status >> >> This board report was mainly constructed by other people than me, >> which is a big improvement (thanks everyone). I also moved the board >> report to a fixed location on the wiki >> (http://wiki.apache.org/jakarta/JakartaBoardReport-current), so it's >> easier to locate for people. The code grant for the not yet commons >> SSL (formerly named commons-ssl), has been completed, so we can >> progress to having a vote where SSL should end up on general and >> based on that result take the correct incubator path (legal / >> full incubation). >> >> What is not completely clear for me at this point, is the board >> report schedule. An extra report was requested (lack of commons >> projects in the report). Reporting next month again will be a lot of >> work, since my goal is to report on every subproject (even if there >> is no or hardly any activity). >> >> Inactive projects >> >> Disclaimer : we have lot's of active projects ! >> >> Definition list : >> >> Inactive project = a project that has no *developer* community. >> >> The Apache Way : >> >> To become committer on a project you have to earn that right, you >> have to stand out, submit patches, show you care, learn the apache >> way and have to get noticed by the current committers who can >> nominate such a person. >> >> Problem : >> >> If that didn't happen enough in the past, it can happen that at a >> certain point no developer community is active anymore. >> >> Which causes : >> >> A catch22 situation. Since there is no developer community, no one >> is able to determine if people deserve to become a committer. Even if >> you are monitoring such a list (such as I do for all Jakarta lists), >> it is hard to determine if people deserve committership. >> >> Solution : >> >> The only thing we know for sure : inactive projects needs someone to >> mentor the project to become active again. This goes for all possible >> scenario's : >> >> 1. Actively support forks and when they show they are capable to work >>on the project, get the code back (needs mentoring, grants, etc) >> 2. More liberal in getting committers on board >> 3. Actively following the user / dev lists and issue trackers to see >>if there is someone ready for committer ship. (is the normal way, >>although the focus here is not if patches etc are technically >>correct) >> >> I like to prevent Jakarta becoming some kind of collection with >> inactive project, so the first goal is preventing that this scenario >> occurs on our current subprojects where possible. So I would like to >> ask the current active developers to invest a little bit more time in >> looking what others are doing. >> >> I think this discussion is also useful to have on the incubator list. >> Releases >> >> * 13 February 2007 Commons Lang 2.3 >> * 13 February 2007 Commons IO 1.3.1 >> * 30 January 2007 Commons IO 1.3 >> * 30 December 2006 Commons Betwixt 0.8 >> * 30 December 2006 Commons VFS 1.0 >> * 19 December 2006 Commons SCXML 0.6 >> >> Community changes >> >> New committers, pmc persons, asf members and departures. >> >> PMC Members >> >> * Yoav Shapira resigned from the PMC >> >> The following new commiters were voted in: >> >> * Yegor Kozlov (POI) >> * Luc Maisonobe (Commons Math) >> * Matt Benson (Commons JXPath) >> >> Infrastructure news >> >> Started to investigate the moderators we have and contacting all the >> moderators asking if they are still active. If there are gaps, I will >> try to fill the void by finding volunteers. This way we prevent that >> lists aren't moderated. >> >> Subproject news >> >> Sections with a prefix of MvdB are notes added by the chair >> >> BCEL >> >> MvdB : >> >> Some user questions, further no action taken on the future of BCEL >> (on the list is contacting the 2 currently exising forks out there, >> to see if there is interenst in moving development back to Jakarta. >> Afaik Findbugs and AspectJ have forks. >> >> BSF >> >> MvdB : >> >> They are currently planning for a 3.0 release and for jsr223 they >> are investigating to get the TCK. Geir is in the process of >> arranging things. >> >> Cactus >> >> MvdB : >> >> Cactus development was stalled and recently Petar Tahchiev sent a >> mail to the list, saying he had continued development of cactus on >> https://mamouth.svn.sourceforge.net/svnroot/mamouth. I >> (=Martin van den Bemt) am currently in the process of informing >> Petar on what actions to take (eg Code Grants/CLA/CCLA) to move >> development back to the cactus project. When the paperwork is there, >> we will run the code base through t
Re: Jakarta board Report February
Previous Board reports have been archived here: http://jakarta.apache.org/site/pmc/board-reports.html Would be good to continue this IMO. Niall On 2/19/07, Martin van den Bemt <[EMAIL PROTECTED]> wrote: Jakarta Board Report Status This board report was mainly constructed by other people than me, which is a big improvement (thanks everyone). I also moved the board report to a fixed location on the wiki (http://wiki.apache.org/jakarta/JakartaBoardReport-current), so it's easier to locate for people. The code grant for the not yet commons SSL (formerly named commons-ssl), has been completed, so we can progress to having a vote where SSL should end up on general and based on that result take the correct incubator path (legal / full incubation). What is not completely clear for me at this point, is the board report schedule. An extra report was requested (lack of commons projects in the report). Reporting next month again will be a lot of work, since my goal is to report on every subproject (even if there is no or hardly any activity). Inactive projects Disclaimer : we have lot's of active projects ! Definition list : Inactive project = a project that has no *developer* community. The Apache Way : To become committer on a project you have to earn that right, you have to stand out, submit patches, show you care, learn the apache way and have to get noticed by the current committers who can nominate such a person. Problem : If that didn't happen enough in the past, it can happen that at a certain point no developer community is active anymore. Which causes : A catch22 situation. Since there is no developer community, no one is able to determine if people deserve to become a committer. Even if you are monitoring such a list (such as I do for all Jakarta lists), it is hard to determine if people deserve committership. Solution : The only thing we know for sure : inactive projects needs someone to mentor the project to become active again. This goes for all possible scenario's : 1. Actively support forks and when they show they are capable to work on the project, get the code back (needs mentoring, grants, etc) 2. More liberal in getting committers on board 3. Actively following the user / dev lists and issue trackers to see if there is someone ready for committer ship. (is the normal way, although the focus here is not if patches etc are technically correct) I like to prevent Jakarta becoming some kind of collection with inactive project, so the first goal is preventing that this scenario occurs on our current subprojects where possible. So I would like to ask the current active developers to invest a little bit more time in looking what others are doing. I think this discussion is also useful to have on the incubator list. Releases * 13 February 2007 Commons Lang 2.3 * 13 February 2007 Commons IO 1.3.1 * 30 January 2007 Commons IO 1.3 * 30 December 2006 Commons Betwixt 0.8 * 30 December 2006 Commons VFS 1.0 * 19 December 2006 Commons SCXML 0.6 Community changes New committers, pmc persons, asf members and departures. PMC Members * Yoav Shapira resigned from the PMC The following new commiters were voted in: * Yegor Kozlov (POI) * Luc Maisonobe (Commons Math) * Matt Benson (Commons JXPath) Infrastructure news Started to investigate the moderators we have and contacting all the moderators asking if they are still active. If there are gaps, I will try to fill the void by finding volunteers. This way we prevent that lists aren't moderated. Subproject news Sections with a prefix of MvdB are notes added by the chair BCEL MvdB : Some user questions, further no action taken on the future of BCEL (on the list is contacting the 2 currently exising forks out there, to see if there is interenst in moving development back to Jakarta. Afaik Findbugs and AspectJ have forks. BSF MvdB : They are currently planning for a 3.0 release and for jsr223 they are investigating to get the TCK. Geir is in the process of arranging things. Cactus MvdB : Cactus development was stalled and recently Petar Tahchiev sent a mail to the list, saying he had continued development of cactus on https://mamouth.svn.sourceforge.net/svnroot/mamouth. I (=Martin van den Bemt) am currently in the process of informing Petar on what actions to take (eg Code Grants/CLA/CCLA) to move development back to the cactus project. When the paperwork is there, we will run the code base through the incubator (at a minimum legal). Commons Switching from Maven-1 to Maven-2 gets closer - we can now build the website from Maven-2. Next we need to look at how we would do a release under Maven-2 and whether it passes our requirements. Key: * Inactive - No activity, no one watching it. Candidate for dormancy. * Maintenance - No activity, someone watching it. There are thirty-two components in the Commons 'Proper', that is the released components. Attributes Inactive - however
Jakarta board Report February
Jakarta Board Report Status This board report was mainly constructed by other people than me, which is a big improvement (thanks everyone). I also moved the board report to a fixed location on the wiki (http://wiki.apache.org/jakarta/JakartaBoardReport-current), so it's easier to locate for people. The code grant for the not yet commons SSL (formerly named commons-ssl), has been completed, so we can progress to having a vote where SSL should end up on general and based on that result take the correct incubator path (legal / full incubation). What is not completely clear for me at this point, is the board report schedule. An extra report was requested (lack of commons projects in the report). Reporting next month again will be a lot of work, since my goal is to report on every subproject (even if there is no or hardly any activity). Inactive projects Disclaimer : we have lot's of active projects ! Definition list : Inactive project = a project that has no *developer* community. The Apache Way : To become committer on a project you have to earn that right, you have to stand out, submit patches, show you care, learn the apache way and have to get noticed by the current committers who can nominate such a person. Problem : If that didn't happen enough in the past, it can happen that at a certain point no developer community is active anymore. Which causes : A catch22 situation. Since there is no developer community, no one is able to determine if people deserve to become a committer. Even if you are monitoring such a list (such as I do for all Jakarta lists), it is hard to determine if people deserve committership. Solution : The only thing we know for sure : inactive projects needs someone to mentor the project to become active again. This goes for all possible scenario's : 1. Actively support forks and when they show they are capable to work on the project, get the code back (needs mentoring, grants, etc) 2. More liberal in getting committers on board 3. Actively following the user / dev lists and issue trackers to see if there is someone ready for committer ship. (is the normal way, although the focus here is not if patches etc are technically correct) I like to prevent Jakarta becoming some kind of collection with inactive project, so the first goal is preventing that this scenario occurs on our current subprojects where possible. So I would like to ask the current active developers to invest a little bit more time in looking what others are doing. I think this discussion is also useful to have on the incubator list. Releases * 13 February 2007 Commons Lang 2.3 * 13 February 2007 Commons IO 1.3.1 * 30 January 2007 Commons IO 1.3 * 30 December 2006 Commons Betwixt 0.8 * 30 December 2006 Commons VFS 1.0 * 19 December 2006 Commons SCXML 0.6 Community changes New committers, pmc persons, asf members and departures. PMC Members * Yoav Shapira resigned from the PMC The following new commiters were voted in: * Yegor Kozlov (POI) * Luc Maisonobe (Commons Math) * Matt Benson (Commons JXPath) Infrastructure news Started to investigate the moderators we have and contacting all the moderators asking if they are still active. If there are gaps, I will try to fill the void by finding volunteers. This way we prevent that lists aren't moderated. Subproject news Sections with a prefix of MvdB are notes added by the chair BCEL MvdB : Some user questions, further no action taken on the future of BCEL (on the list is contacting the 2 currently exising forks out there, to see if there is interenst in moving development back to Jakarta. Afaik Findbugs and AspectJ have forks. BSF MvdB : They are currently planning for a 3.0 release and for jsr223 they are investigating to get the TCK. Geir is in the process of arranging things. Cactus MvdB : Cactus development was stalled and recently Petar Tahchiev sent a mail to the list, saying he had continued development of cactus on https://mamouth.svn.sourceforge.net/svnroot/mamouth. I (=Martin van den Bemt) am currently in the process of informing Petar on what actions to take (eg Code Grants/CLA/CCLA) to move development back to the cactus project. When the paperwork is there, we will run the code base through the incubator (at a minimum legal). Commons Switching from Maven-1 to Maven-2 gets closer - we can now build the website from Maven-2. Next we need to look at how we would do a release under Maven-2 and whether it passes our requirements. Key: * Inactive - No activity, no one watching it. Candidate for dormancy. * Maintenance - No activity, someone watching it. There are thirty-two components in the Commons 'Proper', that is the released components. Attributes Inactive - however the last release had an issue so a new release ideally needs to be done. BeanUtils Maintenance. A 1.8.0 release is slowly being worked on. Struts were a major user, however they've moved on to using OGNL in
