Apache Logo
The Apache Way Contribute ASF Sponsors

Formal board meeting minutes from 2010 through present. Please Note: The board typically approves minutes from one meeting during the next board meeting, so minutes will be published roughly one month later than the scheduled date. Other corporate records are published, as is an alternate categorized view of all board meeting minutes.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

JSecurity

21 Jan 2009

JSecurity is a powerful and flexible open-source Java security framework
that cleanly handles authentication, authorization, enterprise session
management and cryptography.

JSecurity has been incubating since June 2008.

At the end of November, the JSecurity team released a final
external (non-Apache) release: 0.9.0 final.  All modifications
after the release were made under the assumption that the next
release will be an Apache incubating release.

After the November final release, there has been lengthy discussion
for the month and half following about JSecurity's name and whether
or not it should be changed to something else.  3 mentors voted in favor
of chainging the name to something else, 1 voted against, and 1 abstained.
Those voting in favor cited concerns of a few external
(3rd party) products that might cause a name conflict.  Concensus was
not reached, resulting in the vote.  However, it is considered
still an open issue with continued discussion as other IPMC members
are contributing to the discussion.

More recently, the team has debated about how the source tree
should be configured to allow easy modular builds and to clearly
delineate the differnece of JSecurity core versus web support and
3rd party support.  The team came to concensus about an initial
directory organization and the ant build files were modified to
reflect the new structure.  It was also discussed that two build
systems, both Ant+Ivy and Maven, could be used to build the framework,
allowing the one building to choose based on their preference.

Infrastructure migration (noted in our STATUS file) is almost
complete - all that needs to be done is migration of the jsecurity.org
website into our incubator snapshot.  A volunteer is currently
in the process of enabling the existing JSecurity theme in the ASF's
Confluence export mechanism.

Low-hanging fruit to be cleared hopefully by the next board report is
all IP clearance:  the Copyright & Licensing and Distribution Rights
sections of the STATUS file should be able to be completed in their
entirety.

The biggest exit criteria remaining is Team Collaboration.  Although
the team is satisfying all collaboration directives and has a good
community, we need to attract new committers.  Hopefully that will be
a significant difference in the upcoming months and throughout 2009.

Finally, one of our mentors, Alex Karasulu, had to step down and remove
himself as a mentor, citing busy schedules and not enough time to
dedicate (http://markmail.org/message/hkh6pjwjlnmtkrjp).  We are
very grateful for the time he was able to contribute!

The project team is not considering graduation at this point,
as the code is not ready for an Apache release. Once IP clearance is
complete, we'll attempt our first incubator release.

The status is being maintained in SVN
(http://svn.apache.org/repos/asf/incubator/jsecurity/STATUS)

19 Nov 2008

We just have to report that the code base has been imported into the ASF
repository, and as it was a long waited move, it's good to have it announced
in this monthly report !

15 Oct 2008

JSecurity is a powerful and flexible open-source Java security framework
that cleanly handles authentication, authorization, enterprise session
management and cryptography.

JSecurity has been incubating since June 2008.

Last month, a new external release was issued (0.9.0-RC2).
After this, a single bug fix has been implemented and
committed to the external SourceForge SVN repository.
Many other commits have been made, but all were nonfunctional
and were made to round out the project's JavaDoc.

The JavaDoc is already quite good, but not 100%.  The team has
discussed on the development list that it would be a good idea
to get the JavaDoc completed at 100% before releasing 0.9 final,
with 0.9 final being the last external release.  After this point,
we wanted to inject the code source into the Apache repository
as a 'clean slate' initiative.

The idea is that perhaps 0.9.1 would be an Apache release,
allowing that release to focus only on adherence to Apache
policy and not dependent on code or documentation.  Then all
subsequent releases could benefit from the experience of this
'first run', continuing to maintain Apache policy.

The JavaDoc is currently being updated intermittently, as the
development team has the opportunity to update it in their spare
time.  It is certainly desirable to finish this effort soon,
hopefully no more than a week or two. But this time frame is
ultimately dependent upon the number of contributors.

The project team is not considering graduation at this point,
as the code is not ready for an Apache release. The community
is working well, with decisions being made in public.

The status is being maintained at
http://svn.apache.org/repos/asf/incubator/jsecurity/STATUS

17 Sep 2008

JSecurity is a powerful and flexible open-source Java security framework
that cleanly handles authentication, authorization, enterprise session
management and cryptography.

JSecurity has been incubating since June 2008.

Since last month, a new external release has been issued (0.9.0-RC2), and
some
bug fixes, and discussion about the configuration format.

The code source should be injected to the Apache repository soon, when the
external 0.9.0 release will be out. It's a matter of days, may be a week,
accordingly to the latest discussion on the mailing list.

JIRA is set up, but it should be used.

The status is being maintained at
http://svn.apache.org/repos/asf/incubator/jsecurity/STATUS

20 Aug 2008

JSecurity is a powerful and flexible open-source Java security framework
that cleanly handles authentication, authorization, enterprise session
management and cryptography.

JSecurity has been incubating since June 2008.

The project has been very active, with plenty of discussion around
features, implementation, and strategy, on both user and dev lists.

The code is still at codehaus, with the plan to migrate the code base
with all history to the apache repository once a release has been made.
Once the code is in the apache repository, additional releases of the
org.jsecurity code may be published via codehaus, while the
packages are renamed to org.apache.jsecurity.

Mailing lists have been set up, and most email traffic has been migrated
from the previous lists at codehaus.

The JIRA project is set up and is tracking new issues. Issues will be
migrated from the existing bug tracking system in due time.

The status is being maintained at
http://svn.apache.org/repos/asf/incubator/jsecurity/STATUS

16 Jul 2008

JSecurity is a powerful and flexible open-source Java security framework
that cleanly handles authentication, authorization, enterprise session
management and cryptography.

JSecurity has been incubating since June 2008.

The project has kicked off with some basic infrastructure now in place.

Mailing lists have been set up.

The svn repository is ready for code.

The JIRA project is set up.

The initial committers have sent ICLA's and all accounts have been created.

Discussion is underway as to migration of the existing code into the Apache
repository. There is an existing code base with users that will need to have
releases and maintenance while the project is incubating.

PMC comments:
 * jukka: JSecurity status page is missing