Re: Feedback on Project Maturity Model

2016-03-04 Thread Amol Kekre
Very nice docs. Thks Amol On Fri, Mar 4, 2016 at 5:48 PM, Sasha Parfenov wrote: > Apex documentation has been split out, merged, and deployed to the apex > site! > > You can follow the link under docs > to > http://apex.incubator.apache.org/docs/ape

Re: Feedback on Project Maturity Model

2016-03-04 Thread Sasha Parfenov
Apex documentation has been split out, merged, and deployed to the apex site! You can follow the link under docs to http://apex.incubator.apache.org/docs/apex-3.3/ This resolves https://issues.apache.org/jira/browse/APEXCORE-293 Thanks, Sasha On Wed,

Re: Feedback on Project Maturity Model

2016-03-02 Thread Thomas Weise
The Maven artifacts are for development. There is no need to install anything separately when developing Apex applications, including the testing in embedded mode. An installation is needed to launch applications on the cluster and the options I mentioned are for that. Have not seen users asking f

Re: Feedback on Project Maturity Model

2016-03-02 Thread Chinmay Kolhatkar
Hi Hitesh, Are you suggest the build scripts of apex should create a convenient binary package (maybe just a tarball) which is directly deploy-able? - Chinmay. On Thu, Mar 3, 2016 at 3:04 AM, Hitesh Shah wrote: > I am not sure if that is entirely accurate. Convenience binaries usually > refer

Re: Feedback on Project Maturity Model

2016-03-02 Thread Hitesh Shah
I am not sure if that is entirely accurate. Convenience binaries usually refer to a final assembled/package bundle that can be deployed in the end-user env. thanks — Hitesh On Mar 2, 2016, at 11:51 AM, Thomas Weise wrote: > Binaries are the jar files in Maven. For the Apex developer, everythi

Re: Feedback on Project Maturity Model

2016-03-02 Thread Thomas Weise
Getting close: https://github.com/tweise/incubator-apex-core/tree/APEXCORE-293/docs Will probably be merged in a day or two. On Wed, Mar 2, 2016 at 11:46 AM, P. Taylor Goetz wrote: > Not explicitly called out in the maturity model, but also the Apex > documentation needs to be moved off of data

Re: Feedback on Project Maturity Model

2016-03-02 Thread Thomas Weise
Binaries are the jar files in Maven. For the Apex developer, everything is driven through Maven, starting from the archetype. Explicit install is only needed for the CLI. Following are the available options: - Checkout from git: https://github.com/apache /incubator-apex-core/blob/5f216a1bd27

Re: Feedback on Project Maturity Model

2016-03-02 Thread P. Taylor Goetz
Not explicitly called out in the maturity model, but also the Apex documentation needs to be moved off of datatorrent.com and onto ASF infrastructure. It also would need to be stripped of any references to proprietary datatorrent software. What’s the status of that effort? -Taylor > On Mar 2,

Re: Feedback on Project Maturity Model

2016-03-02 Thread Hitesh Shah
I believe RE40 is still pending? — Hitesh On Mar 2, 2016, at 1:38 AM, Chinmay Kolhatkar wrote: > Hello Community, > > We've created an initial project maturity model on apex website: > http://apex.incubator.apache.org/maturity.html > > This model is based on based on ASF project maturity mod

Re: Feedback on Project Maturity Model

2016-03-02 Thread Chris Nauroth
I see. You're right. The "who we are" info is effectively only on the incubation status page right now, which is not something that would be maintained after incubation. http://incubator.apache.org/projects/apex.html Thanks for the reply. I think addressing those 2 items would resolve CO10.

Re: Feedback on Project Maturity Model

2016-03-02 Thread Thomas Weise
Chris, I can think of 2 items: - Version compatibility - Who we are page Do you see anything else? Thanks, Thomas On Wed, Mar 2, 2016 at 10:18 AM, Chris Nauroth wrote: > This looks great! I know some IPMC members will appreciate that you've > documented this and can reference it in a grad

Re: Feedback on Project Maturity Model

2016-03-02 Thread Chris Nauroth
This looks great! I know some IPMC members will appreciate that you've documented this and can reference it in a graduation discussion. I see a red cross next to CO10: The project has a well-known homepage that points to all the information required to operate according to this maturity model. W

Re: Feedback on Project Maturity Model

2016-03-02 Thread Thomas Weise
For QU40 we still need to add the page documenting compatibility: https://issues.apache.org/jira/browse/APEXCORE-319 On Wed, Mar 2, 2016 at 1:38 AM, Chinmay Kolhatkar wrote: > Hello Community, > > We've created an initial project maturity model on apex website: > http://apex.incubator.apache.o

Feedback on Project Maturity Model

2016-03-02 Thread Chinmay Kolhatkar
Hello Community, We've created an initial project maturity model on apex website: http://apex.incubator.apache.org/maturity.html This model is based on based on ASF project maturity model. On the webpage, green check icon next to the element means it is achieved. Red cross icon mean, its not ach