About labeling on Github, I wrote a bot for Superset that enables anyone to
apply labels through commenting using emojis.
It does other things like auto-labeling organization on an allow-list. We
could teach it new tricks top.
Generalizing it or porting it to work in other communities should be
Mine is @vikramkoka
On Sun, Sep 13, 2020 at 7:29 PM Elad Kalif wrote:
> mine is @eladkal
>
> On Mon, Sep 14, 2020 at 4:33 AM Pete DeJoy wrote:
>
> > I’d love to help as well! Gh handle is @petedejoy
> >
> > Thanks for organizing everyone.
> >
> > Pete
> > On Sep 13, 2020, 4:57 PM -0400,
+1 non-binding
On Sun, Sep 13, 2020 at 2:20 PM Kaxil Naik wrote:
> +1 binding
>
> On Sun, Sep 13, 2020 at 10:18 PM Daniel Imberman <
> daniel.imber...@gmail.com>
> wrote:
>
> > +1 (binding).
> >
> > via Newton Mail
> > [
> >
>
mine is @eladkal
On Mon, Sep 14, 2020 at 4:33 AM Pete DeJoy wrote:
> I’d love to help as well! Gh handle is @petedejoy
>
> Thanks for organizing everyone.
>
> Pete
> On Sep 13, 2020, 4:57 PM -0400, Jarek Potiuk ,
> wrote:
> > @Kamil Breguła - I believe we already base
> it
> > on the
I’d love to help as well! Gh handle is @petedejoy
Thanks for organizing everyone.
Pete
On Sep 13, 2020, 4:57 PM -0400, Jarek Potiuk , wrote:
> @Kamil Breguła - I believe we already base it
> on the experience of others (see the discussion before). I think in our
> case the will of people and
+1 binding
On Sun, Sep 13, 2020 at 10:18 PM Daniel Imberman
wrote:
> +1 (binding).
>
> via Newton Mail
> [
> https://cloudmagic.com/k/d/mailapp?ct=dx=10.0.50=10.15.6=email_footer_2
> ]
> On Sun, Sep 13, 2020 at 1:57 PM, Kevin Yang wrote:
> +1 (binding)
>
> On Sun, Sep 13, 2020 at 1:29 PM Jarek
+1 (binding).
via Newton Mail
[https://cloudmagic.com/k/d/mailapp?ct=dx=10.0.50=10.15.6=email_footer_2]
On Sun, Sep 13, 2020 at 1:57 PM, Kevin Yang wrote:
+1 (binding)
On Sun, Sep 13, 2020 at 1:29 PM Jarek Potiuk
wrote:
> Hello Everyone,
>
> Last week, at the Airflow 2.0 meeting the people
+1 (binding)
On Sun, Sep 13, 2020 at 1:29 PM Jarek Potiuk
wrote:
> Hello Everyone,
>
> Last week, at the Airflow 2.0 meeting the people involved made a decision
> that we are releasing Airlow 2.0 as a set of separate "core" and
> "providers" packages - similarly to the 1.10 "backport providers"
@Kamil Breguła - I believe we already base it
on the experience of others (see the discussion before). I think in our
case the will of people and their commitment to do so is far more important
than any tools we would like to use (community over code). I think we
should first let the people who
Hello Everyone,
Last week, at the Airflow 2.0 meeting the people involved made a decision
that we are releasing Airlow 2.0 as a set of separate "core" and
"providers" packages - similarly to the 1.10 "backport providers" packages.
This decision effectively implements the "spirit" of the AIP-8
Hello,
I agree that it is worth considering changes in the way of handling
issues. Google has created a tool that can help us the issue and PR triage
for large open-source projects
https://github.com/google/triage-party
It was built from the Google Container DevEx team's experience contributing
Sounds good!
In the meantime, I will draft up a proposal for the set of labels and
milestones that we are using to eliminate duplication to factor in the 2.0
timeline.
On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk
wrote:
> Fantastic initiative!
>
> However, currently you have no way to give
Fantastic initiative!
However, currently you have no way to give access to either of the
people involved to modify the labels or assign them to issues.
But Wait for it ... ASF *JUST DAYS AGO* allowed the projects to assign
people to the "Triage" role I was talking about:
Hello Everyone,
As promised, I prepared a draft of the proposal of changes that I would
love if a number of interested people discuss it, comment, criticise, agree
on eventually, and submit to the ASF Board for Approval.
I tried to capture all the context, but also I marked clearly all the
14 matches
Mail list logo
