Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes
Hi everyone, My new TOSCA parser will also be ready for public review in about 1 week. I propose we delay the decision a bit longer so we can assess the situation. On Wed, May 30, 2018 at 12:01 AM S Shenbaga Rajan < s.shenbaga.ra...@ericsson.com> wrote: > Hi Sunil, > > Give us couple of days. We are discussing around this topic. > I would come back by end of this week. > > Thanks, > /Shen > > -Original Message- > From: Suneel Marthi [mailto:smar...@apache.org] > Sent: Wednesday, May 30, 2018 5:30 AM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes > > @DJ - any updates - we are due to submit the incubator report , let us > know by tomorrow as to what Ericsson's decision is. > > > > On Fri, May 25, 2018 at 6:11 PM, Suneel Marthi wrote: > > > Thanks for the call this week. > > > > @DJ, please let us know by next week about Ericsson's decision. > > > > > > On Mon, May 21, 2018 at 11:17 AM, Thomas Nadeau > > > > wrote: > > > >> > >> Discussing the Future of AriaTosca > >> > >> Monday, May 21, 2018 10-11AM EST > >> > >> > >> Attendees: Tal, Ido, Shen, DJ, Tom Nadeau, Sunil > >> > >> Tom: Does anyone want to proceed forward with Aria and how? > >> DJ: Ericsson has been looking into this project/area. They started > >> buildign the missing parts of Aria and wish to contirbute them back > >> to the community. Initially we discussed these things with Arthur from > Cloudify > >> (with Tal) and to help with our contirbutions. Other than that, we > were > >> always under the assumption that the communit was moving forward and > >> we thought we could contribute a few things. > >> > >> Most recently we have built a lot of components around Aria > >> (including Tosca 1.1). Issue is there are no active members that can > commit our PRs. > >> We are ready to contribute but need to know what the interest of the > >> community. > >> > >> Tom: Tal, Ido? Opinions? > >> > >> Ido: Speaking on behalf of Cloudify, currently we do not have any > >> committers in the Aria project. We are not actively working on Aria > >> at the moment - as a company we have other initiatives to work on, > >> and other engagements such as LF and ONAP community. I don't know if > >> that is going to change. > >> > >> Tal: I'd like to suggest a few options to move forward. Neither > >> Cloudify nor Ericsson can take leadership of the project. You can > >> take Apache incubation projects into "The Attic". Different status. > >> Can be unfrozen in the future. Taking it out of the attic is much > >> easier than starting a new project. Another option is to fork the > >> project and take it to github (outside of the Apache org). > >> > >> Tom: Thats just forking the code on github. > >> > >> Tal: Yes. We would tell our mentors in ASF that we are leaving the > >> project and will continue on github. > >> > >> Tom: They can fork independently and collaborate (Cloudify and > Ericsson). > >> > >> Tal: Ericsson chose this project because they thought there was an > active > >> community around an orchestrator. One option is to look into the > Cloudify > >> "community edition". This does not support TOSCA proper but is an > option. > >> > >> DJ: The important part of your last point was to use a pure TOSCA parser > >> implementation. This is why we were in favor of Aria. > >> > >> I would like to hear from you (Tal) about moving this to github. > >> > >> Can you explain why this project was started in Apache? > >> > >> Tal: Pros (to github): more flexibility (including management). Cons: > >> the management complications. > >> > >> Right now Aria is being used by the ONAP project in LF. The fact > >> that the code belonged to a foundation made it attractive to that > organization. > >> WIth that said, Aria does not have a big place. > >> > >> There are many successful reasons for how projects are successful on > >> github with healthy communities. > >> > >> I worked hard to get support within Apache for Aria and got mild > >> support. The community at large did not support this much. > >> > >> Sunil: This is exactly the question I asked to Arthur a year ago. > >> > >> Tal: This made sense because it helped us join the open-o and onap > >> communities. We hoped those folks would contribute back to the project. > >> Unfortunately those folks haven't, and I am not hopeful that those > >> folks will. > >> > >> I am actually working on a next-generation of Aria. I am rewriting > >> everything in scratch in Go to create a stateless parser (TOSCA). I > have a > >> lot of faith in TOSCA but the approach needs to be a lot simpler. That > >> might be out there on the community to collaborate with. > >> > >> DJ: As you already pointed out, we are trying to understand if your > >> new project would have the same attraction. > >> > >> Sunil: Attracting contributors is not necessarily related to Apache. > >> Tensorflow is a massive project that is just on github without any >
RE: Updated: Discuss The Future Of AriaTosca - Meeting Minutes
Hi Sunil, Give us couple of days. We are discussing around this topic. I would come back by end of this week. Thanks, /Shen -Original Message- From: Suneel Marthi [mailto:smar...@apache.org] Sent: Wednesday, May 30, 2018 5:30 AM To: dev@ariatosca.incubator.apache.org Subject: Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes @DJ - any updates - we are due to submit the incubator report , let us know by tomorrow as to what Ericsson's decision is. On Fri, May 25, 2018 at 6:11 PM, Suneel Marthi wrote: > Thanks for the call this week. > > @DJ, please let us know by next week about Ericsson's decision. > > > On Mon, May 21, 2018 at 11:17 AM, Thomas Nadeau > > wrote: > >> >> Discussing the Future of AriaTosca >> >> Monday, May 21, 2018 10-11AM EST >> >> >> Attendees: Tal, Ido, Shen, DJ, Tom Nadeau, Sunil >> >> Tom: Does anyone want to proceed forward with Aria and how? >> DJ: Ericsson has been looking into this project/area. They started >> buildign the missing parts of Aria and wish to contirbute them back >> to the community. Initially we discussed these things with Arthur from >> Cloudify >> (with Tal) and to help with our contirbutions. Other than that, we were >> always under the assumption that the communit was moving forward and >> we thought we could contribute a few things. >> >> Most recently we have built a lot of components around Aria >> (including Tosca 1.1). Issue is there are no active members that can commit >> our PRs. >> We are ready to contribute but need to know what the interest of the >> community. >> >> Tom: Tal, Ido? Opinions? >> >> Ido: Speaking on behalf of Cloudify, currently we do not have any >> committers in the Aria project. We are not actively working on Aria >> at the moment - as a company we have other initiatives to work on, >> and other engagements such as LF and ONAP community. I don't know if >> that is going to change. >> >> Tal: I'd like to suggest a few options to move forward. Neither >> Cloudify nor Ericsson can take leadership of the project. You can >> take Apache incubation projects into "The Attic". Different status. >> Can be unfrozen in the future. Taking it out of the attic is much >> easier than starting a new project. Another option is to fork the >> project and take it to github (outside of the Apache org). >> >> Tom: Thats just forking the code on github. >> >> Tal: Yes. We would tell our mentors in ASF that we are leaving the >> project and will continue on github. >> >> Tom: They can fork independently and collaborate (Cloudify and Ericsson). >> >> Tal: Ericsson chose this project because they thought there was an active >> community around an orchestrator. One option is to look into the Cloudify >> "community edition". This does not support TOSCA proper but is an option. >> >> DJ: The important part of your last point was to use a pure TOSCA parser >> implementation. This is why we were in favor of Aria. >> >> I would like to hear from you (Tal) about moving this to github. >> >> Can you explain why this project was started in Apache? >> >> Tal: Pros (to github): more flexibility (including management). Cons: >> the management complications. >> >> Right now Aria is being used by the ONAP project in LF. The fact >> that the code belonged to a foundation made it attractive to that >> organization. >> WIth that said, Aria does not have a big place. >> >> There are many successful reasons for how projects are successful on >> github with healthy communities. >> >> I worked hard to get support within Apache for Aria and got mild >> support. The community at large did not support this much. >> >> Sunil: This is exactly the question I asked to Arthur a year ago. >> >> Tal: This made sense because it helped us join the open-o and onap >> communities. We hoped those folks would contribute back to the project. >> Unfortunately those folks haven't, and I am not hopeful that those >> folks will. >> >> I am actually working on a next-generation of Aria. I am rewriting >> everything in scratch in Go to create a stateless parser (TOSCA). I have a >> lot of faith in TOSCA but the approach needs to be a lot simpler. That >> might be out there on the community to collaborate with. >> >> DJ: As you already pointed out, we are trying to understand if your >> new project would have the same attraction. >> >> Sunil: Attracting contributors is not necessarily related to Apache. >> Tensorflow is a massive project that is just on github without any >> organizational affiliation. >> >> Shen: Cloudify started this project on Apache. If Ericsson wants to >> reboot Aria is this possible? >> >> Shen introduces himself as a Product Manager at Ericsson. >> >> Suneel: Once the project is part of ASF its owned by ASF. The problem >> is that the active commiters are no longer interested in >> participating in the project. Chicken & egg problem. >> >> Shen: Is there a way forward? >> >> Suneel: Ido what
Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes
@DJ - any updates - we are due to submit the incubator report , let us know by tomorrow as to what Ericsson's decision is. On Fri, May 25, 2018 at 6:11 PM, Suneel Marthi wrote: > Thanks for the call this week. > > @DJ, please let us know by next week about Ericsson's decision. > > > On Mon, May 21, 2018 at 11:17 AM, Thomas Nadeau > wrote: > >> >> Discussing the Future of AriaTosca >> >> Monday, May 21, 2018 10-11AM EST >> >> >> Attendees: Tal, Ido, Shen, DJ, Tom Nadeau, Sunil >> >> Tom: Does anyone want to proceed forward with Aria and how? >> DJ: Ericsson has been looking into this project/area. They started >> buildign the missing parts of Aria and wish to contirbute them back to the >> community. Initially we discussed these things with Arthur from Cloudify >> (with Tal) and to help with our contirbutions. Other than that, we were >> always under the assumption that the communit was moving forward and we >> thought we could contribute a few things. >> >> Most recently we have built a lot of components around Aria (including >> Tosca 1.1). Issue is there are no active members that can commit our PRs. >> We are ready to contribute but need to know what the interest of the >> community. >> >> Tom: Tal, Ido? Opinions? >> >> Ido: Speaking on behalf of Cloudify, currently we do not have any >> committers in the Aria project. We are not actively working on Aria at the >> moment - as a company we have other initiatives to work on, and other >> engagements such as LF and ONAP community. I don't know if that is going >> to change. >> >> Tal: I'd like to suggest a few options to move forward. Neither Cloudify >> nor Ericsson can take leadership of the project. You can take Apache >> incubation projects into "The Attic". Different status. Can be unfrozen in >> the future. Taking it out of the attic is much easier than starting a new >> project. Another option is to fork the project and take it to github >> (outside of the Apache org). >> >> Tom: Thats just forking the code on github. >> >> Tal: Yes. We would tell our mentors in ASF that we are leaving the >> project and will continue on github. >> >> Tom: They can fork independently and collaborate (Cloudify and Ericsson). >> >> Tal: Ericsson chose this project because they thought there was an active >> community around an orchestrator. One option is to look into the Cloudify >> "community edition". This does not support TOSCA proper but is an option. >> >> DJ: The important part of your last point was to use a pure TOSCA parser >> implementation. This is why we were in favor of Aria. >> >> I would like to hear from you (Tal) about moving this to github. >> >> Can you explain why this project was started in Apache? >> >> Tal: Pros (to github): more flexibility (including management). Cons: the >> management complications. >> >> Right now Aria is being used by the ONAP project in LF. The fact that >> the code belonged to a foundation made it attractive to that organization. >> WIth that said, Aria does not have a big place. >> >> There are many successful reasons for how projects are successful on >> github with healthy communities. >> >> I worked hard to get support within Apache for Aria and got mild >> support. The community at large did not support this much. >> >> Sunil: This is exactly the question I asked to Arthur a year ago. >> >> Tal: This made sense because it helped us join the open-o and onap >> communities. We hoped those folks would contribute back to the project. >> Unfortunately those folks haven't, and I am not hopeful that those folks >> will. >> >> I am actually working on a next-generation of Aria. I am rewriting >> everything in scratch in Go to create a stateless parser (TOSCA). I have a >> lot of faith in TOSCA but the approach needs to be a lot simpler. That >> might be out there on the community to collaborate with. >> >> DJ: As you already pointed out, we are trying to understand if your new >> project would have the same attraction. >> >> Sunil: Attracting contributors is not necessarily related to Apache. >> Tensorflow is a massive project that is just on github without any >> organizational affiliation. >> >> Shen: Cloudify started this project on Apache. If Ericsson wants to >> reboot Aria is this possible? >> >> Shen introduces himself as a Product Manager at Ericsson. >> >> Suneel: Once the project is part of ASF its owned by ASF. The problem is >> that the active commiters are no longer interested in participating in the >> project. Chicken & egg problem. >> >> Shen: Is there a way forward? >> >> Suneel: Ido what are Cloudify's plans going forward? >> >> Ido: See comment above. >> >> Suneel: Cloudify has no stake currently in participating in the project. >> >> Ido: I am just saying this is the current status. >> >> Tal: There might be interest in Aria but is there interest in keeping it >> in Apache? >> >> Tom: This is one remedy to the chicken problem. >> >> Ido: I think it would be better to keep it
Podling Report Reminder - June 2018
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, 20 June 2018, 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, June 06). 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. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. 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. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/June2018 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
