Re: GIT/JIRA Integration

[John D. Ament]

Take a look now.  Just checked a few tickets

- Branches are shown
- Commits are shown
- everything is under the dev tag

Assuming that's good, I'll shut off the commit edits inline.

John

On Thu, Feb 16, 2017 at 9:38 AM Ran Ziv <r...@gigaspaces.com> wrote:

> How about now? :)
>
> On Tue, Jan 31, 2017 at 5:21 AM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > I just pinged them again.
> >
> > On Mon, Jan 30, 2017 at 7:41 PM Ran Ziv <r...@gigaspaces.com> wrote:
> >
> > > Bumping this again.
> > >
> > > On Sun, Jan 22, 2017 at 11:49 AM, Ran Ziv <r...@gigaspaces.com> wrote:
> > >
> > > > Any news about this perhaps?
> > > >
> > > > On Wed, Jan 4, 2017 at 5:17 PM, Ran Ziv <r...@gigaspaces.com> wrote:
> > > >
> > > >> Sounds good. Any idea when it's supposed to happen so I'll know when
> > to
> > > >> check?
> > > >>
> > > >> On Wed, Jan 4, 2017 at 3:58 PM, John D. Ament <
> johndam...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> So it looks like its there.  INFRA is currently enabling fisheye
> for
> > > ASF,
> > > >>> since Atlassian is shutting down its public offering.  Assuming no
> > > qualms
> > > >>> with enabling fisheye for ARIAs repos, this will happen
> > automatically.
> > > >>> Any
> > > >>> concerns with that?  Once its up, we can turn off the other format.
> > > >>>
> > > >>> John
> > > >>>
> > > >>> On Wed, Jan 4, 2017 at 7:05 AM Ran Ziv <r...@gigaspaces.com> wrote:
> > > >>>
> > > >>> > Yes, that's what I was referring to.
> > > >>> > I indeed don't know about version compatibility, I hope it
> applies
> > > for
> > > >>> the
> > > >>> > Apache JIRA version as well.
> > > >>> >
> > > >>> > Ran
> > > >>> >
> > > >>> > On Wed, Jan 4, 2017 at 2:02 PM, John D. Ament <
> > johndam...@apache.org
> > > >
> > > >>> > wrote:
> > > >>> >
> > > >>> > > Ran,
> > > >>> > >
> > > >>> > > Maybe I have to be logged in to see it.  I don't have an
> account
> > on
> > > >>> that
> > > >>> > > JIRA.  Are you talking about the "Development" section on the
> far
> > > >>> right?
> > > >>> > >
> > > >>> > > That's a feature in newer JIRA versions.  We're on 6.3.  I'd
> have
> > > to
> > > >>> see
> > > >>> > if
> > > >>> > > that's an option first.
> > > >>> > >
> > > >>> > > John
> > > >>> > >
> > > >>> > > On Tue, Jan 3, 2017 at 8:31 AM Ran Ziv <r...@gigaspaces.com>
> > wrote:
> > > >>> > >
> > > >>> > > > Thanks John,
> > > >>> > > > I see that basically all git traffic now appears on JIRA as
> > > >>> comments -
> > > >>> > > that
> > > >>> > > > indeed seems too noisy IMO.
> > > >>> > > > Is it possible to configure it so that the git-jira
> integration
> > > >>> will
> > > >>> > > simply
> > > >>> > > > present commits/branches/PRs related to a specific JIRA on a
> > > >>> separate
> > > >>> > > > section rather than in comments (like it's done here
> > > >>> > > > <https://cloudifysource.atlassian.net/browse/CFY-3000> for
> > > >>> example)?
> > > >>> > > >
> > > >>> > > > thanks
> > > >>> > > >
> > > >>> > > > On Fri, Dec 30, 2016 at 4:52 PM, John D. Ament <
> > > >>> johndam...@apache.org>
> > > >>> > > > wrote:
> > > >>> > > >
> > > >>> > > > > Just as an FYI, I've enabled GIT/JIRA integration for
> > > >>> AriaTosca.  If
> > > >>> > it
> > > >>> > > > > gets too noisy we can switch to worklog entries.  LMK.
> > > >>> > > > >
> > > >>> > > >
> > > >>> > >
> > > >>> >
> > > >>>
> > > >>
> > > >>
> > > >
> > >
> >
>

Re: GIT/JIRA Integration

[John D. Ament]

I am not challenged for credentials (no one really has credentials in
fisheye at this time) and I am able to see the code.

Can you add this note to https://issues.apache.org/jira/browse/INFRA-13431
<https://issues.apache.org/jira/browse/INFRA-13431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel>
 ?

John

On Sun, Feb 19, 2017 at 8:05 AM Ran Ziv <r...@gigaspaces.com> wrote:

> Yes, I see it now, although when I click any of these (e.g. "commits") I'm
> asked to authenticate with Fisheye, but I think it's not my user that's
> needed for this authentication is it..?
> Can you actually see the commits etc.?
>
> On Sun, Feb 19, 2017 at 2:16 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > Take a look now.  Just checked a few tickets
> >
> > - Branches are shown
> > - Commits are shown
> > - everything is under the dev tag
> >
> > Assuming that's good, I'll shut off the commit edits inline.
> >
> > John
> >
> > On Thu, Feb 16, 2017 at 9:38 AM Ran Ziv <r...@gigaspaces.com> wrote:
> >
> > > How about now? :)
> > >
> > > On Tue, Jan 31, 2017 at 5:21 AM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > > > I just pinged them again.
> > > >
> > > > On Mon, Jan 30, 2017 at 7:41 PM Ran Ziv <r...@gigaspaces.com> wrote:
> > > >
> > > > > Bumping this again.
> > > > >
> > > > > On Sun, Jan 22, 2017 at 11:49 AM, Ran Ziv <r...@gigaspaces.com>
> > wrote:
> > > > >
> > > > > > Any news about this perhaps?
> > > > > >
> > > > > > On Wed, Jan 4, 2017 at 5:17 PM, Ran Ziv <r...@gigaspaces.com>
> > wrote:
> > > > > >
> > > > > >> Sounds good. Any idea when it's supposed to happen so I'll know
> > when
> > > > to
> > > > > >> check?
> > > > > >>
> > > > > >> On Wed, Jan 4, 2017 at 3:58 PM, John D. Ament <
> > > johndam...@apache.org>
> > > > > >> wrote:
> > > > > >>
> > > > > >>> So it looks like its there.  INFRA is currently enabling
> fisheye
> > > for
> > > > > ASF,
> > > > > >>> since Atlassian is shutting down its public offering.  Assuming
> > no
> > > > > qualms
> > > > > >>> with enabling fisheye for ARIAs repos, this will happen
> > > > automatically.
> > > > > >>> Any
> > > > > >>> concerns with that?  Once its up, we can turn off the other
> > format.
> > > > > >>>
> > > > > >>> John
> > > > > >>>
> > > > > >>> On Wed, Jan 4, 2017 at 7:05 AM Ran Ziv <r...@gigaspaces.com>
> > wrote:
> > > > > >>>
> > > > > >>> > Yes, that's what I was referring to.
> > > > > >>> > I indeed don't know about version compatibility, I hope it
> > > applies
> > > > > for
> > > > > >>> the
> > > > > >>> > Apache JIRA version as well.
> > > > > >>> >
> > > > > >>> > Ran
> > > > > >>> >
> > > > > >>> > On Wed, Jan 4, 2017 at 2:02 PM, John D. Ament <
> > > > johndam...@apache.org
> > > > > >
> > > > > >>> > wrote:
> > > > > >>> >
> > > > > >>> > > Ran,
> > > > > >>> > >
> > > > > >>> > > Maybe I have to be logged in to see it.  I don't have an
> > > account
> > > > on
> > > > > >>> that
> > > > > >>> > > JIRA.  Are you talking about the "Development" section on
> the
> > > far
> > > > > >>> right?
> > > > > >>> > >
> > > > > >>> > > That's a feature in newer JIRA versions.  We're on 6.3.
> I'd
> > > have
> > > > > to
> > > > > >>> see
> > > > > >>> > if
> > > > > >>> > > that's an option first.
> > > > > >>> > >
> > > > > >>> > > John
> > > > > >>> > >
> > > > > >>> > > On Tue, Jan 3, 2017 at 8:31 AM Ran Ziv <r...@gigaspaces.com
> >
> > > > wrote:
> > > > > >>> > >
> > > > > >>> > > > Thanks John,
> > > > > >>> > > > I see that basically all git traffic now appears on JIRA
> as
> > > > > >>> comments -
> > > > > >>> > > that
> > > > > >>> > > > indeed seems too noisy IMO.
> > > > > >>> > > > Is it possible to configure it so that the git-jira
> > > integration
> > > > > >>> will
> > > > > >>> > > simply
> > > > > >>> > > > present commits/branches/PRs related to a specific JIRA
> on
> > a
> > > > > >>> separate
> > > > > >>> > > > section rather than in comments (like it's done here
> > > > > >>> > > > <https://cloudifysource.atlassian.net/browse/CFY-3000>
> for
> > > > > >>> example)?
> > > > > >>> > > >
> > > > > >>> > > > thanks
> > > > > >>> > > >
> > > > > >>> > > > On Fri, Dec 30, 2016 at 4:52 PM, John D. Ament <
> > > > > >>> johndam...@apache.org>
> > > > > >>> > > > wrote:
> > > > > >>> > > >
> > > > > >>> > > > > Just as an FYI, I've enabled GIT/JIRA integration for
> > > > > >>> AriaTosca.  If
> > > > > >>> > it
> > > > > >>> > > > > gets too noisy we can switch to worklog entries.  LMK.
> > > > > >>> > > > >
> > > > > >>> > > >
> > > > > >>> > >
> > > > > >>> >
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Board Report March 2017

[John D. Ament]

Is anyone available to fill this out?

On Tue, Feb 28, 2017 at 5:22 PM Suneel Marthi 
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.
>

Changes to mailing list settings

[John D. Ament]

All,

Please be advised I've put in a request to change the mailing list
settings.  They were incorrectly set to require moderation on all emails.
The norm is to require moderation for non-subscribers.

This email should not be moderated if its working correctly.

John

Re: Podling Report Reminder - November 2016

[John D. Ament]

Can the drafts be moved to confluence?

On Oct 26, 2016 19:30, "Suneel Marthi"  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,  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: Add me as contributor

[John D. Ament]

You need to have an ICLA on file.  Once that happens, you will be given an
account and write access to incubator repositories.

John

On Wed, Nov 16, 2016 at 5:35 PM Suneel Marthi 
wrote:

> 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

[John D. Ament]

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

Re: Podling Report Reminder - November 2016

[John D. Ament]

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

Re: Podling Report Reminder - November 2016

[John D. Ament]

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

Re: Questions regarding CI, PR and documentation

[John D. Ament]

Could you add me as well?

On Sun, Oct 30, 2016 at 11:50 AM Suneel Marthi 
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  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 
> wrote:
> >
> > > On Tue, Oct 25, 2016 at 10:55 AM, Ran Ziv  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 
> > > 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 
> 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 
> > > 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  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 

JIRA Issue Scheme

[John D. Ament]

I just saw this ticket in the INFRA backlog -
https://issues.apache.org/jira/browse/INFRA-12733

Just wondering, was this discussed on the ML?  I didn't see it, and I would
recommend leaving in ticket types like documentation.

Re: Podling Report Reminder - November 2016

[John D. Ament]

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
> > >
> > > >> 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: Podling Report Reminder - November 2016

[John D. Ament]

Ok, thanks for clarifying.  Can you update the report?

John

On Fri, Nov 4, 2016 at 9:23 AM Ran Ziv <r...@gigaspaces.com> wrote:

> Suneel - it's not completely like that - ARIA is a new project in most
> senses, so there isn't many to migrate to the mailing lists. JIRA is a
> different case though, and in a while we'll probably have others create
> issues on there as well.
>
> John - Arthur's meaning is that additional developers worked on something
> that's intended to be integrated into ARIA in the very near future. they
> haven't been admitted by the PMC. Basically this isn't relevant yet, the
> line should probably be redacted.
>
> same for the bug reports - these issues are relevant for code which will be
> integrated into the ARIA project over the next couple of weeks, but at the
> moment these bugs as well as the bug fixes are completely independent of
> the ARIA project on apache.
>
>
> apologies for the confusion, we're still in the process of merging code
> pieces which were separate before together
>
>
> Ran
>
> On Fri, Nov 4, 2016 at 3:07 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > Ok... this is a bit confusing.
> >
> > This line makes no sense -
> >
> > - 2 addtional Gigaspaces developers joind ARIA.
> >
> > Did we in fact vote them in? What does that mean?
> >
> > - Recieving bug repors from Open-O community which indicates active users
> > of the TOSCA parser.
> >
> > I don't see these in JIRA
> >
> > John
> >
> > On Fri, Nov 4, 2016 at 9:00 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>
> > > &g

Re: Podling Report Reminder - November 2016

[John D. Ament]

Ok... this is a bit confusing.

This line makes no sense -

- 2 addtional Gigaspaces developers joind ARIA.

Did we in fact vote them in? What does that mean?

- Recieving bug repors from Open-O community which indicates active users
of the TOSCA parser.

I don't see these in JIRA

John

On Fri, Nov 4, 2016 at 9:00 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/
> >

[DISCUSS] Move Aria Tosca to Reporting Group 1

[John D. Ament]

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: JIRA Issue Scheme

[John D. Ament]

Hi Ran,

Thanks for the insight.  The biggest I'm trying to point out is to have
open discussions on the mailing lists when making these types of
decisions.  I get that you guys at Gigaspaces are colocated and probably
talked about this in your office - would be good to also have the
discussion here. At some point I hope Aria grows beyond Gigaspaces
employees and in order for this to be a true team of individuals not just
representing corporate interests, those discussions are intended to happen
on the ML.

John

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

> The reason we asked for this is because we wanted to simplify some of the
> JIRA mechanisms (screens, issues) but with only requiring minimal changes
> from the defaults.
>
> From my experience having too many issue types makes it confusing for issue
> reporters to choose the right one (e.g. "story" vs "improvement").
>
> It's true that Documentation specifically is a valid type, but I wanted to
> ask for an existing issue types scheme rather than ask for the creation of
> a new one (partially because I was hoping for this to help in having this
> issue be dealt with quickly, which hasn't quite proven to be the case..).
> Under the current scheme, the right type for a documentation issue would be
> "Task", which seems fine to me, but I don't really feel too strongly about
> it either way.
>
> I do think types such as "test", "wish", "improvement" etc. are problematic
> though, and would rather not have them around :)
>
>
>
>
> On Sun, Oct 30, 2016 at 5:59 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > I just saw this ticket in the INFRA backlog -
> > https://issues.apache.org/jira/browse/INFRA-12733
> >
> > Just wondering, was this discussed on the ML?  I didn't see it, and I
> would
> > recommend leaving in ticket types like documentation.
> >
>

CI for Aria Tosca?

[John D. Ament]

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

Re: Dec 16 Podling Report

[John D. Ament]

I added the following mentor comment to the report:

  johndament:  The podling is still getting its feet wet.  Discussions are
starting to happen on the mailing lists rather than in physical offices
which is good and will help to bring about a more diverse community.  I
would also strongly encourage the podling to work with their mentors to get
infra changes in to avoid confusion.

On Mon, Dec 5, 2016 at 5:25 AM Arthur Berezin <art...@gigaspaces.com> wrote:

> +1
> Thanks, the "How to Contribute" guide is the first step towards starting to
> grow the community and encourage engagement and code contribution.
>
> On Mon, Dec 5, 2016 at 4:50 AM Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
>
> > 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:
> > > >
> > >
> >
>

Re: [DISCUSS] Website

[John D. Ament]

The repo's been created:
https://git-wip-us.apache.org/repos/asf/incubator-ariatosca-website.git
Access it using the normal means.

John

On Tue, Jan 10, 2017 at 11:33 AM Arthur Berezin <art...@gigaspaces.com>
wrote:

> Sounds good. Thanks.
>
> On Tue, Jan 10, 2017 at 6:31 PM John D. Ament <johndam...@apache.org>
> wrote:
>
> > Ok, I'll get the reporeq in.  I'll call it "incubator-ariatosca-website"
> >
> > John
> >
> > On Tue, Jan 10, 2017 at 11:23 AM Arthur Berezin <art...@gigaspaces.com>
> > wrote:
> >
> > > Thanks, John.
> > >
> > > Let's first create a dedicated repo for the website and start from
> there.
> > >
> > > Arthur
> > >
> > > On Mon, Jan 9, 2017 at 4:02 PM John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > > > Arthur,
> > > >
> > > > There's some basic docs up on http://apache.org/dev/#web
> > > > It lists CMS as the preferred approach.  CMS isn't the preferred any
> > > > longer, so this needs some updating.
> > > >
> > > > The recommendation is to use a dedicated git repo for the website
> code.
> > > > Once that's in, you would setup a jenkins job that clones the repo,
> > > builds
> > > > the site, and then pushes to asf-site.
> > > >
> > > > There's a template for a shell script that does this here:
> > > >
> > > >
> > >
> >
> http://svn.apache.org/viewvc/incubator/public/trunk/build_site.sh?revision=1776892=markup
> > > >
> > > > We should be able to keep the discussions on this list, we can raise
> > > infra
> > > > tickets as needed.
> > > >
> > > > John
> > > >
> > > > On Mon, Jan 9, 2017 at 7:50 AM Arthur Berezin <art...@gigaspaces.com
> >
> > > > wrote:
> > > >
> > > > > John, Suneel,  We would like to migrate the website to Jekyll,
> where
> > > can
> > > > I
> > > > > find more information on what servers the web pages from the ASF
> > repos?
> > > > Is
> > > > > there anyone that could help with the migration process, setting up
> > > > needed
> > > > > asf infrastructure?
> > > > >
> > > > >
> > > > > On Mon, Dec 5, 2016 at 2:39 PM Arthur Berezin <
> art...@gigaspaces.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Hi All,
> > > > > > I would like to follow up on this, and pick up the ball for
> > updating
> > > > > > ARIA's website according to ASF guidelines.
> > > > > >
> > > > > > [comments inline]
> > > > > >
> > > > > > On Mon, Nov 14, 2016 at 4:43 PM John D. Ament <
> > johndam...@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > All,
> > > > > >
> > > > > > AriaTosca has been incubating since August and still does not
> have
> > a
> > > > > > website.  IMHO this is a potential problem, especially around
> > > community
> > > > > > building.
> > > > > >
> > > > > >
> > > > > > One idea may be to use the newly crafted Apache Website Template
> to
> > > > build
> > > > > > the website.  You can see the template here:
> > > > > > https://github.com/apache/apache-website-template - its based on
> > > > jekyll.
> > > > > >
> > > > > > The flipside, there's already http://ariatosca.org/ which I'm
> > > assuming
> > > > > is
> > > > > > this podling.  It may make sense for this website to become our
> > > > website,
> > > > > > focused on the underlying Apache community.
> > > > > >
> > > > > >
> > > > > > You are correct, www.ariatosca.org is the website we brought up
> > for
> > > > the
> > > > > > ARIA TOSCA Podling,it was brought up before it was accepted as an
> > asf
> > > > > > Incubator project. I would like to make sure we are compliant
> with
> > > ASF
> > > > > > process as well, and we have all needed information there.
> > > > > >
> > > > > > Can we use this this as a start

Re: Dec 16 Podling Report

[John D. Ament]

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

Re: GIT/JIRA Integration

[John D. Ament]

Ran,

Maybe I have to be logged in to see it.  I don't have an account on that
JIRA.  Are you talking about the "Development" section on the far right?

That's a feature in newer JIRA versions.  We're on 6.3.  I'd have to see if
that's an option first.

John

On Tue, Jan 3, 2017 at 8:31 AM Ran Ziv <r...@gigaspaces.com> wrote:

> Thanks John,
> I see that basically all git traffic now appears on JIRA as comments - that
> indeed seems too noisy IMO.
> Is it possible to configure it so that the git-jira integration will simply
> present commits/branches/PRs related to a specific JIRA on a separate
> section rather than in comments (like it's done here
> <https://cloudifysource.atlassian.net/browse/CFY-3000> for example)?
>
> thanks
>
> On Fri, Dec 30, 2016 at 4:52 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > Just as an FYI, I've enabled GIT/JIRA integration for AriaTosca.  If it
> > gets too noisy we can switch to worklog entries.  LMK.
> >
>

GIT/JIRA Integration

[John D. Ament]

Just as an FYI, I've enabled GIT/JIRA integration for AriaTosca.  If it
gets too noisy we can switch to worklog entries.  LMK.

[jira] [Commented] (ARIA-54) Create an ARIA package on PyPI

[John D. Ament (JIRA)]

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

John D. Ament commented on ARIA-54:
---

[~ran] just to point out, any distribution has to be in compliance with our ASF 
policies.  http://www.apache.org/dev/#releases

Key things:
- We cannot distribute a release outside of ASF if it hasn't been approved
- snapshot builds (if pypi has that concept) must be clearly marked as for dev 
testing only
- needs to conform to proper branding

Feel free to drop a note on the dev list if you have questions.

> Create an ARIA package on PyPI
> --
>
> Key: ARIA-54
> URL: https://issues.apache.org/jira/browse/ARIA-54
> Project: AriaTosca
>  Issue Type: Story
>Reporter: Ran Ziv
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [DISCUSS] Website

[John D. Ament]

Arthur,

There's some basic docs up on http://apache.org/dev/#web
It lists CMS as the preferred approach.  CMS isn't the preferred any
longer, so this needs some updating.

The recommendation is to use a dedicated git repo for the website code.
Once that's in, you would setup a jenkins job that clones the repo, builds
the site, and then pushes to asf-site.

There's a template for a shell script that does this here:
http://svn.apache.org/viewvc/incubator/public/trunk/build_site.sh?revision=1776892=markup

We should be able to keep the discussions on this list, we can raise infra
tickets as needed.

John

On Mon, Jan 9, 2017 at 7:50 AM Arthur Berezin <art...@gigaspaces.com> wrote:

> John, Suneel,  We would like to migrate the website to Jekyll, where can I
> find more information on what servers the web pages from the ASF repos? Is
> there anyone that could help with the migration process, setting up needed
> asf infrastructure?
>
>
> On Mon, Dec 5, 2016 at 2:39 PM Arthur Berezin <art...@gigaspaces.com>
> wrote:
>
> > Hi All,
> > I would like to follow up on this, and pick up the ball for updating
> > ARIA's website according to ASF guidelines.
> >
> > [comments inline]
> >
> > On Mon, Nov 14, 2016 at 4:43 PM John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > All,
> >
> > AriaTosca has been incubating since August and still does not have a
> > website.  IMHO this is a potential problem, especially around community
> > building.
> >
> >
> > One idea may be to use the newly crafted Apache Website Template to build
> > the website.  You can see the template here:
> > https://github.com/apache/apache-website-template - its based on jekyll.
> >
> > The flipside, there's already http://ariatosca.org/ which I'm assuming
> is
> > this podling.  It may make sense for this website to become our website,
> > focused on the underlying Apache community.
> >
> >
> > You are correct, www.ariatosca.org is the website we brought up for the
> > ARIA TOSCA Podling,it was brought up before it was accepted as an asf
> > Incubator project. I would like to make sure we are compliant with ASF
> > process as well, and we have all needed information there.
> >
> > Can we use this this as a starting point, add the missing information
> > expected to be there?
> > I've highlighted the gaps we should complete, based on the the Podling
> > webisite guildeline:
> > http://incubator.apache.org/guides/sites.html
> >
> >
> >- Project Home Page: the primary entry point to the site; contains
> >project description, news, invitation to join the project.
> >- License Page: usually, the Apache License 2.0
> >- Downloads: many projects in incubation will release code, and this
> >page describes them and has links to the download pages that redirect
> to
> >Apache Mirror sites.
> >- Documentation: this page describes the project documentation,
> >including javadoc for Java projects; guides, tutorials, and links to
> >external documentation.
> >- *Committers: *a list of current committers on the project.
> >- *Mailing Lists:* there are several mailing lists that the community
> >might be interested in, and this page contains mailto: links that
> >allow easy subscription (and unsubscription) to any of them.
> >- *FAQ: *frequently asked questions are answered here.
> >- Road Map: if the project has a vision of future community or
> >development activities, the road map is published here.
> >- *Source Code: *links to the browsable source repository and svn
> >commands to check out the sources.
> >- Coding Standards: the coding standards for submitted code by the
> >community, along with a description of how strict the project intends
> to be.
> >- *Issue Tracking: *links to the JIRA or other issue tracking tool,
> >possibly including frequently used filters for issue lists.
> >- Dependencies: other projects that this project depends on.
> >- favicon: the project's icon in a format suitable for a browser's
> >address bar. If absent, an Apache Feather will be displayed.
> >
> >
> >
> >
> > Once we have that ironed our, we need to figure out a solution to getting
> > the website published.  The current recommended solution is gitpubsub.
> >
> > It
> > involves setting up a buildbot to monitor this repo to rebuild the
> asf-site
> > branch, then serving that asf-site branch as the actual website.  Its
> > similar to how github pages work, except you get an apache domain.
> >
> >
> > Currently www.ARIATOSCA.org is a wordpress app running on AWS. The
> reason
> > wordpress was chosen was due the low effort and speed we chould bring up
> a
> > graphically designed website, and add content quickly as we go along.
> >
> > John, Suneel, what would be the recomendation here? Should we migrate to
> > Jekyll?
> >
> >
> > Arthur
> >
> >
> >
> > John
> >
> >
>

[DISCUSS] Rename ARIATOSCA to ARIA

[John D. Ament]

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

[REMINDER] Policies around Publicity & Press

[John D. Ament]

All Podlings,

In recent days I've been contacted about several publicity issues that have
gone a bit off kilter.  I wanted to remind podlings two very import
policies.

1. Podlings MUST coordinate with the Public Relations Committee with all
publicity activities.
2. The Press Team MUST review any press releases or similar communication
referencing a podling before it is published.

Relevant Links:

https://incubator.apache.org/guides/branding.html#publicity_activities
https://incubator.apache.org/guides/branding.html#publicity_throughout_the_incubation_process

Please reach out with any concerns.

Regards,

John D. Ament
VP, Apache Incubator

Re: Congrats on the First Release!

[John D. Ament]

Ran,

One thing I was thinking of, we should include a step to clean up old
releases.  For instance, on dist/dev we should only have the release under
vote.  Once it's been approved we should be moving that to the
dist/release.  When we publish a new release on dist/release, the old
release should be deleted.

John

On Thu, Jul 13, 2017 at 6:58 AM Ran Ziv <r...@gigaspaces.com> wrote:

> I've documented the release process on our Confluence:
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Release+Process
>
> This, together with the release automation script
> <https://issues.apache.org/jira/browse/ARIA-307>, should hopefully make
> things much simpler for the release manager of the next release.
>
>
> Please let me know if you have any comments on the document or if you think
> I might have missed something.
>
>
>
> On Mon, Jul 10, 2017 at 4:11 PM, Ran Ziv <r...@gigaspaces.com> wrote:
>
> > Done:
> > https://issues.apache.org/jira/browse/ARIA-306 ( with sub-tasks
> > https://issues.apache.org/jira/browse/ARIA-307 and
> > https://issues.apache.org/jira/browse/ARIA-308 )
> > https://issues.apache.org/jira/browse/ARIA-309
> >
> >
> > On Mon, Jul 10, 2017 at 3:54 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> >> Ran,
> >>
> >> Do you want to create JIRAs for these?
> >>
> >> John
> >>
> >> On Mon, Jul 10, 2017 at 8:13 AM Ran Ziv <r...@gigaspaces.com> wrote:
> >>
> >> > Thanks :)
> >> >
> >> > 1) Documenting the release process - I have it on my list and will get
> >> it
> >> > on our Confluence soon. I also wrote some scripts to ease this
> process,
> >> > we'll probably merge them onto the repo one way or another soon.
> >> > 2) The sdist comes with generated HTML pages; We should probably have
> >> these
> >> > on our website as well.
> >> > 3) One already exists on our confluence - here:
> >> > https://cwiki.apache.org/confluence/display/ARIATOSCA/Contri
> >> buting+to+ARIA
> >> > and here:
> >> >
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Contributing+Code
> >> > 4) Making things easily discoverable - IMO that's mostly website work,
> >> need
> >> > to make sure the website links everywhere needed including our
> >> Confluence
> >> > etc..
> >> > 5) Downloads page - yup, more website work :)
> >> >
> >> >
> >> > Thanks for the tips, I hope we'll be able to follow up on those
> shortly.
> >> >
> >> >
> >> >
> >> > On Mon, Jul 10, 2017 at 1:04 AM, Suneel Marthi <
> suneel.mar...@gmail.com
> >> >
> >> > wrote:
> >> >
> >> > > Same here, congrats Team on first release.
> >> > >
> >> > > On Sun, Jul 9, 2017 at 5:20 PM, John D. Ament <
> johndam...@apache.org>
> >> > > 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
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>

Congrats on the First Release!

[John D. Ament]

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

Dist Area permissions problem

[John D. Ament]

All,

Please be advised that the infra team is aware of a permission problem that
is affecting podlings ability to write to the incubator dist area.  This
may cause you to be unable to create staged releases and promote those to
the public mirrors.  You can track the status in
https://issues.apache.org/jira/browse/INFRA-14609 .

Likewise, I want to make the podlings aware of a permission problem from
the weekend where git permissions were a little off.  That has since been
fixed.

Apologies for any inconvenience.

John

Re: Installation issue in 0.1.0 release

[John D. Ament]

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!

[John D. Ament]

Ran,

Do you want to create JIRAs for these?

John

On Mon, Jul 10, 2017 at 8:13 AM Ran Ziv <r...@gigaspaces.com> wrote:

> Thanks :)
>
> 1) Documenting the release process - I have it on my list and will get it
> on our Confluence soon. I also wrote some scripts to ease this process,
> we'll probably merge them onto the repo one way or another soon.
> 2) The sdist comes with generated HTML pages; We should probably have these
> on our website as well.
> 3) One already exists on our confluence - here:
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Contributing+to+ARIA
> and here:
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Contributing+Code
> 4) Making things easily discoverable - IMO that's mostly website work, need
> to make sure the website links everywhere needed including our Confluence
> etc..
> 5) Downloads page - yup, more website work :)
>
>
> Thanks for the tips, I hope we'll be able to follow up on those shortly.
>
>
>
> On Mon, Jul 10, 2017 at 1:04 AM, Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
>
> > Same here, congrats Team on first release.
> >
> > On Sun, Jul 9, 2017 at 5:20 PM, John D. Ament <johndam...@apache.org>
> > 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: Contribution for https://issues.apache.org/jira/browse/ARIA-118

[John D. Ament]

You'll probably also want to review
https://cwiki.apache.org/confluence/display/ARIATOSCA/Contributing+to+ARIA

John

On Thu, Jul 20, 2017 at 9:05 AM D Jayachandran 
wrote:

> Thanks Tal,
>
> I will be working on this.
>
> Regards,
> DJ
> -Original Message-
> From: Tal Liron [mailto:t...@gigaspaces.com]
> Sent: Thursday, July 20, 2017 6:24 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Contribution for
> https://issues.apache.org/jira/browse/ARIA-118
>
> It's unassigned, so I don't see why not!
>
> On Thu, Jul 20, 2017 at 7:41 AM, D Jayachandran <
> d.jayachand...@ericsson.com
> > wrote:
>
> > Hi,
> >
> > Do you have any plans on working on this JIRA issue ?
> > https://issues.apache.org/jira/browse/ARIA-118
> > Can we contribute on this ?
> >
> >
> > Regards,
> > DJ
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[John D. Ament]

Ran,

I previously sent this email [1] on a recommended approach for creating a
source release.  Let me know if that helps.  Since I didn't see any
questions, I had assumed that it made sense.

I would label what you have proposed here as the pypi package, which would
be good for review as well.

I'm traveling the next few days (US holiday) so my responses may be delayed.

John


[1]:
https://lists.apache.org/thread.html/59e8102457c1a1b49c435e714c39780dc728d7f74da2021ddd5c8281@%3Cdev.ariatosca.apache.org%3E

On Thu, Jun 29, 2017 at 12:28 PM Ran Ziv <r...@gigaspaces.com> wrote:

> The vote is cancelled in light of a "-1" vote.
> I'll fix the mentioned issues next week and raise another vote.
>
> I could still use some clarification with regards to what constitutes a
> "source distribution" for this matter.
>
> Thanks,
> Ran
>
> On Thu, Jun 29, 2017 at 7:08 PM, Ran Ziv <r...@gigaspaces.com> wrote:
>
> > Right, I'll need to look more into RAT before creating another RC package
> > then.
> >
> >
> > Re source release - so should it contain exactly everything that's in the
> > repository? This is somewhat different from the Python concept of a
> source
> > distribution.
> > Does it mean the generated doc files can't be there (since they're not in
> > the repo)?
> > Should files like "MANIFEST.IN" which gets compiled when creating a
> > source distribution appear in the source release?
> > Do all the tests and CI-related configurations need to appear in the
> > source release as well?
> >
> >
> > If that's what's needed I can just tar the repository itself I guess.
> > Setting aside the canonical distribution for a moment, would it be ok for
> > the source distribution on PyPI to be of the format that I'm using
> > currently rather than the one you're describing now?
> >
> >
> >
> > On Thu, Jun 29, 2017 at 7:00 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> >> On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv <r...@gigaspaces.com> 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-de
> >> v/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/9fd77b14753bbde462bea06
> >> fc2e1c03d5cf5a89cea2fabd6751d805a@%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 <johndam...@apache.org
> >
> >> > wrote:
> >> >
> >> > > -1.  Found the following issues:
> >> > >
> >> > &g

Re: [VOTE] publish ariatosca 0.1.0

[John D. Ament]

On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv <r...@gigaspaces.com> 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/9fd77b14753bbde462bea06fc2e1c03d5cf5a89cea2fabd6751d805a@%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 <johndam...@apache.org>
> 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 <r...@gigaspaces.com> 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

[John D. Ament]

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

[John D. Ament]

-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 (#2)

[John D. Ament]

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: Don't release this because...
>
>
> Thanks,
> Ran
>

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

[John D. Ament]

On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv <r...@gigaspaces.com> 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 <johndam...@apache.org>
> 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 <r...@gigaspaces.com> 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: Don't release this because...
> > >
> > >
> > > Thanks,
> > > Ran
> > >
> >
>

Re: New mailing lists

[John D. Ament]

No, and that's sort of the issue at hand here.  I've requested these
mailing list changes because the dev@ traffic is typically github or JIRA
chatter.  We have no on list discussions.  I'm basically trying to force
you guys to actually talk to one another via email, since our other
attempts have not worked out well.

I would expect that Slack discussions are summarized here by those
participating in them.  Not automatically.

John

On Tue, May 9, 2017 at 10:00 PM Arthur Berezin <art...@gigaspaces.com>
wrote:

> I missed the Slack chat, but sounds good +1. Is there an easy way to get a
> digest of the slack chat over dev mailing list?
>
> On Tue, May 9, 2017, 21:43 John D. Ament <johndam...@apache.org> wrote:
>
> > All,
> >
> > Based on a brief chat on Slack, I'm going to go ahead and create two new
> > mailing lists:
> >
> > - commits@
> > - issues@
> >
> > The reason being, the dev list is designed for developer discussions, but
> > most of the banter is on JIRA issues or GitHub PRs/commits.  To
> effectively
> > measure the community openness we need to separate the types.
> >
> > All changes in a JIRA issue will be sent to issues@ and all commits will
> > go
> > to commits@.
> >
> > John
> >
>

New mailing lists

[John D. Ament]

All,

Based on a brief chat on Slack, I'm going to go ahead and create two new
mailing lists:

- commits@
- issues@

The reason being, the dev list is designed for developer discussions, but
most of the banter is on JIRA issues or GitHub PRs/commits.  To effectively
measure the community openness we need to separate the types.

All changes in a JIRA issue will be sent to issues@ and all commits will go
to commits@.

John

[DRAFT] What the new Status Pages potentially look like

[John D. Ament]

All,

We're piloting a new format for the podling status pages.  Specifically,
the current status page leaves a lot to be desired - it's basically crafted
html, there's no structure and its hard to find missing items.  The end
goal is to have a web form editable in Whimsy, but until we get more input
on what the content looks like I don't want to make changes like that.  I'm
asking at this point for podlings to take a look at the status output,
potentially update their own content, and see if they like the output.

If you navigate to https://whimsy.apache.org/roster/ppmc/ (authentication
is via your ASF committer username/password) and find your podling, you'll
see your current roster as well as your current status information.

The status pages can be found in SVN at this directory
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/

Some more information can be found at
https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E

If you're not sure what to fill out, feel free to reach out.

John

Creating a Source Release

[John D. Ament]

I worked with one of my podlings that has a release very similar to yours
to come up with steps needed for a source release.  That information can be
found at [1].  AriaTosca may want to adapt something very similar for their
source bundle.

John

[1]: http://ponymail.incubator.apache.org/building.html

Website ready for builds?

[John D. Ament]

All,

Some feedback from today's board meeting.  Its noted that Aria Tosca has
been incubating for 10 months and still doesn't have a website hosted at
Apache.  I know Arthur had been doing some work on the area, but wanted to
see if the current code in the website repo was ready to go?

If so, would I be able to get a script together similar to
https://github.com/apache/incubator/blob/jbake-site/build_site.sh that does
the actual site build?  Obviously replace the bake command (from jbake)
with the proper commands to get the website built.

John

Re: Website ready for builds?

[John D. Ament]

Arthur,

Yes, exactly.  If you can get a script like that together, or tell me what
the equivalent of the build would be, I can get it running into a build
chain so that we finally have ariatosca.incubator.apache.org as our website.

John

On Thu, Jun 22, 2017 at 5:12 AM Arthur Berezin <art...@gigaspaces.com>
wrote:

> Thanks, John, I've pushed an update to aria-tosca-website last week and I
> have another major update coming in today.
>
> If I understand correctly, the example script builds a static website and
> then publishes it back to the git repo from which the static HTML would get
> served?
>
>
>
>
> On Thu, Jun 22, 2017 at 5:39 AM John D. Ament <johndam...@apache.org>
> wrote:
>
> > All,
> >
> > Some feedback from today's board meeting.  Its noted that Aria Tosca has
> > been incubating for 10 months and still doesn't have a website hosted at
> > Apache.  I know Arthur had been doing some work on the area, but wanted
> to
> > see if the current code in the website repo was ready to go?
> >
> > If so, would I be able to get a script together similar to
> > https://github.com/apache/incubator/blob/jbake-site/build_site.sh that
> > does
> > the actual site build?  Obviously replace the bake command (from jbake)
> > with the proper commands to get the website built.
> >
> > John
> >
>

Re: Website ready for builds?

[John D. Ament]

Ok, the website is up.  http://ariatosca.incubator.apache.org/

Can you please add the incubator logo + disclaimer on it?

John

On Thu, Jun 22, 2017 at 10:41 AM John D. Ament <johndam...@apache.org>
wrote:

> That should start working after infra does
> https://issues.apache.org/jira/browse/INFRA-14420
>
> John
>
>
> On Thu, Jun 22, 2017 at 10:39 AM Arthur Berezin <art...@gigaspaces.com>
> wrote:
>
>> I'm getting 404 on http://ariatosca.incubator.apache.org/
>> I assume that now infra team needs to redirect $URL to the site?
>>
>> On Thu, Jun 22, 2017 at 5:28 PM John D. Ament <johndam...@apache.org>
>> wrote:
>>
>> > Arthur,
>> >
>> > I setup a build job.  Looks like we're good.
>> >
>> >
>> https://builds.apache.org/view/A-D/view/AriaTosca/job/AriaTosca%20Website/
>> >
>> > I'm going to commit the script changes and open an infra ticket to setup
>> > the website.
>> >
>> > John
>> >
>> > On Thu, Jun 22, 2017 at 10:07 AM Arthur Berezin <art...@gigaspaces.com>
>> > wrote:
>> >
>> > > Yes, it shouldn't be a problem.
>> > >
>> > > On Thu, Jun 22, 2017 at 5:04 PM John D. Ament <john.d.am...@gmail.com
>> >
>> > > wrote:
>> > >
>> > > > Arthur,
>> > > >
>> > > > Can the domain be donated to the ASF?
>> > > >
>> > > > John
>> > > >
>> > > > On Thu, Jun 22, 2017 at 10:03 AM Arthur Berezin <
>> art...@gigaspaces.com
>> > >
>> > > > wrote:
>> > > >
>> > > > > Once this is done, I'll redirect the existing domain
>> > > > http://ariatosca.org/
>> > > > > to
>> > > > > our new ASF homepage
>> > > > >
>> > > > > On Thu, Jun 22, 2017 at 4:56 PM Arthur Berezin <
>> > art...@gigaspaces.com>
>> > > > > wrote:
>> > > > >
>> > > > > > The build command for Jekyll should be:
>> > > > > > bundle exec Jekyll build --destination $WORKDIR $WORKDIR
>> > > > > >
>> > > > > > I added the build script to the website repo and added the
>> Jekyll
>> > > > > command,
>> > > > > > it assumes that all dependencies are already installed and it's
>> a
>> > > > little
>> > > > > > challenge to test this
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://github.com/apache/incubator-ariatosca-website/blob/master/build_site.sh
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > On Thu, Jun 22, 2017 at 3:11 PM John D. Ament <
>> > johndam...@apache.org
>> > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > >> Arthur,
>> > > > > >>
>> > > > > >> Yes, exactly.  If you can get a script like that together, or
>> tell
>> > > me
>> > > > > what
>> > > > > >> the equivalent of the build would be, I can get it running
>> into a
>> > > > build
>> > > > > >> chain so that we finally have ariatosca.incubator.apache.org
>> as
>> > our
>> > > > > >> website.
>> > > > > >>
>> > > > > >> John
>> > > > > >>
>> > > > > >> On Thu, Jun 22, 2017 at 5:12 AM Arthur Berezin <
>> > > art...@gigaspaces.com
>> > > > >
>> > > > > >> wrote:
>> > > > > >>
>> > > > > >> > Thanks, John, I've pushed an update to aria-tosca-website
>> last
>> > > week
>> > > > > and
>> > > > > >> I
>> > > > > >> > have another major update coming in today.
>> > > > > >> >
>> > > > > >> > If I understand correctly, the example script builds a static
>> > > > website
>> > > > > >> and
>> > > > > >> > then publishes it back to the git repo from which the static
>> > HTML
>> > > > > would
>> > > > > >> get
>> > > > > >> > served?
>> > > > > >> >
>> > > > > >> >
>> > > > > >> >
>> > > > > >> >
>> > > > > >> > On Thu, Jun 22, 2017 at 5:39 AM John D. Ament <
>> > > > johndam...@apache.org>
>> > > > > >> > wrote:
>> > > > > >> >
>> > > > > >> > > All,
>> > > > > >> > >
>> > > > > >> > > Some feedback from today's board meeting.  Its noted that
>> Aria
>> > > > Tosca
>> > > > > >> has
>> > > > > >> > > been incubating for 10 months and still doesn't have a
>> website
>> > > > > hosted
>> > > > > >> at
>> > > > > >> > > Apache.  I know Arthur had been doing some work on the
>> area,
>> > but
>> > > > > >> wanted
>> > > > > >> > to
>> > > > > >> > > see if the current code in the website repo was ready to
>> go?
>> > > > > >> > >
>> > > > > >> > > If so, would I be able to get a script together similar to
>> > > > > >> > >
>> > > https://github.com/apache/incubator/blob/jbake-site/build_site.sh
>> > > > > >> that
>> > > > > >> > > does
>> > > > > >> > > the actual site build?  Obviously replace the bake command
>> > (from
>> > > > > >> jbake)
>> > > > > >> > > with the proper commands to get the website built.
>> > > > > >> > >
>> > > > > >> > > John
>> > > > > >> > >
>> > > > > >> >
>> > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: Website ready for builds?

[John D. Ament]

Hey guys, thanks for getting the logo in.  Looks nice.  Would it be
possible to get the logo moved to the top though?

On Thu, Jun 22, 2017 at 12:09 PM John D. Ament <johndam...@apache.org>
wrote:

> Ok, the website is up.  http://ariatosca.incubator.apache.org/
>
> Can you please add the incubator logo + disclaimer on it?
>
> John
>
>
> On Thu, Jun 22, 2017 at 10:41 AM John D. Ament <johndam...@apache.org>
> wrote:
>
>> That should start working after infra does
>> https://issues.apache.org/jira/browse/INFRA-14420
>>
>> John
>>
>>
>> On Thu, Jun 22, 2017 at 10:39 AM Arthur Berezin <art...@gigaspaces.com>
>> wrote:
>>
>>> I'm getting 404 on http://ariatosca.incubator.apache.org/
>>> I assume that now infra team needs to redirect $URL to the site?
>>>
>>> On Thu, Jun 22, 2017 at 5:28 PM John D. Ament <johndam...@apache.org>
>>> wrote:
>>>
>>> > Arthur,
>>> >
>>> > I setup a build job.  Looks like we're good.
>>> >
>>> >
>>> https://builds.apache.org/view/A-D/view/AriaTosca/job/AriaTosca%20Website/
>>> >
>>> > I'm going to commit the script changes and open an infra ticket to
>>> setup
>>> > the website.
>>> >
>>> > John
>>> >
>>> > On Thu, Jun 22, 2017 at 10:07 AM Arthur Berezin <art...@gigaspaces.com
>>> >
>>> > wrote:
>>> >
>>> > > Yes, it shouldn't be a problem.
>>> > >
>>> > > On Thu, Jun 22, 2017 at 5:04 PM John D. Ament <
>>> john.d.am...@gmail.com>
>>> > > wrote:
>>> > >
>>> > > > Arthur,
>>> > > >
>>> > > > Can the domain be donated to the ASF?
>>> > > >
>>> > > > John
>>> > > >
>>> > > > On Thu, Jun 22, 2017 at 10:03 AM Arthur Berezin <
>>> art...@gigaspaces.com
>>> > >
>>> > > > wrote:
>>> > > >
>>> > > > > Once this is done, I'll redirect the existing domain
>>> > > > http://ariatosca.org/
>>> > > > > to
>>> > > > > our new ASF homepage
>>> > > > >
>>> > > > > On Thu, Jun 22, 2017 at 4:56 PM Arthur Berezin <
>>> > art...@gigaspaces.com>
>>> > > > > wrote:
>>> > > > >
>>> > > > > > The build command for Jekyll should be:
>>> > > > > > bundle exec Jekyll build --destination $WORKDIR $WORKDIR
>>> > > > > >
>>> > > > > > I added the build script to the website repo and added the
>>> Jekyll
>>> > > > > command,
>>> > > > > > it assumes that all dependencies are already installed and
>>> it's a
>>> > > > little
>>> > > > > > challenge to test this
>>> > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://github.com/apache/incubator-ariatosca-website/blob/master/build_site.sh
>>> > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > > On Thu, Jun 22, 2017 at 3:11 PM John D. Ament <
>>> > johndam...@apache.org
>>> > > >
>>> > > > > > wrote:
>>> > > > > >
>>> > > > > >> Arthur,
>>> > > > > >>
>>> > > > > >> Yes, exactly.  If you can get a script like that together, or
>>> tell
>>> > > me
>>> > > > > what
>>> > > > > >> the equivalent of the build would be, I can get it running
>>> into a
>>> > > > build
>>> > > > > >> chain so that we finally have ariatosca.incubator.apache.org
>>> as
>>> > our
>>> > > > > >> website.
>>> > > > > >>
>>> > > > > >> John
>>> > > > > >>
>>> > > > > >> On Thu, Jun 22, 2017 at 5:12 AM Arthur Berezin <
>>> > > art...@gigaspaces.com
>>> > > > >
>>> > > > > >> wrote:
>>> > > > > >>
>>> > > > > >> > Thanks, John, I've pushed an update to aria-tosca-website
>>> last
>>> > > week
>>> > > > > and
>>> > > > > >> I
>>> > > > > >> > have another major update coming in today.
>>> > > > > >> >
>>> > > > > >> > If I understand correctly, the example script builds a
>>> static
>>> > > > website
>>> > > > > >> and
>>> > > > > >> > then publishes it back to the git repo from which the static
>>> > HTML
>>> > > > > would
>>> > > > > >> get
>>> > > > > >> > served?
>>> > > > > >> >
>>> > > > > >> >
>>> > > > > >> >
>>> > > > > >> >
>>> > > > > >> > On Thu, Jun 22, 2017 at 5:39 AM John D. Ament <
>>> > > > johndam...@apache.org>
>>> > > > > >> > wrote:
>>> > > > > >> >
>>> > > > > >> > > All,
>>> > > > > >> > >
>>> > > > > >> > > Some feedback from today's board meeting.  Its noted that
>>> Aria
>>> > > > Tosca
>>> > > > > >> has
>>> > > > > >> > > been incubating for 10 months and still doesn't have a
>>> website
>>> > > > > hosted
>>> > > > > >> at
>>> > > > > >> > > Apache.  I know Arthur had been doing some work on the
>>> area,
>>> > but
>>> > > > > >> wanted
>>> > > > > >> > to
>>> > > > > >> > > see if the current code in the website repo was ready to
>>> go?
>>> > > > > >> > >
>>> > > > > >> > > If so, would I be able to get a script together similar to
>>> > > > > >> > >
>>> > > https://github.com/apache/incubator/blob/jbake-site/build_site.sh
>>> > > > > >> that
>>> > > > > >> > > does
>>> > > > > >> > > the actual site build?  Obviously replace the bake command
>>> > (from
>>> > > > > >> jbake)
>>> > > > > >> > > with the proper commands to get the website built.
>>> > > > > >> > >
>>> > > > > >> > > John
>>> > > > > >> > >
>>> > > > > >> >
>>> > > > > >>
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>

Re: Website ready for builds?

[John D. Ament]

Arthur,

I setup a build job.  Looks like we're good.

https://builds.apache.org/view/A-D/view/AriaTosca/job/AriaTosca%20Website/

I'm going to commit the script changes and open an infra ticket to setup
the website.

John

On Thu, Jun 22, 2017 at 10:07 AM Arthur Berezin <art...@gigaspaces.com>
wrote:

> Yes, it shouldn't be a problem.
>
> On Thu, Jun 22, 2017 at 5:04 PM John D. Ament <john.d.am...@gmail.com>
> wrote:
>
> > Arthur,
> >
> > Can the domain be donated to the ASF?
> >
> > John
> >
> > On Thu, Jun 22, 2017 at 10:03 AM Arthur Berezin <art...@gigaspaces.com>
> > wrote:
> >
> > > Once this is done, I'll redirect the existing domain
> > http://ariatosca.org/
> > > to
> > > our new ASF homepage
> > >
> > > On Thu, Jun 22, 2017 at 4:56 PM Arthur Berezin <art...@gigaspaces.com>
> > > wrote:
> > >
> > > > The build command for Jekyll should be:
> > > > bundle exec Jekyll build --destination $WORKDIR $WORKDIR
> > > >
> > > > I added the build script to the website repo and added the Jekyll
> > > command,
> > > > it assumes that all dependencies are already installed and it's a
> > little
> > > > challenge to test this
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-ariatosca-website/blob/master/build_site.sh
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Thu, Jun 22, 2017 at 3:11 PM John D. Ament <johndam...@apache.org
> >
> > > > wrote:
> > > >
> > > >> Arthur,
> > > >>
> > > >> Yes, exactly.  If you can get a script like that together, or tell
> me
> > > what
> > > >> the equivalent of the build would be, I can get it running into a
> > build
> > > >> chain so that we finally have ariatosca.incubator.apache.org as our
> > > >> website.
> > > >>
> > > >> John
> > > >>
> > > >> On Thu, Jun 22, 2017 at 5:12 AM Arthur Berezin <
> art...@gigaspaces.com
> > >
> > > >> wrote:
> > > >>
> > > >> > Thanks, John, I've pushed an update to aria-tosca-website last
> week
> > > and
> > > >> I
> > > >> > have another major update coming in today.
> > > >> >
> > > >> > If I understand correctly, the example script builds a static
> > website
> > > >> and
> > > >> > then publishes it back to the git repo from which the static HTML
> > > would
> > > >> get
> > > >> > served?
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > On Thu, Jun 22, 2017 at 5:39 AM John D. Ament <
> > johndam...@apache.org>
> > > >> > wrote:
> > > >> >
> > > >> > > All,
> > > >> > >
> > > >> > > Some feedback from today's board meeting.  Its noted that Aria
> > Tosca
> > > >> has
> > > >> > > been incubating for 10 months and still doesn't have a website
> > > hosted
> > > >> at
> > > >> > > Apache.  I know Arthur had been doing some work on the area, but
> > > >> wanted
> > > >> > to
> > > >> > > see if the current code in the website repo was ready to go?
> > > >> > >
> > > >> > > If so, would I be able to get a script together similar to
> > > >> > >
> https://github.com/apache/incubator/blob/jbake-site/build_site.sh
> > > >> that
> > > >> > > does
> > > >> > > the actual site build?  Obviously replace the bake command (from
> > > >> jbake)
> > > >> > > with the proper commands to get the website built.
> > > >> > >
> > > >> > > John
> > > >> > >
> > > >> >
> > > >>
> > > >
> > >
> >
>

Re: A few questions about creating a release

[John D. Ament]

Keeping old versions at external repos is fine, no issue with us (but if
they can be explained as non-ASF even better).

Thanks for fixing the package name.

On Thu, Jun 22, 2017 at 10:26 AM Arthur Berezin 
wrote:

> btw, as we already have outdated packages on Pypi, I've asked +Limor
> Shemesh
>  to remove old packages so that we only have new ASF
> packages available on Pypi to avoid confusion.
>
>
> On Thu, Jun 22, 2017 at 5:22 PM Arthur Berezin 
> wrote:
>
> > On Tue, Jun 20, 2017 at 12:26 PM Ran Ziv  wrote:
> >
> >> Bumping this one more time, and also copying this to the legal mailing
> >> list. I'm not 100% sure that's the place for it, but perhaps someone
> there
> >> might be able to help.
> >>
> >> Thanks
> >>
> >> On Wed, Jun 14, 2017 at 6:17 PM, Ran Ziv  wrote:
> >>
> >> > Bumping this as well.
> >> >
> >> > On Mon, Jun 5, 2017 at 5:08 PM, Ran Ziv  wrote:
> >> >
> >> >> Hi Suneel, John,
> >> >>
> >> >> I have a few quick questions about creating a release for an
> incubator
> >> >> project:
> >> >>
> >> >>
> >> >> 1) According to these links: 1
> >> >> <
> >>
> http://incubator.apache.org/guides/releasemanagement.html#podling-constraints
> >> >
> >> >>  2
> >> >> <
> >> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases>
> >> >> Incubating projects must have "Incubating" in the "final file name".
> I
> >> >> might be missing something, but I assume the meaning is the final
> >> tarball
> >> >> (source distribution) or wheel (binary distribution) file.
> >> >> This is unconventional and not compatible with PyPI - and indeed it
> >> seems
> >> >> like other Apache Incubator projects don't adhere to it (see Airflow
> >> >> ).
> >> >> Am I missing something, or perhaps this is simply not relevant for
> >> Python
> >> >> projects?
> >> >>
> >> >>
> >> >> 2) According to this
> >> >> <
> >> http://www.apache.org/legal/release-policy.html#licensing-documentation
> >,
> >> >> LICENSE and NOTICE must be located in all release packages, including
> >> >> binary distributions. I've looked much into this and I couldn't find
> a
> >> good
> >> >> way of bundling these files inside the wheel format - except for
> >> manually
> >> >> pushing them inside after creating the wheel perhaps.
> >> >> The section speaks of a "customary location for licensing materials"
> -
> >> >> However, for the wheel format there's no such "customary location".
> >> >> I tried looking into what other Apache projects do about this, and
> >> indeed
> >> >> the libcloud project doesn't have these files in their wheel package
> >> (also,
> >> >> relating to my other mail with licensing questions - they also seem
> to
> >> be
> >> >> using PyLint).
> >> >> Is this acceptable for  ARIA as well, or should we manually place
> these
> >> >> files inside the wheel package - Or perhaps there's a different way
> to
> >> do
> >> >> this I have not found?
> >> >>
> >> >>
> >> >> 3) What should be the project name on PyPI (when it goes up there)?
> >> Does
> >> >> it have to be named "apache-ariatosca"? Can it be simply named
> "aria"?
> >> >> It can often get confusing when projects are named one thing on PyPI
> >> and
> >> >> yet the main package is named otherwise; Plus, it's simply more
> >> >> straightforward to do "pip install aria" :)
> >> >> I haven't seen any explicit rules about this, but I assumed it's
> better
> >> >> to ask.
> >>
> >
> > My understanding is that "Apahce" should be included as part of the
> > package name, and since the name of the project is AriaTosca we should
> > stick to the project name so "apache-ariatosca" should work.
> > wrt to cli "aria" would be much better ux, but we can also add an alias
> > from "aria" to "ariatosca" for consistency.
> >
> >
> >
> >> >>
> >> >>
> >> >> Thanks
> >> >>
> >> >>
> >> >
> >>
> >
>

How the website build works

[John D. Ament]

All,

Just wanted to give an update on how the website build works.

ASF uses a few different technologies.  The latest is "gitwcsub" which
looks for changes in a git repo and publishes those as a static website.
To do that you can use any technology to build the website, but use some
known naming conventions for the website structure.

Master is used for the source code of the website.  The build_site.sh
builds the actual static content into the HTML/JS using jekyll.  I borrowed
the script structure from OpenWhisk who is using the same exact idea on
jekyll.  The build does pull in rvm and has to use a separate environment
for jekyll gems.

The jenkins job that does the polling for commits in master is at
https://builds.apache.org/view/A-D/view/AriaTosca/job/AriaTosca%20Website/ .
 it runs on special nodes that have permissions to push to your
repositories.  I've created an asf-site branch that you should not commit
to directly.

I've created an infra ticket to get the website up and running, so
hopefully within a few hours http://ariatosca.incubator.apache.org will
start working.

John

Re: Website ready for builds?

[John D. Ament]

That should start working after infra does
https://issues.apache.org/jira/browse/INFRA-14420

John

On Thu, Jun 22, 2017 at 10:39 AM Arthur Berezin <art...@gigaspaces.com>
wrote:

> I'm getting 404 on http://ariatosca.incubator.apache.org/
> I assume that now infra team needs to redirect $URL to the site?
>
> On Thu, Jun 22, 2017 at 5:28 PM John D. Ament <johndam...@apache.org>
> wrote:
>
> > Arthur,
> >
> > I setup a build job.  Looks like we're good.
> >
> >
> https://builds.apache.org/view/A-D/view/AriaTosca/job/AriaTosca%20Website/
> >
> > I'm going to commit the script changes and open an infra ticket to setup
> > the website.
> >
> > John
> >
> > On Thu, Jun 22, 2017 at 10:07 AM Arthur Berezin <art...@gigaspaces.com>
> > wrote:
> >
> > > Yes, it shouldn't be a problem.
> > >
> > > On Thu, Jun 22, 2017 at 5:04 PM John D. Ament <john.d.am...@gmail.com>
> > > wrote:
> > >
> > > > Arthur,
> > > >
> > > > Can the domain be donated to the ASF?
> > > >
> > > > John
> > > >
> > > > On Thu, Jun 22, 2017 at 10:03 AM Arthur Berezin <
> art...@gigaspaces.com
> > >
> > > > wrote:
> > > >
> > > > > Once this is done, I'll redirect the existing domain
> > > > http://ariatosca.org/
> > > > > to
> > > > > our new ASF homepage
> > > > >
> > > > > On Thu, Jun 22, 2017 at 4:56 PM Arthur Berezin <
> > art...@gigaspaces.com>
> > > > > wrote:
> > > > >
> > > > > > The build command for Jekyll should be:
> > > > > > bundle exec Jekyll build --destination $WORKDIR $WORKDIR
> > > > > >
> > > > > > I added the build script to the website repo and added the Jekyll
> > > > > command,
> > > > > > it assumes that all dependencies are already installed and it's a
> > > > little
> > > > > > challenge to test this
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-ariatosca-website/blob/master/build_site.sh
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, Jun 22, 2017 at 3:11 PM John D. Ament <
> > johndam...@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > >> Arthur,
> > > > > >>
> > > > > >> Yes, exactly.  If you can get a script like that together, or
> tell
> > > me
> > > > > what
> > > > > >> the equivalent of the build would be, I can get it running into
> a
> > > > build
> > > > > >> chain so that we finally have ariatosca.incubator.apache.org as
> > our
> > > > > >> website.
> > > > > >>
> > > > > >> John
> > > > > >>
> > > > > >> On Thu, Jun 22, 2017 at 5:12 AM Arthur Berezin <
> > > art...@gigaspaces.com
> > > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Thanks, John, I've pushed an update to aria-tosca-website last
> > > week
> > > > > and
> > > > > >> I
> > > > > >> > have another major update coming in today.
> > > > > >> >
> > > > > >> > If I understand correctly, the example script builds a static
> > > > website
> > > > > >> and
> > > > > >> > then publishes it back to the git repo from which the static
> > HTML
> > > > > would
> > > > > >> get
> > > > > >> > served?
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > On Thu, Jun 22, 2017 at 5:39 AM John D. Ament <
> > > > johndam...@apache.org>
> > > > > >> > wrote:
> > > > > >> >
> > > > > >> > > All,
> > > > > >> > >
> > > > > >> > > Some feedback from today's board meeting.  Its noted that
> Aria
> > > > Tosca
> > > > > >> has
> > > > > >> > > been incubating for 10 months and still doesn't have a
> website
> > > > > hosted
> > > > > >> at
> > > > > >> > > Apache.  I know Arthur had been doing some work on the area,
> > but
> > > > > >> wanted
> > > > > >> > to
> > > > > >> > > see if the current code in the website repo was ready to go?
> > > > > >> > >
> > > > > >> > > If so, would I be able to get a script together similar to
> > > > > >> > >
> > > https://github.com/apache/incubator/blob/jbake-site/build_site.sh
> > > > > >> that
> > > > > >> > > does
> > > > > >> > > the actual site build?  Obviously replace the bake command
> > (from
> > > > > >> jbake)
> > > > > >> > > with the proper commands to get the website built.
> > > > > >> > >
> > > > > >> > > John
> > > > > >> > >
> > > > > >> >
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Moving to 100% GitHub

[John D. Ament]

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>
> Cloudify | http://getcloudify.org
> <
> http://getcloudify.org?utm_source=signaturesatori_medium=email_campaign=general_signature
> >
>
> 
> 
>    
> [image: Azure Webinar]
> <
> http://getcloudify.org/webinars/Azure-plugin-for-cloudify-webinar.html?utm_source=signaturesatori_medium=email_campaign=general_signature
> >
>

Re: Renaming Old ARIA Repos

[John D. Ament]

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: Moving to 100% GitHub

[John D. Ament]

On Sun, May 21, 2017 at 7:51 AM Ran Ziv <r...@gigaspaces.com> 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 <johndam...@apache.org>
> 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 <t...@gigaspaces.com> 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://twitter.com/CloudifySource>
> > > <https://www.linkedin.com/groups/8467478>
> > > <https://github.com/cloudify-cosmo>   <
> 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
> > > >
> > >
> >
>

[NOTICE] Managing Podling Rosters

[John D. Ament]

Podlings,

I wanted to raise a point to all, hence the direct emails.

The Whimsy PMC has put together a roster tool for managing the committers
in a podling.  Rather than managing the committer list in your status file,
this will keep track and make sure we list out everyone's valid IDs.

If you haven't accessed it, it can be found at
https://whimsy.apache.org/roster/ppmc/

The Incubator guide has been updated to reflect this
http://incubator.apache.org/guides/ppmc.html#podling+rosters

Please reach out if you have any questions.

John

Re: ARIA dependencies License issues

[John D. Ament]

Ran,

I believe the reason you're not getting a response is that this isn't the
right list to bring it up.  I can provide some insight, but ultimately you
need to get some legal input (from legal-discuss)

- Code formatting shouldn't be an issue, since its not required for the
execution of the code.
- Paramiko would be an issue.  I would not include it as a dependency.

John

On Wed, Jun 14, 2017 at 11:17 AM Ran Ziv  wrote:

> Bumping this again, still waiting for answers on these issues.
>
> On Sun, Jun 4, 2017 at 3:02 PM, Ran Ziv  wrote:
>
> > Hi,
> >
> > I went over all of ARIA's dependencies (including recursive dependencies)
> > and validated them against the Apache allowed licenses
> > .
> > We've done this before and found no issues, but this time two libraries
> > came up as a possible problem. I have a few theories about how this might
> > have happened, but what's more important is to understand what we can do
> > about it.
> >
> > John, Suneel - I was hoping you might be able to answer some of the legal
> > questions / suggestions I've made below. If not, please advise where I
> > might be able to get answers for those.
> >
> >
> > The first package is PyLint (GPL2.0) - This is the tool we use for
> > validating our Python code format. This is only relevant for development
> > purposes, and would not be packaged with ARIA - not even in the source
> > distribution format.
> > It is installed from the tests/requirements.txt file, and is used by tox
> > on CIs or manually by developers.
> > I'm not sure if this is a problem from Apache's perspective - i'd assume
> > it shouldn't be, but if it is we could supposedly simply work with a
> > different tool for this.
> >
> >
> > The more serious issue is with the Paramiko package (LGPL2.1) - Paramiko
> > is the native python implementation for SSH, and is widely used in Python
> > ecosystem - including in Fabric, which is the library ARIA uses for
> remote
> > execution in the execution-plugin.
> > I believe the main reason we haven't noticed this so far is because in
> the
> > past we only checked for non-recursive dependencies - and Fabric is
> > licensed under BSD-2-clause, which is allowed by Apache.
> >
> > Since ARIA doesn't use Paramiko directly (but only via Fabric), this
> might
> > be considered ok.
> > Otherwise, we have few other options:
> >
> > I'm not completely clear about what constitutes as "included packages" -
> > When we will make a release, we'll distribute a source and binary
> packages
> > of ARIA, but no packages which actually contain any dependencies code -
> > those will be installed separately (e.g. from PyPI).
> >
> > Assuming this is not enough to claim that these packages are "not
> > included" with ARIA, we could remove Fabric (and thereby Paramiko) from
> > ARIA's dependencies, but leave the code using them inside - This way,
> when
> > a user installs ARIA, they won't automatically receive any
> > non-ASF-sanctioned dependency code, and ARIA will work but without any
> > remote execution capabilities - and all that would be required from the
> > user to add these capabilities is to manually install the Fabric library.
> > This way, Fabric is treated like an extension or a plugin, so I'd like to
> > think this is something acceptable according to Apache's legal
> constraints.
> >
> > If this too is not acceptable, because ARIA will still have references to
> > Fabric in the code (despite Fabric not getting installed), then perhaps
> we
> > could extract the referencing code as well into a separate package which
> > lives outside of ASF, and users would have to install this separate
> package
> > to be able to use the remote execution capabilities.
> >
> >
> > Finally, if none of my suggestions above pans out, I'd suggest we
> > temporarily remove the remote execution capabilities, aim for an ARIA
> > release with local capabilities only, and try to figure a workaround for
> > the remote execution at a later date.
> >
> >
> > Thanks,
> > Ran.
> >
> >
>

Re: Working towards Release 1

[John D. Ament]

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: Podling Report Reminder - September 2017

[John D. Ament]

All,

Just a reminder that our report is due.  Please take a look, hopefully
someone can step up to do it.

John

On Mon, Sep 4, 2017 at 7:43 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 September 2017, 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, September 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.
>
> 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/September2017
>
> 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
>

Planning to remove rosters from active podlings

[John D. Ament]

All,

This coming weekend (9/29) I plan to remove the roster sections from all
podling status pages.

Podling rosters are meant to be managed in Whimsy.  The roster in the
status page is redundant and end up out of sync.  In place of the roster, I
will be adding a link automatically to all podling rosters.

John

Re: ASF Slack Access and Write Permissions to the Wiki

[John D. Ament]

Miguel,

To get you set up on JIRA and Confluence, we'll need to know your username.

John

On Mon, Nov 27, 2017 at 12:23 PM Thomas Nadeau <tnadeaua...@gmail.com>
wrote:

>
> Sorry by “apache ID” I meant “jira login” below.  I think Miguel
> looking for wiki and Slack access
> only.  Vish ran into the same issue earlier with wiki access, but in his
> case permissions
> vanished after he did have write access to the wiki.
>
> —Tom
>
>
> > On Nov 27, 2017, at 12:21 PM, John D. Ament <johndam...@apache.org>
> wrote:
> >
> > Hi,
> >
> > I saw your email to general@incubator.  I'm not sure what your goal
> is.  Do
> > you want access to the AriaTosca wiki/JIRA?  Or the incubator wide
> > wiki/JIRA?
> >
> > Note that apache.org emails are only given to committers.
> >
> > John
> >
> > On Mon, Nov 27, 2017 at 12:07 PM Miguel Angel Jimenez Achinte <
> > mig...@rigiresearch.com> wrote:
> >
> >> Thank you Tom. I was reading about the Apache email account and
> >> wasn't sure if I should contact the infrastructure team. I'll send the
> >> email.
> >>
> >> Miguel
> >>
> >> --
> >> Miguel Jimenez, PhD student
> >> Department of Computer Science
> >> University of Victoria
> >> Engineering/Computer Science Building (ECS), Room 412
> >> Victoria, BC
> >> V8W 3p6 Canada
> >>
> >> On Mon, Nov 27, 2017 at 9:04 AM, Thomas Nadeau <tnadeaua...@gmail.com>
> >> wrote:
> >>
> >>>
> >>>Miguel asked about getting access to ASF Slack at the
> >>> grooming call this morning, so I thought I’d send this to the entire
> >>> list.
> >>>
> >>>In order to gain access, please send email to
> >>> gene...@incubator.apache.org
> >>> asking for write permissions on your Apache ID for the wiki/jira
> >>> as well as access to the Slack channel.
> >>>
> >>>—Tom
> >>>
> >>>
> >>>
> >>>
> >>
>
>

Re: ASF Slack Access and Write Permissions to the Wiki

[John D. Ament]

I've given you both access to confluence.  I added MIguel as a contributor
in JIRA, Vish you were already listed as a contributor.

On Mon, Nov 27, 2017 at 1:19 PM Vishwanath Jayaraman <
vishwana...@hotmail.com> wrote:

> John,
>
>  My username is vishwanathj and associated email address is
> vishwana...@hotmail.com.
>
> I need edit access to confuence/wiki and permissions in JIRA to be able to
> change issue states from Open->Progress->resolved, etc.
>
> Thanks in advance for all your help.
>
> Vish
>
>
> 
> From: John D. Ament <johndam...@apache.org>
> Sent: Monday, November 27, 2017 12:13 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: ASF Slack Access and Write Permissions to the Wiki
>
> Miguel,
>
> To get you set up on JIRA and Confluence, we'll need to know your username.
>
> John
>
> On Mon, Nov 27, 2017 at 12:23 PM Thomas Nadeau <tnadeaua...@gmail.com>
> wrote:
>
> >
> > Sorry by “apache ID” I meant “jira login” below.  I think Miguel
> > looking for wiki and Slack access
> > only.  Vish ran into the same issue earlier with wiki access, but in his
> > case permissions
> > vanished after he did have write access to the wiki.
> >
> > —Tom
> >
> >
> > > On Nov 27, 2017, at 12:21 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> > >
> > > Hi,
> > >
> > > I saw your email to general@incubator.  I'm not sure what your goal
> > is.  Do
> > > you want access to the AriaTosca wiki/JIRA?  Or the incubator wide
> > > wiki/JIRA?
> > >
> > > Note that apache.org emails are only given to committers.
> > >
> > > John
> > >
> > > On Mon, Nov 27, 2017 at 12:07 PM Miguel Angel Jimenez Achinte <
> > > mig...@rigiresearch.com> wrote:
> > >
> > >> Thank you Tom. I was reading about the Apache email account and
> > >> wasn't sure if I should contact the infrastructure team. I'll send the
> > >> email.
> > >>
> > >> Miguel
> > >>
> > >> --
> > >> Miguel Jimenez, PhD student
> > >> Department of Computer Science
> > >> University of Victoria
> > >> Engineering/Computer Science Building (ECS), Room 412
> > >> Victoria, BC
> > >> V8W 3p6 Canada
> > >>
> > >> On Mon, Nov 27, 2017 at 9:04 AM, Thomas Nadeau <tnadeaua...@gmail.com
> >
> > >> wrote:
> > >>
> > >>>
> > >>>Miguel asked about getting access to ASF Slack at the
> > >>> grooming call this morning, so I thought I’d send this to the entire
> > >>> list.
> > >>>
> > >>>In order to gain access, please send email to
> > >>> gene...@incubator.apache.org
> > >>> asking for write permissions on your Apache ID for the wiki/jira
> > >>> as well as access to the Slack channel.
> > >>>
> > >>>—Tom
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> >
> >
>

Re: ASF Slack Access and Write Permissions to the Wiki

[John D. Ament]

Hi,

I saw your email to general@incubator.  I'm not sure what your goal is.  Do
you want access to the AriaTosca wiki/JIRA?  Or the incubator wide
wiki/JIRA?

Note that apache.org emails are only given to committers.

John

On Mon, Nov 27, 2017 at 12:07 PM Miguel Angel Jimenez Achinte <
mig...@rigiresearch.com> wrote:

> Thank you Tom. I was reading about the Apache email account and
> wasn't sure if I should contact the infrastructure team. I'll send the
> email.
>
> Miguel
>
> --
> Miguel Jimenez, PhD student
> Department of Computer Science
> University of Victoria
> Engineering/Computer Science Building (ECS), Room 412
> Victoria, BC
> V8W 3p6 Canada
>
> On Mon, Nov 27, 2017 at 9:04 AM, Thomas Nadeau 
> wrote:
>
> >
> > Miguel asked about getting access to ASF Slack at the
> > grooming call this morning, so I thought I’d send this to the entire
> > list.
> >
> > In order to gain access, please send email to
> > gene...@incubator.apache.org
> > asking for write permissions on your Apache ID for the wiki/jira
> > as well as access to the Slack channel.
> >
> > —Tom
> >
> >
> >
> >
>

Re: ASF Slack Access and Write Permissions to the Wiki

[John D. Ament]

Requested -> https://issues.apache.org/jira/browse/INFRA-15566


On Mon, Nov 27, 2017 at 1:50 PM Tal Liron <t...@cloudify.co> wrote:

> I see no harm in giving them that permission.
>
> On Mon, Nov 27, 2017 at 12:44 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > I think I see the issue.  In the JIRA permission scheme, contributors can
> > resolve and close issues, but not transition them.  Are we in agreement
> > that contributors should be able to transition issues?
> >
> > On Mon, Nov 27, 2017 at 1:41 PM Thomas Nadeau <tnadeaua...@gmail.com>
> > wrote:
> >
> > > which issue?
> > >
> > > > On Nov 27, 2017, at 1:33 PM, Vishwanath Jayaraman <
> > > vishwana...@hotmail.com> wrote:
> > > >
> > > > Thanks John.
> > > > Is there a reason why I am not able to edit the state of a Jira item
> > > assigned to me?
> > > >
> > > >
> > > > Sent from my iPhone
> > > >
> > > > On Nov 27, 2017, at 12:25 PM, John D. Ament <johndam...@apache.org
> > > <mailto:johndam...@apache.org>> wrote:
> > > >
> > > > I've given you both access to confluence.  I added MIguel as a
> > > contributor
> > > > in JIRA, Vish you were already listed as a contributor.
> > > >
> > > > On Mon, Nov 27, 2017 at 1:19 PM Vishwanath Jayaraman <
> > > > vishwana...@hotmail.com<mailto:vishwana...@hotmail.com>> wrote:
> > > >
> > > > John,
> > > >
> > > > My username is vishwanathj and associated email address is
> > > > vishwana...@hotmail.com<mailto:vishwana...@hotmail.com>.
> > > >
> > > > I need edit access to confuence/wiki and permissions in JIRA to be
> able
> > > to
> > > > change issue states from Open->Progress->resolved, etc.
> > > >
> > > > Thanks in advance for all your help.
> > > >
> > > > Vish
> > > >
> > > >
> > > > 
> > > > From: John D. Ament <johndam...@apache.org > johndam...@apache.org
> > > >>
> > > > Sent: Monday, November 27, 2017 12:13 PM
> > > > To: dev@ariatosca.incubator.apache.org > > dev@ariatosca.incubator.apache.org>
> > > > Subject: Re: ASF Slack Access and Write Permissions to the Wiki
> > > >
> > > > Miguel,
> > > >
> > > > To get you set up on JIRA and Confluence, we'll need to know your
> > > username.
> > > >
> > > > John
> > > >
> > > > On Mon, Nov 27, 2017 at 12:23 PM Thomas Nadeau <
> tnadeaua...@gmail.com
> > > <mailto:tnadeaua...@gmail.com>>
> > > > wrote:
> > > >
> > > >
> > > >   Sorry by “apache ID” I meant “jira login” below.  I think
> Miguel
> > > > looking for wiki and Slack access
> > > > only.  Vish ran into the same issue earlier with wiki access, but in
> > his
> > > > case permissions
> > > > vanished after he did have write access to the wiki.
> > > >
> > > >   —Tom
> > > >
> > > >
> > > > On Nov 27, 2017, at 12:21 PM, John D. Ament <johndam...@apache.org
> > > <mailto:johndam...@apache.org>>
> > > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I saw your email to general@incubator.  I'm not sure what your goal
> > > > is.  Do
> > > > you want access to the AriaTosca wiki/JIRA?  Or the incubator wide
> > > > wiki/JIRA?
> > > >
> > > > Note that apache.org<http://apache.org> emails are only given to
> > > committers.
> > > >
> > > > John
> > > >
> > > > On Mon, Nov 27, 2017 at 12:07 PM Miguel Angel Jimenez Achinte <
> > > > mig...@rigiresearch.com<mailto:mig...@rigiresearch.com>> wrote:
> > > >
> > > > Thank you Tom. I was reading about the Apache email account and
> > > > wasn't sure if I should contact the infrastructure team. I'll send
> the
> > > > email.
> > > >
> > > > Miguel
> > > >
> > > > --
> > > > Miguel Jimenez, PhD student
> > > > Department of Computer Science
> > > > University of Victoria
> > > > Engineering/Computer Science Building (ECS), Room 412
> > > > Victoria, BC
> > > > V8W 3p6 Canada
> > > >
> > > > On Mon, Nov 27, 2017 at 9:04 AM, Thomas Nadeau <
> tnadeaua...@gmail.com
> > > <mailto:tnadeaua...@gmail.com>
> > > >
> > > > wrote:
> > > >
> > > >
> > > >  Miguel asked about getting access to ASF Slack at the
> > > > grooming call this morning, so I thought I’d send this to the entire
> > > > list.
> > > >
> > > >  In order to gain access, please send email to
> > > > gene...@incubator.apache.org<mailto:gene...@incubator.apache.org>
> > > > asking for write permissions on your Apache ID for the wiki/jira
> > > > as well as access to the Slack channel.
> > > >
> > > >  —Tom
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
>

Re: ASF Slack Access and Write Permissions to the Wiki

[John D. Ament]

Glad its working! And if there's anyone to thank, its our crack infra
team.

On Nov 27, 2017 2:57 PM, "Vishwanath Jayaraman" <vishwana...@hotmail.com>
wrote:

John,

 I am now able to see the edit button on the WIKI page and also able to
change state of the JIRA item.

That was fast, thanks a lot for all your help.


Vish


________
From: John D. Ament <johndam...@apache.org>
Sent: Monday, November 27, 2017 1:52 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: ASF Slack Access and Write Permissions to the Wiki

Vish can you try now?

On Nov 27, 2017 2:28 PM, "Thomas Nadeau" <tnadeaua...@gmail.com> wrote:

> +1
>
> > On Nov 27, 2017, at 1:44 PM, John D. Ament <johndam...@apache.org>
> wrote:
> >
> > I think I see the issue.  In the JIRA permission scheme, contributors
can
> > resolve and close issues, but not transition them.  Are we in agreement
> > that contributors should be able to transition issues?
> >
> > On Mon, Nov 27, 2017 at 1:41 PM Thomas Nadeau <tnadeaua...@gmail.com>
> wrote:
> >
> >> which issue?
> >>
> >>> On Nov 27, 2017, at 1:33 PM, Vishwanath Jayaraman <
> >> vishwana...@hotmail.com> wrote:
> >>>
> >>> Thanks John.
> >>> Is there a reason why I am not able to edit the state of a Jira item
> >> assigned to me?
> >>>
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On Nov 27, 2017, at 12:25 PM, John D. Ament <johndam...@apache.org
> >> <mailto:johndam...@apache.org>> wrote:
> >>>
> >>> I've given you both access to confluence.  I added MIguel as a
> >> contributor
> >>> in JIRA, Vish you were already listed as a contributor.
> >>>
> >>> On Mon, Nov 27, 2017 at 1:19 PM Vishwanath Jayaraman <
> >>> vishwana...@hotmail.com<mailto:vishwana...@hotmail.com>> wrote:
> >>>
> >>> John,
> >>>
> >>> My username is vishwanathj and associated email address is
> >>> vishwana...@hotmail.com<mailto:vishwana...@hotmail.com>.
> >>>
> >>> I need edit access to confuence/wiki and permissions in JIRA to be
able
> >> to
> >>> change issue states from Open->Progress->resolved, etc.
> >>>
> >>> Thanks in advance for all your help.
> >>>
> >>> Vish
> >>>
> >>>
> >>> 
> >>> From: John D. Ament <johndam...@apache.org johndam...@apache.org
> >>>>
> >>> Sent: Monday, November 27, 2017 12:13 PM
> >>> To: dev@ariatosca.incubator.apache.org >> dev@ariatosca.incubator.apache.org>
> >>> Subject: Re: ASF Slack Access and Write Permissions to the Wiki
> >>>
> >>> Miguel,
> >>>
> >>> To get you set up on JIRA and Confluence, we'll need to know your
> >> username.
> >>>
> >>> John
> >>>
> >>> On Mon, Nov 27, 2017 at 12:23 PM Thomas Nadeau <tnadeaua...@gmail.com
> >> <mailto:tnadeaua...@gmail.com>>
> >>> wrote:
> >>>
> >>>
> >>>  Sorry by “apache ID” I meant “jira login” below.  I think Miguel
> >>> looking for wiki and Slack access
> >>> only.  Vish ran into the same issue earlier with wiki access, but in
> his
> >>> case permissions
> >>> vanished after he did have write access to the wiki.
> >>>
> >>>  —Tom
> >>>
> >>>
> >>> On Nov 27, 2017, at 12:21 PM, John D. Ament <johndam...@apache.org
> >> <mailto:johndam...@apache.org>>
> >>> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I saw your email to general@incubator.  I'm not sure what your goal
> >>> is.  Do
> >>> you want access to the AriaTosca wiki/JIRA?  Or the incubator wide
> >>> wiki/JIRA?
> >>>
> >>> Note that apache.org<http://apache.org> emails are only given to
> >> committers.
> >>>
> >>> John
> >>>
> >>> On Mon, Nov 27, 2017 at 12:07 PM Miguel Angel Jimenez Achinte <
> >>> mig...@rigiresearch.com<mailto:mig...@rigiresearch.com>> wrote:
> >>>
> >>> Thank you Tom. I was reading about the Apache email account and
> >>> wasn't sure if I should contact the infrastructure team. I'll send the
> >>> email.
> >>>
> >>> Miguel
> >>>
> >>> --
> >>> Miguel Jimenez, PhD student
> >>> Department of Computer Science
> >>> University of Victoria
> >>> Engineering/Computer Science Building (ECS), Room 412
> >>> Victoria, BC
> >>> V8W 3p6 Canada
> >>>
> >>> On Mon, Nov 27, 2017 at 9:04 AM, Thomas Nadeau <tnadeaua...@gmail.com
> >> <mailto:tnadeaua...@gmail.com>
> >>>
> >>> wrote:
> >>>
> >>>
> >>> Miguel asked about getting access to ASF Slack at the
> >>> grooming call this morning, so I thought I’d send this to the entire
> >>> list.
> >>>
> >>> In order to gain access, please send email to
> >>> gene...@incubator.apache.org<mailto:gene...@incubator.apache.org>
> >>> asking for write permissions on your Apache ID for the wiki/jira
> >>> as well as access to the Slack channel.
> >>>
> >>> —Tom
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
>
>

Re: ASF Slack Access and Write Permissions to the Wiki

[John D. Ament]

I think I see the issue.  In the JIRA permission scheme, contributors can
resolve and close issues, but not transition them.  Are we in agreement
that contributors should be able to transition issues?

On Mon, Nov 27, 2017 at 1:41 PM Thomas Nadeau <tnadeaua...@gmail.com> wrote:

> which issue?
>
> > On Nov 27, 2017, at 1:33 PM, Vishwanath Jayaraman <
> vishwana...@hotmail.com> wrote:
> >
> > Thanks John.
> > Is there a reason why I am not able to edit the state of a Jira item
> assigned to me?
> >
> >
> > Sent from my iPhone
> >
> > On Nov 27, 2017, at 12:25 PM, John D. Ament <johndam...@apache.org
> <mailto:johndam...@apache.org>> wrote:
> >
> > I've given you both access to confluence.  I added MIguel as a
> contributor
> > in JIRA, Vish you were already listed as a contributor.
> >
> > On Mon, Nov 27, 2017 at 1:19 PM Vishwanath Jayaraman <
> > vishwana...@hotmail.com<mailto:vishwana...@hotmail.com>> wrote:
> >
> > John,
> >
> > My username is vishwanathj and associated email address is
> > vishwana...@hotmail.com<mailto:vishwana...@hotmail.com>.
> >
> > I need edit access to confuence/wiki and permissions in JIRA to be able
> to
> > change issue states from Open->Progress->resolved, etc.
> >
> > Thanks in advance for all your help.
> >
> > Vish
> >
> >
> > 
> > From: John D. Ament <johndam...@apache.org<mailto:johndam...@apache.org
> >>
> > Sent: Monday, November 27, 2017 12:13 PM
> > To: dev@ariatosca.incubator.apache.org dev@ariatosca.incubator.apache.org>
> > Subject: Re: ASF Slack Access and Write Permissions to the Wiki
> >
> > Miguel,
> >
> > To get you set up on JIRA and Confluence, we'll need to know your
> username.
> >
> > John
> >
> > On Mon, Nov 27, 2017 at 12:23 PM Thomas Nadeau <tnadeaua...@gmail.com
> <mailto:tnadeaua...@gmail.com>>
> > wrote:
> >
> >
> >   Sorry by “apache ID” I meant “jira login” below.  I think Miguel
> > looking for wiki and Slack access
> > only.  Vish ran into the same issue earlier with wiki access, but in his
> > case permissions
> > vanished after he did have write access to the wiki.
> >
> >   —Tom
> >
> >
> > On Nov 27, 2017, at 12:21 PM, John D. Ament <johndam...@apache.org
> <mailto:johndam...@apache.org>>
> > wrote:
> >
> > Hi,
> >
> > I saw your email to general@incubator.  I'm not sure what your goal
> > is.  Do
> > you want access to the AriaTosca wiki/JIRA?  Or the incubator wide
> > wiki/JIRA?
> >
> > Note that apache.org<http://apache.org> emails are only given to
> committers.
> >
> > John
> >
> > On Mon, Nov 27, 2017 at 12:07 PM Miguel Angel Jimenez Achinte <
> > mig...@rigiresearch.com<mailto:mig...@rigiresearch.com>> wrote:
> >
> > Thank you Tom. I was reading about the Apache email account and
> > wasn't sure if I should contact the infrastructure team. I'll send the
> > email.
> >
> > Miguel
> >
> > --
> > Miguel Jimenez, PhD student
> > Department of Computer Science
> > University of Victoria
> > Engineering/Computer Science Building (ECS), Room 412
> > Victoria, BC
> > V8W 3p6 Canada
> >
> > On Mon, Nov 27, 2017 at 9:04 AM, Thomas Nadeau <tnadeaua...@gmail.com
> <mailto:tnadeaua...@gmail.com>
> >
> > wrote:
> >
> >
> >  Miguel asked about getting access to ASF Slack at the
> > grooming call this morning, so I thought I’d send this to the entire
> > list.
> >
> >  In order to gain access, please send email to
> > gene...@incubator.apache.org<mailto:gene...@incubator.apache.org>
> > asking for write permissions on your Apache ID for the wiki/jira
> > as well as access to the Slack channel.
> >
> >  —Tom
> >
> >
> >
> >
> >
> >
> >
> >
>
>

Re: ASF Slack Access and Write Permissions to the Wiki

[John D. Ament]

Vish can you try now?

On Nov 27, 2017 2:28 PM, "Thomas Nadeau" <tnadeaua...@gmail.com> wrote:

> +1
>
> > On Nov 27, 2017, at 1:44 PM, John D. Ament <johndam...@apache.org>
> wrote:
> >
> > I think I see the issue.  In the JIRA permission scheme, contributors can
> > resolve and close issues, but not transition them.  Are we in agreement
> > that contributors should be able to transition issues?
> >
> > On Mon, Nov 27, 2017 at 1:41 PM Thomas Nadeau <tnadeaua...@gmail.com>
> wrote:
> >
> >> which issue?
> >>
> >>> On Nov 27, 2017, at 1:33 PM, Vishwanath Jayaraman <
> >> vishwana...@hotmail.com> wrote:
> >>>
> >>> Thanks John.
> >>> Is there a reason why I am not able to edit the state of a Jira item
> >> assigned to me?
> >>>
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On Nov 27, 2017, at 12:25 PM, John D. Ament <johndam...@apache.org
> >> <mailto:johndam...@apache.org>> wrote:
> >>>
> >>> I've given you both access to confluence.  I added MIguel as a
> >> contributor
> >>> in JIRA, Vish you were already listed as a contributor.
> >>>
> >>> On Mon, Nov 27, 2017 at 1:19 PM Vishwanath Jayaraman <
> >>> vishwana...@hotmail.com<mailto:vishwana...@hotmail.com>> wrote:
> >>>
> >>> John,
> >>>
> >>> My username is vishwanathj and associated email address is
> >>> vishwana...@hotmail.com<mailto:vishwana...@hotmail.com>.
> >>>
> >>> I need edit access to confuence/wiki and permissions in JIRA to be able
> >> to
> >>> change issue states from Open->Progress->resolved, etc.
> >>>
> >>> Thanks in advance for all your help.
> >>>
> >>> Vish
> >>>
> >>>
> >>> 
> >>> From: John D. Ament <johndam...@apache.org johndam...@apache.org
> >>>>
> >>> Sent: Monday, November 27, 2017 12:13 PM
> >>> To: dev@ariatosca.incubator.apache.org >> dev@ariatosca.incubator.apache.org>
> >>> Subject: Re: ASF Slack Access and Write Permissions to the Wiki
> >>>
> >>> Miguel,
> >>>
> >>> To get you set up on JIRA and Confluence, we'll need to know your
> >> username.
> >>>
> >>> John
> >>>
> >>> On Mon, Nov 27, 2017 at 12:23 PM Thomas Nadeau <tnadeaua...@gmail.com
> >> <mailto:tnadeaua...@gmail.com>>
> >>> wrote:
> >>>
> >>>
> >>>  Sorry by “apache ID” I meant “jira login” below.  I think Miguel
> >>> looking for wiki and Slack access
> >>> only.  Vish ran into the same issue earlier with wiki access, but in
> his
> >>> case permissions
> >>> vanished after he did have write access to the wiki.
> >>>
> >>>  —Tom
> >>>
> >>>
> >>> On Nov 27, 2017, at 12:21 PM, John D. Ament <johndam...@apache.org
> >> <mailto:johndam...@apache.org>>
> >>> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I saw your email to general@incubator.  I'm not sure what your goal
> >>> is.  Do
> >>> you want access to the AriaTosca wiki/JIRA?  Or the incubator wide
> >>> wiki/JIRA?
> >>>
> >>> Note that apache.org<http://apache.org> emails are only given to
> >> committers.
> >>>
> >>> John
> >>>
> >>> On Mon, Nov 27, 2017 at 12:07 PM Miguel Angel Jimenez Achinte <
> >>> mig...@rigiresearch.com<mailto:mig...@rigiresearch.com>> wrote:
> >>>
> >>> Thank you Tom. I was reading about the Apache email account and
> >>> wasn't sure if I should contact the infrastructure team. I'll send the
> >>> email.
> >>>
> >>> Miguel
> >>>
> >>> --
> >>> Miguel Jimenez, PhD student
> >>> Department of Computer Science
> >>> University of Victoria
> >>> Engineering/Computer Science Building (ECS), Room 412
> >>> Victoria, BC
> >>> V8W 3p6 Canada
> >>>
> >>> On Mon, Nov 27, 2017 at 9:04 AM, Thomas Nadeau <tnadeaua...@gmail.com
> >> <mailto:tnadeaua...@gmail.com>
> >>>
> >>> wrote:
> >>>
> >>>
> >>> Miguel asked about getting access to ASF Slack at the
> >>> grooming call this morning, so I thought I’d send this to the entire
> >>> list.
> >>>
> >>> In order to gain access, please send email to
> >>> gene...@incubator.apache.org<mailto:gene...@incubator.apache.org>
> >>> asking for write permissions on your Apache ID for the wiki/jira
> >>> as well as access to the Slack channel.
> >>>
> >>> —Tom
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
>
>

Re: retiring/removal of committers

[John D. Ament]

There is one out.  When a podling graduates, its customary to keep everyone
on.  However, if there are people who are no longer interested in the
project and the project chooses to not include them, its not uncommon that
they be left off the graduation.  They would still be open to be included
later on if they contribute once again.

John

On Wed, Nov 29, 2017 at 4:26 PM Thomas Nadeau  wrote:

>
> I think that is why we were having it - no one knew about Apache’s
> rules around this.
> That seems to settle the matter: once you are in, you are in.
>
> —Tom
>
>
> > On Nov 29, 2017, at 3:42 PM, Suneel Marthi 
> wrote:
> >
> > 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: Podlings reports schedule?

[John D. Ament]

On Mon, Nov 13, 2017 at 2:58 PM Thomas Nadeau  wrote:

>
> Mentors:
>
> I just realized that I overlooked submitting the podling report
> for October, so I looked


Errr, not sure why you believe you overlooked submitting a report.
Podlings submit reports once per quarter.  The last report was due in
September and was received.

On the flip side, you specifically don't owe anything.  The PPMC does.


> around for instructions for how to do this. I was looking for information
> about when/what format the podling reports should be in and found this:
>
> https://incubator.apache.org/guides/ppmc.html <
> https://incubator.apache.org/guides/ppmc.html>
>
> The following link there is broken, I’ve emailed  us...@infra.apache.org
>  to resolve the issue but there is no
> information from there I can get right now.
>

I have no idea why you emailed infra about this.  This is a discussion for
general@incubator.


>
> https://incubator.apache.org/report-groups.txt <
> https://incubator.apache.org/report-groups.txt>
>
>  I found this reference which said to do a PR on the incubator
> site:
>
>
> https://incubator.apache.org/guides/website.html#Edit+your+project+status+page
> <
> https://incubator.apache.org/guides/website.html#Edit+your+project+status+page
> >
>

That's your status page.  Status pages don't maintain reports.


>
> However, I’ve found the previous podling reports here on Jira, so
> should I just edit a page here instead?
>
>
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-09
> <
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-09
> >
>
>
> Is there a specific cadence at which these should be published?
>
>
Quarterly.


>
> Thx,
>
> —Tom
>
>

Re: Jenkins job on ariatosca-website failing after gitbox transition

[John D. Ament]

Ok, so there's a couple of issues.
Jenkins access is limited to those in a certain group, since its a single
jenkins instance for all projects without limited privileges.  Right now I
have access to manage jobs in jenkins, but would be happy to add others who
need it.

The jenkins job is something I set up, based on a cookie cutter I use to
automate website builds (jenkins job configuration for me is like bonsai
trimming).  The job just executes the shell script in the repo.  I just
need to repoint to gitbox to reenable the job, but right now jenkins is
down.  When it comes back I'll get the job going again.

I've assigned myself the infra ticket, please try to avoid sending them
issues that we should be able to fix ourselves (and discussing it on list
helps identify who or what can/should be fixed).

John

On Tue, Dec 5, 2017 at 12:05 PM Thomas Nadeau  wrote:

> i just realized that after the switch to gitbox, pushed PRs to the
> ariatosca-website repo are not triggering the Jenkins job which results in
> the site being re-generated and published to ariatosca.org
>
>
> [5:45]
> so my PR yesterday and @Miguel Jiménez’s from today while merged, are not
> yet reflected
>
>
> smarthi [5:49 PM]
> on other projects like OpenNLP, Flink, Beam etc… there’s a buildbot setup
> that triggers a build and regenerates the website
>
>
> Thomas Nadeau [5:54 PM]
> thats good, but I don't really want to set up a different automation
> trigger/builder if I can help it :sunglasses:
>
>
> [5:54]
> i did look into buildbot earlier before I knew there was an apache infra
> jenkins job setup
>
>
> [5:55]
> I suspect that its just not triggered properly because the triggers need to
> come from github now instead of apache git
>
>
> [5:55]
> so token generator is a one button situation on github, so infra prob needs
> to have a committer generate the token and the replace the old one with
> that
>
>
> smarthi [6:00 PM]
> well u can file Infra ticket to enable buildbot for aria-site
>
>
> Thomas Nadeau [6:04 PM]
> how does one file a ticket?
>
> [6:05]
> just email to infra@apache?
>
>
> smarthi [6:06 PM]
> jira
>
>
> Thomas Nadeau [6:06 PM]
> ah like the gitbox one
>
>
> smarthi [6:07 PM]
> yes
>
>
> Thomas Nadeau [6:08 PM]
> ill fire one up now
>
>
> johndament [6:23 PM]
> i can fix the jenkins job
>

Re: Jenkins job on ariatosca-website failing after gitbox transition

[John D. Ament]

Jenkins is back up, and the website has been built.

John

On Tue, Dec 5, 2017 at 12:13 PM John D. Ament <johndam...@apache.org> wrote:

> Ok, so there's a couple of issues.
> Jenkins access is limited to those in a certain group, since its a single
> jenkins instance for all projects without limited privileges.  Right now I
> have access to manage jobs in jenkins, but would be happy to add others who
> need it.
>
> The jenkins job is something I set up, based on a cookie cutter I use to
> automate website builds (jenkins job configuration for me is like bonsai
> trimming).  The job just executes the shell script in the repo.  I just
> need to repoint to gitbox to reenable the job, but right now jenkins is
> down.  When it comes back I'll get the job going again.
>
> I've assigned myself the infra ticket, please try to avoid sending them
> issues that we should be able to fix ourselves (and discussing it on list
> helps identify who or what can/should be fixed).
>
> John
>
>
> On Tue, Dec 5, 2017 at 12:05 PM Thomas Nadeau <tnadeaua...@gmail.com>
> wrote:
>
>> i just realized that after the switch to gitbox, pushed PRs to the
>> ariatosca-website repo are not triggering the Jenkins job which results in
>> the site being re-generated and published to ariatosca.org
>>
>>
>> [5:45]
>> so my PR yesterday and @Miguel Jiménez’s from today while merged, are not
>> yet reflected
>>
>>
>> smarthi [5:49 PM]
>> on other projects like OpenNLP, Flink, Beam etc… there’s a buildbot setup
>> that triggers a build and regenerates the website
>>
>>
>> Thomas Nadeau [5:54 PM]
>> thats good, but I don't really want to set up a different automation
>> trigger/builder if I can help it :sunglasses:
>>
>>
>> [5:54]
>> i did look into buildbot earlier before I knew there was an apache infra
>> jenkins job setup
>>
>>
>> [5:55]
>> I suspect that its just not triggered properly because the triggers need
>> to
>> come from github now instead of apache git
>>
>>
>> [5:55]
>> so token generator is a one button situation on github, so infra prob
>> needs
>> to have a committer generate the token and the replace the old one with
>> that
>>
>>
>> smarthi [6:00 PM]
>> well u can file Infra ticket to enable buildbot for aria-site
>>
>>
>> Thomas Nadeau [6:04 PM]
>> how does one file a ticket?
>>
>> [6:05]
>> just email to infra@apache?
>>
>>
>> smarthi [6:06 PM]
>> jira
>>
>>
>> Thomas Nadeau [6:06 PM]
>> ah like the gitbox one
>>
>>
>> smarthi [6:07 PM]
>> yes
>>
>>
>> Thomas Nadeau [6:08 PM]
>> ill fire one up now
>>
>>
>> johndament [6:23 PM]
>> i can fix the jenkins job
>>
>

Re: Website Build + Release

[John D. Ament]

Tom,

I don't know how to do this, so I'd recommend someone else jump in to take
care of it.  I would recommend as an immediate step to update the website
with the 0.1.1 release docs to avoid downloading the release on each build.

John

On Thu, Dec 7, 2017 at 5:06 AM Thomas Nadeau <tnad...@apache.org> wrote:

> John,
>
> Can I help you with this or is this something you can do quickly?
>
> --Tom
>
>
> On Wed, Dec 6, 2017 at 10:01 PM, Arthur Berezin <art...@cloudify.co>
> wrote:
>
> > John, +1.
> >
> > Let's update the aria's release process to push  sphynx update on Aria
> > releases.
> >
> > The reason the website is currently pulling the release docs and not the
> > other way around is because we published the docs right after we released
> > 0.1.1 and didn't want to introduce changes in that point in time.
> >
> > Arthur.
> >
> > On Wed, Dec 6, 2017, 16:58 Thomas Nadeau <tnadeaua...@gmail.com> wrote:
> >
> > >
> > >
> > > > On Dec 6, 2017, at 4:40 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> > > >
> > > > Tom,
> > > >
> > > > Based on what I'm seeing, you're getting the current release (0.1.1).
> > > I'm
> > > > not seeing anything that pulls the current master into the site.
> > > >
> > > > I would recommend that we push from the build to the website, rather
> > than
> > > > have the website pull this information in.
> > >
> > > Ok. Ill take a look shortly.
> > >
> > > —Tom
> > >
> > >
> > > >
> > > > John
> > > >
> > > > On Wed, Dec 6, 2017 at 8:59 AM Thomas Nadeau <tnadeaua...@gmail.com>
> > > wrote:
> > > >
> > > >> We use 2 tools to generate the website: Jekyll (html) and spynx
> > (docs),
> > > and
> > > >> both tools generate outputs based on the latest code.
> > > >>
> > > >> --Tom
> > > >>
> > > >>
> > > >> On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament <
> johndam...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> All,
> > > >>>
> > > >>> I'm troubleshooting from yesterday's identified website issues.
> One
> > > >> thing
> > > >>> I noticed is that as a part of the website build, we download our
> > > >> release.
> > > >>> Why is that?
> > > >>>
> > > >>> John
> > > >>>
> > > >>
> > >
> > >
> >
>

Re: AriaTosca December Podling Report

[John D. Ament]

Thomas,

The report was due yesterday.

John

On Thu, Dec 7, 2017 at 2:50 AM Thomas Nadeau  wrote:

> Just to give a little more info than the original sharing link message.
> The mentors
> asked me to share the document with the community that I am using to create
> the next podling report.  This way anyone here can provide inputs/edits. I
> plan on
> submitting this early next Monday, December 11, 2017 at 5PM EST, so please
> get your edits/comments into the document or to me by then.
>
> Cheers,
>
> --Tom
>
>
>
> On Thu, Dec 7, 2017 at 9:47 AM, Thomas Nadeau (via Google Docs) <
> tnadeaua...@gmail.com> wrote:
>
> > tnadeaua...@gmail.com has shared a link to the following document:
> > AriaTosca December Podling Report
> > <
> https://docs.google.com/document/d/1Yg9J-9WD81UjqvwFoc8wek8628RSLzIEZogtVT1HBWg/edit?usp=sharing_eil=5a28f21c
> >
> > Open in Docs
> > <
> https://docs.google.com/document/d/1Yg9J-9WD81UjqvwFoc8wek8628RSLzIEZogtVT1HBWg/edit?usp=sharing_eip=5a28f21c
> >
> > Google Docs: Create and edit documents online.
> > Google Inc. 1600 Amphitheatre Parkway, Mountain View,
> 
> CA 94043, USA
> > <
> https://maps.google.com/?q=1600+Amphitheatre+Parkway,+Mountain+View,+CA+94043,+USA=gmail=g
> >
> > You have received this email because someone shared a document with you
> > from Google Docs. [image: Logo for Google Docs] <
> https://drive.google.com>
> >
>

Re: Time for a new release

[John D. Ament]

No, you just commit the file.  There is no other process.

On Mon, Dec 11, 2017 at 9:06 AM Thomas Nadeau <tnadeaua...@gmail.com> wrote:

>
> Thanks for the pointer.
>
> Is there any sort of pull request process for approvals or are
> these pushes just directly to the master branch?
>
> —Tom
>
>
> > On Dec 9, 2017, at 10:31 AM, John D. Ament <johndam...@apache.org>
> wrote:
> >
> > The SVN repo is
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > So you would just check in your change via SVN.
> >
> > On 2017-12-07 11:22, Thomas Nadeau <tnadeaua...@gmail.com> wrote:
> >> Question about the instructions. It says:
> >>
> >> If this is your first time creating a release for ARIA, make sure to
> update
> >> the KEYS file
> >> <https://dist.apache.org/repos/dist/dev/incubator/ariatosca/KEYS> with
> your
> >> key
> >>
> >>
> >> I went ahead and generated a new key, and amended it to the KEYS file
> that
> >> I found at the URL above which is located here:
> >>
> >> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/KEYS
> >>
> >> I have stored locally.
> >>
> >> How does one modify the actual file in the release area?  The release
> >> script that we have doesn't take it as an argument when it pushes the
> other
> >> artifacts.
> >>
> >> --Tom
> >>
> >>
> >>
> >>
> >> On Thu, Dec 7, 2017 at 5:14 PM, John D. Ament <johndam...@apache.org>
> wrote:
> >>
> >>> Thomas,
> >>>
> >>> I believe the release process was documented on confluence by prior
> release
> >>> manager.
> >>> https://cwiki.apache.org/confluence/display/ARIATOSCA/Release+Process
> >>>
> >>> John
> >>>
> >>> On Thu, Dec 7, 2017 at 7:30 AM Thomas Nadeau <tnadeaua...@gmail.com>
> >>> wrote:
> >>>
> >>>> Community,
> >>>>
> >>>> At last week's grooming we agreed that I would invoke the next
> release of
> >>>> Aria (.3) after certain critical PRs were merged. We are at that time
> >>> now,
> >>>> so I wanted to begin the process.  That leads me to my next
> question...
> >>>>
> >>>> Mentors: is there a document describing the steps to take?  There is a
> >>>> script in our repository under releases that appears to have all the
> >>> steps
> >>>> for creating all of our release candidate artifacts, but I am unsure
> if I
> >>>> need to have the committers/PMCC vote before that is created,
> afterwards
> >>> or
> >>>> both.  I also believe that the apache full PMC is supposed to have
> some
> >>>> time to review the release candidate too.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> --Tom
> >>>>
> >>>
> >>
>
>

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

[John D. Ament]

The typical steps a podling would take:

- Post a report on a common ground (e.g. email, confluence, or other)
- Let others know where it is
- Discuss it and get others to contribute into it
- When the report comes through, post it on the incubator wiki, e.g.
https://wiki.apache.org/incubator/December2017 (link changes each month)

The report generally looks fine, but I would change it so that only "[X]
Community building" is checked.  My current comment from the wiki still
holds "Activity on list is picking up over the slack conversations.  A
community member is planning to write a report, however it indicates a
corporate hierarchy issue within the project that needs to get solved."

Basically what that second sentence means is that we shouldn't be reliant
on one person to do the report.

John

On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau <tnadeaua...@gmail.com> wrote:

>
>
> The AriaTosca report was submitted last Thursday (at least made
> available) and is available here:
>
>
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
> <
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
> >
>
> I was not made aware of any special process for submitting this
> other than letting everyone know on the
> mailer that it was being created and where it was in case folks wanted to
> comment. If there is anything
> else needed for this let me know.
>
> —Tom
>
>
> > On Dec 10, 2017, at 9:36 AM, John D. Ament <johndam...@apache.org>
> wrote:
> >
> > All,
> >
> > Below is the current draft of our report.  As of now, we have 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
> > SAMOA
> > SDAP
> > SINGA
> > Spot
> > Superset
> > Taverna
> > Tephra
> > Trafodion
> > Wave
> >
> > --
> >
> > 
> > Amaterasu
> >
> > Apache Amaterasu is a framework providing contin

Website Build + Release

[John D. Ament]

All,

I'm troubleshooting from yesterday's identified website issues.  One thing
I noticed is that as a part of the website build, we download our release.
Why is that?

John

Re: Time for a new release

[John D. Ament]

The SVN repo is https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
So you would just check in your change via SVN.

On 2017-12-07 11:22, Thomas Nadeau <tnadeaua...@gmail.com> wrote: 
> Question about the instructions. It says:
> 
> If this is your first time creating a release for ARIA, make sure to update
> the KEYS file
> <https://dist.apache.org/repos/dist/dev/incubator/ariatosca/KEYS> with your
> key
> 
> 
> I went ahead and generated a new key, and amended it to the KEYS file that
> I found at the URL above which is located here:
> 
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/KEYS
> 
> I have stored locally.
> 
> How does one modify the actual file in the release area?  The release
> script that we have doesn't take it as an argument when it pushes the other
> artifacts.
> 
> --Tom
> 
> 
> 
> 
> On Thu, Dec 7, 2017 at 5:14 PM, John D. Ament <johndam...@apache.org> wrote:
> 
> > Thomas,
> >
> > I believe the release process was documented on confluence by prior release
> > manager.
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/Release+Process
> >
> > John
> >
> > On Thu, Dec 7, 2017 at 7:30 AM Thomas Nadeau <tnadeaua...@gmail.com>
> > wrote:
> >
> > > Community,
> > >
> > > At last week's grooming we agreed that I would invoke the next release of
> > > Aria (.3) after certain critical PRs were merged. We are at that time
> > now,
> > > so I wanted to begin the process.  That leads me to my next question...
> > >
> > > Mentors: is there a document describing the steps to take?  There is a
> > > script in our repository under releases that appears to have all the
> > steps
> > > for creating all of our release candidate artifacts, but I am unsure if I
> > > need to have the committers/PMCC vote before that is created, afterwards
> > or
> > > both.  I also believe that the apache full PMC is supposed to have some
> > > time to review the release candidate too.
> > >
> > > Thanks,
> > >
> > > --Tom
> > >
> >
> 

[DRAFT] Incubator PMC Board Report - December 2017

[John D. Ament]

All,

Below is the current draft of our report.  As of now, we have 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
SAMOA
SDAP
SINGA
Spot
Superset
Taverna
Tephra
Trafodion
Wave

--


Amaterasu

Apache Amaterasu is a framework providing continuous deployment for Big Data
pipelines.

Amaterasu has been incubating since 2017-09-07.

Three most important issues to address in the move towards graduation:

  1.
  2.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?



How has the project developed since the last report?


How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

  [ ](amaterasu) Jean-Baptiste Onofré
 Comments:
  [ ](amaterasu) Olivier Lamy
 Comments:
  [ ](amaterasu) Davor Bonaci
 Comments:

IPMC/Shepherd notes:

  johndament:
The podling was moving OK until the end of November, not sure if it's a
holiday lull.


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.
  2.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?



How has the project developed since the last report?


How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

  [ ](ariatosca) Suneel Marthi
 Comments:
  [ ](ariatosca) John D. Ament
 Comments:  Activity on list is picking up over the slack
conversations.  A community member is planning to write a report, however
it indicates a corporate hierarchy issue within the project that needs to
get solved.
  [ ](ariatosca) Jakob Homan
 Comments:

IPMC/Shepherd notes:



---
Crail

Crail is a storage platform for sharing performance critical
data in distributed data processing jobs at very high speed.

Crail has been incubating since 2017-11-01.

Three most important issues to address in the move towards graduation:

  1. Finish project setup
  2. Community building
  3. Create a first release

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None.

How has the community developed since the last report?

  N/A

How has the project developed since

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

[John D. Ament]

Thomas,

We'll resolve the issues around how and where to draft the report later.
Can you confirm that the contents of
https://docs.google.com/document/d/1Yg9J-9WD81UjqvwFoc8wek8628RSLzIEZogtVT1HBWg/edit?usp=sharing
match
the contents of
https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
and
I'll get things posted.

John

On Tue, Dec 12, 2017 at 6:25 AM Thomas Nadeau <tnad...@lucidvision.com>
wrote:

>
> I am confused - and have asked about what the specific process is
> for this. All
> I was told by Suneel when I asked, was to post up a G doc for people to
> hack/review
> together.  I have no idea what happens post that, so that is all I’ve done.
>
> So to answer your question, the doc on the wiki is the final one.
> No one has
> submitted any comments since I posted it there last Thursday.
>
> —Tom
>
>
> > On Dec 11, 2017, at 9:32 PM, John D. Ament <johndam...@apache.org>
> wrote:
> >
> > So, I'm a bit confused as far as next steps.
> >
> > Is the report posted at
> >
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
> > the
> > report we are saying should be submitted for the podling?  And are you
> > looking for me to post it on the incubator wiki?
> >
> > John
> >
> > On Mon, Dec 11, 2017 at 9:43 AM Tal Liron <t...@cloudify.co> wrote:
> >
> >> There actually was some in-person conversation between committers about
> the
> >> report. But it's a good criticism -- we should make it explicitly open
> and
> >> via the mailing list.
> >>
> >> On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau <tnadeaua...@gmail.com>
> >> wrote:
> >>
> >>>
> >>>
> >>>> On Dec 11, 2017, at 9:36 AM, John D. Ament <johndam...@apache.org>
> >>> wrote:
> >>>>
> >>>> The typical steps a podling would take:
> >>>>
> >>>> - Post a report on a common ground (e.g. email, confluence, or other)
> >>>> - Let others know where it is
> >>>> - Discuss it and get others to contribute into it
> >>>> - When the report comes through, post it on the incubator wiki, e.g.
> >>>> https://wiki.apache.org/incubator/December2017 (link changes each
> >> month)
> >>>>
> >>>> The report generally looks fine, but I would change it so that only
> >> "[X]
> >>>> Community building" is checked.  My current comment from the wiki
> still
> >>>> holds "Activity on list is picking up over the slack conversations.  A
> >>>> community member is planning to write a report, however it indicates a
> >>>> corporate hierarchy issue within the project that needs to get
> solved."
> >>>>
> >>>> Basically what that second sentence means is that we shouldn't be
> >> reliant
> >>>> on one person to do the report.
> >>>
> >>>Trust me, I am fully willing to share in the “fun” for the next
> >>> report. *)
> >>>
> >>>—Tom
> >>>
> >>>
> >>>>
> >>>> John
> >>>>
> >>>> On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau <tnadeaua...@gmail.com>
> >>> wrote:
> >>>>
> >>>>>
> >>>>>
> >>>>>   The AriaTosca report was submitted last Thursday (at least made
> >>>>> available) and is available here:
> >>>>>
> >>>>>
> >>>>> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> >>> Podling+Report+2017-DEC-12
> >>>>> <
> >>>>> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> >>> Podling+Report+2017-DEC-12
> >>>>>>
> >>>>>
> >>>>>   I was not made aware of any special process for submitting this
> >>>>> other than letting everyone know on the
> >>>>> mailer that it was being created and where it was in case folks
> wanted
> >>> to
> >>>>> comment. If there is anything
> >>>>> else needed for this let me know.
> >>>>>
> >>>>>   —Tom
> >>>>>
> >>>>>
> >>>>>> On Dec 10, 2017, at 9:36 AM, John D. Ament <johndam...@apache.org>
> >>>>> wrote:
> >>>>>>
> >&

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

[John D. Ament]

I went ahead and posted the report to the incubator wiki.  Please review:
https://wiki.apache.org/incubator/December2017

I did make a few changes and ommissions.  Most importantly, we don't
predict graduation dates.  I'm also a bit concerned with the preference of
the grooming meetings over on list communication.

John

On Tue, Dec 12, 2017 at 8:23 AM Suneel Marthi <smar...@apache.org> wrote:

> I have not had a chance to review the draft - given that we are late on the
> report I would prefer filing an updated report next month.
> Meanwhile can we get a release out before the holidays kick in.
>
> Suneel
>
> On Tue, Dec 12, 2017 at 6:24 AM, Thomas Nadeau <tnad...@lucidvision.com>
> wrote:
>
> >
> > I am confused - and have asked about what the specific process is
> > for this. All
> > I was told by Suneel when I asked, was to post up a G doc for people to
> > hack/review
> > together.  I have no idea what happens post that, so that is all I’ve
> done.
> >
> > So to answer your question, the doc on the wiki is the final one.
> > No one has
> > submitted any comments since I posted it there last Thursday.
> >
> > —Tom
> >
> >
> > > On Dec 11, 2017, at 9:32 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> > >
> > > So, I'm a bit confused as far as next steps.
> > >
> > > Is the report posted at
> > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > Podling+Report+2017-DEC-12
> > > the
> > > report we are saying should be submitted for the podling?  And are you
> > > looking for me to post it on the incubator wiki?
> > >
> > > John
> > >
> > > On Mon, Dec 11, 2017 at 9:43 AM Tal Liron <t...@cloudify.co> wrote:
> > >
> > >> There actually was some in-person conversation between committers
> about
> > the
> > >> report. But it's a good criticism -- we should make it explicitly open
> > and
> > >> via the mailing list.
> > >>
> > >> On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau <tnadeaua...@gmail.com
> >
> > >> wrote:
> > >>
> > >>>
> > >>>
> > >>>> On Dec 11, 2017, at 9:36 AM, John D. Ament <johndam...@apache.org>
> > >>> wrote:
> > >>>>
> > >>>> The typical steps a podling would take:
> > >>>>
> > >>>> - Post a report on a common ground (e.g. email, confluence, or
> other)
> > >>>> - Let others know where it is
> > >>>> - Discuss it and get others to contribute into it
> > >>>> - When the report comes through, post it on the incubator wiki, e.g.
> > >>>> https://wiki.apache.org/incubator/December2017 (link changes each
> > >> month)
> > >>>>
> > >>>> The report generally looks fine, but I would change it so that only
> > >> "[X]
> > >>>> Community building" is checked.  My current comment from the wiki
> > still
> > >>>> holds "Activity on list is picking up over the slack
> conversations.  A
> > >>>> community member is planning to write a report, however it
> indicates a
> > >>>> corporate hierarchy issue within the project that needs to get
> > solved."
> > >>>>
> > >>>> Basically what that second sentence means is that we shouldn't be
> > >> reliant
> > >>>> on one person to do the report.
> > >>>
> > >>>Trust me, I am fully willing to share in the “fun” for the
> next
> > >>> report. *)
> > >>>
> > >>>—Tom
> > >>>
> > >>>
> > >>>>
> > >>>> John
> > >>>>
> > >>>> On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau <
> tnadeaua...@gmail.com>
> > >>> wrote:
> > >>>>
> > >>>>>
> > >>>>>
> > >>>>>   The AriaTosca report was submitted last Thursday (at least
> made
> > >>>>> available) and is available here:
> > >>>>>
> > >>>>>
> > >>>>> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > >>> Podling+Report+2017-DEC-12
> > >>>>> <
> > >>>>> https://cwiki.apache.org/confluence/display/ARIATOSCA/
&g

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

[John D. Ament]

So, I'm a bit confused as far as next steps.

Is the report posted at
https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
the
report we are saying should be submitted for the podling?  And are you
looking for me to post it on the incubator wiki?

John

On Mon, Dec 11, 2017 at 9:43 AM Tal Liron <t...@cloudify.co> wrote:

> There actually was some in-person conversation between committers about the
> report. But it's a good criticism -- we should make it explicitly open and
> via the mailing list.
>
> On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau <tnadeaua...@gmail.com>
> wrote:
>
> >
> >
> > > On Dec 11, 2017, at 9:36 AM, John D. Ament <johndam...@apache.org>
> > wrote:
> > >
> > > The typical steps a podling would take:
> > >
> > > - Post a report on a common ground (e.g. email, confluence, or other)
> > > - Let others know where it is
> > > - Discuss it and get others to contribute into it
> > > - When the report comes through, post it on the incubator wiki, e.g.
> > > https://wiki.apache.org/incubator/December2017 (link changes each
> month)
> > >
> > > The report generally looks fine, but I would change it so that only
> "[X]
> > > Community building" is checked.  My current comment from the wiki still
> > > holds "Activity on list is picking up over the slack conversations.  A
> > > community member is planning to write a report, however it indicates a
> > > corporate hierarchy issue within the project that needs to get solved."
> > >
> > > Basically what that second sentence means is that we shouldn't be
> reliant
> > > on one person to do the report.
> >
> > Trust me, I am fully willing to share in the “fun” for the next
> > report. *)
> >
> > —Tom
> >
> >
> > >
> > > John
> > >
> > > On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau <tnadeaua...@gmail.com>
> > wrote:
> > >
> > >>
> > >>
> > >>The AriaTosca report was submitted last Thursday (at least made
> > >> available) and is available here:
> > >>
> > >>
> > >> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > Podling+Report+2017-DEC-12
> > >> <
> > >> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > Podling+Report+2017-DEC-12
> > >>>
> > >>
> > >>I was not made aware of any special process for submitting this
> > >> other than letting everyone know on the
> > >> mailer that it was being created and where it was in case folks wanted
> > to
> > >> comment. If there is anything
> > >> else needed for this let me know.
> > >>
> > >>—Tom
> > >>
> > >>
> > >>> On Dec 10, 2017, at 9:36 AM, John D. Ament <johndam...@apache.org>
> > >> wrote:
> > >>>
> > >>> All,
> > >>>
> > >>> Below is the current draft of our report.  As of now, we have 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
> > >&g

Re: Transition to Gitbox Complete

[John D. Ament]

On Sun, Dec 3, 2017 at 10:11 AM Thomas Nadeau <tnadeaua...@gmail.com> wrote:

> That still uses SSH, which then uses your pre-configured keys.  Github docs
> discourage this use for some reason.
>

Err no, github docs "recommend" using HTTPS, they don't discourage the use
of SSH.

https://stackoverflow.com/questions/11041729/why-does-github-recommend-https-over-ssh
provides
some info about why HTTPS is the current recommendation.


>
> --Tom
>
> On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament <johndam...@apache.org>
> 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 <tnadeaua...@gmail.com>
> > 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: Website Build + Release

[John D. Ament]

Tom,

Based on what I'm seeing, you're getting the current release (0.1.1).  I'm
not seeing anything that pulls the current master into the site.

I would recommend that we push from the build to the website, rather than
have the website pull this information in.

John

On Wed, Dec 6, 2017 at 8:59 AM Thomas Nadeau <tnadeaua...@gmail.com> wrote:

> We use 2 tools to generate the website: Jekyll (html) and spynx (docs), and
> both tools generate outputs based on the latest code.
>
> --Tom
>
>
> On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > All,
> >
> > I'm troubleshooting from yesterday's identified website issues.  One
> thing
> > I noticed is that as a part of the website build, we download our
> release.
> > Why is that?
> >
> > John
> >
>

Re: Lets be verbose on the mailer instead of other wise...

[John D. Ament]

I think it may take a bit of elbow grease to get all of the mailing lists
sorted out.  for instance, the website mentions user@ and dev@.  There's at
least 2 more public mailing lists

commits@, where all of the github emails go out ->
https://lists.apache.org/list.html?comm...@ariatosca.apache.org
issues@, where all of the jira emails go out ->
https://lists.apache.org/list.html?iss...@ariatosca.apache.org

Its fine to have discussions on github, jira since those messages are sent
to lists that are archived.  The main concerns I'm raising around problems
you're facing or development level discussions.  Those shouldn't happen on
slack first, they need to be brought up on list.  There's a few reasons
Apache prefers this:

- Asynchronous communication is preferred, to allow people across multiple
timezones to weigh in.
- There may be missing docs as well, and its a subtle note that we need to
get them documented more (for instance, the recent website issues remind me
that we need to document somewhere that our website is built in Jenkins
using the git-websites label and needs to point to a repo with write
access).

On Wed, Dec 6, 2017 at 10:06 AM Thomas Nadeau  wrote:

> I just wanted to reiterate the advice our mentors have been giving us today
> on Slack about first posting here to the list for any threads of
> discussion/issues/etc... The recommendation is "mailing list first". Please
> try to adhere to this before posting to slack, jira or otherwise as mailing
> list use/chatter is important for our project.
>
> Thanks,
>
> --Tom
>

Re: [Discuss] Future of AriaTosca

[John D. Ament]

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  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 
> > 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 
> > > > 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: Podling Report Reminder - June 2018

[John D. Ament]

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: [VOTE] Retire AriaTosca Podling

[John D. Ament]

+1

On Mon, Jun 25, 2018, 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
>

Re: [VOTE] publish ariatosca 0.2.0

[John D. Ament]

You can also compare to the previously staged release candidates that are
still on /dev

https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.1-incubating/

We created separate source/sdist/bdist directories to house each.  Note
that compared to the existing releases, the use of "sha" extension is now
discouraged to projects, instead the file extension should indicate the
correct sha length (256/512/etc)

The previously documented release process can be seen at
https://cwiki.apache.org/confluence/display/ARIATOSCA/Release+Process

I do see that the release script previously created is still around, and
seems to do the right things (minus the note above about the sha file):
https://github.com/apache/incubator-ariatosca/blob/master/release/asf-release.sh

Perhaps reroll by using this tool?

John

On Fri, Dec 29, 2017 at 5:43 PM Jakob Homan  wrote:

> -1 (binding)
>
> * The release needs to be signed, include the signature and sha512 and
> md5 hashes (see
> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.9.0rc8/ for
> an example)
> * Copyright in NOTICE should just be 2017 rather than range
>
> * NOTICE/DISCLAIMER/LICENSE look good
> * Headers look good
> * Didn't see any included libraries that would require inclusion in LICENSE
>
> Also, just to clarify on the voting procedure.  The entire community
> is encouraged to vote on releases, although on the Podling Project
> Management Committee (PPMC) has binding votes.  Testing and voting on
> releases is an excellent way to contribute to project.
>
> -Jakob
>
> On 28 December 2017 at 07:15, Thomas Nadeau  wrote:
> > I forgot to vote myself.  I downloaded and unpacked the release, the
> > version number there appeared correct, the API docs are in the package,
> > installs correctly using 'make install-virtual', all tests run with "make
> > test" as well.
> >
> > --Tom
> >
> >
> > On Wed, Dec 27, 2017 at 10:49 AM, Tal Liron  wrote:
> >
> >> +1
> >>
> >>- I downloaded and unpacked the release.
> >>- Version is correct.
> >>- API docs are in "docs/html".
> >>- All tests run with "make test".
> >>- Installs correctly with "make install-virtual".
> >>- Played around with Clearwater example.
> >>
> >>
> >> On Tue, Dec 26, 2017 at 10:11 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.
> >> >
> >> > I created a tarball candidate for the 0.2.0 release and placed it in
> >> ARIA's
> >> >  /dist/dev folder:
> >> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> >> > 0.2.0-candidate/
> >> > The list of issues Resolved 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=ARIA-394
> >> > 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.  The voting for this as I understand it, 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,
> Tuesday,
> >> > December 26, 2017 and be completed on  12PM EST on Friday, December
> 29,
> >> > 2017.
> >> >
> >> > Thanks,
> >> >
> >> > --Tom
> >> >
> >>
>

Re: [VOTE] publish ariatosca 0.2.0

[John D. Ament]

On Thu, Jan 4, 2018 at 11:54 AM Thomas Nadeau <tnad...@apache.org> 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 <johndam...@apache.org>
> 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 <tnadeaua...@gmail.com>
> > 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 <tnad...@apache.org>
> > > 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
> > > > > <https://issues.apache.org/jira/secure/RapidBoard.jspa?
> > > > 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: [VOTE] publish ariatosca 0.2.0

[John D. Ament]

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=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: [VOTE] publish ariatosca 0.2.0

[John D. Ament]

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 <tnadeaua...@gmail.com> 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 <tnad...@apache.org>
> 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=ARIA-394
> > > <https://issues.apache.org/jira/secure/RapidBoard.jspa?
> > 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: merging paused until release is completed

[John D. Ament]

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: Confluence wiki page write access

[John D. Ament]

(moving general to bcc)
Thomas,

The IPMC does not grant access to individual podling wikis.  You are an
admin on the Aria Tosca wiki already, and should be able to grant access.
Let's keep it to the dev list if you're unsure how.

John

On Thu, Feb 8, 2018 at 9:07 AM Thomas Nadeau  wrote:

> Adding General.
>
> --Tom
>
>
> On Mon, Feb 5, 2018 at 9:58 AM, D Jayachandran <
> d.jayachand...@ericsson.com>
> wrote:
>
> > Hi All,
> >
> > I would like to write up in the wiki for all the major PR's which am
> > contributing.
> > Could you please provide me with the write access for it.
> >
> >
> > Regards,
> > DJ
> >
>

Re: Podling Report: February 2018

[John D. Ament]

No report is expected by Aria Tosca at this time
https://wiki.apache.org/incubator/February2018


On Thu, Feb 8, 2018 at 10:00 AM Thomas Nadeau  wrote:

> Community:
>
> I've posted the latest podling report here for your review:
>
> https://cwiki.apache.org/confluence/pages/editpage.action?pageId=75966486
>
> Please take a look at this as soon as possible and either edit or comment
> on my proposal.  We need to get this to our mentors today. Apologies for
> the last minute posting.
>
> --Tom
>

Re: Confluence access

[John D. Ament]

Thomas,

You're already an admin on confluence (tnadeau).  There are no other
permissions to grant you.  JIRA and Confluence permissions are not tied
together.

John

On Mon, Feb 19, 2018 at 9:17 AM Thomas Nadeau  wrote:

> John/Suneel,
>
> I conflated Confluence and Jira in my last note. I was able to fix DJ's
> permissions on Confluence. The key here is to modify permissions using the
> "Space Tools" (bottom left on the project main page).
>
> However, on Jira I am listed as a contributor still, and that should be
> fixed.
>
> --Tom
>

[NOTICE] The Aria Tosca Podling has been retired

[John D. Ament]

All,

Please be advised that based on votes occurring on the dev list, private
list and general list the Aria Tosca podling has been retired.

Source code will remain available in a read only fashion.
Mailing lists will be shut down in a few days, archives to remain available.

Thanks,

John

Re: ASF Podling Report for AriaTosca

[John D. Ament]

Please review the setup instructions at the top of
https://wiki.apache.org/incubator

The wiki is not tied to your apache.org credentials.

John

On Mon, Mar 5, 2018 at 9:24 AM Suneel Marthi  wrote:

> John, should be able to grant u write access to wiki
>
> On Mon, Mar 5, 2018 at 9:20 AM, Thomas Nadeau 
> 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 
> 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 
> > 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

[John D. Ament]

Added to the contributors group.

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

> tnadeau
>
> On Mon, Mar 5, 2018 at 9:53 AM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > What is your username?
> >
> > On Mon, Mar 5, 2018 at 9:52 AM Thomas Nadeau <tnadeaua...@gmail.com>
> > wrote:
> >
> > > Ok. I was able to create an account, but I still do not have
> permissions
> > to
> > > edit. When I tried creating a page for AriaTosca off of March2018, I
> got
> > > the error "You are not allowed to edit this page."
> > >
> > > On Mon, Mar 5, 2018 at 9:43 AM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > > > Please review the setup instructions at the top of
> > > > https://wiki.apache.org/incubator
> > > >
> > > > The wiki is not tied to your apache.org credentials.
> > > >
> > > > John
> > > >
> > > > On Mon, Mar 5, 2018 at 9:24 AM Suneel Marthi <smar...@apache.org>
> > wrote:
> > > >
> > > > > 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

[John D. Ament]

What is your username?

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

> Ok. I was able to create an account, but I still do not have permissions to
> edit. When I tried creating a page for AriaTosca off of March2018, I got
> the error "You are not allowed to edit this page."
>
> On Mon, Mar 5, 2018 at 9:43 AM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > Please review the setup instructions at the top of
> > https://wiki.apache.org/incubator
> >
> > The wiki is not tied to your apache.org credentials.
> >
> > John
> >
> > On Mon, Mar 5, 2018 at 9:24 AM Suneel Marthi <smar...@apache.org> wrote:
> >
> > > 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: [RESULT] [VOTE] Retire AriaTosca Podling

[John D. Ament]

Hi

Now a vote must occur on the general@ list.  Once that vote is complete
then the podling retires.  The -1 should also be recorded but we have
provided proper justification for it to not be a blocker.

On Thu, Jun 28, 2018, 9:01 AM Suneel Marthi  wrote:

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