Please add me to the incubator's contributors group

[Siddharth Anand]

Siddharth Anand

Re: Please add me to the incubator's contributors group

[Siddharth Anand]

Hmn.. I agree the space can be problematic.. so I am trying to change my
user name under settings, but it looks like it needs me to change my email
address as well.

On Wed, Mar 16, 2016 at 5:06 PM, Siddharth Anand  wrote:

> Yes. Thanks.
>
> I had tried to followed the recommended convention of "FirstnameLastname",
> but it was taken. So, I used "Siddharth Anand" (with a space) and it
> worked.
>
>
>
>
> On Wed, Mar 16, 2016 at 4:57 PM, Nick Burch  wrote:
>
>> On Wed, 16 Mar 2016, Siddharth Anand wrote:
>>
>>> Siddharth Anand
>>>
>>
>> If you can tell us what username you signed up to the incubator wiki
>> with, then one of us can do so for you
>>
>> Nick
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

Request for permission to edit wiki

[Siddharth Anand]

Hi, I'd like to get permission to edit wiki.
My user name is Siddharth Anand

Thank you

Request for Wiki Edit Access: SiddharthAnand

[Siddharth Anand]

Can I please be added to the incubator wiki Contributors group?  My wiki
login is SiddharthAnand.  I would like to edit my Airflow Incubator
Proposal (https://wiki.apache.org/incubator/AirflowProposal) in response to
feedback.

Thank you,
-s (Sid)

Re: Please add me to the incubator's contributors group

[Siddharth Anand]

Yes. Thanks.

I had tried to followed the recommended convention of "FirstnameLastname",
but it was taken. So, I used "Siddharth Anand" (with a space) and it
worked.




On Wed, Mar 16, 2016 at 4:57 PM, Nick Burch  wrote:

> On Wed, 16 Mar 2016, Siddharth Anand wrote:
>
>> Siddharth Anand
>>
>
> If you can tell us what username you signed up to the incubator wiki with,
> then one of us can do so for you
>
> Nick
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Please add me to the incubator's contributors group

[Siddharth Anand]

Siddharth Anand

My wiki username is above. I would like to add my incubator proposal as I
have a champion and 3 mentors and have received the go-ahead from them.

-s

[PROPOSAL] : Airflow

[Siddharth Anand]

https://wiki.apache.org/incubator/AirflowProposal

Thoughts and comments are welcome!
-s (Sid)

Re: Please add me to the incubator's contributors group

[Siddharth Anand]

I have changed my user name to `r39132` (the same as my twitter and github
handle)

Please add that user name to the group that can edit wiki. Sorry for any
inconvenience.

On Wed, Mar 16, 2016 at 5:09 PM, Siddharth Anand  wrote:

> Hmn.. I agree the space can be problematic.. so I am trying to change my
> user name under settings, but it looks like it needs me to change my email
> address as well.
>
> On Wed, Mar 16, 2016 at 5:06 PM, Siddharth Anand  wrote:
>
>> Yes. Thanks.
>>
>> I had tried to followed the recommended convention of
>> "FirstnameLastname", but it was taken. So, I used "Siddharth Anand" (with a
>> space) and it worked.
>>
>>
>>
>>
>> On Wed, Mar 16, 2016 at 4:57 PM, Nick Burch  wrote:
>>
>>> On Wed, 16 Mar 2016, Siddharth Anand wrote:
>>>
>>>> Siddharth Anand
>>>>
>>>
>>> If you can tell us what username you signed up to the incubator wiki
>>> with, then one of us can do so for you
>>>
>>> Nick
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>
>

Re: [PROPOSAL] : Airflow

[Siddharth Anand]

Hi Stian,
Thanks for the feedback. We are committed to moving towards Apache
community-friendly licensing as documented on
http://www.apache.org/legal/resolved.html#category-x

I've added this to our Roadmap:
https://github.com/airbnb/airflow/wiki/Roadmap and I expect to tackle it
during the incubation phase.

Regarding our Google group - yes. We will move to the
d...@airflow.incubator.apache.org mailing list.  We currently have *258
members*, with about 10 new members being added daily! If you have any
thoughts on how to make that transition more amenable to our community,
they are welcome. For one, the google group offers more functionality than
the old-style mailing lists. I don't mind moving. I would like to keep the
old group's messages searchable and provide an announcement feature to
point people to the Apache mailing list so they know where to go next if
they land on the Google group. Some threads will unfortunately be
decapitated, but we can provide a few months' time for our users to
transition to the Apache mailing lists, wrapping up topic threads or
copying them over.  We will also need to stop accepting new members and
posts in the existing group, but I think that is pretty simple to do.

Thanks for the heads up on CWL and Taverna. We will definitely look into
both. On our side, our user base is growing faster than we can keep up.
Hence, we are investing in growing the committer base and documentation,
and in leveraging processes in order to better meet the growing needs of
our community. We hope to reduce turn-around time on PR reviews/merges,
time between releases, bringing new developers on board, and converting
contributors to committers.


-s

On Mon, Mar 21, 2016 at 4:23 PM, Stian Soiland-Reyes 
wrote:

> Airflow sounds like an interesting workflow project!
>
>
> You will need to review the licenses of dependencies - some of them
> are not compatible with ASF policy [1], e.g.
>
> https://pypi.python.org/pypi/psycopg2
> is LGPL, which is not permitted.
>
> (I didn't check all of them)
>
> You may be able to work around this particular one if you are using
> Python's DB API 2.0 and don't have an explicit dependency on psycopg2
> (e.g. so a downstream user can reasonably use Airflow without
> psycopg2)
>
>
> (Note: you can solve this as part of incubation process - but say if
> your project strongly used 15 GPL and LGPL dependencies, then your
> project might want to reconsider if it would be worth the effort)
>
>
>
> I recognize the challenge of engaging extension developers to also
> care about the 'core'. Moving to an "Apache Way" open development will
> probably help for this, as all dev discussions are in the open. Is
> your plan to move the existing Airflow Google Groups to what will be
> the d...@airflow.incubator.apache.org mailing list?
>
>
> Have you been talking to the SciDap folks doing Common Workflow
> Language [3] support with Airflow? That could be one angle to look at
> increasing the user base. We're also working on Docker and CWL support
> in Apache Taverna [4] - so I'm interested in seeing what we could have
> in common!
>
>
> [1] http://www.apache.org/legal/resolved.html
> [2] https://github.com/SciDAP/scidap
> [3] http://www.commonwl.org/
> [4] http://taverna.incubator.apache.org/
>
> On 17 March 2016 at 00:28, Siddharth Anand 
> wrote:
> > https://wiki.apache.org/incubator/AirflowProposal
> >
> > Thoughts and comments are welcome!
> > -s (Sid)
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/-0001-9842-9718
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Accept Airflow into the Incubator

[Siddharth Anand]

Following the discussion earlier:
https://s.apache.org/AirflowDiscussion

I would like to call a VOTE for accepting Airflow as a new incubator project.

The proposal is available at: https://wiki.apache.org/incubator/AirflowProposal

The proposal is also included at the bottom of this email.

Vote is open until at least Tues, 29 March 2016, 23:59:00 PDT
[ ] +1 accept Airflow into the Apache Incubator
[ ] ±0
[ ] -1 because...

+1 (non-binding)

Thanks,
-s (Sid)


== Abstract ==

Airflow is a workflow automation and scheduling system that can be
used to author and manage data pipelines.

== Proposal ==

Airflow provides a system for authoring and managing workflows a.k.a.
data pipelines a.k.a. DAGs (Directed Acyclic Graphs). The developer
authors DAGs in Python using an Airflow-provided framework. He/She
then executes the DAG using Airflow’s scheduler or registers the DAG
for event-based execution. A web-based UI provides the developer with
a range of options for managing and viewing his/her data pipelines.
Background

Airflow was developed at Airbnb to enable easier authorship and
management of DAGs than were possible with existing solutions such as
Oozie and Azkaban. For starters, both Oozie and Azkaban rely on one or
more XML or property files to be bundled together to define a
workflow. This separation of code and config can present a challenge
to understanding the DAG - in Azkaban, a DAG’s structure is reflected
by its file system tree and one can find himself/herself traversing
the file system when inspecting or changing the structure of the DAG.
Airflow workflows, on the other hand, are simply and elegantly defined
in Python code, often a single file. Airflow merges the powerful
Web-based management aspects of projects like Azkaban and Oozie with
the simplicity and elegance of defining workflows in Python. Airflow,
less than a year old in terms of its Open Source launch, is currently
used in production environments in more than 30 companies and boasts
an active contributor list of more than 100 developers, the vast
majority of which (>95%) are outside of Airbnb.

We would like to share it with the ASF and begin developing a
community of developers and users within Apache.

== Rationale ==

Many organizations (>30) already benefit from running Airflow to
manage data pipelines. Our 100+ contributors continue to provide
integrations with 3rd party systems through the implementation of new
hooks and operators, both of which are used in defining the tasks that
compose workflows.

== Current Status ==

=== Meritocracy ===

Our intent with this incubator proposal is to start building a diverse
developer community around Airflow following the Apache meritocracy
model. Since Airflow was open-sourced in mid-2015, we have had fast
adoption and contributions by multiple organizations the world over.
We plan to continue to support new contributors and we will work to
actively promote those who contribute significantly to the project to
committers.

=== Community ===

Airflow is currently being used in over 30 companies. We hope to
extend our contributor base significantly and invite all those who are
interested in building large-scale distributed systems to participate.

=== Core Developers ===

Airflow is currently being developed by four engineers: Maxime
Beauchemin, Siddharth Anand, Bolke de Bruin, and Chris Riccomini.
Chris is a member of the Apache Samza PMC and a contributor to various
Apache projects, including Apache Kafka and Apache YARN. Maxime,
Siddharth, and Bolke have contributed to Airflow.

=== Alignment ===
The ASF is the natural choice to host the Airflow project as its goal
of encouraging community-driven open-source projects fits with our
vision for Airflow.

== Known Risks ==

=== Orphaned Products ===

The core developers plan to work part time on the project. There is
very little risk of Airflow being abandoned as all of our companies
rely on it.

=== Inexperience with Open Source ===

All of the core developers have experience with open source
development. Chris is a member of the Apache Samza PMC and a
contributor to various Apache projects, including Apache Kafka and
Apache YARN. Bolke is contributor on multiple open source projects and
a few Apache projects as well, including Apache Hive, Apache Hadoop,
and Apache Ranger.

=== Homogeneous Developers ===

The current core developers are all from different companies. Our
community of 100 contributors hail from over 30 different companies
from across the world.

=== Reliance on Salaried Developers ===

Currently, the only developer paid to work on this project is Maxime.

=== Relationships with Other Apache Products ===

Airflow is deeply integrated with Apache products. It currently
provides hooks and operators to enable workflows to leverage Apache
Pig, Apache Hive, Apache Spark, Apache Sqoop, Apache Hadoop, etc… We
plan to add support for other Apache projects in the future.

=== An Excessive Fascination with the Apache

Re: Podling name search - early or late?

[Siddharth Anand]

+1 for clearing the name early based on the many comments already listed.

-s
p.s. I'm a committer on Airflow.

On Fri, May 27, 2016 at 6:43 PM, John D. Ament 
wrote:

> TBH, I'm a bit surprised with the answer provided by Shane in the JIRA.  My
> understanding has been that branding is an important part of incubation, so
> hearing that it should come near the conclusion is a bit perplexing.
>
> Hopefully he can provide some clarification of it.
>
> John
>
> On Fri, May 27, 2016 at 7:19 PM P. Taylor Goetz  wrote:
>
> > +1 for doing it early. Waiting to the bitter end can delay graduation,
> and
> > a podling rename can be disruptive.
> >
> > IMO part of incubation is about establishing and learning how to protect
> > your brand. Establishing a brand is not an exercise you want to have to
> do
> > twice.
> >
> > -Taylor
> >
> > > On May 27, 2016, at 6:37 PM, Mattmann, Chris A (3980) <
> > chris.a.mattm...@jpl.nasa.gov> wrote:
> > >
> > > I’ve always done the podling name search right away. I’m not
> > > sure where that comment came from from Shane - my experience
> > > has been the opposite.
> > >
> > > ++
> > > Chris Mattmann, Ph.D.
> > > Chief Architect
> > > Instrument Software and Science Data Systems Section (398)
> > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > > Office: 168-519, Mailstop: 168-527
> > > Email: chris.a.mattm...@nasa.gov
> > > WWW:  http://sunset.usc.edu/~mattmann/
> > > ++
> > > Director, Information Retrieval and Data Science Group (IRDS)
> > > Adjunct Associate Professor, Computer Science Department
> > > University of Southern California, Los Angeles, CA 90089 USA
> > > WWW: http://irds.usc.edu/
> > > ++
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> On 5/27/16, 3:35 PM, "Stian Soiland-Reyes"  wrote:
> > >>
> > >> I think the point is that name search is not a blocker for doing
> > incubator
> > >> releases - it can be time consuming and there are many other
> > "bureaucratic"
> > >> steps to get through in the beginning like IP clearance and license
> > >> checking.
> > >>
> > >> For brand new projects, name search can therefore be delayed - their
> > name
> > >> is less important as their community will be fully within the
> incubator
> > to
> > >> start with.
> > >>
> > >> However I think for established distributed projects moving to the
> > >> incubator it is more important to sort name earlier - it can be
> > disruptive
> > >> enough for the community with the change of infrastructure and the
> > >> formalities, so you may might not want to confuse them again with a
> new
> > >> name many months later - effectively changing all infrastructure
> again.
> > >>
> > >> Some podlings found their name could be tricky trademark wise and had
> to
> > >> change, but getting together and deciding a new name can even be a
> good
> > >> thing, as it breaks any legacy corporate ownership and builds a new
> > >> collective identity.
> > >>> On 27 May 2016 7:20 p.m., "Balaji Ganesan" 
> > wrote:
> > >>>
> > >>> Podling namesearch is essential step that needs to be completed
> before
> > the
> > >>> podling graduates. There is no specific guidance, as far as i know,
> on
> > what
> > >>> stage of podling you should do it.
> > >>>
> > >>> That said, it would be better to do this early enough and get
> approval
> > on
> > >>> the name. If there is any reason to change name, due to a conflict,
> it
> > is
> > >>> better to do it before releases are made and community starts
> building
> > >>> around. Name change is always a pain.
> > >>>
> >  On Fri, May 27, 2016 at 11:07 AM, Jakob Homan 
> > wrote:
> > 
> >  We were getting ready to start the PNS for Airflow when I came
> across
> >  this comment from Shane in regards to Kudu:
> > 
> >  https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-93
> >  "This looks like a pretty good set of search data, but we usually
> >  don't work on resolving PODLINGNAMESEARCHES until a podling is
> clearly
> >  established, has a release, community is building, etc."
> > 
> >  This is surprising to me and different than the last time I was
> >  involved in an incubating project.  Is this correct?
> > 
> >  It seems more useful to determine if a name can be used early in the
> >  incubation, before releases, talks, thousands of lines code, package
> >  names, emotional attachments, etc.  In the event that a podling
> fails,
> >  nothing is lost by okaying the name early, assuming we don't attempt
> >  to trademark (which we haven't been for non-TLPs, I believe).
> > 
> >  Any thoughts?  Any reason not to start doing the PNS for Airflow
> now?
> > 
> >  Thanks,
> >  Jakob
> > 
> > 
> --

Need write access to the Incubator wiki

[siddharth anand]

Hello!
My user (Siddharth Anand) needs write access to the Incubator wiki so that
I can fill out the October2016 Apache Airflow Podling Report due tomorrow.
I don't have write access to that report page.

-s (Sid)

Re: Wiki Write Access

[siddharth anand]

The same happened to my account -- user id : Siddharth Anand

I used to submit the monthly podling reports for Airflow. Now that we are
3-monthly/quarterly, I no longer have write access.

-s

On Tue, Oct 4, 2016 at 3:45 PM, John D. Ament  wrote:

> Your account is still present.  Are you sure you're logged in?  Just double
> check, force a hard refresh, perhaps even log out and back in again.
>
> John
>
> On Tue, Oct 4, 2016 at 5:35 PM Ellison Anne Williams <
> eawilli...@apache.org>
> wrote:
>
> > My wiki write access appears to have evaporated somehow. Can you please
> > write access for 'EllisonAnneWilliams' ?
> >
> > Thanks!
> >
>

Re: Wiki Write Access

[siddharth anand]

FYI, Nick Burch reinstated my perms 2 hours ago. I now see the Edit (Text)
link. Thx.

-s

On Tue, Oct 4, 2016 at 5:26 PM, siddharth anand  wrote:

> The same happened to my account -- user id : Siddharth Anand
>
> I used to submit the monthly podling reports for Airflow. Now that we are
> 3-monthly/quarterly, I no longer have write access.
>
> -s
>
> On Tue, Oct 4, 2016 at 3:45 PM, John D. Ament 
> wrote:
>
>> Your account is still present.  Are you sure you're logged in?  Just
>> double
>> check, force a hard refresh, perhaps even log out and back in again.
>>
>> John
>>
>> On Tue, Oct 4, 2016 at 5:35 PM Ellison Anne Williams <
>> eawilli...@apache.org>
>> wrote:
>>
>> > My wiki write access appears to have evaporated somehow. Can you please
>> > write access for 'EllisonAnneWilliams' ?
>> >
>> > Thanks!
>> >
>>
>
>

Re: [Incubator Wiki] Trivial Update of "October2016" by jonesde

[Siddharth Anand]

I've added my 10 to
https://cwiki.apache.org/confluence/display/AIRFLOW/Whittling+down+PR+List

 Li Xuanji, Sumit, Dan, Arthur, Max, Bolke, Chris, Jeremiah et al. please
add yours to the list.

-s

On Tue, Oct 4, 2016 at 11:25 AM, Apache Wiki  wrote:

> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Incubator Wiki"
> for change notification.
>
> The "October2016" page has been changed by jonesde:
> https://wiki.apache.org/incubator/October2016?action=diff&rev1=15&rev2=16
>
>
> [ ](freemarker) Jacopo Cappellato
> [ ](freemarker) Jean-Frederic Clere
> -   [ ](freemarker) David E. Jones
> +   [X](freemarker) David E. Jones
> [X](freemarker) Ralph Goers
> [ ](freemarker) Sergio Fernández
>
>
> -
> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> For additional commands, e-mail: cvs-h...@incubator.apache.org
>
>

Re: [Incubator Wiki] Trivial Update of "October2016" by jonesde

[Siddharth Anand]

Ugh.. sorry.. wrong thread.

-s

On Tue, Oct 4, 2016 at 1:04 PM, Siddharth Anand  wrote:

> I've added my 10 to https://cwiki.apache.org/confluence/display/AIRFLOW/
> Whittling+down+PR+List
>
>  Li Xuanji, Sumit, Dan, Arthur, Max, Bolke, Chris, Jeremiah et al. please
> add yours to the list.
>
> -s
>
> On Tue, Oct 4, 2016 at 11:25 AM, Apache Wiki  wrote:
>
>> Dear Wiki user,
>>
>> You have subscribed to a wiki page or wiki category on "Incubator Wiki"
>> for change notification.
>>
>> The "October2016" page has been changed by jonesde:
>> https://wiki.apache.org/incubator/October2016?action=diff&rev1=15&rev2=16
>>
>>
>> [ ](freemarker) Jacopo Cappellato
>> [ ](freemarker) Jean-Frederic Clere
>> -   [ ](freemarker) David E. Jones
>> +   [X](freemarker) David E. Jones
>> [X](freemarker) Ralph Goers
>> [ ](freemarker) Sergio Fernández
>>
>>
>> -
>> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: cvs-h...@incubator.apache.org
>>
>>
>

Fwd: Github Mirroring currently broken

[siddharth anand]

FYI!
Several projects have already reported this (e.g. Nifi, spark website,
brooklyn-server, carbondata, zeppelin, etc...) -- but Apache github
mirroring broke yesterday (Saturday)... and it's a blocker for (every?)
incubator project on Github currently. Hoping it gets resolved soon.

-s


-- Forwarded message --
From: siddharth anand 
Date: Sun, Nov 20, 2016 at 12:10 PM
Subject: Github Mirroring currently broken
To: d...@airflow.incubator.apache.org


Committers/Maintainers,
The Apache Airflow Github mirror is not synchronizing. I've filed a ticket.
It looks like, as of now, 2 other Apache projects (nifi & brooklyn-server)
have reported the same issue.

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

This means that although we are successfully merging to Apache master at
https://git-wip-us.apache.org/repos/asf/incubator-airflow.git, the changes
are not being mirrored to g...@github.com:apache/incubator-airflow.git. This
affects things like rebasing of PRs.. and I've opened the tickets at a
Blocker.

-s

Re: Github Mirroring currently broken

[siddharth anand]

And it's fixed now .. woo hoo! We're back in business! Props to Apache
Infra!

-s

On Sun, Nov 20, 2016 at 12:16 PM, siddharth anand  wrote:

> FYI!
> Several projects have already reported this (e.g. Nifi, spark website,
> brooklyn-server, carbondata, zeppelin, etc...) -- but Apache github
> mirroring broke yesterday (Saturday)... and it's a blocker for (every?)
> incubator project on Github currently. Hoping it gets resolved soon.
>
> -s
>
>
> ------ Forwarded message --
> From: siddharth anand 
> Date: Sun, Nov 20, 2016 at 12:10 PM
> Subject: Github Mirroring currently broken
> To: d...@airflow.incubator.apache.org
>
>
> Committers/Maintainers,
> The Apache Airflow Github mirror is not synchronizing. I've filed a
> ticket. It looks like, as of now, 2 other Apache projects (nifi &
> brooklyn-server) have reported the same issue.
>
> https://issues.apache.org/jira/browse/INFRA-12949
>
> This means that although we are successfully merging to Apache master at
> https://git-wip-us.apache.org/repos/asf/incubator-airflow.git, the
> changes are not being mirrored to g...@github.com:apache/incub
> ator-airflow.git. This affects things like rebasing of PRs.. and I've
> opened the tickets at a Blocker.
>
> -s
>
>

Re: [CANCEL][VOTE] Release Apache Airflow 1.8.0

[siddharth anand]

Good call Bolke.
-s

On Fri, Feb 24, 2017 at 12:30 AM, Bolke de Bruin  wrote:

> I am cancelling the vote fro Airflow 1.8.0 although 72h passed and we
> received a conditional +1 (binding) from Jakob. This is because we feel the
> license issues, packaging issues should be addressed prior to release and
> that we found a blocker at the same time.
>
> We expect to raise a new vote shortly.
>
> - Bolke
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

[siddharth anand]

+1 (non-binding)

On Thu, Mar 16, 2017 at 12:46 PM, Jakob Homan  wrote:

> +1 binding.
>
> md5/asc/LICENSE/NOTICE/DISCLAIMER/headers all look good.
>
> NITs for next release:
> * setup.cfg still has Maxime listed as author and email.
> * usually the artifacts are named apache-whatever, rather than
> whatever-apache.
>
> Thanks,
> Jakob
>
>
> On 16 March 2017 at 10:46, Maxime Beauchemin 
> wrote:
> > +1 (non-binding)
> >
> > On Thu, Mar 16, 2017 at 9:59 AM, Jeremiah Lowin 
> wrote:
> >
> >> +1 (non-binding)
> >>
> >>
> >> On Thu, Mar 16, 2017 at 12:56 PM Arthur Wiedmer 
> wrote:
> >>
> >> > +1 (non-binding)
> >> >
> >> > Best,
> >> > Arthur
> >> >
> >> > On Thu, Mar 16, 2017 at 9:42 AM, Chris Riccomini <
> criccom...@apache.org>
> >> > wrote:
> >> >
> >> > > +1 (non-binding)
> >> > >
> >> > > On Thu, Mar 16, 2017 at 9:32 AM, Bolke de Bruin 
> >> > wrote:
> >> > >
> >> > > > Hello Incubator PMC’ers,
> >> > > >
> >> > > > The Apache Airflow community has voted and approved the proposal
> to
> >> > > > release Apache Airflow 1.8.0 (incubating) based on 1.8.0 Release
> >> > > Candidate
> >> > > > 5. We now kindly request the Incubator PMC members to review and
> vote
> >> > on
> >> > > > this incubator release. If the vote is successful we will rename
> >> > release
> >> > > > candidate 4 to final.
> >> > > >
> >> > > > Airflow is a platform to programmatically author, schedule and
> >> monitor
> >> > > > workflows. Use airflow to author workflows as directed acyclic
> graphs
> >> > > > (DAGs) of tasks. The airflow scheduler executes your tasks on an
> >> array
> >> > of
> >> > > > workers while following the specified dependencies. Rich command
> line
> >> > > > utilities make performing complex surgeries on DAGs a snap. The
> rich
> >> > user
> >> > > > interface makes it easy to visualize pipelines running in
> production,
> >> > > > monitor progress, and troubleshoot issues when needed. When
> workflows
> >> > are
> >> > > > defined as code, they become more maintainable, versionable,
> >> testable,
> >> > > and
> >> > > > collaborative.
> >> > > >
> >> > > > The Apache Airflow-1.8.0-incubating release candidate is now
> >> available
> >> > > > with the following artefacts for a project vote:
> >> > > >
> >> > > > * [VOTE] Thread:*
> >> > > > http://mail-archives.apache.org/mod_mbox/incubator-
> >> > > > airflow-dev/201703.mbox/%3cB1833A3A-05FB-4112-B395-
> >> > > > 135caf930...@gmail.com%3e  >> > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> >> > > 3CB1833A3A-05FB-4112-B395-
> >> > > > 135caf930...@gmail.com%3E>
> >> > > >
> >> > > > *[RESULT][VOTE] Thread:*
> >> > > > http://mail-archives.apache.org/mod_mbox/incubator-
> >> > > > airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> >> > > > b2273660a...@gmail.com%3e  >> > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> >> > > 3c59BC8C2B-12E2-4DE3-9555-
> >> > > > b2273660a...@gmail.com%3e>
> >> > > >
> >> > > > *The release candidate(s) to be voted on is available at:*
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/> or
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> >> > > > airflow-1.8.0rc5+apache.incubating.tar.gz <
> https://dist.apache.org/
> >> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> >> > > apache.incubating.tar.gz
> >> > > > >
> >> > > >
> >> > > > *Git branch*
> >> > > > https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> >> > > > https://github.com/apache/incubator-airflow/tree/v1-8-stable> or
> >> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> >> > > > git;a=tree;h=refs/heads/v1-8-stable;hb=refs/heads/v1-8-stable <
> >> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> >> > > > airflow.git;a=tree;h=refs/heads/v1-8-stable;hb=refs/
> >> heads/v1-8-stable>
> >> > > >
> >> > > > *Git tag*
> >> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> >> > > > git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2 <
> >> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> >> > > > airflow.git;a=shortlog;h=f4760c320a29be62469799355e76ef
> a42d0b6bb2>
> >> > > >
> >> > > > PGP signature
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> >> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.asc <
> >> > https://dist.apache.org/
> >> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> >> > > > apache.incubating.tar.gz.asc>
> >> > > >
> >> > > > MD5/SHA Hashes:
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> >> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.md5 <
> >> > https://dist.apache.org/
> >> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> >> > > > apache.incubating.tar.gz.md5>
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> >> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.sha <
> >> > htt

Re: The state of Sirona

[siddharth anand]

Nicely put.
Sid

On Sat, Apr 15, 2017 at 11:55 AM, Ted Dunning  wrote:

> I think that we need to get over thinking of this state of affairs is a
> "failure".
>
> It is just one of the many different possible outcomes for incubation. To
> my mind, having multiple possible outcomes is a *feature*, not a bug.
>
> Obviously, we should not admit podlings that we aren't committed to helping
> become TLP's and we should help those podlings become TLP's. But there are
> lots of different possible outcomes and only the podling can really
> determine which outcome it will have.
>
> It is a fact of nature that we cannot always know whether a new podling
> really has the right intent and contributor mix to become a good TLP.
> Sometimes it is apparent that the project will be a great fit and sometimes
> it is apparent that it won't be, but many times we won't exactly know.
> There will be cases where a community will melt away and there will be
> cases where a community really didn't get the point of the Apache license.
> In many cases, the world just changes and by the time it is time to
> graduate, the project just isn't the right thing to do any more.
>
> As such, I think we need to (somewhat) over-admit podlings when there is
> doubt. That doesn't mean admit projects that just won't ever succeed, but
> it does mean we should be a little generous in terms of admission. We
> should vote to admit in cases of some doubt.
>
> If that is true, then we have to expect that there will be a variety of
> outcomes and we have to take that as a consequence of our initial
> generosity. This is not a cause for tears. Frankly, every project that
> becomes an obvious candidate for retirement means that there is another
> successful project that we admitted even though there was doubt.
>
> IF it is time to retire Sirona, let's just do it.
>
>
>
> On Sat, Apr 15, 2017 at 10:09 AM, Pierre Smits 
> wrote:
>
> > It is very sad to see a project failing at growing a community. Looking
> at
> > the various public sources, I see:
> >
> >- just 2 pull request since its start in incubation
> >- no postings on the user ml since December 2015
> >- only 3 committing contributors since start in incubation
> >- No description (readme) in github
> >- No mission statement/goal description of the project on the
> project's
> >home page
> >
> > I fear this will not turn around due to the lack of interest in the world
> > beyond the project. At the moment I am inclined to say: time for
> > retirement.
> >
> > Best regards,
> >
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Sat, Apr 15, 2017 at 5:07 PM, Jean-Baptiste Onofré 
> > wrote:
> >
> > > Hi John
> > >
> > > I think you did the right thing by bringing the point on the table.
> > >
> > > AFAIR I already stated some months ago that, regarding the activity and
> > > regarding the community around, we should really think about retirement
> > of
> > > Sirona. Some can argue about the fact that Sirona is a "stable" project
> > > that's not really valid: if it's valid we should see questions, feature
> > > requests, etc coming from the user community. And obviously it's not
> the
> > > case. So I think that Sirona is just use for specific use cases in a
> very
> > > limited community.
> > >
> > > My €0.01 ;)
> > >
> > > Regards
> > > JB
> > >
> > > On Apr 15, 2017, 15:49, at 15:49, "John D. Ament" <
> johndam...@apache.org
> > >
> > > wrote:
> > > >All,
> > > >
> > > >I hate bringing up these topics.  But I think we as the IPMC we have
> to
> > > >take a close look at how Sirona is running and figure out what to do
> > > >next.
> > > >
> > > >- The podling has not reported in several months (this is their 3rd
> > > >attempt
> > > >at monthly).
> > > >- Every time the thought of retirement comes up, a little bit of
> > > >activity
> > > >on the project happens.  It doesn't sustain.
> > > >- There is some limited project history, but no real contribution in 6
> > > >months ( https://github.com/apache/sirona/commits/trunk )
> > > >
> > > >I personally don't want to see projects go, and I don't want to force
> a
> > > >project to leave, but at the same time I'm not convinced that there's
> > > >enough of a community behind the project to sustain it going forward.
> > > >They've put together a limited plan to get a release out the door, but
> > > >other than that I'm not sure they're going to be able to move forward.
> > > >
> > > >So I want to ask, as the IPMC, do we want to give them time to
> regroup?
> > > >
> > > >John
> > >
> >
>

Request to join IPMC

[siddharth anand]

Hi Folks!
I'd like to join the IPMC. I'm a committer/PPMC on the Apache Airflow
podling.
-s