This was extracted (@ 2024-11-19 16: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).
WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache ESME project due to inactivity NOW, THEREFORE, BE IT RESOLVED, that the Apache ESME project is hereby terminated; and be it further RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache ESME Project; and be it further RESOLVED, that the office of "Vice President, Apache ESME" is hereby terminated; and be it further RESOLVED, that the Apache ESME PMC is hereby terminated. Special Order 7A, Termination of the ESME PMC, was approved by Unanimous Vote of the directors present.
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-08-29 1.3 Development: The level of development activity has decreased dramatically the last year. In the last quarter, we had no commits. Community: * No new committers * No new PMC members. Issues: No Board level issues at this time TRADEMARKS / BRANDING * Project Naming And Descriptions : use proper Apache forms, describe product, etc -> Done * Website Navigation Links : navbar links included, link to www.apache.org included -> Done * Trademark Attributions : attribution for all ASF marks included in footers, etc. -> Done * Logos and Graphics : include TM, use consistent product logo on your site -> In progress * Project Metadata : DOAP file checked-in and up to date -> Done
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-08-29 1.3 Development: We are continuing work on our 1.4 release. We hope to focus on Akka and Apache Camel integration. The level of development activity has decreased dramatically the last year. In the last quarter, we had no commits. Community: * No new committers * No new PMC members. Issues: No Board level issues at this time TRADEMARKS / BRANDING * Project Naming And Descriptions : use proper Apache forms, describe product, etc -> Done * Website Navigation Links : navbar links included, link to www.apache.org included -> Done * Trademark Attributions : attribution for all ASF marks included in footers, etc. -> Done * Logos and Graphics : include TM, use consistent product logo on your site -> In progress * Project Metadata : DOAP file checked-in and up to date -> Done
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-08-29 1.3 Development: We are continuing work on our 1.4 release. We hope to focus on Akka and Apache Camel integration. The level of development activity has decreased dramatically the last year. In the last quarter, we just had a few commits dealing with newer issues. We are trying to refresh the community with new developers but this is proving more difficult than expected. Community: * No new committers * No new PMC members. Issues: No Board level issues at this time TRADEMARKS / BRANDING * Project Naming And Descriptions : use proper Apache forms, describe product, etc -> Done * Website Navigation Links : navbar links included, link to www.apache.org included -> Done * Trademark Attributions : attribution for all ASF marks included in footers, etc. -> Done * Logos and Graphics : include TM, use consistent product logo on your site -> In progress * Project Metadata : DOAP file checked-in and up to date -> Done
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-08-29 1.3 Development: We are continuing work on our 1.4 release. We hope to focus on Akka and Apache Camel integration. The level of development activity has remained stable the last 3 months We just had a few commits dealing with the 1.4 release. We are trying to refresh the community with new developers but this is proving more difficult than expected. We started a mail thread about future developments of the project which received a few responses but it looks like the project will remain on the back-burner for a while. Community: * No new committers * No new PMC members. Issues: No Board level issues at this time TRADEMARKS / BRANDING * Project Naming And Descriptions : use proper Apache forms, describe product, etc -> Done * Website Navigation Links : navbar links included, link to www.apache.org included -> Done * Trademark Attributions : attribution for all ASF marks included in footers, etc. -> Done * Logos and Graphics : include TM, use consistent product logo on your site -> In progress * Project Metadata : DOAP file checked-in and up to date -> Done
(ESME)
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-08-29 1.3 Development: We are continuing work on our 1.4 release. We hope to focus on Akka and Apache Camel integration. The level of development activity has decreased dramatically the last 3 months. We just had a few commits dealing with older issues. We are trying to refresh the community with new developers but this is proving more difficult than expected. Community: * No new committers * No new PMC members. Issues: No Board level issues at this time TRADEMARKS / BRANDING * Project Naming And Descriptions : use proper Apache forms, describe product, etc -> Done * Website Navigation Links : navbar links included, link to www.apache.org included -> Done * Trademark Attributions : attribution for all ASF marks included in footers, etc. -> Done * Logos and Graphics : include TM, use consistent product logo on your site -> In progress * Project Metadata : DOAP file checked-in and up to date -> Done
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-08-29 1.3 Development: We are continuing work on our 1.4 release. We hope to focus on Akka and Apache Camel integration. The level of development activity has decreased dramatically the last 1.5 months. We hope to increase the level of activity this quarter. Community: * No new committers * No new PMC members. Issues: No Board level issues at this time TRADEMARKS / BRANDING * Project Naming And Descriptions : use proper Apache forms, describe product, etc -> Done * Website Navigation Links : navbar links included, link to www.apache.org included -> Done * Trademark Attributions : attribution for all ASF marks included in footers, etc. -> Done * Logos and Graphics : include TM, use consistent product logo on your site -> In progress * Project Metadata : DOAP file checked-in and up to date -> Done
There have been no new committers in the past year. Might be a red flag.
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-08-29 1.3 Development: We have started work on our 1.4 release. We hope to focus on Akka and Apache Camel integration. Community: No changes Finished transition of site to CMS. Issues: No Board level issues at this time TRADEMARKS / BRANDING * Project Naming And Descriptions : use proper Apache forms, describe product, etc -> Done * Website Navigation Links : navbar links included, link to www.apache.org included -> Done * Trademark Attributions : attribution for all ASF marks included in footers, etc. -> Done * Logos and Graphics : include TM, use consistent product logo on your site -> In progress * Project Metadata : DOAP file checked-in and up to date -> Done
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-03-14 1.2 Development: We are continuing work on our 1.3 release. We just have 2 JIRA items for this release that are still open. Community: No changes Right now, we are struggling to complete the transition of our site from wiki to Apache CMS. Issues: No Board level issues at this time TRADEMARKS / BRANDING * Project Naming And Descriptions : use proper Apache forms, describe product, etc -> In progress * Website Navigation Links : navbar links included, link to www.apache.org included -> In progress * Trademark Attributions : attribution for all ASF marks included in footers, etc. -> In progress * Logos and Graphics : include TM, use consistent product logo on your site -> In progress * Project Metadata : DOAP file checked-in and up to date -> Done
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-03-14 1.2 Development: We are continuing work on our 1.3 release. New committer Vladimir Ivanov has implemented container-based authentication and LDAP authorization - two features that users have often requested. Community: No changes Issues: No Board level issues at this time
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Releases: 2011-03-14 1.2 2010-10-09 1.1 (Incubator - last release) Development: We are starting work on our 1.3 release. Community: New committer and new PMC member - Vladimir Ivanov Issues: No Board level issues at this time
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Moving to TLP: ESME graduated from the Incubator in December 2010. The majority of the items on the Incubator transfer to TLP list have been completed but not all. We are still using the wiki-based export as our main site but are working on the CMS-based site. We've also been discussing branding and have selected a new icon to reflect our new TLP status. We are also publishing blogs on the Apache blog site [1] that focus on aspects of ESME that are of interest to other developers. Releases: none yet (as a TLP) 2010-10-09 1.1 (Incubator - last release) Development: We are pushing towards our 1.2 release and are learning how best to use the new functionality (Grasshopper, etc) provided by the JIRA version change. We are now using Scala Code Coverage Tool (SCCT) [2] to improve the quality of our tests. Community: No changes Issues: No Board level issues at this time [1] https://blogs.apache.org/esme [2] https://blogs.apache.org/esme/entry/using_scala_code_coverage_tool
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. Moving to TLP: Apache ESME graduated from the incubator last month. This is its first report to the Board. The top level project infrastructure was set up on December 21th, and SVN was moved on December 23. Our web-site has been moved to the TLP position. Our website is currently Confluence-based. We are working with INFRA to migrate to Apache CMS. We also have a non-Apache blog [1] that we are no longer using in order to focus on our new Apache blog [2]. We have more work to do to complete the move to a TLP, including removing the incubation notices and making a first release as a TLP. Releases: none yet (as a TLP) 2010-10-09 1.1 (Incubator - last release) Development: It was relatively quiet during the first part of the month, as we were awaiting our move from the incubator to become a TLP. Subsequently, there has been lots of activity to complete TLP migration. We are currently working on our 1.2 release. A significant number of issues remain in Jira, postponed from the last release. There has been some progress on these, and a few new ones have been raised. Community: No changes Issues: No Board level issues at this time [1] http://blog.esme.us [2] http://blogs.apache.org/esme
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 collaborative messaging systems 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 ESME Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache ESME Project be and hereby is responsible for the creation and maintenance of software related to collaborative messaging systems; and be it further RESOLVED, that the office of "Vice President, Apache ESME" 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 ESME Project, and to have primary responsibility for management of the project within the scope of responsibility of the Apache ESME 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 ESME Project: * Anne Kathrine Petteroe akpetteroe@apache.org * Darren Hague dhague@apache.org * Ethan Jewett esjewett@apache.org * Mrinal Wadhwa mrinal@apache.org * Richard Hirsch rhirsch@apache.org * Vassil Dichev vdichev@apache.org * Imtiaz Ahmed H E imtiaz@apache.org * Bertrand Delacretaz bdelacretaz@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Hirsch be appointed to the office of Vice President, Apache ESME, 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 ESME 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 ESME Project; and be it further RESOLVED, that the Apache ESME Project be and hereby is tasked with the migration and rationalization of the Apache Incubator ESME podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator ESME podling encumbered upon the Apache Incubator Project are hereafter discharged. Approved unanimously by roll call vote.
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * Successful graduation votes on esme-dev and general@incubator * "Proposed Resolution to Establish TLP" email sent to Apache Board * Planning for Release 1.2 The following items are planned for the next reporting period: * Enjoy life as a TLP (Hopefully :->) Top 2 or 3 things to resolve prior to graduation * Increase community involvement in the project
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * A new committer - Imtiaz Ahmed H E - has joined the team * Final preparations for Release 1.1 with 77 completed JIRA issues! * Planning for Release 1.2 The following items are planned for the next reporting period: * Completion of Release 1.1 * Development work on Release 1.2 Top 2 or 3 things to resolve prior to graduation * Increase community involvement in the project * Another Apache release
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * Finally got our new UI up and running which is the foundation of next release * Users from various enterprises are using ESME in test installations * Received some patches from a new contributor in the last few weeks. The following items are planned for the next reporting period: * Next release based on UI code * Other types of authentication * Integrate Stax deployment in daily Hudson builds (more difficult than expected) Top 2 or 3 things to resolve prior to graduation * Increase community involvement in the project * Multiple Apache releases
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * Ethan Jewett was accepted as an Apache committer. * Completion of our first release (1.0 RC1) was our main focus. This included getting the code-base release-ready, learning how to cut releases and communicating on release goals / process within the community. * Dealt with a legal issue involving a committer not wanting to remove copyright information. Solved after long discussions on the apache-legal and esme-dev mailing lists (thanks to all involved!) * Started working on defining the JIRA items for the next release * Collaboration with various Apache-external groups (Thingamy, SAP's All-In-One) * Users from various enterprises are using ESME in test installations The following items are planned for the next reporting period: * Work on new UI * Further releases * Integrate Stax deployment in daily Hudson builds Top 2 or 3 things to resolve prior to graduation * Increase community involvement in the project * Multiple Apache releases
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * Activity on the mailing list has increased dramatically * The Apache wiki is full of content and used widely * We have at least 4 new contributors adding code on a daily (almost) basis. * Professional performance tests have been assisting us to find memory problems * Use of Apache Hudson for daily builds * Started defining the Jira items necessary for a first release * Great deal of media attention - based on Chatter announcement from SalesForce * Collaboration with various Apache-external groups (#ubimic, akibot, etc.) * Collaboration with OFBiz regarding integration of ESME into the application * Users from various enterprises are using ESME in test installations The following items are planned for the next reporting period: * Work on new UI * Hopefully, our first release Top 2 or 3 things to resolve prior to graduation * Move all collaboration to the esme-dev mailing list * Increase community involvement in the project * Multiple Apache releases
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * Creation of Apache Wiki as Podling's main web site - replacing old forrest site. This is an ongoing task but is off to a good start. * Dick Hirsch was accepted as an Apache committer. * Implementation of access pools in main branch * Creation of branch to deal with access pools prototype * Started work on new UI * Patch committed from new developer The following items are planned for the next reporting period: * Continue work on wiki and move more content from mailing list to the wiki * Work on new UI Top 2 or 3 things to resolve prior to graduation * Move all collaboration to the esme-dev mailing list * Increase community involvement in the project * First Apache release
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * Creation of initial draft of Apache Wiki * Dick Hirsch has successfully submitted his Apache CLA * Worked on cleaning up code with a focus on better separation of UI and server code * Creation of branch to deal with access pools prototype The following items are planned for the next reporting period: * Finish work on Apache wiki and replace old forrest site * Merge access pool branch into trunk * Work on new UI Top 2 or 3 things to resolve prior to graduation * Move all collaboration to the esme-dev mailing list * Increase community involvement in the project * Provide instructions for people to build, install and evaluate EMSE by themselves
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. Community: * Additional community members have submitted their iCLA with the aim of becoming more involved * Siemens press release about ESME, reviewed by the Apache PRC and published at http://url.ie/1bjo Development: * Somewhat reduced activity last month, and questioning as to why this is happening. * Good progress on the Twitter API, implementation nearly finished. Top 2 or 3 things to resolve prior to graduation * Move all collaboration to the esme-dev mailing list * Increase community involvement in the project * Provide instructions for people to build, install and evaluate EMSE by themselves
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * Inclusion of other existing svn branches (actions, etc.) from Google Code into Apache SVN trunk * Anne Kathrine Petteroe elected as a committer * Completion of first development sprint * Transfer of existing issues in Google Code to Apache Jira * Source code clean-up (Moving everything to org.apache.esme path, Apache copyright, etc.) The following items are planned for the next reporting period: * Work on development second sprint * Submission of Apache CLA by other team members * -- In progress -- Top 2 or 3 things to resolve prior to graduation * Move all collaboration to the esme-dev mailing list * Increase community involvement in the project * Provide instructions for people to build, install and evaluate EMSE by themselves
Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. This report is ESME's first since it joined the incubator and the following items have been performed since its acceptance * Jira has been established and initial issues have been created * The Apache Wiki for ESME has been created * Initial website has been created with Apache Forrest * ESME Core source code has been partially transfered to the Apache SVN from the Google Code site. This drop is based on the latest version of Scala and includes a more optimal separation of UI and server code to ease customization. * Accounts for the initial committers have been created (dpp, dhague, vdichev, mrinal) The following items are planned for the next reporting period: * Inclusion of other existing svn branches (actions, etc.) from Google Code into Apache SVN trunk * Submission of Apache CLAs by two or more other team members. * Next version of Apache Incubator web site with more details * Collection of feature requests for the next version. Special focus on federation and access rights. * Transfer of existing issues in Google Code to Apache Jira * Focus on evolving the design and building a larger community.