Since we are about to miss the deadline once again - any feedback on my proposal?
Thanks Phil Am 01.11.2016 um 22:14 schrieb P. Ottlinger: > Hi, > > here's my report proposal - thanks for feedback :-) > > <snip> > Tamaya > > Tamaya is a highly flexible configuration solution based on a modular, > extensible and injectable key/value based design, which should provide a > minimal but extensible modern and functional API leveraging SE, ME and EE > environments. > > Tamaya has been incubating since 2014-11-14. > > Three most important issues to address in the move towards graduation: > > 1. Extend Community > 2. Improve Documentation and release base components > 3. Stabilize Jenkins/CI jobs > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > of? > > See following sections. > > How has the community developed since the last report? > > We have increasing feedback of use cases to be covered and also a few > bug reports, so Tamaya is used by developers and companies. > Additionally we are doing regular bi-weekly hangouts and have defined a > well defined roadmap to release and restructure our project. > Apart from that we gathered feedback from JavaOne 2016: official > Configuration JSR proposal and Anatole had a talk there. > > The conflicts that arose in the past seem to be solved as some of the > mentors and early committers have left the project. Since we've > established our hangouts we have the feeling of beeing more connect and > able to work towards a common goal. > > How has the project developed since the last report? > > Apart from the main project we established new repositories to hold > extensions and sandbox modules. In order to get rid of the problematic > webpage generation we decided to start from scratch. > In addition to making the API more smooth, we try to keep the base > repository/project as lean as possible and prepare a next release. > Due to various technical issues (infrastructure behaves differently from > local builds and checkouts) we did not meet our deadline on getting a > release out by the end of October. > > Date of last release: > > 2016-04-06 > > When were the last committers or PMC members elected? > > Phil Ottlinger at 2016-04-24. > </snip> > > > Phil > > Am 01.11.2016 um 01:00 schrieb [email protected]: >> Dear podling, >> >> This email was sent by an automated system on behalf of the Apache >> Incubator PMC. It is an initial reminder to give you plenty of time to >> prepare your quarterly board report. >> >> The board meeting is scheduled for Wed, 16 November 2016, 10:30 am PDT. >> The report for your podling will form a part of the Incubator PMC >> report. The Incubator PMC requires your report to be submitted 2 weeks >> before the board meeting, to allow sufficient time for review and >> submission (Wed, November 02). >> >> Please submit your report with sufficient time to allow the Incubator >> PMC, and subsequently board members to review and digest. Again, the >> very latest you should submit your report is 2 weeks prior to the board >> meeting. >> >> Thanks, >> >> The Apache Incubator PMC >> >> Submitting your Report >> >> ---------------------- >> >> Your report should contain the following: >> >> * Your project name >> * A brief description of your project, which assumes no knowledge of >> the project or necessarily of its field >> * A list of the three most important issues to address in the move >> towards graduation. >> * Any issues that the Incubator PMC or ASF Board might wish/need to be >> aware of >> * How has the community developed since the last report >> * How has the project developed since the last report. >> >> This should be appended to the Incubator Wiki page at: >> >> http://wiki.apache.org/incubator/November2016 >> >> Note: This is manually populated. You may need to wait a little before >> this page is created from a template. > >
