Re: [RESULT] [VOTE] Retire AriaTosca Podling

[Suneel Marthi]

...u r still an Apache committer - (free floating committer now) :-)

On Thu, Jun 28, 2018 at 10:14 AM, Tal Liron  wrote:

> On Thu, Jun 28, 2018 at 8:09 AM Thomas Nadeau 
> wrote:
>
> > I fully intend to take the ASF Committer role seriously and help out/
> > contribute to other projects as time permits going forward and look
> > forward to working
> > and collaborating with you all in the future.
> >
>
> We are only committers on AriaTosca, so now that it's being retired we are
> kings of nothing. :)
>

[RESULT] [VOTE] Retire AriaTosca Podling

[Suneel Marthi]

The vote ended today and here are the results.

Binding +1 : 5 (Jakob Homan, Tal Liron, Thomas Nadeau, John Ament, Suneel
Marthi)

The Vote to retire this podling has passed and will move forward with next
steps to retire this podling.

Thanks for all the votes.

Suneel

Re: [VOTE] Retire AriaTosca Podling

[Suneel Marthi]

Hi Doron,

I agree with Tal - you are more than welcome to fork the project and
continue development internally at work.
The project has lost all active committers who could oversee the project -
hence it makes complete sense to retire this podling.



On Thu, Jun 28, 2018 at 2:58 AM, Tal Liron  wrote:

> Hi Doron,
>
> You do not have voting rights on this issue.
>
> However, I don't think you should be too worried. The license is Apache
> 2.0, and you are very welcome to fork the project and continue its
> development. There have been many successful forks in the history of open
> source. This project may very well live long and prosper under new
> management. It's also possible (so I understand) to resurrect a project
> back into incubation should it prove viable in the future.
>
> On Thu, Jun 28, 2018 at 1:08 AM Doron Bleiberg  >
> wrote:
>
> > -1 At ECI Telecom we are checking whether to contribute for this project.
> > This will be done as part of the work on our MANO product. We will have
> > final resolution by the end of July, after we will complete our tools
> > comparison and selection.
> >
> > -Original Message-
> > From: Suneel Marthi [mailto:smar...@apache.org]
> > Sent: June 28, 2018 00:19
> > To: dev@ariatosca.incubator.apache.org
> > Subject: Re: [VOTE] Retire AriaTosca Podling
> >
> > This is a reminder that this Vote ends tomorrow and so far we seem to
> have
> > consensus to retire this podling.
> >
> > On Mon, Jun 25, 2018 at 4:41 PM, Vishwanath Jayaraman <
> > vishwana...@hotmail.com> wrote:
> >
> > > +1
> > >
> > > Sent from my iPhone
> > >
> > > > On Jun 25, 2018, at 3:12 PM, Jakob Homan  wrote:
> > > >
> > > > +1
> > > >
> > > >> On 25 June 2018 at 09:09, John D. Ament 
> > wrote:
> > > >> +1
> > > >>
> > > >>> On Mon, Jun 25, 2018, 10:40 AM Suneel Marthi 
> > > wrote:
> > > >>>
> > > >>> In light of the discussion on
> > > >>> https://lists.apache.org/thread.html/ccad17927b23573e0bef3062c98e7
> > > >>> a
> > > 72455415be959b2f5859ed6898@%3Cdev.ariatosca.apache.org%3E
> > > >>>
> > > >>> and given that the project has not seen any activity over the past
> > > >>> 5 months and all of the active committers have no time for the
> > > >>> project -
> > > this
> > > >>> is a call for Vote to retire the AriaTosca podling.
> > > >>>
> > > >>> Please Vote :
> > > >>>
> > > >>> +1 = Yes,. Retire AriaTosca
> > > >>> -1 = No, because .
> > > >>>
> > > >>>
> > > >>> Here's my +1.
> > > >>>
> > > >>>
> > > >>> Suneel
> > >
> >
> > 
> ___
> >
> > This e-mail message is intended for the recipient only and contains
> > information which is
> > CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have
> > received this
> > transmission in error, please inform us by e-mail, phone or fax, and then
> > delete the original
> > and all copies thereof.
> > 
> ___
> >
>

Re: [VOTE] Retire AriaTosca Podling

[Suneel Marthi]

This is a reminder that this Vote ends tomorrow and so far we seem to have
consensus to retire this podling.

On Mon, Jun 25, 2018 at 4:41 PM, Vishwanath Jayaraman <
vishwana...@hotmail.com> wrote:

> +1
>
> Sent from my iPhone
>
> > On Jun 25, 2018, at 3:12 PM, Jakob Homan  wrote:
> >
> > +1
> >
> >> On 25 June 2018 at 09:09, John D. Ament  wrote:
> >> +1
> >>
> >>> On Mon, Jun 25, 2018, 10:40 AM Suneel Marthi 
> wrote:
> >>>
> >>> In light of the discussion on
> >>> https://lists.apache.org/thread.html/ccad17927b23573e0bef3062c98e7a
> 72455415be959b2f5859ed6898@%3Cdev.ariatosca.apache.org%3E
> >>>
> >>> and given that the project has not seen any activity over the past 5
> >>> months and all of the active committers have no time for the project -
> this
> >>> is a call for Vote to retire the AriaTosca podling.
> >>>
> >>> Please Vote :
> >>>
> >>> +1 = Yes,. Retire AriaTosca
> >>> -1 = No, because .
> >>>
> >>>
> >>> Here's my +1.
> >>>
> >>>
> >>> Suneel
>

Re: [VOTE] Retire AriaTosca Podling

[Suneel Marthi]

... and this vote will remain open for 72 hrs ending on Thursday - June 28.

On Mon, Jun 25, 2018 at 10:40 AM, Suneel Marthi  wrote:

> In light of the discussion on https://lists.apache.org/thread.html/
> ccad17927b23573e0bef3062c98e7a72455415be959b2f5859ed6898@%
> 3Cdev.ariatosca.apache.org%3E
>
> and given that the project has not seen any activity over the past 5
> months and all of the active committers have no time for the project - this
> is a call for Vote to retire the AriaTosca podling.
>
> Please Vote :
>
> +1 = Yes,. Retire AriaTosca
> -1 = No, because .
>
>
> Here's my +1.
>
>
> Suneel
>

[VOTE] Retire AriaTosca Podling

[Suneel Marthi]

In light of the discussion on
https://lists.apache.org/thread.html/ccad17927b23573e0bef3062c98e7a72455415be959b2f5859ed6898@%3Cdev.ariatosca.apache.org%3E

and given that the project has not seen any activity over the past 5 months
and all of the active committers have no time for the project - this is a
call for Vote to retire the AriaTosca podling.

Please Vote :

+1 = Yes,. Retire AriaTosca
-1 = No, because .


Here's my +1.


Suneel

Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes

[Suneel Marthi]

https://incubator.apache.org/guides/retirement.html

On Mon, Jun 25, 2018 at 9:59 AM, Tal Liron  wrote:

> Sadly, yes.
>
> Do you have a link the formal procedure? Does it need to be proposed in
> private@ or here?
>
> On Mon, Jun 25, 2018 at 7:57 AM Thomas Nadeau 
> wrote:
>
> > +1
> >
> > > On Jun 25, 2018, at 8:56 AM, Suneel Marthi  wrote:
> > >
> > > Given that its been over a month since our last meeting about the
> future
> > of
> > > AriaTosca - and wee have not heard back from Ericsson - I propose that
> we
> > > start a [DISCUSS] to retire this project.
> > >
> > > Thoughts?
> > >
> > > On Thu, Jun 7, 2018 at 6:51 PM, Tal Liron  wrote:
> > >
> > >> I actually think my work is not orthogonal... It is a complete TOSCA
> > parser
> > >> that can do a lot of what AriaTosca does, if not more, in that
> respect.
> > So,
> > >> depending on what folk think about it my project, it might make since
> to
> > >> move development focus there. (It's also Apache licensed.)
> > >>
> > >> However, it does not exactly include an orchestrator. Instead, it
> > targets
> > >> Kubernetes, which does your orchestration for you.
> > >>
> > >> If folk want an AriaTosca-style orchestrator, I don't think it would
> be
> > too
> > >> hard to add one. AriaTosca's orchestration is very simple. I have some
> > >> thoughts for how to do so and can assist, though I am not personally
> > >> interested in classical orchestration. A think a better option might
> be
> > to
> > >> plug it into Cloudify Community Edition, which is a serious
> > orchestrator.
> > >> The Cloudify folk might be interested in assisting on that, since they
> > do
> > >> want TOSCA support in their product.
> > >>
> > >> I am planning on a public release on Monday, assuming I don't have to
> > much
> > >> fun this weekend. :)
> > >>
> > >> On Thu, Jun 7, 2018 at 4:20 PM Thomas Nadeau  >
> > >> wrote:
> > >>
> > >>>Tal’s work is orthogonal to the status of the project as we
> > >>> discussed.  Sunil’s
> > >>> ‘ask’ hasn’t been addressed, which was your guys’ action from the
> > meeting
> > >>> we had about
> > >>> 2 weeks ago now.
> > >>>
> > >>>—Tom
> > >>>
> > >>>
> > >>>> On Jun 7, 2018, at 9:07 AM, S Shenbaga Rajan <
> > >>> s.shenbaga.ra...@ericsson.com> wrote:
> > >>>>
> > >>>> Hi Tom,
> > >>>>
> > >>>> There are some internal delays anyway. But I thought we will be
> having
> > >>> for some info from Tal's work and assess the same, before we can
> make a
> > >>> final decision.
> > >>>>
> > >>>> Thanks,
> > >>>> /Shen
> > >>>>
> > >>>> -Original Message-
> > >>>> From: Thomas Nadeau [mailto:tnadeaua...@gmail.com]
> > >>>> Sent: Thursday, June 07, 2018 6:30 PM
> > >>>> To: dev@ariatosca.incubator.apache.org
> > >>>> Cc: smar...@apache.org
> > >>>> Subject: Re: Updated: Discuss The Future Of AriaTosca - Meeting
> > Minutes
> > >>>>
> > >>>> Guys,
> > >>>>
> > >>>> Its been a week (and well past “the end of this week”). Do you have
> > any
> > >>> updates ?
> > >>>>
> > >>>> —Tom
> > >>>>
> > >>>>
> > >>>>> On May 30, 2018, at 1: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
> > >>>>> Subje

Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes

[Suneel Marthi]

Given that its been over a month since our last meeting about the future of
AriaTosca - and wee have not heard back from Ericsson - I propose that we
start a [DISCUSS] to retire this project.

Thoughts?

On Thu, Jun 7, 2018 at 6:51 PM, Tal Liron  wrote:

> I actually think my work is not orthogonal... It is a complete TOSCA parser
> that can do a lot of what AriaTosca does, if not more, in that respect. So,
> depending on what folk think about it my project, it might make since to
> move development focus there. (It's also Apache licensed.)
>
> However, it does not exactly include an orchestrator. Instead, it targets
> Kubernetes, which does your orchestration for you.
>
> If folk want an AriaTosca-style orchestrator, I don't think it would be too
> hard to add one. AriaTosca's orchestration is very simple. I have some
> thoughts for how to do so and can assist, though I am not personally
> interested in classical orchestration. A think a better option might be to
> plug it into Cloudify Community Edition, which is a serious orchestrator.
> The Cloudify folk might be interested in assisting on that, since they do
> want TOSCA support in their product.
>
> I am planning on a public release on Monday, assuming I don't have to much
> fun this weekend. :)
>
> On Thu, Jun 7, 2018 at 4:20 PM Thomas Nadeau 
> wrote:
>
> > Tal’s work is orthogonal to the status of the project as we
> > discussed.  Sunil’s
> > ‘ask’ hasn’t been addressed, which was your guys’ action from the meeting
> > we had about
> > 2 weeks ago now.
> >
> > —Tom
> >
> >
> > > On Jun 7, 2018, at 9:07 AM, S Shenbaga Rajan <
> > s.shenbaga.ra...@ericsson.com> wrote:
> > >
> > > Hi Tom,
> > >
> > > There are some internal delays anyway. But I thought we will be having
> > for some info from Tal's work and assess the same, before we can make a
> > final decision.
> > >
> > > Thanks,
> > > /Shen
> > >
> > > -Original Message-
> > > From: Thomas Nadeau [mailto:tnadeaua...@gmail.com]
> > > Sent: Thursday, June 07, 2018 6:30 PM
> > > To: dev@ariatosca.incubator.apache.org
> > > Cc: smar...@apache.org
> > > Subject: Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes
> > >
> > > Guys,
> > >
> > > Its been a week (and well past “the end of this week”). Do you have any
> > updates ?
> > >
> > > —Tom
> > >
> > >
> > >> On May 30, 2018, at 1: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
> > >

Re: Podling Report Reminder - June 2018

[Suneel Marthi]

Ok, i'll file the report. We still have time for edits.

On Sat, Jun 2, 2018 at 2:22 PM, Thomas Nadeau 
wrote:

> I read over the doc and I think it sums things up correctly.
>
> —Tom
>
>
> > On Jun 2, 2018, at 1:12 PM, Suneel Marthi 
> wrote:
> >
> > I put together a doc -
> > https://docs.google.com/document/d/1UZndvPXs9j4ydjje_
> uZLIU3NNEsqmDsogd4dDnJCPsM/edit?usp=sharing
> >
> > Please feel free to edit.
> >
> > On Sat, Jun 2, 2018 at 8:18 AM, John D. Ament 
> wrote:
> >
> >> All,
> >>
> >> Please see below reminder.  Any available to get a report together?
> >>
> >> John
> >>
> >> On Tue, May 29, 2018 at 7:46 PM  wrote:
> >>
> >>> 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
> >>>
> >>
>
>

Re: Podling Report Reminder - June 2018

[Suneel Marthi]

I put together a doc -
https://docs.google.com/document/d/1UZndvPXs9j4ydjje_uZLIU3NNEsqmDsogd4dDnJCPsM/edit?usp=sharing

Please feel free to edit.

On Sat, Jun 2, 2018 at 8:18 AM, John D. Ament  wrote:

> All,
>
> Please see below reminder.  Any available to get a report together?
>
> John
>
> On Tue, May 29, 2018 at 7:46 PM  wrote:
>
> > 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
> >
>

Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes

[Suneel Marthi]

@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

Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes

[Suneel Marthi]

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 under Apache than starting a
> github project. Why can't we just add Ericsson to the Committers list?
>
> Suneel:  Do we have any PRs that need to be merged?
>
> DJ: We have many things which we wish to contribute.
>
> Shen: We have many improvements.
>
> Tom: Are they ready as a 

Re: Conference Info for Monday, June 21, 10AM EST Session

[Suneel Marthi]

You say 'discussion around closing down AriaTosca' - seems like some of us
already have an end goal in mind ???

On Fri, May 18, 2018 at 8:11 AM, Thomas Nadeau 
wrote:

>
> Hi,
>
> Below is the conference info for our call on Monday regarding the
> discussion around closing down AriaTosca.
> Anyone in the community is invited to participate and can use this
> conference info to connect.
> The invite supports as many people as I expect to show up, but if
> you for some reason have trouble joining,
> please directly email me.
>
> I will be posting the meeting minutes/notes after the meeting to
> the list here as a written record of what
> transpires in case anyone cannot attend, as well as to indicate to
> the community any decisions/actions
> that were agreed upon.
>
> —Tom
>
>
>
> The following meeting has been forwarded:
>
> Subject: Fwd: Discuss Closing Down AriaTosca  (DO NOT FORWARD THIS INVITE)
> Organizer: inv...@meet.bluejeans.com 
>
> Location: https://bluejeans.com/7897462078/5797?src=calendarLink <
> https://bluejeans.com/7897462078/5797?src=calendarLink>
> Time: Monday, May 21, 2018, 10:00:00 AM - 11:00:00 AM GMT +00:00 Britain,
> Ireland, Portugal
>
> Invitees: tnad...@redhat.com ;
> tnad...@lucidvision.com 
>
>
> *~*~*~*~*~*~*~*~*~*
>
>
>
> - Original Appointment -
> Subject: Fwd: Discuss Closing Down AriaTosca  (DO NOT FORWARD THIS INVITE)
> Organizer: inv...@meet.bluejeans.com 
>
> Location: https://bluejeans.com/7897462078/5797?src=calendarLink <
> https://bluejeans.com/7897462078/5797?src=calendarLink>
> Time: Monday, May 21, 2018, 10:00:00 AM - 11:00:00 AM GMT +00:00 Britain,
> Ireland, Portugal
>
> Invitees: tnad...@redhat.com 
>
>
> *~*~*~*~*~*~*~*~*~*
>
>
>
>
> To join the meeting on a computer or mobile phone : https://bluejeans.com/
> 7897462078/5797?src=calendarLink  7897462078/5797?src=calendarLink>
>
> Here are the details for the meeting you scheduled:
>
> To join from a Red Hat Deskphone or Softphone, dial: 84336.
> ---
> Connecting directly from a room system?
>
> Just want to dial in on your phone?
>
> 1.) Dial one of the following numbers:
> 408-915-6466 (US)
>
> See all numbers: https://www.redhat.com/en/conference-numbers <
> https://www.redhat.com/en/conference-numbers>
> 2.) Enter Meeting ID: 7897462078
>
> 3.) Enter Passcode: 5797
> 4.) Press #
>
> ---
> Want to test your video connection?
> https://bluejeans.com/111 
>
>

Re: [Discuss] Future of AriaTosca

[Suneel Marthi]

On Wed, May 16, 2018 at 4:17 PM, Thomas Nadeau <tnad...@lucidvision.com>
wrote:

>
> I meant that he was 2 ahead of Israel.  *)
>

Neh... its 3.5 hrs ahead of Israel.

>
> Anyways… is Monday at 10AM EST cool for everyone?
>

Please go ahead and schedule the meeting, I'll not be available but
nevertheless go ahead without me.


>
> > On May 16, 2018, at 11:44 AM, Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
> >
> > India is GMT + 5.5  (Indian culture is setup to handle Float types)
> >
> >
> >
> > On Wed, May 16, 2018 at 10:40 AM, Thomas Nadeau <tnad...@lucidvision.com
> >
> > wrote:
> >
> >>
> >>Sorry to not respond to this thread; been very busy with my new
> >> gig.
> >>
> >>I am happy to setup a Zoom for this Thursday or Friday and take
> >> meeting minutes
> >> which will be published to this list/Slack.  The challenge has always
> been
> >> the spanning
> >> timezones.  Tal is in Central, I am EST and DJ is GMT+2 I think.
> >>
> >>I propose we book 10 or 11AM EST which is more or less in the
> >> center of those.
> >>
> >>—Tom
> >>
> >>
> >>> On May 16, 2018, at 1:40 AM, Suneel Marthi <suneel.mar...@gmail.com>
> >> wrote:
> >>>
> >>> DJ, if u could setup a call - please go ahead and do it - I really
> don't
> >>> have time for this given my day job.
> >>>
> >>> If Tal and other committers could join the call and decide on future
> >> course
> >>> of action that would be great.
> >>>
> >>>
> >>>
> >>> On Wed, May 16, 2018 at 1:30 AM, D Jayachandran <
> >> d.jayachand...@ericsson.com
> >>>> wrote:
> >>>
> >>>> Hi Suneel,
> >>>>
> >>>> We in Ericsson are actively working on ARIA. We want to keep the
> project
> >>>> on and community active.
> >>>> It is just that we couldn't make any contribution because there is no
> >>>> active committer. I already contacted you regarding the same.
> >>>> Could we setup a short call to discuss on this?
> >>>>
> >>>> Thanks,
> >>>> /DJ
> >>>>
> >>>> -Original Message-
> >>>> From: Suneel Marthi [mailto:smar...@apache.org]
> >>>> Sent: Tuesday, May 15, 2018 11:53 PM
> >>>> To: dev@ariatosca.incubator.apache.org
> >>>> Subject: Re: [Discuss] Future of AriaTosca
> >>>>
> >>>> Adding dev@ to the conversation.
> >>>>
> >>>> On Mon, May 14, 2018 at 7:42 PM, Tal Liron <tal.li...@gmail.com>
> wrote:
> >>>>
> >>>>> Almost all the committers have moved on. Unless new contributors want
> >>>>> to come in and revive the efforts, the course of action seems clear.
> >>>>>
> >>>>>
> >>>>> On Mon, May 14, 2018 at 6:38 PM Suneel Marthi <smar...@apache.org>
> >>>> wrote:
> >>>>>
> >>>>>> Given that the project's not seen any activity in like 3 months and
> >>>>>> the mail lists have gone dry - reviving this discussion again about
> >>>>>> the future of AriaTosca and what the next course of action is?
> >>>>>>
> >>>>>> Thoughts/Comments ?
> >>>>>>
> >>>>>> Suneel
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
>
>

Re: [Discuss] Future of AriaTosca

[Suneel Marthi]

India is GMT + 5.5  (Indian culture is setup to handle Float types)



On Wed, May 16, 2018 at 10:40 AM, Thomas Nadeau <tnad...@lucidvision.com>
wrote:

>
> Sorry to not respond to this thread; been very busy with my new
> gig.
>
> I am happy to setup a Zoom for this Thursday or Friday and take
> meeting minutes
> which will be published to this list/Slack.  The challenge has always been
> the spanning
> timezones.  Tal is in Central, I am EST and DJ is GMT+2 I think.
>
> I propose we book 10 or 11AM EST which is more or less in the
> center of those.
>
>     —Tom
>
>
> > On May 16, 2018, at 1:40 AM, Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
> >
> > DJ, if u could setup a call - please go ahead and do it - I really don't
> > have time for this given my day job.
> >
> > If Tal and other committers could join the call and decide on future
> course
> > of action that would be great.
> >
> >
> >
> > On Wed, May 16, 2018 at 1:30 AM, D Jayachandran <
> d.jayachand...@ericsson.com
> >> wrote:
> >
> >> Hi Suneel,
> >>
> >> We in Ericsson are actively working on ARIA. We want to keep the project
> >> on and community active.
> >> It is just that we couldn't make any contribution because there is no
> >> active committer. I already contacted you regarding the same.
> >> Could we setup a short call to discuss on this?
> >>
> >> Thanks,
> >> /DJ
> >>
> >> -Original Message-
> >> From: Suneel Marthi [mailto:smar...@apache.org]
> >> Sent: Tuesday, May 15, 2018 11:53 PM
> >> To: dev@ariatosca.incubator.apache.org
> >> Subject: Re: [Discuss] Future of AriaTosca
> >>
> >> Adding dev@ to the conversation.
> >>
> >> On Mon, May 14, 2018 at 7:42 PM, Tal Liron <tal.li...@gmail.com> wrote:
> >>
> >>> Almost all the committers have moved on. Unless new contributors want
> >>> to come in and revive the efforts, the course of action seems clear.
> >>>
> >>>
> >>> On Mon, May 14, 2018 at 6:38 PM Suneel Marthi <smar...@apache.org>
> >> wrote:
> >>>
> >>>> Given that the project's not seen any activity in like 3 months and
> >>>> the mail lists have gone dry - reviving this discussion again about
> >>>> the future of AriaTosca and what the next course of action is?
> >>>>
> >>>> Thoughts/Comments ?
> >>>>
> >>>> Suneel
> >>>>
> >>>
> >>
>
>

Re: [Discuss] Future of AriaTosca

[Suneel Marthi]

Ido Berkovitch (cc'ed here) from Cloudify has been contacting me offlist
about the project - @Ido please respond to dev@ariatosca in future.

On Wed, May 16, 2018 at 10:06 AM, Tal Liron <tal.li...@gmail.com> wrote:

> Hi John, they were not private meetings -- everyone was invited on the
> public dev list, but the community is small enough that it likely felt
> quite intimate. :)
>
> I'm not sure what a meeting would accomplish. I have moved on from
> AriaTosca, as I am no longer am paid to work on it. I can't speak for Tom,
> but I imagine he would say the same.
>
> I personally have no objections to someone else picking up the project and
> taking it over.
>
> I've contacted Cloudify, the company who provided the seed code and paid
> for the majority of the work on it until now, but they have not responded.
>
> On Wed, May 16, 2018 at 6:38 AM John D. Ament <johndam...@apache.org>
> wrote:
>
> > While it may help to have meetings ultimately its a sign of the problems
> > here.  All discussion, including PR questions, should be on list.  All
> > github commentary is sent to a list as well.
> >
> > I personally had no idea DJ and Tom met privately to review.
> >
> > On Wed, May 16, 2018, 7:16 AM Suneel Marthi <smar...@apache.org> wrote:
> >
> > > DJ,
> > >
> > > You don't need me for this meeting and I won't be able to make it
> > anyways.
> > > Its best to coordinate with AriaTosca PMC and committers as to what's a
> > > good time that works for all.
> > >
> > > I'll let Tal and others respond to that.
> > >
> > > Suneel
> > >
> > > On Wed, May 16, 2018 at 2:39 AM, D Jayachandran <
> > > d.jayachand...@ericsson.com
> > > > wrote:
> > >
> > > > Hi Suneel,
> > > >
> > > > What is the meeting tool which is preferred. We usually use skype
> > meeting
> > > > calls.
> > > > Also can we have the meeting scheduled tomorrow. Could you please let
> > me
> > > > know your comfortable time for the meeting ?
> > > >
> > > > Regards,
> > > > DJ
> > > > -Original Message-
> > > > From: Suneel Marthi [mailto:suneel.mar...@gmail.com]
> > > > Sent: Wednesday, May 16, 2018 11:12 AM
> > > > To: dev@ariatosca.incubator.apache.org
> > > > Subject: Re: [Discuss] Future of AriaTosca
> > > >
> > > > On Wed, May 16, 2018 at 1:38 AM, D Jayachandran <
> > > > d.jayachand...@ericsson.com
> > > > > wrote:
> > > >
> > > > > Hi Suneel,
> > > > >
> > > > > Currently there is no pending PR's from my side. Earlier Tom and
> > > > > myself used to have one to one discussion for merging a PR.
> > > > > We have many contributions pending from our side which we have made
> > as
> > > > > PR yet as we don’t have any committer to acknowledge and merge it I
> > > > > can send those contributions as PR, if we have committers to review
> > > > > and merge it.
> > > > >
> > > >
> > > > That's the problem - all of the committers and PPMC have since moved
> > away
> > > > from the project and there's none to steer this forward.
> > > > Regardless please setup a call and let's decide on future course.
> > > >
> > > >
> > > > >
> > > > > Regards,
> > > > > DJ
> > > > >
> > > > > -Original Message-
> > > > > From: Suneel Marthi [mailto:smar...@apache.org]
> > > > > Sent: Wednesday, May 16, 2018 11:04 AM
> > > > > To: dev@ariatosca.incubator.apache.org
> > > > > Subject: Re: [Discuss] Future of AriaTosca
> > > > >
> > > > > Do u have any open PRs pending review ?  Would any of the present
> > > > > PMC/committers have time to review and merge the PRs? @Tal and
> > others ?
> > > > >
> > > > >
> > > > >
> > > > > On Wed, May 16, 2018 at 1:30 AM, D Jayachandran <
> > > > > d.jayachand...@ericsson.com
> > > > > > wrote:
> > > > >
> > > > > > Hi Suneel,
> > > > > >
> > > > > > We in Ericsson are actively working on ARIA. We want to keep the
> > > > > > project on and community active.
> > > > > > It is just that we couldn't make any contribution becau

Re: [Discuss] Future of AriaTosca

[Suneel Marthi]

On Wed, May 16, 2018 at 7:38 AM, John D. Ament <johndam...@apache.org>
wrote:

> While it may help to have meetings ultimately its a sign of the problems
> here.  All discussion, including PR questions, should be on list.  All
> github commentary is sent to a list as well.
>
> I personally had no idea DJ and Tom met privately to review.
>

That happened during one of the weekly grooming sessions that Tom used to
run. Tom did post that back on mail lists, so it wasn't a secret.

>
> On Wed, May 16, 2018, 7:16 AM Suneel Marthi <smar...@apache.org> wrote:
>
> > DJ,
> >
> > You don't need me for this meeting and I won't be able to make it
> anyways.
> > Its best to coordinate with AriaTosca PMC and committers as to what's a
> > good time that works for all.
> >
> > I'll let Tal and others respond to that.
> >
> > Suneel
> >
> > On Wed, May 16, 2018 at 2:39 AM, D Jayachandran <
> > d.jayachand...@ericsson.com
> > > wrote:
> >
> > > Hi Suneel,
> > >
> > > What is the meeting tool which is preferred. We usually use skype
> meeting
> > > calls.
> > > Also can we have the meeting scheduled tomorrow. Could you please let
> me
> > > know your comfortable time for the meeting ?
> > >
> > > Regards,
> > > DJ
> > > -Original Message-
> > > From: Suneel Marthi [mailto:suneel.mar...@gmail.com]
> > > Sent: Wednesday, May 16, 2018 11:12 AM
> > > To: dev@ariatosca.incubator.apache.org
> > > Subject: Re: [Discuss] Future of AriaTosca
> > >
> > > On Wed, May 16, 2018 at 1:38 AM, D Jayachandran <
> > > d.jayachand...@ericsson.com
> > > > wrote:
> > >
> > > > Hi Suneel,
> > > >
> > > > Currently there is no pending PR's from my side. Earlier Tom and
> > > > myself used to have one to one discussion for merging a PR.
> > > > We have many contributions pending from our side which we have made
> as
> > > > PR yet as we don’t have any committer to acknowledge and merge it I
> > > > can send those contributions as PR, if we have committers to review
> > > > and merge it.
> > > >
> > >
> > > That's the problem - all of the committers and PPMC have since moved
> away
> > > from the project and there's none to steer this forward.
> > > Regardless please setup a call and let's decide on future course.
> > >
> > >
> > > >
> > > > Regards,
> > > > DJ
> > > >
> > > > -Original Message-
> > > > From: Suneel Marthi [mailto:smar...@apache.org]
> > > > Sent: Wednesday, May 16, 2018 11:04 AM
> > > > To: dev@ariatosca.incubator.apache.org
> > > > Subject: Re: [Discuss] Future of AriaTosca
> > > >
> > > > Do u have any open PRs pending review ?  Would any of the present
> > > > PMC/committers have time to review and merge the PRs? @Tal and
> others ?
> > > >
> > > >
> > > >
> > > > On Wed, May 16, 2018 at 1:30 AM, D Jayachandran <
> > > > d.jayachand...@ericsson.com
> > > > > wrote:
> > > >
> > > > > Hi Suneel,
> > > > >
> > > > > We in Ericsson are actively working on ARIA. We want to keep the
> > > > > project on and community active.
> > > > > It is just that we couldn't make any contribution because there is
> > > > > no active committer. I already contacted you regarding the same.
> > > > > Could we setup a short call to discuss on this?
> > > > >
> > > > > Thanks,
> > > > > /DJ
> > > > >
> > > > > -Original Message-
> > > > > From: Suneel Marthi [mailto:smar...@apache.org]
> > > > > Sent: Tuesday, May 15, 2018 11:53 PM
> > > > > To: dev@ariatosca.incubator.apache.org
> > > > > Subject: Re: [Discuss] Future of AriaTosca
> > > > >
> > > > > Adding dev@ to the conversation.
> > > > >
> > > > > On Mon, May 14, 2018 at 7:42 PM, Tal Liron <tal.li...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Almost all the committers have moved on. Unless new contributors
> > > > > > want to come in and revive the efforts, the course of action
> seems
> > > > clear.
> > > > > >
> > > > > >
> > > > > > On Mon, May 14, 2018 at 6:38 PM Suneel Marthi <
> smar...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > >> Given that the project's not seen any activity in like 3 months
> > > > > >> and the mail lists have gone dry - reviving this discussion
> again
> > > > > >> about the future of AriaTosca and what the next course of action
> > is?
> > > > > >>
> > > > > >> Thoughts/Comments ?
> > > > > >>
> > > > > >> Suneel
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [Discuss] Future of AriaTosca

[Suneel Marthi]

DJ,

You don't need me for this meeting and I won't be able to make it anyways.
Its best to coordinate with AriaTosca PMC and committers as to what's a
good time that works for all.

I'll let Tal and others respond to that.

Suneel

On Wed, May 16, 2018 at 2:39 AM, D Jayachandran <d.jayachand...@ericsson.com
> wrote:

> Hi Suneel,
>
> What is the meeting tool which is preferred. We usually use skype meeting
> calls.
> Also can we have the meeting scheduled tomorrow. Could you please let me
> know your comfortable time for the meeting ?
>
> Regards,
> DJ
> -Original Message-
> From: Suneel Marthi [mailto:suneel.mar...@gmail.com]
> Sent: Wednesday, May 16, 2018 11:12 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: [Discuss] Future of AriaTosca
>
> On Wed, May 16, 2018 at 1:38 AM, D Jayachandran <
> d.jayachand...@ericsson.com
> > wrote:
>
> > Hi Suneel,
> >
> > Currently there is no pending PR's from my side. Earlier Tom and
> > myself used to have one to one discussion for merging a PR.
> > We have many contributions pending from our side which we have made as
> > PR yet as we don’t have any committer to acknowledge and merge it I
> > can send those contributions as PR, if we have committers to review
> > and merge it.
> >
>
> That's the problem - all of the committers and PPMC have since moved away
> from the project and there's none to steer this forward.
> Regardless please setup a call and let's decide on future course.
>
>
> >
> > Regards,
> > DJ
> >
> > -Original Message-
> > From: Suneel Marthi [mailto:smar...@apache.org]
> > Sent: Wednesday, May 16, 2018 11:04 AM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: Re: [Discuss] Future of AriaTosca
> >
> > Do u have any open PRs pending review ?  Would any of the present
> > PMC/committers have time to review and merge the PRs? @Tal and others ?
> >
> >
> >
> > On Wed, May 16, 2018 at 1:30 AM, D Jayachandran <
> > d.jayachand...@ericsson.com
> > > wrote:
> >
> > > Hi Suneel,
> > >
> > > We in Ericsson are actively working on ARIA. We want to keep the
> > > project on and community active.
> > > It is just that we couldn't make any contribution because there is
> > > no active committer. I already contacted you regarding the same.
> > > Could we setup a short call to discuss on this?
> > >
> > > Thanks,
> > > /DJ
> > >
> > > -Original Message-
> > > From: Suneel Marthi [mailto:smar...@apache.org]
> > > Sent: Tuesday, May 15, 2018 11:53 PM
> > > To: dev@ariatosca.incubator.apache.org
> > > Subject: Re: [Discuss] Future of AriaTosca
> > >
> > > Adding dev@ to the conversation.
> > >
> > > On Mon, May 14, 2018 at 7:42 PM, Tal Liron <tal.li...@gmail.com>
> wrote:
> > >
> > > > Almost all the committers have moved on. Unless new contributors
> > > > want to come in and revive the efforts, the course of action seems
> > clear.
> > > >
> > > >
> > > > On Mon, May 14, 2018 at 6:38 PM Suneel Marthi <smar...@apache.org>
> > > wrote:
> > > >
> > > >> Given that the project's not seen any activity in like 3 months
> > > >> and the mail lists have gone dry - reviving this discussion again
> > > >> about the future of AriaTosca and what the next course of action is?
> > > >>
> > > >> Thoughts/Comments ?
> > > >>
> > > >> Suneel
> > > >>
> > > >
> > >
> >
>

Re: [Discuss] Future of AriaTosca

[Suneel Marthi]

On Wed, May 16, 2018 at 1:38 AM, D Jayachandran <d.jayachand...@ericsson.com
> wrote:

> Hi Suneel,
>
> Currently there is no pending PR's from my side. Earlier Tom and myself
> used to have one to one discussion for merging a PR.
> We have many contributions pending from our side which we have made as PR
> yet as we don’t have any committer to acknowledge and merge it
> I can send those contributions as PR, if we have committers to review and
> merge it.
>

That's the problem - all of the committers and PPMC have since moved away
from the project and there's none to steer this forward.
Regardless please setup a call and let's decide on future course.


>
> Regards,
> DJ
>
> -Original Message-
> From: Suneel Marthi [mailto:smar...@apache.org]
> Sent: Wednesday, May 16, 2018 11:04 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: [Discuss] Future of AriaTosca
>
> Do u have any open PRs pending review ?  Would any of the present
> PMC/committers have time to review and merge the PRs? @Tal and others ?
>
>
>
> On Wed, May 16, 2018 at 1:30 AM, D Jayachandran <
> d.jayachand...@ericsson.com
> > wrote:
>
> > Hi Suneel,
> >
> > We in Ericsson are actively working on ARIA. We want to keep the
> > project on and community active.
> > It is just that we couldn't make any contribution because there is no
> > active committer. I already contacted you regarding the same.
> > Could we setup a short call to discuss on this?
> >
> > Thanks,
> > /DJ
> >
> > -Original Message-
> > From: Suneel Marthi [mailto:smar...@apache.org]
> > Sent: Tuesday, May 15, 2018 11:53 PM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: Re: [Discuss] Future of AriaTosca
> >
> > Adding dev@ to the conversation.
> >
> > On Mon, May 14, 2018 at 7:42 PM, Tal Liron <tal.li...@gmail.com> wrote:
> >
> > > Almost all the committers have moved on. Unless new contributors
> > > want to come in and revive the efforts, the course of action seems
> clear.
> > >
> > >
> > > On Mon, May 14, 2018 at 6:38 PM Suneel Marthi <smar...@apache.org>
> > wrote:
> > >
> > >> Given that the project's not seen any activity in like 3 months and
> > >> the mail lists have gone dry - reviving this discussion again about
> > >> the future of AriaTosca and what the next course of action is?
> > >>
> > >> Thoughts/Comments ?
> > >>
> > >> Suneel
> > >>
> > >
> >
>

Re: [Discuss] Future of AriaTosca

[Suneel Marthi]

DJ, if u could setup a call - please go ahead and do it - I really don't
have time for this given my day job.

If Tal and other committers could join the call and decide on future course
of action that would be great.



On Wed, May 16, 2018 at 1:30 AM, D Jayachandran <d.jayachand...@ericsson.com
> wrote:

> Hi Suneel,
>
> We in Ericsson are actively working on ARIA. We want to keep the project
> on and community active.
> It is just that we couldn't make any contribution because there is no
> active committer. I already contacted you regarding the same.
> Could we setup a short call to discuss on this?
>
> Thanks,
> /DJ
>
> -Original Message-
> From: Suneel Marthi [mailto:smar...@apache.org]
> Sent: Tuesday, May 15, 2018 11:53 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: [Discuss] Future of AriaTosca
>
> Adding dev@ to the conversation.
>
> On Mon, May 14, 2018 at 7:42 PM, Tal Liron <tal.li...@gmail.com> wrote:
>
> > Almost all the committers have moved on. Unless new contributors want
> > to come in and revive the efforts, the course of action seems clear.
> >
> >
> > On Mon, May 14, 2018 at 6:38 PM Suneel Marthi <smar...@apache.org>
> wrote:
> >
> >> Given that the project's not seen any activity in like 3 months and
> >> the mail lists have gone dry - reviving this discussion again about
> >> the future of AriaTosca and what the next course of action is?
> >>
> >> Thoughts/Comments ?
> >>
> >> Suneel
> >>
> >
>

Re: [Discuss] Future of AriaTosca

[Suneel Marthi]

Do u have any open PRs pending review ?  Would any of the present
PMC/committers have time to review and merge the PRs? @Tal and others ?



On Wed, May 16, 2018 at 1:30 AM, D Jayachandran <d.jayachand...@ericsson.com
> wrote:

> Hi Suneel,
>
> We in Ericsson are actively working on ARIA. We want to keep the project
> on and community active.
> It is just that we couldn't make any contribution because there is no
> active committer. I already contacted you regarding the same.
> Could we setup a short call to discuss on this?
>
> Thanks,
> /DJ
>
> -Original Message-
> From: Suneel Marthi [mailto:smar...@apache.org]
> Sent: Tuesday, May 15, 2018 11:53 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: [Discuss] Future of AriaTosca
>
> Adding dev@ to the conversation.
>
> On Mon, May 14, 2018 at 7:42 PM, Tal Liron <tal.li...@gmail.com> wrote:
>
> > Almost all the committers have moved on. Unless new contributors want
> > to come in and revive the efforts, the course of action seems clear.
> >
> >
> > On Mon, May 14, 2018 at 6:38 PM Suneel Marthi <smar...@apache.org>
> wrote:
> >
> >> Given that the project's not seen any activity in like 3 months and
> >> the mail lists have gone dry - reviving this discussion again about
> >> the future of AriaTosca and what the next course of action is?
> >>
> >> Thoughts/Comments ?
> >>
> >> Suneel
> >>
> >
>

Re: [Discuss] Future of AriaTosca

[Suneel Marthi]

Adding dev@ to the conversation.

On Mon, May 14, 2018 at 7:42 PM, Tal Liron <tal.li...@gmail.com> wrote:

> Almost all the committers have moved on. Unless new contributors want to
> come in and revive the efforts, the course of action seems clear.
>
>
> On Mon, May 14, 2018 at 6:38 PM Suneel Marthi <smar...@apache.org> wrote:
>
>> Given that the project's not seen any activity in like 3 months and the
>> mail lists have gone dry - reviving this discussion again about the future
>> of AriaTosca and what the next course of action is?
>>
>> Thoughts/Comments ?
>>
>> Suneel
>>
>

Re: ASF Podling Report for AriaTosca

[Suneel Marthi]

John, should be able to grant u write access to wiki

On Mon, Mar 5, 2018 at 9:20 AM, Thomas Nadeau <tnadeaua...@gmail.com> wrote:

> I just tried logging in here but my apache.org credentials do not seem to
> work. Does someone need to add me to a group, etc.. ?
>
> https://wiki.apache.org/incubator/March2018
>
> --Tom
>
>
> On Mon, Mar 5, 2018 at 9:16 AM, Suneel Marthi <smar...@apache.org> wrote:
>
> > Thanks @tnadeau.
> >
> > Please go ahead and post it to incubator wiki if u have access - else i
> can
> > do it later today and sign-off.
> >
> > On Mon, Mar 5, 2018 at 9:14 AM, Thomas Nadeau <tnad...@apache.org>
> wrote:
> >
> > > Community:
> > >
> > > It looks like we are on the next cycle for podling reports, and we need
> > to
> > > have one finished for John et al by March 7.  Since not much has
> changed
> > > since I wrote one up in February, I simply renamed that one and it can
> be
> > > found here:
> > >
> > > https://cwiki.apache.org/confluence/pages/editpage.
> > action?pageId=75966486
> > >
> > > Please take a look at what I have there and comment/hack it.  Again, I
> > must
> > > submit this by March 7.
> > >
> > > --Tom
> > >
> >
>

Re: ASF Podling Report for AriaTosca

[Suneel Marthi]

Thanks @tnadeau.

Please go ahead and post it to incubator wiki if u have access - else i can
do it later today and sign-off.

On Mon, Mar 5, 2018 at 9:14 AM, Thomas Nadeau  wrote:

> Community:
>
> It looks like we are on the next cycle for podling reports, and we need to
> have one finished for John et al by March 7.  Since not much has changed
> since I wrote one up in February, I simply renamed that one and it can be
> found here:
>
> https://cwiki.apache.org/confluence/pages/editpage.action?pageId=75966486
>
> Please take a look at what I have there and comment/hack it.  Again, I must
> submit this by March 7.
>
> --Tom
>

Re: merging paused until release is completed

[Suneel Marthi]

I don't see why u can't push a PR when a release is in progress as long as
the PRs are not merged until the release is finalized and have been rebased
off of the latest master.

Ofcourse you could always have development continue on a different branch
if you are comfortable with merging and rebasing the branches to master.

On Tue, Jan 9, 2018 at 7:52 AM, Thomas Nadeau  wrote:

> I agree for the next release. This was just the easiest approach for me
> since I had little assistance doing this first one.
>
> --Tom
>
> On Tue, Jan 9, 2018 at 7:49 AM, John D. Ament 
> wrote:
>
> > Does it make sense to create a branch for the release (when prepped) and
> > merge that in when done?  I'd hate to see development slow down due to
> the
> > release window in flight.  Most other projects don't stop committing
> while
> > this is happening.
> >
> > On Tue, Jan 9, 2018 at 7:41 AM Thomas Nadeau 
> > wrote:
> >
> > > I just saw a PR pushed Vaish and realized we probably had not
> > communicated
> > > that we're holding off on merging PRs until the release is finished.
> The
> > > reasoning is to leave master in its current state in case anything odd
> > > happens and we need to redo the release (which has happened).
> > >
> > > Note that PRs may need to be rebased once we open the gates again, as
> > there
> > > may be PRs ahead of yours.
> > >
> > > Thanks for your patience until (hopefully) Wedneday.
> > >
> > > --Tom
> > >
> >
>

Re: Status of ARIA-19 JIRA issue

[Suneel Marthi]

u could also link this Jira to Aria-1

On Sun, Jan 7, 2018 at 1:17 PM, Vishwanath Jayaraman <
vishwana...@hotmail.com> wrote:

> I was assigned the JIRA issue https://issues.apache.org/
> jira/browse/ARIA-19
>
> When I started looking at the code to fix, the issue, I noticed that the
> "% usages with string format" has now already been replaced with "string
> format" as part of pull request related to ARIA-1(https://issues.apache.
> org/jira/browse/ARIA-1) by Tal.
>
> I am going to mark the issue as Resolved and put the comment that it has
> been fixed by Tal as part of Aria-1.
>
>
> Vish
>

Re: [VOTE] publish ariatosca 0.2.0

[Suneel Marthi]

+1 binding

On Fri, Jan 5, 2018 at 12:04 PM, John D. Ament 
wrote:

> On Thu, Jan 4, 2018 at 11:54 AM Thomas Nadeau  wrote:
>
> > I updated the script and pushed the artifacts again.  The issue is that
> > test.pypi.org does not let you change artifacts once they've been
> pushed,
> > so I cannot delete the one I pushed to replace it with the updated one.
> > This should not be an issue, as you can test/verify everything else and
> > when I push to the real pypi after everyone checks this out, we should be
> > ok.
> >
> > BTW there is a bug in the asf-release script that has issues if you
> re-push
> > onto an existing release.  The script should delete the target (or
> attempt
> > to) before it svn adds the new artifacts. I can fix that once the smoke
> has
> > cleared with this release.
> >
> >
> Cool, that'll be useful.
>
> I reviewed the release.
>
> I thought there was a downloads page on http://ariatosca.apache.org/ we
> need to add one after this release goes out.  You can use
> http://deltaspike.apache.org/download.html as an example of one that works
> and is comprehensive.
>
> It would be good to have instructions on how to run the verification steps
> (I can't find the KEYS file).  but I'm +1 from a licensing point of view.
>
>
> > --Tom
> >
> >
> >
> > On Thu, Jan 4, 2018 at 11:38 AM, John D. Ament 
> > wrote:
> >
> > > Can you use the one that is checked in ?
> > > https://github.com/apache/incubator-ariatosca/blob/
> > > master/release/asf-release.sh#L138
> > >
> > >
> > > On Thu, Jan 4, 2018 at 11:37 AM Thomas Nadeau 
> > > wrote:
> > >
> > > > The asf-release.sh script we are currently using names them as they
> > are:
> > > >
> > > > function _sign_package {
> > > > local ARCHIVE_NAME=$1
> > > >
> > > > echo "Signing archive ${ARCHIVE_NAME}..."
> > > > gpg --armor --output ${ARCHIVE_NAME}.asc --detach-sig
> > ${ARCHIVE_NAME}
> > > > gpg --print-md MD5 ${ARCHIVE_NAME} > ${ARCHIVE_NAME}.md5
> > > > gpg --print-md SHA512 ${ARCHIVE_NAME} > ${ARCHIVE_NAME}.sha
> > > > }
> > > >
> > > >
> > > > I can change that to sha512 now.
> > > >
> > > > --Tom
> > > >
> > > >
> > > >
> > > > On Thu, Jan 4, 2018 at 11:14 AM, John D. Ament <
> johndam...@apache.org>
> > > > wrote:
> > > >
> > > > > Thomas,
> > > > >
> > > > > The files are still named "sha" instead of "sha512"
> > > > >
> > > > > John
> > > > >
> > > > > On Thu, Jan 4, 2018 at 10:59 AM Thomas Nadeau 
> > > > wrote:
> > > > >
> > > > > > Aria Community:
> > > > > >
> > > > > > This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If
> > the
> > > > > vote
> > > > > > passes, another vote for approving the release will take place on
> > the
> > > > > > Apache Incubator's PMC. Please verify the various release
> artifacts
> > > and
> > > > > > respond to the list with your results.  Instructions for locating
> > the
> > > > > > artifacts can be found below.
> > > > > >
> > > > > > The tarball candidate for the 0.2.0 release is in ARIA's
> /dist/dev
> > > > > folder:
> > > > > > *
> > > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > > 0.2.0-incubating/
> > > > > > <
> > > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > > 0.2.0-incubating/
> > > > > > >*
> > > > > >
> > > > > > The testing/staging pypi version can be found here:
> > > > > > https://test.pypi.org/project/apache-ariatosca/
> > > > > > Instructions for installation etc. may be found in the README
> file
> > > > inside
> > > > > > the tarball.  Note there are different instructions for
> downloading
> > > and
> > > > > > installing from test.pypi, so please refer to test.pypi.org for
> > > > > > instructions.   The list of resolved issues for this release are
> > > simply
> > > > > all
> > > > > > the issues that have been resolved thus far since the last
> release.
> > > > Those
> > > > > > can be found here:
> > https://issues.apache.org/jira/secure/RapidBoard.
> > > > > > jspa?rapidView=150=ARIA=planning&
> > > selectedIssue=ARIA-394
> > > > > >  > > > > rapidView=150=ARIA=planning=
> ARIA-394>
> > > > > > Please vote to publish this tarball on ARIA's /dist/release
> folder
> > > and
> > > > > > release on pypi.  The voting for this must be open for 3 full
> days
> > to
> > > > all
> > > > > > Committers within the project, and then for 3 full days on the
> > Apache
> > > > > PMC.
> > > > > >  Voting for the release will begin now at 12PM EST, Thursday,
> > January
> > > > 4,
> > > > > > 2018 and be completed on  12PM EST on Sunday, January 7, 2018.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > --Tom
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DRAFT] Incubator PMC Board Report - December 2017

[Suneel Marthi]

e 5
> >> reports
> >>>>>> missing and 4 reports not signed off on.  I hope we can get that
> >>> resolved
> >>>>>> in the next few days.  I have copied those podlings impacted.
> >>>>>>
> >>>>>> Incubator PMC report for December 2017
> >>>>>>
> >>>>>> The Apache Incubator is the entry path into the ASF for projects and
> >>>>>> codebases wishing to become part of the Foundation's efforts.
> >>>>>>
> >>>>>> There are currently 53 podlings incubating.  In the month of
> >> November,
> >>> we
> >>>>>> executed six releases, added one IPMC member and received the
> >>> resignation
> >>>>>> of another (which is in flight until their sole podling retires).
> We
> >>>>> added
> >>>>>> two podlings to our roster, have a few more in the pipeline and have
> >>> one
> >>>>>> podling planning to graduate this month.
> >>>>>>
> >>>>>> * Community
> >>>>>>
> >>>>>> New IPMC members:
> >>>>>>
> >>>>>> - Michael Semb Wever
> >>>>>>
> >>>>>> People who left the IPMC:
> >>>>>>
> >>>>>> - Upayavira (not processed in LDAP yet)
> >>>>>>
> >>>>>> * New Podlings
> >>>>>>
> >>>>>> - Crail
> >>>>>> - Service Comb
> >>>>>>
> >>>>>> * Podlings that failed to report, expected next month
> >>>>>>
> >>>>>> - Amaterasu - Activity stopped late November
> >>>>>> - Aria Tosca
> >>>>>> - HTrace - 0 on list activity
> >>>>>> - Pony Mail - Low activity, suspect just missed.
> >>>>>> - Wave - Retiring
> >>>>>>
> >>>>>> * Podlings Missing sign off
> >>>>>>
> >>>>>> - Griffin
> >>>>>> - Myriad
> >>>>>> - OpenWhisk
> >>>>>> - Spot
> >>>>>>
> >>>>>> * Graduations
> >>>>>>
> >>>>>> The board has motions for the following:
> >>>>>>
> >>>>>> - Trafodion
> >>>>>> - Your podling here?
> >>>>>> - Your podling here?
> >>>>>>
> >>>>>> * Releases
> >>>>>>
> >>>>>> The following releases entered distribution during the month of
> >>>>>> November:
> >>>>>>
> >>>>>> - 2017-11-01 Apache Freemarker  2.3.27
> >>>>>> - 2017-11-08 Apache Netbeans HTML4J 1.5
> >>>>>> - 2017-11-15 Apache Mnemonic0.10.0
> >>>>>> - 2017-11-15 Apache MXNet   0.12.1
> >>>>>> - 2017-11-18 Apache Netbeans HTML4J 1.5.1
> >>>>>> - 2017-11-28 Apache Griffin 0.1.6
> >>>>>>
> >>>>>> * IP Clearance
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> * Legal / Trademarks
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> * Infrastructure
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> * Miscellaneous
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> * Credits
> >>>>>>
> >>>>>>
> >> --
> >>>>>> Table of Contents
> >>>>>> Amaterasu
> >>>>>> AriaTosca
> >>>>>> Crail
> >>>>>> Daffodil
> >>>>>> Gearpump
> >>>>>> Griffin
> >>>>>> Hivemall
> >>>>>> HTrace
> >>>>>> Myriad
> >>>>>> Omid
> >>>>>> OpenWhisk
> >>>>>> PageSpeed
> >>>>>> Pony Mail
> >>>>>> Pulsar
> >>>>>> Quickstep
> >>>>&

Re: Subscription access request

[Suneel Marthi]

Its dev-subscr...@ariatosca.apache.org

On Fri, Dec 8, 2017 at 9:24 AM, Thomas Nadeau 
wrote:

>
> You need to send an email to dev-subscr...@apache.org. You will
> get an email confirmation with a link or you can simply reply to it to
> confirm and then you are in.
>
> —Tom
>
>
> > On Dec 8, 2017, at 1:47 AM, Venkatesan Venugopal  ericsson.com> wrote:
> >
> > Hi,
> >
> > Am looking for subscription for dev@ariatosca.incubator.apache.org
>  to have my queries posted to
> dev forum.
> > Could you help with this ?
> >
> > Regards,
> > Venkatesan V
> >
>
>

Re: Subscription access request

[Suneel Marthi]

Subscribe to dev-subscr...@ariatosca.apache.org

Sent from my iPhone

> On Dec 8, 2017, at 1:47 AM, Venkatesan Venugopal 
>  wrote:
> 
> Hi,
> 
> Am looking for subscription for 
> dev@ariatosca.incubator.apache.org 
> to have my queries posted to dev forum.
> Could you help with this ?
> 
> Regards,
> Venkatesan V
> 

Re: Subscribe for dev mailing list

[Suneel Marthi]

Email dev-subscr...@ariatosca.apache.org

Sent from my iPhone

> On Dec 5, 2017, at 12:48 AM, Vaishali Krishnamurthy 
>  wrote:
> 
> Hi,
> 
> 
> 
> Am looking for subscription for dev@ariatosca.incubator.apache.org to have
> my queries posted to dev forum.
> 
> Could you help with this ?
> 
> 
> 
> Regards,
> 
> Vaishali

Re: Transition to Gitbox Complete

[Suneel Marthi]

If it helps, here's what was done on OpenNLP - one of the first projects
that transitioned to gitbox in July 2017 after gitbox was announced.

http://opennlp.apache.org/using-git.html



On Sun, Dec 3, 2017 at 10:11 AM, Thomas Nadeau 
wrote:

> That still uses SSH, which then uses your pre-configured keys.  Github docs
> discourage this use for some reason.
>
> --Tom
>
> On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament 
> wrote:
>
> > Any reason you wouldn't just use the github direct URLs?
> >
> > g...@github.com:apache/incubator-ariatosca.git
> > g...@github.com:apache/incubator-ariatosca-website.git
> >
> >
> >
> > On Sun, Dec 3, 2017 at 4:45 AM Thomas Nadeau 
> > wrote:
> >
> > > The gitbox transition appears to have completed - thanks for setting
> this
> > > up Suneel.
> > >
> > > Committers please follow the instructions Suneel provided on Slack
> > earlier
> > > to synch your apache account with github so permissions work/etc...
> > >
> > > --Tom
> > >
> > >
> > > From slack:
> > >
> > > https://gitbox.apache.org/repos/asf?p=incubator-
> ariatosca.git;a=summary
> > >
> > > https://gitbox.apache.org/repos/asf?p=incubator-
> ariatosca-website.git;a=
> > summary
> > >
> > > Moved to both repos Gitbox.  You'll need to have your committers link
> > their
> > > Github IDs on id.apache.org and enable two factor authentication here:
> > > https://gitbox.apache.org/setup/  This process can take up to 2 hours
> > for
> > > Gitbox to see.
> > >
> >
>

Re: retiring/removal of committers

[Suneel Marthi]

Fyi... committership never expires in ASF, unless the committer chooses to
go Emeritus. So not sure if this discussion is needed.

On Wed, Nov 29, 2017 at 3:23 PM, Thomas Nadeau 
wrote:

>
> One action I took from the last grooming meeting was to
> investigate with the community, what process and policies we want to use
> around the retirement and/or removal of Committers on the project. As our
> mentors have told us before, the community here is empowered to decide the
> criteria for how people are voted as committers, and the implication is
> that the reverse is true too. However, after discussing this on our call
> this week, it doesn’t seem there is any criteria defined; therefore, I
> wanted to open up the discussion on this.
>
> To start, The Apache PMC guide says this about removal of
> Committers/PMC members:
>
> [http://www.apache.org/dev/pmc.html#pmc-removal <
> http://www.apache.org/dev/pmc.html#pmc-removal>]
>
> Projects can establish their own policy on handling inactive members, as
> long as it is applied consistently.
>
> It is not a problem to retain members of the PMC who have become inactive,
> and it can make it easier for them to stay in touch with the project if
> they choose to become active again.
>
> Typically, PMC members who are no longer able to participate will resign
> from the PMC. However, if a PMC chooses to remove one of its members (i.e.
> without that member's consent), then it must request the Board to make that
> decision (which is typically done with a resolution at the Board's next
> meeting). The PMC chair should send and email to the board@ mailing list
> detailing the request for removal and the justification the PMC has for
> that removal, and cc: the project's private@ list.
>
>
> So with that in mind, it looks like we need to augment the
> guidelines Tal started on the wiki [https://cwiki.apache.org/
> confluence/display/ARIATOSCA/Becoming+a+Committer <
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Becoming+a+Committer>]
> to include removal/retirement/inactive PMC/committers.
> To get the ball rolling, I wanted to make some suggestions for
> (de)selection criteria that I’ve used in other OSS projects:
>
> Open Daylight uses this process:
>
> https://wiki.opendaylight.org/view/TSC:Main#Committer_Removal_Process <
> https://wiki.opendaylight.org/view/TSC:Main#Committer_Removal_Process>
>
> OPNFV uses this:
>
> https://wiki.opnfv.org/display/DEV/Committer+Removal <
> https://wiki.opnfv.org/display/DEV/Committer+Removal>
>
> Basically the process everyone basically uses allows a current
> committer to elect to step down and there is a simple, straight-forward
> process for this.
> In other cases its a little more than the obvious: if someone isn’t
> contributing to the project for an obviously prolonged time and hasn’t
> verified they’re on a leave of absence or something, then they are simply
> notified with some notice to respond after which they are removed.   All of
> the examples also have solutions to more dire situations, but I’ve
> literally never seen that happen in any project I’ve worked on in like 6
> years.
>
> I’d like to propose a simple copy/paste of the OPNFV rules which
> seem to cover what is needed except for obviously changing the mailing
> list/TSC contacts.  We need to change “TSC” to “AriaTosca PPMC”.  There are
> things to clean up in there too like references to IRC - Apache requires
> everything to be on the dev mailer officially.
>
> —Tom
>
>
>
>
>

Re: Official Project Vote: Moving to Gitbox

[Suneel Marthi]

Have we kept this vote open for 3 days ?

On Fri, Nov 10, 2017 at 2:28 AM, Thomas Nadeau 
wrote:

>
> The official voting tally is:
>
> Active committers:
>
> Suneel: +1
> Tal: +1
> Avia: +1
> Maxim: +1
>
> Active Contributors:
>
> Tom: +1
> Vish: +1
>
>
> I am calling that we’ve met the threshold to make this change.
> John or Suneel, I think the next step here is for one of you guys
> to request to Apache Ops to make the switch.
>
> —Tom
>
>
>

Re: moving to git

[Suneel Marthi]

The title of this thread should read as 'Moving to gitbox' :-)

On Wed, Nov 8, 2017 at 3:34 AM, Thomas Nadeau  wrote:

>
> I just wanted to raise awareness that a discussion of moving our
> repo from one that is hosted at Apache’s git and mirrored on Github, to one
> that is solely hosted on GitHub.  Suneel raised this on the list the other
> day, and we’ve had a little discussion about it with John A just now.  The
> day to day operation of the project will not be affected as far as I can
> tell.  Basically what needs to happen is for me to send in a ticket request
> to the Apache Infra/Tools folks to activate this.
>
> If anyone has any opinions either way, please speak up ASAP.  I’ll
> plan to send the note out at COB Thursday if I don’t hear anything negative.
>
> Cheers,
>
> —Tom
>
>

Re: Slack

[Suneel Marthi]

Need ur email !!!

On Sat, Oct 7, 2017 at 4:05 AM, chbndrhnns  wrote:

> Interested!
>
> 2017-10-06 21:51 GMT+02:00 Tal Liron :
>
> > Hi, devs!
> >
> > As you have probably surmised from reading the digests sent to this list,
> > there is a Slack channel where ARIA devs can chat. I thought it was for
> > committers only, but in fact any contributor can join and talk to others
> in
> > a more real-time fashion.
> >
> > It's critical to understand that Slack is *not* a replacement for email.
> > Slack is *not* a place for support questions: all those should to the dev
> > mailing list, like they do now. Slack is for *coordination* of
> development
> > activities that are already in progress.
> >
> > ASF is email-centric by design. This ensures an even playing field for
> > contributors from all time zones and with all variations of Internet
> > accessibility. We should never use Slack to exclude anyone.
> >
> > With that in mind, if you think it would be useful for you, please
> respond
> > to this email with a request to be invited to Slack. We will use the same
> > email you use here to invite you.
> >
>

Re: Working towards Release 1

[Suneel Marthi]

Everything's gonna happen on list @John - spoke with Tal and Thomas
already.

On Fri, Oct 6, 2017 at 7:34 PM, John D. Ament  wrote:

> What's weekly grooming? Does it happen on list? If I don't work at
> Cloudify, how do I participate in weekly grooming?
>
> John
>
> On Thu, Oct 5, 2017 at 12:09 PM Thomas Nadeau 
> wrote:
>
> >
> > Agreed. We can update the Jira on the weekly grooming.
> >
> > —Tom
> >
> >
> > > On Oct 5, 2017, at 11:24 AM, Tal Liron  wrote:
> > >
> > > I think we can discuss the epic in general here, and leave
> implementation
> > > details on JIRA.
> > >
> > > On Thu, Oct 5, 2017 at 9:52 AM, Vishwanath Jayaraman <
> > > vishwana...@hotmail.com> wrote:
> > >
> > >> Tal/Tom,
> > >>
> > >> Very glad to see an epic and its associated stories/tasks for Release
> > 1.0.
> > >>
> > >> I am assuming you are expecting the comments(if any) in the JIRA
> itself,
> > >> right?
> > >>
> > >> Vish
> > >>
> > >>
> > >> 
> > >> From: Thomas Nadeau 
> > >> Sent: Wednesday, October 4, 2017 3:38 PM
> > >> To: dev@ariatosca.incubator.apache.org
> > >> Subject: Working towards Release 1
> > >>
> > >>
> > >>Tal and I sat down yesterday and started with a new epic (
> > >> https://issues.apache.org/jira/browse/ARIA-386)
> > >> in order to begin to capture what we think as a project, is needed to
> > get
> > >> Aria to a stable release 1.0.  I like to do
> > >> releases in “themes” so for this one it is simple: TOSCA 1.0
> > “compliance”
> > >> as we see it.  There are related issues to
> > >> releasing things, but this is a start. Please take a look and comment
> > here.
> > >>
> > >>—Tom
> > >>
> > >>
> >
> >
>

Re: Slack

[Suneel Marthi]

...and i can add interested folks to the slack channel - just need your
preferred email.

On Fri, Oct 6, 2017 at 3:51 PM, Tal Liron  wrote:

> Hi, devs!
>
> As you have probably surmised from reading the digests sent to this list,
> there is a Slack channel where ARIA devs can chat. I thought it was for
> committers only, but in fact any contributor can join and talk to others in
> a more real-time fashion.
>
> It's critical to understand that Slack is *not* a replacement for email.
> Slack is *not* a place for support questions: all those should to the dev
> mailing list, like they do now. Slack is for *coordination* of development
> activities that are already in progress.
>
> ASF is email-centric by design. This ensures an even playing field for
> contributors from all time zones and with all variations of Internet
> accessibility. We should never use Slack to exclude anyone.
>
> With that in mind, if you think it would be useful for you, please respond
> to this email with a request to be invited to Slack. We will use the same
> email you use here to invite you.
>

Re: [VOTE] publish ariatosca 0.1.1

[Suneel Marthi]

+1 binding

1. Checked Sigs and Hashes
2. Verified RAT check


On Mon, Jul 10, 2017 at 1:04 PM, Ran Ziv  wrote:

> This is a vote to release Apache AriaTosca (Incubating) 0.1.1.
> If the vote passes, another vote for approving the release will take place
> on the Apache Incubator's PMC.
>
>
> I created a tarball candidate for the 0.1.1 release and placed it in ARIA's
> /dist/dev folder:
> *https://dist.apache.org/repos/dist/dev/incubator/
> ariatosca/0.1.1-incubating/
>  ariatosca/0.1.1-incubating/>*
>
> The directory contains three packages:
> source - The canonical Apache release - a snapshot of the repository.
> sdist - The pythonic source distribution - contains generated docs,
> examples, and files needed for install from source (yet doesn't contain
> tests etc.).
> bdist - The pythonic binary distribution - contains compiled code.
>
>
> The sdist and bdist packages have been uploaded to test-PyPI:
> https://test.pypi.org/project/apache-ariatosca/0.1.1/
>
>
> The list of issues Resolved for this release can be found in the CHANGELOG
> or here:
>  1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)>
> https://issues.apache.org/jira/browse/ARIA-312?filter=-
> 1=project%3Dariatosca%20and%20status%20in%20(
> resolved%2C%20closed)%20and%20fixVersion%3D0.1.1
>
>
> Instructions for installation etc. may be found in the README file inside
> the tarball.
> (Please note that the relevant installation instructions are for "source
> installation", not "install from PyPI")
>
>
> To use RAT to validate package conformance with ASF standards, please use
> the ".rat-excludes" file, for example:
> java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
>
>
>
> The vote will last 72 hours.
>
> Please vote:
>
> [ ] +1: Good to go!
> [ ] 0: I don't care
> [ ] -1: Don't release this because...
>
>
> Thanks,
> Ran
>

Re: Installation issue in 0.1.0 release

[Suneel Marthi]

...and that's something i follow even on the TLPs I am involved with - more
frequent releases

On Mon, Jul 10, 2017 at 8:54 AM, John D. Ament 
wrote:

> IMHO, podlings should try to cut releases frequently.  Gets in the habit of
> how to do it.  So if you or someone else has the cycles to cut the release
> I say do it.
>
> I personally don't care what version it is, its just a number.
>
> John
>
> On Mon, Jul 10, 2017 at 8:13 AM Ran Ziv  wrote:
>
> > I've found the following issue with the 0.1.0 release:
> > https://issues.apache.org/jira/browse/ARIA-304
> >
> > A fix for this has already been merged into master; PR can be seen here:
> > https://github.com/apache/incubator-ariatosca/pull/178
> >
> >
> >
> > I'm proposing the possibility of creating a quick 0.1.1 release for
> fixing
> > this bug.
> > On one hand it's not necessarily in the main path (requires optional
> > dependency installation, not relevant for Windows) and has a simple
> > workaround (see comment on the JIRA issue); On the other hand, it's a
> > pretty annoying bug that could deter users from using the 0.1.0, and the
> > fix is simple.
> >
> >
> > If we're to release a 0.1.1 package, there are a few other bug fixes that
> > have been merged since the original 0.1.0 proposal, that we could have
> as a
> > part of this release as well:
> > https://issues.apache.org/jira/browse/ARIA-296
> > https://issues.apache.org/jira/browse/ARIA-202
> > https://issues.apache.org/jira/browse/ARIA-298
> > https://issues.apache.org/jira/browse/ARIA-287
> >
> >
> > What do you think?
> >
> > Ran
> >
>

Re: Congrats on the First Release!

[Suneel Marthi]

Same here, congrats Team on first release.

On Sun, Jul 9, 2017 at 5:20 PM, John D. Ament  wrote:

> All,
>
> I wanted to express my well wishes to you all on a successful first
> release.  Most podlings see this as a milestone, I'll be updating the
> various tracking sheets shortly with this note.
>
> So what's next?  Once the mechanics of a release are squared away, projects
> figure out ways to grow the community.  Here's a short list of things I'd
> recommend:
>
> - Make sure the release process is documented and that the next release has
> a different release manager.
> - Start putting together developer centric documentation.  This may include
> some high level architecture, written designs.
> - Put together a contributor's guide.  This may explain how the project
> works (via github pull requests), creating JIRA tickets, browsing fisheye,
> testing locally.
> - Make all of this easily discoverable.  We have a lot of these documents,
> but they may be hard to find.
> - Make sure we have a downloads page that points to the source release (ASF
> requirement).
>
> John
>

Re: [VOTE] publish ariatosca 0.1.0 (#2)

[Suneel Marthi]

+1 binding

1. Verified {sdist, bdist, source} * {sha, md5} hashes and sigs
2. Built project from {source} with "pip install"
3. Ran tests
4. Verified -incubating in artifacts names.


On Mon, Jul 3, 2017 at 7:13 AM, John D. Ament  wrote:

> On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv  wrote:
>
> > Okay. I didn't have anything to go by since as far as I can tell, other
> > projects don't put their PyPI package candidates on /dist/dev, but to my
> > understanding, in the previous voting thread you've requested to have it
> on
> > there as well.
> >
>
> Nope, the only package I care about is source.  Having the others is an ace
> in the hole though, since it's covering the source, binary and sdist
> releases needed by pypi (FWIW, there was an effort to spin up an internal
> pypi service but it's stalled).  When we verify, we can verify the full
> package.  Now I know more about pypi dist's to be able to push back when
> other projects publish bad releases.
>
> Here's my +1 to release as is.
>
> I would recommend adding the instructions to the readme at some point, this
> block:
>
> Instructions for installation etc. may be found in the README file inside
> the tarball.
> (Please note that the relevant installation instructions are for "source
> installation", not "install from PyPI")
>
>
> To use RAT to validate package conformance with ASF standards, please use
> the ".rat-excludes" file, for example:
> java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
>
>
> In any case, I modified the layout as you'd requested.
> >
> > Regarding md5 and sha files, note that on PyPI only pgp signatures may be
> > used. I added them regardless.
> >
> >
> > Thanks,
> > Ran
> >
> >
> > On Sun, Jul 2, 2017 at 4:01 PM, John D. Ament 
> > wrote:
> >
> > > Ran,
> > >
> > > I would recommend a different directory layout, to make it clear that
> > these
> > > are three different artifacts for the same release.  Most projects
> > create a
> > > version number below their project name, or just dump all of the files
> in
> > > the root (makes it easier to remember to clean up afterwards).
> > >
> > > Starting from
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > 0.1.0-incubating/
> > > create
> > > "source", "sdist" and "bdist" directories.
> > >
> > > Put the current contents of this URL in "source" and move the other two
> > to
> > > the respective locations.  When sending out the vote, you only need to
> > > include the root URL.  Or you can just dump everything directly into
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ .
> > >
> > > For the contents in sdist and bdist, please include the md5 and sha
> > files.
> > >
> > > John
> > >
> > > On Sun, Jul 2, 2017 at 8:40 AM Ran Ziv  wrote:
> > >
> > > > This is a vote to release Apache AriaTosca (Incubating) 0.1.0.
> > > > If the vote passes, another vote for approving the release will take
> > > place
> > > > on the Apache Incubator's PMC.
> > > >
> > > >
> > > > I created a tarball candidate for the 0.1.0 release and placed it in
> > > ARIA's
> > > > /dist/dev folder:
> > > > *
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > 0.1.0-incubating/
> > > > <
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > 0.1.0-incubating/
> > > > >*
> > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> > in
> > > > that folder as well.
> > > >
> > > >
> > > > In addition, I've created packages for (Pythonic-)source & binary
> > > > distributions, which would be uploaded to PyPI if the release is
> > > approved.
> > > > These artifacts may be found here:
> > > > Source distribution:
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-sdist/
> > > > Binary distribution:
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-bdist/
> > > >
> > > >
> > > >
> > > > The list of issues Resolved for this release are simply all the
> issues
> > > that
> > > > have been resolved thus far, seeing as this would be the first
> release
> > :)
> > > > Those can be found here:
> > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-1;
> > > > jql=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> > > >
> > > >
> > > > Instructions for installation etc. may be found in the README file
> > inside
> > > > the tarball.
> > > > (Please note that the relevant installation instructions are for
> > "source
> > > > installation", not "install from PyPI")
> > > >
> > > >
> > > > To use RAT to validate package conformance with ASF standards, please
> > use
> > > > the ".rat-excludes" file, for example:
> > > > java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
> > > >
> > > >
> > > >
> > > > The vote will last 72 hours.
> > > >
> > > > Please vote:
> > > >
> > > > [ ] +1: Good to go!
> > > > [ ] 0: I don't care
> > > > [ ] -1: 

Re: [VOTE] publish ariatosca 0.1.0

[Suneel Marthi]

You can go with this - this is more recent and i have been enforcing this
on podlings I mentor as well as TLPs I am involved with

https://lists.apache.org/thread.html/f27488e6a5d2355651b0aeb9dd6d82891e20d802ee3c58a0cc4a6533@%3Cdev.streams.apache.org%3E



On Thu, Jun 29, 2017 at 12:00 PM, John D. Ament 
wrote:

> On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:
>
> > Suneel, re mentioning 72 hours - note that I simply used the recommended
> > template for these messages from here:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-
> dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3E
> >
> >
> I'll note this is an email from 10 years ago, and things have been refined
> since then.  I plan to rewrite that guide to give better examples.  Here's
> a more up to date example
>
> https://lists.apache.org/thread.html/9fd77b14753bbde462bea06fc2e1c0
> 3d5cf5a89cea2fabd6751d805a@%3Cdev.ponymail.apache.org%3E
>
>
>
> >
> >
> > John:
> > Are you reading this off the README? If so, you'll notice that the
> > installation section mentions that when installing ARIA from source, the
> > command that should be executed is actually "pip install ." when you're
> > inside the extracted dir.
> >
> > Regarding your other comments:
> >  - DISCLAIMER file - apparently it was dropped from the manifest file
> > somehow, i'll add it back.
> >  - Is RAT to be used for Python projects as well? I thought it was
> > Java-specific and I'm not familiar with similar tools for Python. We've
> > done what we can to verify every code file has the license header.
> >
>
> RAT is a tool written in java that checks headers in all languages.  We
> should have instructions on how to run it here.
>
>
> >  - This is indeed the source release - There are indeed deltas between
> this
> > and the repo files but that's because some files are unnecessary for
> users
> > (e.g. docs generating files) while some aren't needed in the repo (e.g.
> > docs generated files).
> >
> >
> The source release is what's in your repo.  Source releases are for
> everyone to consume.
>
>
> >
> >
> > Ran
> >
> >
> > On Thu, Jun 29, 2017 at 6:43 PM, John D. Ament 
> > wrote:
> >
> > > -1.  Found the following issues:
> > >
> > > - BUILD instructions are INSTALL instructions, and the installation
> > doesn't
> > > work
> > >
> > > pip install apache-ariatosca
> > >
> > >
> > > Collecting apache-ariatosca
> > >   Could not find a version that satisfies the requirement
> > apache-ariatosca
> > > (from versions: )
> > > No matching distribution found for apache-ariatosca
> > >
> > > - There is no DISCLAIMER file
> > > - No instructions on how to run RAT
> > > - I'm not sure this is a source release, many files don't match whats
> in
> > > the repo (files added/missing?)
> > >
> > > Other things look fine:
> > > - contains incubating
> > > - files contain headers
> > >
> > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
> > >
> > > > I created a tarball candidate for the 0.1.0 release and placed it in
> > > ARIA's
> > > > /dist/dev folder:
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> > in
> > > > that folder as well.
> > > >
> > > >
> > > > The list of issues Resolved for this release are simply all the
> issues
> > > that
> > > > have been resolved thus far, seeing as this would be the first
> release
> > :)
> > > > Those can be found here:
> > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > > > 1=project%3Dariatosca%20and%20status%20in%20(
> resolved%2C%20closed)
> > > >
> > > >
> > > > Instructions for installation etc. may be found in the README file
> > inside
> > > > the tarball.
> > > >
> > > >
> > > > Please vote to publish this tarball on ARIA's /dist/release folder.
> > > >
> > > >
> > > > Ran
> > > >
> > >
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[Suneel Marthi]

... and also please mention that the vote will be 'Open' for 72 hrs - which
means July 2, Sunday for this release candidate - following which we move
to IPMC votes (another 72 hrs) --- and then the release happens if all goes
well.

On Thu, Jun 29, 2017 at 11:37 AM, John D. Ament 
wrote:

> Ran,
>
> Just to be clear, per incubator voting policies this is the dev vote.
> There's a second vote that happens on general@incubator before actually
> moving it to /dist/release
>
> John
>
> On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
>
> > I created a tarball candidate for the 0.1.0 release and placed it in
> ARIA's
> > /dist/dev folder:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> > that folder as well.
> >
> >
> > The list of issues Resolved for this release are simply all the issues
> that
> > have been resolved thus far, seeing as this would be the first release :)
> > Those can be found here:
> > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> >
> >
> > Instructions for installation etc. may be found in the README file inside
> > the tarball.
> >
> >
> > Please vote to publish this tarball on ARIA's /dist/release folder.
> >
> >
> > Ran
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[Suneel Marthi]

That's correct - u get to move the artifacts to /release only after the
iPMC okays the release artifacts.

On Thu, Jun 29, 2017 at 11:37 AM, John D. Ament 
wrote:

> Ran,
>
> Just to be clear, per incubator voting policies this is the dev vote.
> There's a second vote that happens on general@incubator before actually
> moving it to /dist/release
>
> John
>
> On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
>
> > I created a tarball candidate for the 0.1.0 release and placed it in
> ARIA's
> > /dist/dev folder:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> > that folder as well.
> >
> >
> > The list of issues Resolved for this release are simply all the issues
> that
> > have been resolved thus far, seeing as this would be the first release :)
> > Those can be found here:
> > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> >
> >
> > Instructions for installation etc. may be found in the README file inside
> > the tarball.
> >
> >
> > Please vote to publish this tarball on ARIA's /dist/release folder.
> >
> >
> > Ran
> >
>

Re: Moving to 100% GitHub

[Suneel Marthi]

I think what John means is that  - migrate http://ariatosca.org to
http://ariatosca.incubator.apache.org



On Sun, May 21, 2017 at 4:15 PM, Tal Liron  wrote:

> We have both a website and a contribution guide. How should we improve
> them?
>
> http://ariatosca.org/
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Contributing+to+ARIA
>
> On Sun, May 21, 2017 at 2:38 PM, John D. Ament 
> wrote:
>
> > On Sun, May 21, 2017 at 7:51 AM Ran Ziv  wrote:
> >
> > > I don't think moving the project to Github and the issue of lack of
> > > discussions on the mailing list are related - we need to solve the
> latter
> > > regardless of the former.
> > >
> > >
> > I disagree Ran.  Aria Tosca has no website, has no documented model for
> how
> > to collaborate.  Yet for some reason developers raise pull requests.  How
> > did that come to be the case?
> >
> >
> > > Tal, I'm not sure how exactly it would increase visibility - The mirror
> > is
> > > as visible as the new repository would be..?
> > > It could however make things somewhat more convenient to us, although
> > that
> > > too depends on who's managing the repo - I'm not familiar with this
> > > 100%-hosted-on-github concept yet.
> > >
> > > Tal, care to share some more links / info about this?
> > >
> > >
> > >
> > >
> > > On Thu, May 18, 2017 at 8:56 PM, John D. Ament 
> > > wrote:
> > >
> > > > One con I see is that the project already struggles with on list
> > > > discussions.  We want to open up github usage, but want to make sure
> > that
> > > > projects are communicating well, so that the source code being
> > maintained
> > > > on github is more of a convenience.  Until I see more action from
> > > AriaTosca
> > > > on this list I would be hesitant to say yes for the project.
> > > >
> > > > John
> > > >
> > > > On Thu, May 18, 2017 at 1:51 PM Tal Liron 
> wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > ASF now has an option of moving the repository to be 100% hosted on
> > > > GitHub,
> > > > > so it won't be a mirror of the ASF repo. I think this could
> increase
> > > our
> > > > > visibility and make the project seem more welcoming to outside
> > > > > contributions. Also would make management a bit easier for us.
> > > > >
> > > > > What do you think? Pros and cons?
> > > > >
> > > > >
> > > > > --
> > > > > Tal Liron
> > > > > Solution Architect
> > > > > t...@gigaspaces.com | +13123758299 <(312)%20375-8299>
> > > <(312)%20375-8299>
> > > > > Cloudify | http://getcloudify.org
> > > > > <
> > > > > http://getcloudify.org?utm_source=signaturesatori_
> > > > medium=email_campaign=general_signature
> > > > > >
> > > > >
> > > > > 
> > > > > 
> > > > >    <
> > > https://github.com/cloudify-cosmo
> > > > >
> > > > > [image: Azure Webinar]
> > > > > <
> > > > > http://getcloudify.org/webinars/Azure-plugin-for-
> > > > cloudify-webinar.html?utm_source=signaturesatori_
> > > > medium=email_campaign=general_signature
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Tal Liron
> Senior Engineer
> t...@gigaspaces.com | +1 (773) 828-9339
> Cloudify | http://getcloudify.org
>  medium=email_campaign=general_signature>
>
> 
> 
>    
> [image: Azure Webinar]
>  cloudify-webinar.html?utm_source=signaturesatori_
> medium=email_campaign=general_signature>
>

Re: Renaming Old ARIA Repos

[Suneel Marthi]

+1 Arthur

On Sun, May 21, 2017 at 11:36 AM, Arthur Berezin 
wrote:

> I think it would be nice to redirect the traffic to the right place,
> instead of creating broken links, and also to keep the old content for
> reference.
>
>
> On Sun, May 21, 2017 at 6:14 PM John D. Ament 
> wrote:
>
> > Is there a real reason for the old repos to continue to exist? What would
> > be the problem if they were just deleted?
> >
> > John
> >
> > On Sun, May 21, 2017 at 9:28 AM Arthur Berezin 
> > wrote:
> >
> > > Hi All,
> > >
> > >
> > > It seems that the old ARIA organization on GitHub from before we moved
> to
> > > ASF(https://github.com/aria-tosca-old) are still creating confusion.
> > > I added text "-old" to repo name and changed the description of all
> > > repos to point to the new ASF repo.
> > >
> > > Do you think we should also move all the content to separate branches
> and
> > > keep only the readme.md in master that would point to the new repo?
> > >
> > > I prefere not deleting this org altoghether to it keep for refenrece.
> > >
> > > Arthur
> > >
> >
>

Re: [CONF] Ariatosca > Podling Report 2017-03

[Suneel Marthi]

Thanks John, will fix that.

On Sun, Mar 5, 2017 at 9:09 AM, John D. Ament <john.d.am...@gmail.com>
wrote:

> Suneel,
>
> This area is a 1 X, not a multi-select.  We typically see that community
> building begins after the first release - you have software that users can
> leverage, questions come through.  IMHO, this is not in community building.
>
> John
>
> On Sun, Mar 5, 2017 at 9:01 AM Suneel Marthi (Confluence) <
> conflue...@apache.org> wrote:
>
>> [image: avatar_e1ac74408df1fba1b108a97c76b1836f.png]
>> <https://cwiki.apache.org/confluence/display/~smarthi?src=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0>
>>  Suneel
>> Marthi *edited* a page
>>
>> [image: page-icon.png]
>> <https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-03?src=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=view>
>>  Podling
>> Report 2017-03
>> <https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-03?src=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=view>
>>
>> ...
>>
>> [ ] Initial setup
>> [X] Working towards first release
>> [X] Community building
>> [ ] Nearing graduation
>> [ ] Other:
>>
>> ...
>> [image:
>> com.atlassian.confluence.plugins.confluence-email-resources:view-page-email-adg-footer-item:icon.png]
>> <https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-03?src=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=view>
>>  View
>> page
>> <https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-03?src=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=view>
>> •
>> [image:
>> com.atlassian.confluence.plugins.confluence-email-resources:add-comment-to-content-email-adg-footer-item:icon.png]
>> <https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-03?showComments=true=true=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=comment#addcomment>
>>  Add
>> comment
>> <https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-03?showComments=true=true=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=comment#addcomment>
>> •
>> [image:
>> com.atlassian.confluence.plugins.confluence-like:view-email-adg-content-item:icon.png]
>> <https://cwiki.apache.org/confluence/plugins/likes/like.action?contentId=68717022=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=like>
>> Like
>> <https://cwiki.apache.org/confluence/plugins/likes/like.action?contentId=68717022=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=like>
>>
>> Stop watching page
>> <https://cwiki.apache.org/confluence/users/removepagenotification.action?pageId=68717022=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=stop-watching>
>> •
>> Manage notifications
>> <https://cwiki.apache.org/confluence/users/editmyemailsettings.action?src=mail=1488722486198=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification=8aa980874e36a1eb014e36a29f562cf0=manage>
>> [image: footer-desktop-logo.png]
>> This message was sent by Atlassian Confluence 5.8.4
>> [image: footer-mobile-logo.png]
>>
>

Re: Board Report March 2017

[Suneel Marthi]

I believe most of the folks could be at 'Mobile World Congress' at
Barcelona this week, hence the silence.
Could we wait till the weekend for the report to be filed?

On Thu, Mar 2, 2017 at 7:46 AM, John D. Ament <johndam...@apache.org> wrote:

> Is anyone available to fill this out?
>
> On Tue, Feb 28, 2017 at 5:22 PM Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
>
> > @Ran @Arthur
> >
> > Created a template here
> >
> >
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> Podling+Report+2017-03
> >
> >
> > Report's due for posting on March 1.
> >
>

Board Report March 2017

[Suneel Marthi]

@Ran @Arthur

Created a template here

https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-03


Report's due for posting on March 1.

[jira] [Commented] (ARIA-88) Add blueprint examples

[Suneel Marthi (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873758#comment-15873758
 ] 

Suneel Marthi commented on ARIA-88:
---

This is in blatant violation of the Royal decree - it says 'Blueprints'. Thou 
shall be condemned to the gallows.

> Add blueprint examples
> --
>
> Key: ARIA-88
> URL: https://issues.apache.org/jira/browse/ARIA-88
> Project: AriaTosca
>  Issue Type: Story
>Reporter: Ran Ziv
>Assignee: Tal Liron
>Priority: Minor
> Fix For: 0.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Plan for first AriaTosca release ?

[Suneel Marthi]

cool!

On Wed, Jan 25, 2017 at 5:36 AM, Ran Ziv <r...@gigaspaces.com> wrote:

> I don't think we're there quite yet, but we're getting closer.
> We're making many changes to the data model at the moment, so it's probably
> a good idea to wait until those are complete and we can fully run TOSCA
> workflows before we make the first release.
>
>
> On Tue, Jan 24, 2017 at 5:00 PM, Suneel Marthi <smar...@apache.org> wrote:
>
> > Are we ready for a first Apache release for this project yet? I do see
> > sustained activity over the past few months.
> >
> > Suneel
> >
>

Plan for first AriaTosca release ?

[Suneel Marthi]

Are we ready for a first Apache release for this project yet? I do see
sustained activity over the past few months.

Suneel

Re: [DISCUSS] Rename ARIATOSCA to ARIA

[Suneel Marthi]

When reviewing the incubator proposal for this I recall someone from IPMC
mention a project from Mozilla called 'Aria' and this project choosing a
different name. Arthur had then suggested 'AriaTosca' and we went ahead
with that name when setting up this podling.

On Wed, Dec 7, 2016 at 8:56 PM, John D. Ament  wrote:

> All,
>
> I'm following up on this item.  There were previous discussion points about
> renaming the JIRA instance from ARIATOSCA to ARIA.  I've point out to the
> project in the past that the rename is meant to be a thorough process - all
> podling resources should be named consistently.
>
> If its decided to rename fro ARIATOSCA to ARIA, the following changes would
> be involved:
>
> - New JIRA project ARIA created.  No data retained.
> - Git repos renamed from incubator-ariatosca to incubator-aria
> - Maling lists renamed from @ariatosca.incubator.apache.org to @
> aria.incubator.apache.org
>
> I'm sure there are other resources as well.  The point is that within the
> ASF, we strive for consistency (the whole convention over configuration
> argument).  You will find two projects (that I can think of) that break
> this mold - and they break it really well.  AMQ and CMDA always require
> special handling.  CMDA is purely too long of a name
> (climatemodeldatanalyzer), and AMQ was simply the first JIRA project.
>
> If the podling chooses to rename itself, I don't have a personal opinion.
> I will point out that the name ARIA is not specially unique and wouldn't be
> something we could get a trademark on.  Its not that easy to defend.
> ARIATOSCA is very unique and can be defended as a trademark.
>
> John
>

Re: Dec 16 Podling Report

[Suneel Marthi]

Updated the Dec 16 draft, see
https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2016-12

If Ok, I'll post the same to Incubator.

Here's my +1

On Sun, Dec 4, 2016 at 9:25 PM, John D. Ament <johndam...@apache.org> wrote:

> +1
> Its important to remember that graduation is not around technical merits
> but all about functional.  There are some basic mechanical things - cutting
> valid releases but the bulk of it is around community.
>
> On Sun, Dec 4, 2016 at 7:39 PM Suneel Marthi <smar...@apache.org> wrote:
>
> > What's most important for the graduation is the growth in community that
> > includes committers and contributions from outside of Gigaspaces, that's
> > something we need to work on as a higher priority.
> >
> >
> >
> > --
> >
> > AriaTosca  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. Model storage mechanisem, and execution plugin.
> >
> > >>> Replace this with 'Grow community and enroll new committers"
> >
> >2. Update ARIA website acording to ASF guideline(Include release
> > process for ARIA-TOSCA Project)
> >
> >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 <https://issues.apache.org/jira/browse/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?
> >
> >
> >- Open-O is in process for consuming the ARIA ASF package
> >- Cloudfiy is in process for consuming the ARIA ASF package as well.
> >
> >   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:
> >   -
> >
> >  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:
> >
> >[ ](ariatosca) Suneel Marthi
> >[ ](ariatosca) John D. Ament
> >[ ](ariatosca) Jakob Homan
> >
> >  Shepherd/Mentor notes:
> >
>

Dec 16 Podling Report

[Suneel Marthi]

What's most important for the graduation is the growth in community that
includes committers and contributions from outside of Gigaspaces, that's
something we need to work on as a higher priority.



--

AriaTosca  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. Model storage mechanisem, and execution plugin.

>>> Replace this with 'Grow community and enroll new committers"

   2. Update ARIA website acording to ASF guideline(Include release
process for ARIA-TOSCA Project)

   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 <https://issues.apache.org/jira/browse/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?


   - Open-O is in process for consuming the ARIA ASF package
   - Cloudfiy is in process for consuming the ARIA ASF package as well.

  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:
  -

 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:

   [ ](ariatosca) Suneel Marthi
   [ ](ariatosca) John D. Ament
   [ ](ariatosca) Jakob Homan

 Shepherd/Mentor notes:

Re: Add me as contributor

[Suneel Marthi]

If u r in the initial list of committers, u should have access already

Sent from my iPhone

> On Nov 16, 2016, at 11:31 PM, Tal Liron  wrote:
> 
> Could someone please give me write access to the git repo? My Apache
> username is "emblemparade".

Re: Podling Report Reminder - November 2016

[Suneel Marthi]

R u folks migrating existing users to sign up for Apache mailing lists and 
filing issues on Project Jira?

I don't see that addressed in the report.

Sent from my iPhone

> On Nov 4, 2016, at 8:59 AM, Arthur Berezin <art...@gigaspaces.com> wrote:
> 
> Okay, Podling page is up-to-date now.
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2016-11 
> 
> 
> On Fri, Nov 4, 2016 at 2:28 AM John D. Ament <johndam...@apache.org> wrote:
> Arthur,
> 
> Your account is fixed now.  But please - report is past due at this point.
> 
> John
> 
> On Thu, Nov 3, 2016 at 12:08 PM Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
> 
> > @Arthur,
> >
> > Please go ahead and post the report here on dev@, me or John can then post
> > that to incubator wiki.
> >
> > On Thu, Nov 3, 2016 at 12:06 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > I still see no account for you.
> > >
> > > On Thu, Nov 3, 2016 at 11:52 AM Arthur Berezin <art...@gigaspaces.com>
> > > wrote:
> > >
> > > > Okay, now I can access it but not edit, I might have hit some weird
> > > > Confluence cookies bug, where It showed me as signed in under
> > > > ariatosca instance, but I didn't really have an acount...
> > > >
> > > > Anyway, now I've created an account with username "arthur", how do I
> > gain
> > > > edit rights for the podling page
> > > >
> > > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > > Podling+Report+2016-11
> > > > ?
> > > >
> > > >
> > > > On Thu, Nov 3, 2016 at 4:55 PM John D. Ament <johndam...@apache.org>
> > > > wrote:
> > > >
> > > > > Public access is there, try again.
> > > > >
> > > > > I don't see a confluence user named "arthurberezin" please make sure
> > > you
> > > > > registered (its a separate account)
> > > > >
> > > > > On Thu, Nov 3, 2016 at 10:53 AM John D. Ament <johndam...@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > > Give me a few mins, I'll fix confluence permissions.
> > > > >
> > > > > John
> > > > >
> > > > > On Thu, Nov 3, 2016 at 10:52 AM Arthur Berezin <
> > art...@gigaspaces.com>
> > > > > wrote:
> > > > >
> > > > > My user ID as Email:Arthur at gigaspaces dot com
> > > > > Username:
> > > > > arthurberezin
> > > > >
> > > > >
> > > > > On Thu, Nov 3, 2016 at 4:49 PM Arthur Berezin <art...@gigaspaces.com
> > >
> > > > > wrote:
> > > > >
> > > > > John, I'm not able to access to the template you created, Do I have
> > > > > permissions for it?
> > > > >
> > > > >
> > > > > On Thu, Nov 3, 2016 at 2:43 PM Suneel Marthi <smar...@apache.org>
> > > wrote:
> > > > >
> > > > > @Arthur
> > > > >
> > > > > We are late on the podling report, could u please get it in ASAP. If
> > u
> > > > can
> > > > > post the report here on dev@. I can file it on incubator wiki.
> > > > >
> > > > > On Wed, Nov 2, 2016 at 6:13 PM, John D. Ament <johndam...@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > > > Please note - the board report is due tonight.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > On Wed, Nov 2, 2016 at 1:42 PM Arthur Berezin <
> > art...@gigaspaces.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks John, I'll update this soon.
> > > > > > >
> > > > > > > On Wed, Nov 2, 2016, 04:30 John D. Ament <johndam...@apache.org>
> > > > > wrote:
> > > > > > >
> > > > > > > > I created a template of the page here:
> > > > > > > >
> > > > > > > >
> > > > > > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > > > > > Podling+Report+2016-11
> > > > > > > >
> > > > > > > > Please fill in as appropriate :-)
> > > >

Re: Podling Report Reminder - November 2016

[Suneel Marthi]

@Arthur,

Please go ahead and post the report here on dev@, me or John can then post
that to incubator wiki.

On Thu, Nov 3, 2016 at 12:06 PM, John D. Ament <johndam...@apache.org>
wrote:

> I still see no account for you.
>
> On Thu, Nov 3, 2016 at 11:52 AM Arthur Berezin <art...@gigaspaces.com>
> wrote:
>
> > Okay, now I can access it but not edit, I might have hit some weird
> > Confluence cookies bug, where It showed me as signed in under
> > ariatosca instance, but I didn't really have an acount...
> >
> > Anyway, now I've created an account with username "arthur", how do I gain
> > edit rights for the podling page
> >
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> Podling+Report+2016-11
> > ?
> >
> >
> > On Thu, Nov 3, 2016 at 4:55 PM John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > Public access is there, try again.
> > >
> > > I don't see a confluence user named "arthurberezin" please make sure
> you
> > > registered (its a separate account)
> > >
> > > On Thu, Nov 3, 2016 at 10:53 AM John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > > Give me a few mins, I'll fix confluence permissions.
> > >
> > > John
> > >
> > > On Thu, Nov 3, 2016 at 10:52 AM Arthur Berezin <art...@gigaspaces.com>
> > > wrote:
> > >
> > > My user ID as Email:Arthur at gigaspaces dot com
> > > Username:
> > > arthurberezin
> > >
> > >
> > > On Thu, Nov 3, 2016 at 4:49 PM Arthur Berezin <art...@gigaspaces.com>
> > > wrote:
> > >
> > > John, I'm not able to access to the template you created, Do I have
> > > permissions for it?
> > >
> > >
> > > On Thu, Nov 3, 2016 at 2:43 PM Suneel Marthi <smar...@apache.org>
> wrote:
> > >
> > > @Arthur
> > >
> > > We are late on the podling report, could u please get it in ASAP. If u
> > can
> > > post the report here on dev@. I can file it on incubator wiki.
> > >
> > > On Wed, Nov 2, 2016 at 6:13 PM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > > > Please note - the board report is due tonight.
> > > >
> > > > John
> > > >
> > > > On Wed, Nov 2, 2016 at 1:42 PM Arthur Berezin <art...@gigaspaces.com
> >
> > > > wrote:
> > > >
> > > > > Thanks John, I'll update this soon.
> > > > >
> > > > > On Wed, Nov 2, 2016, 04:30 John D. Ament <johndam...@apache.org>
> > > wrote:
> > > > >
> > > > > > I created a template of the page here:
> > > > > >
> > > > > >
> > > > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > > > Podling+Report+2016-11
> > > > > >
> > > > > > Please fill in as appropriate :-)
> > > > > >
> > > > > > John
> > > > > >
> > > > > > On Sat, Oct 29, 2016 at 11:48 PM Suneel Marthi <
> > > > suneel.mar...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Nope I did not do it, please go ahead and create it.
> > > > > > >
> > > > > > > Thanx
> > > > > > >
> > > > > > > Sent from my iPhone
> > > > > > >
> > > > > > > > On Oct 29, 2016, at 9:50 PM, Arthur Berezin <
> > > art...@gigaspaces.com
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Suneel, I'll take care of this month's podling report.
> > > > > > > > Have you already created this in confluence?
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, Oct 27, 2016 at 2:52 AM Suneel Marthi <
> > > > > suneel.mar...@gmail.com
> > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Will do.
> > > > > > > >>
> > > > > > > >> On Wed, Oct 26, 2016 at 7:51 PM, John D. Ament <
> > > > > johndam...@apache.org
> > > > > > >
> > > > 

Re: [DISCUSS] Move Aria Tosca to Reporting Group 1

[Suneel Marthi]

+1 for the move.  But we still do file the November report correct? and the
next report would be due Jan 2017.



On Tue, Nov 1, 2016 at 10:36 PM, John D. Ament 
wrote:

> Hey guys
>
> I typically serve as incubator report manager.  Boring job, but someone has
> to do it.  Anyways, there's a slight imbalance between the reporting groups
> (see [1]).  Since we're still early, I wanted to propose moving AriaTosca
> from Reporting Group to Reporting Group 1.  Its a new podling, so it
> shouldn't impact too much right now.
>
> This means your quarterly reports would be January, April, July, October.
> Any concerns?
>
> John
>
> [1]: http://incubator.apache.org/report-groups.txt
>

Re: Questions regarding CI, PR and documentation

[Suneel Marthi]

On Sun, Oct 30, 2016 at 7:00 PM, Ran Ziv <r...@gigaspaces.com> wrote:

> Thanks Suneel.
> Actually I believe it was the wrong Tal, so I removed his permissions.
>
> Unless I'm missing something, everyone needs to register to confluence
> separately from jira / apache-id etc., here
> <https://cwiki.apache.org/confluence/signup.action>.
>

Correct. All need to register separately on Confluence (and its separate
from Jira).

>
> Guys please send your ID once you do that so we could grant you permissions
>
> On Sun, Oct 30, 2016 at 6:07 PM, Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
>
> > Done - added Tal, John D. Jakob. Ran <- all these users have admin
> > privs, please feel free to add others.
> >
> > On Sun, Oct 30, 2016 at 11:56 AM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > Could you add me as well?
> > >
> > > On Sun, Oct 30, 2016 at 11:50 AM Suneel Marthi <
> suneel.mar...@gmail.com>
> > > wrote:
> > >
> > > > Heh Sorry, Ran I added u to confluence - ur ApacheId 'ran' would be
> ur
> > > > login.
> > > >
> > > > You have permissions to add users, please feel free to add others.
> > > >
> > > > On Sun, Oct 30, 2016 at 11:40 AM, Ran Ziv <r...@gigaspaces.com>
> wrote:
> > > >
> > > > > Suneel, could you please provide me (and possibly the rest of us as
> > > well)
> > > > > permissions for creating pages on our Confluence? I don't seem to
> > have
> > > > > these permissions at the moment.
> > > > > Thank you :)
> > > > >
> > > > > On Tue, Oct 25, 2016 at 6:05 PM, Suneel Marthi <smar...@apache.org
> >
> > > > wrote:
> > > > >
> > > > > > On Tue, Oct 25, 2016 at 10:55 AM, Ran Ziv <r...@gigaspaces.com>
> > > wrote:
> > > > > >
> > > > > > > Done.
> > > > > > > I'll update the project's .travis file now.
> > > > > > >
> > > > > > > What is the process of setting up a Jenkins job?
> > > > > > >
> > > > > >
> > > > > > Needs an Infra ticket.
> > > > > >
> > > > > > >
> > > > > > > -
> > > > > > >
> > > > > > > Regarding shared documents, is Confluence the Apache standard?
> > What
> > > > > about
> > > > > > > using github markup files and have the documents as a part of
> the
> > > > repo?
> > > > > > > Does anyone have any specific preference or other ideas on this
> > > > matter?
> > > > > > >
> > > > > >
> > > > > > Its again up to the project. Projects like Flink, Pirk, Beam have
> > > > markup
> > > > > > files in github and use Jekyll.
> > > > > >
> > > > > > They also use Confluence for few other things.
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Oct 25, 2016 at 3:11 PM, Suneel Marthi <
> > smar...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Never heard of CircleCI, and I don't think Infra is gonna
> > support
> > > > > that.
> > > > > > > >
> > > > > > > > Please go ahead and create an Infra ticket to enable Travis
> for
> > > > Aria.
> > > > > > > >
> > > > > > > > On Tue, Oct 25, 2016 at 5:24 AM, Ran Ziv <r...@gigaspaces.com
> >
> > > > wrote:
> > > > > > > >
> > > > > > > > > Regarding CI - Does Apache also support CircleCI? I assume
> > less
> > > > > > > projects
> > > > > > > > > use it and if that's the case it could possibly be a better
> > > > option
> > > > > > for
> > > > > > > us
> > > > > > > > > if the purpose of using an additional CI environment
> (besides
> > > > > > jenkins)
> > > > > > > is
> > > > > > > > > to allow for quick feedback over PRs.
> > > > > > > > > If not I'll create an

Re: Questions regarding CI, PR and documentation

[Suneel Marthi]

Done - added Tal, John D. Jakob. Ran <- all these users have admin
privs, please feel free to add others.

On Sun, Oct 30, 2016 at 11:56 AM, John D. Ament <johndam...@apache.org>
wrote:

> Could you add me as well?
>
> On Sun, Oct 30, 2016 at 11:50 AM Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
>
> > Heh Sorry, Ran I added u to confluence - ur ApacheId 'ran' would be ur
> > login.
> >
> > You have permissions to add users, please feel free to add others.
> >
> > On Sun, Oct 30, 2016 at 11:40 AM, Ran Ziv <r...@gigaspaces.com> wrote:
> >
> > > Suneel, could you please provide me (and possibly the rest of us as
> well)
> > > permissions for creating pages on our Confluence? I don't seem to have
> > > these permissions at the moment.
> > > Thank you :)
> > >
> > > On Tue, Oct 25, 2016 at 6:05 PM, Suneel Marthi <smar...@apache.org>
> > wrote:
> > >
> > > > On Tue, Oct 25, 2016 at 10:55 AM, Ran Ziv <r...@gigaspaces.com>
> wrote:
> > > >
> > > > > Done.
> > > > > I'll update the project's .travis file now.
> > > > >
> > > > > What is the process of setting up a Jenkins job?
> > > > >
> > > >
> > > > Needs an Infra ticket.
> > > >
> > > > >
> > > > > -
> > > > >
> > > > > Regarding shared documents, is Confluence the Apache standard? What
> > > about
> > > > > using github markup files and have the documents as a part of the
> > repo?
> > > > > Does anyone have any specific preference or other ideas on this
> > matter?
> > > > >
> > > >
> > > > Its again up to the project. Projects like Flink, Pirk, Beam have
> > markup
> > > > files in github and use Jekyll.
> > > >
> > > > They also use Confluence for few other things.
> > > >
> > > >
> > > > >
> > > > >
> > > > > On Tue, Oct 25, 2016 at 3:11 PM, Suneel Marthi <smar...@apache.org
> >
> > > > wrote:
> > > > >
> > > > > > Never heard of CircleCI, and I don't think Infra is gonna support
> > > that.
> > > > > >
> > > > > > Please go ahead and create an Infra ticket to enable Travis for
> > Aria.
> > > > > >
> > > > > > On Tue, Oct 25, 2016 at 5:24 AM, Ran Ziv <r...@gigaspaces.com>
> > wrote:
> > > > > >
> > > > > > > Regarding CI - Does Apache also support CircleCI? I assume less
> > > > > projects
> > > > > > > use it and if that's the case it could possibly be a better
> > option
> > > > for
> > > > > us
> > > > > > > if the purpose of using an additional CI environment (besides
> > > > jenkins)
> > > > > is
> > > > > > > to allow for quick feedback over PRs.
> > > > > > > If not I'll create an Infra JIRA to enable Travis for our
> > project.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Oct 20, 2016 at 5:29 PM, Suneel Marthi <
> > smar...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > On Thu, Oct 20, 2016 at 8:38 AM, Ran Ziv <r...@gigaspaces.com
> >
> > > > wrote:
> > > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > I have some questions for our mentors:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > 1) CI - we've noticed some Apache projects use online
> > services
> > > > > rather
> > > > > > > > than
> > > > > > > > > the infra tools <https://ci.apache.org/> offered by
> Apache.
> > > > We're
> > > > > > > > leaning
> > > > > > > > > towards using TravisCI, however we're somewhat worried that
> > > since
> > > > > all
> > > > > > > > > apache projects are under a single github organization,
> > builds
> > > in
> > > > > > > Travis
> > > > > > > > > will take

Re: Podling Report Reminder - November 2016

[Suneel Marthi]

Nope I did not do it, please go ahead and create it.

Thanx

Sent from my iPhone

> On Oct 29, 2016, at 9:50 PM, Arthur Berezin <art...@gigaspaces.com> wrote:
> 
> Suneel, I'll take care of this month's podling report.
> Have you already created this in confluence?
> 
> 
> 
> On Thu, Oct 27, 2016 at 2:52 AM Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
> 
>> Will do.
>> 
>> On Wed, Oct 26, 2016 at 7:51 PM, John D. Ament <johndam...@apache.org>
>> wrote:
>> 
>>> Can the drafts be moved to confluence?
>>> 
>>>> On Oct 26, 2016 19:30, "Suneel Marthi" <smar...@apache.org> wrote:
>>>> 
>>>> Here's a Draft of November Podling Report, @Ran and others please fill
>>> in /
>>>> modify as you see fit.
>>>> 
>>>> https://docs.google.com/document/d/1QqShfZUBf5Awzw_
>>>> cued-79kHAFjEtW5A6EM_8aHwlRI/edit?usp=sharing
>>>> 
>>>> 
>>>> 
>>>>> On Wed, Oct 26, 2016 at 7:01 PM, <johndam...@apache.org> wrote:
>>>>> 
>>>>> 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.
>>>>> 
>>>>> 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
>>>>> 
>>>> 
>>> 
>> 

Re: Questions regarding CI, PR and documentation

[Suneel Marthi]

On Tue, Oct 25, 2016 at 10:55 AM, Ran Ziv <r...@gigaspaces.com> wrote:

> Done.
> I'll update the project's .travis file now.
>
> What is the process of setting up a Jenkins job?
>

Needs an Infra ticket.

>
> -
>
> Regarding shared documents, is Confluence the Apache standard? What about
> using github markup files and have the documents as a part of the repo?
> Does anyone have any specific preference or other ideas on this matter?
>

Its again up to the project. Projects like Flink, Pirk, Beam have markup
files in github and use Jekyll.

They also use Confluence for few other things.


>
>
> On Tue, Oct 25, 2016 at 3:11 PM, Suneel Marthi <smar...@apache.org> wrote:
>
> > Never heard of CircleCI, and I don't think Infra is gonna support that.
> >
> > Please go ahead and create an Infra ticket to enable Travis for Aria.
> >
> > On Tue, Oct 25, 2016 at 5:24 AM, Ran Ziv <r...@gigaspaces.com> wrote:
> >
> > > Regarding CI - Does Apache also support CircleCI? I assume less
> projects
> > > use it and if that's the case it could possibly be a better option for
> us
> > > if the purpose of using an additional CI environment (besides jenkins)
> is
> > > to allow for quick feedback over PRs.
> > > If not I'll create an Infra JIRA to enable Travis for our project.
> > >
> > >
> > >
> > > On Thu, Oct 20, 2016 at 5:29 PM, Suneel Marthi <smar...@apache.org>
> > wrote:
> > >
> > > > On Thu, Oct 20, 2016 at 8:38 AM, Ran Ziv <r...@gigaspaces.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I have some questions for our mentors:
> > > > >
> > > > >
> > > > > 1) CI - we've noticed some Apache projects use online services
> rather
> > > > than
> > > > > the infra tools <https://ci.apache.org/> offered by Apache. We're
> > > > leaning
> > > > > towards using TravisCI, however we're somewhat worried that since
> all
> > > > > apache projects are under a single github organization, builds in
> > > Travis
> > > > > will take a very long time to start etc..
> > > > >
> > > > >  Are you aware of any such issues (or perhaps Travis offers some
> > > special
> > > > > QoS to Apache projects or so)..?
> > > > >
> > > >
> > > > Most Apache projects use both Travis (unofficial) and Jenkins
> (Official
> > > > Apache CI).
> > > >
> > > > Jenkins is the official CI for all Apache projects while u can also
> use
> > > > Travis to validate PRs.
> > > >
> > > > YEs, I do see that the Travis builds take forever to launch sometimes
> > > given
> > > > the large number of Apache projects.
> > > >
> > > > For Aria, you can go wth Travis if you choose to (and we need to file
> > an
> > > > Infra ticket to enable Travis for the project), but Jenkins would be
> > the
> > > > authoritative CI - most projects now have both enabled.
> > > >
> > > >
> > > > > 2) Pull requests - we're used to reviewing code using PRs on
> github.
> > > > > However, since the github repo is merely a mirror, it's impossible
> to
> > > > merge
> > > > > PRs directly on github, which means we have to rebase the PR into
> the
> > > > > master branch and close the PR manually.
> > > > >
> > > >
> > > > Pull Requests for Apache github projects work a little different
> unlike
> > > the
> > > > regular github projects.
> > > > See  http://mahout.apache.org/developers/github.html for how other
> > > > projects
> > > > handle PRs.
> > > >
> > > > Feel free to use that to create a similar documentation for Aria.
> > > >
> > > >
> > > > > Do you have any recommendation for a different workflow we could
> use
> > > for
> > > > > this purpose? Are there possibly any common automation tools from
> > other
> > > > > projects, which serve for the same purpose as the "merge PR" button
> > on
> > > > > github?
> > > > >
> > > > > By the way, I saw on Spark's documentation
> > > > > <https://cwiki.apache.org/confluence/display/SPARK/Contribut
> > > > > ing+to+Spark#ContributingtoSpark-PullRequest>
> > > > > that
> > > > > they mention the merging as if it were done automatically via
> github,
> > > so
> > > > > maybe I'm missing something here (or perhaps they do have some kind
> > of
> > > > > automation for it).
> > > > >
> > > > >
> > > > > 3) Where should project documents and documentation reside at? I've
> > > seen
> > > > > that many projects use confluence for storing development documents
> > > (e.g.
> > > > > contribution guides etc.). If you think that's what we should use
> as
> > > > well,
> > > > > could you please create us such a confluence environment too?
> > > > >
> > > >
> > > > We do have a confluence Wiki that was setup for AriaTosca. -
> > > > https://cwiki.apache.org/confluence/display/ARIATOSCA/Ariatosca+Home
> > > >
> > > >
> > > >
> > > > >
> > > > > Thanks,
> > > > > Ran
> > > > >
> > > >
> > >
> >
>

Re: Questions regarding CI, PR and documentation

[Suneel Marthi]

Never heard of CircleCI, and I don't think Infra is gonna support that.

Please go ahead and create an Infra ticket to enable Travis for Aria.

On Tue, Oct 25, 2016 at 5:24 AM, Ran Ziv <r...@gigaspaces.com> wrote:

> Regarding CI - Does Apache also support CircleCI? I assume less projects
> use it and if that's the case it could possibly be a better option for us
> if the purpose of using an additional CI environment (besides jenkins) is
> to allow for quick feedback over PRs.
> If not I'll create an Infra JIRA to enable Travis for our project.
>
>
>
> On Thu, Oct 20, 2016 at 5:29 PM, Suneel Marthi <smar...@apache.org> wrote:
>
> > On Thu, Oct 20, 2016 at 8:38 AM, Ran Ziv <r...@gigaspaces.com> wrote:
> >
> > > Hi,
> > >
> > > I have some questions for our mentors:
> > >
> > >
> > > 1) CI - we've noticed some Apache projects use online services rather
> > than
> > > the infra tools <https://ci.apache.org/> offered by Apache. We're
> > leaning
> > > towards using TravisCI, however we're somewhat worried that since all
> > > apache projects are under a single github organization, builds in
> Travis
> > > will take a very long time to start etc..
> > >
> > >  Are you aware of any such issues (or perhaps Travis offers some
> special
> > > QoS to Apache projects or so)..?
> > >
> >
> > Most Apache projects use both Travis (unofficial) and Jenkins (Official
> > Apache CI).
> >
> > Jenkins is the official CI for all Apache projects while u can also use
> > Travis to validate PRs.
> >
> > YEs, I do see that the Travis builds take forever to launch sometimes
> given
> > the large number of Apache projects.
> >
> > For Aria, you can go wth Travis if you choose to (and we need to file an
> > Infra ticket to enable Travis for the project), but Jenkins would be the
> > authoritative CI - most projects now have both enabled.
> >
> >
> > > 2) Pull requests - we're used to reviewing code using PRs on github.
> > > However, since the github repo is merely a mirror, it's impossible to
> > merge
> > > PRs directly on github, which means we have to rebase the PR into the
> > > master branch and close the PR manually.
> > >
> >
> > Pull Requests for Apache github projects work a little different unlike
> the
> > regular github projects.
> > See  http://mahout.apache.org/developers/github.html for how other
> > projects
> > handle PRs.
> >
> > Feel free to use that to create a similar documentation for Aria.
> >
> >
> > > Do you have any recommendation for a different workflow we could use
> for
> > > this purpose? Are there possibly any common automation tools from other
> > > projects, which serve for the same purpose as the "merge PR" button on
> > > github?
> > >
> > > By the way, I saw on Spark's documentation
> > > <https://cwiki.apache.org/confluence/display/SPARK/Contribut
> > > ing+to+Spark#ContributingtoSpark-PullRequest>
> > > that
> > > they mention the merging as if it were done automatically via github,
> so
> > > maybe I'm missing something here (or perhaps they do have some kind of
> > > automation for it).
> > >
> > >
> > > 3) Where should project documents and documentation reside at? I've
> seen
> > > that many projects use confluence for storing development documents
> (e.g.
> > > contribution guides etc.). If you think that's what we should use as
> > well,
> > > could you please create us such a confluence environment too?
> > >
> >
> > We do have a confluence Wiki that was setup for AriaTosca. -
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/Ariatosca+Home
> >
> >
> >
> > >
> > > Thanks,
> > > Ran
> > >
> >
>

Re: Handling Apache Github PRs

[Suneel Marthi]

Not sure that I am following.. how else would you accept contributions for
github based projects if not via PRs.

Most other projects I am involved with have stopped accepting old svn-style
patches.

On Sun, Oct 23, 2016 at 10:16 PM, John D. Ament <johndam...@apache.org>
wrote:

> That's assuming aria wants to leverage PRs, they may not.
>
> On Oct 23, 2016 22:04, "Suneel Marthi" <smar...@apache.org> wrote:
>
> > Wanted to run this by dev@ about handling github PRs and Jira for Apache
> > projects.
> >
> > Please see http://mahout.apache.org/developers/github.html
> >
> > Aria Project should have similar instructions on the project website.
> >
> > Also presently see that the github repo for Aria has a pointer to
> > ariatosca.org, you are expected to create a project website at
> > ariatosca.apache.org
> >
>

Re: CI for Aria Tosca?

[Suneel Marthi]

We missed that completely John while setting up the Infra for the project.
I suppose we need another Infra Jira to have that setup.
I can do it today.

Suneel

On Sun, Oct 16, 2016 at 12:15 PM, John D. Ament 
wrote:

> Hey guys
>
> I noticed there's no builds on https://builds.apache.org/ for Aria Tosca.
> Whats the plan for CI for this project?
>
> John
>