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).
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible modern and functional API leveraging SE, ME and EE
environments.
Tamaya has been incubating since 2014-11-14.
### Three most important unfinished issues to address before graduating:
1. Gain more active contributors and committers
2. Decide how to ensure future development of Tamaya
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Since we lack a lot of committers and contributors we started a
discussion
on the mailing list about the future of the project.
One way might be to let the code return to Github instead of becoming a
TLP
- it's an ongoing discussion with no decision yet.
### How has the community developed since the last report?
No changes in the project.
### How has the project developed since the last report?
We released version 0.4-incubating and continue working on changes in
upcoming 0.5.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-11-11 0.4-incubating
### When were the last committers or PPMC members elected?
* 2018-12: Aaron Coburn
* 2018-12: William Lieurance
### Have your mentors been helpful and responsive?
Julian took part in the discussion about the Tamaya's future.
### Is the PPMC managing the podling's brand / trademarks?
No answer
### Signed-off-by:
- [x] (tamaya) John D. Ament
Comments: Tamaya is currently discussing its next steps. We may need
to prod that conversation along a bit to ensure that it can be
resolved in a way that allows the podling to move past their current
blockers.
- [ ] (tamaya) David Blevins
Comments:
- [ ] (tamaya) Kanchana Pradeepika Welagedara
Comments:
- [X] (tamaya) Julian Feinauer
Comments: I wrote an email to incubator private to inform about the
discussion, some weeks ago. Lets see how the discussion ends.
### IPMC/Shepherd notes:
Justin Mclean: Please make sure to answer all questions.
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible modern and functional API leveraging SE, ME and EE
environments.
Tamaya has been incubating since 2014-11-14.
### Three most important unfinished issues to address before graduating:
1. Finish getting our release candidate out.
2. Grow the PPMC from the existing community.
3. Blog and publish more about Tamaya.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Release candidate vote is still pending (2 more +1 votes are needed to
get the RC out).
### How has the community developed since the last report?
No changes, Julian helped out as a new mentor.
### How has the project developed since the last report?
Started forging a new release, had 5 RC.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2017-05-28 0.3-incubating
### When were the last committers or PPMC members elected?
* 2018-12: Aaron Coburn
* 2018-12: William Lieurance
### Have your mentors been helpful and responsive?
New mentor Julian is very helpful as he is present to help out and guide.
### Signed-off-by:
- [ ] (tamaya) John D. Ament
Comments:
- [ ] (tamaya) David Blevins
Comments:
- [ ] (tamaya) Kanchana Pradeepika Welagedara
Comments:
- [x] (tamaya) Julian Feinauer
Comments:
### IPMC/Shepherd notes:
Justin Mclean: I can see the RC vote issues has been resolved. Sometimes
a little patience is needed to get votes on releases. Be sure to ping
your mentors first and make sure they vote.
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible modern and functional API leveraging SE, ME and EE environments. Tamaya has been incubating since 2014-11-14. ### Three most important unfinished issues to address before graduating: 1. Grow the PPMC from the existing community. 2. Make another Release, release more often. 3. Blog more about Tamaya features to get a wider feeedback and audience ### Are there any issues that the IPMC or ASF Board need to be aware of? We'd like to graduate soon. ### How has the community developed since the last report? * No new committers or contributors added, but some interaction via Github pull requests. Development is going on slowly but steadily after the summer break. * New mentor added, kudos to Julian for stepping in. ### How has the project developed since the last report? * Voting took place on 4 RCs - current release candidate 0.4-incubating looks promising * Current release implements the full Microprofile config spec :-) * Jira cleanup for release, changes in sandbox and extensions * Homepage rework * Julian Feinauer started as new mentor and provided feedback concerning release procedures ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2017-05-28 0.3-incubating ### When were the last committers or PPMC members elected? * 2018-12: Aaron Coburn * 2018-12: William Lieurance ### Have your mentors been helpful and responsive? Yes, thanks to Julian for stepping in and actually being present for Tamaya! ### Signed-off-by: - [ ](tamaya) John D. Ament - [ ](tamaya) David Blevins - [ ](tamaya) Kanchana Pradeepika Welagedara - [X](tamaya) Julian Feinauer ### IPMC/Shepherd notes:
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible modern and functional API leveraging SE, ME and EE environments. Tamaya has been incubating since 2014-11-14. Three most important unfinished issues to address before graduating: 1. Grow the PPMC from the existing community. 2. Make another Release 3. Blog about Tamaya Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We'd like to graduate soon. How has the community developed since the last report? No new committers or contributors added, but some interaction via Github pull requests - thanks for the new possibilities. How has the project developed since the last report? Minor changes and SonarCloud integration, homepage improvements. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [X] Nearing graduation [ ] Other: Date of last release: 2017-05-28 0.3-incubating When were the last committers or PPMC members elected? * 2018-12: Aaron Coburn * 2018-12: William Lieurance Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. A new mentor was introduced but did not yet send anything to mailing lists. Signed-off-by: [X](tamaya) John D. Ament Comments: The podling is likely in need of more mentors who can pay closer attention if they want to survive (an additional mentor was added but has yet to participate in the podling). I'm not sure how much of a community is here to be honest, while development works well (slow, but well) not seeing much consumer interaction. [ ](tamaya) David Blevins Comments: [ ](tamaya) Kanchana Pradeepika Welagedara Comments: IPMC/Shepherd notes:
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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. Grow the PPMC from the existing community.
2. Make another Release
3. Blog about Tamaya
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* We'd like to graduate soon.
How has the community developed since the last report?
* elected 2 new committers and onboarded them
* discussions/we benefited from the Gitbox migration as it makes
contribution much easier
How has the project developed since the last report?
* frequent bugreports and discussions via Jira/mailing list
* new external contributions (code improvements, Jira issues, OSGi
bugfixes)
* homepage overhaul
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-05-28 0.3-incubating
When were the last committers or PPMC members elected?
* 2018-12: Aaron Coburn
* 2018-12: William Lieurance
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
* As the project needs a wider audience, maybe mentors with interest in
Tamaya would be welcome.
* Current mentors did not sign-off the report in February and did not
react on mails :-(
Signed-off-by:
[X](tamaya) John D. Ament
Comments: Podling is continuing to struggle. I strongly disagree with
the notion that this project is ready to graduate or nearing readiness. It
has not executed a release in 2 years, Development activity has definitely
increased in the past few months, and with the addition of 2 new committers
may see more sustained progress, but we need to ensure that this vitality
continues on.
[ ](tamaya) David Blevins
Comments:
IPMC/Shepherd notes:
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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. Grow the PPMC from the existing community.
2. Make another Release
3. Blog about Tamaya
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* We'd like to graduate soon.
How has the community developed since the last report?
* elected 2 new committers and onboarded them
* discussions/we benefited from the Gitbox migration as it makes
contribution much easier
How has the project developed since the last report?
* frequent bugreports and discussions via Jira/mailing list
* new external contributions (code improvements, Jira issues, OSGi
bugfixes)
* homepage overhaul
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-05-28 0.3-incubating
When were the last committers or PPMC members elected?
* 2018-12: Aaron Coburn
* 2018-12: William Lieurance
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
* As the project needs a wider audience, maybe mentors with interest in
Tamaya would be welcome.
Signed-off-by:
[ ](tamaya) John D. Ament
Comments:
[ ](tamaya) David Blevins
Comments:
IPMC/Shepherd notes:
Dave Fisher - sent an email regarding following release distribution
policy.
https://lists.apache.org/thread.html/91835c4e5b5e7d0cbe8be640e0878d8a3ac95dc
f9d2e1d91d13b28fb@%3Cdev.tamaya.apache.org%3E
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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. Grow the PPMC from the existing community.
2. Make another Release
3. Blog about Tamaya
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* We'd like to graduate soon and plan some reworks to access a broader
audience and collect new contributors/people interested in the project.
How has the community developed since the last report?
* frequent bugreports and discussions via Jira/mailing list
* new external contributions
How has the community developed since the last report?
* frequent bugreports and discussions via Jira/mailing list
* new external contributions
How has the project developed since the last report?
* Bugfixes, changes, discussions going on
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
Date of last release:
2017-05-28 0.3-incubating
When were the last committers or PPMC members elected?
* P. Ottlinger at 2016-04-24.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
* John is and was the onliest active mentor and answers questions or gives
hints for quite a while.
* As the project needs a wider audience, maybe mentors with interest in Ta
maya would be welcome.
Signed-off-by:
[X](tamaya) John D. Ament
Comments: The podling hasn't executed a release in over a year, has
limited on list discussions. I would be cautious about graduating,
considering how small the community is.
[ ](tamaya) David Blevins
Comments:
IPMC/Shepherd notes:
Dave Fisher: They are currently looking to add committers.
Assuming that they show more community and make one or two
releases then they are close to graduation.
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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.release new versions compliant with configJSR, rework API
2.grow the community, get more active participants
3.graduate as the project is functionally very mature already
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We'd like to graduate after 0.4 is out.
How has the community developed since the last report?
New external contributors: Aaron Coburn, William Lieurance
How has the project developed since the last report?
* minor bugfixes and small changes (due to summer holidays)
* relatively low traffic on mailing lists
* some interest via mail/contributions from external people/possibly new
contributors
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2018-05-27 v0.3-incubating
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[ ] David Blevins
Comments:
[X] John D. Ament
Comments: The podling shows a lot of potential, but I'm not sure there's
enough for it to move forward as a TLP.
IPMC/Shepherd notes:
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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.release new versions compliant with configJSR, rework API
2.grow the community, get more active participants
3.graduate as the project is functionally very mature already
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We'd like to graduate after 0.4 is out, maybe Q2-2018.
How has the community developed since the last report?
New external contributor Aaron Coburn
How has the project developed since the last report?
* continue working on the configJSR-branch
* updated to new microprofile v1.2
* new external blogposts about Tamaya
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2018-05-27 v0.3-incubating
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[X](tamaya) John D. Ament
Comments: I disagree that the podling is nearing graduation. They have a long ways to go. Some people are interested in the project, and they need to come up with a way to capitalize on it.
[ ](tamaya) David Blevins
Comments:
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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.release new versions compliant with configJSR/enhanced OSGi support
2.grow the community, get more active participants
3.graduate as the project is functionally very mature
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We'd like to graduate after 0.4 is out, maybe Q1-2018.
How has the community developed since the last report?
New external contributor William Lieurance
How has the project developed since the last report?
Continued development of v0.4, struggled with build problems after JDK
updates, introduced rewritten Tamaya-API compliant with
Eclipse-ConfigJSR proposal (on a separate branch yet).
Integrated with Travis to get rid of build failures, updated
documentation of project, blog articles
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2018-05-27 v0.3-incubating
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[X](tamaya) John D. Ament
Comments:
[ ](tamaya) David Blevins
Comments:
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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. Announce release 0.3 properly
2. Prepare release 0.4 (end of November)
3. Grow community and get more active developers as a TLP
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We'd like to graduate after 0.4 is out, maybe Q1-2018.
How has the community developed since the last report?
A lot of discussion/bugreport/fixing concerning the upcoming OSGi features on the mailing list.
Unfortunately not yet any new committers.
Members of the project have joined the official Configuration JSR (Anatole/John)
How has the project developed since the last report?
We've introduced new features such as OSGi support and full Java8 compatibility
while raising test and mutation test coverage.
Apart from that the upcoming 0.4-SNAPSHOT has Microprofile API support.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-08-01
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[X](tamaya) John D. Ament
Comments: Its clear to me that the podling has a rough understanding of Apache Way.
However, I think they need the marketing side to pick up to draw some interest.
[ ](tamaya) David Blevins
Comments:
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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. Release version 0.3 of Tamaya Core and Extensions
2. Start a new Howto/blog series about Tamaya and its new features
3. Use attention of these releases to gather new committers
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We'd like to graduate soon.
How has the community developed since the last report?
No changes, due to holiday season a slightly lower activity.
How has the project developed since the last report?
Release of Core 0.3 is out, extensions just passed the IPMC approval.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-08-01
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[X](tamaya) John D. Ament
Comments:
[ ](tamaya) David Blevins
Comments:
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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. finally release 0.3 - RC vote already took place
2. Release next artifacts after core/API 0.3-incubating is out
3. graduate
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
We would like to graduate after our new release is out.
How has the community developed since the last report?
Many discussions and bug reports were filed in order to see how
microprofile.io discussions match the Tamaya roadmap. In order to prepare for
the new release some people (inactive for quite a while) were moved to the
emeritus section.
How has the project developed since the last report?
New homepage is live, release candidates for 0.3-incubating are out. Waiting
to continue with extensions and further development on sandbox modules.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2016-04-06
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[X](tamaya) John D. Ament
Comments: It's a small and diverse community. They have a little bit to
go before graduation, and need to figure out how to get communicating
more on list.
[ ](tamaya) David Blevins
Comments:
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible 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 / finish new homepage 3. Start graduation after 0.3 is out Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We are thinking about graduating after the next release since our new homepage contains information about many new features and we do have a new module structure. How has the community developed since the last report? On conferences and after Oracle dropped the configuration JSR many conversations started about Configuration in the Java world. Apart from bugfixes the main new features is basic OSGi support (currently still in development in sandbox module). Weekly hangouts (monday 8pm Berlin time) take place to have shorter feedback cycles, minutes are communicated via mail. How has the project developed since the last report? The infrastructure runs much more smoothly with the new module structure: core, extensions, sandbox and a separate project for the homepage based on jBake. OSGi support is a big thing since different OSGi containers have their problems. Good contact to Apache Karaf developers. New homepage with new structure and more information available as prototype via: https://tamaya.apache.org/jbake/ Homepage is connected to its repository via gitpubsub. Date of last release: 2016-04-06 When were the last committers or PPMC members elected? P. Ottlinger at 2016-04-24. Signed-off-by: [X](tamaya) John D. Ament [ ](tamaya) David Blevins Shepherd/Mentor notes: John D. Ament: Podling is having some initial conversations around graduation.
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible 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. Graduate als TLP in 2017 after next releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? After our next releases and improving our homepage we'd like to graduate as a TLP in 2017. 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. Signed-off-by: [X](tamaya) John D. Ament [ ](tamaya) David Blevins Shepherd/Mentor notes: John D. Ament: While the podling has had issues in the past around community growth, I am seeing them operate more consistently, with clear open discussions. I believe they're operating well and should be ready to graduate soon, if not already.
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
3. Stabilize existing code base
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?
A number of existing committers have decided to leave the project, this
includes the loss of two mentors and two other committers.
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.
How has the project developed since the last report?
We have decided to improve the project setup, so we can
release easier and faster in the future: separating the site from the
project release, separating experimental modules and stable modules
into separate repositories. This work is currently ongoing, but we make
good progress and we plan to get out a release of the core parts around
end of October.
Date of last release:
2016-04-06
When were the last committers or PMC members elected?
Phil Ottlinger at 24th April 2016.
Signed-off-by:
[X](tamaya) John D. Ament
[ ](tamaya) David Blevins
Shepherd/Mentor notes:
johndament:
The project has room to improve. With the loss of mentors and existing
committers, need help mentoring this project.
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible modern and functional API leveraging SE, ME and EE environments. Tamaya has been incubating since 2014-11-14. Shepherd/Mentor notes: John D. Ament: The project continues to struggle. I'm not sure its recoverable as an ASF project at this time. May make sense to reboot in an external resource, e.g. GitHub, build a true community, and then come back.
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible 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. Allow community to build consensus in APIs. 2. Get new contributors. 3. Understand and work through end user use-cases. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The community recently had a bit of a falling out between this project and some changes proposed to go into the Geronimo project. Its generally believed that what was being proposed was not malicious. It does however represent some of the core issues around this project's ability create consensus and grow. The project has already been incubating for two years, with very few releases and very little contributor growth. How has the community developed since the last report? - See issues section. How has the project developed since the last report? - Releases are still in progress, and work is being done to refactor the Tamaya APIs based on some input from Mark Struberg and others. Date of last release: 2016-04-06 (0.2-incubating) When were the last committers or PMC members elected? Philipp Ottlinger has been elected on 2016-04-22 as new committer. Signed-off-by: [X](tamaya) John D. Ament [X](tamaya) Mark Struberg [ ](tamaya) Gerhard Petracek [ ](tamaya) David Blevins Shepherd/Mentor notes: johndament: Discussions are beginning to talk through the future of the podling. Going to request an extra report next month since this was created by mentors.
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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. We released Tamaya 0.2-incubating on 2016-04-06.
2. Attract more community members.
3. Create a fully ASF compliant release (both source and binary,
since the source one was good this time around)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
There are no such items.
How has the community developed since the last report?
- We elected a new committer.
- Some people expressed their interest to use Tamaya in their projects.
How has the project developed since the last report?
- Release 0.2-incubating has been released.
- New features based on community input have been added to the roadmap.
Date of last release:
2016-04-06 (0.2-incubating)
When were the last committers or PMC members elected?
Philipp Ottlinger has been elected on 2016-04-22 as new committer.
Signed-off-by:
[X](tamaya) John D. Ament
[ ](tamaya) Mark Struberg
[ ](tamaya) Gerhard Petracek
[ ](tamaya) David Blevins
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible 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. Make the project known in projects world-wide. 2. Release more often. 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? We have new people committing to our project and are in good hope one or another will join us as an official committer. JUG talks in Switzerland showed that the project is widely known and well appreciated in the enterprise context. How has the project developed since the last report? The project's API has proven to work very well. We added additional integrations with several key technologies such as Spring, OSGI and CDI. We streamlined our build and also had discussions on some needed enhancements on the API/SPI. We are currently working on the final aspects for getting out our next release, which within 2-4 weeks. Date of last release: 2015-08-22 When were the last committers or PMC members elected? 25th January 2015 Signed-off-by: [x](tamaya) John D. Ament [ ](tamaya) Mark Struberg [ ](tamaya) Gerhard Petracek [ ](tamaya) David Blevins Shepherd/Mentor notes: John D. Ament (johndament): The core committers are very dedicated to the project. However, there's only two of them. For the project to be sustainable, they need to show growth in contributors.
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible 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. Make the project known in projects world-wide. 2. Release more often. 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? We have new people joining the mailinglist and also starting discussions for possible future involvement. We had quite broad feedback in the Java EE space, since we added full blown CDI support to Tamaya. We are looking forward to gain new committers within next reporting period hopefully. During ApacheCon Europe different projects found our approach very interesting. We also have a request from a JUG in Switzerland going to present the project as well several conferences that accept the topic as well. How has the project developed since the last report? The project's API has proven to work very well. Many, also complex extensions were written and we started to add support for very important eco-systems (JavaEE, Spring, OSGI). I think we can release the next release before X-Mas the latest. Date of last release: 2015-08-22 When were the last committers or PMC members elected? See last report (no new committers or PMC members). Signed-off-by: [X](tamaya) John D. Ament [X](tamaya) Mark Struberg [ ](tamaya) Gerhard Petracek [ ](tamaya) David Blevins Shepherd/Mentor notes:
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible 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. We need more active contributors. 2. We must provide support for Java EE. 3. We must release more often. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? Streamlining all features and preparingthe first release took more time as originally suggested due to absences of key people involved. It has shown that additional committers are urgently needed. There were several that have shown interest, but unfortunately this did not lead to additional contributors. We hope that presentations at ApacheCon, Devoxx and several other conferences as well as articles at JAXenter and more will help to improve the community until end of year. How has the project developed since the last report? We have now an agreed core set of APIs and extensions that provide a healthy and usefule base for the future. The extensions are all well tested and documented, so we should be able tome come up if a good quality with our first release. The first release 0.1-incubating is now in the vote on PMC, so we are now on track to further wider community awereness for our project. Anatole has a article series on the topic in the biggest German technical paper and also will blog regularly on it, once the release is out. As a star spec lead his network should definitively help to grow community then. Date of last release: None. But first release is discussed in the PMC as of now, so within the next 1-2 week it should be out. When were the last committers or PMC members elected? See last report (no new committers or PMC members). Signed-off-by: [X](tamaya) John D. Ament [ ](tamaya) Mark Struberg [ ](tamaya) Gerhard Petracek [ ](tamaya) David Blevins Shepherd/Mentor notes: johndament: The small community came together quickly following existing ASF best practices to get their first together. Thank you especially to Justin Mclean for pre-reviewing the release to catch any issues. Once Tamaya gets through some community growth, they will be well functioning.
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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. Publish a first release until mid year.
2. Keep focus for a reasonable functionality and way forward.
3. Keep up/increase community engagement, increase publicity by further
evangelizing it.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No.
How has the community developed since the last report?
Two people have shown very interested 1) on the mailing list, or 2) even
helped with some work at ZH Hackergarten. Crcial will be going out with a
first release asap.
How has the project developed since the last report?
We successfully backported API/core to Java 7. Overall project quality
increased. Some API aspects were reevaluated and several bugfixes and new
features were added. Also a lot of documentation and examples were added,
so we definitively approach a first release.
Date of last release:
N/A (not released anything).
When were the last committers or PMC members elected?
25th January 2015 (Reinhard Sandtner)
Signed-off-by:
[X](tamaya) John D. Ament
[X](tamaya) Mark Struberg
[ ](tamaya) Gerhard Petracek
[ ](tamaya) David Blevins
Shepherd/Mentor notes:
John Ament:
Podling is beginning the process towards the first release.
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible 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. Publish a first release soon. 2. Keep focus for a reasonable functionality and way forward. 3. Keep up/increase community engagement. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? Reinhard Sandtner was successfully elected to join as a new committer, PPMC member. During Zurich Hackergarten we implemented the backport of the current Java 8 core implementation. How has the project developed since the last report? We identified a minimalistic but extendible API. Basic implementation work for Java 8 and Java 7 is ongoing, but makes overall good progress. Date of last release: not yet defined, probably in Q2/2015 When were the last committers or PMC members elected? 25th January 2015 (Reinhard Sandtner) Signed-off-by: [X](tamaya) John D. Ament [X](tamaya) Mark Struberg [ ](tamaya) Gerhard Petracek [ ](tamaya) David Blevins Shepherd/Mentor notes: jda: Initial growing pains seem to be resolved, initial members are working together better. Mailing list activity is steady and everyone is getting adjusted to The Apache Way. mbf: Community activity looks strong and the community is discussing and deciding on the list.
Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible 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. Project web site must be setup (done). 2. Establish a solid code base for a release. 3. Continue to grow the community. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There are many discussions about how simple the API and or code should be. How has the community developed since the last report? We got a new contributor, Reinhard Sandtner who already shipped a patch and is participating in some discussions. How has the project developed since the last report? The project setup is going quite well. The initial code donation is under ongoing review. Date of last release: None yet. When were the last committers or PMC members elected? None yet. Signed-off-by: [X](tamaya) John D. Ament [X](tamaya) Mark Struberg [ ](tamaya) Gerhard Petracek [ ](tamaya) David Blevins Shepherd/Mentor notes: John D. Ament (johndament): Podling is struggling a bit with some growing pains. Hope it will straighten out soon.
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible 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. Project web site must be setup (ongoing).
2. Establish a collaboration model within the community and ensure a
common view on the main focus points.
3. Improve code base for being ready for a first release around Q1 2015.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No.
How has the community developed since the last report?
Many of the committers have successfully filed the ICLA and also started
to contribute, some of them already by doing first patches. Feedback in
the community was overwhelming. We could also successfully place the
topic at conferences as well as in the German Java Magazin and other
events. Also interest of people during the Zurich Hackergarten in
November was great and will definitely lead to additional committers
early 2015.
How has the project developed since the last report?
The project setup is going quite well. Initial committers are onboarding,
the initial code donation was successfully moved and other preconditions
like the project name, IP clearance, Jenkins etc. were successfully done.
Thanks to INFRA for their incredible support!
Date of last release: Still getting started.
When were the last committers or PMC members elected?
Still getting started.
Signed-off-by:
[x](tamaya) John D. Ament
[ ](tamaya) David Blevins
[ ](tamaya) Mark Struberg
[ ](tamaya) Gerhard Petracek
Shepherd/Mentor notes:
Justin Mclean - Off to a good start. Email list and mentors active.