This was extracted (@ 2024-04-17 22:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
Report was filed, but display is awaiting the approval of the Board minutes.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Project Status: Over the past year two pmc members left. Many more in the years prior. There are four active members remaining, including one who was added to the PMC in the last quarter. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (19 years ago) There are currently 59 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - Brian Demers was added to the PMC on 2023-10-23 - No new committers. Last addition was Fredrik Roubert on 2023-07-10. ## Project Activity: Per sub-project: - ApacheDS: Apache DS 2.0.0.AM27 was released on 2023-10-21. - LDAP API: Apache LDAP API 2.1.5 was released on 2023-10-12. - Studio: no activity: Stefan Seelman was the maintainer of this project for many years. He has left the project and we must find someone else. - Fortress: low activity - Kerby: low activity - Mavibot: no activity - SCIMple: good activity: The first release in the works ## Community Health: Activity is low but project continues to be adequately maintained despite concerns over losing members and not being able to attract new ones.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Project Status: - New: Scimple release being worked on. - Ongoing: Fortress migrated to Jakarta - Ongoing: ApacheDS first release in over 3 years. - At risk: With the addition of Brian Demers we only have 4 active PMC members to vote on releases. ## Membership Data: Apache Directory was founded 2005-02-22 (17 years ago) There are currently 59 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - Brian Demers added to the PMC members on 2023-10-23. - Fredrik Roubert was added as committer on 2023-07-10 - Longtime PMC member Stefan Seelman went emeritus. ## Project Activity: Overall: Activity's slow but steady, the projects are being maintained. ## Community Health: No problems to report. 4Q activity low but PMC has active members and the project continues to be adequately maintained. ## Releases: - Apache Fortress 3.0.0 was released on 2023-09-06. - Apache LDAP API 2.1.4 was released on 2023-08-29. - Apache LDAP API 2.1.5 was released on 2023-10-12. - Apache DS 2.0.0.AM27 was released on 2023-10-21.
No report was submitted.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Project Status: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (17 years ago) There are currently 58 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - Fredrik Roubert was added as committer on 2023-07-10. ## Project Activity: Activity's slow but steady, the projects are being maintained. - Fortress has migrated from Javax to Jakarta and a release will be soon. ## Community Health: No problems to report. 1Q activity low but PMC has active members and the project continues to be adequately maintained.
No report was submitted.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (18 years ago) There are currently 59 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - No new committers. Last addition was Brian Demers on 2022-04-14. ## Project Activity: Activity's slow but steady, the projects are being maintained. The PMC is pleased to note that activity in Scimple continues to be robust with what appears to be a growing community. ## Community Health: No problems to report. 1Q activity low but PMC has active members and the project continues to be adequately maintained.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (18 years ago) There are currently 59 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - No new committers. Last addition was Brian Demers on 2022-04-14. ## Project Activity: Overall: Activity's slow but steady, the projects are being maintained. Per sub-project: - ApacheDS: low activity. - LDAP API: low activity. - Studio: low activity. - Fortress: low activity. - Kerby: low activity. Security vulnerability reported. Fix has been merged into the repo. There were some delays which have introduced concerns that will be monitored closely. - Mavibot: low activity. - SCIMple: good activity. Brian Demers continues work on Scimple. Still no release is scheduled which is an ongoing concern as the project has yet to be released. ## Community Health: No problems to report. 4Q activity low but PMC has active members and the project continues to be adequately maintained.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (18 years ago) There are currently 59 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - No new committers. Last addition was Brian Demers on 2022-04-14. ## Project Activity: Overall: Activity's slow but steady, the projects are being maintained. Per sub-project: - ApacheDS: low activity. Work being done in preparation of new release including many bug fixes, and complete review of the PasswordPolicy implementation. - LDAP API: low activity. Now using latest MINA. A few extensions needed for the coming ApacheDS release. Released in last quarter. - Studio: low activity. - Fortress: low activity. Upgrade to latest Apache Wicket. Released in last quarter. - Kerby: low activity. - Mavibot: low activity. - SCIMple: low activity but increasing. A new committer, Brian Demers, continues work on Scimple and gave a presentation at ACNA. ## Community Health: No problems to report. 3Q activity low but PMC has active members and the project continues to be adequately maintained. Two releases last quarter. One project (scimple) that's being revived.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (17 years ago) There are currently 59 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - Brian Demers was added as committer on 2022-04-14 ## Project Activity: Overall: Activity's slow but steady, the projects are being maintained. Per sub-project: - ApacheDS: low activity. - LDAP API: low activity. - Studio: low activity. - Fortress: low activity. - Kerby: low activity. 2.0.2 was released on 2022-05-09. - Mavibot: low activity. - SCIMple: good activity. Brian Demers was added as a committer to the project and many changes have been made. Project seems to be moving in the right direction. ## Community Health: No problems to report. 2Q activity low but PMC has active members and the project continues to be adequately maintained.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (17 years ago) There are currently 58 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - No new committers. Last addition was Admir Hodzic on 2021-05-17. - Brian Burch removed from Directory committers list. ## Project Activity: Overall: Activity's slow but steady, the projects are being maintained. Per sub-project: - ApacheDS: low activity. New release using latest MINA 2.2, soon. Had to rework for TLS changes in MINA. - LDAP API: low activity. Same as above. - Studio: low activity. Security issue was brought up to PMC. It was determined the issue is with the underlying Eclipse framework that Studio uses. - Fortress: low activity. Added support for OpenLDAP 2.5. Many upgrades, latest Apache Wicket, CXF, other packages. - Kerby: low activity. - Mavibot: low activity. - SCIMple: no activity. Current maintainers have drifted away. Just now entering discussions with Brian Demers who has offered to take over as maintainer. A vote to add him as committer is underway. Critical next steps include planning a first release, getting the website updated. ## Community Health: No problems to report. 1Q activity low but PMC has active members and the project continues to be adequately maintained.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (15 years ago) There are currently 58 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - No new committers. Last addition was Admir Hodzic on 2021-05-17. ## Project Activity: Overall: While activity remains low, the projects are being maintained, community involvement remains fair. Fortress was impacted by Log4Shell vulnerability. An emergency release was coordinated over private mailing list followed by release 2 days after the announcement demonstrating the PMC is able to respond to critical security issues. Per sub-project: - ApacheDS: low activity but starting to pickup, with more programmer involvement expected in '22 - LDAP API: moderate activity. - Studio: low activity but being maintained. - Fortress: moderate activity. Emergency release for Log4j-core vulnerability. Response to CVE-2021-44228. - Kerby: low activity. Release being planned. - Mavibot: low activity. - SCIMple: no activity. ## Community Health: No problems to report. 4Q activity low but PMC has active members and the project continues to be adequately maintained. ## Releases: Emergency releases: Apache Fortress 2.0.7: 2021-12-12 was released on 2021-12-12.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (17 years ago) There are currently 59 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - No new committers. Last addition was Admir Hodzic on 2021-05-17. ## Project Activity: Overall: A critical security fix was made to Studio. Per sub-project: - ApacheDS: low activitiy. - LDAP API: low activity. - Studio: moderate activity: a security vulnerability, CVE-2021-33900, regarding SASL authN was reported and fixed. - Fortress: low activity. Approved the donation of a new library, openldap accelerator client. Details still being worked out including the CCLA. - Kerby: low activity. - Mavibot: low activity. - SCIMple: low activity. The maintainers are responding to questions on ML. ## Community Health: No problems to report. 3Q activity low but PMC has active members and the project continues to be adequately maintained. ## Releases: Apache Directory Studio 2.0.0-M17 was released on 2021-07-24. Apache Fortress 2.0.6 was released on 2021-07-15.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (16 years ago) There are currently 59 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - Admir Hodzic was added as committer on 2021-05-17 ## Project Activity: Overall: A number of critical security fixes (and improvements) made to studio, apacheds and the API. Per sub-project: - ApacheDS: moderate activitity: security fixes and improvements along with support for latest version of Java. - LDAP API: moderate activity: security fixes and improvements pushed out with two releases this quarter. - Studio: moderate activity: security, bug fixes and improvements to integration tests working across (different) directory server implementaions. - Fortress: moderate activity: bug fixes and enhancements including migration to LDAP API 2.x. Next release is being voted on currently. - Kerby: low activity: security and bug fixes. - Mavibot: low activity. - SCIMple: very low activity. ## Community Health: - No problems to report. 2Q activity continues to be fairly low but reliably steady.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. Besides LDAP it supports Kerberos 5 and the Change Password Protocol. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (15 years ago) There are currently 58 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - new committer Jiayi Liu on 2021-01-11 ## Project Activity: Overall: Activity over the subprojects continues to be low but the needful is being done thanks to the work of a few dedicated members. Also community interaction remains steady. As first reported last quarter we are using the new CMS and the project website migration (using it) was successful. This was a big effort, and we want to recognize the work from Roy Lenferink and Stefan Seelman. Per sub-project: - ApacheDS: low activitity: due to a known corruption issue in its backend database the project has placed a notification on its website recommending the directory is not be used in production unless the data is read-only. This recommendation will be lifted when the necessary changes are made to migrate to the new backend (mavibot). Also work done to migrate tests to Junit 5 is nearly complete. - LDAP API: very low activity. - Studio: moderate activity: new release this quarter - Fortress: low activity: bug fixes and enhancements. Plans for next release put off to early summer. - Kerby: low activity: security and bug fixes. - Mavibot: low activity. - SCIMple: no activity. ## Community Health: No problems to report. 1Q activity continues to be low but steady across most of the sub-projects. ## Releases: Apache Directory Studio 2.0.0-M16 was released on 2021-02-21
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. Besides LDAP it supports Kerberos 5 and the Change Password Protocol. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (16 years ago) There are currently 58 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - new committer Jiayi Liu on 2021-01-11 ## Project Activity: Overall: As first reported last quarter we are using the new CMS and the project website migration (using it) was successful, made possible by a large effort from a few members of our project team. Per sub-project: - ApacheDS: low activitity: security, bug fixes and work migrating to Junit 5. - LDAP API: very low activity. - Studio: low activity: being maintained, with latest eclipse compatibility (its framework) and move beyond Java 8 is required. - Fortress: low activity: security, bug fixes and enhancements. Planning for next release, late spring early summer. - Kerby: low activity: security and bug fixes. - Mavibot: low activity. It was heavily modified during 2Q 2020. At that time transactions across B-trees were added. Next is to add old revisions removal. This is quite a bit more work but the developer, Emmanuel Lecharny has made it clear that it will be done. It's considered important to the future of the directory server sub-project due to its promise of a stable database. - SCIMple: no activity. ## Community Health: No problems to report. 4Q activity continues to be low but steady across most of the sub-projects.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. Besides LDAP it supports Kerberos 5 and the Change Password Protocol. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (16 years ago) There are currently 58 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - No new committers. Last addition was Lothar Haeger on 2018-12-16. ## Project Activity: Overall: Activty continues to be low but not a concern because as previously reported the project team remains intact and completing tasks as necessary. The big item that needs to be addressed this quarter is moving off of the old Apache CMS/SVN system onto a new one using Hugo and Git. Roy Lenferink and Andrew Wetmore from the infra team have been helping us with this. There is a lot of content to manage and so we really appreciate their help. We held a vote last week and agreed to use Hugo and Git. Challenges will be training the PMC (to use the new system) we'll let you know how it goes. There are also typical assignments like migrating unit tests off of builds.a.o instance to work with the new Jenkins servers. Stefan Seelman has been handling that. Per sub-project: - ApacheDS: low activity: although we continue to see user input and PR's are up. - LDAP API: very low activity. - Studio: low activity. - Fortress: low activity: ApacheCon @Home presentation: A Groovy Apache Fortress. - Kerby: low activity. - Mavibot: low activity. - SCIMple: low activity. ## Community Health: 3Q activity continues to be low across the sub-projects, decrease in overall mailing list activity, commits and JIRA. On the brightside, there is an uptick in PR's showing the community remains interested and engaged. Still plenty left to do and we're optimistic about the future.
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. Besides LDAP it supports Kerberos 5 and the Change Password Protocol. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Directory was founded 2005-02-22 (15 years ago) There are currently 58 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Radovan Semancik on 2018-09-28. - No new committers. Last addition was Lothar Haeger on 2018-12-16. ## Project Activity: Per sub-project: - ApacheDS: low activity: Status about the same as last quarter. User questions and occasional security issues get brought to PMC, to be evaulated and acted on. - LDAP API: low activity: Also had a release this quarter. - Studio: low activity: A release this quarter shows the project is still active and being maintained. - Fortress: low activity: Also picking up a bit this past quarter with a new release and several improvements being made. - Kerby: low activity but also still being maintained and a release this past quarter as well. - Mavibot: renewed activity, transaction support added just recently. This will be the new backend for ApacheDS and fix a longstanding problem with data corruption. - SCIMple: low activity: More commits tricking into the git repository shows the project maintainers are still working. Very low interaction between the team developing the software and the PMC. Communication will have to improve to ensure this particular sub-project is moving on a forward trajectory. ## Community Health: 2Q brought a bit more activity in the subprojects with three releases and renewed activity across all of the projects although still rather low. The PMC is active and responsive ensuring the necessary steps are being done to keep the lights on, responding to questions, acting on pull requests, fixing bugs, making minor improvements. There are a few risks. Low activity on the mailing list is a concern although downloads are robust in directory, kerby, studio and the api and about the same in fortress telling us that the software is still quite important to the ecosystem. Things are being tried to renew interest in the projects and bring fresh blood in. For example a new slack channel on fortress. Also noticing an uptick in commits. ## Releases: - Apache Kerby 2.0.1 was released on 2020-06-03. - Apache Fortress 2.0.5 was released on 2020-05-28. - Apache Directory Studio 2.0.0-M15 was released on 2020-04-18. ## Mailing list activity: Up a bit in fortress, about the same in api, down in users. - api@directory.apache.org had a 93% decrease in traffic in the past quarter (1 emails compared to 13) - dev@directory.apache.org had a 1% increase in traffic in the past quarter (327 emails compared to 323) - fortress@directory.apache.org had a big increase in traffic in the past quarter (11 emails compared to 0) - notifications@directory.apache.org had a 51% increase in traffic in the past quarter (85 emails compared to 56) - users@directory.apache.org had a 60% decrease in traffic in the past quarter (22 emails compared to 55) ## JIRA activity: - 35 issues opened in JIRA, past quarter (84% increase) - 35 issues closed in JIRA, past quarter (-2% decrease)
## Description: The Apache Directory TLP consists of the following sub-projects: - ApacheDS: An extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group. Besides LDAP it supports Kerberos 5 and the Change Password Protocol. - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware” API with some convenient ways to access all types of LDAP servers. - Studio: A complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins. - Fortress: A standards-based authorization platform that provides role-based access control, delegated administration and password policy services with an LDAP backend. - Kerby: An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. - Mavibot: An embeddable key-value database library with MVCC (Multi Version Concurrency Control) support. - SCIMple: An implementation of SCIM v2.0 specification. ## Issues: - There are no issues requiring board attention at this time. ## Activity: Per sub-project: - ApacheDS: low activity: The project continues to be fairly low activity although there’s been an uptick this quarter with a release. The major hurdle for this project is utilization of the new backend, mavibot, bringing much needed performance improvements and stability to the directory server. - LDAP API: low activity: Also had a release this quarter. Downloads over maven remain robust, around 1M/month. - Studio: low activity: No releases this quarter but still being maintained and used. Also robust download activity. - Fortress: low activity: This project also had a release recently containing enhancements and bug fixes. The next hurdle for this project is to consume the LDAP API 2.x which will bring it in line with current. - Kerby: very low activity but also still being maintained with lots of downloads per month. - Mavibot: no activity - SCIMple: low activity: After several quarters with almost zero activity (being called out on previous reports) this project woke up a bit this quarter. Numerous pull requests and coding activities although still not much in the way of communication over the mailing list. We are in contact with the project team and will continue to monitor this activity closely. ## Health report: Another slow quarter for the projects that comprise this TLP. While this is a cause for concern, the PMC feels the overall health of the project remains healthy with a decent core of contributors maintaining, fixing bugs. Demand remains for the project's wares, we are continuing to release, albeit at a lower level than in previous years, as evidenced by overall decreased commits. ## PMC changes: - Currently 19 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Radovan Semancik on Sat Sep 29 2018 ## Committer base changes: - Currently 58 committers. - No new committers added in the last 3 months - Lothar Haeger was added as a committer on Mon Dec 17 2018 ## Releases: - Apache LDAP API 2.0.1 was released on 2020-03-26. - ApacheDS 2.0L.0.AM26 was released on 2020-03-07. - Apache Fortress 2.0.4 was released on 2019-12-13. ## Mailing list activity: - Dev, Users and API, moderate increase. - Fortress, Kerby and Scimple almost no activity on mailing lists. ## JIRA activity: - 19 issues opened in JIRA, past quarter (-26% decrease) - 25 issues closed in JIRA, past quarter (150% increase)
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification.
## Issues:
The PMC is concerned that project activity is very low. This is mostly due to
lack of contributors as the community is healthy except Fortress, Kerby and
Scimple where community involvement remains low. That is to say there is
important work that remains undone due to a low number of contributors. One
problem is a change in job status of one prominent member (of ApacheDS). He
has less time available to contribute. We are having discussions about this
and will continue to monitor going forward. The low community activity in
Fortress, Kerby and no activity (of any kind) in Scimple are a concern as
well.
## Membership Data:
Apache Directory was founded 2005-02-22 (15 years ago)
There are currently 58 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Radovan Semancik on 2018-09-28.
- No new committers. Last addition was Lothar Haeger on 2018-12-16.
## Project Activity:
Per sub-project:
- ApacheDS: low activity: A release was planned for last quarter but was
delayed due to the work not getting completed. The primary developer had a
change is job status which hampered progress in this project. Nevertheless,
a release (again) planned for this quarter. It is much needed and will
include LDAP API 2.0. One security issue, a timing issue, was reported to
the PMC. It was determined not to be a vulnerability.
- LDAP API: low activity. A GA release last November.
- Studio: low activity but being maintained. No new releases planned at
this time.
- Fortress: low activity. One release last December, included all of the
enhancements and bug fixes from 2019.
- Kerby: low activity: A release is being planned for this quarter.
- Mavibot: decent activity: Work is being done implementing transaction
support and improving the data structures.
- SCIMple: no activity: For the third quarter in a row, this project has been
dormant. The project members have again been contacted asking for status.
The PMC is weighing options of waiting more or recommending a move to the
attic.
## Community Health:
The concerns listed in issues above (low activity, community involvement,
availability) notwithstanding, activity has picked up a little bit during the
4Q 2019. Releases in both the LDAP API and Fortress. Overall the work being
done has increased as well. With 234% increase in commits and 75% increase in
committers. But, overall activity is still pretty low although the PMC is
diligent, fixes reported problems, helps users over the mailing list and
continues to plan new features and capabilities. The project is healthy and
actively being maintained. The are releases planned for 1Q for ApacheDS and
Kerby.
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification.
## Issues:
The activity level this past quarter was low. With the exception of Kerby
and Scimple (discussed below) the PMC is unconcerned, as periods of inactivty
are not unusual with this project. Members become busy with their day jobs
this time of year.
## Activity:
Per sub-project:
- ApacheDS: low activity:
ApacheDS is still in an intermediary state, due to stability problems with
its underlying database. This is a longstanding problem. The goal is to
complete the work on the new database, Mavibot. The project team is
committed to this important work, but it's a labor of love, and so sits on
the backburner. Other items addressed. Many tests were added to the test
suite and misc issues are being worked on and resolved. A review of the
Password Policy subsystem, working on outstanding issues, along with a
necessary change to the Change Password extended operation is underway. A
release is being planned for 4Q 2019.
- LDAP API: low activity but keeping up with security patches to libraries
and issues being reported to the community. A release is being planned for
4Q to roll the latest fixes out.
- Studio: low activity but this project has many users and is being
maintained. No new releases planned at this time.
- Fortress: low activity and also being maintained. Some work this past
quarter, add support for Java 11 and other misc feature requests. Release
scheduled for 4Q 2019 which will include upgrade to LDAP 2.0 API along with
rolling out the fixes/enhancements since its last release.
- Kerby: low activity: This project has quite a following. Over 1.8M
downloads a month via Maven during the past quarter. Project activity has
been dormant, which is a concern. The PMC is making inquiries into the
project team, to ensure it's being properly maintained going forward.
- Mavibot: no activity: As stated above, Mavibot is to be the new database
for ApacheDS. There is still much work to be done before it's usable.
This work is related to adding/improving transaction support and reclaiming
memory space. The project team is committed to doing the work.
- SCIMple: no activity: For the second quarter in a row, this project has
been dormant. The PMC has made contact with the project members to
determine viability. If it's determined to not be active, a vote will be
held to move into the attic.
## Health report:
Overall the project is healthy and actively being maintained. The are
releases planned for 4Q for ApacheDS, API and Fortress.
## PMC changes:
- Currently 19 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Radovan Semancik on Sat Sep 29 2018
## Committer base changes:
- Currently 58 committers.
- No new committers added in the last 3 months
- Lothar Haeger was added as a committer on Mon Dec 17 2018
## Releases:
No releases this quarter.
## Mailing list activity:
- Moderate activity, about the same as previous quarter.
## JIRA activity:
- 19 issues opened in JIRA, past quarter (-42% decrease)
- 4 issues closed in JIRA, past quarter (-96% decrease)
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely written in
Java, which has been certified LDAPv3 compatible by the Open Group. Besides
LDAP it supports Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API).
This is a "schema aware" API with some convenient ways to access all types
of LDAP servers.
- Studio: A complete directory tooling platform intended to be used with any
LDAP server however it is particularly designed for use with ApacheDS. It is
an Eclipse RCP application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and password policy
services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains various
tools to access and manage kerberos principals and keytabs. It provides a
rich, intuitive and interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2) as desired in modern
environments such as cloud, Hadoop and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
Per sub-project:
- ApacheDS: good activity: Lots of work being done clearing out JIRA tickets,
bugs and enhancements. New release being planned.
- LDAP API: good activity: Three releases over the past quarter addressing
security issues and new functionality along with significant performance
enhancements.
- Studio: low activity: New release planned after ApacheDS release.
- Fortress: low activity: Release 2.0.4 postponed to allow the LDAP API
releases to happen. Next steps, migrate to LDAP API 2.X, combine the four
git repos into one, remove ehcache.
- Kerby: no activity
- Mavibot: no activity
- SCIMple: no activity
## Health report:
Number of releases is low compared to previous quarters. However, there is
quite a bit of activity in LDAP API and ApacheDS. New releases are planned in
Fortress and ApacheDS that will take advantage of the new code being produced
by the API project.
The PMC feels the overall project is healthy. There is very low activity in
Kerby and Scimple which is a concern and will be monitored by the PMC.
## PMC changes:
- Currently 19 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Radovan Semancik on Sat Sep 29 2018
## Committer base changes:
- Currently 58 committers.
- No new committers added in the last 3 months
- Lothar Haeger was added as a committer on Mon Dec 17 2018
## Releases:
- Apache LDAP API 1.0.3 was released on Thu Apr 18 2019
- Apache LDAP API 2.0.0.AM3 was released on Tue May 14 2019
- Apache LDAP API 2.0.0.AM4 was released on Sat Jun 08 2019
## Mailing list activity:
- Moderate activity, about the same as previous quarter.
## JIRA activity:
- 32 JIRA tickets created in the last 3 months
- 139 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely written in
Java, which has been certified LDAPv3 compatible by the Open Group. Besides
LDAP it supports Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API).
This is a "schema aware" API with some convenient ways to access all types
of LDAP servers.
- Studio: A complete directory tooling platform intended to be used with any
LDAP server however it is particularly designed for use with ApacheDS. It is
an Eclipse RCP application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and password policy
services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains various
tools to access and manage kerberos principals and keytabs. It provides a
rich, intuitive and interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2) as desired in modern
environments such as cloud, Hadoop and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
Per sub-project:
- ApacheDS: good activity: New release being planned. Includes support for
transactions & improved handing of java keystores.
- LDAP API: good activity: Preparation of Release of 2.0.0-AM3. Refactoring of
code, signficant performance improvements.
- Studio: low activity: Improvements on connections and support for latest
version of eclipse framework.
- Fortress: good activity: Preparation of Release 2.0.4. New UI using ViewJS,
improved delegated admin. Talks at SCaLE17X & Apache Roadshow.
- Kerby: good activity: Release of 2.0.0.
- Mavibot: no activity
- SCIMple: low activity
## Health report:
Fewer releases than previous quarter but overall development activty is good.
Many important issues being worked on with several releases being planned
including ldap api, studio, apacheds and fortress.
The PMC feels the project is healthy.
## PMC changes:
- Currently 19 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Radovan Semancik on Sat Sep 29 2018
## Committer base changes:
- Currently 58 committers.
- No new committers added in the last 3 months
- Lothar Haeger was added as a committer on Mon Dec 17 2018
## Releases:
- Only one release but several are in the works (see above).
- Apache Kerby 2.0.0 was released on Sun Jan 13 2019
## Mailing list activity:
- Moderate activity, about the same as previous quarter.
- users@directory.apache.org: Currently: 315 subscribers (down -3 in the last
3 months) (23 emails sent in the past 3 months, 46 in the previous cycle)
- dev@directory.apache.org: Currently: 179 subscribers (down -1 in the last 3
months) (310 emails sent in the past 3 months, 393 in the previous cycle)
- api@directory.apache.org: Currently: 80 subscribers (down -3 in the last 3
months) (9 emails sent in the past 3 months, 2 in the previous cycle)
- fortress@directory.apache.org: Currently: 41 subscribers (up 1 in the last 3
months) (17 emails sent in the past 3 months, 30 in the previous cycle)
- kerby@directory.apache.org: Currently: 39 subscribers (up 0 in the last 3
months) (25 emails sent in the past 3 months, 15 in the previous cycle)
- scimple@directory.apache.org: Currently: 10 subscribers (up 1 in the last 3
months) (3 emails sent in the past 3 months, 0 in the previous cycle)
## JIRA activity:
- 33 JIRA tickets created in the last 3 months
- 18 JIRA tickets closed/resolved in the last 3 months
WHEREAS, the Board of Directors heretofore appointed Stefan Seelmann (seelmann) to the office of Vice President, Apache Directory, and WHEREAS, the Board of Directors is in receipt of the resignation of Stefan Seelmann from the office of Vice President, Apache Directory, and WHEREAS, the Project Management Committee of the Apache Directory project has chosen by vote to recommend Shawn McKinney (smckinney) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Stefan Seelmann is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Directory, and BE IT FURTHER RESOLVED, that Shawn McKinney be and hereby is appointed to the office of Vice President, Apache Directory, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Directory Project Chair, was approved by Unanimous Vote of the directors present.
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
Per sub-project:
- ApacheDS: low activity: Mostly changes due to LDAP API refactoring.
Nice contribution to upgrade cache library received.
Release planned.
- LDAP API: good activity: Heavy refactoring of request/response
encoding. Improvements in TLS certificate error handling.
Contribution to upgrade commons library received. Release
planned.
- Studio: good activity: Removal of JNDI abstraction layer and
bugfixes. Release planned.
- Fortress: good activity: Release of 2.0.3. Added JSON/REST
interface and started work on a new web UI.
- Kerby: low activity: Release preparations for 2.0.0 finished,
issues detected during vote are already resolved
- Mavibot: no activity
- SCIMple: low activity: Not much activity after code contribution
and inital release process discussion.
## Health report:
Overall development activity (commits, development related mails,
resolved issues, releases) was lower than previous quarter. There
is no specific reason, just less time developers could spend on
the project.
The new SCIMple sub-project didn't have a good start. After the
code contribution there was almost no activity from the initial
contributors. Instead two bugfix releases of the old project were
created. On the other hand new people are interested. All in all
not alarming yet, but the PMC needs to continue to give advice
and guidance to the new sub-project.
After long time a new committer was voted in.
In good old tradition the PMC decided to rotate the chairman, see
related resolution.
The PMC feels the project is healthy.
## PMC changes:
- Currently 19 PMC members.
- Last PMC addition was Radovan Semancik on Sat Sep 29 2018
## Committer base changes:
- Currently 58 committers.
- Lothar Haeger was added as a committer on Mon Dec 17 2018
## Releases:
- Apache Fortress 2.0.3: was released on Mon Nov 12 2018
## Mailing list activity:
- Lower activiy level than previous quarter.
## JIRA activity:
- 42 JIRA tickets created in the last 3 months
- 21 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
Per sub-project:
- ApacheDS: good activity: Release of 2.0.0.AM25. Code quality
improvements. Continued work on transaction support.
- LDAP API: good activity: Release of 2.0.0-AM1 and 2.0.0-AM2.
Cleanup in LDAP message encoding/decoding code.
- Studio: good activity: Release of 2.0.0-M14.
- Fortress: good activity: Release of 2.0.1 and 2.0.2. Talk at
ApacheCon NA.
- Kerby: good activity: More work on new "Hadoop Authentication
Service" and 2.0.0 release preparation.
- Mavibot: no activity
- SCIMple: good activity: IP clearence done. Discussion about
release process.
## Health report:
Overall development activity (commits, development related mails,
resolved issues, releases) was higher than previous quarter.
This is mainly caused by release activity and initial high pull
requests activity of the SCIMple sub-project.
The PMC feels the project is healthy.
## PMC changes:
- Currently 19 PMC members.
- Radovan Semancik was added to the PMC on Sat Sep 29 2018
- Last PMC addition was Radovan Semancik on Sat Sep 29 2018
## Committer base changes:
- Currently 57 committers.
- No new committers added in the last 3 months
- Last committer addition was Wei Zhou at Fri Sep 29 2017
## Releases:
- Apache LDAP API 2.0.0-AM1 was released on Thu Jul 19 2018
- Apache Fortress 2.0.1 was released on Fri Jul 20 2018
- ApacheDS 2.0.0.AM25 was released on Fri Aug 17 2018
- Apache Directory Studio 2.0.0-M14 was released on Sat Sep 08 2018
- Apache Fortress 2.0.2 was released on Wed Sep 12 2018
- Apache LDAP API 2.0.0-AM2 was released on Sun Sep 02 2018
## Mailing list activity:
- Higher activiy level than previous quarter, see health report
above.
## JIRA activity:
- 45 JIRA tickets created in the last 3 months
- 46 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
- SCIMple: An implementation of SCIM v2.0 specification. (new)
## Issues:
- there are no issues requiring board attention at this time
## Activity:
General:
- We had to deal with a vulnerability in LDAP API 1.0.0 which took
quite some effort and slowed down other work.
- We have a new sub-project SCIMple. It was accepted long time ago
but paperwork took some time. It replaces eSCIMo which will be
moved to attic.
- Discussion about how to deal with Java 9/10/11
Per sub-project:
- ApacheDS: low activity: Mainly updates due to changes in LDAP API.
- LDAP API: good activity: Release of 1.0.2 (security fix).
Improvements in error logging and reporting. Preparation
for first 2.0 release canditate was re-started.
- Studio: low activity: Mainly updates due to changes in LDAP API.
- Fortress: good activity: Added support for HA and RFC2307 BIS.
General dependency updates. Vote for 2.0.1 started.
- Kerby: good activity: More work on new "Hadoop Authentication
Service" and some bugfixes. 1.1.1 was released and
2.0.0 release is planned.
- Mavibot: no activity
- SCIMple: good activity: Initial code import, IP clearance ongoing.
## Health report:
Overall development activity (commits, development related mails,
resolved issues, releases) was similar to previous quarter.
In general there is good activity and release planning across
all sub-projects.
The PMC feels the project is still healthy.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Chris Pike on Wed Nov 23 2016
## Committer base changes:
- Currently 57 committers.
- No new committers added in the last 3 months
- Last committer addition was Wei Zhou at Fri Sep 29 2017
## Releases:
- Apache Kerby 1.1.1 was released on Fri May 25 2018
- Apache LDAP API 1.0.2 was released on Wed Jun 06 2018
## Mailing list activity:
- Same activity level as previous quarter
## JIRA activity:
- 38 JIRA tickets created in the last 3 months
- 40 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
Per sub-project:
- ApacheDS: good activity: Transaction support added.
- LDAP API: good activity: Release preparation started
- Studio: good activity: Release to fix Java 9/10 issues planned
- Fortress: low activity
- Kerby: good activity: More work on new "Hadoop Authentication
Service" and some bugfixes. Discussion about next release.
- Mavibot: no activity
## Health report:
Overall develomment activity (commits, development related mails,
resolved issues, releases) was similar to previous quarter.
There are some new contributors which should be considered
for committership if they stay active.
The PMC feels the project is still healthy.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Chris Pike on Wed Nov 23 2016
## Committer base changes:
- Currently 57 committers.
- No new committers added in the last 3 months
- Last committer addition was Wei Zhou at Fri Sep 29 2017
## Releases:
- No release in the last 3 months
- Apache Kerby 1.1.0 was released on Mon Nov 27 2017
## Mailing list activity:
- Same activiy level then previous quarter
## JIRA activity:
- 61 JIRA tickets created in the last 3 months
- 49 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
## Issues:
- there are no issues requiring board attention at this time"
## Activity:
General:
- Finished migration for most projects from SVN to Git/GitBox
- Ongoing search to strengthen the committer pool and the PMC
Per sub-project:
- ApacheDS: low activity
- LDAP API: low activity
- Studio: low activity
- Fortress: low activity
- Kerby: good activity: Relase of version 1.1.0. Started integration
on new "Hadoop Authentication Service" (DIRKRB-671).
- Mavibot: good activity
## Health report:
Overall develomment activity (commits, development related mails,
resolved issues, releases) was lower than last quarter.
The PMC feels the project is still healthy.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Chris Pike on Wed Nov 23 2016
## Committer base changes:
- Currently 57 committers.
- No new committers added in the last 3 months
- Last committer addition was Wei Zhou at Fri Sep 29 2017
## Releases:
- Apache Kerby 1.1.0 was released on Mon Nov 27 2017
## Mailing list activity:
- Same activiy level then previous quarter
## JIRA activity:
- 43 JIRA tickets created in the last 3 months
- 41 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
## Issues:
In response to previous report:
rb: There's a huge gap between your committer and PMC member counts.
Is there any chance that some of those 55 committers might be
good additions to the PMC?
We discussed this on the private ML, but there was no obvious candidate. In
general we promote people to PMC 6 month after they became committer if they
remain active.
## Activity:
General:
- We decided to move more projects to Git/GitBox
Per sub-project activity:
- ApacheDS: Low activity
- LDAP API: Low activity: Migrated repo to GitBox
- Studio: Good activity: Release of version 2.0.0-M13
- Fortress: Low activity
- Kerby: Good activity: Relase of version 1.0.1
- Mavibot: Good activity: Work on transaction support and caching
## Health report:
Overall develomment activity (commits, development related mails, resolved
issues, releases) was lower than last quarter. Two new committers were added
who contribute to Kerby. One user shows interest to contribute to Studio. 2
releases were published. The project is healthy.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Chris Pike on Wed Nov 23 2016
## Committer base changes:
- Currently 57 committers.
- Wei Zhou was added as a committer on Fri Sep 29 2017
- Frank Zeng was added as a committer on Fri Sep 29 2017
## Releases:
- Kerby: 1.0.1 was released on Mon Sep 04 2017
- Studio: 2.0.0-M13 was released on Mon Sep 04 2017
- Fortress: last release 2.0.0 on 2017-07-07
- LDAP API: last release 1.0.0 on 2017-06-07
- ApacheDS: last release 2.0.0-M24 on 2017-06-07
- Mavibot: last release 1.0.0-M8 on 2015-08-15
## Mailing list activity:
- Lower activiy then previous quarter
## JIRA activity:
- 52 JIRA tickets created in the last 3 months
- 33 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
General:
- We decided to move all projects to Java 8
Per sub-project activity:
- ApacheDS: Good activity
- LDAP API: High activity: Version 1.0.0 release, discussion about
2.0.0 roadmap, repository will be migrated to Git
- Studio: Low activity: Bugfix release planned
- Fortress: Good activity: Release of version 2.0.0
- Kerby: High activity: Relase of version 1.0.0, work on GSSAPI,
improvements in kinit and kadmin tools
- Mavibot: Low activity, but a talk at LDAPCon was accepted
## Health report:
Overall develomment activity (commits, development related mails,
resolved issues, releases) was higher than last quater. Two new
committers were added. 4 release were published. The project is
healthy.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Chris Pike on Wed Nov 23 2016
## Committer base changes:
- Currently 55 committers.
- Yudhi Karunia Surtan was added as a committer on Mon May 29 2017
- Brian Burch was added as a commiter end of April 2017
## Releases:
- Apache Directory Fortress 2.0.0 was released on Fri Jul 07 2017
- Apache Kerby 1.0.0 was released on Sat May 13 2017
- Apache LDAP API 1.0.0 was released on Wed Jun 07 2017
- ApacheDS 2.0.0-M24 was released on Wed Jun 07 2017
- Studio: Last release 2.0.0.v20161101-M12 on 2016-11-01
- Mavibot: Last release 1.0.0-M8 on 2015-08-15
## Mailing list activity:
- Higher activiy then previous quater
- Peak on kerby@d.a.o due to release activity
## JIRA activity:
- 52 JIRA tickets created in the last 3 months
- 43 JIRA tickets closed/resolved in the last 3 months
No report was submitted.
@Rich: pursue a report for Directory
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
- eSCIMo: An implementation of SCIM (System for Cross-domain
Identity Management).
## Issues:
In response to previous report:
mt: I was expecting to see some reference to the Groovy LDAP API in
this report. Please include a brief summary in your next report.
On 2016-06-28 a security vulnerability in the "Groovy LDAP API" has
been reported. The "Groovy LDAP API" was never officially released,
it was a PoC and there was no further development after 2012. However
it somehow happened that a project page and a zip archive existed.
The page stated "We do not know, whether it will become an official
project with releases and so (no official release yet)". The version
within the "groovy-ldap.zip" file was 0.1-SNAPHSOT. The following
actions were taken:
- The zip archived was removed from the website
- The "Groovy LDAP" website was completely removed
- The vulnerable source code was fixed
- The vulnerability was published to our users and dev mailing lists
The Directory PMC does not plan to release the "Groovy LDAP API". The
source will be kept in Subversion for reference.
## Activity:
General:
- We had a discussion about moving all projects to Java 8.
- A project blog was started at https://blogs.apache.org/directory/
Per sub-project activity:
- ApacheDS: Low activity: Mainly bugfixes
- LDAP API: Good activity: Bugfixes, work on immutable schema,
and update of documentation. Towards a 1.0.0 release.
- Studio: Medium activity: Upgrade to Java 8 and bugfixes
- Fortress: Low activity
- Kerby: Low activity
- Mavibot: Good activity: Work on transaction support
- eSCIMo: Zero activity
## Health report:
Overall develomment activity (commits, development related mails,
resolved issues, releases) is lower than last quarter. This is
probably due to lack of time, but also due to low number of active
developers.
On the other hand activity on user mailing lists increased.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Chris Pike on Wed Nov 23 2016
## Committer base changes:
- Currently 53 committers.
- No new committers added in the last 3 months
- Last committer addition was Alex Haskell at Wed Aug 03 2016
## Releases:
- No release this quarter
- ApacheDS: Last release 2.0.0-M23 on 2016-07-21
- LDAP API: Last release 1.0.0-RC2 on 2016-10-31
- Studio: Last release 2.0.0.v20161101-M12 on 2016-11-01
- Fortress: Last release 2.0.0-RC1 on 2016-11-06
- Kerby: Last release 1.0.0-RC2 on 2016-03-11
- Mavibot: Last release 1.0.0-M8 on 2015-08-15
- eSCIMo: No release yet
## Mailing list activity:
- Slight increase of subscribers
- In general less mails than in previous quarter
## JIRA activity:
- 34 JIRA tickets created in the last 3 months
- 17 JIRA tickets closed/resolved in the last 3 months
WHEREAS, the Board of Directors heretofore appointed Kiran Ayyagari (kayyagari) to the office of Vice President, Apache Directory, and WHEREAS, the Board of Directors is in receipt of the resignation of Kiran Ayyagari (kayyagari) from the office of Vice President, Apache Directory, and WHEREAS, the Project Management Committee of the Apache Directory project has chosen by vote to recommend Stefan Seelmann (seelmann) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Kiran Ayyagari is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Directory, and BE IT FURTHER RESOLVED, that Stefan Seelmann be and hereby is appointed to the office of Vice President, Apache Directory, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7D, Change the Apache Directory Project Chair, was approved by Unanimous Vote of the directors present.
Current Activity and Status --------------------------- In the last quarter 1 new PMC member was added. Stefan Seelmann has been voted as the new PMC chair, resolution was sent to board for approval. ------------------------- Detailed Information ------------------ ### Community No new committers (last addition: August 2016) One new PMC member was added (last addition: November 2016) - Chris Pike ## Projects Note: Unless otherwise specified all projects are implemented in pure Java. ### Apache Directory Server ApacheDS is an extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group ###### Mailing list subscriber info - Users mailing list: 323 subscribers (+19) - Development mailing list: 190 subscribers (+15) ###### Development and Releases - No new releases (last release was on 22nd July, 2016) - A lot of code documentation was reviewed and modified ### Apache Directory LDAP API The Apache Directory LDAP API is an ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware" API with some convenient ways to access all types of LDAP servers, not only ApacheDS but any LDAP server ###### Mailing list subscriber info - 73 subscribers (+1) ###### Development and Releases - New version 1.0.0-RC2 was released on 31st Oct, 2016 - A lot of code documentation was reviewed and modified ### Apache Directory Studio Apache Directory Studio is a complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins, that can be easily upgraded with additional ones. These plugins can even run within Eclipse itself ###### Development and Releases - New version 2.0.0.v20161101-M12 was released on 1st Nov, 2016 ### Apache Fortress Apache Fortress is a standards-based access management system that provides role-based access control, delegated administration and password policy services with an LDAP backend. ###### Development and Releases - New version 2.0.0-RC1 was released on 6th Nov, 2016 ###### Mailing list subscriber info - 35 subscribers (+3) ### Apache Kerby An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. ###### Development and Releases - Low activity - No new releases ###### Mailing list subscriber info - 31 subscribers (+4) ### Apache Mavibot An embeddable key-value database library with Multi-version Concurrency support ###### Development and Releases - Low activity - No new releases ### Apache eSCIMo An implementation of SCIM(System for Cross-domain Identity Management) protocol version 1. ###### Development and Releases - Nil activity - No releases yet - Will be replaced with the code from newly accepted project, SCIMple-Identity, from Penn State University. This is still pending as of now.
Current Activity and Status --------------------------- In the last quarter 5 committers were added. PMC voted to accept SCIMple-Identity as a sub-project. ------------------------- Detailed Information ------------------ # Community Five new committers (last addition: August 2016) - Alex Haskell - Christopher Harm - Richard Feezel - Steve Moyer - Shawn E Smith No new PMC members (last addition: May 2016) # Projects Note: Unless otherwise specified all projects are implemented in pure Java. ## Apache Directory Server ApacheDS is an extensible and embeddable directory server entirely written in Java, which has been certified LDAPv3 compatible by the Open Group ### Mailing list subscriber info - Users mailing list: 304 subscribers (+2) - Development mailing list: 175 subscribers (+0) ### Development and Releases - Version 2.0.0-M23 was released on 22nd July, 2016 ## Apache Directory LDAP API The Apache Directory LDAP API is an ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a "schema aware" API with some convenient ways to access all types of LDAP servers, not only ApacheDS but any LDAP server ### Mailing list subscriber info - 72 subscribers (+4) ### Development and Releases - Low activity - No new releases, switched to RC state in the last release and preparing to release a GA soon - Bug fixes and improvements ## Apache Directory Studio Apache Directory Studio is a complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins, that can be easily upgraded with additional ones. These plugins can even run within Eclipse itself ### Development and Releases - Low activity - No new releases. The latest attempt to cut a release was halted due to a bug in the installer generation script ## Apache Fortress Apache Fortress is a standards-based access management system that provides role-based access control, delegated administration and password policy services with an LDAP backend. ### Development and Releases - Very high activity - Version 1.0.1 was released on 22nd, July 2016 ### Mailing list subscriber info - 32 subscribers (+1) ## Apache Kerby An implementation of Kerberos v5 protocol and contains various tools to access and manage kerberos principals and keytabs. It provides a rich, intuitive and interoperable implementation, library, KDC and various facilities that integrates PKI, OTP and token (OAuth2) as desired in modern environments such as cloud, Hadoop and mobile. ### Development and Releases - Low activity - No new releases ### Mailing list subscriber info - 27 subscribers (-1) ## Apache Mavibot An embeddable key-value database library with Multi-version Concurrency support ### Development and Releases - Low activity - No new releases ## Apache eSCIMo An implementation of SCIM(System for Cross-domain Identity Management) protocol version 1. ### Development and Releases - Nil activity - No releases yet - Will be replaced with the code from newlyaccepted project, SCIMple-Identity, from Penn State University
Directory Quarterly Report - July 2016 Current Activity and Status --------------------------- In the last quarter one new committer and one new PMC members were added A project from Penn State University has been accepted as a sub project of Apache Directory project. This is an implementation of SCIM( http://simplecloud.info/) protocol. Three contributors of this project have been accepted by the PMC to become committers and they have been invited. The refactoring work on Directory Server codebase that was reported in the previous report has been succefully completed and these changes will be released in the next major version. Three projects had their new versions released in this quarter. ------------------------- Detailed Information ------------------ -- Community -- * One new committer (last addition: January 2016) * Gerard Gagliano * One new PMC member (last addition: November 2015) * Jiajia Li * Mailing lists: * Users mailing list: 304 subscribers (+2) * Development mailing list: 175 subscribers (+0) * API mailing list: 68 subscribers (-5) * Fortress mailing list: 31 subscribers (+3) * Kerby mailing list: 28 subscribers (+3) -- Current activity -- * Apache Directory LDAP API: * One new releases. * Good activity * Bug fixes and improvements. * Apache Mavibot: * No new releases. * Low activity * ApacheDS: * One new release. * High activity. * Apache Directory Studio: * No new release. * Good activity owing to a new release preparation. * Apache eSCIMo: * Nil activity. * No releases yet. * Likely to be replaced with the code from newly accepted project from Penn State University * Fortress: * No new releases. * Low activity. * Apache Kerby: * No new releases. * Good activity. -- Releases -- * One new release for Apache Directory Server * 2.0.0-M22 (June 28th, 2016) * One new release for Apache LDAP API * 1.0.0-RC1 (June 17th, 2016) * One new release for Apache Directory Fortress * 1.0.0 (April 15th, 2016) * No releases for Apache Directory Studio, Mavibot, Kerby and eSCIMo
Current Activity and Status --------------------------- In the last quarter two new committers were added and new versions of two sub-projects were released. A major refactoring work is happening in the ApacheDS project at the moment and Fortress sub-project is being prepared for a general release. There is very little activity in the remaining sub-projects. ------------------------- Detailed Information ------------------ -- Community -- * Two new committers (last addition: Aug 2015) * Chris Pike * Jan Sindberg * No new PMC members (last addition: November 2015) * Mailing lists: * Users mailing list: 302 subscribers (+1) * Development mailing list: 175 subscribers (+2) * API mailing list: 73 subscribers (+2) * Fortress mailing list: 28 subscribers (+1) * Kerby mailing list: 25 subscribers (+2) -- Current activity -- * Apache Directory LDAP API: * No new releases. * Low activity * Mainly bug fixes. * Apache Mavibot: * No new releases. * Low activity * ApacheDS: * No new release. * High activity. * Apache Directory Studio: * One new release. * Low activity. * Apache eSCIMo: * Nil activity. * No releases yet. * Fortress: * One new releases. * Good activity. * Apache Kerby: * One new releases. * Good activity. -- Releases -- * One new releases for Apache Directory Fortress * 1.0-RC42 (March 24th, 2016) * One new releases for Apache Kerby * 1.0.0-RC2 (March 13th, 2016) * No releases for Apache Directory LDAP API, Server, Studio, Mavibot and eSCIMo
In the last quarter two new PMC members were added and 4 new versions of various sub-projects were released. Voting is currently going on for adding one more committer. Work is still going on to support cross-BTree transactions in Mavibot and the project Kerby's source code is being peer reviewed. A security issue(CVE-2015-5349) affecting Apache Directory Studio was fixed and a new version of Studio was released. --- Detailed Information --- -- Community -- * No new committer (last previous addition: Aug 2015) * Two new PMC members (last previous addition: April 2015) * Colm O hEigeartaigh * Kai Zheng * Mailing lists: * Users mailing list: 301 subscribers (+6) * Development mailing list: 173 subscribers (+1) * API mailing list: 71 subscribers (+2) * Fortress mailing list: 27 subscribers (+4) * Kerby mailing list: 23 subscribers (+7) -- Current activity -- * Apache Directory LDAP API: * Two new releases. * Good activity * Mainly bug fixes. * Apache Mavibot: * No new releases. * Low activity * Work is going on for supporting cross-BTree transactions. * ApacheDS: * One new release. * Low activity. * Apache Directory Studio: * One new release. * Good activity. * Apache eSCIMo: * Nil activity. * No releases yet. * Fortress: * No new releases. * Low activity. * Apache Kerby: * No new releases. * Good activity, code reviewe in progress. -- Releases -- * Two releases for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M32 (October 19th 2015) * Apache Directory LDAP API 1.0.0-M33 (December 21st 2015) * One release for Directory Server: * Apache Directory Server 2.0.0-M21 (December 21st 2015) * One release for Directory Studio: * Apache Directory Studio 2.0.0.v20151221-M10 (January 2nd 2016) * No releases for Apache Mavibot, Apache Kerby, Fortress and eSCIMo
Current Activity and Status --------------------------- The last quarter was mainly focused on releasing the first version of Kerby. A new version of the LDAP API release was discussed and in the preparation to it there is some bug fixing going on. We have received an offer to contribute RADIUS software built on top of ApacheDS, we are still evaluating this offer. We are thinking of adding two more members to the PMC, the vote is not started yet. There were three presentations in the recently concluded ApacheConCore EU, one each on Fortress, Kerby and ApacheDS projects. The default JDBM backend used by ApacheDS is causing data corruption problems. We are seeing a lot of users complaining about it in the recent weeks. Though we have suggested some workarounds this remains our top priority to fix the issue by replacing JDBM with the new MVCC backend library, Mavibot. Currently work is going on to support cross-BTree transactions in Mavibot. ------------------------- Detailed Information ------------------ -- Community -- One new committer (last previous addition: May 2015) * Yaning Xu No new PMC member (last previous addition: April 2015). Mailing lists: * Users mailing list: 295 subscribers (-2) * Development mailing list: 172 subscribers (-5) * API mailing list: 69 subscribers (-1) * Fortress mailing list: 23 subscribers (+3) * Kerby mailing list: 16 subscribers (+3) -- Current activity -- Apache Directory LDAP API: * No new releases. * Good activity * Mainly bug fixes. Apache Mavibot: * One new release. * Low activity * Many smaller fixes. * Work started on supporting cross-BTree transactions. ApacheDS: * No new releases. * Low activity. Apache Directory Studio: * One release during this quarter. * Good activity. * Work in progress on OpenLDAP configuration editor. Apache eSCIMo: * Nil activity. * No releases yet. Fortress: * No new releases. * Low activity. Apache Kerby: * One new release. * Good activity -- Releases -- * One release for Apache Mavibot: * Apache Mavibot 1.0.0-M8 (August 16th 2015) * One release for Apache Kerby: * Apache Kerby 1.0.0-RC1 (September 16th 2015) * No releases for Apache Directory LDAP API, Directory Server, Studio, Fortress and eSCIMo
Current Activity and Status --------------------------- The last quarter was mainly focused on Studio and especially on completing the migration to the new build system. The OpenLDAP configuration editor has been greatly improved and is still in progress. There is an increased activity on Kerby mailing list and development is going at a fast pace with a clearly defined roadmap. At present we have a working server with support for many preauth mechanisms and gearing towards its first release. The Mavibot(an MVCC BTree library) project is also under active development, now it has complete support for reusing free pages and version 1.0.0-M8 will be released soon. We are actively communicating about Apache Directory project through twitter (https://twitter.com/apacheds). The follower base is growing every month, currently it stands at 61. ------------------------- Detailed Information ------------------ -- Community -- * One new committer (last previous addition: March 2015) * Jiajia Li * One new PMC member (last previous addition: April 2015). * Shawn McKinney * Mailing lists: * Users mailing list: 297 subscribers (+0) * Development mailing list: 177 subscribers (+2) * API mailing list: 70 subscribers (+2) * Fortress mailing list: 20 subscribers (+1) * Kerby mailing list: 11 subscribers (+11) -- Current activity -- * Apache Directory LDAP API: * Two releases during this quarter. * Good activity * Mainly bug fixes. * Apache Mavibot: * No new releases. * Good activity * Many smaller fixes. * Work on freepage management completed. * ApacheDS: * One release during this quarter. * Low activity. * Apache Directory Studio: * One release during this quarter. * Good activity. * Work in progress on OpenLDAP configuration editor. * Apache eSCIMo: * Nil activity. * No releases yet. * Fortress: * One release during this quarter. * Low activity. * Apache Kerby: * Good activity * No releases yet. -- Releases -- * Two releases for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M30 (May 4th 2015) and 1.0.0-M31 (July 5th 2015) * One release for Apache Directory Server: * Apache Directory Server 2.0.0-M20 (May 4th 2015) * One release for Apache Directory Studio: * Apache Directory Studio 2.0.0-M9 (June 13th 2015) * One release for Apache Fortress: * Apache Fortress 1.0-RC40 (April 16th 2015) * No releases for Apache Mavibot, eSCIMo and Kerby.
I have been elected as the new Chairman of the project. I have been contributing to Directory project since January, 2008. I thank my mentors and PMC for entrusting me with this duty. Current Activity and Status --------------------------- The last three quarters have seen an increased activity on almost all of the Directory projects. After years of stable number of committers and PMC members, we have added 5 new committers (all of them active) and 2 new PMC members (and we are thinking about voting another in) From the project point of view, we are still moving forward with stable releases, but released as milestones. Hopefully, we can expect an RC for the LDAP API soon, a couple of more milestone for Mavibot, followed by an RC for ApacheDS. At the same time, we are cutting the first RC for Fortress, which was added as a sub-project last September. The release is currently blocked by a problem with Nexus, but that should be solved quickly. We do think that the new Kerberos server (Kerby) will be better than the current implementation we have, and the goal is to simply replace what we have with the new code. At the same time, we will most certainly benefit from some of the modules of this project, like the new ASN.1 codec, for ApacheDS. In the similar fashion, Kerby might benefit from a stable version of Mavibot. Studio is expecting to be released soon too. A new build system is put in place, which lead to a lot of modifications. At the same time, many additional plugins have been injected (template editor, OpenLDAP configuration editor, and we also have a new contribution for an eDirectory configuration editor). There is an increased activity on the user and developer mailing lists. We are quite happy with the recent evolution of the project! ------------------------- Detailed Information ------------------ -- Community -- * One new committer (last previous addition: Feb 2015): * Radovan Semancik * One new PMC member (last previous addition: October 2014). * Pierre Smits * Mailing lists: * Users mailing list: 297 subscribers (+4) * Development mailing list: 175 subscribers (+4) * API mailing list: 68 subscribers (-2) * Fortress mailing list: 19 subscribers (+2) -- Current activity -- * Apache Directory LDAP API: * One release during this quarter. * Good activity * Mainly bug fixes and improvements in schema loaders. * Apache Mavibot: * One release during this quarter. * Good activity * Many smaller fixes. * Work in progress on the freepage management. * ApacheDS: * No new releases during this quarter. * Low activity. * Apache Directory Studio: * No releases during this quarter. * Good activity. * Added support for editing OpenLDAP configuration. * Added template editor. * Apache eSCIMo: * Low activity. * No releases yet. * Fortress: * Good activity preparing for releasing the first version. * Apache Kerby: * Good activity * No releases yet. -- Releases -- * One release for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M29 (March 30th 2015) * One release for Apache Mavibot: * Apache Mavibot 1.0.0-M7 (March 27th 2015) * No releases for ApacheDS: * No releases for Apache Directory Studio. * No releases for Apache eSCIMo, Fortress and Kerby.
WHEREAS, the Board of Directors heretofore appointed Pierre-Arnaud Marcelot to the office of Vice President, Apache Directory, and WHEREAS, the Board of Directors is in receipt of the resignation of Pierre-Arnaud Marcelot from the office of Vice President, Apache Directory, and WHEREAS, the Project Management Committee of the Apache Directory project has chosen by vote to recommend Kiran Ayyagari as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Pierre-Arnaud Marcelot is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Directory, and BE IT FURTHER RESOLVED, that Kiran Ayyagari be and hereby is appointed to the office of Vice President, Apache Directory, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7C, Resolution to Change the Apache Directory Chair, was approved by Unanimous Vote of the directors present.
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAPv3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * Kiran Ayyagari has been voted as new Apache Directory Chair. * Three new committers voted (last previous addition: October 2014): * Colm O hEigeartaigh * Kai Zheng * Lin Chen * No new PMC member voted (last previous addition: October 2014). * Mailing lists: * Users mailing list: 292 subscribers * Development mailing list: 173 subscribers * API mailing list: 69 subscribers * Fortress mailing list: 19 subscribers -- Current activity -- * Apache Directory LDAP API: * Four releases during this quarter. * Good activity * Mainly bug fixes. * Apache Mavibot: * One release during this quarter. * Good activity * Many smaller fixes. * Work in progress on the bulk-loader and freepage management. * ApacheDS: * Two releases during this quarter. * Mainly bug fixes and an important fix to remove support for SSLv3. * Apache Directory Studio: * No releases during this quarter. * Build system was migrated from Maven to Tycho. * Apache eSCIMo: * Low activity. * No releases yet. * Fortress: * IP clearance for the project has been completed and the source code has been brought to the Directory Git repository. * The project now has its dedicated website, mailing list and Jira space. * No releases yet, but a first release is currently being processed. * Apache Kerby: * IP clearance for the project is currently being processed and the source code has been brought to the Directory Git repository. * Good activity * No releases yet. -- Releases -- * Four release for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M25 (November 11th 2014) * Apache Directory LDAP API 1.0.0-M26 (November 22nd 2014) * Apache Directory LDAP API 1.0.0-M27 (December 29th 2014) * Apache Directory LDAP API 1.0.0-M28 (January 15th 2015) * One release for Apache Mavibot: * Apache Mavibot 1.0.0-M6 (November 16th 2014) * Two releases for ApacheDS: * ApacheDS 2.0.0-M18 (November 13th 2014) * ApacheDS 2.0.0-M19 (November 22th 2014) * No releases for Apache Directory Studio. * No releases for Apache eSCIMo, Fortress and Kerby.
No report was submitted.
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAPv3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * Two new committers voted (last previous addition: January 2014) * Pierre Smits * Shawn McKinney * One new PMC member voted (last previous addition: October 2008) * Lucas Theisen (lucastheisen) Invitations and paperwork for all three new committers and PMC Members are currently being handled. -- Current activity -- * Apache Directory LDAP API: * One release during this quarter. * Mainly bug fixes. * Apache Mavibot: * No releases during this quarter. * Good activity * Work focused on a bulk-loader functionality and free pages management. * ApacheDS: * No releases during this quarter. * Mainly bug fixes * Apache Directory Studio: * No releases during this quarter. * Work has begun on migrating our build system to use Tycho for our Eclipse plugins. * Apache eSCIMo: * Low activity * No releases yet. * Fortress: * The Fortress open source project (http://iamfortress.org/overview) offered to donate its source code to Apache Directory. * Fortress is a standards-based and open source IAM system that provides ANSI RBAC (INCITS 359) management and enforcement capabilities to networked applications and systems. * The inclusion of the Fortress code under the Apache Directory umbrella has been voted and accepted by the PMC. * IP clearance for the project is currently being processed. Once completed the source code will be brought to the Directory SVN repository. * One of Fortress' main contributor, Shawn McKinney, has been voted as a committer. -- Releases -- * One release for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M24 (July 4th 2014) * No releases for Apache Mavibot. * No releases for ApacheDS. * No releases for Apache Directory Studio. * No releases for Apache eSCIMo. -- Comment for the Board on a question on our previous Board report -- Greg Stein and the Board asked us about the lack of new PMC Members over the last six years (since October 2008). The good news is that we have one new PMC Member (Lucas Theisen) to report this quarter. Lucas, who was invited as a committer in January, has proven to be a valuable member for the project.
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAPv3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers(last addition: January 2014) * No new PMC members (last addition: October 2008) -- Current activity -- * Apache Directory LDAP API: * One releases during this quarter. * Good activity * Small bug fixes and improvements. * Apache Mavibot: * One release during this quarter. * Good activity * Speed improvements. * Partial support of a bulk load feature. * ApacheDS: * One release during this quarter. * Good activity. * Major fixes around Kerberos, restart issues & minor bug fixes. * Apache Directory Studio: * No releases during this quarter. * Low activity * Mainly bug fixes. * Apache eSCIMo: * Low activity * No releases yet. -- Releases -- * One release for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M23 (July 4th 2014) * One release for Apache Mavibot: * Apache Mavibot 1.0.0-M5 (July 4th 2014) * One release for ApacheDS: * ApacheDS 1.0.0-M17 (July 4th 2014) * No releases for Apache Directory Studio. * No releases for Apache eSCIMo.
@Greg: Six years seems too long between additions to the PMC.
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAPv3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers(last addition: January 2014) * No new PMC members (last addition: October 2008) * Mailing lists information: * users@directory: 279 subscribers (278 in january) * api@directory: 65 subscribers (62 in january) * dev@directory: 178 subscribers (173 in january) -- Current activity -- * Apache Directory LDAP API: * Two releases during this quarter. * Good activity * Refactoring of extended operations system and implementation of the WhoAmI extended operation. * Additions of more controls (Server Side Sorting, DirSync). * Apache Mavibot: * One release during this quarter. * Good activity * Improved performances. * Partial support of transactions coming soon. * Apache Escimo: * Low activity * No releases yet. * ApacheDS: * One release during this quarter. * Good activity. * Major fixes around Kerberos & minor bug fixes. * Apache Directory Studio: * No releases during this quarter. * Bug fixes. * Preparation for a release scheduled next quarter -- Releases -- * Two releases for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M21 (March 13th 2014) * Apache Directory LDAP API 1.0.0-M22 (April 22th 2014) * One release for Apache Mavibot: * Apache Mavibot 1.0.0-M4 (March 13th 2014) * No releases for Apache Escimo. * One releases for ApacheDS: * ApacheDS 1.0.0-M16 (March 13th 2014) * No releases for Apache Directory Studio.
No report was submitted.
AI: Shane to pursue a report for Directory
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAPv3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * One new committer has been voted, Lucas Theisen. (last previous addition: July 2012) * No new PMC members (last addition: October 2008) * Mailing lists information: * users@directory: 278 subscribers (240 a year ago) * api@directory: 62 subscribers (49 a year ago) * dev@directory: 173 subscribers (170 a year ago) -- Current activity -- * Apache Directory LDAP API: * No releases during this quarter. * Low activity / Very minor bug fixes. * Apache Mavibot: * Two releases during this quarter. * Major refactorings to the managed and in-memory btrees. Shared the cache system between btrees. Increased performance by making sure we only deserialize the required keys and values. * Apache Escimo: * The project has been listed as an experimental SCIM 2.0 implementation on the official SCIM website. * No releases yet. * ApacheDS: * No releases during this quarter. * Good activity. * Improved the integration of Apache Mavibot as a usable (and much faster) backend for ApacheDS. * Apache Directory Studio: * No releases during this quarter. * Low activity / Very minor bug fixes. -- Releases -- * No releases for Apache Directory LDAP API. * Two release for Apache Mavibot: * Apache Mavibot 1.0.0-M2 (November 6th 2013) * Apache Mavibot 1.0.0-M3 (December 16th 2013) * No releases for Apache Escimo. * No releases for ApacheDS. * No releases for Apache Directory Studio.
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAPv3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers (last addition: July 2012) * No new PMC members (last addition: October 2008) * Mavibot, a project that started in the Labs, is now a sub-project of the Apache Directory project. Apache Mavibot is a Multi Version Concurrency Control (MVCC) BTree implementation in Java. It is expected to be a replacement for JDBM (the current backend for ApacheDS), but could be a good fit for any other project in need of a Java MVCC BTree implementation. * Escimo is also a new sub-project of the Apache Directory project. Apache Escimo is a SCIM v2 protocol implementation in Java. -- Current activity -- * Apache Directory LDAP API: * One release during this quarter. * Low activity / Very minor bug fixes. * Apache Mavibot: * Voted as an Apache Directory sub-project on August 3rd 2013 (from the Apache Labs). * One release during this quarter. * Apache Escimo: * Created as an Apache Directory sub-project on July 7th 2013. * No releases yet. * ApacheDS: * One release during this quarter. * Good activity. * Integrated Apache Mavibot as a usable backend for ApacheDS (in addition to JDBM) * Apache Directory Studio: * No releases during this quarter. * A new release is pending on a new version of ApacheDS. * Low activity / Very minor bug fixes. -- Releases -- * One release for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M20 (August 18th 2013) * One release for Apache Mavibot: * Apache Mavibot 1.0.0-M1 (August 6th 2013) * No releases for Apache Escimo. * One release for ApacheDS: * ApacheDS 2.0.0-M15 (August 18th 2013) * No releases for Apache Directory Studio.
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAPv3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers * No new PMC members -- Current activity -- * Apache Directory LDAP API: * Three releases during this quarter. * Low activity * Very minor bug fixes. * ApacheDS: * Three releases during this quarter. * Good activity * Improved stability and fixed major issues related to corrupted backend. * Apache Directory Studio: * Two new releases during this quarter. * Good activity * Integration and support of the latest version of the Apache Directory LDAP API and ApacheDS * Added the ability to store connection passwords in a password-protected keystore * Improved existing value editors (Password & Hex editors) + minor bug fixes -- Releases -- * Three releases for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M17 (May 2nd 2013) * Apache Directory LDAP API 1.0.0-M18 (June 25th 2013) * Apache Directory LDAP API 1.0.0-M19 (July 1st 2013) * Three releases for ApacheDS: * ApacheDS 2.0.0-M12 (May 2nd 2013) * ApacheDS 2.0.0-M13 (June 25th 2013) * ApacheDS 2.0.0-M14 (July 1st 2013) * Two releases for Apache Directory Studio: * Apache Directory Studio 2.0.0-M7 (May 31st 2013) * Apache Directory Studio 2.0.0-M8 (July 4th 2013)
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAPv3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers * No new PMC members -- Current activity -- * Apache Directory LDAP API: * Two releases during this quarter. * Low activity * Very minor bug fixes. * ApacheDS: * Three releases during this quarter. * Good activity * Improved stability, indexing and replication (reliability & better logs) * Good work done on Kerberos layer and documentation * Ongoing work on depending projects (Apache Mina and Apache Labs Mavibot) * A 2.0.0-RC1 release may be expected soon * Apache Directory Studio: * Three new releases during this quarter. * Good activity * Integration and support of the latest version of the Apache Directory LDAP API and ApacheDS * Added new and improved existing value editors + minor bug fixes * A 2.0.0-RC1 release may be expected soon as well -- Releases -- * Two releases for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M15 (January 29th 2013) * Apache Directory LDAP API 1.0.0-M16 (March 3rd 2013) * Two releases for ApacheDS: * ApacheDS 2.0.0-M10 (January 29th 2013) * ApacheDS 2.0.0-M11 (March 3rd 2013) * Three releases for Apache Directory Studio: * Apache Directory Studio 2.0.0-M4 (January 30th 2013) * Apache Directory Studio 2.0.0-M5 (February 12th 2013) * Apache Directory Studio 2.0.0-M6 (March 14th 2013)
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAP v3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers * No new PMC members. -- Development -- * ApacheDS: * Two releases during this quarter. * We added support for the SyncRepl protocol (Multi-Master replication) * Improved performances and minor improvements and bug fixes. * Apache Directory LDAP API: * Two releases during this quarter. * Prior to releasing any final version of the API, we had to rename our base package name, 'org.apache.directory.shared' becoming 'org.apache.directory.api'. * We fixed various issues related to the connection pool, RDN parsing (with special characters) and an infinite loop when founding a referral entry. * Apache Directory Studio: * No new releases during this quarter. * Small activity (small bug fixes and improvements) on Apache Directory Studio which was mainly waiting on other subprojects to be released. * The preparation of a release of Apache Directory Studio 2.0.0-RC1 is expected in the next days. * Website & Distributions: * We have successfully moved our 'dist' to svnsubpub. * We requested the move to svnsubpub and the Apache CMS for our website as well and it should done in the next days. -- Releases -- * Two releases for Apache Directory LDAP API: * Apache Directory LDAP API 1.0.0-M13 (October 12th 2012) * Apache Directory LDAP API 1.0.0-M14 (January 7th 2013) * Two releases for ApacheDS: * ApacheDS 2.0.0-M8 (October 12th 2012) * ApacheDS 2.0.0-M9 (January 2nd 2013) * No releases for Apache Directory Studio
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAP v3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers * No new PMC members. -- Development -- * ApacheDS: * No new releases during this quarter. * A new release is currently being voted. * We have fixed a crucial problem that occurred when performing concurrent searches and modifications. * Apache Directory LDAP API: * No new releases during this quarter. * A new release is currently being voted. * Refactored and simplified our entry cursor implementation and our use of generics. * Apache Directory Studio: * No new releases during this quarter. * Very low activity. * Website: * We are still migrating our website to use svnpubsub and the Apache CMS. It will be ready for the January 2013 deadline. -- Releases -- * No releases for Apache Directory LDAP API * No releases for ApacheDS * No releases for Apache Directory Studio
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAP v3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * One new committer * Aleksander Adamowski (aadomowski) * No new PMC members. -- Development -- * Apache Directory LDAP API: * One new release during this quarter. * Important bug fixes in low level classes taking care of LDAP decoding and entries handling. * ApacheDS: * One new release during this quarter. * Work continued on our MVCC BTree branch and we're trying to merge it to the current trunk, but the divergence since the branch was created (8 months ago) makes it a little more complicated. * The removal of 2 unnecessary system indices has allowed us to boost the search performance of ApacheDS by a 2x to 4x factor (depending on the type of search). We're not back to the level of performance we had on versions 1.5.x but we're getting closer. * Bug fixes and small additions to previously released milestones versions. * Apache Directory Studio: * No new releases during this quarter. * A discussion in a Jira issue raised the problem that Apache Directory Studio contained sources of some classes released under the Eclipse Public License (EPL). While it's OK to include a EPL binary (as a library for example) in a release of an Apache project, it isn't the same for EPL source files. We cleaned Apache Directory Studio sources and removed/rewrote any of these files. The situation is now clear. * Minor bug fixes. * Website: - Work has started to migrate our website. Svnpubsub has been activated with a staging website and we're in the process of migrating pages from Confluence to SVN. -- Releases -- * One release for Apache Directory LDAP API: * 1.0.0-M12 (May 11th 2012) * One release for ApacheDS: * 2.0.0-M7 (May 21st 2012) * No releases for Apache Directory Studio
(Directory)
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAP v3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers. * No new PMC members. -- Development -- * Apache Directory LDAP API: * Three releases during this quarter. * Mainly bug fixes and feature stabilization. * The use of the API inside Apache Directory Studio 2.0 has greatly helped discovering new bugs and stabilize the features. * ApacheDS: * Three releases during this quarter. * These releases contains small bug fixes and were meant for inclusion inside Apache Directory Studio. * In the meantime, major works are still underway on these topics: * a transaction mechanism on top of our backend implementations * a review of the indices system * An important vulnerability has been discovered very recently in the ApacheDS 1.5.x branch which allows authentication with the direct use of the hashed password as credentials. Considering that the ApacheDS 1.5.x branch is almost dead, we are in the process of documenting it on the website and moving our users towards the 2.0 milestone versions (which are not affected by the issue). * Apache Directory Studio: * Three releases during this quarter. * A first milestone version, followed by 2 other ones, has finally been released for Apache Directory Studio 2.0. 1 year and 9 months after the latest released version (1.5.3) back in April 2010. * These releases have been very well received and users provided us important bug reports that helped us stabilize it. * Following an incubator email, we've discovered that Apache Directory Studio's usage of some external binary libraries (contained in the source release) was not appropriate and we are working to get this fixed during the next quarter for our next releases. * Website: * An update of the ApacheDS website is required ASAP to let our users know about the authentication vulnerability and make it clear that they should use 2.0 milestone versions instead. * We also need to start thinking about the migration of our entire website to use svnpubsub instead of Confluence. -- Releases -- * Three releases for Apache Directory LDAP API: * 1.0.0-M9 (January 18th 2012) * 1.0.0-M10 (February 7th 2012) * 1.0.0-M11 (February 29th 2012) * Three releases for ApacheDS: * 2.0.0-M4 (January 18th 2012) * 2.0.0-M5 (February 7th 2012) * 2.0.0-M6 (February 29th 2012) * Three releases for Apache Directory Studio: * 2.0.0-M1 [2.0.0.v20120111] (January 18th 2012) * 2.0.0-M2 [2.0.0.v20120127] (February 7th 2012) * 2.0.0-M3 [2.0.0.v20120224] (February 29th 2012)
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAP v3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers * No new PMC members. -- Development -- * Apache LDAP API: * Bug fixes and small additions. * A new release is expected very shortly (to be included inside Apache Directory Studio 2.0.0-M1). * ApacheDS 2.0: * Work continued on two main focus points: * Make ApacheDS run in an OSGI container (using Apache Felix or Karaf). * Include a transaction mechanism on top of our backend implementations. * Apache Directory Studio 2.0: * A lot of bug fixes and improvements have been made in order to be able to release a first milestone version (2.0.0-M1) in early 2012. -- Releases -- * One minor bugfix release for Apache Directory Studio Maven Plugin: * 1.0.5 (January 2nd 2011)
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAP v3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * Two new committers * Selcuk Aya (saya@apache.org) * Gokturk Gezer (gokturk@apache.org) * No new PMC member. * One contributor (Oliver Schmidt) has been given write permission on Confluence to contribute some documentation on ApacheDS 2.0. * Two of our team members went and presented at LDAPCon 2011 (October 10-11) in Heidelberg, Germany. -- Development -- * Apache LDAP API: * Improvements on common replication objects and utilities. * Bug fixes and small additions to previously released milestones versions. * Three new milestones versions have been released (see below). * ApacheDS 2.0: * The master-slave replication sub-system is finally back and working. * Bug fixes for some server startup and Kerberos corner case issues. * Two new milestones versions have been released (see below). * Apache Directory Studio: * Added the ability to start ApacheDS 2.0.0-M3 version within Studio. * Small bug fixes and minor code cleaning. * Overall: * We have voted the removal of support for Java 5 for ApacheDS and Apache Directory Studio. The compilation target for these two projects is now Java 6. -- Releases -- * Three milestones releases for Apache LDAP API 1.0: * 1.0.0-M6 (August 4th 2011) * 1.0.0-M7 (August 19th 2011) * 1.0.0-M8 (September 8th 2011) * Two milestone releases for ApacheDS 2.0: * 2.0.0-M2 (August 19th 2011) * 2.0.0-M3 (September 12th 2011)
The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAP v3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache Directory Studio) and a client API that can be used to communicate with any directory server (Apache LDAP API). -- Community -- * No new committers or PMC members. * A user expressed his willing of contributing some documentation. -- Development -- * Apache LDAP API: * A major refactoring took place to remove the embedded Apache Felix OSGI container based on feedback from some users who had difficulties with it. We're still looking for the best solution which pleases both our OSGI and non-OSGI users, still allowing a good modularity and extensibility. * Two new milestones versions have been released (see below). * ApacheDS 2.0: * After almost a year of development and major refactorings in key parts of the server, a first milestone version has been released (see below). * This should allow our users to take a look at the state of ApacheDS 2.0 after a long period without any releases. * Other incremental milestones should follow in the next months. * Apache Directory Studio: * Lower activity on Studio since the last report. Mainly small bug fixes and minor code cleaning. * Overall: * There's currently a discussion about removing support for Java 5 in the next releases (at least for ApacheDS and Apache Directory Studio). -- Releases -- * Two milestones releases for Apache LDAP API 1.0: * 1.0.0-M4 (May 30th 2011) * 1.0.0-M5 (June 25th 2011) * First milestone release for ApacheDS 2.0: * 2.0.0-M1 (June 25th 2011)
Community: * No new commiter or PMC member. * A misunderstanding between two PMC members came to a situation where a chair rotation vote was launched in January by a PMC member and then rejected by the chairman. This misunderstanding between the two PMC members was about releasing version 2.0 of ApacheDS. One party was trying to push a release, while the chairmain was concerned with "potential" commercial interests instead of focusing on code quality first. The chair rotation vote was interpreted as a retaliatory action by the chair, who rejected the rotation, recalling that it can't be used as a tool for retaliatory purposes. The chairman indicated his will to continue to fulfill his duty and that rotation could take place a little later, after the situation was diffused to prevent a tour de force situation. Afterwards, things calmed down, both members took some time to discuss in details and the dispute was settled. No release occured but it was decided to move to an incremental milestones, then RCs, then formal releases cycle which allows more frequent releases without compromising code quality. Both parties came to the conclusion that it was only a big misunderstanding. As the chairman recommended, three months later, he requested a formal vote for chair rotation, which was a success. A highly toxic situation that could severely damage the community was successfully avoided thanks to the understanding of all those involved. Development: * We are working on finalizing a first (official) release of the Apache Directory LDAP API. There has been an important reorganization in projects hierarchy and a good cleaning of the overall APIs. A first draft of the documentation for the API has been started on the wiki Three milestone versions has been released (see below). * We are still working on versions 2.0 for Apache DS and Apache Directory Studio which need a little more work. First milestones releases could be out in the next two months with RC following them probably around September. * Before the version 2.0 of Apache Directory Studio comes out, it has been decided to release a 1.5.4 bug fix version (the last version, 1.5.3, is already one year old). Releases: * Three milestone releases of the Apache Directory LDAP API: * 1.0.0-M1 (February 18th 2011) * 1.0.0-M2 (March 15th 2011) * 1.0.0-M3 (April 22th 2011)
WHEREAS, the Board of Directors heretofore appointed Alex Karasulu to the office of Vice President, Apache Directory, and WHEREAS, the Board of Directors is in receipt of the resignation of Alex Karasulu from the office of Vice President, Apache Directory, and WHEREAS, the Project Management Committee of the Apache Directory project has chosen by vote to recommend Pierre Arnaud Marcelot as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Alex Karasulu is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Directory, and BE IT FURTHER RESOLVED, that Pierre Arnaud Marcelot be and hereby is appointed to the office of Vice President, Apache Directory, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. This resolution passed unanimously on a roll call vote.
Board report wise we just had a couple LDAP-API releases and no change in the community committership or the PMC besides the chair change.
The report was not accepted due to its brevity and format. AI Greg: contact the chair and discuss an acceptable report.
Community --------------- No new PMC members. One new committer (already Apache Member), Antoine Levy Lambert, who added the delegated authentication feature. List Subscribers: API : 34 DEV : 173 (was 170 one year ago, 185 2 years ago) USERS : 219 (was 189 one year ago, 145 2 years ago) Releases ------------ None but the community is not idle preparing milestones for major version releases. The community has voted to change the versioning scheme we've used in the past which was slowing us down. We've started using the Eclipse Milestone scheme and have started work on 2.0.0-M1. We're working on a shared-1.0.0-M1, which will include the LDAP API. Studio 2.0.0-M1 will also be released shortly there after. Slowdowns resulted due to the need for a full Kerberos Codec rewrite by Emmanuel Lecharny and Kiran Ayyagari. Various optimizations and fixes are also being done on the LDAP side by Emmanuel. A new ApacheDS Configuration plugin has been created by Pierre to compliment the 2.0 ApacheDS M1 release which includes a new configuration subsystem inside the LDAP DIT. Miscellaneous ------------------- There's been a great deal of refactoring and feature addition to get a more stable ApacheDS 2.0 ready. The new release versioning scheme will give us more flexibility over our older scheme. Apache Project Branding requirements for all ASF marks have been fulfilled by Stefan Seelman.
Community:
o No new PMC members
o No new committers
o Finalization of 2010 GSoC projects
o Increase in users interacting on our mailing lists -
qualitatively it seems more users are using ADS/Studio and
participating on our user mailing lists with various
issues/shortcomings they're encountering.
Releases:
o Nothing since last quarter when the new LDAP API was first released
Summary:
o What seems like a quiet quarter really had lots of preparatory
activity for 2.0 releases
- skins for site and documentation
- switch to docbook for (manuals) documentation
- revamped installers and subproject cleanup (installers and
daemon subprojects)
- interface consolidation refactoring and cleanup in shared
o Everything seems to be in order and nothing is warranting the
attention of the board
There's nothing noteworthy to report. No new committers, or new PMC members. The GSoC projects have started up with two new students. There are some releases: Apache Directory Server 1.5.7 Apache LDAP API 0.1 Currently heavy work is being done on Apache Directory Server 2.0 which will hopefully be released before the next board report is due. Work has already begun on Apache Directory Studio 2.0.
Releases: o ApacheDS 1.5.6 o ApacheDS 1.5.7 next week o Apache Directory Studio 1.5.3 o Ldap-API 0.1.0 is out Community: o Ersin Er requested to go emeritus and requested removal from PMC due to inactivity. No new committers. o GSoC proposals (one very interested guy, another one maybe)
Community ======== No new committers. No new PMC members. New unofficial alliance between OpenLDAP and Apache Directory yielding greater collaboration and interoperability namely where replication is concerned. Releases ======== No new ApacheDS releases. Few minor releases of Apache Directory Studio. Summary ======= All quiet over all with a lot of activity on the new LDAP API list. Many groups are collaborating to build the next LDAP API standard.
Doug to pursue a report for Directory
No new committers, no new PMC members. No release since the last report, but Studio 1.5.0 is in its ultimate finitions. The server is again under some huge refactoring (schema) Releases ======== Studio 1.5.O should be voted in the next two weeks. We expected to release ADS 2.0-RC1 before ApacheCon US, but it might be a bit tight schedule... Community ========= No new committer this quarter. No new PMC members either. We gained 27 new subscribers on the users' mailing list since january report (174 against 147). Since July, a big refactoring is being done, affecting a main part of the server, the Schema. It's expected to be done by the end of october. Two members of the Directory community went to LdapCon 2009 in Portland, OR, where they presented the base replication system which is currently being written, a common API effort with SUN, tooling and some Java/Ldap mapping. The LDAP API effort has been started with the creation of a new mailing list (api@directory.a.o), it's currently not very active as we are swamped in the Schema redesign. Conclusion/Summary ================== A very active quarter, with major modifications being done, and a lot of discussions going on with other LDAP actors (SUN, OpenLDAP).
<note> We requested an extension for the July report since many of us were traveling without Internet access. Hence why we're reporting in August instead of our regular time. </note> We had a pretty slow quarter as far as releases and new committers are concerned. No new committers and no new PMC members appeared. Many new contributors and list participants are appearing to create even greater activity on our user list. We have a new mailing list for a client API effort where several LDAP projects are collaborating together: api@directory.apache.org. We just today kicked off a vote to release ApacheDS 1.5.5 which has been long awaited: 11 months since ApacheDS 1.5.4. It should be the last release before we go to ApacheDS 2.0. However this is mostly for the next report. Noteworthy point is that some of us are heading out to present ApacheDS and Studio at the next international LDAP conference. Emmanuel and Stefan Seelmann will be attending and speaking. Again though most of this will be in the next report. Overall this was a relatively event-less quarter for Apache Directory.
Jim to follow up with Alex on the use of the api@ list and will report back to the board@ list.
Jim: this project asked for a postponement until Aug 2009.
WHEREAS, the Board of Directors heretofore appointed Emmanuel Lecharny to the office of Vice President, Apache Directory, and WHEREAS, the Board of Directors is in receipt of the resignation of Emmanuel Lecharny from the office of Vice President, Apache Directory, and WHEREAS, the Project Management Committee of the Apache Directory project has chosen by vote to recommend Alex Karasulu as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Emmanuel Lecharny is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Directory, and BE IT FURTHER RESOLVED, that Alex Karasulu be and hereby is appointed to the office of Vice President, Apache Directory, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special order 7A, Change of Directory PMC Chair, was approved by Unanimous Vote of the directors present.
We have voted a 'new' Chairman, Alex Karasulu. Emmanuel Lecharny is stepping down from the chair after having been in this position for two years. Releases ======== Studio 1.4 has been released on april, 10th. We have scheduled to release ADS 1.5.5 next week. This will probably be the last release before ADS 2.0. Community ========= A new Committer : Andrea Gariboldi, who wrote an Oracle backend. No new PMC members. Although last quarter was very calm, since March, all the ADS committers suddenly surged and are back. All the team is now targeting ADS 2.0, with Replication, DRS and configuration in DiT. This should be feasible by the next three months. A few reorganization in the code has been discussed, we will create a subproject for Kerberos. We have had some discussion about more collaboration with OpenLDAP, and the decision was made to build a compatible replication system : OpenLDAP and ADS should be able to replicate. OpenLDAP people also asked us about supporting jLDAP (see next point). Last, not least, we are working on a Client LDAP API, which will be used by Studio and the replication system. We will most certainly promote this project as a sub-project of Directory. This should be close to jLDAP but leveraging Java 5 (based on MINA, it will be a non- blocking API, with varargs and generics). Conclusion/Summary ================== An interesting quarter, very active, with a great Apache Con.
Status report for the Apache Directory Project No new committers, no new PMC members. Studio 1.3 has been released in november. A lot of work has been done to migrate to MINA 2.0. we have to refine the 2.0 roadmap, as the current roadmap is a bit irrealistic. Right now, we are mainly focused on replication and on the Disaster Recovery System. The idea is to get a 2.0-RC1 out by the next Apache conference (Amsterdam). Releases ======== Studio 1.3 has been released. It does not contain a lot of visible modifications, but a lot of new small features and bug fixes. We expected to release ADS 1.5.5 by the end of last year, but failed to meet this milestone. This is still a target for the next few weeks, as we have a lot of bugs fixed in this version. Community ========= No new committer this quarter. No new PMC members either. We gained 19 new subscribers on the users' mailing list since july's report (147 against 128). We didn't had a lot of activity for many of the main committers, as many of us are on a day job. Alex was MIA for 3 months, but it was announced, and he is now back. Obviously, being one of the most active committer, it impacted negatively the activity. Emmanuel had to spend one month on MINA to get the 2.0.0-M4 out, as there were blocking issues in the library, forbidding us to use it for ADS. As there is a starting Infrastructure project (using ADS inside The ASF) we also spend some time installing ADS on a solaris zone, and to do a first injection of Apache committers into the ldap base. Until we get a working replication system, we won't go any further, though. Conclusion/Summary ================== A slow quarter, but an active beginning of year, as we have a lot of communication around the replication system first because it's a major feature we want to have in 2.0, and second because it's mandatory for ADS to be used by Infra. We are pretty happy to have the OpenLDAP community participating in this area, through mails. Thanks to Howard Chu and Quanah Gibson-Mount. The number of downloads (ADS and Studio) has stabilized to 350 downloads per day (10 000 per month), down from a peak of 56 000 downloads in April, according to V. gritsenko stats (people.apache.org/~vgritsenko). Google Analytics gives a more accurate number of downloads for each product : 1.5 : 41 472 downloads in 2008 (113 per day) 1.0 : 6 116 downloads in 2008 (16 per day) Studio : 52 188 downloads in 2008 (142 per day)
The board is pleased to see this project being used in-house.
The privacy policy should have been noted in the report, and is much appreciated.
Nothing much to mention. We have two new PMC members, no new committer. We are still busy working on new features, targeting a 2.0 before Apache Con EU 2009. Otherwise, nothing special. Releases ======== We have had 2 releases in the last 3 months, 1.5.3 and 1.5.4. The latest is not a bug release, but we just have decided to work on a better roadmap, with more releases, more often. Hopefully, ADS 2.0 RC could be ready for Q1 2009. Studio 1.3.0-RC1 has justbeen voted as well, 3 months only after the latest release (1.2.0). It seems that we are now in a good trend of a release every 3 months. Community ========= No new committer this quarter. Two new PMC members : Felix Knecht and Kiran Ayyagari. The community has been more active this quarter, with around 15% more commit than on the last 4 quarters. Export Notification =================== The Export Notification procedure has been fulfiled for Studio. OpenGroup certification ======================= Apache DS 1.0 certification has been extended one more year, thanks to Stefan Zörner who run the VSLDAP suite and to the OpenGroup. Conclusion/Summary ================== A standard quarter, with nothing important worth mentionning. We are moving slowly toward the 2.0 version. The number of downloads (ADS and Studio) has grown up to a rate of 400 downloads per day (150 000 per year).
Business as usual, this quarter. Bug fixes, lot of work to implement new features. Otherwise, nothing special. Releases ======== The latest release (1.5.3) is being voted. A lot of errors have been fixed. Some big new features have also been added in this release, including a SASL NTLM mechanism, allowing users to authenticate on Windows server (as the current implementation is based on some GPL code, the jar is not delivered within the server, users have to download it by themselves). Studio 1.2.0, being voted too, is bringing some very important new feature: it's now possible to launch an internal ADS server, without having to install it beside. That helps a lot for those who want to experiment the server at no cost. Community ========= No new committer this quarter. We gained 16 new subscribers on the users' mailing list since last report (128 against 112). It seems that we have around one new subscriber every week or so. The Apache conference in Amsterdam was pretty successful, and we have had many interesting conversations with other Apache project. Derby project is interested to establish some collaboration between our two projects. Things are on their way. I have informed the PMC of my will to rotate the chair, and proposed Alex. He asked me to reconsider my call, at least for a few months, just to make sure that we don't rotate too quickly. Features ======== SASL NTLM mechanism is one of the most important added feature. We also have installer for almost all the platforms : - windows - linux (RPM, DEB, zip) - MAC OSX - Solaris The site download page has been completly revamped Performance are now much better. We still have some work to do, but we will do it in 1.5.4. Studio now embed ADS, which can be launched and stopped internally. Stefan also worked on a GUI test tool. Issues ====== The very same : we don't release fast enough, bigbang branch takes forever to complete, and more documentation is needed. Otherwise, some of us had to spend some time on MINA, which is a major component of Directory. Export Notification =================== The Export Notification procedure has to be fulfiled for Studio. It's just a matter to update the matrix, it will be done in the next couple of weeks. Conclusion/Summary ================== A busy quarter. I have to add that until we get rid of the bigbang branch, we won't see a lot of activity beside the current active committers. Studio is really doing well, and there are more and more common parts between the server and Studio. We are still expecting to announce ADS 2.0 by the end of Q3.
The last quarter was pretty calm, with some intense coding sessions, and preparation for releases and Apache Conference EU. Two releases will be done : - Apache Directory Server 1.5.2 - Apache Directory Studio 1.1.0 We have welcomed 2 new committers. Releases ======== Again, we missed our target, which was to release every 3 months. We missed it by 6 months ! Last release (1.5.1) was done back in september, and we tried hard to release for december, with no success. What happened is that we under estimated our workload and overestimated our capacity to do it on time. The impact is quite huge as a lot of our committers were waiting for this new release to move on, as we were refactoring some major parts of the core server. Hopefully, we are close to be done with this big refactoring, and we start to see the benefit of it. Studio was also expected to be released in december, but we spent 2 months to change the build system from Ant to Maven. Thanks to Felix and Pierre- Arnaud, we are done. So here we are, just in time to release before Apache Conference, as usual ! We gained 15 subscribers on the users' mailing list since last report (112 against 97). As we released some RC for studio, the number of download has increased greatly. We are now around 30 000 downloads, including the server. We are still moving slowly to the 2.0 version, adding some more feature, working on performance, removing bugs. The server has doubled in size since the 1.0 version ... Community ========= We have had the pleasure to welcome two new committers : - Jan Rellermeyer - Kiran Ayyagari Jan will work on all the protocols other than LDAP, and Kiran is currently implementing some core data structure dedicated for our needs (AVL trees). At the same time, some long waited cleaning has been done. As MINA and ADS split last year, the MINA committers don't belongs anymore to the ADS committers' group. After having asked them, and received their agreement, they have been removed from the ADS committers list. Here is the list : - Dave Irving - Julien Vermillard - Mike Heath - Nicklas Therning - Peter Royal 6 ADS committers will be present at Amsterdam. Features ======== The long expected StartTLS extended operation has been added last month. A new API is now used instead of JNDI inside the server, allowing better control. This is something we want to pursue, eventually down the road to a RFC or a JSR. Performance are not as good as the previous version, due to some of the refactoring. This was expected, and will be fixed in 1.5.3 We have installers for almost all the platforms, but Solaris. Issues ====== Our priority is to finish the refactoring, so a lot of issues have been postponed. The server is still 'stable', but we will add new functionalities in the next few months. Documentation is lagging... A big effort will have to be done on this before releasing 2.0 ! Export Notification =================== The Export Notification procedure has been fulfiled. We are now registred in the ECCN matrix, the US gov has been notified, the README files have been updated. I wish we are OK ... Conclusion/Summary ================== We are on our way to Apache Conference now. The next big thing will be the september LDAP conference in Germany (?), where we expect to announce ADS 2.0. We start to see more and more people who want to use ADS in production or to integrate it into some product. This is encouraging, even if this is not the explosion projects like Wicket can have ! It's a long term project, which needs dedication. Apache is pretty good at that :)
Happy new year !! Those last three months were pretty busy, trying to change things into the core server. We are still in the middle of this process. We are happy to have one more new committer! Releases ======== No release at all since september, which is a little bit disapointing if we consider that we wanted to release every 3 months. Maybe a little bit too optimistic vision, considering the size of the project... ADS is on its way to 2.0, expected for Apache Conference EU. It will be a major rewrite of many internal parts of the server : - Replacement of the JNDI API with our own API - Addition of cursors to deal with entries from the backend - New configuration (already done, thanks to David and Alex) - New installers, with silent installers - Many bug fixes, and other features. The documentation is being reworked toward 2.0 now that the configuration has been totally rewritten. We expect to have an updated documentation available by Apache Conference too ! Studio is supposed to be released soon (we are expecting a 1.1 version every now and then as soon as the migration from ant to maven is done). Many bugs have been fixed, and some few internal features have been added. The main workshop is the migration from ant to maven. Triplesec : Still in hibernation. We are waiting spring to wake it up ... Kerberos : A third of the rewrite being done in august has been imported into trunk. This is not finished yet, as we have more urgent tasks on our plates. Still to be completed by june, I think. Community ========= Another addition to our team : Felix Knecht. He is a committer from cocoon, and has a deep knowledge about Maven. He is being very active moving Studio from ant to maven, which will have a deep impact on the project, as we will be able to build all the pieces together. This is important as we have some common libraries we would like to be sure they don't break any single project using them. More than being a maven Guru, he is also quite experienced, and we all benefit from his insights, when it comes to code rules... definitively a valuable addition ! Apache Directory Studio has been downloaded more than 17 400 times last year. This is a bare minimum, as we have no ideas about how many people are installing the plugin directly into Eclipse. However, we should not get too excited about this number, as many people will downloaded the tool more than once. Anyways, this is quite a success for such a specialized tool ! Around 20 more users have subscribed to the users mailing list since september ( 97 against 80 ). The number of downloads is also increasing a lot lately : from 2000 downloads a month in junuary up to 13000 last december ! The curve is quite impressive (http://people.apache.org/~vgritsenko/stats/projects/directory.html#Downloads-N1008F). The only little problem is that we have no idea about which part is due to ADS, Studio and maybe MINA... Some very important things has happened since the Köln Ldap Conference : we are now working hand to hand with the OpenLdap people, which is a great thing, as they have a deep knowledge on Ldap. Lot of informations have been exchanged lately, and we may work together on replication. One of our common target will be to be able to replicate data between ADS and OpenLdap. Features ======== We are now targeting a ADS 2.0 in the next 3 months. This is done through tactical moves : we have created a bigbang branch in which we are practicing heart surgery, while the trunk contains the 'stabilized' version. The idea is to periodically merge bigbang with the trunk, when some big piece of work has been completed. This is important for other committers who are not necessarilly involved into the bigbang challenge, as they are impacted. We are not exactly adding some new features to the server, but more important, we are trying to rise the server to a point were it will be easier to do so. The 2.0 version should be more reliable, faster, and easier to use. Studio will be extended to have a remote schema handling : it should be possible to dynamically manipulate a running server schema in 2.0. Another addition will be a new configuration manager, able to handle different versions of the file, depending on the remote server version. Issues ====== Not a lot of new bugs have been found lately. Not that the server is perfect or that "we have found the last bug!", but the obvious bugs have been found and mostly fixed. We still have a 100 bugs to fix. The main issue we have currently is the documentation which is a little bit sparse and confusing. The Basic user Guide is pretty much ok, but we still have to work hard on the Augmented User Guide and Developper Guide. Some of our committers are currently handling this big issue. Installers are also a big concern. We have delivered installers for Windows, Linux, Mac and Solaris, but they are all graphical installers. As ADS is a server, we need a silent mode installer for those platforms. This is a work-in-progress... Conclusion/Summary ================== This was really an interesting year, as we saw a lot of talented people joining us. Studio is a real success, and ADS is slowly but steadily progressing toward more stability. Things are going pretty well. We still have a lot of work to do, but this is a pleasant journey ! The big challenge we will face now is to use ADS for real, starting by Apache itself !
Approved by General Consent.
Being the chair for now 5 months, and still learning how to deal with the project in the best possible way. Not easy every day :) The project is somehow stabilizing, with no new committers those 3 months (july and august are not the best months to get some new guys away from sun and beach to face a computer...). A very good Ldap Conference stood up in Köln (Germany) at the beginning of September. This coupled with a PR and some new versions generated a lot of buzz for ADS (more than 20% hit increase since then, with a 100% peak for two weeks !). Marketing is important :) (Thanks to Sally and Jim, btw) Releases ======== It was quite a stressfull period, as we released 3 versions in one month: As we have now three sub projects (Apache Directory Server, AKA ADS, Apache Directory Studio AKA ADStudio and TripleSec) we also have three different status : ADS 1.5.1 : a long waited release, which fixed more than 100 bugs, some of them being very annoying. The server is also faster, more stable, and contains some interesting new things. ADS 1.0.x : Nothing new since may, we can say that this major version is pretty dormant. Not that we don't have bugs to fix in it, but we consider that this version is almost dead. ADStudio : 2 versions in september : 1.0.0 !!! and 2 weeks later, an urgent bug fix, 1.0.1 (SSL support has been snatched by mistake in 1.0.0). Triplesec : Nothing has changed right now Kerberos : A big rewrite has been started on july, but due to external reasons, the effort as somehow stopped since august. We hope to have a better code base by the end of 2007, maybe Q1-2008 Community ========= Chris Custine has been voted as a new PMC at the end of August. This is a very good addition for us, as he shown dedication, and more important, some good balance when it comes to take a decision. It's good to have young blood, but it's also valuable to have some older blood, with experimented peeople ! Seven of us went to Köln last month, for the first LdapConference. As there were around 70 persons attending this conference, we were pretty proud to represent 10% of all those guys ! We have had 3 presentations, and were pretty lucky to have had a lot of very intersting conversations with Ldap top guns, and also with some OpenLdap and Sun guys. We have seen some pretty harsh blog posts this year from OpenLdap developpers about ApacheDS, pinting out ADS bad performances, and it was a good occasion to see each other and to try to align our visions. And it worked ! I can say that we are brother in arms now :) Apache Directory Studio has been downloaded more than 8500 times since the very first version (feb, 15), but this is a very underestimated estimation, as there are many other places where someone can download the tool. However, this is a very successfull project, which brings a lot of visibility on the project. A 1.1 version will be released in the next couple of month, with new functionalities. Kerberos has stalled since August, for many reasons, personnal and professional. We are still to build a strong community around it, and it will take time. We are still thinking that Kerberos is really a major piece of the game, so we won't let it be. We have more and more users, and the users mailing list is becoming pretty active. We now have around 80 subscribers, 60 more than at the beginning of this year. The curve show a steady increase (http://people.apache.org/~coar/mlists.html#directory.apache.org). Some discussion on the infra ML has occured about the opportunity to use ADS as a base for managing committers, contributors, etc. The common agreement is that we must experiment first. Features ======== After the 1.5.1 release, some discussions arose about what will be the next step : work on a 1.5.2 or move to a 2.0. We all agreed that we have a pretty stable server (with around 100 issues ;) but the more we fix it, the more we find it difficult to improve the server, because of some technical choices which have been made years ago. At the end, a clear decision was agreed on : - we will work on a 2.0 target, with massive architectural redesign (no more JNDI inside the server, a new configuration, etc) - a 1.5.2 version will be release, but it will be a merge from the 2.0 branch, so that users can 'experiment' the cool new features we will add. We expect to have a better base and a faster server after this big refactoring, which will last for the next couple of months. Our final target is to have this 2.0 out for the next Apache CON EU, 2008. We all think this is not impossible. 2.0 should also be validated as compliant by the OpenGroup, but with a strongest level : STANDARD (VSLDAP compliance has three levels : BASE - wich is what we have reached -, STANDARD and EXTENDED). We are confident that we will obtain this STANDARD compliance. A lot of work as been done to ease the configuration too. We now need to focus on some migration tools, as this configuration have changed. Issues ====== The number of open issues is increasing, not only because we find bugs, but also because we are using JIRA more than before (which is a good thing, IMO). Bugs are fixed as much as possible, but as releases are not so easy to deliver, we try to focus on bugs when we feel a release is needed. Hopefully, we don't have major issues. Nothing new about documentation, except that we are now moving to update 1.5 documentation to be ready when 2.0 will be out. We want to add more real world use cases too. Conclusion/Summary ================== The 2.0 move was a very important decision, which was not so easy. We have had some heated discussions, but this was good because at elast, we had an opportunity to envision the different paths. We really expect to get some production ready server by mid-2008 now, with a level of performance close to the other servers. The next big move will be to use ADS in real life and to extend it with user oriented features : Triggers, Stored Procedure, Virtual Attributes, other backends...
Approved by General Consent.
After more than 2 years being the Chairman of this project, Alex decided to ask the PMCs to elect a new Chairman, and proposed me for this task, which was accepted and voted by the PMCs. I would like to thank the PMCs for their confidence and trust, and I will do my best to contribute as much as I can to be a decent Chairman, helping the project to grow and trying to let contributors to feel at home when working on it. I would also mention that this project would simply not exist without Alex hard work, and I'm very pleased that Alex is not willing to quit the project, but just want someone else to cope with administrative tasks. Releases ======== As we have now three sub projects (Apache Directory Server, AKA ADS, Apache Directory Studio AKA ADStudio and TripleSec) we also have three different status : ADS 1.5.x : no release in the past three months, since we released 1.5.0 in march. We are working on a 1.5.1 to be released by end of July. ADS 1.0.x : 1.0.2 has been released on may. It's a bug fix. ADStudio : The 0.8.1 released has just been voted those last days, and it's simply a version which support 64 bits procs. We are expecting a 1.0 bySseptember, hopefully. Triplesec : A full rewrite has been initiated lately. No release expected in the next three months. Community ========= The community is still growing with one new committer, Martin Alderson, who has pushed some very valuable fixes on Mitosis, the replication feature we have added to the server. He knows it more than the current committers because he has used it. It was a great addition to the team as we now have more than one people working on each major part of the server. We have voted two committers to become PMCs, Stefan Seelmann, who was a major contributor to Apache Directory Studio, and Christine Koppelt, who has recently moved from working solely on documentation to an active contribution to code, which is a really god news. Both of them has done a real great job on the past six months, not only being active committers, but also trying to make the project working better, helping other committers and users. They will for sure be very good PMCs members ! Chris Custine has been very active since he has been granted Karma, and this is really great, as he is a very experimented developer, and as he dedicated a lot of time on parts where we were weak : packaging. He is also very valuable in helping users and new commers. The Kerberos server is being improved (speed, tests, documentation), and we are doing our best to exit from a situation where this is a one man show. As this will be a major component used by TripleSec, this is absolutely mandatory to have 2 or 3 committers able to fix bugs and to help users. We are working hard on that. Apache Directory Studio is also gaining a lot of traction, not only from our users (more than 5000 downloads since the first announcement !), but also within the committers. It's not only Pierre-Arnaud and Stefan baby, as Christine and Stefan (Zorner) are now deeply involved. Some discussion relative to DNS protocol have started last month, about moving DNS to MINA. We don't have a clear position about it, as this is a dormant project in Directory. From some perspective, it would be better to have an active DNS project supported on MINA than a dormant project within Directory. No clear decision has been stated yet. We have submitted some proposals for LdapCon, the first LDAP dedicated conference, for the beginning of September in Köln (Germany). We expect to meet a lot of Directory committers there, but more important, we will expose the server and the associated projects to a LDAP dedicated community. Features ======== The last three months were just about working on bug fixes, and also improving the server performances. We have now a much faster server (up from 1500 search requests per second to 4500 on my laptop), but we didn't caught OpenLdap level yet. Thanks to Matt Hogstrom, we will be able to conduct wider tests on a huge server, and we will build a more complex and more realistic set of performance tests. What we want is to be able to have a clear grid of tests to compare ADS with other OSS LDAP servers. The Schema Editor in ADStudio is under heavy work, as we want the GUI to directly access the schema loaded into ADS. It's almost done. A lot of bugs have been fixed in the browser too. ADStudio is really moving fast in the good direction, and we expect to be able to follow the "release fast, release often" moto. Issues ====== We have a huge number of issues open, mainly Improvements and Tasks, which need more man power to address. This is not very simple to cope with all of them, but things are under control, as we are focusing on bugs first. We can't expect the server to be bullet-proof, but we can't also expect to have no bug report as more and more people are using ADS. The number of bugs we have is surprisingly low, but on the opposite side, people are often complaining about usability (Schema handling, packaging for embedded servers, server configuration). We have to work more on those issues. Documentation for 1.0 version has stabilized, and 1.5 version still needs some more work. Things are going much better, but as it's a never ended story ... Thanks to our 'wunderbar' german team, we have a usable documentation. Some of our users are asking for a PDF version of this documentation, this seems a good idea, but I don't know if it's something we can provide out of confluence. Conclusion/Summary ================== Working on this project is a very pleasant experience. We have new committers, and they are very efficients, users are now growing by numbers, and we can see it on the users mailing list graph generated by Ken Coar (http://people.apache.org/~coar/mlists.html#directory.apache.org) We don't have specific issues, I would say that the only problem we are focusing on at the moment is how to grow without loosing our current harmony. This is really a very pleasant situation !
Approved by General Consent.
Technically I'm not the PMC chair anymore. Emmanuel Lecharny is now the new Chair for Directory. However we received word late that the resolution passed and Emmanuel may be detained over the weekend. Also we don't want to miss the deadline for this report while providing the board with the information they need to properly conduct business in the upcoming meeting. If you'll permit me this will be my last board report. Community ----------------- The biggest change has already been noted regarding the new PMC Chair. I will help Emmanuel acclimate into the role while we transition. We (the PMC) are all confident in his abilities in this capacity. The community is really flourishing. As mentioned before the MINA elevation to TLP status we had some worries that Directory would loose some steam but this was not at all the case. We have more users and active committers than ever. People are communicating very well on the ML list and collaboration is at a high point. Some of us have been contacted privately by SUN engineers to participate on a new JSR for a client API for LDAP. I have reported this to our PMC list and will bring this matter to the jcp-open mailing list so those wanting to get involved may do so through the proper channels. A person was recently removed from the PMC for their unacceptable conduct has continued to participate and has rectified their behavior. The person is keeping conversations on the mailing list and informing us of their intentions, documenting their changes and has ceased to dump code without informing us. I think we have to keep and eye on this person but our actions seems to have stop their detrimental activities in it's tracks. The outcome has been positive. Pierre Arnod Marcelot (PAM) has been added to the PMC. No new committers since the last out of cycle board report last month. Brett Porter and Vince Tence resigned from the PMC on their own accord due to an inability to contribute more time to our effort: we look forward to their return if life permits. Releases ------------- We have released ApacheDS 1.0.1 (a bug fix release) and we are currently in the process of releasing the latest feature addition release of ApacheDS 1.5.0. This release includes the initial multimaster replication feature and the dynamic schema feature for the server not to mention many other enhancements. It's the most functional and feature rich release of ApacheDS to date. ApacheDS is getting to a point where we would be comfortable using it in production for a large directory. We just released version 0.7 of LDAP Studio and this project is taking off fast. The users are growing and I suspect we're going to add a few new committers over the course of the next couple months. Triplesec has yet to be released. We have much work to do to make it releasable WRT compliance with ASF releases. Conclusions/Summary -------------------------------- In general the Directory Project is doing very well. The community is healthy and vibrant and PMC has solved our most important issue without any observable collateral damage. Emmanuel can't complain that he's stepped into a mess :). We should expect a strong quarter with several releases, new additions to our user and developer base and possibly a couple of new PMC members. With this last report I will introduce the new Chair on our MLs. Thank you, Alex Karasulu
There was discussion around the inclusion of a person's name in the board report, where the report was "less than flattering" towards that person. The general consent was that the issue was and is public knowledge within the development community and in the PMC and the inclusion of the name and issue shows a clear direct line of management and oversight from the development community all the way up to the board.
Approved by General Consent.
WHEREAS, the Board of Directors heretofore appointed Alex Karasulu to the office of Vice President, Apache Directory, and WHEREAS, the Board of Directors is in receipt of the resignation of Alex Karasulu from the office of Vice President, Apache Directory, and WHEREAS, the Project Management Committee of the Apache Directory project has chosen by vote to recommend Emmanuel Lecharny as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Alex Karasulu is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Directory, and BE IT FURTHER RESOLVED, that Emmanuel Lecharny be and hereby is appointed to the office of Vice President, Apache Directory, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 6B, Appointing a new chair for Apache Directory, was approved by Unanimous Vote.
Releases
========
No releases since the last board report. Getting ready though for an
ApacheDS 1.0.1 (stable branch) and a 1.5.0 (feature branch+jdk jump)
release. Our budding new LDAP Studio project also plans a release (0.6)
in a short while as soon as we can get RAT to give us a clean bill of
health.
Code Donations
==============
CA still tried to push the JXPlorer donation however the PMC clearly
stated their position on the JXPlorer code base which comes without a
community. We will not be sponsoring an incubator proposal for
JXPlorer, the community would prefer to build a UI from scratch instead.
Community
=========
Last month we had an unfortunate situation where an individual, Enrique
Rodriguez (erodriguez@apache.org), was indefinitely suspended from the
Directory PMC.
Enrique has been warned several times both off and on the Directory
mailing lists about code dumping. He has without discussion introduced
major new features into the server. Without the consent or knowledge of
others in the community we urged him to cease adding unsupportable code.
There were several references to a "One Man Show" situation over the
course of months [0] which he publicly admitted to. The PMC urged
Enrique to start building some community around the code he already
added to Apache Directory Server before attempting to add new
functionality especially without consulting others. The bare minimum we
asked was simple internal/external documentation and test cases on the
features he authored so others could feel comfortable navigating and bug
fixing the code to support users. None of our requests were met.
Several PMC members saw the warning signs and people jumped in to try to
get involved with the new services introduced by Enrique. ersiner@ and
akarasulu@ tried to get into the code to support it. When we started
committing code and patches Enrique had a knee jerk reaction towards
anyone touching "his" code. This was unacceptable and hurt the feelings
of those in our community.
Enrique soon thereafter disappeared for a while (which is OK). However
he left us with code we could barely support (which is not OK) after we
asked him to document his existing work. Several of us just dealt with
the situation the best we could.
Recently Enrique popped back onto the mailing list asking for us to
support his submissions to ApacheCon EU. Enrique intended to introduce
new functionality into the server to support the claims of one of his
presentations (AD1854) [1]. This was completely unacceptable to us.
Several PMC members spoke out about the presentation yet Enrique ignored
our concerns. Meanwhile a few PMC members and I began conversing about
possible ways to handle this situation.
With the gravity of Enrique's actions, the recent attempt to add an STS
service to ApacheDS for an ApacheCon presentation, combined with his
lack of a response to our concerns warranted, at a bare minimum, a
suspension from the PMC. We were also worried that his ability to veto
others trying to get involved with the code he authored might be enough
to prevent any gelling of community around these features. Regardless
no one had a clear idea as to how to proceed.
Enrique then posted a message [2] to private@ which spoke about a recent
Hiatus. Myself and others (trustin, ersiner, and elecharny) felt this
was an attempt to avoid genuinely responding to our concerns to [1]. So
we confronted him with a WARNING to respond to our concerns to [1] with
[3]. Instead of a direct engagement there were mere excuses for his
behavior. Contrary to the presentation abstract for (AD1854) which
clearly enables ApacheDS as an STS service, Enrique later stated that
ApacheDS was only intended to serve as a backing store for the service
instead. This might work with people unfamiliar with the
technology/terminology but it was apparent to us that this was mere back
peddling. The abstract for AD1854 was very clear about the nature of
the facility to be present and available within ApacheDS.
After this correspondence I quickly consulted a number of PMC members to
see if they felt corrective action along the lines of a PMC suspension
was in order. A postmortem log of these conversations were posted to
the PMC mailing list with the thread starting with message [4].
Immediately after collecting consensus I acted without a formal vote,
however with definite PMC approval, to remove Enrique from the PMC: see
[5] on Directory's private@ list.
Overall the action applied quickly and resulted in very little commotion
or collateral damage to the community. A couple PMC members were a bit
worried about loosing Enrique however this action has lead to positive
results WRT to his community interaction and attempt to start complying
with our original requests. Several recent commits show Enrique
replacing @author tags, adding javadocs and test cases. He has started
to engage users interested in the code he's written and has started to
apply patches submitted by users instead of introducing new functionality.
Overall I think the PMC feels the actions taken in [5] were successful
in at least getting us on the right path to reaching our aims with the
least bit of damage.
I hope this was sufficient to inform the board of the recent events at
Apache Directory.
New Committers and PMC Members
==============================
No new committers. One new PMC member was just recently added although
not yet ACK'nowledged by the board: Pierre-Arnaud Marcelot (a.k.a. PAM).
Other
=====
On a cheerful note we recently revamped our website which is driven off
of auto-exported pages from confluence. The site is still under
construction yet is looking pretty slick:
http://directory.apache.org
Please feel free to give us more feedback.
Jim indicated that the committer summary provided in the report was good, and accurate.
Approved by General Consent.
New Committers ============== We had a couple new committers join us: Christine Koppelt (ckoppelt) and Stefan Seelmann. Community ========= Just recently MINA graduated to a TLP leaving the Directory TLP which it was a subproject of. We had some fears that this would result in the loss of some activity but surprisingly it has not. The activity is actually increasing in Directory proper. New Projects ============ With the flux of people interested in LDAP Studio and having 3-4 committers on it now we decided to take it out of our sandbox. Triplesec came to Apache Directory through the IP clearance process: http://incubator.apache.org/ip-clearance/directory-triplesec.html Another code base was brought in worth mentioning yet was not really made into a separate project but integrated straight into ApacheDS called mitosis for ApacheDS Multi Master replication: http://incubator.apache.org/ip-clearance/directory-mitosis.html Releases ======== At ApacheCon US 06 we released 1.0 of ApacheDS which was certified by the OpenGroup. We are preparing the first bug fix release for the end of this month. Other Noteworthy Matters ======================== CA is offering to contribute JXPlorer, an LDAP GUI client, (http://www.jxplorer.org/) but the PMC decided to reject it since the project is dead with little or no community behind it at this point.
Approved by General Consent.
Releases -------- A couple release candidates for long term evaluation were made available: 1.0-RC3, and 1.0-RC4. Finally just today we released the official 1.0 GA release. We're holding off on the announcements until ApacheCon in just a couple days when we will issue a press release thanks to the help of Sally and the PRC. Certification ------------- ApacheDS 1.0 has also passed all certification tests from the Open Group. As you may know from an earlier Directory board report the Open Group donated their time and waived the cost of certifying ApacheDS with their LDAPv3 product standard. Various certification docs have been fax/scanned and put into the directory PMC area in subversion. Donations and Software Grants ----------------------------- Recently, my company Solarsis Group LLC., donated an LDAP multimaster replication product called Mitosis Pro which will be integrated into ApacheDS. It will *NOT* be it's own subproject. The Mitosis (non-pro) edition was a Safehaus [0] community project located here [1]. Mitosis was an open source project originally kicked off by Trustin Lee, Emmanuel Lecharny and myself who are all Directory committers. The committers and I agreed to donate Mitosis to the ASF since an LDAP server without "out of the box" replication is a sad thing. Another project called Triplesec [2] was also granted to the ASF. Triplesec is a strong identity management platform built on top of ApacheDS leveraging it's LDAP and Kerberos server. This identity management product also performs two factor authentication using a J2ME mobile client. Because both projects were ASL 2.0 and composed completely of Apache Directory committers the PMC voted to import them. These projects are now in the process of being relocated with package name changes. Again the Mitosis code will be integrated directly into the ApacheDS code base. Triplesec will become it's own subproject.
Jim is to confirm that Mitosis and Triplesec have done software grants and that the required IP Clearance procedures for the Incubator have been performed.
Approved by General Consent
PMC Changes & New Committers ============================ Since April we've seen two new people added to the PMC: Ersin Er, and Stefan Zoerner. Peter Royal who just became a member of the ASF is now a committer on the MINA subproject of Directory, and Jim Jag. is also a new committer on MINA and ApacheDS. Software Releases and Goals =========================== We've been consistently (about every 2-3 months) releasing what we consider candidates for a 1.0 GA release but they have been falling short of our requirements. We'll keep fixing bugs and offering release candidates until we meet the mark of a GA worthy server. We're not rushing this. It takes time to find memory leaks and multi-threaded issues within a long running server. MINA has had a couple releases as well and the user community is growing rapidly. MINA is an amazing success. Peter and I would like to propose MINA for a TLP since MINA really does not belong under the Directory TLP even if it was created for ApacheDS' protocol related needs here at Directory. Expect a proposal soon :). Software Contributions ====================== We've been very slow on the uptake of a contribution by CA for an LDAP browser client called JXPlorer. Here's a link to the client if anyone is interested in looking at it: http://www.jxplorer.org/. I've dropped the ball on this one and have to contact CA to pick it up again. This will most likely lead to an incubator proposal to vet the IP. Committer Activity ================== Recently our activity on ApacheDS has been decreasing. The server is very complicated and there are several protocols to manage in one server. Besides striving to be an LDAP protocol server, ApacheDS contains plugins that enable it to master and serve DNS records in the LDAP directory. Likewise, it contains a partial DHCP server and a Kerberos server backing their information in the LDAP tree. This is all thanks to MINA BTW. Essentially it's looking as though we have all the capabilities of a simple windows 2003 server in one process minus the file system services. All of this backed by LDAP. Although a herculean effort, most of the non-LDAP plugin code has been written by a single person. At most two people can maintain it currently. IMO this is not a very healthy place for us to be especially with our recent diminished activity and the proposal to promote MINA to a TLP. Before the communities were intertwined. Now we're finding a warranted split occurring. However I worry most for sustaining the same quality of development with community support on the ApacheDS side more so than the MINA side. MINA will explode with activity IMO because its more general purpose and it does have a smaller learning curve. FYI it's only about 30-40K in size while ApacheDS is 10 times that. I've taken two steps to make sure we're get out of our slump and start growing healthily to accommodate these changes and to prevent us from fragmenting into an umbrella with 1-2 man subprojects like for example the logging TLP. (1) I've tried to both privately and publicaly warn the main developer of the non-LDAP modules. He cannot sustain these modules as a one man show without risking a fallback to the incubator. The message was specifically to share knowledge and grow the amount of committers and users of these modules. (2) I contacted the PMC and told them of my worries. I've also offered some options for overcoming these problems. We have several consistent contributors that are not quite there but have patches and other things waiting in queue for committers to pickup in JIRA. We proposed lowering our barrier of entry for new committers for a quarter to pull these peeps on the periphery into our committer base. These novice committers will be expected to follow a review then commit process on non-sandbox areas until senior committers think they no longer need to obtain approval. Currently there is a vote underway to install this process for the duration of 1 quarter starting in and including July. In conclusion, this is not something to freak out over. Our PMC simply feels that this is more a precautionary measure to prevent a potential spiral downward. We want to be more effective in engaging those that are interested in contributing and to fuel the growth of the community.
Juston noted that the temporary change in rules is interesting. Jim is following and involved in the PMC and reported the recent work on lowering committer bar in PMC. Sam indicated that he was impressed by the PMC being proactive.
Approved by General Consent
We've added two new PMC members (szoerner and ersiner) and a couple of committers to MINA (proyal and niklas). MINA has a new dev list because of all the traffic it's been having. Other than this we have had a steady stream of releases for MINA and ApacheDS. Looks like we're stalling a little bit on Naming but you never know when it will fire back up. ApacheDS 1.0 RC1 has released with an RC2 to follow shortly.
Approved by General Consent.
In general it's been a good and quiet quarter. Here are some
relatively notable things:
People and Community
=================
(FYI MINA is our network library which we use for implementing
protocols for ApacheDS)
o New committer on MINA: Niklas Thering
o MINA activity is picking up. We had to request a mailing list just
for MINA: 2/3 of the traffic on the dev list was MINA dev traffic.
o There are two candidates being considered as I write this email for
MINA committers
o Up to now we have knowledge of the following protocols being
implemented using MINA
- ldap[s],
- radius,
- kerberos,
- changepw,
- syslog,
- dns,
- dhcp,
- XMPP (jabber),
- ntp,
- nntp,
- bunch of simple protocols (echo, reverse, sysdate etc.)
Releases
======
o A few MINA releases (a series of 0.8 bug fix releases and a 0.9)
o A couple ApacheDS releases (0.9.2 and 0.9.3)
o We are preparing for a 1.0 release candidate around mid January
with most (98%) of the LDAPv3 functionality.
Donations
=======
OpenGroup (http://opengroup.org/) graciously donated their services to
certify ApacheDS for LDAPv3. We intend to certify ApacheDS in 1.1 with
full LDAPv3 support in the 1.2 stable release this summer. CA's eTrust
Directory, IBM's Tivoli, SUN's Java System Directory, Novell's
eDirectory and Oracle's OID are the only LDAPv3 servers that have
passed this certification.
Approved by General Consent.
On the people front we added the following new committers: * Stefan Zoerner * Ersin Er We also added a new member to the PMC who has been a long time committer on the project (since graduation): * Emmanuel Lecharny Besides this we're working towards a 1.0 release as rapidly as we can. We have released two feature releases since our last report: 0.9.1 and 0.9.2. We have a few more of these to go until a 1.0. Generally speaking everything is going well with the project which seems to be growing steadily.
Approved by General Consent.
Community ======= It's been smooth sailing for us at the Directory Project. We have taken our time deciding upon some recent candidates which have been posting patches regularly. The community of contributors and users is growing in a rapid pace. We definitely realize that we have to grow the committership to keep up with the influx of patches and user questions. Our last committer Emmanuel Lecharny turned out to be a heavy hitter so we must be doing something right :). As of our last report 9 different commercial companies have started to integrate Apache Directory Server into their products. This list includes Atlassian for their JIRA and Confluence products. We're excited obviously about this. Technical Strides ========== Within our sandbox is a almost complete rewrite by Emmanuel for our ASN.1 codecs which should be 5x faster than what we have in place today. We also have an OSGi version of the server sitting in the sandbox ready to be unleashed. We have standardized our logging and have stabilized several aspects of the server and our networking layer (MINA): o MINA 0.7.3 has been released o Apache Directory Server has been completely refactored with imminent 0.9.1 release o Removed AspectJ dependency in ApacheDS o Preparing to use OSGi based container for ApDS o Preparing to switch to new ASN.1 libraries in releases subsequent to 0.9.3
Some very positive things to note otherwise all is well ... Website Revamped ------------------------- Because we were planning for our first release out of the incubator we really wanted all the peices of the server to meet some fundamental requirements on the new TLP's website. This is in respect to the documentation obviously but specifically we cleaned up several links, comments, old materials as well as the expected references to the incubator. ApacheDS 0.9 Released ------------------------------- Perhaps the most significant news is another release of ApacheDS (version 0.9). The 0.9 series of releases are experimental feature releases. This one includes the Kerberos plugin which can be enabled to make the server service Kerberos 5 requests with users backed in the directory. This is all in addition to the existing LDAP support. Other releases will come rapidly after this one to include an NTP, and DNS plugin.
Apache Directory Project report approved as submitted by general consent.
There are no significant changes since last months report really. Everything is operating smoothly. Some significant notes on our present objectives ... We are trying to get the site up to par with a TLP site outside of the incubator before our next release. That is in terms of quality. We all do not want to draw too much attention until everything is in order for our users. The 0.9 code is ready to go but the docs and site are the only factors holding us back. We really want to make sure everything is right with this first release of apacheds outside of the incubator.
Apache Directory Project report approved as submitted by general consent.
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of an
open-source directory server and naming related software, for
distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Directory PMC", be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further
RESOLVED, that the "Apache Directory PMC" be and hereby is
responsible for the creation and maintenance of a directory
server and naming related software based on software licensed
to the Foundation; and be it further
RESOLVED, that the office of "Vice President, Apache Directory"
be and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Directory PMC, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Directory PMC; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Directory PMC:
Enrique Rodriguez <erodriguez@apache.org>
Phil Steitz <psteitz@apache.org>
Alex Karasulu <akarasulu@apache.org>
Vince Tence <vtence@apache.org>
Trustin Lee <trustin@apache.org>
Brett Porter <brett@apache.org>
Noel J. Bergman <noel@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alex Karasulu be
and hereby is appointed to the office of Vice President, Apache
Directory, to serve in accordance with and subject to the
direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed; and be it
further
RESOLVED, that the initial Apache Directory PMC be and hereby
is tasked with the creation of a set of rules and procedures
intended to encourage open development and increased
participation in the Apache Directory community.
By Unanimous Vote, the above Special Order,
6D: Establish the Apache Directory Project, was approved.
Our last report was posted here:
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=general@incubator.apache.org&msgNo=3919
Since then we have ...
o Vetted all IP issues within the project, namely where Snacc4J was
concerned. Snickers, the Snacc4J replacement subproject, now
supports BER and, in a branch maintained by Alan Cabrera, DER as
well. Alan Cabrera has been progressing on his ASN.1 compiler but
for the time being we have hand coded LDAP stubs. We have also
integrated the new Snickers based LDAP provider as the default BER
codec for the ldap-common project. This is a major step for us on
the path toward exiting the incubator.
o We have retrofitted the old LDAPd code base with the newly modified
ldap-common code along with Snickers. This primitive precursor to
Eve now runs as it did while at sourceforge however there are no IP
issues with this functional server. Users can now kick the tires
on an LDAP server that works. We however see this server as more
of a demo rather than the real deal which will be Eve.
o We have also made progress on another major aspect that demonstrates
the viability of this project: building community. BTW, all new
committers have signed and submitted their CLAs which are on file
and software grants were submitted where appropriate. We have
added three new committers to the project of which two are still
active.
- Trustin Lee joined us to work on the frontend networking code
and is making progress adding UDP support to the new SEDA
subproject. He will be continuing to work on making Eve's
front end code serve as a gateway/proxy server to other LDAP
servers soon.
- Enrique Rodriguez became a committer as well and is working on
the new integrated Kerberos server which plugs into Eve for
network authentication. He is also persuing the goal of
writing wrappers for Eve to embed Eve into OSGi containers.
- Niclas Hedman became a commiter and started work on decoupling
Eve's backend from Merlin, however some Avalon commitments have
taken his time.
o We have begun to pull the backend subsystem out of the sandbox:
this is almost complete. A new schema subsystem design has been
added while making the move. I have also removed all depenencies
on Avalon and Merlin while maintaining the wrappers for Merlin.
o Vincent continues to maintain Janus and is getting into some of the
LDAP code base while writing unit test cases for them. Vincent is
also working on getting all projects rigged into Gump.
o We added two new subprojects. The first is called the SEDA
framework. It is basically the LDAP frontend networking code with
all LDAP dependencies removed so it can run any protocol. In fact
it can run multiple protocols on the same plumbing. This is what
Trustin is working on most of all. The second subproject is a
Kerberos server that Enrique and I had been working on just toying
with from within Eve but it wound up being something very
attractive so we added it to our project rather than leaving it out
there. We don't expect these projects to stay under the directory
umbrella forever. We feel this way especially since SEDA can be
reused anywhere a Java based protocol server is needed and the
Kerberos server can run in stand alone mode one day. Until then we
are comfortable having them here indefinately.
o On the Naming subproject front, Phil Steitz has integrated Naming
with Gump. Phil has been very busy in jakarta-commons working on
getting an excellent new addition, the commons math project, out
the door. Meanwhile he has been supporting inquiries about Naming
and Jira issues posted on it.
Conclusions and goals ...
[We] are doing really well and are very close to our goals. Perhaps
before ApacheCon or by the next status report at the latest we should
have all of Eve's parts up and running. Meanwhile we're growing the
community and getting more comfortable working together to support our
code base. More people are contacting us about various directory
subprojects than before so ... if we build it they will come.
Since the last report: * Alan Cabrera has joined us to write the stub compiler for Snickers. * We have resusitated the original LDAPd code base right before we entered the incubator to have a running server. This is there for people to be able to play around with as server: fire it up and kick the tires. Of course all the package names and other aspects of the server have been adjusted to convey that it is now a part of Apache. * We have begun to focus specifically on Snickers after a recommendation by Nicola and Noel. The goal is to lift this sole IP issue from the project to prepare us to exit the incubator. At the present time the decoder half of the BER codec is complete and working well. We should have the encoder half complete soon since it is already under way. * The server front end is ready and comes up in the new Eve server. The only problem at this point is that it returns busy for every response. This will remain the case until we pull the new backend subsystem out of the sandbox to complete the new server. * Thanks to Vincent we have a new website look and feel using Maven out of the box. We also have been discussing a better ontological organization to the site to reflect the role of our subprojects within the overall effort.
Since the last report: * Alan Cabrera has joined us to write the stub compiler for Snickers. * We have resusitated the original LDAPd code base right before we entered the incubator to have a running server. This is there for people to be able to play around with as server: fire it up and kick the tires. Of course all the package names and other aspects of the server have been adjusted to convey that it is now a part of Apache. * We have begun to focus specifically on Snickers after a recommendation by Nicola and Noel. The goal is to lift this sole IP issue from the project to prepare us to exit the incubator. At the present time the decoder half of the BER codec is complete and working well. We should have the encoder half complete soon since it is already under way. * The server front end is ready and comes up in the new Eve server. The only problem at this point is that it returns busy for every response. This will remain the case until we pull the new backend subsystem out of the sandbox to complete the new server. * Thanks to Vincent we have a new website look and feel using Maven out of the box. We also have been discussing a better ontological organization to the site to reflect the role of our subprojects within the overall effort.