This was extracted (@ 2024-03-20 21: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).
## Description: Empire-db is a lightweight relational database access library dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems (RDBMS). As an alternative to traditional OR-Mapping solutions, it provides an SQL centric, no-compromise approach that uses a Java-Object-Model rather than Mapping Files or Annotations. ## Project Status: Current project status: Ongoing with low activity Issues for the board: none ## Membership Data: Apache Empire-db was founded 2012-01-24 (12 years ago) There are currently 10 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Ralf Eichinger on 2022-03-15. ## Project Activity: Latest release is empire-db-3.1.0 released on 2023-04-22. Given the maturity of the code base there has been little demand for major improvments or new features. However some modules will have to be updated soon due to the Javax to Jakarta Namespace change. ## Community Health: Our community is still alive and healthy albeit low activity with 2 commits from 2 code contributors in the past quarter.
@Christofer: follow up on PMC member private subscriptions
## Description: Empire-db is a lightweight relational database access library dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems (RDBMS). As an alternative to traditional OR-Mapping solutions, it provides an SQL centric, no-compromise approach that uses a Java-Object-Model rather than Mapping Files or Annotations. ## Project Status: Current project status: Ongoing with low activity Issues for the board: none ## Membership Data: Apache Empire-db was founded 2012-01-24 (12 years ago) There are currently 10 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Ralf Eichinger on 2022-03-15. ## Project Activity: Latest release is empire-db-3.1.0 released on 2023-04-22. Given the maturity of the code base and that several fixes and small improvments have been provided with our April release there has not been demand for any major code changes yet. ## Community Health: Our community is still alive and healthy albeit low activity with 3 commits from 3 code contributors and 1 pull requst from github.
## Description: Empire-db is a lightweight relational database access library dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems (RDBMS). As an alternative to traditional OR-Mapping solutions, it provides an SQL centric, no-compromise approach that uses a Java-Object-Model rather than Mapping Files or Annotations. ## Project Status: Current project status: Ongoing with low activity Issues for the board: none ## Membership Data: Apache Empire-db was founded 2012-01-24 (12 years ago) There are currently 10 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Ralf Eichinger on 2022-03-15. ## Project Activity: Latest release is empire-db-3.1.0 released on 2023-04-22. Following our April release there are no crucial open issues and there have only been a few minor changes and fixes since. Concerning the voting on our previous release the board asked the question: "Is there a reason vote threads on new releases are being done on private@ and not on dev@?". Actually the vote request has been issued on both dev@ and private@. Its probably redundant but just in case the chair wanted to make sure that everyone gets notice of the vote. However the board also found, that there is someone on our private@ list who is not part of the PMC. This person should not be on the private@ list and should be removed. Not sure how this is achieved. Any help here is appreciated. ## Community Health: After we have published a new release in April which contained many new features and fixes the previous quarter has been quieter. 4 issues opened in JIRA 1 issue closed in JIRA 7 commits in the past quarter 3 code contributors in the past quarter
## Description: Empire-db is a lightweight relational database access library dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems (RDBMS). As an alternative to traditional OR-Mapping solutions, it provides an SQL centric, no-compromise approach that uses a Java-Object-Model rather than Mapping Files or Annotations. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (11 years ago) There are currently 10 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Ralf Eichinger on 2022-03-15. ## Project Activity: Latest release is empire-db-3.1.0 released on 2023-04-22. This quarter we have successfully prepared and published a new release containing 12 significant improvements and 9 bugfixes. The project website has also been updated to reflect the API improvements. ## Community Health: After a couple of quiet quarters with low activity we had significantly more contributions this quarter as indicated by the activity report numbers: 11 issues opened in JIRA 19 issues closed in JIRA 45 commits in the past quarter from 3 code contributors Even so, we admit that size of our community is small. However, besides the active code contributors there are some passive members who are following our mailing lists and participating in the voting process. Still given the maturity of the project combined with the "old-fashionedness" of the subject (relational databases) it is rather unlikely that we will attract many new committers in the future.
## Description: Empire-db is a lightweight library for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems (RDBMS). As an alternative to traditional OR-Mapping solutions, it provides an SQL centric, no-compromise approach that uses a Java-Object-Model rather than Mapping Files or Annotations. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (11 years ago) There are currently 10 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Ralf Eichinger on 2022-03-15. ## Project Activity: Latest release is empire-db-3.0.0 released on 2022-03-11. There has not been much activity during the last quarter with (only) two new issues opened in JIRA. As soon as a significant number of issues have been fully resolved we are intending to publish a new release, probably within the upcoming two quarters. ## Community Health: Our community, although small, is alive and active. 2 issues opened in JIRA 0 issues closed in JIRA
## Description: Empire-db is a lightweight library for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems (RDBMS). As an alternative to traditional OR-Mapping solutions, it provides an SQL centric, no-compromise approach that uses a Java-Object-Model rather than Mapping Files or Annotations. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (11 years ago) There are currently 10 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Ralf Eichinger on 2022-03-15. ## Project Activity: Latest release is empire-db-3.0.0 released on 2022-03-11. The previous quarter has been rather quiet with one major improvement and some minor improvements and bug fixes. Due to the maturity of the project and a major API overhaul made just in March there are currently no major changes planned. ## Community Health: Our community, although small, is alive and active. 5 issues opened in JIRA 4 issues closed in JIRA
## Description: Empire-db is a lightweight library for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems (RDBMS). As an alternative to traditional OR-Mapping solutions, it provides an SQL centric, no-compromise approach that uses a Java-Object-Model rather than Mapping Files or Annotations. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (11 years ago) There are currently 10 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Ralf Eichinger on 2022-03-15. ## Project Activity: Latest release is empire-db-3.0.0 released on 2022-03-11. After the release of our major new version in the previous quarter, we have now fixed a few minor issues and answered some user questions. Fixes will be collected for an upcoming release. ## Community Health: Our community, although small, is alive and active. 3 issues opened in JIRA 2 issues closed in JIRA
## Description: Empire-db is a library for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems. As an alternative to traditional OR-Mapping solutions it provides an SQL centric, no-compromise approach that uses a Java-Object-Model rather than Mapping Files or Annotations. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (10 years ago) There are currently 10 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - Ralf Eichinger was added as committer on 2022-03-15 ## Project Activity: The previous quarter has been one of the most active in recent years as we have not only completed and released a new major version featuring a full API rework but also published an all new project website. ## Community Health: The community has been particularly active during the final approval of the new version with a lot of activity on all mailing lists and in Jira. The project has also invited and successfully added a new committer for his contribution to the project.
## Description: Empire-db is an object orientated API for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems. With an SQL centric, no-compromise approach Empire-db attempts to makes the full power of the database system available to applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (10 years ago) There are currently 9 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: The previous quarter has been quite busy as we have completed and published out new release that we have prepared for several months. The release has been approved by our community with 6 votes of which 5 were binding. Even more important though, we have created a new branch for a complete API overhaul that is supposed to lead to a new major version 3.x. This is because over the years the API has suffered from various changes and has now some inconsistencies and irregularities which should be resolved. Also the source level should be raised to Java 8 to allow new features to be added (e.g. java.time). Work on this new version has already begun and will hopefully result in another release later this year. ## Releases empire-db-2.5.1 was released on 2022-01-22. ## Community Health: The community is still active. The increased activity is due to the completion of the current release 2.5.1 and work on the new branch for a complete API overhaul 3.x. 10 issues opened in JIRA, past quarter (150% increase) 21 issues closed in JIRA, past quarter (2000% increase) 118 commits in the past quarter (807% increase)
## Description: Empire-db is an object orientated API for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems. With an SQL centric, no-compromise approach Emprie-db attempts to makes the full power of the database system available to applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (10 years ago) There are currently 9 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: Originally it was planned finish and publish our upcoming release 2.5.1. However due to personal circumstances the work could not yet be completed. The chair intends to make another attempt to finish and vote on the upcoming release in December or January. ## Releases empire-db-2.5.0 was released on 2020-05-12. ## Community Health: Community is still active. 4 issues opened in JIRA, past quarter (-20% change) 1 issue closed in JIRA, past quarter (100% increase) 13 commits in the past quarter (-35% change)
## Description: Empire-db is an object orientated API for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems. With an SQL centric, no-compromise approach Emprie-db attempts to makes the full power of the database system available to applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (10 years ago) There are currently 9 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: Work on open and new issues has progressed but not yet completed for an upcoming release. A user request for Spring Boot integration has been made along with an example code that needs to be evaluated. ## Community Health: Community is still active. The last release was in May, 2020. 6 issues opened in JIRA, past quarter 0 issues closed in JIRA, past quarter 15 commits in the past quarter
## Description: Empire-db is an object orientated API for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems. With an SQL centric, no-compromise approach Emprie-db attempts to makes the full power of the database system available to applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (9 years ago) There are currently 9 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: There has been a considerable amount of development activity in the previous quarter with many existing issues resolved and new tickets for improvements created. This raises the possibility for an upcoming new release later this year. ## Community Health: Community is still active. The last release was in May, 2020. 14 issues opened in JIRA 6 issues closed in JIRA
## Description: Empire-db is an object orientated API for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems. With an SQL centric, no-compromise approach Emprie-db attempts to makes the full power of the database system available to applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (9 years ago) There are currently 9 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: The previous quarter has been quiet with little activity which in large part may be due to the maturity of the solution. The last release was in May, 2020. ## Community Health: Community is still active. 3 issues opened in JIRA, past quarter. 0 issues closed in JIRA, past quarter.
## Description: Empire-db is an object orientated API for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems. With an SQL centric, no-compromise approach Emprie-db attempts to makes the full power of the database system available to applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24. There are currently 9 committers and PMC members in this project. One PMC member that was not a committer was removed from the PMC after contacting this member by the chair has failed. ## Project Activity: There have been a few new tickets for improvments and bugfixing that are still in progress. The last release was in May, 2020. ## Community Health: Community is still active. 3 issues opened in JIRA, past quarter (50% increase) 2 issues closed in JIRA, past quarter (100% increase)
## Description: Empire-db aims to provide a sophisticated approach to access SQL based relational database systems and to make the full power of the RDBMS available in applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 There are currently 9 committers and 10 PMC members in this project. The chair does not know why one PMC-member is not a committer and has yet to investigate the issue. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: After publishing our latest release on May 12th there has been very little activity. New issues and actities have yet to be collected. ## Community Health: Community is still active.
## Description: Empire-db aims to provide a sophisticated approach to access SQL based relational database systems and to make the full power of the RDBMS available in applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring the boards attention at this time ## Membership Data: Apache Empire-db was founded 2012-01-24 (8 years ago) There are currently 9 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 9:10. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: We just had our new release 2.5.0 built and approved by committers and will now proceed with publishing the release. ## Community Health: Community is still active with the usual suspects :-) Comming activities are yet to be planned.
## Description: Empire-db aims to provide a sophisticated approach to access SQL based relational database systems and to make the full power of the RDBMS available in applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring board attention at this time ## Membership Data: Apache Empire-db was founded 2012-01-24 (8 years ago) There are currently 9 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 9:10. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: We have now just completed the work on our upcoming release and started a vote to begin with the build and publication process. If no objections arise, we will proceed and publish the release in the coming weeks. ## Community Health: Our existing community is still alive and active, although as we have mentioned before, for a small but mature project which is not about a hot new topic, it is not easy to attract new committers.
## Description: The mission of Empire-db is the creation and maintenance of software related to Relational Data Persistence ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (8 years ago) There are currently 9 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 9:10. Community changes, past quarter: - No new PMC members. Last addition was Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: During the past three months considerable work has been done on the project: 17 issues have been opened in JIRA. 51 commits have been performed by 3 contributors. As soon as the issues have all been resolved and features are complete a new release will be published. ## Community Health: Attracting new committers has not been easy and remains difficult. This may be due to serveral reasons like e.g. relational database access is a rather old subject that is not the most trendy among young developers. Also there is not a lot of change in the underlying relational database systems either. However we acknowledge that especially our website needs more attention and updates. This will probably be done with or after the upcoming release.
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
It encapsulates the functionality of a RDBMS in a powerful, vendor
independent, intuitive and maintenance friendly API providing a maximum of
compile-time-safety.
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- Recently development of the new version 2.5.0 has picked up steam and many
new issues for improvement have been created. With the upcoming release we
want to introduce more dramatic changes and want to improve both
consistency and intuitivity of the API.
## Health report:
- The project remains healthy.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was empire-db-2.4.7 on Wed Oct 31 2018
## Mailing list activity:
- dev@empire-db.apache.org:
- 31 subscribers (down -2 in the last 3 months):
- 43 emails sent to list (1 in previous quarter)
- user@empire-db.apache.org:
- 51 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (1 in previous quarter)
## JIRA activity:
- 16 JIRA tickets created in the last 3 months
- 12 JIRA tickets closed/resolved in the last 3 months
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
It encapsulates the functionality of a RDBMS in a powerful, vendor
independent, intuitive and maintenance friendly API providing a maximum of
compile-time-safety.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Frankly there has been no activity during the last quarter. Due to its
maturity, no bugs were reported. However the PMC is aware, that there is
work to do to improve the project visibitly and popularity.
## Health report:
- The project remains healthy.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was empire-db-2.4.7 on Wed Oct 31 2018
## Mailing list activity:
- dev@empire-db.apache.org:
- 33 subscribers (down -1 in the last 3 months):
- 1 emails sent to list (16 in previous quarter)
- user@empire-db.apache.org:
- 51 subscribers (down -3 in the last 3 months):
- 1 emails sent to list (0 in previous quarter)
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
It encapsulates the functionality of a RDBMS in a powerful, vendor
independent, intuitive and maintenance friendly API providing a maximum of
compile-time-safety.
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- After having released version 2.4.7 last October we had to deal with issues
regarding database compatibility, especially regarding new versions of
Microsoft SQL-Server newer than 2016, which have been requested from users
over JIRA. Regarding JIRA we have found, that the mailing notifications had
been incorrect, which we asked INFRA to correct. Also we had to deal with
the mandatory migration of the GIT repository from git-wip-us.apache.org to
gitbox.apache.org.
## Health report:
- The project remains healthy as activity in JIRA shows.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was empire-db-2.4.7 on Wed Oct 31 2018
## Mailing list activity:
- dev@empire-db.apache.org:
- 34 subscribers (down -1 in the last 3 months):
- 15 emails sent to list (45 in previous quarter)
- user@empire-db.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (2 in previous quarter)
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
It encapsulates the functionality of a RDBMS in a powerful, vendor
independent, intuitive and maintenance friendly API providing a maximum of
compile-time-safety.
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- This quarter we have completed our work on release 2.4.7 which we have
finally published on Oct 31. The release contains 9 bugfixes and 18
improvements. The main new feature is a template that can be used
to build clients using the JavaScript framework vue and a REST server
backend utilizing database metadata.
## Health report:
- The project remains healthy. There are about 5 committers who
contribute to the project and who have approved the release.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- empire-db-2.4.7 was released on Wed Oct 31 2018
## Mailing list activity:
- dev@empire-db.apache.org:
- 36 subscribers (up 0 in the last 3 months):
- 45 emails sent to list (6 in previous quarter)
- user@empire-db.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (3 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 27 JIRA tickets closed/resolved in the last 3 months
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
It encapsulates the functionality of a RDBMS in a powerful, vendor
independent, intuitive and maintenance friendly API providing a maximum of
compile-time-safety.
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- Activity has been low partially due to holidays, but we have had some fixes
and improvements. We are about to publish a new release within the next
three months.
## Health report:
- The project remains healthy.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was 2.4.6 on Tue Jan 17 2017
## Mailing list activity:
- dev@empire-db.apache.org:
- 36 subscribers (up 0 in the last 3 months):
- 6 emails sent to list (20 in previous quarter)
- user@empire-db.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 3 emails sent to list (6 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
It encapsulates the functionality of a RDBMS in a powerful, vendor
independent, intuitive and maintenance friendly API providing a maximum of
compile-time-safety.
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- Again, we have worked on fixes and received various improvements which we
plan to publish with a new release later this year.
- Work on the redesign of our website has not yet started due to lack of time
of the chair (and possibly others).
## Health report:
- The project remains healthy.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was 2.4.6 on Tue Jan 17 2017
## Mailing list activity:
- dev@empire-db.apache.org:
- 36 subscribers (down -1 in the last 3 months):
- 19 emails sent to list (25 in previous quarter)
- user@empire-db.apache.org:
- 54 subscribers (down -1 in the last 3 months):
- 6 emails sent to list (1 in previous quarter)
## JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Several code improvements and one bugfix have been submitted since the last
report
- One committer has submitted a new example project that demonstrates how to
utilize empire-db data model metadata with a JavaScript application
frontend built with vue.js and a REST Service. However, this projects needs
to be further worked on before it can be released
- We have set two major goals for 2018 which might help to possibly attract
new users and committers: First we want to publish a new release to
include the various improvements and bugfixes that have been collected since
our last release. Second the project website should finally be redesigned in
2018 to make it more attractive to users, both regarding design and
information content.
## Health report:
- The project remains healthy albeit low activity. As requested by the board
last time, we have asked PMC-members on the private list to confirm whether
or not they are still active an engaged with the project. Seven members
(including the chair) have responded, but three members have said that while
they would still read emails, they are not actively engaged any more.
Four members (Jan, Dimitar, Ivan and Rainer) have said to be still engaged
with the project. We are aware that those numbers are not great and that we
have to find ways to attract new committers again.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was 2.4.6 on Tue Jan 17 2017
## Mailing list activity:
- dev@empire-db.apache.org:
- 37 subscribers (down -1 in the last 3 months):
- 26 emails sent to list (2 in previous quarter)
- user@empire-db.apache.org:
- 55 subscribers (down -1 in the last 3 months):
- 1 emails sent to list (0 in previous quarter)
## JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- There has been activity in providing bugfixes, feature improvements
and answering user questions.
- The project is mature and there seems to be currently little demand by the
committers or users to undertake major changes. The chair intends new to ask
committers about where the project should be heading. Unfortunately the
chair has been too busy recently to already have started such a discussion.
## Answers to comments made by Board members to our last report
Mark Thomas: "It has been a while since the last committer was added. Are
there any prospects on the horizon?"
- Whenever we are notified of suggestions for improvement other than simple
bugfixes we guide people to a possible solution and encourage them to
provide us with their code that solves their problem and make a
contribution. However there has not been enough feedback recently that made
us believe that there is a willingness by someone to engage in the project
and really bring the project forward. This may also be due to the fact that
rdbms and sql have been around for so long, that there is little change on
the rdbms side and hence there is little demand for big changes or
improvements in our code base. So to be frank, at the moment there are no
good prospects for new comitters.
## Health report:
- The project remains healthy although activity has been low this quarter.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was 2.4.6 on Tue Jan 17 2017
## Mailing list activity:
- dev@empire-db.apache.org:
- 38 subscribers (up 1 in the last 3 months):
- 2 emails sent to list (7 in previous quarter)
- user@empire-db.apache.org:
- 56 subscribers (up 1 in the last 3 months):
- 0 emails sent to list (9 in previous quarter)
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in comparison to traditional OR-Mappers
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- This quarter we have created new tickets for improvements in order
to make our the code more robust and to support new features in the
latest version of the SQL-Server DBMS and have already partially
resolved some of those issues.
- Additionally some bugs reported by users or committers have been
resolved and user questions have been answered.
## Health report:
- The project remains healthy. Activity levels on mailing lists, git and
JIRA are low but constant among the existing community.
- However it is acknowledged that in order to attract new user and
committers an overhaul of the website and the documentation is necessary.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was 2.4.6 on Tue Jan 17 2017
## Mailing list activity:
- dev@empire-db.apache.org:
- 37 subscribers (up 0 in the last 3 months):
- 7 emails sent to list (1 in previous quarter)
- user@empire-db.apache.org:
- 55 subscribers (up 1 in the last 3 months):
- 9 emails sent to list (2 in previous quarter)
## JIRA activity:
- 9 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in comparison to traditional OR-Mappers
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- No significant activities have been performed this quarter
We apologize for being late with the report.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- 2.4.6 was released on Tue Jan 17 2017
## Mailing list activity:
- Latest release of Jan 17 appears to be stable and mature
hence activity has been low.
- dev@empire-db.apache.org:
- 37 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (49 in previous quarter)
- user@empire-db.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (6 in previous quarter)
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in comparison to traditional OR-Mappers
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Since the last board report we have approved and released version 2.4.6
- We have also updated and documented the release procedure
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- 2.4.6 was released on Tue Jan 17 2017
## Mailing list activity:
- dev@empire-db.apache.org:
- 37 subscribers (up 0 in the last 3 months):
- 48 emails sent to list (30 in previous quarter)
- user@empire-db.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 5 emails sent to list (10 in previous quarter)
## JIRA activity:
- 5 JIRA tickets created in the last 3 months
- 4 JIRA tickets closed/resolved in the last 3 months
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project --------------------------- We have completed the work for our upcoming release and are currently voting on a release candidate. Changes in committers or PMC members -------------------------------------------------- There have been no changes in committers or PMC members during the last months. Issues -------- There are no issues that require the board's attention at this time. Releases ----------- Latest release was Apache-Empire-db 2.4.4 released on 19/Aug/2015.
Empire-db board report August 2016 Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. # Progress of the project Over the last months we have collected various improvements and some new features that will justify the publication of a new release. # Changes in committers or PMC members This quarter we have promoted 3 committers who have not been pmc members to become members of our pmc. # Issues There are no issues that require the board's attention at this time. # Releases Latest release was Apache-Empire-db 2.4.4 released on 19/Aug/2015.
WHEREAS, the Board of Directors heretofore appointed Francis De Brabandere (francisdb) to the office of Vice President, Apache Empire-db, and WHEREAS, the Board of Directors is in receipt of the resignation of Francis De Brabandere from the office of Vice President, Apache Empire-db, and WHEREAS, the Project Management Committee of the Apache Empire-db project has chosen by vote to recommend Rainer Döbele (doebele) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Francis De Brabandere is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Empire-db, and BE IT FURTHER RESOLVED, that Rainer Döbele be and hereby is appointed to the office of Vice President, Apache Empire-db, 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, Change the Apache Empire-db Project Chair, was approved by Unanimous Vote of the directors present.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project Committers have been working on updating components to newer versions JEE components. There will be a new release after those changes have been completed. Changes in committers or PMC members Our current chair has announced to step down. There has been a vote for a new chair who has been confirmed by the PMC members. Acceptance by the board is still pending. Issues There are no issues that require the board's attention at this time. Releases Latest release was Apache-Empire-db 2.4.4 released on 19/Aug/2015.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project The project progresses at it's rather slow but steady pace. Our new committers both contributed since last report. Changes in committers or PMC members No changes since last report. Our chair has indicated that he wishes to step down so we plan to have a change of pmc chair resolution in the next report. Issues There are no issues that require the board's attention at this time. Releases Latest release was Apache-Empire-db 2.4.4 released on 19/Aug/2015.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project We had a bad health score of -7.55 'URGENT ACTION REQUIRED' and took action. Part of that low score was due too technical issues with our project name containing a dash. Further we decided to invite 2 extra committers to the project. We are happy to report that this brought more activity to the project and our score is now 3.47 'Healthy' Changes in committers or PMC members 2 committers were invited and accepted: Jan Glaubitz Ivan Nemeth Issues While discussing the score issue Benson Margulies mentioned this: I recommend taking the bull by the horns and having your chair call into the next board meeting and asking them, point blank, if they are unhappy. If not, things continue as they are. I predict that so long as you remain an active, responsive, group, large enough to have release votes, that the board will be contented. Therefore we explicitly ask the board if there are any concerns regarding our project and it's rather low membership count and moderate activity level. Releases Latest release was Apache-Empire-db 2.4.4 released on 19/Aug/2015.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project In the past three month we have received several contributions from new users as well as suggestions for improvements and some bug reports. We have already added the contributions to the project trunk and we have added some more improvements and fixes. At the moment we are in the process of preparing a new release. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time. Releases The vote for Apache-Empire-db 2.4.4 is currently awaiting acceptance. Latest release was Apache-Empire-db 2.4.3 released on 20/Aug/2014.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project We switched from svn to git as we heard from other projects that it lowers the barrier for sending patches. Further we got a really useful patch submitted by a community member that we are currently integrating. A release should be following soon. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time. Releases No releases since last report. Latest release was Apache-Empire-db 2.4.3 released on 20/Aug/2014.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project With our latest stable release there has been little demand for changes of the codebase during the past three months. However the documentation on the web page has been extended describing how to generate code from an existing database. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time. Releases No releases since last report. Latest release was Apache-Empire-db 2.4.3 released on 20/Aug/2014
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project The project keeps getting attention from new users, although at a slow rate. We also see a lot of value in the fact that Empire-DB is easily extendible which allows users to adapt it to their needs without the need for a new release. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time. Releases No releases since last report. Latest release was Apache-Empire-db 2.4.3 released on 20/Aug/2014
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project During the last three months we have worked on a new release with contains several bugfixes and improvements. The release was approved and published on 20/Aug/2014. We have also received suggestions and code contributions from uses which we will evaluate and integrate in an upcoming release. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time. Releases Apache-Empire-db 2.4.3 released on 20/Aug/2014
No report was submitted.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project During the last three months there have been no noteworthy changes to the project. The project team is answering user questions and provides small improvements which are collected for an upcoming release. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time. Releases NONE
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project The last three months have been quite calm, nothing specific to mention. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time. Releases NONE
AI: Chris: follow up with Empire-db
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Project Status After several improvements and bugfixes have been accomplished during the recent months, we have published a new release on October, 16th. Some more complex decisions have been postponed for a further release. Changes in committers or PMC members No committers have joined or left the project. Issues There are no issues that require the board's attention at this time. Latest Release Apache-Empire-db 2.4.2 was released on Oct 16, 2013.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Project Status We have not seen a lot of activity lately, could be related the holidays and the fact that the project is quite mature. Changes in committers or PMC members No changes to report. Issues There are no issues that require the board's attention at this time. Latest Release Apache-Empire-db 2.4.1 was released on Oct 30, 2012.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Project Status During the previous months we have submitted several minor bug fixes and small improvements that we will publish with our next release. The overall code base however is very stable and mature and there has been no demand for major changes. Changes in committers or PMC members After several contributions last year prior to our current release, we have decided to accept Dimitar Simeonov as a new committer on our project. Issues There are no issues that require the board's attention at this time. Latest Release Apache-Empire-db 2.4.1 was released on Oct 30, 2012.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project With our release last November many issues have been resolved and we are now collecting new issues and ideas for future development. Mailing list traffic was low, probably because of the holidays. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time. Releases NONE
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project During recent months we have worked on an extension module that works as a bridge for web applications based on Java Server Faces (JSF) version 2.x or later. This simplifies and enhances JSF development significantly, since meta-data provided from the model is directly available in the business and view layer, reducing redundancies. This module had been initially released 3 months ago as part of release 2.4.0 and has now been significantly improved with our latest release 2.4.1 that was published on October 30th. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time. Releases Apache-Empire-db 2.4.1 was released on Oct 30, 2012.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project Apache Empire-db became a TLP in January 2012. We have published our first top-level release last April and our next release has just been successfully voted. Our user community is slowly growing and we regularly receive useful contributions. Further we have a new integration module with example code that should help us get a broader adoption. Changes in committers or PMC members There have been no changes in committers or PMC members during the last months. Issues There are no issues that require the board's attention at this time.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project Apache Empire-db became a TLP in January 2012 and the migration process has been fully completed. After we have published our first top-level release last month we have begun with the development of new features. As the core component is largely stable and mature our goal is to provide assistance to use Empire-db in a wider range of application scenarios - especially in combination with common front-end frameworks. Changes in committers or PMC members There have been no changes in committers or PMC members during the last month. Issues There are no issues that require the board's attention at this time.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project Apache Empire-db became a TLP in January 2012. The migration from the incubator has been completed. We just shipped our first Apache Empire-db top-level release and since this is our third monthly report we can now switch to a quarterly reporting schedule. Changes in committers or PMC members Benson Margulies was added as PMC member. Benson has been with us for a long time as mentor in the Incubator and we somehow forgot to add him to our graduation resolution. Issues There are no issues that require the board's attention at this time. Releases Apache-Empire-db 2.3.0 was released on 02 Apr 2012, this is our first top-level release.
Apache Empire-db Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project Apache Empire-db became a TLP in January 2012. The migration from the incubator has been completed, our website was updated to reflect the changes. We are now working towards a first TLP release, this will probably take a bit longer than usual as we have to update our release process guide. The release should be out before next board report. Changes in committers or PMC members There have been no changes in Committers since our TLP graduation in February 2012 Issues There are no issues that require the board's attention at this time. Releases No releases as TLP yet
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Progress of the project Apache Empire-db became a TLP in January 2012. We are still busy migrating the project to TLP infrastructure, mostly because of lack of time of our project chair but this should be solved by our next report. Issues There are no issues that require the board's attention at this time. Releases No releases as TLP yet
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 open-source software related to api-based SQL generation and utilization of RDBMS features, 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 Empire-db Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Empire-db Project be and hereby is responsible for the creation and maintenance of software related to api-based SQL generation and utilization of RDBMS features; and be it further RESOLVED, that the office of "Vice President, Apache Empire-db" 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 Empire-db Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Empire-db Project; 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 Empire-db Project: * Martijn Dashorst <dashorst@apache.org> * Francis De Brabandere <francisdb@apache.org> * Rainer Döbele <doebele@apache.org> * Eike Kettner <ek@apache.org> * Jörg Reiher <reiher@apache.org> * Benjamin Venditti <benniven@apache.org> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Francis De Brabandere be appointed to the office of Vice President, Apache Empire-db, 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 Empire-db PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Empire-db Project; and be it further RESOLVED, that the Apache Empire-db Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Empire-db podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Empire-db podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7C, Establish the Apache Empire-db Project, was approved by Unanimous Vote of the directors present.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Empire-db has entered Incubation in August 2008. Activity since last report: * Last month we voted for graduation, submitted our resolution which was revoked because of a copy-paste issue * A fixed resolution will be submitted for this month's board meeting
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 open-source software related to fully distributed storage of structured data, 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 Empire-db Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Empire-db Project be and hereby is responsible for the creation and maintenance of software related to api-based SQL generation and utilization of RDBMS features; and be it further RESOLVED, that the office of "Vice President, Apache Empire-db" 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 Empire-db Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Empire-db Project; 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 Empire-db Project: * Martijn Dashorst <dashorst@apache.org> * Francis De Brabandere <francisdb@apache.org> * Rainer Döbele <doebele@apache.org> * Eike Kettner <ek@apache.org> * Jörg Reiher <reiher@apache.org> * Benjamin Venditti <benniven@apache.org> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Francis De Brabandere be appointed to the office of Vice President, Apache Empire-db, 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 Empire-db PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Empire-db Project; and be it further RESOLVED, that the Apache Empire-db Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Empire-db podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Empire-db podling encumbered upon the Apache Incubator Project are hereafter discharged Special Order 7C, Establish the Apache Empire-db Project, tabled due to inconsistent wording.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Empire-db has entered Incubation in August 2008. Activity since last report: * a lot of work on the code has been done in order to address architectural changes that may significantly improve the ease-of-use and robustness of the code. These changes have been the biggest core code changes since incubation. * Testing of the new features and preparation of a new release are in progress Community * many of our committers have worked and contributed to this upcoming release especially all new committers that have joined the project since incubation. This gives us confidence that community improvements are slow but steady and that once people have learned about the benefits of Empire-db they will stick to it. * requests of new users on mailing lists have been answered and problems have been solved. Top priorities prior to graduation: * Finish and publish the release * Go out and advertise the benefits of Empire-db in general and the advantages of the new features in particular
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Empire-db has entered Incubation in August 2008. After having published our 2.1.0 release in April, things went a bit slower during the last quarter. Recently our committers have fixed smaller issues and we have made the Empire-db code base available on git. We regularly receive user requests on our user list asking for help and or improvements. Some users submitted small patches through Jira. For the next term we have planned to start a major API improvement which might help making Empire-db attractive for even more users. In order to graduate we still need to increase awareness of the project through various channels in order to grow our community. This means participating in blogs and write our own articles. We will set up a discussion on how exactly our communication can be improved.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Empire-db has entered Incubation in August 2008. Activity since last report: - We have successfully completed and published our 2.1.0 release with few but major improvements. - We have increased your community by taking on a new long-time contributor as a new committer. Important issues to address for graduation: We still need more contributors and more attention in the Java community. Recently we experience increased traffic on the user lists and there are plenty of plans on the development side. The challenge will be to keep users interested and let them participate in the development process.
Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Project development since the last report Last December we have finished and published release 2.0.7 that features some minor improvements and bug fixes. Currently we are working on release 2.1.0 with more significant improvements. Issues to address in the move towards graduation and community development After now being 2 and a half years in the incubator we have managed to successfully implement and establish the Apache development and release cycle, we have published several releases and we have received good feedback from users who are subscribed to the dev and user lists. However during all this time, we have still not managed to get ourselves known to a wider audience and to get a significant amount of public attention, most certainly due to the fact that have not managed to work on publicity as much as on code. Also our community currently consists of only 3 active committers that are regularly contributing to the project. For this reason questions about the future of the project and whether we will ever be able to graduate have been raised. While the remaining active committers are determined to continue their project commitment and to work towards graduation it is still unclear by which measures new committers can be won to join the project. Hence, for the coming months answering this question and establishing the corresponding measures should be our focus. One way of answering this question could be to move this discussion to the dev list in order to find out how our subscribers feel about the status of the project. Also it might make sense to combine the user and dev lists in order to prevent subscribers from missing information and getting them more involved in the project.
Apache Empire-db is an Open Source relational data persistence component which allows database vendor independent dynamic query definition as well as safe and simple data retrieval and updating. Empire-db entered the incubator on July 8th, 2008 After a slow start things have been picked up: CLAs have been submitted, accounts have been created, the status page is up and running, the podling website is online and the initial code has been imported. The mailinglists are booting up, and we're learning how to use each list (i.e. ppmc communication only for private matters on private@).