[Slack] Notifications from the ASF team for June 30th, 2017 at 8:17 AM

2017-06-29 Thread Slack 
Hi ARIA TOSCA,

You have a new direct message from the ASF team
(https://the-asf.slack.com/x-185534614710-206058223746/).

---

@digestai
View in the archives:
https://the-asf.slack.com/x-185534614710-206058223746/archives/D5E4SCANM/p1498798845087266

Digest.AI (8:00 AM, June 30th)
Hi ARIA,
*Here’s your digest for June 30th 2017*
There are 60 messages yesterday, and the most active user is ran

*#ariatosca*
 @ran: :thumbsup: that's great Tal, Maxim and I have went over it and
besides a few tiny issues (mostly around some extras from rebase which
were no longer needed) I merged the PR
 We'll indeed need to talk about the right flow to make sure that the
docs are staying up to date and not only updated once per release
 weird that bad crossreferences don't raise any errors :confused:
 in any case im not sure if we have to review the resulting
documentation every PR, perhaps just building it (and making sure no
errors were raised) would be enough in most cases?
 In any case thank you for doing this, seems like you've put much effort
into it, so we'll definitely try not to mess it :wink:
 @ran: I've created a 0.1.0 package, placed it on `/dist/dev` and raised
a voting thread. Please see the relevant mail and vote
:slightly_smiling_face:
 @emblemparade: can we create a party coalition to override @johndament
? just kidding, we do need to fix those things :confused: the package
does install, but the instructions assume it's already on pypi, which is
actually wrong for a source distribution
 @ran: oh I totally get it, we should probably have tried pausing or
letting you merge first before introducing new changes as your changes
were pretty much all over the place :slightly_smiling_face: but then
again we didnt know how long it might take.
in any case the issues i remember were:
1) changed methods in modeling/relationships - maxim changed a couple of
methods there, and on your branch your kept both the old and new
versions.
2) renamed module `compilation.py` -- `graph_compilation.py` - on your
branch they both existed.

overall it wasn't so bad to find and fix these issues so
:slightly_smiling_face:



*Links shared by your team today:*



* * *

You can snooze these notifications for
an hour:
https://the-asf.slack.com/unsub/U5FFQJ2LW-5a1cb74d28-notify-mute-1h
eight hours:
https://the-asf.slack.com/unsub/U5FFQJ2LW-796e6535e1-notify-mute-8h
a day:
https://the-asf.slack.com/unsub/U5FFQJ2LW-4e6e073ada-notify-mute-1d
three days:
https://the-asf.slack.com/unsub/U5FFQJ2LW-806a2d8aa0-notify-mute-3d
or the next week:
https://the-asf.slack.com/unsub/U5FFQJ2LW-6adc840c34-notify-mute-7d.

You can also turn email notifications off:
https://the-asf.slack.com/unsub/U5FFQJ2LW-64de78982b-notify.

For more detailed preferences, see your account page:
https://the-asf.slack.com/account.

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread 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  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  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 
> > wrote:
> >
> >> On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:
> >>
> >> > Suneel, re mentioning 72 hours - note that I simply used the
> recommended
> >> > template for these messages from here:
> >> >
> >> > http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-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  >
> >> > wrote:
> >> >
> >> > > -1.  Found the following issues:
> >> > >
> >> > > - BUILD instructions are INSTALL instructions, and the installation
> >> > doesn't
> >> > > work
> >> > >
> >> > > pip install apache-ariatosca
> >> > >
> >> > >
> >> > > Collecting apache-ariatosca
> >> > >   Could not find a version that satisfies the requirement
> >> > apache-ariatosca
> >> > > (from versions: )
> >> > > No matching distribution found for apache-ariatosca
> >> > >
> >> > > - There is no DISCLAIMER file
> >> > > - No instructions on how to run RAT
> >> > > - I'm not sure this is a source release, many files don't match
> whats
> >> in
> >> > > the repo (files added/missing?)
> >> > >
> >> > > Other things look fine:
> >> > > - contains incubating
> >> > > - files contain headers
> >> > >
> >> > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv 
> wrote:
> >> > >
> >> > > > I created a tarball candidate for the 0.1.0 release and placed it
> in
> >> > > ARIA's
> >> > > > /dist/dev folder:
> >> > > >

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread Ran Ziv 
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  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 
> wrote:
>
>> On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:
>>
>> > Suneel, re mentioning 72 hours - note that I simply used the recommended
>> > template for these messages from here:
>> >
>> > http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-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 
>> > wrote:
>> >
>> > > -1.  Found the following issues:
>> > >
>> > > - BUILD instructions are INSTALL instructions, and the installation
>> > doesn't
>> > > work
>> > >
>> > > pip install apache-ariatosca
>> > >
>> > >
>> > > Collecting apache-ariatosca
>> > >   Could not find a version that satisfies the requirement
>> > apache-ariatosca
>> > > (from versions: )
>> > > No matching distribution found for apache-ariatosca
>> > >
>> > > - There is no DISCLAIMER file
>> > > - No instructions on how to run RAT
>> > > - I'm not sure this is a source release, many files don't match whats
>> in
>> > > the repo (files added/missing?)
>> > >
>> > > Other things look fine:
>> > > - contains incubating
>> > > - files contain headers
>> > >
>> > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
>> > >
>> > > > I created a tarball candidate for the 0.1.0 release and placed it in
>> > > ARIA's
>> > > > /dist/dev folder:
>> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
>> > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be
>> found
>> > in
>> > > > that folder as well.
>> > > >
>> > > >
>> > > > The list of issues Resolved for this release are simply all the
>> issues
>> > > that
>> > > > have been resolved thus far, seeing as this would be the first
>> release
>> > :)
>> > > > Those can be found here:
>> > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-
>> > > > 1=project%3Dariatosca%20and%20status%20in%20(resolved%
>> 2C%20closed)
>> > > >
>> > > >
>> > > > Instructions for installation etc. may be found in the README file
>> > inside
>> > > > the tarball.
>> > > >
>> > > >
>> > > > Please vote to publish this tarball on ARIA's /dist/release folder.
>> > > >
>> > > >
>> > > > Ran
>> > > >
>> > >
>> >
>>
>
>

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread Ran Ziv 
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 
wrote:

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

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread Tal Liron 
This is confusing to me. Python is an interpreted language, so there is no
real difference between source and binary.

In the Python world, you would probably differentiate between "dev"
(everything on the git repo, including tests and development tools) and
"release" (just what's needed to run). I think we treated this as a
"release".

Is there a way to map Python's "dev" and "release" onto ASF's "source" and
"binary"? What do other Python ASF projects do?

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

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



-- 
Tal Liron, Senior Solutions Architect 
--
M: +1-312-375-8299 http://cloudify.co @cloudifysource

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread Suneel Marthi 
You can go with this - this is more recent and i have been enforcing this
on podlings I mentor as well as TLPs I am involved with

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



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

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

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread John D. Ament 
On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:

> Suneel, re mentioning 72 hours - note that I simply used the recommended
> template for these messages from here:
>
> http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3E
>
>
I'll note this is an email from 10 years ago, and things have been refined
since then.  I plan to rewrite that guide to give better examples.  Here's
a more up to date example

https://lists.apache.org/thread.html/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 
> wrote:
>
> > -1.  Found the following issues:
> >
> > - BUILD instructions are INSTALL instructions, and the installation
> doesn't
> > work
> >
> > pip install apache-ariatosca
> >
> >
> > Collecting apache-ariatosca
> >   Could not find a version that satisfies the requirement
> apache-ariatosca
> > (from versions: )
> > No matching distribution found for apache-ariatosca
> >
> > - There is no DISCLAIMER file
> > - No instructions on how to run RAT
> > - I'm not sure this is a source release, many files don't match whats in
> > the repo (files added/missing?)
> >
> > Other things look fine:
> > - contains incubating
> > - files contain headers
> >
> > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
> >
> > > I created a tarball candidate for the 0.1.0 release and placed it in
> > ARIA's
> > > /dist/dev folder:
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> in
> > > that folder as well.
> > >
> > >
> > > The list of issues Resolved for this release are simply all the issues
> > that
> > > have been resolved thus far, seeing as this would be the first release
> :)
> > > Those can be found here:
> > > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > > 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> > >
> > >
> > > Instructions for installation etc. may be found in the README file
> inside
> > > the tarball.
> > >
> > >
> > > Please vote to publish this tarball on ARIA's /dist/release folder.
> > >
> > >
> > > Ran
> > >
> >
>

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread Ran Ziv 
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



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



Ran


On Thu, Jun 29, 2017 at 6:43 PM, John D. Ament 
wrote:

> -1.  Found the following issues:
>
> - BUILD instructions are INSTALL instructions, and the installation doesn't
> work
>
> pip install apache-ariatosca
>
>
> Collecting apache-ariatosca
>   Could not find a version that satisfies the requirement apache-ariatosca
> (from versions: )
> No matching distribution found for apache-ariatosca
>
> - There is no DISCLAIMER file
> - No instructions on how to run RAT
> - I'm not sure this is a source release, many files don't match whats in
> the repo (files added/missing?)
>
> Other things look fine:
> - contains incubating
> - files contain headers
>
> On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
>
> > I created a tarball candidate for the 0.1.0 release and placed it in
> ARIA's
> > /dist/dev folder:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> > that folder as well.
> >
> >
> > The list of issues Resolved for this release are simply all the issues
> that
> > have been resolved thus far, seeing as this would be the first release :)
> > Those can be found here:
> > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> >
> >
> > Instructions for installation etc. may be found in the README file inside
> > the tarball.
> >
> >
> > Please vote to publish this tarball on ARIA's /dist/release folder.
> >
> >
> > Ran
> >
>

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread 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

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

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

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

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread Suneel Marthi 
That's correct - u get to move the artifacts to /release only after the
iPMC okays the release artifacts.

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

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

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread Ran Ziv 
Yes, I'm aware of this, sorry if I've mis-phrased the purpose of the vote.
Thanks for clearing this up.

On Thu, Jun 29, 2017 at 6:37 PM, John D. Ament 
wrote:

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

Re: [VOTE] publish ariatosca 0.1.0

2017-06-29 Thread 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
>

[VOTE] publish ariatosca 0.1.0

2017-06-29 Thread Ran Ziv 
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

Digest for ASF's Slack

2017-06-29 Thread Digest 
Here’s your digest for today! 
#ariatosca
undefined: sorry, i know this is taking forever :disappointed: but i honestly 
did not expect so much breakage. python is just too dynamic, and not enough 
library devs know how to play well with these dynamics to ensure proper OOP 
behavior. the good news is that we only ever have to solve all these problems 
once.
undefined: Okay. Re service modifications models, definitely ignore them for 
now.
undefined: [UPDATE]

Very happy to announce a PR for our code documentation. It is a huge PR in 
sheer number of lines...

The resulting "User Manual for ARIA TOSCA" is thorough and enormous, and gives 
you a quick sense of just how big this project is. It starts with a section for 
the CLI (and eventually REST will be there), and then a deep dive into all our 
packages, modules, and APIs. I've divided the APIs into as many sections as 
make sense, though in some cases the pages are *very* big indeed. In those 
cases a added an extra "summary" at the top of the page that could make things 
easier.

There's a lot crossreferencing, though there will obviously be a few bugs. 
(Please fix when you find them.) All the TOSCA references lead you directly to 
the place in the TOSCA specification. References to standard Python types will 
lead you to the Python 2.7 documentation.

This is a good start, but we need some discipline in the team to keep this 
going. First off, there is a JIRA to add a tox test to make sure you do not 
break the documentation. But ... Sphinx errors only cover bad ReST, they won't 
catch sloppy formatting, and *don't* tell you if your crossreferences don't 
work.

Also, Sphinx is only ... partially automated. There is manual work involved in 
adding new packages, modules, and sometimes even classes (you might need to 
update those summaries at top of pages). So, we're also going to have to get 
used to editing the rst files in the `docs/` dir. It's not a lot of work, but 
if you forget ... your new code might not be in the published documentation! 
Basically, as part of code reviews for PRs I think we should also review the 
*resulting* built documentation before merging. We could use readthedocs just 
for this purpose, as it has tools for building on branches. Of course we can 
also find a way to create our own hook.

Very easy to build: `make docs` should do the trick.

Finally, the wiki I posted a while ago is already out of date. I learned a lot 
and will need to change some of the rules there. So, don't refer to the wiki -- 
refer instead to other code documentation in the repo.


#general


#random