Jakarta Board Report January

2008-01-14 Thread Martin van den Bemt
== December 2007 Board Report ==

=== Status ===

The downsizing of Jakarta continued this quarter.
HttpComponents became TLP and has finished moving all the resources to their 
own TLP. We wish them
all the best with their new identity!
Slide was retired (see Slide section for more details), with a notice on the 
Slide page (see
http://jakarta.apache.org/slide/).

The main focus this quarter will be (re)starting discussions about the future 
of the mature
components/libraries like ORO, Regexp (maintained) and ECS and BCEL (not 
maintained).

=== Releases ===

  * 29 September 2007 - JMeter 2.3 final
  * 9 October 2007 - !HttpComponents !HttpCore 4.0 alpha 6
  * 7 November 2007 - !HttpComponents !HttpClient 4.0 alpha 2
  * 30 November 2007 - JMeter 2.3.1 final

=== Community changes ===

No changes in the community

=== Subproject news ===

 BCEL 

No activity this quarter. Since there is a lack of developer and user 
community, we should
definitely retire BCEL this quarter and also point the users to possible 
alternatives. A discussion
will be started about this.

 BSF 

There is an outstanding request for the TCK for scripting. Geir expressed the 
concern that
this TCK could be part of the JDK 1.6 TCK and not independ. We are sitll 
waiting for
the definitive answer on this.

 Cactus 

Development has picked up after Apachecon Atlanta and Petar is working towards 
a release.

 ECS 

No activity and not maintained. As with BCEL it is probably best to retire the 
project or see if it
can find a
home at Apache Commons.

 HttpComponents 

HttpComponents released one alpha each for HttpCore and HttpClient
as a Jakarta sub-project. A TLP proposal was submitted for the
November board meeting and accepted. Starting December 2007,
HttpComponents submits separate board reports as a TLP.

By end of December 2007, HttpComponents is no longer using Jakarta resources.
Mailing lists, SVN, website, dist, and archive have been moved.
The HttpComponents Wiki still has Jakarta in it's name, but it is
a separate Wiki.

 JCS 

No developer activity going on at this moment, though there is user activity on
the dev and user lists.

 JMeter 

JMeter released 2.3 and 2.3.1 final.

 ORO 

Since the mature nature hardly any activity (it is maintained). There are still 
a lot of users and
bug reports are actively monitored and acted upon. Since the library nature of 
the subproject it is
definitely worth investigating if Apache Commons can be the new home for this 
library.

 Regexp 

See ORO.

 Slide 

Due to the lack of a developer community, Slide has been retired on 03/Nov/2007.
It is thus no longer actively maintained or supported by the ASF.
Subversion, Bugzilla, and one of the mailing lists will remain open for a 
transition period.
Slide users will be pointed to Apache Jackrabbit as a replacement.

Every few weeks, somebody inquires about a separate WebDAV client project
on a mailing list of Slide, Jackrabbit, Commons, or HttpComponents. There
are some people, some of which are Apache committers, who expressed some
interest to put in some time, if others are with them. But nobody seems to
want to take the lead and request a sandbox or lab project in which to start.
The presence of two separate codebases (Jackrabbit, Slide) from which one
could start doesn't help. Jackrabbit is alive, Slide is used in the wild.

 Taglibs 

Development is still taking place, although not at a high priority. Bug fixing 
took place on the
Standard Taglib and there is the intention to make a final release after all 
bugfixing is done.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Jakarta Board Report

2007-06-18 Thread Rony G. Flatscher (Apache)
... snip ...
  BSF 

 MvdB :Silent quarter. A talk for Apachecon US was accepted (Rony Flatcher),
 which will hopefully increase the user base (observation : since the user
 list is also pretty quiet it can mean that BSF is bug free or it needs
 more users)
   
... snip ...

Sorry, oversaw that the release of beta 1 of BSF 3.0 fell into the
second quarter (ant was able to report the result of the vote on
2007-04-16) and should have been reported as such by us! This is the
version that brings JSR-223 (a.k.a.  Java 6 scripting framework) to
the Apache table: it allows de/employing the Java scripting framework
starting with Java 1.4 (the Sun implementation is only available
starting with Java 1.6/6, foregoing the entire pre-Java-6 installed
base). ant has been trying to get word on receiving the appropriate Sun
TCK from Geir, but so far no news can be reported here

---rony


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Jakarta Board Report

2007-06-18 Thread Martin van den Bemt
I've added it to the report..

Mvgr,
Martin

Rony G. Flatscher (Apache) wrote:
 ... snip ...
  BSF 

 MvdB :Silent quarter. A talk for Apachecon US was accepted (Rony Flatcher),
 which will hopefully increase the user base (observation : since the user
 list is also pretty quiet it can mean that BSF is bug free or it needs
 more users)
   
 ... snip ...
 
 Sorry, oversaw that the release of beta 1 of BSF 3.0 fell into the
 second quarter (ant was able to report the result of the vote on
 2007-04-16) and should have been reported as such by us! This is the
 version that brings JSR-223 (a.k.a.  Java 6 scripting framework) to
 the Apache table: it allows de/employing the Java scripting framework
 starting with Java 1.4 (the Sun implementation is only available
 starting with Java 1.6/6, foregoing the entire pre-Java-6 installed
 base). ant has been trying to get word on receiving the appropriate Sun
 TCK from Geir, but so far no news can be reported here
 
 ---rony
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Jakarta Board Report

2007-06-17 Thread Martin van den Bemt
== June 2007 Jakarta Board Report ==

=== Status ===

Another 2 projects have left Jakarta to live on their own : POI and Turbine
and both of almost (or completely) finished the move. I like to wish the
projects the best and a very good and long lasting future. In a seperate
mail there is a TLP proposal for commons, which on acceptance will mean
that the biggest part of the Jakarta community have no direct ties anymore
with Jakarta. The focus after commons will be on the projects left at
Jakarta and see if there is possibility for them to go TLP or when
that is not viable or possible, find a suitable solution for those projects.
My explicit wish is that there will be no deadline for projects to move so
there will be enough time to find the best solution, instead of the quickest
solution. We owe that to all the people in those projects who invest a lot
of time and energy in those projects.
One of the big discussions that took place was about the future of Jakarta
and the thing we in majority agreed on (at least the people who spoke up)
is that it is worth to save the Jakarta brand. Since I prefer to spend
the energy and time I have in the projects that are left at Jakarta, I
decided not to invest time on what will happen to the Jakarta brand at this
time, simply because they deserve my time and energy and out of respect for
the projects that still currently have their existance at Jakarta.
If the board decides to not esablish the commons TLP, we need to go back
to the drawing table.

All in all : a lot is happening and a lot is going to happen in the months
to come. If there is reason to do so, I will provide extra board reports
besides the quarterly schedule.

Reports prefixed with MvdB are written by me.

=== Releases ===

  * 30 March 2007 - !HttpComponents !HttpCore 4.0 alpha 4 released
  * 4 April 2007 - Commons DBCP 1.2.2
  * 8 April 2007 - Commons Configuration 1.4
  * 18 May 2007 - POI 3.0 Final released
  * 6 June 2007 - JCS 1.3 released

=== Community changes ===

New committers, pmc persons, asf members and departures.

  * New Committers
* Ben Speakmon was voted in as a Commons Committer
* Alf Hogemark was voted in as a JMeter Committer
* Asankha C. Perera was voted in as a !HttpComponents Committer
* M. Johnson (although not new, his account was created just now,
  because of CLA problems). (POI)

  * PMC Members
* Thomas Vandahl was voted on to the PMC
* Danny Angus was persuaded to come back on the PMC.
* Ant Elder was voted on the PMC.

Fixed the bookkeeping on the addition of Nick Burch to the Jakarta PMC (that
was reported in the December 2006 report.

=== Infrastructure news ===

The only things currently happening is the move of infrastructure for the 
Turbine and POI TLP projects.

=== General project news ===

The Jakarta PMC has started to review all Jakarta projects whether they
contain or rely on cryptographic software and if they must be marked as
described on http://apache.org/dev/crypto. This is an ongoing process and
we expect some corner cases where we will need legal advice.

=== Subproject news ===


 BCEL 

No activity.

 BSF 

MvdB :Silent quarter. A talk for Apachecon US was accepted (Rony Flatcher),
which will hopefully increase the user base (observation : since the user
list is also pretty quiet it can mean that BSF is bug free or it needs
more users)

 Cactus 

MvdB:
The ip clearance finally passed, so Petar is now able to (re)integrate
his code into the cactus codebase.

 Commons 

A commons TLP resolution was sent to the Board at the same time of this board 
report.

31 March 2007 - vote passed to promote the JCI (Java Compiler Interface) to a 
proper component (from
the Sandbox).

''Chain''
  * Ready for a 1.2 bugfix release.

''CLI''
  * Gearing up for a 1.1 release.

''Configuration''
  * 8 April 2007 - Configuration 1.4 released

''DBCP''
  * 1 April 2007 DBCP 1.2.2 released

''IO''
  * Gearing up for a 1.3.2 bugfix release.

''JCI''
  * Gearing up for a first 1.0 release.

''JXPath''
  * Gearing up for a 1.3 release.

''Logging''
  * Needs someone to do a 1.1.1 bugfix release.

''Math''
  * Gearing up for a 1.2 release.

''SCXML''
 * Working towards a 0.7 release.

 ECS 

Nothing happened on the ECS front.

 HttpComponents 

Work on the first alpha of !HttpClient 4.0 has made good progress. We expect to 
release
client-alpha1 and the matching core-alpha5 shortly.

There is currently no release manager for a potential !HttpClient 3.1 final 
release. Since the RC1
was released only in March, this is not an immediate problem. Bug reports are 
still dripping in, and
bugs keep getting fixed. But we'll need to find a volunteer eventually.

Various options to spin off !HttpComponents from Jakarta are being discussed.
This could improve the focus of the active members of the !HttpComponents 
(sub-)community.


 JCS 
JCS 1.3 has been released. Thomas Vandahl acted as the release

Jakarta Board Report

2007-03-26 Thread Martin van den Bemt

March 2007 Jakarta Board Report

Status

Activity seems to pick in projects that haven't been so active, so that's
really good news. Besides the releases and the code donation (see Cactus)
and the releases, there is nothing in particular that needs board attention
at this moment.
On a side note : I really hope we can go back to the 3 month schedule again.
If there is something out of the ordinary however, I will add an extra report.

Releases

* 13 February 2007 - Commons Fileupload 1.2 Released
* 17 March 2007 - Commons HttpClient 3.1-rc1 Released
* 18 March 2007 - Commons Transaction 1.2 Released
* 18 March 2007 - Jakarta Regexp 1.5 released

Community changes

Ant Elder - Voted as a committer for the BSF.
Stephen Kestle - Voted as a committer for Commons

BSF
Ant Elder - Voted as a committer for the BSF.

Cactus

Currently in the process of voting on a new committer (Petar Tahchiev).
After this vote a vote will be started to finish the code donation
by Petar, for more details of the code grant, please see
http://incubator.apache.org/ip-clearance/jakarta-cactus-tahchiev.html.

Commons FileUpload

The release 1.2 of Commons Fileupload 1.2 introduces a new streaming API,
which allows to use the library with arbitrarily large files and an extremely
low memory profile.

POI

Gearing up for a release of 3.0, which hopefully will be in a month or so's
time.

Regexp

Released 1.5 version of Regexp which brings number of known issues down to 3.
Dev and user lists are quiet.

Mvgr,
Martin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Jakarta Board Report

2007-03-26 Thread Jim Jagielski

Thank you for your report. It has been added to
the board agenda.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Jakarta board Report February

2007-02-21 Thread Niall Pemberton

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

Re: Jakarta board Report February

2007-02-21 Thread Martin van den Bemt
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 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