Re: [PROPOSAL] MetaModel for the Apache Incubator

[ant elder]

>From the subject line I thought this was going to be another attempt to
sort out the incubator  :-/

   ...ant

On Tue, May 28, 2013 at 7:20 PM, Henry Saputra wrote:

> Dear ASF members,
>
> We would like to propose MetaModel for the incubator.
>
> Matt Franklin will be the Champion for this project and the proposal draft
> is available at:
>
> https://wiki.apache.org/incubator/MetaModelProposal
>
> Looking forward to all of your suggestions and feedback.
>
> Thanks,
>
> Henry Saputra
>
>
>
> -
>
> = MetaModel – uniform data access across datastores =
>
> Proposal for Apache Incubator
>
> == Abstract ==
>
> MetaModel is a data access framework, providing a common interface for
> exploration and querying of different types of datastores.
>
> == Proposal ==
>
> MetaModel provides a uniform meta-model for exploring and querying the
> structure of datastores, covering but not limited to relational databases,
> various data file formats, NoSQL databases, Salesforce.com, SugarCRM and
> more. The scope of the project is to stay domain-agnostic, so the
> meta-model will be concerned with schemas, tables, columns, rows,
> relationships etc.
>
> On top of this meta-model a rich querying API is provided which resembles
> SQL, but built using compiler-checked Java language constructs. For
> datastores that do not have a native SQL-compatible query engine, the
> MetaModel project also includes an abstract Java-based query engine
> implementation which individual datastore-modules can adapt to fit the
> concrete datastore.
>
> === Background ===
>
> The MetaModel project was initially developed by eobject.dk to service the
> DataCleaner application (http://datacleaner.org). The main requirement was
> to perform data querying and modification operations on a wide range of
> quite different datastores. Furthermore a programmatic query model was
> needed in order to allow different components to influence the query plan.
>
> In 2009, Human Inference acquired the eobjects projects including
> MetaModel. Since then MetaModel has been put to extensive use in the Human
> Inference products. The open source nature of the project was reinforced,
> leading to a significant growth in the community.
>
> MetaModel has successfully been used in a number of other open source
> projects as well as mission critical commercial software from Human
> Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org.
>
> === Rationale ===
>
> Different types of datastores have different characteristics, which always
> lead to the interfaces for these being different from one another.
> Standards like JDBC and the SQL language attempt to standardize data
> access, but for some datastore types like flat files, spreadsheets, NoSQL
> databases and more, such standards are not even implementable.
>
> Specialization in interfaces obviously has merit for optimized usage, but
> for integration tools, batch applications and or generic data modification
> tools, this myriad of specialized interfaces is a big pain. Furthermore,
> being able to query every datastore with a basic set of SQL-like features
> can be a great productivity boost for a wide range of applications.
>
> === Initial goals ===
>
> MetaModel is already a stable project, so initial goals are more oriented
> towards an adaption to the Apache ecosystem than about functional changes.
>
> We are constantly adding more datastore types to the portfolio, but the
> core modules have not had drastic changes for some time.
>
> Our focus will be on making ties with other Apache projects (such as POI,
> Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project
> to something more rememberable.
> This includes comply with Apache Software Foundation license for third
> party dependencies.
>
> == Current status ==
>
> === Meritocracy ===
>
> We intend to do everything we can to encourage a meritocracy in the
> development of MetaModel. Currently most important development and design
> decisions have been made at Human Inference, but with an open window for
> anyone to participate on mailing lists and discussion forums. We believe
> that the approach going forward should be more encouraging by sharing all
> the design ideas and discussions in the open, not only just the topics that
> have been “dragged” into the open by third parties.  We believe that
> meritocracy will be further stimulated by granting the control of the
> project to an independent committee.
>
> === Community ===
>
> The community around MetaModel already exists, but we believe it will grow
> substantially by becoming an Apache project. With MetaModel used in a wide
> range of both open and closed source application, both at Human Inference
> (HIquality MDM), it’s open source projects DataCleaner, SassyReader and
> AnalyzerBeans and by other parties (such as the Quipo data warehouse
> automation project), we believe that the critical mass to sustain a
> commu

[jira] [Created] (PODLINGNAMESEARCH-33) Establish whether "Apache JSPWiki" is a suitable name

[JIRA]

Juan Pablo Santos Rodríguez created PODLINGNAMESEARCH-33:


 Summary: Establish whether "Apache JSPWiki" is a suitable name 
 Key: PODLINGNAMESEARCH-33
 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Juan Pablo Santos Rodríguez


We have to do some investigations to ensure that "Apache JSPWiki" is a suitable 
name for a TLP. Here are some resources related to this issue:

http://incubator.apache.org/guides/names.html
http://www.apache.org/foundation/marks/

A similar search was perfomed 3 years ago, so this issue is mostly an update on 
that JIRA. cfr with: https://issues.apache.org/jira/browse/JSPWIKI-547

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Fwd: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3)

[Vinod Kone]

Please vote on releasing the following candidate as Apache Mesos
(incubating)
version 0.11.0. This will be the third incubator release for Mesos in Apache

.

The candidate for Mesos 0.11.0-incubating release is available at:

http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz


The tag to be voted on:
https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=dbcaa0d348a88188c17a8b06b57306832a7a5885


The MD5 checksum of the tarball can be found at:

http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.md5


The signature of the tarball can be found at:

http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.asc

PGP key used to sign the release:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2B1D89DA5C6E508C

Please vote on releasing this package as Apache Mesos 0.11.0-incubating!

The vote is open until Friday, May 31st at 18:30 UTC and passes if a

majority of at least 3 +1 IPMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.11.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache Mesos, please see
http://incubator.apache.org/mesos.

[VOTE] Release Apache Mesos 0.11.0-incubating (RC3)

[Vinod Kone]

Please vote on releasing the following candidate as Apache Mesos
(incubating)
version 0.11.0. This will be the third incubator release for Mesos in Apache

.

The candidate for Mesos 0.11.0-incubating release is available at:

http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz


The tag to be voted on:
https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=dbcaa0d348a88188c17a8b06b57306832a7a5885


The MD5 checksum of the tarball can be found at:

http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.md5


The signature of the tarball can be found at:

http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.asc

PGP key used to sign the release:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2B1D89DA5C6E508C

Please vote on releasing this package as Apache Mesos 0.11.0-incubating!

The vote is open until Friday, May 31st at 18:30 UTC and passes if a

majority of at least 3 +1 IPMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.11.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache Mesos, please see
http://incubator.apache.org/mesos.

Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC1)

[Vinod Kone]

Thanks Luciano for the suggestions. I think we got some conflicting advice
before (when we released 0.9.0) about what goes into LICENSE and NOTICE.
I've (hopefully) fixed it now. Will whip up RC3 shortly.


@vinodkone


On Sat, May 25, 2013 at 12:01 PM, Luciano Resende wrote:

> On Fri, May 24, 2013 at 1:58 PM, Vinod Kone  wrote:
> > Please vote on releasing the following candidate as Apache Mesos
> > (incubating)
> > version 0.11.0. This will be the third incubator release for Mesos in
> Apache
> > .
> >
> > The candidate for Mesos 0.11.0-incubating release is available at:
> >
> >
> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC2/mesos-0.11.0-incubating.tar.gz
> >
> > The tag to be voted on:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=399b857ec4a3558b63ab8eb47df5c51bcad64251
> >
> > The MD5 checksum of the tarball can be found at:
> >
> >
> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC2/mesos-0.11.0-incubating.tar.gz.md5
> >
> > The signature of the tarball can be found at:
> >
> >
> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC2/mesos-0.11.0-incubating.tar.gz.asc
> >
> > PGP key used to sign the release:
> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2B1D89DA5C6E508C
> >
> > Please vote on releasing this package as Apache Mesos 0.11.0-incubating!
> >
> > The vote is open until Monday, May 27th at 21:00 UTC and passes if a
> > majority of at least 3 +1 IPMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Mesos 0.11.0-incubating
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache Mesos, please see
> > http://incubator.apache.org/mesos.
>
> I'm just copying my comments from previous RC as I don't see any one
> of them fixed.
>
> -1
>
> Extracted release is missing Incubator DISCLAIMER
> http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer
>
> Looks like the LICENSE information got attached to the NOTICE file,
> instead of LICENSE. Please update the LICENSE file accordingly and
> then clean up the NOTICE with required attributions.
>
>
> http://incubator.apache.org/guides/releasemanagement.html#note-license-and-notice
>
> The following might also be helpful
>
> http://www.apache.org/dev/release.html#license
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC1)

[Vinod Kone]

Also, note that the vote for RC2 has been cancelled.


On Tue, May 28, 2013 at 11:18 AM, Vinod Kone  wrote:

> Thanks Luciano for the suggestions. I think we got some conflicting advice
> before (when we released 0.9.0) about what goes into LICENSE and NOTICE.
> I've (hopefully) fixed it now. Will whip up RC3 shortly.
>
>
> @vinodkone
>
>
> On Sat, May 25, 2013 at 12:01 PM, Luciano Resende wrote:
>
>> On Fri, May 24, 2013 at 1:58 PM, Vinod Kone  wrote:
>> > Please vote on releasing the following candidate as Apache Mesos
>> > (incubating)
>> > version 0.11.0. This will be the third incubator release for Mesos in
>> Apache
>> > .
>> >
>> > The candidate for Mesos 0.11.0-incubating release is available at:
>> >
>> >
>> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC2/mesos-0.11.0-incubating.tar.gz
>> >
>> > The tag to be voted on:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=399b857ec4a3558b63ab8eb47df5c51bcad64251
>> >
>> > The MD5 checksum of the tarball can be found at:
>> >
>> >
>> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC2/mesos-0.11.0-incubating.tar.gz.md5
>> >
>> > The signature of the tarball can be found at:
>> >
>> >
>> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC2/mesos-0.11.0-incubating.tar.gz.asc
>> >
>> > PGP key used to sign the release:
>> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2B1D89DA5C6E508C
>> >
>> > Please vote on releasing this package as Apache Mesos 0.11.0-incubating!
>> >
>> > The vote is open until Monday, May 27th at 21:00 UTC and passes if a
>> > majority of at least 3 +1 IPMC votes are cast.
>> >
>> > [ ] +1 Release this package as Apache Mesos 0.11.0-incubating
>> > [ ] -1 Do not release this package because ...
>> >
>> > To learn more about Apache Mesos, please see
>> > http://incubator.apache.org/mesos.
>>
>> I'm just copying my comments from previous RC as I don't see any one
>> of them fixed.
>>
>> -1
>>
>> Extracted release is missing Incubator DISCLAIMER
>> http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer
>>
>> Looks like the LICENSE information got attached to the NOTICE file,
>> instead of LICENSE. Please update the LICENSE file accordingly and
>> then clean up the NOTICE with required attributions.
>>
>>
>> http://incubator.apache.org/guides/releasemanagement.html#note-license-and-notice
>>
>> The following might also be helpful
>>
>> http://www.apache.org/dev/release.html#license
>>
>> --
>> Luciano Resende
>> http://people.apache.org/~lresende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
>>
>
>

Re: Unused OpenOffice source tree in incubator: keep or remove?

[Daniel Shahaf]

On Tue, May 21, 2013 at 09:40:19PM +0200, Andrea Pescetti wrote:
> Is this the recommended configuration or shall we "svn remove" the whole 
> old tree, maybe leaving only a README.txt pointing to the new location? 

Ask infra about arranging a redirect - this might be possible but would have to
be done manually since "ooo" != "openoffice".

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Process of adding a proposal to the incubator wiki

[Afkham Azeez]

Hi folks,
Can somebody let me know what is the process of obtaining write access to
the incubator wiki? I need to add an incubator proposal.

Thanks
Azeez

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com,
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
*
*email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
*
*

Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3)

[Luciano Resende]

On Tue, May 28, 2013 at 11:24 AM, Vinod Kone  wrote:
> Please vote on releasing the following candidate as Apache Mesos
> (incubating)
> version 0.11.0. This will be the third incubator release for Mesos in Apache
>
> .
>
> The candidate for Mesos 0.11.0-incubating release is available at:
>
> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz
>
>
> The tag to be voted on:
> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=dbcaa0d348a88188c17a8b06b57306832a7a5885
>
>
> The MD5 checksum of the tarball can be found at:
>
> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.md5
>
>
> The signature of the tarball can be found at:
>
> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.asc
>
> PGP key used to sign the release:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2B1D89DA5C6E508C
>
> Please vote on releasing this package as Apache Mesos 0.11.0-incubating!
>
> The vote is open until Friday, May 31st at 18:30 UTC and passes if a
>
> majority of at least 3 +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.11.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Mesos, please see
> http://incubator.apache.org/mesos.


-1

Your notice still looks wrong, for example, boto-2.0b2.zip license
says that the copyright notice should be included in all copies of the
software, and the boto README has :

Copyright (c) 2006-2010 Mitch Garnaat 
Copyright (c) 2010, Eucalyptus Systems, Inc.
All rights reserved.

Which is not on the Notice, which now only have :

Apache Mesos
Copyright 2012, The Apache Software Foundation

This product includes software developed by The Apache Software
Foundation (http://www.apache.org/).

Note that the year is also wrong.


Similar comments apply to the copyright info from glog, the function
gettimeofday, etc

Which should bring your Notice to something like :

Apache Mesos
Copyright 2013, The Apache Software Foundation

This product includes software developed at The Apache Software
Foundation (http://www.apache.org/).

This product includes software developed by Google Inc
Copyright (c) 2008, Google Inc.
All rights reserved.

This product includes software developed by Jouni Malinen and contributors
Copyright (c) 2003-2008, Jouni Malinen  and contributors
All Rights Reserved.

Having said that, you will need to do this exercise for all third
party dependencies that you have in your release.

--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Updated] (PODLINGNAMESEARCH-33) Establish whether "Apache JSPWiki" is a suitable name

[JIRA]

 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Juan Pablo Santos Rodríguez updated PODLINGNAMESEARCH-33:
-

Description: 
We have to do some investigations to ensure that "Apache JSPWiki" is a suitable 
name for a TLP. Here are some resources related to this issue:

http://incubator.apache.org/guides/names.html
http://www.apache.org/foundation/marks/

A similar search was perfomed 4 years ago, so this issue is mostly an update on 
that JIRA. cfr with: https://issues.apache.org/jira/browse/JSPWIKI-547

  was:
We have to do some investigations to ensure that "Apache JSPWiki" is a suitable 
name for a TLP. Here are some resources related to this issue:

http://incubator.apache.org/guides/names.html
http://www.apache.org/foundation/marks/

A similar search was perfomed 3 years ago, so this issue is mostly an update on 
that JIRA. cfr with: https://issues.apache.org/jira/browse/JSPWIKI-547


corrected typo

> Establish whether "Apache JSPWiki" is a suitable name 
> --
>
> Key: PODLINGNAMESEARCH-33
> URL: 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Juan Pablo Santos Rodríguez
>
> We have to do some investigations to ensure that "Apache JSPWiki" is a 
> suitable name for a TLP. Here are some resources related to this issue:
> http://incubator.apache.org/guides/names.html
> http://www.apache.org/foundation/marks/
> A similar search was perfomed 4 years ago, so this issue is mostly an update 
> on that JIRA. cfr with: https://issues.apache.org/jira/browse/JSPWIKI-547

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Process of adding a proposal to the incubator wiki

[Upayavira]

You need to let us know your wiki username, and we will grant you write
access.

Upayavira

On Wed, May 29, 2013, at 03:48 PM, Afkham Azeez wrote:
> Hi folks,
> Can somebody let me know what is the process of obtaining write access to
> the incubator wiki? I need to add an incubator proposal.
> 
> Thanks
> Azeez
> 
> -- 
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com,
> *Member; Apache Software Foundation;
> **http://www.apache.org/*
> *
> *
> *email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter:
> **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
> *
> *

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: What's the difference between dormant and retired?

[Alan Cabrera]

If no one minds I will change them all to dormant, since all are welcome back 
to the fold, should they so desire.


Regards,
Alan

On May 27, 2013, at 12:58 PM, Christian Grobmeier  wrote:

> On Mon, May 27, 2013 at 9:17 PM, John D. Ament  wrote:
>> I think the terms mean different things, from the incubator perspective.
>> 
>> Dormant - we're not active enough right now for a full community, but
>> believe later on we can build it back up.
>> Retired - we've given up all hope of becoming a TLP, instead we think it's
>> best to archive the code/move it to github/move it to bitbucket and allow
>> others who want to work on it to just grab it and go.
> 
> The difference is one goes to github and one does not?
> 
> After this interpretation I would expect dormant projects to retire.
> Retired projects
> can be revived too. It does not matter if there was something on GitHub or 
> not.
> 
> Not enough for me to maintain two terms.
> 
>> 
>> Just my 2 cents..
>> 
>> 
>> On Mon, May 27, 2013 at 2:10 PM, Christian Grobmeier 
>> wrote:
>> 
>>> On Mon, May 27, 2013 at 7:40 PM, Alan Cabrera 
>>> wrote:
 Yeah, I like the word dormant as well.  Should we rename them all to
>>> dormant?
>>> 
>>> +1 from me. So far I don't see any difference in the end.
>>> 
>>> 
>>> 
 
 Regards,
 Alan
 
 On May 27, 2013, at 10:32 AM, Upayavira  wrote:
 
> I think it was just a question of 'retiring' sounding too final. Using
> the word 'dormant' was less threatening, and made it more feasible for
> the podlings to go, well, dormant.
> 
> Upayavira
> 
> On Mon, May 27, 2013, at 05:39 PM, Alan Cabrera wrote:
>> They kinda sound the same.  Why didn't podlings want to retire?  Does
>> anyone know?
>> 
>> 
>> Regards,
>> Alan
>> 
>> On May 27, 2013, at 9:14 AM, Christian Grobmeier 
>> wrote:
>> 
>>> I asked the same question in july 2011, and got a response from Henri
>>> Yandell which I repost here:
>>> 
>>> "Given the PPMC is closed down, I think it has to be retired.
>>> 
>>> Dormant implies a PPMC is taking some time off.
>>> 
>>> Basically this is a larger version of "don't be afraid to delete a
>>> line of code; it's in version control".
>>> 
>>> Hen"
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Mon, May 27, 2013 at 5:38 PM, Alan Cabrera 
>>> wrote:
 Looking at the podlings.xml and it's not clear to me what the
>>> difference is.  I'm sure I neglected to read some documentation bit.
 
 
 Regards,
 Alan
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
>>> 
>>> 
>>> 
>>> --
>>> http://www.grobmeier.de
>>> https://www.timeandbill.de
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
>>> 
>>> 
>>> 
>>> --
>>> http://www.grobmeier.de
>>> https://www.timeandbill.de
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
> 
> 
> 
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Process of adding a proposal to the incubator wiki

[Afkham Azeez]

My wiki username is AfkhamAzeez

Thanks

--
Afkham Azeez
Sent from my phone
On May 29, 2013 11:17 PM, "Upayavira"  wrote:

> You need to let us know your wiki username, and we will grant you write
> access.
>
> Upayavira
>
> On Wed, May 29, 2013, at 03:48 PM, Afkham Azeez wrote:
> > Hi folks,
> > Can somebody let me know what is the process of obtaining write access to
> > the incubator wiki? I need to add an incubator proposal.
> >
> > Thanks
> > Azeez
> >
> > --
> > *Afkham Azeez*
> > Director of Architecture; WSO2, Inc.; http://wso2.com,
> > *Member; Apache Software Foundation;
> > **http://www.apache.org/*
> > *
> > *
> > *email: **az...@wso2.com* * cell: +94 77 3320919
> > blog: **http://blog.afkham.org* *
> > twitter:
> > **http://twitter.com/afkham_azeez*
> > *
> > linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> > *
> > *
> > *Lean . Enterprise . Middleware*
> > *
> > *
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Process of adding a proposal to the incubator wiki

[Christian Grobmeier]

You have write access now.

Please see this guide:
http://incubator.apache.org/guides/proposal.html

And please see these proposals for examples:
http://wiki.apache.org/incubator/ProjectProposals

I would look at for example BeanShell or Callback or any other recent one.

Cheers
Christian


On Wed, May 29, 2013 at 8:01 PM, Afkham Azeez  wrote:
> My wiki username is AfkhamAzeez
>
> Thanks
>
> --
> Afkham Azeez
> Sent from my phone
> On May 29, 2013 11:17 PM, "Upayavira"  wrote:
>
>> You need to let us know your wiki username, and we will grant you write
>> access.
>>
>> Upayavira
>>
>> On Wed, May 29, 2013, at 03:48 PM, Afkham Azeez wrote:
>> > Hi folks,
>> > Can somebody let me know what is the process of obtaining write access to
>> > the incubator wiki? I need to add an incubator proposal.
>> >
>> > Thanks
>> > Azeez
>> >
>> > --
>> > *Afkham Azeez*
>> > Director of Architecture; WSO2, Inc.; http://wso2.com,
>> > *Member; Apache Software Foundation;
>> > **http://www.apache.org/*
>> > *
>> > *
>> > *email: **az...@wso2.com* * cell: +94 77 3320919
>> > blog: **http://blog.afkham.org* *
>> > twitter:
>> > **http://twitter.com/afkham_azeez*
>> > *
>> > linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> > *
>> > *
>> > *Lean . Enterprise . Middleware*
>> > *
>> > *
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>



--
http://www.grobmeier.de
https://www.timeandbill.de

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] MetaModel for the Apache Incubator

[Henry Saputra]

There are already a lot of discussions about it and this aint one of them =P


- Henry


On Wed, May 29, 2013 at 12:33 AM, ant elder  wrote:

> From the subject line I thought this was going to be another attempt to
> sort out the incubator  :-/
>
>...ant
>
> On Tue, May 28, 2013 at 7:20 PM, Henry Saputra  >wrote:
>
> > Dear ASF members,
> >
> > We would like to propose MetaModel for the incubator.
> >
> > Matt Franklin will be the Champion for this project and the proposal
> draft
> > is available at:
> >
> > https://wiki.apache.org/incubator/MetaModelProposal
> >
> > Looking forward to all of your suggestions and feedback.
> >
> > Thanks,
> >
> > Henry Saputra
> >
> >
> >
> > -
> >
> > = MetaModel – uniform data access across datastores =
> >
> > Proposal for Apache Incubator
> >
> > == Abstract ==
> >
> > MetaModel is a data access framework, providing a common interface for
> > exploration and querying of different types of datastores.
> >
> > == Proposal ==
> >
> > MetaModel provides a uniform meta-model for exploring and querying the
> > structure of datastores, covering but not limited to relational
> databases,
> > various data file formats, NoSQL databases, Salesforce.com, SugarCRM and
> > more. The scope of the project is to stay domain-agnostic, so the
> > meta-model will be concerned with schemas, tables, columns, rows,
> > relationships etc.
> >
> > On top of this meta-model a rich querying API is provided which resembles
> > SQL, but built using compiler-checked Java language constructs. For
> > datastores that do not have a native SQL-compatible query engine, the
> > MetaModel project also includes an abstract Java-based query engine
> > implementation which individual datastore-modules can adapt to fit the
> > concrete datastore.
> >
> > === Background ===
> >
> > The MetaModel project was initially developed by eobject.dk to service
> the
> > DataCleaner application (http://datacleaner.org). The main requirement
> was
> > to perform data querying and modification operations on a wide range of
> > quite different datastores. Furthermore a programmatic query model was
> > needed in order to allow different components to influence the query
> plan.
> >
> > In 2009, Human Inference acquired the eobjects projects including
> > MetaModel. Since then MetaModel has been put to extensive use in the
> Human
> > Inference products. The open source nature of the project was reinforced,
> > leading to a significant growth in the community.
> >
> > MetaModel has successfully been used in a number of other open source
> > projects as well as mission critical commercial software from Human
> > Inference. Currently MetaModel is hosted at
> http://metamodel.eobjects.org.
> >
> > === Rationale ===
> >
> > Different types of datastores have different characteristics, which
> always
> > lead to the interfaces for these being different from one another.
> > Standards like JDBC and the SQL language attempt to standardize data
> > access, but for some datastore types like flat files, spreadsheets, NoSQL
> > databases and more, such standards are not even implementable.
> >
> > Specialization in interfaces obviously has merit for optimized usage, but
> > for integration tools, batch applications and or generic data
> modification
> > tools, this myriad of specialized interfaces is a big pain. Furthermore,
> > being able to query every datastore with a basic set of SQL-like features
> > can be a great productivity boost for a wide range of applications.
> >
> > === Initial goals ===
> >
> > MetaModel is already a stable project, so initial goals are more oriented
> > towards an adaption to the Apache ecosystem than about functional
> changes.
> >
> > We are constantly adding more datastore types to the portfolio, but the
> > core modules have not had drastic changes for some time.
> >
> > Our focus will be on making ties with other Apache projects (such as POI,
> > Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project
> > to something more rememberable.
> > This includes comply with Apache Software Foundation license for third
> > party dependencies.
> >
> > == Current status ==
> >
> > === Meritocracy ===
> >
> > We intend to do everything we can to encourage a meritocracy in the
> > development of MetaModel. Currently most important development and design
> > decisions have been made at Human Inference, but with an open window for
> > anyone to participate on mailing lists and discussion forums. We believe
> > that the approach going forward should be more encouraging by sharing all
> > the design ideas and discussions in the open, not only just the topics
> that
> > have been “dragged” into the open by third parties.  We believe that
> > meritocracy will be further stimulated by granting the control of the
> > project to an independent committee.
> >
> > === Community ===
> >
> > The community around MetaModel already exists, but we believe 

Re: What's the difference between dormant and retired?

[ant elder]

I agree with Mark and John, the terms mean different things, and the term
"retired" is reasonably well understood now and mentioned in various places
in the Incubator documentation so wouldn't it be better to keep it as is?
Are there really any dormant poddlings? If so probably they are really
retired now and they should just be changed to that.

   ...ant

On Wed, May 29, 2013 at 6:47 PM, Alan Cabrera  wrote:

> If no one minds I will change them all to dormant, since all are welcome
> back to the fold, should they so desire.
>
>
> Regards,
> Alan
>
> On May 27, 2013, at 12:58 PM, Christian Grobmeier 
> wrote:
>
> > On Mon, May 27, 2013 at 9:17 PM, John D. Ament 
> wrote:
> >> I think the terms mean different things, from the incubator perspective.
> >>
> >> Dormant - we're not active enough right now for a full community, but
> >> believe later on we can build it back up.
> >> Retired - we've given up all hope of becoming a TLP, instead we think
> it's
> >> best to archive the code/move it to github/move it to bitbucket and
> allow
> >> others who want to work on it to just grab it and go.
> >
> > The difference is one goes to github and one does not?
> >
> > After this interpretation I would expect dormant projects to retire.
> > Retired projects
> > can be revived too. It does not matter if there was something on GitHub
> or not.
> >
> > Not enough for me to maintain two terms.
> >
> >>
> >> Just my 2 cents..
> >>
> >>
> >> On Mon, May 27, 2013 at 2:10 PM, Christian Grobmeier <
> grobme...@gmail.com>wrote:
> >>
> >>> On Mon, May 27, 2013 at 7:40 PM, Alan Cabrera 
> >>> wrote:
>  Yeah, I like the word dormant as well.  Should we rename them all to
> >>> dormant?
> >>>
> >>> +1 from me. So far I don't see any difference in the end.
> >>>
> >>>
> >>>
> 
>  Regards,
>  Alan
> 
>  On May 27, 2013, at 10:32 AM, Upayavira  wrote:
> 
> > I think it was just a question of 'retiring' sounding too final.
> Using
> > the word 'dormant' was less threatening, and made it more feasible
> for
> > the podlings to go, well, dormant.
> >
> > Upayavira
> >
> > On Mon, May 27, 2013, at 05:39 PM, Alan Cabrera wrote:
> >> They kinda sound the same.  Why didn't podlings want to retire?
>  Does
> >> anyone know?
> >>
> >>
> >> Regards,
> >> Alan
> >>
> >> On May 27, 2013, at 9:14 AM, Christian Grobmeier <
> grobme...@gmail.com>
> >> wrote:
> >>
> >>> I asked the same question in july 2011, and got a response from
> Henri
> >>> Yandell which I repost here:
> >>>
> >>> "Given the PPMC is closed down, I think it has to be retired.
> >>>
> >>> Dormant implies a PPMC is taking some time off.
> >>>
> >>> Basically this is a larger version of "don't be afraid to delete a
> >>> line of code; it's in version control".
> >>>
> >>> Hen"
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Mon, May 27, 2013 at 5:38 PM, Alan Cabrera  >
> >>> wrote:
>  Looking at the podlings.xml and it's not clear to me what the
> >>> difference is.  I'm sure I neglected to read some documentation bit.
> 
> 
>  Regards,
>  Alan
> 
> 
> 
> -
>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>  For additional commands, e-mail:
> general-h...@incubator.apache.org
> 
> >>>
> >>>
> >>>
> >>> --
> >>> http://www.grobmeier.de
> >>> https://www.timeandbill.de
> >>>
> >>>
> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>
> >>
> >>
> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> 
> 
>  -
>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>  For additional commands, e-mail: general-h...@incubator.apache.org
> 
> >>>
> >>>
> >>>
> >>> --
> >>> http://www.grobmeier.de
> >>> https://www.timeandbill.de
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >
> >
> >
> > --
> > http://www.grobmeier.de
> > https://www.t

Re: What's the difference between dormant and retired?

[John D. Ament]

I can't see any place in the docs that describe dormant.


On Wed, May 29, 2013 at 3:36 PM, ant elder  wrote:

> I agree with Mark and John, the terms mean different things, and the term
> "retired" is reasonably well understood now and mentioned in various places
> in the Incubator documentation so wouldn't it be better to keep it as is?
> Are there really any dormant poddlings? If so probably they are really
> retired now and they should just be changed to that.
>
>...ant
>
> On Wed, May 29, 2013 at 6:47 PM, Alan Cabrera 
> wrote:
>
> > If no one minds I will change them all to dormant, since all are welcome
> > back to the fold, should they so desire.
> >
> >
> > Regards,
> > Alan
> >
> > On May 27, 2013, at 12:58 PM, Christian Grobmeier 
> > wrote:
> >
> > > On Mon, May 27, 2013 at 9:17 PM, John D. Ament  >
> > wrote:
> > >> I think the terms mean different things, from the incubator
> perspective.
> > >>
> > >> Dormant - we're not active enough right now for a full community, but
> > >> believe later on we can build it back up.
> > >> Retired - we've given up all hope of becoming a TLP, instead we think
> > it's
> > >> best to archive the code/move it to github/move it to bitbucket and
> > allow
> > >> others who want to work on it to just grab it and go.
> > >
> > > The difference is one goes to github and one does not?
> > >
> > > After this interpretation I would expect dormant projects to retire.
> > > Retired projects
> > > can be revived too. It does not matter if there was something on GitHub
> > or not.
> > >
> > > Not enough for me to maintain two terms.
> > >
> > >>
> > >> Just my 2 cents..
> > >>
> > >>
> > >> On Mon, May 27, 2013 at 2:10 PM, Christian Grobmeier <
> > grobme...@gmail.com>wrote:
> > >>
> > >>> On Mon, May 27, 2013 at 7:40 PM, Alan Cabrera 
> > >>> wrote:
> >  Yeah, I like the word dormant as well.  Should we rename them all to
> > >>> dormant?
> > >>>
> > >>> +1 from me. So far I don't see any difference in the end.
> > >>>
> > >>>
> > >>>
> > 
> >  Regards,
> >  Alan
> > 
> >  On May 27, 2013, at 10:32 AM, Upayavira  wrote:
> > 
> > > I think it was just a question of 'retiring' sounding too final.
> > Using
> > > the word 'dormant' was less threatening, and made it more feasible
> > for
> > > the podlings to go, well, dormant.
> > >
> > > Upayavira
> > >
> > > On Mon, May 27, 2013, at 05:39 PM, Alan Cabrera wrote:
> > >> They kinda sound the same.  Why didn't podlings want to retire?
> >  Does
> > >> anyone know?
> > >>
> > >>
> > >> Regards,
> > >> Alan
> > >>
> > >> On May 27, 2013, at 9:14 AM, Christian Grobmeier <
> > grobme...@gmail.com>
> > >> wrote:
> > >>
> > >>> I asked the same question in july 2011, and got a response from
> > Henri
> > >>> Yandell which I repost here:
> > >>>
> > >>> "Given the PPMC is closed down, I think it has to be retired.
> > >>>
> > >>> Dormant implies a PPMC is taking some time off.
> > >>>
> > >>> Basically this is a larger version of "don't be afraid to delete
> a
> > >>> line of code; it's in version control".
> > >>>
> > >>> Hen"
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> On Mon, May 27, 2013 at 5:38 PM, Alan Cabrera <
> a...@toolazydogs.com
> > >
> > >>> wrote:
> >  Looking at the podlings.xml and it's not clear to me what the
> > >>> difference is.  I'm sure I neglected to read some documentation bit.
> > 
> > 
> >  Regards,
> >  Alan
> > 
> > 
> > 
> > -
> >  To unsubscribe, e-mail:
> general-unsubscr...@incubator.apache.org
> >  For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > 
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> http://www.grobmeier.de
> > >>> https://www.timeandbill.de
> > >>>
> > >>>
> > -
> > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >>> For additional commands, e-mail:
> general-h...@incubator.apache.org
> > >>>
> > >>
> > >>
> > >>
> > -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail:
> general-h...@incubator.apache.org
> > >>
> > >
> > >
> -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > 
> > 
> > 
> -
> >  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >  For additional comma

Re: What's the difference between dormant and retired?

[Joseph Schaefer]

What we really need now is a few hundred more emails on this exciting subject, 
just like every other year!  At the end we can all agree to disagree and go 
away sad that nothing ever gets done around here, just like every other year we 
have this interesting debate!

Party on I say.

Sent from my iPhone

On May 29, 2013, at 3:38 PM, "John D. Ament"  wrote:

> I can't see any place in the docs that describe dormant.
> 
> 
> On Wed, May 29, 2013 at 3:36 PM, ant elder  wrote:
> 
>> I agree with Mark and John, the terms mean different things, and the term
>> "retired" is reasonably well understood now and mentioned in various places
>> in the Incubator documentation so wouldn't it be better to keep it as is?
>> Are there really any dormant poddlings? If so probably they are really
>> retired now and they should just be changed to that.
>> 
>>   ...ant
>> 
>> On Wed, May 29, 2013 at 6:47 PM, Alan Cabrera 
>> wrote:
>> 
>>> If no one minds I will change them all to dormant, since all are welcome
>>> back to the fold, should they so desire.
>>> 
>>> 
>>> Regards,
>>> Alan
>>> 
>>> On May 27, 2013, at 12:58 PM, Christian Grobmeier 
>>> wrote:
>>> 
 On Mon, May 27, 2013 at 9:17 PM, John D. Ament >> 
>>> wrote:
> I think the terms mean different things, from the incubator
>> perspective.
> 
> Dormant - we're not active enough right now for a full community, but
> believe later on we can build it back up.
> Retired - we've given up all hope of becoming a TLP, instead we think
>>> it's
> best to archive the code/move it to github/move it to bitbucket and
>>> allow
> others who want to work on it to just grab it and go.
 
 The difference is one goes to github and one does not?
 
 After this interpretation I would expect dormant projects to retire.
 Retired projects
 can be revived too. It does not matter if there was something on GitHub
>>> or not.
 
 Not enough for me to maintain two terms.
 
> 
> Just my 2 cents..
> 
> 
> On Mon, May 27, 2013 at 2:10 PM, Christian Grobmeier <
>>> grobme...@gmail.com>wrote:
> 
>> On Mon, May 27, 2013 at 7:40 PM, Alan Cabrera 
>> wrote:
>>> Yeah, I like the word dormant as well.  Should we rename them all to
>> dormant?
>> 
>> +1 from me. So far I don't see any difference in the end.
>> 
>> 
>> 
>>> 
>>> Regards,
>>> Alan
>>> 
>>> On May 27, 2013, at 10:32 AM, Upayavira  wrote:
>>> 
 I think it was just a question of 'retiring' sounding too final.
>>> Using
 the word 'dormant' was less threatening, and made it more feasible
>>> for
 the podlings to go, well, dormant.
 
 Upayavira
 
 On Mon, May 27, 2013, at 05:39 PM, Alan Cabrera wrote:
> They kinda sound the same.  Why didn't podlings want to retire?
>>> Does
> anyone know?
> 
> 
> Regards,
> Alan
> 
> On May 27, 2013, at 9:14 AM, Christian Grobmeier <
>>> grobme...@gmail.com>
> wrote:
> 
>> I asked the same question in july 2011, and got a response from
>>> Henri
>> Yandell which I repost here:
>> 
>> "Given the PPMC is closed down, I think it has to be retired.
>> 
>> Dormant implies a PPMC is taking some time off.
>> 
>> Basically this is a larger version of "don't be afraid to delete
>> a
>> line of code; it's in version control".
>> 
>> Hen"
>> 
>> 
>> 
>> 
>> 
>> On Mon, May 27, 2013 at 5:38 PM, Alan Cabrera <
>> a...@toolazydogs.com
 
>> wrote:
>>> Looking at the podlings.xml and it's not clear to me what the
>> difference is.  I'm sure I neglected to read some documentation bit.
>>> 
>>> 
>>> Regards,
>>> Alan
>>> -
>>> To unsubscribe, e-mail:
>> general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail:
>>> general-h...@incubator.apache.org
>> 
>> 
>> 
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail:
>> general-h...@incubator.apache.org
>>> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail:
>> general-h...@incubator.apache.org
>> -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
>> ---

Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3)

[Marvin Humphrey]

On Wed, May 29, 2013 at 9:12 AM, Luciano Resende  wrote:
> Your notice still looks wrong, for example, boto-2.0b2.zip license
> says that the copyright notice should be included in all copies of the
> software, and the boto README has :
>
> Copyright (c) 2006-2010 Mitch Garnaat 
> Copyright (c) 2010, Eucalyptus Systems, Inc.
> All rights reserved.
>
> Which is not on the Notice, which now only have :
>
> Apache Mesos
> Copyright 2012, The Apache Software Foundation
>
> This product includes software developed by The Apache Software
> Foundation (http://www.apache.org/).
>
> Note that the year is also wrong.
>
>
> Similar comments apply to the copyright info from glog, the function
> gettimeofday, etc
>
> Which should bring your Notice to something like :
>
> Apache Mesos
> Copyright 2013, The Apache Software Foundation
>
> This product includes software developed at The Apache Software
> Foundation (http://www.apache.org/).
>
> This product includes software developed by Google Inc
> Copyright (c) 2008, Google Inc.
> All rights reserved.
>
> This product includes software developed by Jouni Malinen and contributors
> Copyright (c) 2003-2008, Jouni Malinen  and contributors
> All Rights Reserved.
>
> Having said that, you will need to do this exercise for all third
> party dependencies that you have in your release.

Hi, I'm sorry that I don't have the time to participate in this thread fully
and perform a thorough review of the release candidate, but
respinning an RC in order to add copyright notices to NOTICE
doesn't sound right.

http://www.apache.org/dev/licensing-howto.html#mod-notice

Modifications to NOTICE

NOTICE is reserved for a certain subset of legally required notifications
which are not satisfied by either the text of LICENSE or the presence of
licensing information embedded within the dependency subtree. Aside from
Apache-licensed dependencies which supply NOTICE files of their own, it is
uncommon for a dependency to require additions to NOTICE.

Copyright notifications which have been relocated from source files
(rather than removed) must be preserved in NOTICE. However, elements such
as the copyright notifications embedded within BSD and MIT licenses need
not be duplicated in NOTICE -- it suffices to leave those notices in their
original locations.

It is important to keep NOTICE as brief and simple as possible, as each
addition places a burden on downstream consumers. Do not add anything to
NOTICE which is not legally required.

See LEGAL-59, LEGAL-62 and LEGAL-155 for the back story.

The "Licensing HowTo" linked above is supposed to provide a formulaic approach
for generating LICENSE and NOTICE.  Hopefully, LICENSE and NOTICE files which
conform to its recommendations will not get any -1 votes from IPMC members.

Marvin Humphrey

On Wed, May 29, 2013 at 9:12 AM, Luciano Resende  wrote:
> On Tue, May 28, 2013 at 11:24 AM, Vinod Kone  wrote:
>> Please vote on releasing the following candidate as Apache Mesos
>> (incubating)
>> version 0.11.0. This will be the third incubator release for Mesos in Apache
>>
>> .
>>
>> The candidate for Mesos 0.11.0-incubating release is available at:
>>
>> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz
>>
>>
>> The tag to be voted on:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=dbcaa0d348a88188c17a8b06b57306832a7a5885
>>
>>
>> The MD5 checksum of the tarball can be found at:
>>
>> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.md5
>>
>>
>> The signature of the tarball can be found at:
>>
>> http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.asc
>>
>> PGP key used to sign the release:
>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2B1D89DA5C6E508C
>>
>> Please vote on releasing this package as Apache Mesos 0.11.0-incubating!
>>
>> The vote is open until Friday, May 31st at 18:30 UTC and passes if a
>>
>> majority of at least 3 +1 IPMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Mesos 0.11.0-incubating
>> [ ] -1 Do not release this package because ...
>>
>> To learn more about Apache Mesos, please see
>> http://incubator.apache.org/mesos.
>
>
> -1
>
> Your notice still looks wrong, for example, boto-2.0b2.zip license
> says that the copyright notice should be included in all copies of the
> software, and the boto README has :
>
> Copyright (c) 2006-2010 Mitch Garnaat 
> Copyright (c) 2010, Eucalyptus Systems, Inc.
> All rights reserved.
>
> Which is not on the Notice, which now only have :
>
> Apache Mesos
> Copyright 2012, The Apache Software Foundation
>
> This product includes software developed by The Apache Software
> Foundation (http://www.apache.org/).
>
> Note that the year is also wrong.
>
>
> Similar comments apply to the copyright info from glog, the function
> gettimeofday, etc
>
> Which should brin

Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3)

[Luciano Resende]

On Wed, May 29, 2013 at 3:27 PM, Marvin Humphrey wrote:

> On Wed, May 29, 2013 at 9:12 AM, Luciano Resende 
> wrote:
> > Your notice still looks wrong, for example, boto-2.0b2.zip license
> > says that the copyright notice should be included in all copies of the
> > software, and the boto README has :
> >
> > Copyright (c) 2006-2010 Mitch Garnaat 
> > Copyright (c) 2010, Eucalyptus Systems, Inc.
> > All rights reserved.
> >
> > Which is not on the Notice, which now only have :
> >
> > Apache Mesos
> > Copyright 2012, The Apache Software Foundation
> >
> > This product includes software developed by The Apache Software
> > Foundation (http://www.apache.org/).
> >
> > Note that the year is also wrong.
> >
> >
> > Similar comments apply to the copyright info from glog, the function
> > gettimeofday, etc
> >
> > Which should bring your Notice to something like :
> >
> > Apache Mesos
> > Copyright 2013, The Apache Software Foundation
> >
> > This product includes software developed at The Apache Software
> > Foundation (http://www.apache.org/).
> >
> > This product includes software developed by Google Inc
> > Copyright (c) 2008, Google Inc.
> > All rights reserved.
> >
> > This product includes software developed by Jouni Malinen and
> contributors
> > Copyright (c) 2003-2008, Jouni Malinen  and contributors
> > All Rights Reserved.
> >
> > Having said that, you will need to do this exercise for all third
> > party dependencies that you have in your release.
>
> Hi, I'm sorry that I don't have the time to participate in this thread
> fully
> and perform a thorough review of the release candidate, but
> respinning an RC in order to add copyright notices to NOTICE
> doesn't sound right.
>
> http://www.apache.org/dev/licensing-howto.html#mod-notice
>
> Modifications to NOTICE
>
> NOTICE is reserved for a certain subset of legally required
> notifications
> which are not satisfied by either the text of LICENSE or the presence
> of
> licensing information embedded within the dependency subtree. Aside
> from
> Apache-licensed dependencies which supply NOTICE files of their own,
> it is
> uncommon for a dependency to require additions to NOTICE.
>
> Copyright notifications which have been relocated from source files
> (rather than removed) must be preserved in NOTICE. However, elements
> such
> as the copyright notifications embedded within BSD and MIT licenses
> need
> not be duplicated in NOTICE -- it suffices to leave those notices in
> their
> original locations.
>
> It is important to keep NOTICE as brief and simple as possible, as each
> addition places a burden on downstream consumers. Do not add anything
> to
> NOTICE which is not legally required.
>
> See LEGAL-59, LEGAL-62 and LEGAL-155 for the back story.
>
> The "Licensing HowTo" linked above is supposed to provide a formulaic
> approach
> for generating LICENSE and NOTICE.  Hopefully, LICENSE and NOTICE files
> which
> conform to its recommendations will not get any -1 votes from IPMC members.
>
> Marvin Humphrey
>
>
Thanks for the pointers Marvin, based on [1] I'm changing my vote to +0 as
I haven't looked into any other aspects of the release other then legal
files.

[1] http://www.apache.org/legal/resolved.html#required-third-party-notices


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[VOTE] Apache Ambari 1.2.3-incubating RC1

[Yusaku Sako]

Hi all,

ambari-1.2.3-incubating-rc1 release candidate is now available.

Here's a summary of Ambari 1.2.3 features:
* Improved stability
* Ability to update core-site.xml properties post-install
* Ability to add and remove custom configuration properties
* New Heatmaps (Host > CPU WIO %, HBase > RegionServer
Reads/Writes/Regions/QueueSize/MemstoreSize)
* Ability to add host components on existing hosts
* Filter hosts by host health status
* Mixed OS support
* init.d scripts
* Support for Oracle Enterprise Linux 5 and 6

I have successfully deployed a 5-node cluster on RHEL 6.3 using the
instructions available at:
http://incubator.apache.org/ambari/1.2.3/installing-hadoop-using-ambari/content/index.html

SVN source tag:
https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.3-rc1

Staging site:
http://people.apache.org/~yusaku/ambari-1.2.3-incubating-rc1

PGP release keys (signed using 3ABE18B3)
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x4C3AA2723ABE18B3

One can look into the issues fixed in this release at:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%20%221.2.3%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


Here's my vote to start: +1 (binding)

Yusaku

Re: What's the difference between dormant and retired?

[Christian Grobmeier]

On Wed, May 29, 2013 at 9:36 PM, ant elder  wrote:
> I agree with Mark and John, the terms mean different things, and the term
> "retired" is reasonably well understood now and mentioned in various places
> in the Incubator documentation so wouldn't it be better to keep it as is?

Question comes up from time to time, I don't see it's well understood.

> Are there really any dormant poddlings? If so probably they are really
> retired now and they should just be changed to that.

Were there ever dormant podlings?

Maybe there is a difference in the terms itself, but when ever we saw
a podling became inactive we would discuss to retire them. Not sure
anybody ever said "oh we have no committers, but I have heard next
month comes a bunch of them". Or if there is just little activity,
would you really go to a project and tell them they are dormant now
and will retire in a few months? This all is just more overhead with
no benefit for me.

Cheers
Christian

>
>...ant
>
> On Wed, May 29, 2013 at 6:47 PM, Alan Cabrera  wrote:
>
>> If no one minds I will change them all to dormant, since all are welcome
>> back to the fold, should they so desire.
>>
>>
>> Regards,
>> Alan
>>
>> On May 27, 2013, at 12:58 PM, Christian Grobmeier 
>> wrote:
>>
>> > On Mon, May 27, 2013 at 9:17 PM, John D. Ament 
>> wrote:
>> >> I think the terms mean different things, from the incubator perspective.
>> >>
>> >> Dormant - we're not active enough right now for a full community, but
>> >> believe later on we can build it back up.
>> >> Retired - we've given up all hope of becoming a TLP, instead we think
>> it's
>> >> best to archive the code/move it to github/move it to bitbucket and
>> allow
>> >> others who want to work on it to just grab it and go.
>> >
>> > The difference is one goes to github and one does not?
>> >
>> > After this interpretation I would expect dormant projects to retire.
>> > Retired projects
>> > can be revived too. It does not matter if there was something on GitHub
>> or not.
>> >
>> > Not enough for me to maintain two terms.
>> >
>> >>
>> >> Just my 2 cents..
>> >>
>> >>
>> >> On Mon, May 27, 2013 at 2:10 PM, Christian Grobmeier <
>> grobme...@gmail.com>wrote:
>> >>
>> >>> On Mon, May 27, 2013 at 7:40 PM, Alan Cabrera 
>> >>> wrote:
>>  Yeah, I like the word dormant as well.  Should we rename them all to
>> >>> dormant?
>> >>>
>> >>> +1 from me. So far I don't see any difference in the end.
>> >>>
>> >>>
>> >>>
>> 
>>  Regards,
>>  Alan
>> 
>>  On May 27, 2013, at 10:32 AM, Upayavira  wrote:
>> 
>> > I think it was just a question of 'retiring' sounding too final.
>> Using
>> > the word 'dormant' was less threatening, and made it more feasible
>> for
>> > the podlings to go, well, dormant.
>> >
>> > Upayavira
>> >
>> > On Mon, May 27, 2013, at 05:39 PM, Alan Cabrera wrote:
>> >> They kinda sound the same.  Why didn't podlings want to retire?
>>  Does
>> >> anyone know?
>> >>
>> >>
>> >> Regards,
>> >> Alan
>> >>
>> >> On May 27, 2013, at 9:14 AM, Christian Grobmeier <
>> grobme...@gmail.com>
>> >> wrote:
>> >>
>> >>> I asked the same question in july 2011, and got a response from
>> Henri
>> >>> Yandell which I repost here:
>> >>>
>> >>> "Given the PPMC is closed down, I think it has to be retired.
>> >>>
>> >>> Dormant implies a PPMC is taking some time off.
>> >>>
>> >>> Basically this is a larger version of "don't be afraid to delete a
>> >>> line of code; it's in version control".
>> >>>
>> >>> Hen"
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Mon, May 27, 2013 at 5:38 PM, Alan Cabrera > >
>> >>> wrote:
>>  Looking at the podlings.xml and it's not clear to me what the
>> >>> difference is.  I'm sure I neglected to read some documentation bit.
>> 
>> 
>>  Regards,
>>  Alan
>> 
>> 
>> 
>> -
>>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>  For additional commands, e-mail:
>> general-h...@incubator.apache.org
>> 
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> http://www.grobmeier.de
>> >>> https://www.timeandbill.de
>> >>>
>> >>>
>> -
>> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >>> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>>
>> >>
>> >>
>> >>
>> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >
>> > -
>> > To unsubscribe, e-mail: genera

Re: [PROPOSAL] MetaModel for the Apache Incubator

[Arvind Prabhakar]

Henry,

Thank you for submitting this proposal. I am very glad to be a mentor for
this project and look forward to working with you and the broader
community. I have a couple of comments with regards to the stated proposal -

First - as noted in the proposal MetaModel has been an open source project
with contributions coming from various corners of the world. Given this
development model, do the individual contributors hold copyright over their
contributed code? If so, you will likely need their consent in order to
provide this code to the Incubator for the purposes of starting this
project.

Second - I noticed that the proposal calls out the LGPL dependency that
will be removed before sourcing the initial drop. Along the same lines, I
urge you to go through the the legal FAQ [1] to make sure that there are no
other dependencies that merit removal or special handling.

[1] http://www.apache.org/legal/resolved.html

Regards,
Arvind Prabhakar


On Tue, May 28, 2013 at 11:20 AM, Henry Saputra wrote:

> Dear ASF members,
>
> We would like to propose MetaModel for the incubator.
>
> Matt Franklin will be the Champion for this project and the proposal draft
> is available at:
>
> https://wiki.apache.org/incubator/MetaModelProposal
>
> Looking forward to all of your suggestions and feedback.
>
> Thanks,
>
> Henry Saputra
>
>
>
> -
>
> = MetaModel – uniform data access across datastores =
>
> Proposal for Apache Incubator
>
> == Abstract ==
>
> MetaModel is a data access framework, providing a common interface for
> exploration and querying of different types of datastores.
>
> == Proposal ==
>
> MetaModel provides a uniform meta-model for exploring and querying the
> structure of datastores, covering but not limited to relational databases,
> various data file formats, NoSQL databases, Salesforce.com, SugarCRM and
> more. The scope of the project is to stay domain-agnostic, so the
> meta-model will be concerned with schemas, tables, columns, rows,
> relationships etc.
>
> On top of this meta-model a rich querying API is provided which resembles
> SQL, but built using compiler-checked Java language constructs. For
> datastores that do not have a native SQL-compatible query engine, the
> MetaModel project also includes an abstract Java-based query engine
> implementation which individual datastore-modules can adapt to fit the
> concrete datastore.
>
> === Background ===
>
> The MetaModel project was initially developed by eobject.dk to service the
> DataCleaner application (http://datacleaner.org). The main requirement was
> to perform data querying and modification operations on a wide range of
> quite different datastores. Furthermore a programmatic query model was
> needed in order to allow different components to influence the query plan.
>
> In 2009, Human Inference acquired the eobjects projects including
> MetaModel. Since then MetaModel has been put to extensive use in the Human
> Inference products. The open source nature of the project was reinforced,
> leading to a significant growth in the community.
>
> MetaModel has successfully been used in a number of other open source
> projects as well as mission critical commercial software from Human
> Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org.
>
> === Rationale ===
>
> Different types of datastores have different characteristics, which always
> lead to the interfaces for these being different from one another.
> Standards like JDBC and the SQL language attempt to standardize data
> access, but for some datastore types like flat files, spreadsheets, NoSQL
> databases and more, such standards are not even implementable.
>
> Specialization in interfaces obviously has merit for optimized usage, but
> for integration tools, batch applications and or generic data modification
> tools, this myriad of specialized interfaces is a big pain. Furthermore,
> being able to query every datastore with a basic set of SQL-like features
> can be a great productivity boost for a wide range of applications.
>
> === Initial goals ===
>
> MetaModel is already a stable project, so initial goals are more oriented
> towards an adaption to the Apache ecosystem than about functional changes.
>
> We are constantly adding more datastore types to the portfolio, but the
> core modules have not had drastic changes for some time.
>
> Our focus will be on making ties with other Apache projects (such as POI,
> Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project
> to something more rememberable.
> This includes comply with Apache Software Foundation license for third
> party dependencies.
>
> == Current status ==
>
> === Meritocracy ===
>
> We intend to do everything we can to encourage a meritocracy in the
> development of MetaModel. Currently most important development and design
> decisions have been made at Human Inference, but with an open window for
> anyone to participate on mailing lists a

Re: [PROPOSAL] MetaModel for the Apache Incubator

[Henry Saputra]

Hi Arvind,

For concern 1 I will let the lead engineer Kasper to answer. I believe if
the contributors already signed copyright agreement to Human Inference then
it should be fine since it means all code contributions belong to Human
Inference which  will then be transferred to ASF.

Someone might want to help clarifying this if I am mistaken.

As for concern 2, I have scanned the master pom.xml's dependencyManagement
section and looks like all dependencies are Apache 2.0 friendly. Again,
Kasper could help verify if this is the case.


- Henry



On Wed, May 29, 2013 at 10:31 PM, Arvind Prabhakar wrote:

> Henry,
>
> Thank you for submitting this proposal. I am very glad to be a mentor for
> this project and look forward to working with you and the broader
> community. I have a couple of comments with regards to the stated proposal
> -
>
> First - as noted in the proposal MetaModel has been an open source project
> with contributions coming from various corners of the world. Given this
> development model, do the individual contributors hold copyright over their
> contributed code? If so, you will likely need their consent in order to
> provide this code to the Incubator for the purposes of starting this
> project.
>
> Second - I noticed that the proposal calls out the LGPL dependency that
> will be removed before sourcing the initial drop. Along the same lines, I
> urge you to go through the the legal FAQ [1] to make sure that there are no
> other dependencies that merit removal or special handling.
>
> [1] http://www.apache.org/legal/resolved.html
>
> Regards,
> Arvind Prabhakar
>
>
> On Tue, May 28, 2013 at 11:20 AM, Henry Saputra  >wrote:
>
> > Dear ASF members,
> >
> > We would like to propose MetaModel for the incubator.
> >
> > Matt Franklin will be the Champion for this project and the proposal
> draft
> > is available at:
> >
> > https://wiki.apache.org/incubator/MetaModelProposal
> >
> > Looking forward to all of your suggestions and feedback.
> >
> > Thanks,
> >
> > Henry Saputra
> >
> >
> >
> > -
> >
> > = MetaModel – uniform data access across datastores =
> >
> > Proposal for Apache Incubator
> >
> > == Abstract ==
> >
> > MetaModel is a data access framework, providing a common interface for
> > exploration and querying of different types of datastores.
> >
> > == Proposal ==
> >
> > MetaModel provides a uniform meta-model for exploring and querying the
> > structure of datastores, covering but not limited to relational
> databases,
> > various data file formats, NoSQL databases, Salesforce.com, SugarCRM and
> > more. The scope of the project is to stay domain-agnostic, so the
> > meta-model will be concerned with schemas, tables, columns, rows,
> > relationships etc.
> >
> > On top of this meta-model a rich querying API is provided which resembles
> > SQL, but built using compiler-checked Java language constructs. For
> > datastores that do not have a native SQL-compatible query engine, the
> > MetaModel project also includes an abstract Java-based query engine
> > implementation which individual datastore-modules can adapt to fit the
> > concrete datastore.
> >
> > === Background ===
> >
> > The MetaModel project was initially developed by eobject.dk to service
> the
> > DataCleaner application (http://datacleaner.org). The main requirement
> was
> > to perform data querying and modification operations on a wide range of
> > quite different datastores. Furthermore a programmatic query model was
> > needed in order to allow different components to influence the query
> plan.
> >
> > In 2009, Human Inference acquired the eobjects projects including
> > MetaModel. Since then MetaModel has been put to extensive use in the
> Human
> > Inference products. The open source nature of the project was reinforced,
> > leading to a significant growth in the community.
> >
> > MetaModel has successfully been used in a number of other open source
> > projects as well as mission critical commercial software from Human
> > Inference. Currently MetaModel is hosted at
> http://metamodel.eobjects.org.
> >
> > === Rationale ===
> >
> > Different types of datastores have different characteristics, which
> always
> > lead to the interfaces for these being different from one another.
> > Standards like JDBC and the SQL language attempt to standardize data
> > access, but for some datastore types like flat files, spreadsheets, NoSQL
> > databases and more, such standards are not even implementable.
> >
> > Specialization in interfaces obviously has merit for optimized usage, but
> > for integration tools, batch applications and or generic data
> modification
> > tools, this myriad of specialized interfaces is a big pain. Furthermore,
> > being able to query every datastore with a basic set of SQL-like features
> > can be a great productivity boost for a wide range of applications.
> >
> > === Initial goals ===
> >
> > MetaModel is already a stable project, so initial

Re: Process of adding a proposal to the incubator wiki

[Afkham Azeez]

Thanks Christian. I will take a look at the recent proposals.

Azeez

On Wed, May 29, 2013 at 11:49 PM, Christian Grobmeier
wrote:

> You have write access now.
>
> Please see this guide:
> http://incubator.apache.org/guides/proposal.html
>
> And please see these proposals for examples:
> http://wiki.apache.org/incubator/ProjectProposals
>
> I would look at for example BeanShell or Callback or any other recent one.
>
> Cheers
> Christian
>
>
> On Wed, May 29, 2013 at 8:01 PM, Afkham Azeez  wrote:
> > My wiki username is AfkhamAzeez
> >
> > Thanks
> >
> > --
> > Afkham Azeez
> > Sent from my phone
> > On May 29, 2013 11:17 PM, "Upayavira"  wrote:
> >
> >> You need to let us know your wiki username, and we will grant you write
> >> access.
> >>
> >> Upayavira
> >>
> >> On Wed, May 29, 2013, at 03:48 PM, Afkham Azeez wrote:
> >> > Hi folks,
> >> > Can somebody let me know what is the process of obtaining write
> access to
> >> > the incubator wiki? I need to add an incubator proposal.
> >> >
> >> > Thanks
> >> > Azeez
> >> >
> >> > --
> >> > *Afkham Azeez*
> >> > Director of Architecture; WSO2, Inc.; http://wso2.com,
> >> > *Member; Apache Software Foundation;
> >> > **http://www.apache.org/*
> >> > *
> >> > *
> >> > *email: **az...@wso2.com* * cell: +94 77 3320919
> >> > blog: **http://blog.afkham.org* *
> >> > twitter:
> >> > **http://twitter.com/afkham_azeez*
> >> > *
> >> > linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> >> > *
> >> > *
> >> > *Lean . Enterprise . Middleware*
> >> > *
> >> > *
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com,
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
*
*email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
*
*