Re: Joining IPMC member

[Marvin Humphrey]

Edward, are you not familiar with our custom of handling personnel
matters on private lists? It has not always been that way, but do you
understand why virtually all ASF projects adhere to that convention
now?

Marvin Humphrey

On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon  wrote:
> Hi,
>
> I just noticed that Mentor must be members of the Incubator PMC[1].
> Regarding MRQL podling, I'm not only Champion but also want to be a
> Mentor for MRQL project.
>
> Please add me to IPMC.
>
> 1. 
> http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor
>
> --
> Best Regards, Edward J. Yoon
> @eddieyoon
>
> -
> 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

[VOTE] Apache Ambari (incubating) 1.2.1 Release Candidate RC1.

[Mahadev Konar]

Thanks to feedback from general@incubator we have updated the release
artifacts with the following fixes:

  1. Fixed NOTICE.txt
  2. Fixed KEYS file.
  3. Removed pyc files in my svn tree (unfortunately ran mvn test
before building last time).
  4. mvn apache-rat:check passes. The exclude files are files that
cannot have Apache Headers since it breaks the run time.
  5. Website has been updated (http://incubator.apache.org/ambari/ to
fix all the issues mentioned earlier - thanks to Yusaku).
  6. Release artifacts now use md5 and sha1.

The staging Staging site is:
http://people.apache.org/~mahadev/ambari-1.2.1-incubating-rc1/

with user docs at:
http://incubator.apache.org/ambari/1.2.1/installing-hadoop-using-ambari/content/index.html
and dev docs at:
https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development

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

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

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

thanks
mahadev

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

Joining IPMC member

[Edward J. Yoon]

Hi,

I just noticed that Mentor must be members of the Incubator PMC[1].
Regarding MRQL podling, I'm not only Champion but also want to be a
Mentor for MRQL project.

Please add me to IPMC.

1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor

-- 
Best Regards, Edward J. Yoon
@eddieyoon

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

Re: [PROPOSAL] Ivory - Hadoop data management and processing platform

[Vinod Kumar Vavilapalli]

+1, this will be a great addition to the Hadoop eco-system!

The proposal looks fine overall. I quickly searched around for the name ivory, 
it looks to be a safe one, but someone needs to do due diligence?

And I think you can chose to have git as the version control if you feel like 
it.

Thanks,
+Vinod Kumar Vavilapalli

On Mar 13, 2013, at 10:00 AM, Srikanth Sundarrajan wrote:

> = Ivory Proposal =
> 
> == Abstract ==
> Ivory is a data processing and management solution for Hadoop designed for
> data motion, coordination of data pipelines, lifecycle management, and
> data discovery. Ivory enables end consumers to quickly onboard their data
> and its associated processing and management tasks on Hadoop clusters.
> 
> == Proposal ==
> Ivory will enable easy data management via declarative mechanism for
> Hadoop. Users of Ivory platform simply define infrastructure endpoints,
> data sets and processing rules declaratively. These configurations
> are expressed in such a way that the dependencies between
> these entities are explicitly described. This information about
> inter-dependencies between various entities allows Ivory to orchestrate and
> manage various data management functions.
> 
> The key use cases that Ivory addresses are:
> * Data Motion
> * Process orchestration and scheduling
> * Policy-based Lifecycle Management
> * Data Discovery
> * Operability/Usability
> 
> With these features it is possible for users to onboard their data sets
> with
> a comprehensive and holistic understanding of how, when and where their
> data
> is managed across its lifecycle. Complex functions such as retrying
> failures,
> identifying possible SLA breaches or automated handling of input data
> changes
> are now simple directives. All the administrative functions and user level
> functions are available via RESTful APIs. CLI is simply a wrapper over the
> RESTful APIs.
> 
> == Background ==
> Hadoop and its ecosystem of products have made storing and processing
> massive
> amounts of data commonplace. This has enabled numerous organizations to
> gain
> valuable insights that they never could have achieved in the past. While it
> is easy to leverage Hadoop for crunching large volumes of data, organizing
> data, managing life cycle of data and processing data is fairly involved.
> This is solved adequately well in a classic data platform involving data
> warehouses and standard ETL (extract-transform-load) tools, but remains
> largely
> unsolved today. In addition to data processing complexities, Hadoop
> presents
> new sets of challenges and opportunities relating to management of data.
> 
> Data Management on Hadoop encompasses data motion, process orchestration,
> lifecycle management, data discovery, etc. among other concerns that are
> beyond
> ETL. Ivory is a new data processing and management platform for Hadoop that
> solves this problem and creates additional opportunities by building on
> existing
> components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop
> DistCp
> etc.) without reinventing the wheel. Ivory has been in production at
> InMobi,
> going on its second year and has been managing hundreds of feeds and
> processes.
> 
> Ivory is being developed by engineers employed with InMobi, Hortonworks and
> Yahoo!. This platform addition will increase the adoption of Apache Hadoop
> by
> driving data management tractable for end users. We are therefore proposing
> to
> make Ivory an Apache open source project.
> 
> == Rationale ==
> The Ivory project aims to improve the usability of Apache Hadoop. As a
> result
> Apache Hadoop will grow its community of users by increasing the places
> Hadoop
> can be utilized and the use cases it will solve. By developing Ivory in
> Apache
> we hope to gather a diverse community of contributors, helping to ensure
> that
> Ivory is deployable for a broad range of scenarios. Members of the Hadoop
> development community will be able to influence Ivory’s roadmap, and
> contribute
> to it. We believe having Ivory as part of the Apache Hadoop ecosystem will
> be
> a great benefit to all of Hadoop's users.
> 
> == Current Status ==
> Ivory is widely deployed in production within InMobi and moving on to its
> second year. A version with a valuable set of features is developed by the
> list of initial committers and is hosted on github.
> 
> === Meritocracy ===
> Our intent with this incubator proposal is to start building a diverse
> developer
> community around Ivory following the Apache meritocracy model. We have
> wanted to
> make the project open source and encourage contributors from multiple
> organizations from the start. We plan to provide plenty of support to new
> developers and to quickly recruit those who make solid contributions to
> committer status.
> 
> === Community ===
> We are happy to report that the initial team already represents multiple
> organizations. We hope to extend the user and developer base further in the
> future and build a soli

Re: Request for edit karma for incubator pages in http://wiki.apache.org/incubator

[Henry Saputra]

It works. Thank you guys.

- Henry


On Wed, Mar 13, 2013 at 4:43 PM, Mattmann, Chris A (388J) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Fixed, you just surround the username with spaces with '[[' and with ']]'.
>
> Cheers,
> Chris
>
>
> On 3/13/13 4:41 PM, "David Crossley"  wrote:
>
> >Henry Saputra wrote:
> >> Hi,
> >>
> >> I would like to ask for karma to edit proposal for incubator project. In
> >> particular http://wiki.apache.org/incubator/MetaModelProposal
> >>
> >> My wiki user name is "Henry
> >> Saputra
> >
> >Done. However i am not sure how to deal with spaces in usernames.
> >
> >http://wiki.apache.org/incubator/ContributorsGroup
> >
> >-David
> >
> >>
> >> Thank you,
> >>
> >> Henry
> >
> >-
> >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] Graduation of EasyAnt into Ant

[edward yoon]

+1 (binding)

On 3/14/2013 12:30 AM, Matt Franklin wrote:

+1 (binding)

On Tue, Mar 12, 2013 at 11:06 AM, Nicolas Lalevée
 wrote:

Hi,

The EasyAnt community would like to graduate as an subproject of Ant.

The Ant PMC has just accepted:
http://mail-archives.apache.org/mod_mbox/ant-dev/201303.mbox/%3CBD5DB6B8-13BC-421F-800C-CE6CB21D7BF4%40hibnet.org%3E

The goal is to make EasyAnt a subproject of Ant, just like Ivy and IvyDE are.
- EasyAnt code will be brought into Ant's svn tree.
- EasyAnt committers will become Ant committers but not part of the PMC (on 5 
committers, 3
are already Ant ones, and 2 are part of Ant's PMC)
- The Ant PMC will be responsible for the code, the community, the next 
releases of EasyAnt.

Easyant has been incubating since 31/01/2011.
A release has been done the 27/02/2013.

Some usefull links:
- the EasyAnt project incubator page:
http://incubator.apache.org/projects/easyant.html
- the archive of the mailing lists
http://mail-archives.apache.org/mod_mbox/incubator-easyant-commits/
http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/
- the release
http://www.apache.org/dist/incubator/easyant

Please cast your votes over the graduation of Easyant as a subproject of Ant.

cheers,
Nicolas
-
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



--
Best Regards, Edward J. Yoon
@eddieyoon


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

Re: Request for edit karma for incubator pages in http://wiki.apache.org/incubator

[Mattmann, Chris A (388J)]

Fixed, you just surround the username with spaces with '[[' and with ']]'.

Cheers,
Chris


On 3/13/13 4:41 PM, "David Crossley"  wrote:

>Henry Saputra wrote:
>> Hi,
>> 
>> I would like to ask for karma to edit proposal for incubator project. In
>> particular http://wiki.apache.org/incubator/MetaModelProposal
>> 
>> My wiki user name is "Henry
>> Saputra
>
>Done. However i am not sure how to deal with spaces in usernames.
>
>http://wiki.apache.org/incubator/ContributorsGroup
>
>-David
>
>> 
>> Thank you,
>> 
>> Henry
>
>-
>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: Request for edit karma for incubator pages in http://wiki.apache.org/incubator

[David Crossley]

Henry Saputra wrote:
> Hi,
> 
> I would like to ask for karma to edit proposal for incubator project. In
> particular http://wiki.apache.org/incubator/MetaModelProposal
> 
> My wiki user name is "Henry
> Saputra

Done. However i am not sure how to deal with spaces in usernames.

http://wiki.apache.org/incubator/ContributorsGroup

-David

> 
> Thank you,
> 
> Henry

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

Re: Looking for a volunteer to finalize the March report

[Matt Franklin]

Working on it now.  Will have it ready in the morning for review &
comment and will submit it to the board on Friday.

-Matt

On Mon, Mar 11, 2013 at 9:52 AM, Benson Margulies  wrote:
> Thanks!
>
>
> On Mon, Mar 11, 2013 at 7:28 AM, Matt Franklin 
> wrote:
>
>> On Monday, March 11, 2013, Benson Margulies wrote:
>>
>> > If no one else is willing to take this on, I will finalize the report on
>> > Wednesday 13 March in the EDT evening, and it will contain what it
>> contains
>> > at that moment.
>>
>>
>> I can do it.
>>
>>
>> >
>> >
>> > On Sat, Mar 9, 2013 at 2:39 PM, Benson Margulies > 
>> > >wrote:
>> >
>> > > Folks,
>> > >
>> > > I will be travelling the week of 18 March, with somewhat uncertain
>> > > networking and state of jet lag.
>> > >
>> > > Would someone else be willing to tie off the report and deliver it to
>> the
>> > > board's doorstep?
>> > >
>> > > --benson
>> > >
>> > >
>> >
>>

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

Request for edit karma for incubator pages in http://wiki.apache.org/incubator

[Henry Saputra]

Hi,

I would like to ask for karma to edit proposal for incubator project. In
particular http://wiki.apache.org/incubator/MetaModelProposal

My wiki user name is "Henry
Saputra


Thank you,

Henry

Re: [PROPOSAL] Ivory - Hadoop data management and processing platform

[Jarek Jarcec Cecho]

Hi Srikanth,
I've read the proposal and documentation available on Github and the project 
seems very interesting to me. I'm currently mainly focusing on Apache Sqoop [1] 
and I can see a lot of opportunities for integration. I'll be more than happy 
to help with Ivory going forward. In case that you're open to the idea of "open 
enrolment", I'll be more than happy to sign up as initial contributor.

Jarcec

P.S. - I found few nits in the docs so I've created github pull request to fix 
them.

Links:
1: http://sqoop.apache.org/

On Wed, Mar 13, 2013 at 10:30:01PM +0530, Srikanth Sundarrajan wrote:
> = Ivory Proposal =
> 
> == Abstract ==
> Ivory is a data processing and management solution for Hadoop designed for
> data motion, coordination of data pipelines, lifecycle management, and
> data discovery. Ivory enables end consumers to quickly onboard their data
> and its associated processing and management tasks on Hadoop clusters.
> 
> == Proposal ==
> Ivory will enable easy data management via declarative mechanism for
> Hadoop. Users of Ivory platform simply define infrastructure endpoints,
> data sets and processing rules declaratively. These configurations
> are expressed in such a way that the dependencies between
> these entities are explicitly described. This information about
> inter-dependencies between various entities allows Ivory to orchestrate and
> manage various data management functions.
> 
> The key use cases that Ivory addresses are:
>  * Data Motion
>  * Process orchestration and scheduling
>  * Policy-based Lifecycle Management
>  * Data Discovery
>  * Operability/Usability
> 
> With these features it is possible for users to onboard their data sets
> with
> a comprehensive and holistic understanding of how, when and where their
> data
> is managed across its lifecycle. Complex functions such as retrying
> failures,
> identifying possible SLA breaches or automated handling of input data
> changes
> are now simple directives. All the administrative functions and user level
> functions are available via RESTful APIs. CLI is simply a wrapper over the
> RESTful APIs.
> 
> == Background ==
> Hadoop and its ecosystem of products have made storing and processing
> massive
> amounts of data commonplace. This has enabled numerous organizations to
> gain
> valuable insights that they never could have achieved in the past. While it
> is easy to leverage Hadoop for crunching large volumes of data, organizing
> data, managing life cycle of data and processing data is fairly involved.
> This is solved adequately well in a classic data platform involving data
> warehouses and standard ETL (extract-transform-load) tools, but remains
> largely
> unsolved today. In addition to data processing complexities, Hadoop
> presents
> new sets of challenges and opportunities relating to management of data.
> 
> Data Management on Hadoop encompasses data motion, process orchestration,
> lifecycle management, data discovery, etc. among other concerns that are
> beyond
> ETL. Ivory is a new data processing and management platform for Hadoop that
> solves this problem and creates additional opportunities by building on
> existing
> components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop
> DistCp
> etc.) without reinventing the wheel. Ivory has been in production at
> InMobi,
> going on its second year and has been managing hundreds of feeds and
> processes.
> 
> Ivory is being developed by engineers employed with InMobi, Hortonworks and
> Yahoo!. This platform addition will increase the adoption of Apache Hadoop
> by
> driving data management tractable for end users. We are therefore proposing
> to
> make Ivory an Apache open source project.
> 
> == Rationale ==
> The Ivory project aims to improve the usability of Apache Hadoop. As a
> result
> Apache Hadoop will grow its community of users by increasing the places
> Hadoop
> can be utilized and the use cases it will solve. By developing Ivory in
> Apache
> we hope to gather a diverse community of contributors, helping to ensure
> that
> Ivory is deployable for a broad range of scenarios. Members of the Hadoop
> development community will be able to influence Ivory’s roadmap, and
> contribute
> to it. We believe having Ivory as part of the Apache Hadoop ecosystem will
> be
> a great benefit to all of Hadoop's users.
> 
> == Current Status ==
> Ivory is widely deployed in production within InMobi and moving on to its
> second year. A version with a valuable set of features is developed by the
> list of initial committers and is hosted on github.
> 
> === Meritocracy ===
> Our intent with this incubator proposal is to start building a diverse
> developer
> community around Ivory following the Apache meritocracy model. We have
> wanted to
> make the project open source and encourage contributors from multiple
> organizations from the start. We plan to provide plenty of support to new
> developers and to quickly recruit those who make solid contributions 

[PROPOSAL] Ivory - Hadoop data management and processing platform

[Srikanth Sundarrajan]

= Ivory Proposal =

== Abstract ==
Ivory is a data processing and management solution for Hadoop designed for
data motion, coordination of data pipelines, lifecycle management, and
data discovery. Ivory enables end consumers to quickly onboard their data
and its associated processing and management tasks on Hadoop clusters.

== Proposal ==
Ivory will enable easy data management via declarative mechanism for
Hadoop. Users of Ivory platform simply define infrastructure endpoints,
data sets and processing rules declaratively. These configurations
are expressed in such a way that the dependencies between
these entities are explicitly described. This information about
inter-dependencies between various entities allows Ivory to orchestrate and
manage various data management functions.

The key use cases that Ivory addresses are:
 * Data Motion
 * Process orchestration and scheduling
 * Policy-based Lifecycle Management
 * Data Discovery
 * Operability/Usability

With these features it is possible for users to onboard their data sets
with
a comprehensive and holistic understanding of how, when and where their
data
is managed across its lifecycle. Complex functions such as retrying
failures,
identifying possible SLA breaches or automated handling of input data
changes
are now simple directives. All the administrative functions and user level
functions are available via RESTful APIs. CLI is simply a wrapper over the
RESTful APIs.

== Background ==
Hadoop and its ecosystem of products have made storing and processing
massive
amounts of data commonplace. This has enabled numerous organizations to
gain
valuable insights that they never could have achieved in the past. While it
is easy to leverage Hadoop for crunching large volumes of data, organizing
data, managing life cycle of data and processing data is fairly involved.
This is solved adequately well in a classic data platform involving data
warehouses and standard ETL (extract-transform-load) tools, but remains
largely
unsolved today. In addition to data processing complexities, Hadoop
presents
new sets of challenges and opportunities relating to management of data.

Data Management on Hadoop encompasses data motion, process orchestration,
lifecycle management, data discovery, etc. among other concerns that are
beyond
ETL. Ivory is a new data processing and management platform for Hadoop that
solves this problem and creates additional opportunities by building on
existing
components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop
DistCp
etc.) without reinventing the wheel. Ivory has been in production at
InMobi,
going on its second year and has been managing hundreds of feeds and
processes.

Ivory is being developed by engineers employed with InMobi, Hortonworks and
Yahoo!. This platform addition will increase the adoption of Apache Hadoop
by
driving data management tractable for end users. We are therefore proposing
to
make Ivory an Apache open source project.

== Rationale ==
The Ivory project aims to improve the usability of Apache Hadoop. As a
result
Apache Hadoop will grow its community of users by increasing the places
Hadoop
can be utilized and the use cases it will solve. By developing Ivory in
Apache
we hope to gather a diverse community of contributors, helping to ensure
that
Ivory is deployable for a broad range of scenarios. Members of the Hadoop
development community will be able to influence Ivory’s roadmap, and
contribute
to it. We believe having Ivory as part of the Apache Hadoop ecosystem will
be
a great benefit to all of Hadoop's users.

== Current Status ==
Ivory is widely deployed in production within InMobi and moving on to its
second year. A version with a valuable set of features is developed by the
list of initial committers and is hosted on github.

=== Meritocracy ===
Our intent with this incubator proposal is to start building a diverse
developer
community around Ivory following the Apache meritocracy model. We have
wanted to
make the project open source and encourage contributors from multiple
organizations from the start. We plan to provide plenty of support to new
developers and to quickly recruit those who make solid contributions to
committer status.

=== Community ===
We are happy to report that the initial team already represents multiple
organizations. We hope to extend the user and developer base further in the
future and build a solid open source community around Ivory.

=== Core Developers ===
Ivory is currently being developed by three engineers from InMobi –
Srikanth Sundarrajan, Shwetha G S, and Shaik Idris, two Hortonworks
employees –
Sanjay Radia and Venkatesh Seetharam. In addition, two Yahoo! employees,
Rohini Palaniswamy and Thiruvel Thirumoolan, are also involved. Srikanth,
Shwetha and Shaik are the original developers. All the engineers have built
two generations of Data Management on Hadoop, having deep expertise in
Hadoop
and are quite familiar with the Hadoop Ecosystem.

=== Alignment ===
The ASF is a

Re: [VOTE] Graduation of EasyAnt into Ant

[Matt Franklin]

+1 (binding)

On Tue, Mar 12, 2013 at 11:06 AM, Nicolas Lalevée
 wrote:
> Hi,
>
> The EasyAnt community would like to graduate as an subproject of Ant.
>
> The Ant PMC has just accepted:
> http://mail-archives.apache.org/mod_mbox/ant-dev/201303.mbox/%3CBD5DB6B8-13BC-421F-800C-CE6CB21D7BF4%40hibnet.org%3E
>
> The goal is to make EasyAnt a subproject of Ant, just like Ivy and IvyDE are.
> - EasyAnt code will be brought into Ant's svn tree.
> - EasyAnt committers will become Ant committers but not part of the PMC (on 5 
> committers, 3
> are already Ant ones, and 2 are part of Ant's PMC)
> - The Ant PMC will be responsible for the code, the community, the next 
> releases of EasyAnt.
>
> Easyant has been incubating since 31/01/2011.
> A release has been done the 27/02/2013.
>
> Some usefull links:
> - the EasyAnt project incubator page:
> http://incubator.apache.org/projects/easyant.html
> - the archive of the mailing lists
> http://mail-archives.apache.org/mod_mbox/incubator-easyant-commits/
> http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/
> - the release
> http://www.apache.org/dist/incubator/easyant
>
> Please cast your votes over the graduation of Easyant as a subproject of Ant.
>
> cheers,
> Nicolas
> -
> 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] Graduation of EasyAnt into Ant

[Matt Franklin]

On Wed, Mar 13, 2013 at 9:01 AM, John D. Ament  wrote:
> Was there a vote on the ant list to import easyant?

The vote referenced in the original e-mail was held on ant-dev.

>
>
> On Wed, Mar 13, 2013 at 8:59 AM, Stefan Bodewig  wrote:
>
>> On 2013-03-13, Bertrand Delacretaz wrote:
>>
>> > I hope the Ant PMC will consider electing deserving committers to the
>> > PMC rather sooner than later.
>>
>> The Ant PMC has done so in the past and I trust it to keep doing so ;-)
>>
>> Stefan
>>
>> -
>> 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: New podling infra setup question

[Sergio Fernández]

Hi Kevin,

in case it helps you to have a time estimation, you can take a look on 
Marmotta's podling:


https://issues.apache.org/jira/browse/INFRA-5608

which entered Incubator three months before Knox.

Cheers,

On 13/03/13 12:57, Kevin Minder wrote:

Hi Bertrand,
Yep.  We did that although I'm not sure correctly.  We have an umbrella
Jira INFRA-5913 and then 4 "sub-task" tickets so far.
INFRA-5922 Create Apache Knox JIRA
INFRA-5953 Setup svnpubsub based stie for Apache Knox podling
INFRA-5952 Create Git repo for Apache Knox podling
INFRA-5954 Setpu Confluence wiki for Apache Knox podling
In particular the ticket to setup JIRA was created on March 2nd.  Given
that it hasn't moved I want to make sure I didn't do something wrong.  In
particular, if these are the expected turn-around times I want to make sure
I get things right the first time to avoid iteration.
Thanks.
Kevin.


On Wed, Mar 13, 2013 at 4:54 AM, Bertrand Delacretaz
wrote:



Hi,

On Tue, Mar 12, 2013 at 4:00 PM, Kevin Minder  wrote:

...I'm asking this from the perspective of the Knox podling.  We
have an umbrella Jira (

https://issues.apache.org/jira/browse/INFRA-5913)...

Did you check http://www.apache.org/dev/infra-contact#requesting-podling
? It looks like you should create one sub-task ticket for each service
that you request, that should help the infra team act faster.

-Bertrand

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






--
Sergio Fernández
Salzburg Research
+43 662 2288 318
Jakob-Haringer Strasse 5/II
A-5020 Salzburg (Austria)
http://www.salzburgresearch.at

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

Re: [VOTE] Graduation of EasyAnt into Ant

[John D. Ament]

Was there a vote on the ant list to import easyant?


On Wed, Mar 13, 2013 at 8:59 AM, Stefan Bodewig  wrote:

> On 2013-03-13, Bertrand Delacretaz wrote:
>
> > I hope the Ant PMC will consider electing deserving committers to the
> > PMC rather sooner than later.
>
> The Ant PMC has done so in the past and I trust it to keep doing so ;-)
>
> Stefan
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduation of EasyAnt into Ant

[Stefan Bodewig]

On 2013-03-13, Bertrand Delacretaz wrote:

> I hope the Ant PMC will consider electing deserving committers to the
> PMC rather sooner than later.

The Ant PMC has done so in the past and I trust it to keep doing so ;-)

Stefan

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

Re: [VOTE] Graduation of EasyAnt into Ant

[Jean-Louis Boudart]

Hi Bertrand,

Thanks for your feedback, we already have a Getting Started tutorial [1],
but i agree that it is not enough accessible in the menu. We will fix it
soon.

Cheers,

[1]
http://incubator.apache.org/easyant/history/trunk/howto/GettingStarted.html


2013/3/13 Bertrand Delacretaz 

> On Tue, Mar 12, 2013 at 4:06 PM, Nicolas Lalevée
>  wrote:
> > ...The EasyAnt community would like to graduate as an subproject of Ant.
> >
> > The Ant PMC has just accepted:
> >
> http://mail-archives.apache.org/mod_mbox/ant-dev/201303.mbox/%3CBD5DB6B8-13BC-421F-800C-CE6CB21D7BF4%40hibnet.org%3E...
>
> +1
>
> with a comment about "EasyAnt committers will become Ant committers
> but not part of the PMC (on 5 committers,
> 3 are already Ant ones, and 2 are part of Ant's PMC)" in the above
> message: I hope the Ant PMC will consider electing deserving
> committers to the PMC rather sooner than later.
>
> -Bertrand
>
> (BTW: I tried to find out what EasyAnt actually does by looking at
> http://incubator.apache.org/easyant/ and it's kind of hard - you
> probably need a concrete and prominent "EasyAnt in 5 minutes" example
> in there)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Jean Louis Boudart 

Re: Please publish the incubator website, when did changes

[Daniel Shahaf]

Christian Grobmeier wrote on Wed, Mar 13, 2013 at 07:41:32 +0100:
> It would be better if the person who pushed a change (most often the
> status page) would also publish the website right after. Otherwise the
> next publisher will never knew if publication is desired or not.

(speaking on my experience with the www site, not the incubator site:)

Generally I skim the change and assume it's publishable unless it's
obviously spam (has never happened) or there's hunk at the top of the
diff saying "Don't publish me yet please".

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

Re: Please publish the incubator website, when did changes

[Edward J. Yoon]

Nice. Thanks!

On Wed, Mar 13, 2013 at 5:33 PM, Christian Grobmeier
 wrote:
> On Wed, Mar 13, 2013 at 7:53 AM, Edward J. Yoon  wrote:
>>> status page) would also publish the website right after. Otherwise the
>>
>> Thanks I see. To publish the website, do I only need to commit to
>> production like below?
>
> Even easier. Its document here:
> http://incubator.apache.org/guides/website.html
>
> When you have committed the incubator website as you did it recently,
> then you just need to go to this place:
> https://cms.apache.org/incubator/publish
> (see: generating the top level website)
>
> Fill out the form, check the diff and hit submit button. The CMS will
> take care of all the rest from there. You changes should be visible
> pretty quickly.
>
> Cheers
> Christian
>
>> 
>> Log:
>> mrql added, changes to ripple.
>>
>> Added:
>> websites/production/incubator/content/
>>   - copied from r854238, websites/staging/incubator/trunk/content/
>>
>>
>> On Wed, Mar 13, 2013 at 3:41 PM, Christian Grobmeier
>>  wrote:
>>> Hi folks,
>>>
>>> from time to time I publish the website. Usually I check the diff
>>> first, and it happens that I see changes which I didn't include. I am
>>> then required to make a quick cross check and see if they are ok.
>>>
>>> It would be better if the person who pushed a change (most often the
>>> status page) would also publish the website right after. Otherwise the
>>> next publisher will never knew if publication is desired or not.
>>>
>>> Cheers
>>> Christian
>>>
>>> --
>>> 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
>>>
>>
>>
>>
>> --
>> Best Regards, Edward J. Yoon
>> @eddieyoon
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de



-- 
Best Regards, Edward J. Yoon
@eddieyoon

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

Re: New podling infra setup question

[Kevin Minder]

Hi Bertrand,
Yep.  We did that although I'm not sure correctly.  We have an umbrella
Jira INFRA-5913 and then 4 "sub-task" tickets so far.
INFRA-5922 Create Apache Knox JIRA
INFRA-5953 Setup svnpubsub based stie for Apache Knox podling
INFRA-5952 Create Git repo for Apache Knox podling
INFRA-5954 Setpu Confluence wiki for Apache Knox podling
In particular the ticket to setup JIRA was created on March 2nd.  Given
that it hasn't moved I want to make sure I didn't do something wrong.  In
particular, if these are the expected turn-around times I want to make sure
I get things right the first time to avoid iteration.
Thanks.
Kevin.


On Wed, Mar 13, 2013 at 4:54 AM, Bertrand Delacretaz  wrote:

> Hi,
>
> On Tue, Mar 12, 2013 at 4:00 PM, Kevin Minder  wrote:
> > ...I'm asking this from the perspective of the Knox podling.  We
> > have an umbrella Jira (
> https://issues.apache.org/jira/browse/INFRA-5913)...
>
> Did you check http://www.apache.org/dev/infra-contact#requesting-podling
> ? It looks like you should create one sub-task ticket for each service
> that you request, that should help the infra team act faster.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduation of EasyAnt into Ant

[Bertrand Delacretaz]

On Tue, Mar 12, 2013 at 4:06 PM, Nicolas Lalevée
 wrote:
> ...The EasyAnt community would like to graduate as an subproject of Ant.
>
> The Ant PMC has just accepted:
> http://mail-archives.apache.org/mod_mbox/ant-dev/201303.mbox/%3CBD5DB6B8-13BC-421F-800C-CE6CB21D7BF4%40hibnet.org%3E
>  ...

+1

with a comment about "EasyAnt committers will become Ant committers
but not part of the PMC (on 5 committers,
3 are already Ant ones, and 2 are part of Ant's PMC)" in the above
message: I hope the Ant PMC will consider electing deserving
committers to the PMC rather sooner than later.

-Bertrand

(BTW: I tried to find out what EasyAnt actually does by looking at
http://incubator.apache.org/easyant/ and it's kind of hard - you
probably need a concrete and prominent "EasyAnt in 5 minutes" example
in there)

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

Re: New podling infra setup question

[Bertrand Delacretaz]

Hi,

On Tue, Mar 12, 2013 at 4:00 PM, Kevin Minder  wrote:
> ...I'm asking this from the perspective of the Knox podling.  We
> have an umbrella Jira (https://issues.apache.org/jira/browse/INFRA-5913)...

Did you check http://www.apache.org/dev/infra-contact#requesting-podling
? It looks like you should create one sub-task ticket for each service
that you request, that should help the infra team act faster.

-Bertrand

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

Re: Please publish the incubator website, when did changes

[Christian Grobmeier]

On Wed, Mar 13, 2013 at 7:53 AM, Edward J. Yoon  wrote:
>> status page) would also publish the website right after. Otherwise the
>
> Thanks I see. To publish the website, do I only need to commit to
> production like below?

Even easier. Its document here:
http://incubator.apache.org/guides/website.html

When you have committed the incubator website as you did it recently,
then you just need to go to this place:
https://cms.apache.org/incubator/publish
(see: generating the top level website)

Fill out the form, check the diff and hit submit button. The CMS will
take care of all the rest from there. You changes should be visible
pretty quickly.

Cheers
Christian

> 
> Log:
> mrql added, changes to ripple.
>
> Added:
> websites/production/incubator/content/
>   - copied from r854238, websites/staging/incubator/trunk/content/
>
>
> On Wed, Mar 13, 2013 at 3:41 PM, Christian Grobmeier
>  wrote:
>> Hi folks,
>>
>> from time to time I publish the website. Usually I check the diff
>> first, and it happens that I see changes which I didn't include. I am
>> then required to make a quick cross check and see if they are ok.
>>
>> It would be better if the person who pushed a change (most often the
>> status page) would also publish the website right after. Otherwise the
>> next publisher will never knew if publication is desired or not.
>>
>> Cheers
>> Christian
>>
>> --
>> 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
>>
>
>
>
> --
> Best Regards, Edward J. Yoon
> @eddieyoon



--
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 join the Apache Incubator

[Kasper Sørensen]

I'll update the wiki page then, and add Sameer as an "initial committer" since 
he is already working (to my understanding) on a HBase module contribution. 
I'll remove Willem Cazander for the moment since I think he's too busy right 
now to be a real initial committer.

And great news that you want to mentor this. That's very good, thank you.


From: Henry Saputra [henry.sapu...@gmail.com]
Sent: 12 March 2013 19:24
To: general@incubator.apache.org
Subject: Re: [PROPOSAL] MetaModel join the Apache Incubator

Hi Kasper,


One suggestion is to remove the "Contributors with known interest if
project is accepted in Incubator" section and only add contributors that
really want to get the project going.

I could see this could be very useful for projects like Apache Gora or
pluggable query component for Apache Drill.

I would like to volunteer to become mentor and initial committer for this
project to get it rolling.

Thanks,

Henry


On Mon, Mar 11, 2013 at 5:43 AM, Kasper Sørensen <
kasper.soren...@humaninference.com> wrote:

> Christian, your point regarding number of active contributors is valid and
> this is in deed also something that we feel is a risk to the project. I
> would say though that Human Inference is committed to continue the effort
> even if I should personally stop committing to it - reason being that the
> software stack we have here is highly dependent on MetaModel. Right now we
> are simply  in a situation where I am the key go-to-guy when there's
> MetaModel related work involved. Often we pair program on these tasks, but
> commit through my account.
>
> The other side of the story is that we have several testers that
> contribute a lot in terms of bug reports and so on. But because we're a
> closed company these reports are typically going first through our internal
> bugtracker and then into the trac system. At that point in time it will
> typically be me that enters the trac ticket. This is obviously a style of
> closedness that won't work in an Apache situation, and we need to adapt to
> that. But I also believe that we can manage that transition during
> incubation.
>
> As for the "potential" contributors - one have indicated that it is
> important to him that we move MetaModel out of the corporate setting for
> him to sign a contributors agreement. The other (Sameer) actually just told
> me that he would want to contribute anyways, but that the incubation would
> be an additional incentive, because of Apache's brand value. I don't think
> any of us wants a @apache.org email though! :)
>
> Hope that sheds a bit more light on the matter. And thanks for questioning
> this, it gives us opportunity to explain things!
>
> -Original Message-
> From: Christian Grobmeier [mailto:grobme...@gmail.com]
> Sent: 11. marts 2013 11:43
> To: general@incubator.apache.org
> Subject: Re: [PROPOSAL] MetaModel join the Apache Incubator
>
> I still think this is a nice project and it might fit right into the ASF.
> Currently I am out of time, so I cannot champion this proposal nor can I be
> the  most active mentor. Unfortunately it seems nobody else in the IPMC has
> an interest in helping this proposal.
>
> Looking at:
> http://eobjects.org/trac/timeline
>
> It seems MetaModel is more or less a single-man with a little support from
> two other devs. With less interest from the Incubator and a small dev
> community I am not sure how this project will develop here. If Kasper stops
> to commit, the project is dead.
>
> Two contributors are listed as "have an interest to commit if accepted to
> the ASF". Why didn't they contribute before? It reads a bit like they want
> to have an @apache.org e-mail address than a real interest in the project.
>
> Hopefully other IPMC'lers find some time to comment here too.
>
>
>
>
> On Mon, Mar 11, 2013 at 10:04 AM, Kasper Sørensen <
> kasper.soren...@humaninference.com> wrote:
> > Just for reference, I'd add to Sameer's mail that the proposal is here:
> >
> > http://wiki.apache.org/incubator/MetaModelProposal
> >
> > We would very much appreciate if one or more apache champions will help
> us to get further in the process.
> >
> > Kasper
> >
> > -Original Message-
> > From: sameer arora [mailto:sameer11...@gmail.com]
> > Sent: 10. marts 2013 05:50
> > To: general@incubator.apache.org
> > Subject: RE: [PROPOSAL] MetaModel join the Apache Incubator
> >
> > Hi,
> >
> > I have been working on Metamodel as a developer for the last 1.5
> years.We are also working on adding Hbase support to Metamodel to cater the
> needs of today.
> >
> > It would be great to see Metamodel accepted at Apache Incubator, surely
> the efforts from us would gain some momentum.
> >
> > Sameer
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
>
> --
> http://www.grobmeier.