date:20180909

Re: Call for fixes for Airflow 1.10.1

2018-09-09 Thread Ash Berlin-Taylor

I've (re)created the v1-10-test branch with some of the fixes cherry-picked in. 
I can't give much time this week (as what spare time I have is being used up 
working on my talk) but I'll work more on this towards the end of next week.

I'll look at resolved Jira tickets targeted with a fix version of 1.10.1 (i.e. 
if you want it in 1.10.1, merge the pr into master and also mark the Jira as 
fix in 1.10.1 and I'll work on cherry-picking the fixes. If they can be. If it 
is diffucult/has other things to cherry pick in I might change the fix version 
on you.)

-ash


> On 9 Sep 2018, at 19:22, Ash Berlin-Taylor  wrote:
> 
> On 9 September 2018 18:19:40 BST, Bolke de Bruin  wrote:
> You can already add them to v1-10-test. 
> 
> Normally we are a bit cautious to this if you are not the release manager to 
> ensure that he/she knows what the state is. 
> 
> B
> 
> Op zo 9 sep. 2018 18:02 schreef Driesprong, Fokko :
> Can we add this one as well?
> 
> https://github.com/apache/incubator-airflow/pull/3862 
> 
> https://issues.apache.org/jira/browse/AIRFLOW-1917 
> 
> 
> I'm happy to cherry pick them onto the 1.10.1 by myself as well. Any idea
> when we will start this branch?
> 
> Cheers, Fokko
> 
> Op do 6 sep. 2018 om 08:08 schreef Deng Xiaodong  >:
> 
> > Hi Ash,
> >
> >
> > May you consider including JIRA ticket 2848 (PR 3693, Ensure dag_id in
> > metadata "job" for LocalTaskJob) in 1.10.1 as well?
> >
> > https://issues.apache.org/jira/browse/AIRFLOW-2848 
> > 
> >
> > https://github.com/apache/incubator-airflow/pull/3693 
> > 
> >
> >
> > This is a bug in terms of metadata, which also affects the UI
> > “Browse->Jobs”.
> >
> >
> > Thanks.
> >
> >
> > Regards,
> >
> > XD
> >
> > On Wed, Sep 5, 2018 at 23:55 Bolke de Bruin  > > wrote:
> >
> > > You should push these to v1-10-test not to stable. Only once we start
> > > cutting RCs you should push to -stable. See the docs. This ensures a
> > stable
> > > “stable”branch.
> > >
> > > Cheers
> > > Bolke.
> > >
> > > > On 3 Sep 2018, at 14:20, Ash Berlin-Taylor  > > > > wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > I'm starting the process of gathering fixes for a 1.10.1. So far the
> > > list of issues I have that we should pull in are
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20AIRFLOW%20AND%20fixVersion%20%3D%201.10.1%20ORDER%20BY%20key%20ASC
> >  
> > 
> > > (reproduces below)
> > > >
> > > > I will start pushing these as cherry-picked commits to the v1-10-stable
> > > branch today.
> > > >
> > > > If you have something that is not in the list below let me know. I'd
> > > like to keep this to bug fixes against 1.10.0 only if possible.
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2145 
> > > >  Deadlock after
> > > clearing a running task
> > > > https://github.com/apache/incubator-airflow/pull/3657 
> > > > 
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2476 
> > > >  update tabulate dep
> > > to 0.8.2
> > > > https://github.com/apache/incubator-airflow/pull/3835 
> > > > 
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2778 
> > > >  Bad Import in
> > > collect_dag in DagBag
> > > > https://github.com/apache/incubator-airflow/pull/3624 
> > > > 
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2900 
> > > >  Show code for
> > > packaged DAGs
> > > > https://github.com/apache/incubator-airflow/pull/3749 
> > > > 
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2949 
> > > >  Add syntax
> > highlight
> > > for single quote strings
> > > > https://github.com/apache/incubator-airflow/pull/3795 
> > > > 
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2984 
> > > >  Cannot convert
> > > naive_datetime when task has a naive start_date/end_date
> > > > https://github.com/apache/incubator-airflow/pull/3822 
> > > > 
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2979 
> > > >

Re: Call for fixes for Airflow 1.10.1

2018-09-09 Thread Bolke de Bruin

You can already add them to v1-10-test.

Normally we are a bit cautious to this if you are not the release manager
to ensure that he/she knows what the state is.

B

Op zo 9 sep. 2018 18:02 schreef Driesprong, Fokko :

> Can we add this one as well?
>
> https://github.com/apache/incubator-airflow/pull/3862
> https://issues.apache.org/jira/browse/AIRFLOW-1917
>
> I'm happy to cherry pick them onto the 1.10.1 by myself as well. Any idea
> when we will start this branch?
>
> Cheers, Fokko
>
> Op do 6 sep. 2018 om 08:08 schreef Deng Xiaodong :
>
> > Hi Ash,
> >
> >
> > May you consider including JIRA ticket 2848 (PR 3693, Ensure dag_id in
> > metadata "job" for LocalTaskJob) in 1.10.1 as well?
> >
> > https://issues.apache.org/jira/browse/AIRFLOW-2848
> >
> > https://github.com/apache/incubator-airflow/pull/3693
> >
> >
> > This is a bug in terms of metadata, which also affects the UI
> > “Browse->Jobs”.
> >
> >
> > Thanks.
> >
> >
> > Regards,
> >
> > XD
> >
> > On Wed, Sep 5, 2018 at 23:55 Bolke de Bruin  wrote:
> >
> > > You should push these to v1-10-test not to stable. Only once we start
> > > cutting RCs you should push to -stable. See the docs. This ensures a
> > stable
> > > “stable”branch.
> > >
> > > Cheers
> > > Bolke.
> > >
> > > > On 3 Sep 2018, at 14:20, Ash Berlin-Taylor  wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > I'm starting the process of gathering fixes for a 1.10.1. So far the
> > > list of issues I have that we should pull in are
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AIRFLOW%20AND%20fixVersion%20%3D%201.10.1%20ORDER%20BY%20key%20ASC
> > > (reproduces below)
> > > >
> > > > I will start pushing these as cherry-picked commits to the
> v1-10-stable
> > > branch today.
> > > >
> > > > If you have something that is not in the list below let me know. I'd
> > > like to keep this to bug fixes against 1.10.0 only if possible.
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2145 Deadlock after
> > > clearing a running task
> > > > https://github.com/apache/incubator-airflow/pull/3657
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2476 update tabulate
> dep
> > > to 0.8.2
> > > > https://github.com/apache/incubator-airflow/pull/3835
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2778 Bad Import in
> > > collect_dag in DagBag
> > > > https://github.com/apache/incubator-airflow/pull/3624
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2900 Show code for
> > > packaged DAGs
> > > > https://github.com/apache/incubator-airflow/pull/3749
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2949 Add syntax
> > highlight
> > > for single quote strings
> > > > https://github.com/apache/incubator-airflow/pull/3795
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2984 Cannot convert
> > > naive_datetime when task has a naive start_date/end_date
> > > > https://github.com/apache/incubator-airflow/pull/3822
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2979 Deprecated Celery
> > > Option not in Options list
> > > > https://github.com/apache/incubator-airflow/pull/3832
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2989 No Parameter to
> > > change bootDiskType for DataprocClusterCreateOperator
> > > > https://github.com/apache/incubator-airflow/pull/3825
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2990 Docstrings for
> > > Hooks/Operators are in incorrect format
> > > > https://github.com/apache/incubator-airflow/pull/3820
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2994 flatten_results
> in
> > > BigQueryOperator/BigQueryHook should default to None
> > > > https://github.com/apache/incubator-airflow/pull/3829
> > > >
> > > >
> > > > In addition to those PRs which are already marked with Fix Version of
> > > 1.10.1 I think we should also pull in these:
> > > >
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2713 Rename async
> > > variable for Python 3.7.0 compatibility
> > > > https://github.com/apache/incubator-airflow/pull/3561
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2895 Prevent scheduler
> > > from spamming heartbeats/logs
> > > > https://github.com/apache/incubator-airflow/pull/3747
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2921 A trivial
> > > incorrectness in CeleryExecutor()
> > > > https://github.com/apache/incubator-airflow/pull/3773
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2866 Missing CSRF
> Token
> > > Error on Web RBAC UI Create/Update Operations
> > > > https://github.com/apache/incubator-airflow/pull/3804
> > > >
> > > >
> > > > https://issues.apache.org/jira/browse/AIRFLOW-2951
> > > > https://github.com/apache/incubator-airflow/pull/3798 Update dag_run
> > > table end_date when state change
> > > > (though as written it has a few other deps to cherry pick in, so will
> > > see about this one)
> > > >
> > >
> > >
> >
>

Re: Call for fixes for Airflow 1.10.1

2018-09-09 Thread Driesprong, Fokko

Can we add this one as well?

https://github.com/apache/incubator-airflow/pull/3862
https://issues.apache.org/jira/browse/AIRFLOW-1917

I'm happy to cherry pick them onto the 1.10.1 by myself as well. Any idea
when we will start this branch?

Cheers, Fokko

Op do 6 sep. 2018 om 08:08 schreef Deng Xiaodong :

> Hi Ash,
>
>
> May you consider including JIRA ticket 2848 (PR 3693, Ensure dag_id in
> metadata "job" for LocalTaskJob) in 1.10.1 as well?
>
> https://issues.apache.org/jira/browse/AIRFLOW-2848
>
> https://github.com/apache/incubator-airflow/pull/3693
>
>
> This is a bug in terms of metadata, which also affects the UI
> “Browse->Jobs”.
>
>
> Thanks.
>
>
> Regards,
>
> XD
>
> On Wed, Sep 5, 2018 at 23:55 Bolke de Bruin  wrote:
>
> > You should push these to v1-10-test not to stable. Only once we start
> > cutting RCs you should push to -stable. See the docs. This ensures a
> stable
> > “stable”branch.
> >
> > Cheers
> > Bolke.
> >
> > > On 3 Sep 2018, at 14:20, Ash Berlin-Taylor  wrote:
> > >
> > > Hi everyone,
> > >
> > > I'm starting the process of gathering fixes for a 1.10.1. So far the
> > list of issues I have that we should pull in are
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AIRFLOW%20AND%20fixVersion%20%3D%201.10.1%20ORDER%20BY%20key%20ASC
> > (reproduces below)
> > >
> > > I will start pushing these as cherry-picked commits to the v1-10-stable
> > branch today.
> > >
> > > If you have something that is not in the list below let me know. I'd
> > like to keep this to bug fixes against 1.10.0 only if possible.
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2145 Deadlock after
> > clearing a running task
> > > https://github.com/apache/incubator-airflow/pull/3657
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2476 update tabulate dep
> > to 0.8.2
> > > https://github.com/apache/incubator-airflow/pull/3835
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2778 Bad Import in
> > collect_dag in DagBag
> > > https://github.com/apache/incubator-airflow/pull/3624
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2900 Show code for
> > packaged DAGs
> > > https://github.com/apache/incubator-airflow/pull/3749
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2949 Add syntax
> highlight
> > for single quote strings
> > > https://github.com/apache/incubator-airflow/pull/3795
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2984 Cannot convert
> > naive_datetime when task has a naive start_date/end_date
> > > https://github.com/apache/incubator-airflow/pull/3822
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2979 Deprecated Celery
> > Option not in Options list
> > > https://github.com/apache/incubator-airflow/pull/3832
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2989 No Parameter to
> > change bootDiskType for DataprocClusterCreateOperator
> > > https://github.com/apache/incubator-airflow/pull/3825
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2990 Docstrings for
> > Hooks/Operators are in incorrect format
> > > https://github.com/apache/incubator-airflow/pull/3820
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2994 flatten_results in
> > BigQueryOperator/BigQueryHook should default to None
> > > https://github.com/apache/incubator-airflow/pull/3829
> > >
> > >
> > > In addition to those PRs which are already marked with Fix Version of
> > 1.10.1 I think we should also pull in these:
> > >
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2713 Rename async
> > variable for Python 3.7.0 compatibility
> > > https://github.com/apache/incubator-airflow/pull/3561
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2895 Prevent scheduler
> > from spamming heartbeats/logs
> > > https://github.com/apache/incubator-airflow/pull/3747
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2921 A trivial
> > incorrectness in CeleryExecutor()
> > > https://github.com/apache/incubator-airflow/pull/3773
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2866 Missing CSRF Token
> > Error on Web RBAC UI Create/Update Operations
> > > https://github.com/apache/incubator-airflow/pull/3804
> > >
> > >
> > > https://issues.apache.org/jira/browse/AIRFLOW-2951
> > > https://github.com/apache/incubator-airflow/pull/3798 Update dag_run
> > table end_date when state change
> > > (though as written it has a few other deps to cherry pick in, so will
> > see about this one)
> > >
> >
> >
>

Re: [VOTE][RESULT] Replace with Gitter with Slack?

2018-09-09 Thread Jakob Homan

So, binding VOTEs are generally only called on releases, where PMC
members get those binding votes (and on electing new committers or PMC
members, and those votes happen in private on the private list).
Communities often call VOTEs on other things, like logos, questions of
sponsorship, large scale tech decisions, etc.  How those VOTEs are
executed (consesus [ie anyone with a binding vote can VETO] or
majority) are up to the community to decide.

The community can codify those decisions with bylaws (Here's Hadoop's:
https://hadoop.apache.org/bylaws.html).  However, extensive bylaws are
considered an anti-pattern - they can be indicative of a fractured or
unwieldy community.  This is why Incubator projects are not generally
recommended to go down this route.  Also, incubator podlings are not
separate top-level projects, and so would be governed by the Incubator
project bylaws, which as far as I can tell, don't exist.

Also, keep in mind that the bylaws of any particular project are valid
at the pleasure of the Board.  If the Board deems any part of them
invalid, which it has done even very recently, it can come in and
require the project to change them immediately.

As for the current discussion, the large number of <1 votes, is a bit
concerning.  This is indicative of lack of consensus and that further
discussion is probably warranted.  Whether or not it's an official
result is up for debate.

However, one thing worth noting is that there's no 'official' gitter
or slack channel for any ASF project.  The only official communication
medium for ASF is mailing lists.  The edict 'If it didn't happen on
the mailing list, it didn't happen' is one of the axioms of the Apache
Way [1][2].  There's also no official IRC channel or official Stack
Overflow tag or official in-person meetup.  Every member of the
community is welcome to participate in whatever forum they want, but
the only place things actually happen is on the list.  Any non-PMC
discussions can happen anywhere, but if a decision needs to occur as
part of that discussion, the discussion needs to be re-homed onto the
mailing list and made there.  Part of the PMC's job is to enforce and
model this behavior.

Speaking entirely for myself, I'm not comfortable with the invitation
model of Slack discussions.  For most of my time at Apache, irc was
the way to go for most projects.  Some had very active irc channels
and some were nearly dead.  (The #infra irc channel is a godsend
though.)

And again, this type of meta discussion is awesome.  It shows the
project is maturing and thinking through some of the edge cases of
what it means to an Apache project.

-Jakob

[1] 
https://community.apache.org/newbiefaq.html#NewbieFAQ-IsthereaCodeofConductforApacheprojects?
[2] 
https://blogs.apache.org/foundation/entry/success-at-apache-asynchronous-decision

On 8 September 2018 at 23:14, Sid Anand  wrote:
> Taking Binding votes into account :
>
> +1: 1 vote
>
>- Sid Anand
>
> 0: 2 votes
>
>- Bolke de Bruin
>- Kaxil Naik
>
> -0.5: 1 vote
>
>- Arthur Wiedmer
>
>
> Vote result is a net positive of +0.5.
>
> I counted all of the PMC/committers' votes as binding.
>
> -s
>
> On Sat, Sep 8, 2018 at 11:07 PM Arthur Wiedmer 
> wrote:
>
>> Sid,
>>
>> Erm, the next line is (emphasis mine) :
>>
>> PMC members have formally binding votes, but in general community members
>> are encouraged to vote, even if their votes are *only advisory*.
>>
>> Again, that's not to say that the community at large cannot decide to host
>> a Slack channel. I think you are more than welcome to if you want to.
>>
>> Best,
>> Arthur
>>
>> On Sat, Sep 8, 2018 at 10:59 PM Sid Anand  wrote:
>>
>> > Why doesn't every vote matter for this topic?
>> > https://www.apache.org/foundation/voting.html#binding-votes
>> >
>> > Am I misinterpreting the "Who is permitted to vote is, to some extent, a
>> > community-specific thing."?
>> >
>> > For the established Apache processes around promoting a contributor to
>> > committer/PMC, deciding on the number of +1s to allow a merge to master,
>> or
>> > voting on releases, I understand the need to follow the
>> binding/non-binding
>> > protocol. In all of those cases, the outcomes affect maintainers.
>> >
>> > My understanding is that this topic affects the entire community, where
>> > some members of the community are helping others. This seems to chug
>> along
>> > without maintainers being present. Hence, why do maintainers' votes
>> matter
>> > more here?
>> >
>> > Question for the mentors.. Jakob?
>> >
>> > -s
>> >
>> > On Sat, Sep 8, 2018 at 10:27 PM Bolke de Bruin 
>> wrote:
>> >
>> > > Committers can only vote binding. Most of the time it is tagged by,
>> > > indeed, adding "binding" to the vote.
>> > >
>> > > Sent from my iPhone
>> > >
>> > > > On 9 Sep 2018, at 07:20, Scott Halgrim > > .INVALID>
>> > > wrote:
>> > > >
>> > > > What makes a vote binding? Just putting “(binding)” after your vote?
>> > > >> On Sep 8, 2018, 10:19 PM -0700, Bolke de Bruin

Re: [VOTE][RESULT] Replace with Gitter with Slack?

2018-09-09 Thread Bolke de Bruin

I know I'm nitpicking but afaik you need 3 +1s to make the change.

However why dont you open a slack Channel and see who joins and let people
know on gitter as well that it exists?

B.

Op zo 9 sep. 2018 08:15 schreef Sid Anand :

> Taking Binding votes into account :
>
> +1: 1 vote
>
>- Sid Anand
>
> 0: 2 votes
>
>- Bolke de Bruin
>- Kaxil Naik
>
> -0.5: 1 vote
>
>- Arthur Wiedmer
>
>
> Vote result is a net positive of +0.5.
>
> I counted all of the PMC/committers' votes as binding.
>
> -s
>
> On Sat, Sep 8, 2018 at 11:07 PM Arthur Wiedmer 
> wrote:
>
> > Sid,
> >
> > Erm, the next line is (emphasis mine) :
> >
> > PMC members have formally binding votes, but in general community members
> > are encouraged to vote, even if their votes are *only advisory*.
> >
> > Again, that's not to say that the community at large cannot decide to
> host
> > a Slack channel. I think you are more than welcome to if you want to.
> >
> > Best,
> > Arthur
> >
> > On Sat, Sep 8, 2018 at 10:59 PM Sid Anand  wrote:
> >
> > > Why doesn't every vote matter for this topic?
> > > https://www.apache.org/foundation/voting.html#binding-votes
> > >
> > > Am I misinterpreting the "Who is permitted to vote is, to some extent,
> a
> > > community-specific thing."?
> > >
> > > For the established Apache processes around promoting a contributor to
> > > committer/PMC, deciding on the number of +1s to allow a merge to
> master,
> > or
> > > voting on releases, I understand the need to follow the
> > binding/non-binding
> > > protocol. In all of those cases, the outcomes affect maintainers.
> > >
> > > My understanding is that this topic affects the entire community, where
> > > some members of the community are helping others. This seems to chug
> > along
> > > without maintainers being present. Hence, why do maintainers' votes
> > matter
> > > more here?
> > >
> > > Question for the mentors.. Jakob?
> > >
> > > -s
> > >
> > > On Sat, Sep 8, 2018 at 10:27 PM Bolke de Bruin 
> > wrote:
> > >
> > > > Committers can only vote binding. Most of the time it is tagged by,
> > > > indeed, adding "binding" to the vote.
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On 9 Sep 2018, at 07:20, Scott Halgrim  > > .INVALID>
> > > > wrote:
> > > > >
> > > > > What makes a vote binding? Just putting “(binding)” after your
> vote?
> > > > >> On Sep 8, 2018, 10:19 PM -0700, Bolke de Bruin  >,
> > > > wrote:
> > > > >> Sorry sid, only binding votes directly count to the vote. Please
> > > update
> > > > the
> > > > >> result accordingly.
> > > > >>
> > > > >> Btw did you ask on gitter itself?
> > > > >>
> > > > >>
> > > > >>
> > > > >> Op zo 9 sep. 2018 03:47 schreef Sid Anand :
> > > > >>
> > > > >>> +1: 12 votes
> > > > >>>
> > > > >>> - Sid Anand
> > > > >>> - Steve Carpenter
> > > > >>> - Beau Barker
> > > > >>> - Marc Bollinger
> > > > >>> - Pedro Machado
> > > > >>> - Scott Halgrim
> > > > >>> - Eamon Keane
> > > > >>> - Adam Boscarino
> > > > >>> - Daniel Cohen
> > > > >>> - Chandu Kavar
> > > > >>> - William Horton
> > > > >>> - Ben Gregory
> > > > >>>
> > > > >>> 0: 2 votes
> > > > >>>
> > > > >>> - Bolke de Bruin
> > > > >>> - Kaxil Naik
> > > > >>>
> > > > >>>
> > > > >>> -0.5: 1 vote
> > > > >>>
> > > > >>> - Arthur Wiedmer
> > > > >>>
> > > > >>> -1: 4 votes
> > > > >>>
> > > > >>> - Shah Altaf
> > > > >>> - James Meickle
> > > > >>> - Ravi Kotecha
> > > > >>> - airflowuser (??)
> > > > >>>
> > > > >>> The vote concludes with 12 votes for and 4.5 votes against. The
> > > > community
> > > > >>> has opted to move to Slack from Gitter.
> > > > >>>
> > > > >>> -s
> > > > >>>
> > > >
> > >
> >
>

Re: [VOTE][RESULT] Replace with Gitter with Slack?

2018-09-09 Thread Arthur Wiedmer

Sid,

Erm, the next line is (emphasis mine) :

PMC members have formally binding votes, but in general community members
are encouraged to vote, even if their votes are *only advisory*.

Again, that's not to say that the community at large cannot decide to host
a Slack channel. I think you are more than welcome to if you want to.

Best,
Arthur

On Sat, Sep 8, 2018 at 10:59 PM Sid Anand  wrote:

> Why doesn't every vote matter for this topic?
> https://www.apache.org/foundation/voting.html#binding-votes
>
> Am I misinterpreting the "Who is permitted to vote is, to some extent, a
> community-specific thing."?
>
> For the established Apache processes around promoting a contributor to
> committer/PMC, deciding on the number of +1s to allow a merge to master, or
> voting on releases, I understand the need to follow the binding/non-binding
> protocol. In all of those cases, the outcomes affect maintainers.
>
> My understanding is that this topic affects the entire community, where
> some members of the community are helping others. This seems to chug along
> without maintainers being present. Hence, why do maintainers' votes matter
> more here?
>
> Question for the mentors.. Jakob?
>
> -s
>
> On Sat, Sep 8, 2018 at 10:27 PM Bolke de Bruin  wrote:
>
> > Committers can only vote binding. Most of the time it is tagged by,
> > indeed, adding "binding" to the vote.
> >
> > Sent from my iPhone
> >
> > > On 9 Sep 2018, at 07:20, Scott Halgrim  .INVALID>
> > wrote:
> > >
> > > What makes a vote binding? Just putting “(binding)” after your vote?
> > >> On Sep 8, 2018, 10:19 PM -0700, Bolke de Bruin ,
> > wrote:
> > >> Sorry sid, only binding votes directly count to the vote. Please
> update
> > the
> > >> result accordingly.
> > >>
> > >> Btw did you ask on gitter itself?
> > >>
> > >>
> > >>
> > >> Op zo 9 sep. 2018 03:47 schreef Sid Anand :
> > >>
> > >>> +1: 12 votes
> > >>>
> > >>> - Sid Anand
> > >>> - Steve Carpenter
> > >>> - Beau Barker
> > >>> - Marc Bollinger
> > >>> - Pedro Machado
> > >>> - Scott Halgrim
> > >>> - Eamon Keane
> > >>> - Adam Boscarino
> > >>> - Daniel Cohen
> > >>> - Chandu Kavar
> > >>> - William Horton
> > >>> - Ben Gregory
> > >>>
> > >>> 0: 2 votes
> > >>>
> > >>> - Bolke de Bruin
> > >>> - Kaxil Naik
> > >>>
> > >>>
> > >>> -0.5: 1 vote
> > >>>
> > >>> - Arthur Wiedmer
> > >>>
> > >>> -1: 4 votes
> > >>>
> > >>> - Shah Altaf
> > >>> - James Meickle
> > >>> - Ravi Kotecha
> > >>> - airflowuser (??)
> > >>>
> > >>> The vote concludes with 12 votes for and 4.5 votes against. The
> > community
> > >>> has opted to move to Slack from Gitter.
> > >>>
> > >>> -s
> > >>>
> >
>

Re: [VOTE][RESULT] Replace with Gitter with Slack?

2018-09-09 Thread Sid Anand

Why doesn't every vote matter for this topic?
https://www.apache.org/foundation/voting.html#binding-votes

Am I misinterpreting the "Who is permitted to vote is, to some extent, a
community-specific thing."?

For the established Apache processes around promoting a contributor to
committer/PMC, deciding on the number of +1s to allow a merge to master, or
voting on releases, I understand the need to follow the binding/non-binding
protocol. In all of those cases, the outcomes affect maintainers.

My understanding is that this topic affects the entire community, where
some members of the community are helping others. This seems to chug along
without maintainers being present. Hence, why do maintainers' votes matter
more here?

Question for the mentors.. Jakob?

-s

On Sat, Sep 8, 2018 at 10:27 PM Bolke de Bruin  wrote:

> Committers can only vote binding. Most of the time it is tagged by,
> indeed, adding "binding" to the vote.
>
> Sent from my iPhone
>
> > On 9 Sep 2018, at 07:20, Scott Halgrim 
> wrote:
> >
> > What makes a vote binding? Just putting “(binding)” after your vote?
> >> On Sep 8, 2018, 10:19 PM -0700, Bolke de Bruin ,
> wrote:
> >> Sorry sid, only binding votes directly count to the vote. Please update
> the
> >> result accordingly.
> >>
> >> Btw did you ask on gitter itself?
> >>
> >>
> >>
> >> Op zo 9 sep. 2018 03:47 schreef Sid Anand :
> >>
> >>> +1: 12 votes
> >>>
> >>> - Sid Anand
> >>> - Steve Carpenter
> >>> - Beau Barker
> >>> - Marc Bollinger
> >>> - Pedro Machado
> >>> - Scott Halgrim
> >>> - Eamon Keane
> >>> - Adam Boscarino
> >>> - Daniel Cohen
> >>> - Chandu Kavar
> >>> - William Horton
> >>> - Ben Gregory
> >>>
> >>> 0: 2 votes
> >>>
> >>> - Bolke de Bruin
> >>> - Kaxil Naik
> >>>
> >>>
> >>> -0.5: 1 vote
> >>>
> >>> - Arthur Wiedmer
> >>>
> >>> -1: 4 votes
> >>>
> >>> - Shah Altaf
> >>> - James Meickle
> >>> - Ravi Kotecha
> >>> - airflowuser (??)
> >>>
> >>> The vote concludes with 12 votes for and 4.5 votes against. The
> community
> >>> has opted to move to Slack from Gitter.
> >>>
> >>> -s
> >>>
>

Re: Call for fixes for Airflow 1.10.1

Re: Call for fixes for Airflow 1.10.1

Re: Call for fixes for Airflow 1.10.1

Re: [VOTE][RESULT] Replace with Gitter with Slack?

Re: [VOTE][RESULT] Replace with Gitter with Slack?

Re: [VOTE][RESULT] Replace with Gitter with Slack?

Re: [VOTE][RESULT] Replace with Gitter with Slack?

7 matches

Site Navigation

Mail list logo

Footer information