This was extracted (@ 2025-02-19 17: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).
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. All development activity has ceased.
2. Discussions underway to decide on the future course of the podling.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Discussions in progress about the future course of the project.
How has the project developed since the last report?
All development activity on the project has ceased, all present
committers have moved on to pursue other interests.
How would you assess the podling's maturity?
Community Building
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-01-16
When were the last committers or PPMC members elected?
Thomas Nadeau added in Feb 2018
Signed-off-by:
[X](ariatosca) Suneel Marthi
Comments:
[ ](ariatosca) John D. Ament
Comments:
[ ](ariatosca) Jakob Homan
Comments:
IPMC/Shepherd notes:
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Have (more) frequent Release cycles to be compliant with the Apache Way.
3. Grow the project’s contributions from existing community of contributors
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
1. The project issued its third release (0.2.0) as far as the code is
concerned. Some considerable functionality has been added since the last
release in addition to a growth in diversity of contributions.
How has the community developed since the last report?
* All project communication now takes place on either the mailing list or
ASF's Slack, and is open for everybody. We have worked hard to make this
the normal operating mode of the community. There have been some hiccups,
but in general the majority of discourse has taken place on the list.
* Increased chatter on the mailing list including new subscribers who ask
questions, make suggestions and are likely to become contributors
themselves in the near future.
* Weekly grooming meetings are now attended by the majority of the community.
This is not only a forum to review the weekly work items list, but also as a
place for open discussion about issues, questions as well as for the
community to get to better know each other.
How has the community developed since the last report?
Over the last 3 months we have seen a significant increase in contributions as
well as a few new contributors, particularly from the Ericsson contingent.
How has the project developed since the last report?
ARIA now has two new patches considerably extend the parser's
plugin/extensions
Website and documentation improvements for usability and to enhance new user
Usability in terms of “getting started” instructions
9 JIRA issues have been resolved since the last report. Note that the
repository was locked for several weeks during this period due to release
process issues and learning curve.
We will be doing another release during this quarter.
The community has begun to undertake updating AriaTosca to support the Tosca
1.1 Simple YAML profile.
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:
The 0.2.0 release was issued on January 16, 2018. The .3 release is planned
for this quarter.
When were the last committers or PPMC members elected?
Tom Nadeau was added to the PMC/committers on 11/28/2017
Signed-off-by:
[X](ariatosca) Suneel Marthi
Comments: Podling needs to focus on growing the community and a more frequent release cadence.
[X](ariatosca) John D. Ament
Comments: It's a small group. On list communication is still a struggle.
[X](ariatosca) Jakob Homan
Comments: Small but growing slowly and heading in the right direction.
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Have frequent Release cycles to be compliant with the Apache Way.
3. Grow the project’s contributions from existing contributors
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The project is ready for its third release as far as the code is concerned. Considerable functionality has been added since the last release in addition to a growth in diversity of contributions.
How has the community developed since the last report?
* All project communication takes now place on either the mailing list or ASF's Slack, and is open for everybody. We have worked hard to make this the normal operating mode of the community. There have been some hiccups, but in general the majority of discourse has taken place on the list. Slack has been used as a secondary method.
* Increased chatter on the mailing list including new subscribers who ask questions, make suggestions and are likely to become contributors themselves in the near future.
* Weekly grooming meetings are now attended by the majority of the community. This is not only a forum to review the weekly work items list, but also as a place for open discussion about issues, questions as well as for the community to get to better know each other.
* Over the last 3 months we have seen an over %50 increase in contributors and the existing group of committers voted to elect a new Committer to the project.
How has the project developed since the last report?
- ARIA now has a robust parser testing framework (ARIA-1)
- Huge performance improvement (ARIA-1)
- Significant website and documentation improvements for usability and to enhance new user Usability in terms of “getting started” instructions
- Clearwater IMS Example
- Package names fixed/made consistent
- Configuration loading mechanism
- Removed support for Python 2.6
- 42 JIRA issues have been resolved since the last report
- Moved project to gitbox
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:
2017-07-13 0.1.1
When were the last committers or PPMC members elected?
Tom Nadeau was added to the PMC/committers on 2017-11-28
Signed-off-by:
[ ](ariatosca) Suneel Marthi
Comments:
[X](ariatosca) John D. Ament
Comments: Activity on list is picking up over the slack conversations. A community member is planning to write a report, however it indicates a corporate hierarchy issue within the project that needs to get solved. In addition, the podling needs to figure out how to operate more on list (without grooming meetings) and do things more asynchronously.
[ ](ariatosca) Jakob Homan
Comments:
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Rotate Release Managers for future releases.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Seeing some contributions now from independent developers.
Active discussions on mailing lists with potential users and contributors.
How has the project developed since the last report?
The project has had its first two releases in July 2017 - 0.1 and 0.1.1
Important new features have been added:
- Resumable workflows
- Scaling nodes during service creation
- AWS plugin support
- Additional work towards being more TOSCA-compliant (e.g. interface inputs support)
- Additional usage examples have been added, including ones that use IaaS plugins (Openstack, AWS), as well as one covering a real-life NFV use-case (Clearwater example)
- More comprehensive tests, including for documentation generation, and parallelization of test suites
- Standardized the release process with automatic shell scripts, allowing anyone to easily create additional releases for the project
- 64 JIRA issues have been resolved since the last report
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:
July 17, 2017
When were the last committers or PPMC members elected?
Project is still functioning with the initial set of committers.
Signed-off-by:
[X](ariatosca) Suneel Marthi
Comments:
[X](ariatosca) John D. Ament
Comments: The project has started to see more community interest. Need to figure out how to drive development more on list to get more outside contributions.
[ ](ariatosca) Jakob Homan
Comments:
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Have frequent Release cycles to be compliant with the Apache Way.
3. Move the website to apache.org
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
The project is ready for its first release as far as the code is concerned;
We're working on updating the README and ensuring compatibility with ASF's
regulations regarding creating releases. On the latter issue, we've come
across a few possible problems, that are being discussed on the project's
mailing list. For more information, see the threads "ARIA dependencies License
issues" and "A few questions about creating a release" on the mailing list
archive.
How has the community developed since the last report?
* All project communication takes now place on either the mailing list or
ASF's Slack, and is open for everybody.
* Increased chatter on the mailing list including new subscribers who ask
questions, make suggestions and are likely to become contributors themselves
in the near future.
How has the project developed since the last report?
1. ARIA now has a CLI, making it usable as a stand alone tool as well as a
library. 2. Usage examples have been added 3. End-to-End tests now run on a
daily basis (as well as on CIs for every commit) 4. 93 JIRA issues have been
resolved since the last report
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No release yet.
When were the last committers or PPMC members elected?
Project is still functioning with the initial set of committers.
Signed-off-by:
[X](ariatosca) Suneel Marthi
Comments:
[X](ariatosca) John D. Ament
Comments: The project continues to struggle in adopting the Apache Way.
It's clear most of them want to do it, but need to work on getting
focused to make it happen.
[ ](ariatosca) Jakob Homan
Comments:
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Have frequent Release cycles to be compliant with the Apache Way.
3. Update ARIA website according to ASF guideline(Include release process
for ARIA-TOSCA Project).
4. Publish "How To Contribute" guide at ARIA-TOSCA Website.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Most of the project discussions are now happening on mailing lists.
How has the project developed since the last report?
TOSCA parser migrated into ASF
CI on Appveyor, Jenkins
Sphinx documentation added to the project
CLIs of workflow engine and parser coalesced
TOSCA CSAR packager added
APIs for workflows, operations
Workflow engine task retry support
Workflow engine execution cancel support
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No release yet
When were the last committers or PPMC members elected?
Project is still operating with the initial set of committers.
Signed-off-by:
[X](ariatosca) Suneel Marthi
Comments:
Podling activity has been consistent and discussions are now happening
on the mailing lists.
[X](ariatosca) John D. Ament
Comments:
Podling activity peaks and dives. Would like to see more on-list
chatter.
[ ](ariatosca) Jakob Homan
Comments:
IPMC/Shepherd notes:
Drew Farris (shepherd): 2 mentors active on mailing lists, evidence of healthy
development activity. Consider a separate jira/commits list to encourage
discussion among humans on the dev list.
ARIA TOSCA project offers an easily consumable Software Development
Kit(SDK) and a Command Line Interface(CLI) to implement TOSCA(Topology
and Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Have frequent Release cycles to be compliant with the Apache Way.
3. Publish "How To Contribute" guide at ARIA-TOSCA Website.
4. Update ARIA website acording to ASF guideline(Include release process
for ARIA-TOSCA Project)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
There's an INFRA jira we created over a month ago which has yet to be
addressed - please see here INFRA-12733 - Ability to create a Sprint
Board for AriaTosca WAITING FOR USER
It is not entirely critical for the project's progress, but it could
be helpful if we indeed get a sprint board and the other things
requested in that issue.
Update: the ticket is now in progress.
How has the community developed since the last report?
* Open-O is in process for consuming the ARIA ASF package
* Cloudfiy is in process for consuming the ARIA ASF package as well.
* Need to work on building the community and accepting external
contributions.
How has the project developed since the last report?
* TOSCA parser migrated into ASF
* CI on Appveyor, Jenkins
* Sphinx documentation added to the project
* CLIs of workflow engine and parser coalesced
* TOSCA CSAR packager added
* APIs for workflows, operations
* Workflow engine task retry support
* Workflow engine execution cancel support
Date of last release:
No Releases yet
When were the last committers or PMC members elected?
Project is still functioning with the initial set of committers.
Signed-off-by:
[X](ariatosca) Suneel Marthi
[X](ariatosca) John D. Ament
[ ](ariatosca) Jakob Homan
Shepherd/Mentor notes:
John D. Ament:
The podling is still getting its feet wet. Discussions are starting to
happen on the mailing lists rather than in physical offices which is good
and will help to bring about a more diverse community. I would also
strongly encourage the podling to work with their mentors to get infra
changes in to avoid confusion.
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Finalize migration of existing ARIA code, including Parser-NG with TOSCA
and TOSCA for NFV profiles, and workflow engine to the ASF repo.
2. Create and publish release process for ARIA-TOSCA Project, release
process will include Parser, TOSCA profiles, Workflow Engine, CLI.
3. Publish "How To Contribute" guide at ARIA-TOSCA Website.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
There's an INFRA jira we created over a month ago which has yet to be
addressed - please see here INFRA-12733 - Ability to create a Sprint Board
for AriaTosca WAITING FOR USER
It is not entirely critical for the project's progress, but it could be
helpful if we indeed get a sprint board and the other things requested in
that issue.
How has the community developed since the last report?
Preparing TOSCA DSL training materials
Confluence space initialized
How has the project developed since the last report?
1. Created master branch
2. CI on travis enabled for the project
3. Initial workflow engine code migrated to ASF repo
4. Preparing migrating Parser code to ASF repo
5. Various task executors have been implemented
Date of last release:
None
When were the last committers or PMC members elected?
Project is being established in incubator with the proposed initial set of
committers.
Signed-off-by:
[X](ariatosca) Suneel Marthi
[X](ariatosca) John D. Ament
[ ](ariatosca) Jakob Homan
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK) and a Command Line Interface(CLI) to implement TOSCA(Topology and Orchestration Specification of Cloud Applications) based solutions. AriaTosca has been incubating since 2016-08-27. Three most important issues to address in the move towards graduation: 1.Establish a formal release process and schedule, allowing for dependable release cycles in a manner consistent with the Apache development process and formulate a plan for fully functional release 1 of ARIA and populate tasks to ASF Jira 2.Migrate existing users to apache mailing lists, redirect the present external project links to Apache. 3.Grow the community around the project. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Project is still being established and presently onboarding the initial committers. How has the community developed since the last report? Received Software Grant Agreement (SGA) from Gigaspaces. The mailing lists, Jira, Github Repo, Incubator podling, Confluence Wiki have been setup for the project. The initial set of committers now have their apacheIds. How has the project developed since the last report? The project is presently being setup in Incubator. We expect the first code push to happen in the month of October. Date of last release: None When were the last committers or PMC members elected? Project is running with the initial set of committers. Signed-off-by: [X](ariatosca) Suneel Marthi [X](ariatosca) John D. Ament [ ](ariatosca) Jakob Homan
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Establish a formal release process and schedule, allowing for dependable
release cycles in a manner consistent with the Apache development
process.
2. Grow the community around the project.
3. Migrate existing users to apache mailing lists, redirect the present
external project links to Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
The project is still being setup in Apache Incubator and is presently.
Received Software Grant Agreement (SGA) from Gigaspaces.
The mailing lists, Jira, Github Repo, Incubator podling, Confluence Wiki
have been setup for the project.
How has the project developed since the last report?
This would be the first report for AriaTosca.
The project is presently being setup in Incubator.
Date of last release:
None
When were the last committers or PMC members elected?
Project is being established in incubator with the proposed initial set of
committers.
Signed-off-by:
[X](ariatosca) Suneel Marthi
[X](ariatosca) John D. Ament
[X](ariatosca) Jakob Homan