It's very hard to become a committer on the project

[airflowuser <ai...@protonmail.com.INVALID>]

Hello all,

I'm struggling finding tickets to address and while discussing it on chat others reported they had the same problem when they began working on the project.

The problem is due to:
1. It's very hard to locate tickets on Jira. The categories are a mess, versions are not enforced. each use can tag,label and set priority at his will. No one monitor or overwrite it
2. It's impossible for a new committer to  find issues which can be easy-fix and a "good first issue".

My suggestions:
1. Looking at the ticket system there are usually less than 10 new tickets a day. It won't take too much time for someone with knowledge on the project to properly tag  the ticket.

2. I think that most of you don't even check the Jira. Most of you submit PRs and 5 seconds before opening a ticket (just because you must). There is no doubt that the Jira is a "side" system which doesn't really perform it's job.

Take a look at this:
https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
a member of the community asks for committers for input but no one replies. I doubt this is because no one has input.. I am sure that if a PR was submitted you had comments. It's simply because you don't see it. This is why I think the current Jira does't function properly. I think that Github can perform a better role. All of you as committers are already there and it's always better to work with one system rather with two. The colors and labels of the GitHub as very easy to notice.

Either way, what ever you decide something needs to be change. Either Jira will be more informative or move to GitHub.

Thank you all for your good work :)

Re: It's very hard to become a committer on the project

[Ash Berlin-Taylor <as...@apache.org>]

For background I got involve in Airflow by adding features I wanted, and fixing bugs/oddities that I came across - I didn't fix other peoples tickets. Most other committers are the same. We've all "scratched our own itch" as it were.

You have proposed a technical solution to a non-technical problem.

The problem is not a lack of visibility on issues (If you are subscribed to the commits@ list, which most active committers should be), as I am, then I receive an email for every new ticket opened or every comment on an issue.

The problem is time.

No one is paid to work on Airflow full time, we all do it as a side-effect of using Airflow for our jobs. And triaging Jira tickets is _very_ hard to justify spending that time. I also think you under estimate how much time it takes to triage even a single ticket.

I would *love* to be able to spend more time improving airflow, making it easier for other people to get involved, improving documentation, and triaging issues. But no one is currently paying me or any other committer to do this, so any time we spent on Airflow is going to be focused on what we need out of airflow. Sorry.

(For the record though, I do dislike Jira, but I don't care enough to think about changing.)

Hope this helps explain the situation.

-ash


> On 16 Sep 2018, at 14:29, airflowuser <ai...@protonmail.com.INVALID> wrote:
> 
> Hello all,
> 
> I'm struggling finding tickets to address and while discussing it on chat others reported they had the same problem when they began working on the project.
> 
> The problem is due to:
> 1. It's very hard to locate tickets on Jira. The categories are a mess, versions are not enforced. each use can tag,label and set priority at his will. No one monitor or overwrite it
> 2. It's impossible for a new committer to  find issues which can be easy-fix and a "good first issue".
> 
> My suggestions:
> 1. Looking at the ticket system there are usually less than 10 new tickets a day. It won't take too much time for someone with knowledge on the project to properly tag  the ticket.
> 
> 2. I think that most of you don't even check the Jira. Most of you submit PRs and 5 seconds before opening a ticket (just because you must). There is no doubt that the Jira is a "side" system which doesn't really perform it's job.
> 
> Take a look at this:
> https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> a member of the community asks for committers for input but no one replies. I doubt this is because no one has input.. I am sure that if a PR was submitted you had comments. It's simply because you don't see it. This is why I think the current Jira does't function properly. I think that Github can perform a better role. All of you as committers are already there and it's always better to work with one system rather with two. The colors and labels of the GitHub as very easy to notice.
> 
> Either way, what ever you decide something needs to be change. Either Jira will be more informative or move to GitHub.
> 
> Thank you all for your good work :)

Re: It's very hard to become a committer on the project

["Driesprong, Fokko" <fo...@driesprong.frl>]

Many thanks for the effort Stefan, I just went through them and updated the
status accordingly in Jira.

Thanks!

Cheers, Fokko

Op za 22 sep. 2018 om 23:25 schreef Stefan Seelmann <mail@stefan-seelmann.de
>:

> On 9/20/18 10:02 PM, Driesprong, Fokko wrote:
> > us still have a full time job on the side :) Tomorrow I'll spend time to
> > clean up the old Jira's.
>
> My cold prevents me for doing creative things, so I went through Jira
> and picked the low hanging fruits. The following issues can be closed IMHO:
>
> Spam:
> * AIRFLOW-1944
> * AIRFLOW-2277
>
> Missing description:
> * AIRFLOW-2583
>
> Fixed (commit in master):
> * AIRFLOW-1448
> * AIRFLOW-692
> * AIRFLOW-553
> * AIRFLOW-529
> * AIRFLOW-7
> * AIRFLOW-2810
> * AIRFLOW-2863
> * AIRFLOW-2419
> * AIRFLOW-951
> * AIRFLOW-1487
> * AIRFLOW-1532
> * AIRFLOW-1531
> * AIRFLOW-2653
> * AIRFLOW-3074
> * AIRFLOW-276
>
> Fixed (duplicate):
> * AIRFLOW-768
> * AIRFLOW-499
> * AIRFLOW-699
> * AIRFLOW-1701
> * AIRFLOW-1386
> * AIRFLOW-1353
> * AIRFLOW-346
>
> Not reproducable:
> * AIRFLOW-1285
>
> Fixed or no longer valid because of new FAB/RBAC UI:
> * AIRFLOW-294
> * AIRFLOW-292
>
> Issues referencing specifc issues with Airflow 1.6/1.7:
> * AIRFLOW-668
> * AIRFLOW-1137
> * AIRFLOW-344
> * AIRFLOW-317
>

Re: It's very hard to become a committer on the project

[Stefan Seelmann <ma...@stefan-seelmann.de>]

On 9/20/18 10:02 PM, Driesprong, Fokko wrote:
> us still have a full time job on the side :) Tomorrow I'll spend time to
> clean up the old Jira's.

My cold prevents me for doing creative things, so I went through Jira
and picked the low hanging fruits. The following issues can be closed IMHO:

Spam:
* AIRFLOW-1944
* AIRFLOW-2277

Missing description:
* AIRFLOW-2583

Fixed (commit in master):
* AIRFLOW-1448
* AIRFLOW-692
* AIRFLOW-553
* AIRFLOW-529
* AIRFLOW-7
* AIRFLOW-2810
* AIRFLOW-2863
* AIRFLOW-2419
* AIRFLOW-951
* AIRFLOW-1487
* AIRFLOW-1532
* AIRFLOW-1531
* AIRFLOW-2653
* AIRFLOW-3074
* AIRFLOW-276

Fixed (duplicate):
* AIRFLOW-768
* AIRFLOW-499
* AIRFLOW-699
* AIRFLOW-1701
* AIRFLOW-1386
* AIRFLOW-1353
* AIRFLOW-346

Not reproducable:
* AIRFLOW-1285

Fixed or no longer valid because of new FAB/RBAC UI:
* AIRFLOW-294
* AIRFLOW-292

Issues referencing specifc issues with Airflow 1.6/1.7:
* AIRFLOW-668
* AIRFLOW-1137
* AIRFLOW-344
* AIRFLOW-317

Re: It's very hard to become a committer on the project

[Sid Anand <sa...@apache.org>]

I will chime in here as well and essentially parrot Fokko and Ash’s
sentiments.

If your driving goal is to become a committer on an Apache project, then
OSS and Apache may not be for you. Committers are contributors,
contributors are users. So, your journey starts by using Apache Airflow to
solve a problem that you have. As you use it, you may find it doesn’t work
as you’d wish or has documentation gaps. That is when, from an informed
perspective, you’d start discussions on the mailing lists and slack, open
JIras, and submit PRs. After making contributions, you may become a
committer. We have 20 committers today and that was the journey each of us
went through, similar to the journey that others go through on other Apache
projects.

Now, as much as we can leverage the community, we do. So, we love it when
users and contributors comment on JIras, update the wiki, propose changes,
and vet each other’s PRs. And we are always looking to scale out and add
more commuters.
-s


On Thu, Sep 20, 2018 at 1:02 PM Driesprong, Fokko <fo...@driesprong.frl>
wrote:

> Some history. Recently we've moved the to Gitbox
> <https://gitbox.apache.org/> and moved away from the Apache repo itself to
> simplify the setup. Before that, the code on Github was merely a mirror of
> the Apache git repo. Before Gitbox there was a Python script that would
> like the issues to the Github PR's. Now because we've moved to Github
> itself, this piece of automation is gone and we need to get this working
> again. Also for projects like Spark there is a lot of automation going on
> between Jira and Github. Unfortunately I don't have a lot of experience
> here, but I suspect a whole bunch of hooks. For my perspective, automation
> is key here.
>
> Furthermore, as Ash is saying. It is hard for Airflow to pick up any
> arbitrary task from Jira since the usage of Airflow ranges form a wide
> range of applications, from AWS to GCP, from MySQL to Druid, from Bash to
> Slack. My advise would be the same as Ash; start using Airflow, and if you
> run into anything, raise a ticket (first check if it is already there), and
> open a PR. Like your saying; you're pretty new to Airflow, it would be best
> to get some experience first.
>
> The community (committers, contributors and users) is happy to help and
> assist, like the recent conversations on Slack. But nobody is getting paid
> to work on Airflow, and this isn't a problem, but this means that most of
> us still have a full time job on the side :) Tomorrow I'll spend time to
> clean up the old Jira's.
>
> Cheers, Fokko
>
>
> Op do 20 sep. 2018 om 11:40 schreef airflowuser
> <ai...@protonmail.com.invalid>:
>
> > >> Are you volunteering to sponsor someone's time to be able to do this?
> >
> > I am. But I have no knowledge of all the components of the project.
> > I doubt I can be much of value for this tagging task.
> >
> >
> > Sent with ProtonMail Secure Email.
> >
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Thursday, September 20, 2018 12:37 PM, Ash Berlin-Taylor <
> > ash@apache.org> wrote:
> >
> > > > Remember my basic question: I want to contribute - how on earth I can
> > find a ticket that is suitable for first time committer? Can you show me?
> > >
> > > There aren't that many feature requests in Jira, so looking there for
> > easy tickets, is as you have probably found a fruitless exercise. I'd
> > recommend using Airflow and when you come across something you want
> fixed,
> > or a feature you want added, that you open a PR for it.
> > >
> > > > Again, If decided to stay with Jira.. I highly recommend that someone
> > from the project will maintain it. Don't allow to regular users to tag
> and
> > set priorities for the tickets.. someone from the project should do it.
> > >
> > > Are you volunteering to sponsor someone's time to be able to do this?
> > >
> > > > Sent with ProtonMail Secure Email.
> > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > On Tuesday, September 18, 2018 11:57 AM, Sid Anand sanand@apache.org
> > wrote:
> > > >
> > > > > Hi Folks!
> > > > > For some history, Airlfow started on GH issues. We also had a very
> > popular Google group. When we moved to Apache, we were told that Jira was
> > the way we needed to go for issue tracking because it resided on Apache
> > infrastructure. When we moved over, we had to drop 100+ GH issues on the
> > floor -- there was no way to transfer them to Jira and maintain the
> > original submitter/owner info since there was no mapping of users between
> > the 2 systems.
> > > > > Here's a pie chart of our existing issues by status:
> > > > >
> >
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next
> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next>
> > <
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next
> >
> > > > > I'm attaching a screen shot as well.
> > > > > I think we all agree that there is better integration between GH
> PRs
> > and GH Issues than between GH PRs and Jira issues.
> > > > > There are some practical matters to consider:
> > > > >
> > > > > -   For the 1100-1200 unclosed/unresolved issues, how will we
> > transfer them to GH or will we drop those on the floor? How would we map
> > submitters between the 2 systems, and how would we transfer the
> > content/comments,etc...
> > > > > -   For the existing closed PRs (>3k), whose PRs reference JIRA,
> > we'd need to keep JIRA around in read-only mode so we could reference the
> > bug/feature details, but somehow disallow new JIRA creations, lest some
> > people continue to use it to create new issues
> > > > > -   I'm assuming the GH issue naming would not conflict with that
> of
> > JIRA naming in commit message subjects and PRs. In other words,
> > incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly
> > conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the incubator
> name
> > will be dropped, so there may be a naming conflict.
> > > > >
> > > > > In the end, these are 2 different tools. The issues you raise are
> > mainly around governance.
> > > > > If you folks would like to propose a new means to manage the JIRAs,
> > can you outline a solution on Wiki and drop a link into an email on this
> > list? We can then raise a vote.
> > > > > IMHO, our community would scale the best if more people picked up
> > responsibilities such as these. Grooming/Organizing JIRAs doesn't need to
> > be a responsibility owned by the maintainers. Anyone can take the lead on
> > discussions, etc...
> > > > > -s
> > > > > On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari
> > sumeet.manit@gmail.com wrote:
> > > > >
> > > > > > Strong +1 for moving to GitHub from Jira.
> > > > > > On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman
> > waksman@gmail.com
> > > > > > wrote:
> > > > > >
> > > > > > > Are there Apache rules preventing us from switching to GitHub
> > Issues?
> > > > > > > That seems like it might better fit much of Airflow's user
> base.
> > > > > > > On Sun, Sep 16, 2018, 9:21 AM Jeff Payne jpayne@bombora.com
> > wrote:
> > > > > > >
> > > > > > > > I agree that Jira could be better utilized. I read the
> original
> > > > > > > > conversation on the mailing list about how Jira should be
> used
> > (or if it
> > > > > > > > should be used at all) and I'm still unclear about why it was
> > picked over
> > > > > > > > just using github issues. It refers to a dashboard, which
> I've
> > yet to
> > > > > > > > investigate, but Jira is much more than just dashboards.
> > > > > > > > If this project is going to use Jira, then:
> > > > > > > >
> > > > > > > > 1.  It would be great to see moderation and labeling of the
> > Jira issues by
> > > > > > > >     the main contributors to make it easier for people to
> > break into
> > > > > > > >     contributing.
> > > > > > > >
> > > > > > > > 2.  It would also be nice if the initial conversation of
> > whether or not an
> > > > > > > >     issue warrants development at all happened on the Jira
> > issue, or at least
> > > > > > > >     some acknowledgement by the main contributors.
> > > > > > > >
> > > > > > > > 3.  Larger enhancements and efforts or vague suggestions
> still
> > get
> > > > > > > >     discussed on the dev mailing list before a Jira is even
> > opened, but after
> > > > > > > >     that, the discussion moves to the Jira, with a link back
> > to the mailing
> > > > > > > >     list email for reference.
> > > > > > > >
> > > > > > > > 4.  The discussion on the PR is only concerned with HOW the
> > change/fix is
> > > > > > > >     implemented.
> > > > > > > >
> > > > > > > >
> > > > > > > > Get Outlook for Androidhttps://aka.ms/ghei36
> > > > > > > >
> > > > > > > > From: James Meickle jmeickle@quantopian.com.INVALID
> > > > > > > > Sent: Sunday, September 16, 2018 7:46:58 AM
> > > > > > > > To: dev@airflow.apache.org
> > > > > > > > Subject: Re: It's very hard to become a committer on the
> > project
> > > > > > > > Definitely agree with this. I'm not always opposed to JIRA
> for
> > projects,
> > > > > > > > but the way it's being used for this project makes it very
> > hard to break
> > > > > > > > into contributing. The split between GH and JIRA is also
> > painful since
> > > > > > > > there's no automatic integration of them.
> > > > > > > > On Sun, Sep 16, 2018 at 9:29 AM airflowuser
> > > > > > > > airflowuser@protonmail.com.invalid wrote:
> > > > > > > >
> > > > > > > > > Hello all,
> > > > > > > > > I'm struggling finding tickets to address and while
> > discussing it on
> > > > > > > > > chat
> > > > > > > >
> > > > > > > > > others reported they had the same problem when they began
> > working on
> > > > > > > > > the
> > > > > > > >
> > > > > > > > > project.
> > > > > > > > > The problem is due to:
> > > > > > > > >
> > > > > > > > > 1.  It's very hard to locate tickets on Jira. The
> categories
> > are a mess,
> > > > > > > > >     versions are not enforced. each use can tag,label and
> > set priority at
> > > > > > > > >     his
> > > > > > > > >
> > > > > > > >
> > > > > > > > > will. No one monitor or overwrite it
> > > > > > > > > 2. It's impossible for a new committer to find issues which
> > can be
> > > > > > > > > easy-fix and a "good first issue".
> > > > > > > > > My suggestions:
> > > > > > > > >
> > > > > > > > > 1.  Looking at the ticket system there are usually less
> than
> > 10 new
> > > > > > > > >     tickets
> > > > > > > > >     a day. It won't take too much time for someone with
> > knowledge on the
> > > > > > > > >     project to properly tag the ticket.
> > > > > > > > >
> > > > > > > > > 2.  I think that most of you don't even check the Jira.
> Most
> > of you
> > > > > > > > >     submit
> > > > > > > > >
> > > > > > > >
> > > > > > > > > PRs and 5 seconds before opening a ticket (just because you
> > must).
> > > > > > > > > There
> > > > > > > > > is
> > > > > > > >
> > > > > > > > > no doubt that the Jira is a "side" system which doesn't
> > really perform
> > > > > > > > > it's
> > > > > > > > > job.
> > > > > > > > > Take a look at this:
> > > > > > > > >
> > https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> > > > > > > > > a member of the community asks for committers for input but
> > no one
> > > > > > > > > replies. I doubt this is because no one has input.. I am
> > sure that if a
> > > > > > > > > PR
> > > > > > > > > was submitted you had comments. It's simply because you
> > don't see it.
> > > > > > > > > This
> > > > > > > > > is why I think the current Jira does't function properly. I
> > think that
> > > > > > > > > Github can perform a better role. All of you as committers
> > are already
> > > > > > > > > there and it's always better to work with one system rather
> > with two.
> > > > > > > > > The
> > > > > > > >
> > > > > > > > > colors and labels of the GitHub as very easy to notice.
> > > > > > > > > Either way, what ever you decide something needs to be
> > change. Either
> > > > > > > > > Jira
> > > > > > > > > will be more informative or move to GitHub.
> > > > > > > > > Thank you all for your good work :)
> >
> >
> >
>
-- 
Sent from Gmail Mobile

Re: It's very hard to become a committer on the project

["Driesprong, Fokko" <fo...@driesprong.frl>]

Some history. Recently we've moved the to Gitbox
<https://gitbox.apache.org/> and moved away from the Apache repo itself to
simplify the setup. Before that, the code on Github was merely a mirror of
the Apache git repo. Before Gitbox there was a Python script that would
like the issues to the Github PR's. Now because we've moved to Github
itself, this piece of automation is gone and we need to get this working
again. Also for projects like Spark there is a lot of automation going on
between Jira and Github. Unfortunately I don't have a lot of experience
here, but I suspect a whole bunch of hooks. For my perspective, automation
is key here.

Furthermore, as Ash is saying. It is hard for Airflow to pick up any
arbitrary task from Jira since the usage of Airflow ranges form a wide
range of applications, from AWS to GCP, from MySQL to Druid, from Bash to
Slack. My advise would be the same as Ash; start using Airflow, and if you
run into anything, raise a ticket (first check if it is already there), and
open a PR. Like your saying; you're pretty new to Airflow, it would be best
to get some experience first.

The community (committers, contributors and users) is happy to help and
assist, like the recent conversations on Slack. But nobody is getting paid
to work on Airflow, and this isn't a problem, but this means that most of
us still have a full time job on the side :) Tomorrow I'll spend time to
clean up the old Jira's.

Cheers, Fokko


Op do 20 sep. 2018 om 11:40 schreef airflowuser
<ai...@protonmail.com.invalid>:

> >> Are you volunteering to sponsor someone's time to be able to do this?
>
> I am. But I have no knowledge of all the components of the project.
> I doubt I can be much of value for this tagging task.
>
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Thursday, September 20, 2018 12:37 PM, Ash Berlin-Taylor <
> ash@apache.org> wrote:
>
> > > Remember my basic question: I want to contribute - how on earth I can
> find a ticket that is suitable for first time committer? Can you show me?
> >
> > There aren't that many feature requests in Jira, so looking there for
> easy tickets, is as you have probably found a fruitless exercise. I'd
> recommend using Airflow and when you come across something you want fixed,
> or a feature you want added, that you open a PR for it.
> >
> > > Again, If decided to stay with Jira.. I highly recommend that someone
> from the project will maintain it. Don't allow to regular users to tag and
> set priorities for the tickets.. someone from the project should do it.
> >
> > Are you volunteering to sponsor someone's time to be able to do this?
> >
> > > Sent with ProtonMail Secure Email.
> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > On Tuesday, September 18, 2018 11:57 AM, Sid Anand sanand@apache.org
> wrote:
> > >
> > > > Hi Folks!
> > > > For some history, Airlfow started on GH issues. We also had a very
> popular Google group. When we moved to Apache, we were told that Jira was
> the way we needed to go for issue tracking because it resided on Apache
> infrastructure. When we moved over, we had to drop 100+ GH issues on the
> floor -- there was no way to transfer them to Jira and maintain the
> original submitter/owner info since there was no mapping of users between
> the 2 systems.
> > > > Here's a pie chart of our existing issues by status:
> > > >
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next
> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next>
> > > > I'm attaching a screen shot as well.
> > > > I think we all agree that there is better integration between GH PRs
> and GH Issues than between GH PRs and Jira issues.
> > > > There are some practical matters to consider:
> > > >
> > > > -   For the 1100-1200 unclosed/unresolved issues, how will we
> transfer them to GH or will we drop those on the floor? How would we map
> submitters between the 2 systems, and how would we transfer the
> content/comments,etc...
> > > > -   For the existing closed PRs (>3k), whose PRs reference JIRA,
> we'd need to keep JIRA around in read-only mode so we could reference the
> bug/feature details, but somehow disallow new JIRA creations, lest some
> people continue to use it to create new issues
> > > > -   I'm assuming the GH issue naming would not conflict with that of
> JIRA naming in commit message subjects and PRs. In other words,
> incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly
> conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the incubator name
> will be dropped, so there may be a naming conflict.
> > > >
> > > > In the end, these are 2 different tools. The issues you raise are
> mainly around governance.
> > > > If you folks would like to propose a new means to manage the JIRAs,
> can you outline a solution on Wiki and drop a link into an email on this
> list? We can then raise a vote.
> > > > IMHO, our community would scale the best if more people picked up
> responsibilities such as these. Grooming/Organizing JIRAs doesn't need to
> be a responsibility owned by the maintainers. Anyone can take the lead on
> discussions, etc...
> > > > -s
> > > > On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari
> sumeet.manit@gmail.com wrote:
> > > >
> > > > > Strong +1 for moving to GitHub from Jira.
> > > > > On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman
> waksman@gmail.com
> > > > > wrote:
> > > > >
> > > > > > Are there Apache rules preventing us from switching to GitHub
> Issues?
> > > > > > That seems like it might better fit much of Airflow's user base.
> > > > > > On Sun, Sep 16, 2018, 9:21 AM Jeff Payne jpayne@bombora.com
> wrote:
> > > > > >
> > > > > > > I agree that Jira could be better utilized. I read the original
> > > > > > > conversation on the mailing list about how Jira should be used
> (or if it
> > > > > > > should be used at all) and I'm still unclear about why it was
> picked over
> > > > > > > just using github issues. It refers to a dashboard, which I've
> yet to
> > > > > > > investigate, but Jira is much more than just dashboards.
> > > > > > > If this project is going to use Jira, then:
> > > > > > >
> > > > > > > 1.  It would be great to see moderation and labeling of the
> Jira issues by
> > > > > > >     the main contributors to make it easier for people to
> break into
> > > > > > >     contributing.
> > > > > > >
> > > > > > > 2.  It would also be nice if the initial conversation of
> whether or not an
> > > > > > >     issue warrants development at all happened on the Jira
> issue, or at least
> > > > > > >     some acknowledgement by the main contributors.
> > > > > > >
> > > > > > > 3.  Larger enhancements and efforts or vague suggestions still
> get
> > > > > > >     discussed on the dev mailing list before a Jira is even
> opened, but after
> > > > > > >     that, the discussion moves to the Jira, with a link back
> to the mailing
> > > > > > >     list email for reference.
> > > > > > >
> > > > > > > 4.  The discussion on the PR is only concerned with HOW the
> change/fix is
> > > > > > >     implemented.
> > > > > > >
> > > > > > >
> > > > > > > Get Outlook for Androidhttps://aka.ms/ghei36
> > > > > > >
> > > > > > > From: James Meickle jmeickle@quantopian.com.INVALID
> > > > > > > Sent: Sunday, September 16, 2018 7:46:58 AM
> > > > > > > To: dev@airflow.apache.org
> > > > > > > Subject: Re: It's very hard to become a committer on the
> project
> > > > > > > Definitely agree with this. I'm not always opposed to JIRA for
> projects,
> > > > > > > but the way it's being used for this project makes it very
> hard to break
> > > > > > > into contributing. The split between GH and JIRA is also
> painful since
> > > > > > > there's no automatic integration of them.
> > > > > > > On Sun, Sep 16, 2018 at 9:29 AM airflowuser
> > > > > > > airflowuser@protonmail.com.invalid wrote:
> > > > > > >
> > > > > > > > Hello all,
> > > > > > > > I'm struggling finding tickets to address and while
> discussing it on
> > > > > > > > chat
> > > > > > >
> > > > > > > > others reported they had the same problem when they began
> working on
> > > > > > > > the
> > > > > > >
> > > > > > > > project.
> > > > > > > > The problem is due to:
> > > > > > > >
> > > > > > > > 1.  It's very hard to locate tickets on Jira. The categories
> are a mess,
> > > > > > > >     versions are not enforced. each use can tag,label and
> set priority at
> > > > > > > >     his
> > > > > > > >
> > > > > > >
> > > > > > > > will. No one monitor or overwrite it
> > > > > > > > 2. It's impossible for a new committer to find issues which
> can be
> > > > > > > > easy-fix and a "good first issue".
> > > > > > > > My suggestions:
> > > > > > > >
> > > > > > > > 1.  Looking at the ticket system there are usually less than
> 10 new
> > > > > > > >     tickets
> > > > > > > >     a day. It won't take too much time for someone with
> knowledge on the
> > > > > > > >     project to properly tag the ticket.
> > > > > > > >
> > > > > > > > 2.  I think that most of you don't even check the Jira. Most
> of you
> > > > > > > >     submit
> > > > > > > >
> > > > > > >
> > > > > > > > PRs and 5 seconds before opening a ticket (just because you
> must).
> > > > > > > > There
> > > > > > > > is
> > > > > > >
> > > > > > > > no doubt that the Jira is a "side" system which doesn't
> really perform
> > > > > > > > it's
> > > > > > > > job.
> > > > > > > > Take a look at this:
> > > > > > > >
> https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> > > > > > > > a member of the community asks for committers for input but
> no one
> > > > > > > > replies. I doubt this is because no one has input.. I am
> sure that if a
> > > > > > > > PR
> > > > > > > > was submitted you had comments. It's simply because you
> don't see it.
> > > > > > > > This
> > > > > > > > is why I think the current Jira does't function properly. I
> think that
> > > > > > > > Github can perform a better role. All of you as committers
> are already
> > > > > > > > there and it's always better to work with one system rather
> with two.
> > > > > > > > The
> > > > > > >
> > > > > > > > colors and labels of the GitHub as very easy to notice.
> > > > > > > > Either way, what ever you decide something needs to be
> change. Either
> > > > > > > > Jira
> > > > > > > > will be more informative or move to GitHub.
> > > > > > > > Thank you all for your good work :)
>
>
>

Re: It's very hard to become a committer on the project

[airflowuser <ai...@protonmail.com.INVALID>]

>> Are you volunteering to sponsor someone's time to be able to do this?

I am. But I have no knowledge of all the components of the project.
I doubt I can be much of value for this tagging task.


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, September 20, 2018 12:37 PM, Ash Berlin-Taylor <as...@apache.org> wrote:

> > Remember my basic question: I want to contribute - how on earth I can find a ticket that is suitable for first time committer? Can you show me?
>
> There aren't that many feature requests in Jira, so looking there for easy tickets, is as you have probably found a fruitless exercise. I'd recommend using Airflow and when you come across something you want fixed, or a feature you want added, that you open a PR for it.
>
> > Again, If decided to stay with Jira.. I highly recommend that someone from the project will maintain it. Don't allow to regular users to tag and set priorities for the tickets.. someone from the project should do it.
>
> Are you volunteering to sponsor someone's time to be able to do this?
>
> > Sent with ProtonMail Secure Email.
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Tuesday, September 18, 2018 11:57 AM, Sid Anand sanand@apache.org wrote:
> >
> > > Hi Folks!
> > > For some history, Airlfow started on GH issues. We also had a very popular Google group. When we moved to Apache, we were told that Jira was the way we needed to go for issue tracking because it resided on Apache infrastructure. When we moved over, we had to drop 100+ GH issues on the floor -- there was no way to transfer them to Jira and maintain the original submitter/owner info since there was no mapping of users between the 2 systems.
> > > Here's a pie chart of our existing issues by status:
> > > https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next
> > > I'm attaching a screen shot as well.
> > > I think we all agree that there is better integration between GH PRs and GH Issues than between GH PRs and Jira issues.
> > > There are some practical matters to consider:
> > >
> > > -   For the 1100-1200 unclosed/unresolved issues, how will we transfer them to GH or will we drop those on the floor? How would we map submitters between the 2 systems, and how would we transfer the content/comments,etc...
> > > -   For the existing closed PRs (>3k), whose PRs reference JIRA, we'd need to keep JIRA around in read-only mode so we could reference the bug/feature details, but somehow disallow new JIRA creations, lest some people continue to use it to create new issues
> > > -   I'm assuming the GH issue naming would not conflict with that of JIRA naming in commit message subjects and PRs. In other words, incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the incubator name will be dropped, so there may be a naming conflict.
> > >
> > > In the end, these are 2 different tools. The issues you raise are mainly around governance.
> > > If you folks would like to propose a new means to manage the JIRAs, can you outline a solution on Wiki and drop a link into an email on this list? We can then raise a vote.
> > > IMHO, our community would scale the best if more people picked up responsibilities such as these. Grooming/Organizing JIRAs doesn't need to be a responsibility owned by the maintainers. Anyone can take the lead on discussions, etc...
> > > -s
> > > On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari sumeet.manit@gmail.com wrote:
> > >
> > > > Strong +1 for moving to GitHub from Jira.
> > > > On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman waksman@gmail.com
> > > > wrote:
> > > >
> > > > > Are there Apache rules preventing us from switching to GitHub Issues?
> > > > > That seems like it might better fit much of Airflow's user base.
> > > > > On Sun, Sep 16, 2018, 9:21 AM Jeff Payne jpayne@bombora.com wrote:
> > > > >
> > > > > > I agree that Jira could be better utilized. I read the original
> > > > > > conversation on the mailing list about how Jira should be used (or if it
> > > > > > should be used at all) and I'm still unclear about why it was picked over
> > > > > > just using github issues. It refers to a dashboard, which I've yet to
> > > > > > investigate, but Jira is much more than just dashboards.
> > > > > > If this project is going to use Jira, then:
> > > > > >
> > > > > > 1.  It would be great to see moderation and labeling of the Jira issues by
> > > > > >     the main contributors to make it easier for people to break into
> > > > > >     contributing.
> > > > > >
> > > > > > 2.  It would also be nice if the initial conversation of whether or not an
> > > > > >     issue warrants development at all happened on the Jira issue, or at least
> > > > > >     some acknowledgement by the main contributors.
> > > > > >
> > > > > > 3.  Larger enhancements and efforts or vague suggestions still get
> > > > > >     discussed on the dev mailing list before a Jira is even opened, but after
> > > > > >     that, the discussion moves to the Jira, with a link back to the mailing
> > > > > >     list email for reference.
> > > > > >
> > > > > > 4.  The discussion on the PR is only concerned with HOW the change/fix is
> > > > > >     implemented.
> > > > > >
> > > > > >
> > > > > > Get Outlook for Androidhttps://aka.ms/ghei36
> > > > > >
> > > > > > From: James Meickle jmeickle@quantopian.com.INVALID
> > > > > > Sent: Sunday, September 16, 2018 7:46:58 AM
> > > > > > To: dev@airflow.apache.org
> > > > > > Subject: Re: It's very hard to become a committer on the project
> > > > > > Definitely agree with this. I'm not always opposed to JIRA for projects,
> > > > > > but the way it's being used for this project makes it very hard to break
> > > > > > into contributing. The split between GH and JIRA is also painful since
> > > > > > there's no automatic integration of them.
> > > > > > On Sun, Sep 16, 2018 at 9:29 AM airflowuser
> > > > > > airflowuser@protonmail.com.invalid wrote:
> > > > > >
> > > > > > > Hello all,
> > > > > > > I'm struggling finding tickets to address and while discussing it on
> > > > > > > chat
> > > > > >
> > > > > > > others reported they had the same problem when they began working on
> > > > > > > the
> > > > > >
> > > > > > > project.
> > > > > > > The problem is due to:
> > > > > > >
> > > > > > > 1.  It's very hard to locate tickets on Jira. The categories are a mess,
> > > > > > >     versions are not enforced. each use can tag,label and set priority at
> > > > > > >     his
> > > > > > >
> > > > > >
> > > > > > > will. No one monitor or overwrite it
> > > > > > > 2. It's impossible for a new committer to find issues which can be
> > > > > > > easy-fix and a "good first issue".
> > > > > > > My suggestions:
> > > > > > >
> > > > > > > 1.  Looking at the ticket system there are usually less than 10 new
> > > > > > >     tickets
> > > > > > >     a day. It won't take too much time for someone with knowledge on the
> > > > > > >     project to properly tag the ticket.
> > > > > > >
> > > > > > > 2.  I think that most of you don't even check the Jira. Most of you
> > > > > > >     submit
> > > > > > >
> > > > > >
> > > > > > > PRs and 5 seconds before opening a ticket (just because you must).
> > > > > > > There
> > > > > > > is
> > > > > >
> > > > > > > no doubt that the Jira is a "side" system which doesn't really perform
> > > > > > > it's
> > > > > > > job.
> > > > > > > Take a look at this:
> > > > > > > https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> > > > > > > a member of the community asks for committers for input but no one
> > > > > > > replies. I doubt this is because no one has input.. I am sure that if a
> > > > > > > PR
> > > > > > > was submitted you had comments. It's simply because you don't see it.
> > > > > > > This
> > > > > > > is why I think the current Jira does't function properly. I think that
> > > > > > > Github can perform a better role. All of you as committers are already
> > > > > > > there and it's always better to work with one system rather with two.
> > > > > > > The
> > > > > >
> > > > > > > colors and labels of the GitHub as very easy to notice.
> > > > > > > Either way, what ever you decide something needs to be change. Either
> > > > > > > Jira
> > > > > > > will be more informative or move to GitHub.
> > > > > > > Thank you all for your good work :)

Re: It's very hard to become a committer on the project

[Ash Berlin-Taylor <as...@apache.org>]

> Remember my basic question: I want to contribute - how on earth I can find a ticket that is suitable for first time committer? Can you show me?

There aren't that many feature requests in Jira, so looking there for easy tickets, is as you have probably found a fruitless exercise. I'd recommend using Airflow and when you come across something you want fixed, or a feature you want added, that you open a PR for it. 

> Again, If decided to stay with Jira.. I highly recommend that someone from the project will maintain it. Don't allow to regular users to tag and set priorities for the tickets.. someone from the project should do it.

Are you volunteering to sponsor someone's time to be able to do this?

> 
> 
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Tuesday, September 18, 2018 11:57 AM, Sid Anand <sa...@apache.org> wrote:
> 
>> Hi Folks!
>> For some history, Airlfow started on GH issues. We also had a very popular Google group. When we moved to Apache, we were told that Jira was the way we needed to go for issue tracking because it resided on Apache infrastructure. When we moved over, we had to drop 100+ GH issues on the floor -- there was no way to transfer them to Jira and maintain the original submitter/owner info since there was no mapping of users between the 2 systems.
>> 
>> Here's a pie chart of our existing issues by status:
>> [https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next](https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next)
>> 
>> I'm attaching a screen shot as well.
>> 
>> I think we all agree that there is better integration between GH PRs and GH Issues than between GH PRs and Jira issues.
>> 
>> There are some practical matters to consider:
>> 
>> - For the 1100-1200 unclosed/unresolved issues, how will we transfer them to GH or will we drop those on the floor? How would we map submitters between the 2 systems, and how would we transfer the content/comments,etc...
>> - For the existing closed PRs (>3k), whose PRs reference JIRA, we'd need to keep JIRA around in read-only mode so we could reference the bug/feature details, but somehow disallow new JIRA creations, lest some people continue to use it to create new issues
>> - I'm assuming the GH issue naming would not conflict with that of JIRA naming in commit message subjects and PRs. In other words, incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the incubator name will be dropped, so there may be a naming conflict.
>> 
>> In the end, these are 2 different tools. The issues you raise are mainly around governance.
>> 
>> If you folks would like to propose a new means to manage the JIRAs, can you outline a solution on Wiki and drop a link into an email on this list? We can then raise a vote.
>> 
>> IMHO, our community would scale the best if more people picked up responsibilities such as these. Grooming/Organizing JIRAs doesn't need to be a responsibility owned by the maintainers. Anyone can take the lead on discussions, etc...
>> 
>> -s
>> 
>> On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari <su...@gmail.com> wrote:
>> 
>>> Strong +1 for moving to GitHub from Jira.
>>> 
>>> On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman <wa...@gmail.com>
>>> wrote:
>>> 
>>>> Are there Apache rules preventing us from switching to GitHub Issues?
>>>> 
>>>> That seems like it might better fit much of Airflow's user base.
>>>> 
>>>> 
>>>> On Sun, Sep 16, 2018, 9:21 AM Jeff Payne <jp...@bombora.com> wrote:
>>>> 
>>>>> I agree that Jira could be better utilized. I read the original
>>>>> conversation on the mailing list about how Jira should be used (or if it
>>>>> should be used at all) and I'm still unclear about why it was picked over
>>>>> just using github issues. It refers to a dashboard, which I've yet to
>>>>> investigate, but Jira is much more than just dashboards.
>>>>> 
>>>>> If this project is going to use Jira, then:
>>>>> 
>>>>> 1) It would be great to see moderation and labeling of the Jira issues by
>>>>> the main contributors to make it easier for people to break into
>>>>> contributing.
>>>>> 2) It would also be nice if the initial conversation of whether or not an
>>>>> issue warrants development at all happened on the Jira issue, or at least
>>>>> some acknowledgement by the main contributors.
>>>>> 3) Larger enhancements and efforts or vague suggestions still get
>>>>> discussed on the dev mailing list before a Jira is even opened, but after
>>>>> that, the discussion moves to the Jira, with a link back to the mailing
>>>>> list email for reference.
>>>>> 4) The discussion on the PR is only concerned with HOW the change/fix is
>>>>> implemented.
>>>>> 
>>>>> Get Outlook for Android<https://aka.ms/ghei36>
>>>>> 
>>>>> ________________________________
>>>>> From: James Meickle <jm...@quantopian.com.INVALID>
>>>>> Sent: Sunday, September 16, 2018 7:46:58 AM
>>>>> To: dev@airflow.apache.org
>>>>> Subject: Re: It's very hard to become a committer on the project
>>>>> 
>>>>> Definitely agree with this. I'm not always opposed to JIRA for projects,
>>>>> but the way it's being used for this project makes it very hard to break
>>>>> into contributing. The split between GH and JIRA is also painful since
>>>>> there's no automatic integration of them.
>>>>> 
>>>>> On Sun, Sep 16, 2018 at 9:29 AM airflowuser
>>>>> <ai...@protonmail.com.invalid> wrote:
>>>>> 
>>>>>> Hello all,
>>>>>> 
>>>>>> I'm struggling finding tickets to address and while discussing it on
>>>> chat
>>>>>> others reported they had the same problem when they began working on
>>>> the
>>>>>> project.
>>>>>> 
>>>>>> The problem is due to:
>>>>>> 1. It's very hard to locate tickets on Jira. The categories are a mess,
>>>>>> versions are not enforced. each use can tag,label and set priority at
>>>> his
>>>>>> will. No one monitor or overwrite it
>>>>>> 2. It's impossible for a new committer to  find issues which can be
>>>>>> easy-fix and a "good first issue".
>>>>>> 
>>>>>> My suggestions:
>>>>>> 1. Looking at the ticket system there are usually less than 10 new
>>>>> tickets
>>>>>> a day. It won't take too much time for someone with knowledge on the
>>>>>> project to properly tag  the ticket.
>>>>>> 
>>>>>> 2. I think that most of you don't even check the Jira. Most of you
>>>> submit
>>>>>> PRs and 5 seconds before opening a ticket (just because you must).
>>>> There
>>>>> is
>>>>>> no doubt that the Jira is a "side" system which doesn't really perform
>>>>> it's
>>>>>> job.
>>>>>> 
>>>>>> Take a look at this:
>>>>>> https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
>>>>>> a member of the community asks for committers for input but no one
>>>>>> replies. I doubt this is because no one has input.. I am sure that if a
>>>>> PR
>>>>>> was submitted you had comments. It's simply because you don't see it.
>>>>> This
>>>>>> is why I think the current Jira does't function properly. I think that
>>>>>> Github can perform a better role. All of you as committers are already
>>>>>> there and it's always better to work with one system rather with two.
>>>> The
>>>>>> colors and labels of the GitHub as very easy to notice.
>>>>>> 
>>>>>> Either way, what ever you decide something needs to be change. Either
>>>>> Jira
>>>>>> will be more informative or move to GitHub.
>>>>>> 
>>>>>> Thank you all for your good work :)
>>>>> 

Re: It's very hard to become a committer on the project

[airflowuser <ai...@protonmail.com.INVALID>]

If the Jira could be converted into read only then there is no problem.
Having 1000+ tickets on Jira isn't really an issue. It's not like committers actually pass the tickets and choose what to do from it. Tickets of 2017, 2016 are most likely to never be fixed or even already have been fixed but no one will check it.
Note that many tickets are on 1.7 and 1.8

Again, If decided to stay with Jira.. I highly recommend that someone from the project will maintain it. Don't allow to regular users to tag and set priorities for the tickets.. someone from the project should do it.

Remember my basic question: I want to contribute - how on earth I can find a ticket that is suitable for first time committer? Can you show me?

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, September 18, 2018 11:57 AM, Sid Anand <sa...@apache.org> wrote:

> Hi Folks!
> For some history, Airlfow started on GH issues. We also had a very popular Google group. When we moved to Apache, we were told that Jira was the way we needed to go for issue tracking because it resided on Apache infrastructure. When we moved over, we had to drop 100+ GH issues on the floor -- there was no way to transfer them to Jira and maintain the original submitter/owner info since there was no mapping of users between the 2 systems.
>
> Here's a pie chart of our existing issues by status:
> [https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next](https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next)
>
> I'm attaching a screen shot as well.
>
> I think we all agree that there is better integration between GH PRs and GH Issues than between GH PRs and Jira issues.
>
> There are some practical matters to consider:
>
> - For the 1100-1200 unclosed/unresolved issues, how will we transfer them to GH or will we drop those on the floor? How would we map submitters between the 2 systems, and how would we transfer the content/comments,etc...
> - For the existing closed PRs (>3k), whose PRs reference JIRA, we'd need to keep JIRA around in read-only mode so we could reference the bug/feature details, but somehow disallow new JIRA creations, lest some people continue to use it to create new issues
> - I'm assuming the GH issue naming would not conflict with that of JIRA naming in commit message subjects and PRs. In other words, incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the incubator name will be dropped, so there may be a naming conflict.
>
> In the end, these are 2 different tools. The issues you raise are mainly around governance.
>
> If you folks would like to propose a new means to manage the JIRAs, can you outline a solution on Wiki and drop a link into an email on this list? We can then raise a vote.
>
> IMHO, our community would scale the best if more people picked up responsibilities such as these. Grooming/Organizing JIRAs doesn't need to be a responsibility owned by the maintainers. Anyone can take the lead on discussions, etc...
>
> -s
>
> On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari <su...@gmail.com> wrote:
>
>> Strong +1 for moving to GitHub from Jira.
>>
>> On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman <wa...@gmail.com>
>> wrote:
>>
>>> Are there Apache rules preventing us from switching to GitHub Issues?
>>>
>>> That seems like it might better fit much of Airflow's user base.
>>>
>>>
>>> On Sun, Sep 16, 2018, 9:21 AM Jeff Payne <jp...@bombora.com> wrote:
>>>
>>> > I agree that Jira could be better utilized. I read the original
>>> > conversation on the mailing list about how Jira should be used (or if it
>>> > should be used at all) and I'm still unclear about why it was picked over
>>> > just using github issues. It refers to a dashboard, which I've yet to
>>> > investigate, but Jira is much more than just dashboards.
>>> >
>>> > If this project is going to use Jira, then:
>>> >
>>> > 1) It would be great to see moderation and labeling of the Jira issues by
>>> > the main contributors to make it easier for people to break into
>>> > contributing.
>>> > 2) It would also be nice if the initial conversation of whether or not an
>>> > issue warrants development at all happened on the Jira issue, or at least
>>> > some acknowledgement by the main contributors.
>>> > 3) Larger enhancements and efforts or vague suggestions still get
>>> > discussed on the dev mailing list before a Jira is even opened, but after
>>> > that, the discussion moves to the Jira, with a link back to the mailing
>>> > list email for reference.
>>> > 4) The discussion on the PR is only concerned with HOW the change/fix is
>>> > implemented.
>>> >
>>> > Get Outlook for Android<https://aka.ms/ghei36>
>>> >
>>> > ________________________________
>>> > From: James Meickle <jm...@quantopian.com.INVALID>
>>> > Sent: Sunday, September 16, 2018 7:46:58 AM
>>> > To: dev@airflow.apache.org
>>> > Subject: Re: It's very hard to become a committer on the project
>>> >
>>> > Definitely agree with this. I'm not always opposed to JIRA for projects,
>>> > but the way it's being used for this project makes it very hard to break
>>> > into contributing. The split between GH and JIRA is also painful since
>>> > there's no automatic integration of them.
>>> >
>>> > On Sun, Sep 16, 2018 at 9:29 AM airflowuser
>>> > <ai...@protonmail.com.invalid> wrote:
>>> >
>>> > > Hello all,
>>> > >
>>> > > I'm struggling finding tickets to address and while discussing it on
>>> chat
>>> > > others reported they had the same problem when they began working on
>>> the
>>> > > project.
>>> > >
>>> > > The problem is due to:
>>> > > 1. It's very hard to locate tickets on Jira. The categories are a mess,
>>> > > versions are not enforced. each use can tag,label and set priority at
>>> his
>>> > > will. No one monitor or overwrite it
>>> > > 2. It's impossible for a new committer to  find issues which can be
>>> > > easy-fix and a "good first issue".
>>> > >
>>> > > My suggestions:
>>> > > 1. Looking at the ticket system there are usually less than 10 new
>>> > tickets
>>> > > a day. It won't take too much time for someone with knowledge on the
>>> > > project to properly tag  the ticket.
>>> > >
>>> > > 2. I think that most of you don't even check the Jira. Most of you
>>> submit
>>> > > PRs and 5 seconds before opening a ticket (just because you must).
>>> There
>>> > is
>>> > > no doubt that the Jira is a "side" system which doesn't really perform
>>> > it's
>>> > > job.
>>> > >
>>> > > Take a look at this:
>>> > > https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
>>> > > a member of the community asks for committers for input but no one
>>> > > replies. I doubt this is because no one has input.. I am sure that if a
>>> > PR
>>> > > was submitted you had comments. It's simply because you don't see it.
>>> > This
>>> > > is why I think the current Jira does't function properly. I think that
>>> > > Github can perform a better role. All of you as committers are already
>>> > > there and it's always better to work with one system rather with two.
>>> The
>>> > > colors and labels of the GitHub as very easy to notice.
>>> > >
>>> > > Either way, what ever you decide something needs to be change. Either
>>> > Jira
>>> > > will be more informative or move to GitHub.
>>> > >
>>> > > Thank you all for your good work :)
>>> >
>>>

Re: It's very hard to become a committer on the project

[Jeff Payne <jp...@bombora.com>]

I'll gladly give being triage nurse a shot.

Get Outlook for Android<https://aka.ms/ghei36>




From: Sid Anand < sanand @apache.org>
Sent: Tuesday, September 18, 2018 8:57:13 AM
To: dev@airflow.incubator.apache.org
Subject: Re: It's very hard to become a committer on the project

Hi Folks!
For some history, Airlfow started on GH issues. We also had a very popular Google group. When we moved to Apache, we were told that Jira was the way we needed to go for issue tracking because it resided on Apache infrastructure. When we moved over, we had to drop 100+ GH issues on the floor -- there was no way to transfer them to Jira and maintain the original submitter/owner info since there was no mapping of users between the 2 systems.

Here's a pie chart of our existing issues by status:
https://issues.apache.org/jira/secure/ConfigureReport.jspa?<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> projectOrFilterId<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> =project-12320023&<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> statistictype<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> =statuses&<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> selectedProjectId<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> =12320023&<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> reportKey<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> =com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> A5KQ<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> -2QAV-<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> T4JA<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> -<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> FDED<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next> |a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next>

I'm attaching a screen shot as well.



I think we all agree that there is better integration between GH PRs and GH Issues than between GH PRs and Jira issues.

There are some practical matters to consider:
For the 1100-1200 unclosed/unresolved issues, how will we transfer them to GH or will we drop those on the floor? How would we map submitters between the 2 systems, and how would we transfer the content/comments,etc...
For the existing closed PRs (>3k), whose PRs reference JIRA, we'd need to keep JIRA around in read-only mode so we could reference the bug/feature details, but somehow disallow new JIRA creations, lest some people continue to use it to create new issuesI'm assuming the GH issue naming would not conflict with that of JIRA naming in commit message subjects and PRs. In other words, incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the incubator name will be dropped, so there may be a naming conflict.
In the end, these are 2 different tools. The issues you raise are mainly around governance.

If you folks would like to propose a new means to manage the JIRAs, can you outline a solution on Wiki and drop a link into an email on this list? We can then raise a vote.

IMHO, our community would scale the best if more people picked up responsibilities such as these. Grooming/Organizing JIRAs doesn't need to be a responsibility owned by the maintainers. Anyone can take the lead on discussions, etc...

-s

On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari < sumeet.manit@gmail.com<ma...@gmail.com>> wrote:
Strong +1 for moving to GitHub from Jira.

On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman < waksman<ma...@gmail.com> @gmail.com<ma...@gmail.com>>
wrote:

> Are there Apache rules preventing us from switching to GitHub Issues?
>
> That seems like it might better fit much of Airflow's user base.
>
>
> On Sun, Sep 16, 2018, 9:21 AM Jeff Payne < jpayne<ma...@bombora.com> @bombora.com<ma...@bombora.com>> wrote:
>
> > I agree that Jira could be better utilized. I read the original
> > conversation on the mailing list about how Jira should be used (or if it
> > should be used at all) and I'm still unclear about why it was picked over
> > just using github issues. It refers to a dashboard, which I've yet to
> > investigate, but Jira is much more than just dashboards.
> >
> > If this project is going to use Jira, then:
> >
> > 1) It would be great to see moderation and labeling of the Jira issues by
> > the main contributors to make it easier for people to break into
> > contributing.
> > 2) It would also be nice if the initial conversation of whether or not an
> > issue warrants development at all happened on the Jira issue, or at least
> > some acknowledgement by the main contributors.
> > 3) Larger enhancements and efforts or vague suggestions still get
> > discussed on the dev mailing list before a Jira is even opened, but after
> > that, the discussion moves to the Jira, with a link back to the mailing
> > list email for reference.
> > 4) The discussion on the PR is only concerned with HOW the change/fix is
> > implemented.
> >
> > Get Outlook for Android< https://aka.ms/<https://aka.ms/ghei36> ghei36<https://aka.ms/ghei36>>
> >
> > ________________________________
> > From: James Meickle < jmeickle<ma...@quantopian.com> @quantopian.com<ma...@quantopian.com>.INVALID>
> > Sent: Sunday, September 16, 2018 7:46:58 AM
> > To: dev@airflow.apache.org<ma...@airflow.apache.org>
> > Subject: Re: It's very hard to become a committer on the project
> >
> > Definitely agree with this. I'm not always opposed to JIRA for projects,
> > but the way it's being used for this project makes it very hard to break
> > into contributing. The split between GH and JIRA is also painful since
> > there's no automatic integration of them.
> >
> > On Sun, Sep 16, 2018 at 9:29 AM airflowuser
> > < airflowuser<ma...@protonmail.com> @protonmail.com<ma...@protonmail.com>.invalid> wrote:
> >
> > > Hello all,
> > >
> > > I'm struggling finding tickets to address and while discussing it on
> chat
> > > others reported they had the same problem when they began working on
> the
> > > project.
> > >
> > > The problem is due to:
> > > 1. It's very hard to locate tickets on Jira. The categories are a mess,
> > > versions are not enforced. each use can tag,label and set priority at
> his
> > > will. No one monitor or overwrite it
> > > 2. It's impossible for a new committer to  find issues which can be
> > > easy-fix and a "good first issue".
> > >
> > > My suggestions:
> > > 1. Looking at the ticket system there are usually less than 10 new
> > tickets
> > > a day. It won't take too much time for someone with knowledge on the
> > > project to properly tag  the ticket.
> > >
> > > 2. I think that most of you don't even check the Jira. Most of you
> submit
> > > PRs and 5 seconds before opening a ticket (just because you must).
> There
> > is
> > > no doubt that the Jira is a "side" system which doesn't really perform
> > it's
> > > job.
> > >
> > > Take a look at this:
> > > https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> > > a member of the community asks for committers for input but no one
> > > replies. I doubt this is because no one has input.. I am sure that if a
> > PR
> > > was submitted you had comments. It's simply because you don't see it.
> > This
> > > is why I think the current Jira does't function properly. I think that
> > > Github can perform a better role. All of you as committers are already
> > > there and it's always better to work with one system rather with two.
> The
> > > colors and labels of the GitHub as very easy to notice.
> > >
> > > Either way, what ever you decide something needs to be change. Either
> > Jira
> > > will be more informative or move to GitHub.
> > >
> > > Thank you all for your good work :)
> >
>

Re: It's very hard to become a committer on the project

[Ash Berlin-Taylor <as...@apache.org>]

> On 18 Sep 2018, at 13:07, Ash Berlin-Taylor <as...@apache.org> wrote:
> 
> Somewhat annoyingly you can't (or we don't have permission to) set the fix version on a closed Jira ticket. We can probably ask for permission to edit closed/resolved Jira tickets in the AIRFLOW project, which would remove some of the pain here. I've asked for that https://issues.apache.org/jira/browse/INFRA-17033 <https://issues.apache.org/jira/browse/INFRA-17033>

I was being blind- the Edit button is in a different place on closed issues is all >_<

Re: It's very hard to become a committer on the project

[James Meickle <jm...@quantopian.com.INVALID>]

I would definitely be interested in doing some JIRA project management if
the bureaucracy overhead isn't too high, but I'm definitely not familiar
with how Apache projects work, so that's somewhat of a barrier.

On Tue, Sep 18, 2018 at 8:07 AM Ash Berlin-Taylor <as...@apache.org> wrote:

> Before we could merge directly on Github the way we (committers) closed
> PRs was by using a script that would close the Jira ticket and set the fix
> version at the same time.
>
> Somewhat annoyingly you can't (or we don't have permission to) set the fix
> version on a closed Jira ticket. We can probably ask for permission to edit
> closed/resolved Jira tickets in the AIRFLOW project, which would remove
> some of the pain here. I've asked for that
> https://issues.apache.org/jira/browse/INFRA-17033
>
> Thanks for finding the issues to close btw, it's helpful.
>
> -ash
>
> > On 18 Sep 2018, at 12:33, Deng Xiaodong <xd...@gmail.com> wrote:
> >
> > Hi,
> >
> > Regarding your 2nd point, I think one of the reasons for what the
> > committers are not using hook to automatically close JIRA ticket after PR
> > merged is that they need to set fix version for each ticket.
> >
> > XD
> >
> >
> > On Tue, Sep 18, 2018 at 17:17 Юли Волкова <xnuinside@gmail.com <mailto:
> xnuinside@gmail.com>> wrote:
> >
> >> Hi, Sid, thanks for some clarification about JIRA. At now, I walking
> >> through jira's task and ask Ash or other guys with admins right to close
> >> issues (for example:
> >>
> >>
> https://issues.apache.org/jira/browse/AIRFLOW-307?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> >> ),
> >> because PRs was successful merged 2 years ago. I would like to help in
> this
> >> scope: 1) If I have same moderators rights I can close tickets by myself
> >> 2) JIRA is a powerful tool on about integration - question only in do we
> >> have admin rights to add different integrations and triggers-hooks to
> JIRA.
> >> First of all, I propose to create hook what close task after PR was
> merged
> >> in master. Many task are open without any status changing with  already
> >> merged PRs.
> >>
> >> On Tue, Sep 18, 2018 at 11:58 AM Sid Anand <sa...@apache.org> wrote:
> >>
> >>> Hi Folks!
> >>> For some history, Airlfow started on GH issues. We also had a very
> >> popular
> >>> Google group. When we moved to Apache, we were told that Jira was the
> way
> >>> we needed to go for issue tracking because it resided on Apache
> >>> infrastructure. When we moved over, we had to drop 100+ GH issues on
> the
> >>> floor -- there was no way to transfer them to Jira and maintain the
> >>> original submitter/owner info since there was no mapping of users
> between
> >>> the 2 systems.
> >>>
> >>> Here's a pie chart of our existing issues by status:
> >>>
> >>>
> >>
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next
> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next>
> >> <
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next
> >
> >>> <
> >>
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next
> <
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next
> >
> >>>
> >>>
> >>> I'm attaching a screen shot as well.
> >>>
> >>> [image: Screenshot 2018-09-16 11.28.57.png]
> >>>
> >>> I think we all agree that there is better integration between GH PRs
> and
> >>> GH Issues than between GH PRs and Jira issues.
> >>>
> >>> There are some practical matters to consider:
> >>>
> >>>   - For the 1100-1200 unclosed/unresolved issues, how will we transfer
> >>>   them to GH or will we drop those on the floor? How would we map
> >> submitters
> >>>   between the 2 systems, and how would we transfer the
> >> content/comments,etc...
> >>>   - For the existing closed PRs (>3k), whose PRs reference JIRA, we'd
> >>>   need to keep JIRA around in read-only mode so we could reference the
> >>>   bug/feature details, but somehow disallow new JIRA creations, lest
> >> some
> >>>   people continue to use it to create new issues
> >>>   - I'm assuming the GH issue naming would not conflict with that of
> >>>   JIRA naming in commit message subjects and PRs. In other words,
> >>>   incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly
> >>>   conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the
> >> incubator name
> >>>   will be dropped, so there may be a naming conflict.
> >>>
> >>> In the end, these are 2 different tools. The issues you raise are
> mainly
> >>> around governance.
> >>>
> >>> If you folks would like to propose a new means to manage the JIRAs, can
> >>> you outline a solution on Wiki and drop a link into an email on this
> >> list?
> >>> We can then raise a vote.
> >>>
> >>> IMHO, our community would scale the best if more people picked up
> >>> responsibilities such as these. Grooming/Organizing JIRAs doesn't need
> to
> >>> be a responsibility owned by the maintainers. Anyone can take the lead
> on
> >>> discussions, etc...
> >>>
> >>> -s
> >>>
> >>> On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari <
> sumeet.manit@gmail.com
> >>>
> >>> wrote:
> >>>
> >>>> Strong +1 for moving to GitHub from Jira.
> >>>>
> >>>> On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman <
> >> waksman@gmail.com
> >>>>>
> >>>> wrote:
> >>>>
> >>>>> Are there Apache rules preventing us from switching to GitHub Issues?
> >>>>>
> >>>>> That seems like it might better fit much of Airflow's user base.
> >>>>>
> >>>>>
> >>>>> On Sun, Sep 16, 2018, 9:21 AM Jeff Payne <jp...@bombora.com> wrote:
> >>>>>
> >>>>>> I agree that Jira could be better utilized. I read the original
> >>>>>> conversation on the mailing list about how Jira should be used (or
> >> if
> >>>> it
> >>>>>> should be used at all) and I'm still unclear about why it was picked
> >>>> over
> >>>>>> just using github issues. It refers to a dashboard, which I've yet
> >> to
> >>>>>> investigate, but Jira is much more than just dashboards.
> >>>>>>
> >>>>>> If this project is going to use Jira, then:
> >>>>>>
> >>>>>> 1) It would be great to see moderation and labeling of the Jira
> >>>> issues by
> >>>>>> the main contributors to make it easier for people to break into
> >>>>>> contributing.
> >>>>>> 2) It would also be nice if the initial conversation of whether or
> >>>> not an
> >>>>>> issue warrants development at all happened on the Jira issue, or at
> >>>> least
> >>>>>> some acknowledgement by the main contributors.
> >>>>>> 3) Larger enhancements and efforts or vague suggestions still get
> >>>>>> discussed on the dev mailing list before a Jira is even opened, but
> >>>> after
> >>>>>> that, the discussion moves to the Jira, with a link back to the
> >>>> mailing
> >>>>>> list email for reference.
> >>>>>> 4) The discussion on the PR is only concerned with HOW the
> >> change/fix
> >>>> is
> >>>>>> implemented.
> >>>>>>
> >>>>>> Get Outlook for Android<https://aka.ms/ghei36>
> >>>>>>
> >>>>>> ________________________________
> >>>>>> From: James Meickle <jm...@quantopian.com.INVALID>
> >>>>>> Sent: Sunday, September 16, 2018 7:46:58 AM
> >>>>>> To: dev@airflow.apache.org
> >>>>>> Subject: Re: It's very hard to become a committer on the project
> >>>>>>
> >>>>>> Definitely agree with this. I'm not always opposed to JIRA for
> >>>> projects,
> >>>>>> but the way it's being used for this project makes it very hard to
> >>>> break
> >>>>>> into contributing. The split between GH and JIRA is also painful
> >> since
> >>>>>> there's no automatic integration of them.
> >>>>>>
> >>>>>> On Sun, Sep 16, 2018 at 9:29 AM airflowuser
> >>>>>> <ai...@protonmail.com.invalid> wrote:
> >>>>>>
> >>>>>>> Hello all,
> >>>>>>>
> >>>>>>> I'm struggling finding tickets to address and while discussing it
> >> on
> >>>>> chat
> >>>>>>> others reported they had the same problem when they began working
> >> on
> >>>>> the
> >>>>>>> project.
> >>>>>>>
> >>>>>>> The problem is due to:
> >>>>>>> 1. It's very hard to locate tickets on Jira. The categories are a
> >>>> mess,
> >>>>>>> versions are not enforced. each use can tag,label and set priority
> >>>> at
> >>>>> his
> >>>>>>> will. No one monitor or overwrite it
> >>>>>>> 2. It's impossible for a new committer to  find issues which can
> >> be
> >>>>>>> easy-fix and a "good first issue".
> >>>>>>>
> >>>>>>> My suggestions:
> >>>>>>> 1. Looking at the ticket system there are usually less than 10 new
> >>>>>> tickets
> >>>>>>> a day. It won't take too much time for someone with knowledge on
> >> the
> >>>>>>> project to properly tag  the ticket.
> >>>>>>>
> >>>>>>> 2. I think that most of you don't even check the Jira. Most of you
> >>>>> submit
> >>>>>>> PRs and 5 seconds before opening a ticket (just because you must).
> >>>>> There
> >>>>>> is
> >>>>>>> no doubt that the Jira is a "side" system which doesn't really
> >>>> perform
> >>>>>> it's
> >>>>>>> job.
> >>>>>>>
> >>>>>>> Take a look at this:
> >>>>>>>
> >> https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> >>>>>>> a member of the community asks for committers for input but no one
> >>>>>>> replies. I doubt this is because no one has input.. I am sure that
> >>>> if a
> >>>>>> PR
> >>>>>>> was submitted you had comments. It's simply because you don't see
> >>>> it.
> >>>>>> This
> >>>>>>> is why I think the current Jira does't function properly. I think
> >>>> that
> >>>>>>> Github can perform a better role. All of you as committers are
> >>>> already
> >>>>>>> there and it's always better to work with one system rather with
> >>>> two.
> >>>>> The
> >>>>>>> colors and labels of the GitHub as very easy to notice.
> >>>>>>>
> >>>>>>> Either way, what ever you decide something needs to be change.
> >>>> Either
> >>>>>> Jira
> >>>>>>> will be more informative or move to GitHub.
> >>>>>>>
> >>>>>>> Thank you all for your good work :)
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> --
> >> _________
> >>
> >> С уважением, Юлия Волкова
> >> Тел. : +7 (911) 116-71-82
>
>

Re: It's very hard to become a committer on the project

[Ash Berlin-Taylor <as...@apache.org>]

Before we could merge directly on Github the way we (committers) closed PRs was by using a script that would close the Jira ticket and set the fix version at the same time.

Somewhat annoyingly you can't (or we don't have permission to) set the fix version on a closed Jira ticket. We can probably ask for permission to edit closed/resolved Jira tickets in the AIRFLOW project, which would remove some of the pain here. I've asked for that https://issues.apache.org/jira/browse/INFRA-17033

Thanks for finding the issues to close btw, it's helpful.

-ash

> On 18 Sep 2018, at 12:33, Deng Xiaodong <xd...@gmail.com> wrote:
> 
> Hi,
> 
> Regarding your 2nd point, I think one of the reasons for what the
> committers are not using hook to automatically close JIRA ticket after PR
> merged is that they need to set fix version for each ticket.
> 
> XD
> 
> 
> On Tue, Sep 18, 2018 at 17:17 Юли Волкова <xnuinside@gmail.com <ma...@gmail.com>> wrote:
> 
>> Hi, Sid, thanks for some clarification about JIRA. At now, I walking
>> through jira's task and ask Ash or other guys with admins right to close
>> issues (for example:
>> 
>> https://issues.apache.org/jira/browse/AIRFLOW-307?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
>> ),
>> because PRs was successful merged 2 years ago. I would like to help in this
>> scope: 1) If I have same moderators rights I can close tickets by myself
>> 2) JIRA is a powerful tool on about integration - question only in do we
>> have admin rights to add different integrations and triggers-hooks to JIRA.
>> First of all, I propose to create hook what close task after PR was merged
>> in master. Many task are open without any status changing with  already
>> merged PRs.
>> 
>> On Tue, Sep 18, 2018 at 11:58 AM Sid Anand <sa...@apache.org> wrote:
>> 
>>> Hi Folks!
>>> For some history, Airlfow started on GH issues. We also had a very
>> popular
>>> Google group. When we moved to Apache, we were told that Jira was the way
>>> we needed to go for issue tracking because it resided on Apache
>>> infrastructure. When we moved over, we had to drop 100+ GH issues on the
>>> floor -- there was no way to transfer them to Jira and maintain the
>>> original submitter/owner info since there was no mapping of users between
>>> the 2 systems.
>>> 
>>> Here's a pie chart of our existing issues by status:
>>> 
>>> 
>> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next
>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next>
>>> <
>> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next>
>>> 
>>> 
>>> I'm attaching a screen shot as well.
>>> 
>>> [image: Screenshot 2018-09-16 11.28.57.png]
>>> 
>>> I think we all agree that there is better integration between GH PRs and
>>> GH Issues than between GH PRs and Jira issues.
>>> 
>>> There are some practical matters to consider:
>>> 
>>>   - For the 1100-1200 unclosed/unresolved issues, how will we transfer
>>>   them to GH or will we drop those on the floor? How would we map
>> submitters
>>>   between the 2 systems, and how would we transfer the
>> content/comments,etc...
>>>   - For the existing closed PRs (>3k), whose PRs reference JIRA, we'd
>>>   need to keep JIRA around in read-only mode so we could reference the
>>>   bug/feature details, but somehow disallow new JIRA creations, lest
>> some
>>>   people continue to use it to create new issues
>>>   - I'm assuming the GH issue naming would not conflict with that of
>>>   JIRA naming in commit message subjects and PRs. In other words,
>>>   incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly
>>>   conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the
>> incubator name
>>>   will be dropped, so there may be a naming conflict.
>>> 
>>> In the end, these are 2 different tools. The issues you raise are mainly
>>> around governance.
>>> 
>>> If you folks would like to propose a new means to manage the JIRAs, can
>>> you outline a solution on Wiki and drop a link into an email on this
>> list?
>>> We can then raise a vote.
>>> 
>>> IMHO, our community would scale the best if more people picked up
>>> responsibilities such as these. Grooming/Organizing JIRAs doesn't need to
>>> be a responsibility owned by the maintainers. Anyone can take the lead on
>>> discussions, etc...
>>> 
>>> -s
>>> 
>>> On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari <sumeet.manit@gmail.com
>>> 
>>> wrote:
>>> 
>>>> Strong +1 for moving to GitHub from Jira.
>>>> 
>>>> On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman <
>> waksman@gmail.com
>>>>> 
>>>> wrote:
>>>> 
>>>>> Are there Apache rules preventing us from switching to GitHub Issues?
>>>>> 
>>>>> That seems like it might better fit much of Airflow's user base.
>>>>> 
>>>>> 
>>>>> On Sun, Sep 16, 2018, 9:21 AM Jeff Payne <jp...@bombora.com> wrote:
>>>>> 
>>>>>> I agree that Jira could be better utilized. I read the original
>>>>>> conversation on the mailing list about how Jira should be used (or
>> if
>>>> it
>>>>>> should be used at all) and I'm still unclear about why it was picked
>>>> over
>>>>>> just using github issues. It refers to a dashboard, which I've yet
>> to
>>>>>> investigate, but Jira is much more than just dashboards.
>>>>>> 
>>>>>> If this project is going to use Jira, then:
>>>>>> 
>>>>>> 1) It would be great to see moderation and labeling of the Jira
>>>> issues by
>>>>>> the main contributors to make it easier for people to break into
>>>>>> contributing.
>>>>>> 2) It would also be nice if the initial conversation of whether or
>>>> not an
>>>>>> issue warrants development at all happened on the Jira issue, or at
>>>> least
>>>>>> some acknowledgement by the main contributors.
>>>>>> 3) Larger enhancements and efforts or vague suggestions still get
>>>>>> discussed on the dev mailing list before a Jira is even opened, but
>>>> after
>>>>>> that, the discussion moves to the Jira, with a link back to the
>>>> mailing
>>>>>> list email for reference.
>>>>>> 4) The discussion on the PR is only concerned with HOW the
>> change/fix
>>>> is
>>>>>> implemented.
>>>>>> 
>>>>>> Get Outlook for Android<https://aka.ms/ghei36>
>>>>>> 
>>>>>> ________________________________
>>>>>> From: James Meickle <jm...@quantopian.com.INVALID>
>>>>>> Sent: Sunday, September 16, 2018 7:46:58 AM
>>>>>> To: dev@airflow.apache.org
>>>>>> Subject: Re: It's very hard to become a committer on the project
>>>>>> 
>>>>>> Definitely agree with this. I'm not always opposed to JIRA for
>>>> projects,
>>>>>> but the way it's being used for this project makes it very hard to
>>>> break
>>>>>> into contributing. The split between GH and JIRA is also painful
>> since
>>>>>> there's no automatic integration of them.
>>>>>> 
>>>>>> On Sun, Sep 16, 2018 at 9:29 AM airflowuser
>>>>>> <ai...@protonmail.com.invalid> wrote:
>>>>>> 
>>>>>>> Hello all,
>>>>>>> 
>>>>>>> I'm struggling finding tickets to address and while discussing it
>> on
>>>>> chat
>>>>>>> others reported they had the same problem when they began working
>> on
>>>>> the
>>>>>>> project.
>>>>>>> 
>>>>>>> The problem is due to:
>>>>>>> 1. It's very hard to locate tickets on Jira. The categories are a
>>>> mess,
>>>>>>> versions are not enforced. each use can tag,label and set priority
>>>> at
>>>>> his
>>>>>>> will. No one monitor or overwrite it
>>>>>>> 2. It's impossible for a new committer to  find issues which can
>> be
>>>>>>> easy-fix and a "good first issue".
>>>>>>> 
>>>>>>> My suggestions:
>>>>>>> 1. Looking at the ticket system there are usually less than 10 new
>>>>>> tickets
>>>>>>> a day. It won't take too much time for someone with knowledge on
>> the
>>>>>>> project to properly tag  the ticket.
>>>>>>> 
>>>>>>> 2. I think that most of you don't even check the Jira. Most of you
>>>>> submit
>>>>>>> PRs and 5 seconds before opening a ticket (just because you must).
>>>>> There
>>>>>> is
>>>>>>> no doubt that the Jira is a "side" system which doesn't really
>>>> perform
>>>>>> it's
>>>>>>> job.
>>>>>>> 
>>>>>>> Take a look at this:
>>>>>>> 
>> https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
>>>>>>> a member of the community asks for committers for input but no one
>>>>>>> replies. I doubt this is because no one has input.. I am sure that
>>>> if a
>>>>>> PR
>>>>>>> was submitted you had comments. It's simply because you don't see
>>>> it.
>>>>>> This
>>>>>>> is why I think the current Jira does't function properly. I think
>>>> that
>>>>>>> Github can perform a better role. All of you as committers are
>>>> already
>>>>>>> there and it's always better to work with one system rather with
>>>> two.
>>>>> The
>>>>>>> colors and labels of the GitHub as very easy to notice.
>>>>>>> 
>>>>>>> Either way, what ever you decide something needs to be change.
>>>> Either
>>>>>> Jira
>>>>>>> will be more informative or move to GitHub.
>>>>>>> 
>>>>>>> Thank you all for your good work :)
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
>> --
>> _________
>> 
>> С уважением, Юлия Волкова
>> Тел. : +7 (911) 116-71-82

Re: It's very hard to become a committer on the project

[Deng Xiaodong <xd...@gmail.com>]

Hi,

Regarding your 2nd point, I think one of the reasons for what the
committers are not using hook to automatically close JIRA ticket after PR
merged is that they need to set fix version for each ticket.

XD


On Tue, Sep 18, 2018 at 17:17 Юли Волкова <xn...@gmail.com> wrote:

> Hi, Sid, thanks for some clarification about JIRA. At now, I walking
> through jira's task and ask Ash or other guys with admins right to close
> issues (for example:
>
> https://issues.apache.org/jira/browse/AIRFLOW-307?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> ),
> because PRs was successful merged 2 years ago. I would like to help in this
> scope: 1) If I have same moderators rights I can close tickets by myself
> 2) JIRA is a powerful tool on about integration - question only in do we
> have admin rights to add different integrations and triggers-hooks to JIRA.
> First of all, I propose to create hook what close task after PR was merged
> in master. Many task are open without any status changing with  already
> merged PRs.
>
> On Tue, Sep 18, 2018 at 11:58 AM Sid Anand <sa...@apache.org> wrote:
>
> > Hi Folks!
> > For some history, Airlfow started on GH issues. We also had a very
> popular
> > Google group. When we moved to Apache, we were told that Jira was the way
> > we needed to go for issue tracking because it resided on Apache
> > infrastructure. When we moved over, we had to drop 100+ GH issues on the
> > floor -- there was no way to transfer them to Jira and maintain the
> > original submitter/owner info since there was no mapping of users between
> > the 2 systems.
> >
> > Here's a pie chart of our existing issues by status:
> >
> >
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next
> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next>
> > <
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next
> >
> >
> > I'm attaching a screen shot as well.
> >
> > [image: Screenshot 2018-09-16 11.28.57.png]
> >
> > I think we all agree that there is better integration between GH PRs and
> > GH Issues than between GH PRs and Jira issues.
> >
> > There are some practical matters to consider:
> >
> >    - For the 1100-1200 unclosed/unresolved issues, how will we transfer
> >    them to GH or will we drop those on the floor? How would we map
> submitters
> >    between the 2 systems, and how would we transfer the
> content/comments,etc...
> >    - For the existing closed PRs (>3k), whose PRs reference JIRA, we'd
> >    need to keep JIRA around in read-only mode so we could reference the
> >    bug/feature details, but somehow disallow new JIRA creations, lest
> some
> >    people continue to use it to create new issues
> >    - I'm assuming the GH issue naming would not conflict with that of
> >    JIRA naming in commit message subjects and PRs. In other words,
> >    incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly
> >    conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the
> incubator name
> >    will be dropped, so there may be a naming conflict.
> >
> > In the end, these are 2 different tools. The issues you raise are mainly
> > around governance.
> >
> > If you folks would like to propose a new means to manage the JIRAs, can
> > you outline a solution on Wiki and drop a link into an email on this
> list?
> > We can then raise a vote.
> >
> > IMHO, our community would scale the best if more people picked up
> > responsibilities such as these. Grooming/Organizing JIRAs doesn't need to
> > be a responsibility owned by the maintainers. Anyone can take the lead on
> > discussions, etc...
> >
> > -s
> >
> > On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari <sumeet.manit@gmail.com
> >
> > wrote:
> >
> >> Strong +1 for moving to GitHub from Jira.
> >>
> >> On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman <
> waksman@gmail.com
> >> >
> >> wrote:
> >>
> >> > Are there Apache rules preventing us from switching to GitHub Issues?
> >> >
> >> > That seems like it might better fit much of Airflow's user base.
> >> >
> >> >
> >> > On Sun, Sep 16, 2018, 9:21 AM Jeff Payne <jp...@bombora.com> wrote:
> >> >
> >> > > I agree that Jira could be better utilized. I read the original
> >> > > conversation on the mailing list about how Jira should be used (or
> if
> >> it
> >> > > should be used at all) and I'm still unclear about why it was picked
> >> over
> >> > > just using github issues. It refers to a dashboard, which I've yet
> to
> >> > > investigate, but Jira is much more than just dashboards.
> >> > >
> >> > > If this project is going to use Jira, then:
> >> > >
> >> > > 1) It would be great to see moderation and labeling of the Jira
> >> issues by
> >> > > the main contributors to make it easier for people to break into
> >> > > contributing.
> >> > > 2) It would also be nice if the initial conversation of whether or
> >> not an
> >> > > issue warrants development at all happened on the Jira issue, or at
> >> least
> >> > > some acknowledgement by the main contributors.
> >> > > 3) Larger enhancements and efforts or vague suggestions still get
> >> > > discussed on the dev mailing list before a Jira is even opened, but
> >> after
> >> > > that, the discussion moves to the Jira, with a link back to the
> >> mailing
> >> > > list email for reference.
> >> > > 4) The discussion on the PR is only concerned with HOW the
> change/fix
> >> is
> >> > > implemented.
> >> > >
> >> > > Get Outlook for Android<https://aka.ms/ghei36>
> >> > >
> >> > > ________________________________
> >> > > From: James Meickle <jm...@quantopian.com.INVALID>
> >> > > Sent: Sunday, September 16, 2018 7:46:58 AM
> >> > > To: dev@airflow.apache.org
> >> > > Subject: Re: It's very hard to become a committer on the project
> >> > >
> >> > > Definitely agree with this. I'm not always opposed to JIRA for
> >> projects,
> >> > > but the way it's being used for this project makes it very hard to
> >> break
> >> > > into contributing. The split between GH and JIRA is also painful
> since
> >> > > there's no automatic integration of them.
> >> > >
> >> > > On Sun, Sep 16, 2018 at 9:29 AM airflowuser
> >> > > <ai...@protonmail.com.invalid> wrote:
> >> > >
> >> > > > Hello all,
> >> > > >
> >> > > > I'm struggling finding tickets to address and while discussing it
> on
> >> > chat
> >> > > > others reported they had the same problem when they began working
> on
> >> > the
> >> > > > project.
> >> > > >
> >> > > > The problem is due to:
> >> > > > 1. It's very hard to locate tickets on Jira. The categories are a
> >> mess,
> >> > > > versions are not enforced. each use can tag,label and set priority
> >> at
> >> > his
> >> > > > will. No one monitor or overwrite it
> >> > > > 2. It's impossible for a new committer to  find issues which can
> be
> >> > > > easy-fix and a "good first issue".
> >> > > >
> >> > > > My suggestions:
> >> > > > 1. Looking at the ticket system there are usually less than 10 new
> >> > > tickets
> >> > > > a day. It won't take too much time for someone with knowledge on
> the
> >> > > > project to properly tag  the ticket.
> >> > > >
> >> > > > 2. I think that most of you don't even check the Jira. Most of you
> >> > submit
> >> > > > PRs and 5 seconds before opening a ticket (just because you must).
> >> > There
> >> > > is
> >> > > > no doubt that the Jira is a "side" system which doesn't really
> >> perform
> >> > > it's
> >> > > > job.
> >> > > >
> >> > > > Take a look at this:
> >> > > >
> https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> >> > > > a member of the community asks for committers for input but no one
> >> > > > replies. I doubt this is because no one has input.. I am sure that
> >> if a
> >> > > PR
> >> > > > was submitted you had comments. It's simply because you don't see
> >> it.
> >> > > This
> >> > > > is why I think the current Jira does't function properly. I think
> >> that
> >> > > > Github can perform a better role. All of you as committers are
> >> already
> >> > > > there and it's always better to work with one system rather with
> >> two.
> >> > The
> >> > > > colors and labels of the GitHub as very easy to notice.
> >> > > >
> >> > > > Either way, what ever you decide something needs to be change.
> >> Either
> >> > > Jira
> >> > > > will be more informative or move to GitHub.
> >> > > >
> >> > > > Thank you all for your good work :)
> >> > >
> >> >
> >>
> >
>
> --
> _________
>
> С уважением, Юлия Волкова
> Тел. : +7 (911) 116-71-82
>

Re: It's very hard to become a committer on the project

[Юли Волкова <xn...@gmail.com>]

Hi, Sid, thanks for some clarification about JIRA. At now, I walking
through jira's task and ask Ash or other guys with admins right to close
issues (for example:
https://issues.apache.org/jira/browse/AIRFLOW-307?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel),
because PRs was successful merged 2 years ago. I would like to help in this
scope: 1) If I have same moderators rights I can close tickets by myself
2) JIRA is a powerful tool on about integration - question only in do we
have admin rights to add different integrations and triggers-hooks to JIRA.
First of all, I propose to create hook what close task after PR was merged
in master. Many task are open without any status changing with  already
merged PRs.

On Tue, Sep 18, 2018 at 11:58 AM Sid Anand <sa...@apache.org> wrote:

> Hi Folks!
> For some history, Airlfow started on GH issues. We also had a very popular
> Google group. When we moved to Apache, we were told that Jira was the way
> we needed to go for issue tracking because it resided on Apache
> infrastructure. When we moved over, we had to drop 100+ GH issues on the
> floor -- there was no way to transfer them to Jira and maintain the
> original submitter/owner info since there was no mapping of users between
> the 2 systems.
>
> Here's a pie chart of our existing issues by status:
>
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next
> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next>
>
> I'm attaching a screen shot as well.
>
> [image: Screenshot 2018-09-16 11.28.57.png]
>
> I think we all agree that there is better integration between GH PRs and
> GH Issues than between GH PRs and Jira issues.
>
> There are some practical matters to consider:
>
>    - For the 1100-1200 unclosed/unresolved issues, how will we transfer
>    them to GH or will we drop those on the floor? How would we map submitters
>    between the 2 systems, and how would we transfer the content/comments,etc...
>    - For the existing closed PRs (>3k), whose PRs reference JIRA, we'd
>    need to keep JIRA around in read-only mode so we could reference the
>    bug/feature details, but somehow disallow new JIRA creations, lest some
>    people continue to use it to create new issues
>    - I'm assuming the GH issue naming would not conflict with that of
>    JIRA naming in commit message subjects and PRs. In other words,
>    incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly
>    conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the incubator name
>    will be dropped, so there may be a naming conflict.
>
> In the end, these are 2 different tools. The issues you raise are mainly
> around governance.
>
> If you folks would like to propose a new means to manage the JIRAs, can
> you outline a solution on Wiki and drop a link into an email on this list?
> We can then raise a vote.
>
> IMHO, our community would scale the best if more people picked up
> responsibilities such as these. Grooming/Organizing JIRAs doesn't need to
> be a responsibility owned by the maintainers. Anyone can take the lead on
> discussions, etc...
>
> -s
>
> On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari <su...@gmail.com>
> wrote:
>
>> Strong +1 for moving to GitHub from Jira.
>>
>> On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman <waksman@gmail.com
>> >
>> wrote:
>>
>> > Are there Apache rules preventing us from switching to GitHub Issues?
>> >
>> > That seems like it might better fit much of Airflow's user base.
>> >
>> >
>> > On Sun, Sep 16, 2018, 9:21 AM Jeff Payne <jp...@bombora.com> wrote:
>> >
>> > > I agree that Jira could be better utilized. I read the original
>> > > conversation on the mailing list about how Jira should be used (or if
>> it
>> > > should be used at all) and I'm still unclear about why it was picked
>> over
>> > > just using github issues. It refers to a dashboard, which I've yet to
>> > > investigate, but Jira is much more than just dashboards.
>> > >
>> > > If this project is going to use Jira, then:
>> > >
>> > > 1) It would be great to see moderation and labeling of the Jira
>> issues by
>> > > the main contributors to make it easier for people to break into
>> > > contributing.
>> > > 2) It would also be nice if the initial conversation of whether or
>> not an
>> > > issue warrants development at all happened on the Jira issue, or at
>> least
>> > > some acknowledgement by the main contributors.
>> > > 3) Larger enhancements and efforts or vague suggestions still get
>> > > discussed on the dev mailing list before a Jira is even opened, but
>> after
>> > > that, the discussion moves to the Jira, with a link back to the
>> mailing
>> > > list email for reference.
>> > > 4) The discussion on the PR is only concerned with HOW the change/fix
>> is
>> > > implemented.
>> > >
>> > > Get Outlook for Android<https://aka.ms/ghei36>
>> > >
>> > > ________________________________
>> > > From: James Meickle <jm...@quantopian.com.INVALID>
>> > > Sent: Sunday, September 16, 2018 7:46:58 AM
>> > > To: dev@airflow.apache.org
>> > > Subject: Re: It's very hard to become a committer on the project
>> > >
>> > > Definitely agree with this. I'm not always opposed to JIRA for
>> projects,
>> > > but the way it's being used for this project makes it very hard to
>> break
>> > > into contributing. The split between GH and JIRA is also painful since
>> > > there's no automatic integration of them.
>> > >
>> > > On Sun, Sep 16, 2018 at 9:29 AM airflowuser
>> > > <ai...@protonmail.com.invalid> wrote:
>> > >
>> > > > Hello all,
>> > > >
>> > > > I'm struggling finding tickets to address and while discussing it on
>> > chat
>> > > > others reported they had the same problem when they began working on
>> > the
>> > > > project.
>> > > >
>> > > > The problem is due to:
>> > > > 1. It's very hard to locate tickets on Jira. The categories are a
>> mess,
>> > > > versions are not enforced. each use can tag,label and set priority
>> at
>> > his
>> > > > will. No one monitor or overwrite it
>> > > > 2. It's impossible for a new committer to  find issues which can be
>> > > > easy-fix and a "good first issue".
>> > > >
>> > > > My suggestions:
>> > > > 1. Looking at the ticket system there are usually less than 10 new
>> > > tickets
>> > > > a day. It won't take too much time for someone with knowledge on the
>> > > > project to properly tag  the ticket.
>> > > >
>> > > > 2. I think that most of you don't even check the Jira. Most of you
>> > submit
>> > > > PRs and 5 seconds before opening a ticket (just because you must).
>> > There
>> > > is
>> > > > no doubt that the Jira is a "side" system which doesn't really
>> perform
>> > > it's
>> > > > job.
>> > > >
>> > > > Take a look at this:
>> > > > https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
>> > > > a member of the community asks for committers for input but no one
>> > > > replies. I doubt this is because no one has input.. I am sure that
>> if a
>> > > PR
>> > > > was submitted you had comments. It's simply because you don't see
>> it.
>> > > This
>> > > > is why I think the current Jira does't function properly. I think
>> that
>> > > > Github can perform a better role. All of you as committers are
>> already
>> > > > there and it's always better to work with one system rather with
>> two.
>> > The
>> > > > colors and labels of the GitHub as very easy to notice.
>> > > >
>> > > > Either way, what ever you decide something needs to be change.
>> Either
>> > > Jira
>> > > > will be more informative or move to GitHub.
>> > > >
>> > > > Thank you all for your good work :)
>> > >
>> >
>>
>

-- 
_________

С уважением, Юлия Волкова
Тел. : +7 (911) 116-71-82

Re: It's very hard to become a committer on the project

[Sid Anand <sa...@apache.org>]

Hi Folks!
For some history, Airlfow started on GH issues. We also had a very popular
Google group. When we moved to Apache, we were told that Jira was the way
we needed to go for issue tracking because it resided on Apache
infrastructure. When we moved over, we had to drop 100+ GH issues on the
floor -- there was no way to transfer them to Jira and maintain the
original submitter/owner info since there was no mapping of users between
the 2 systems.

Here's a pie chart of our existing issues by status:
https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED|a85ff737799378265f90bab4f1456b5e2811a507|lin&Next=Next
<https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320023&statistictype=statuses&selectedProjectId=12320023&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7Ca85ff737799378265f90bab4f1456b5e2811a507%7Clin&Next=Next>

I'm attaching a screen shot as well.

[image: Screenshot 2018-09-16 11.28.57.png]

I think we all agree that there is better integration between GH PRs and GH
Issues than between GH PRs and Jira issues.

There are some practical matters to consider:

   - For the 1100-1200 unclosed/unresolved issues, how will we transfer
   them to GH or will we drop those on the floor? How would we map submitters
   between the 2 systems, and how would we transfer the content/comments,etc...
   - For the existing closed PRs (>3k), whose PRs reference JIRA, we'd need
   to keep JIRA around in read-only mode so we could reference the bug/feature
   details, but somehow disallow new JIRA creations, lest some people continue
   to use it to create new issues
   - I'm assuming the GH issue naming would not conflict with that of JIRA
   naming in commit message subjects and PRs. In other words,
   incubator-airlow-1 vs AIRFLOW-1 or airflow-1 vs AIRFLOW-1 or possibly
   conflict at AIRFLOW-1? Once we graduate, I'm pretty sure the incubator name
   will be dropped, so there may be a naming conflict.

In the end, these are 2 different tools. The issues you raise are mainly
around governance.

If you folks would like to propose a new means to manage the JIRAs, can you
outline a solution on Wiki and drop a link into an email on this list? We
can then raise a vote.

IMHO, our community would scale the best if more people picked up
responsibilities such as these. Grooming/Organizing JIRAs doesn't need to
be a responsibility owned by the maintainers. Anyone can take the lead on
discussions, etc...

-s

On Mon, Sep 17, 2018 at 2:09 AM Sumit Maheshwari <su...@gmail.com>
wrote:

> Strong +1 for moving to GitHub from Jira.
>
> On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman <wa...@gmail.com>
> wrote:
>
> > Are there Apache rules preventing us from switching to GitHub Issues?
> >
> > That seems like it might better fit much of Airflow's user base.
> >
> >
> > On Sun, Sep 16, 2018, 9:21 AM Jeff Payne <jp...@bombora.com> wrote:
> >
> > > I agree that Jira could be better utilized. I read the original
> > > conversation on the mailing list about how Jira should be used (or if
> it
> > > should be used at all) and I'm still unclear about why it was picked
> over
> > > just using github issues. It refers to a dashboard, which I've yet to
> > > investigate, but Jira is much more than just dashboards.
> > >
> > > If this project is going to use Jira, then:
> > >
> > > 1) It would be great to see moderation and labeling of the Jira issues
> by
> > > the main contributors to make it easier for people to break into
> > > contributing.
> > > 2) It would also be nice if the initial conversation of whether or not
> an
> > > issue warrants development at all happened on the Jira issue, or at
> least
> > > some acknowledgement by the main contributors.
> > > 3) Larger enhancements and efforts or vague suggestions still get
> > > discussed on the dev mailing list before a Jira is even opened, but
> after
> > > that, the discussion moves to the Jira, with a link back to the mailing
> > > list email for reference.
> > > 4) The discussion on the PR is only concerned with HOW the change/fix
> is
> > > implemented.
> > >
> > > Get Outlook for Android<https://aka.ms/ghei36>
> > >
> > > ________________________________
> > > From: James Meickle <jm...@quantopian.com.INVALID>
> > > Sent: Sunday, September 16, 2018 7:46:58 AM
> > > To: dev@airflow.apache.org
> > > Subject: Re: It's very hard to become a committer on the project
> > >
> > > Definitely agree with this. I'm not always opposed to JIRA for
> projects,
> > > but the way it's being used for this project makes it very hard to
> break
> > > into contributing. The split between GH and JIRA is also painful since
> > > there's no automatic integration of them.
> > >
> > > On Sun, Sep 16, 2018 at 9:29 AM airflowuser
> > > <ai...@protonmail.com.invalid> wrote:
> > >
> > > > Hello all,
> > > >
> > > > I'm struggling finding tickets to address and while discussing it on
> > chat
> > > > others reported they had the same problem when they began working on
> > the
> > > > project.
> > > >
> > > > The problem is due to:
> > > > 1. It's very hard to locate tickets on Jira. The categories are a
> mess,
> > > > versions are not enforced. each use can tag,label and set priority at
> > his
> > > > will. No one monitor or overwrite it
> > > > 2. It's impossible for a new committer to  find issues which can be
> > > > easy-fix and a "good first issue".
> > > >
> > > > My suggestions:
> > > > 1. Looking at the ticket system there are usually less than 10 new
> > > tickets
> > > > a day. It won't take too much time for someone with knowledge on the
> > > > project to properly tag  the ticket.
> > > >
> > > > 2. I think that most of you don't even check the Jira. Most of you
> > submit
> > > > PRs and 5 seconds before opening a ticket (just because you must).
> > There
> > > is
> > > > no doubt that the Jira is a "side" system which doesn't really
> perform
> > > it's
> > > > job.
> > > >
> > > > Take a look at this:
> > > > https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> > > > a member of the community asks for committers for input but no one
> > > > replies. I doubt this is because no one has input.. I am sure that
> if a
> > > PR
> > > > was submitted you had comments. It's simply because you don't see it.
> > > This
> > > > is why I think the current Jira does't function properly. I think
> that
> > > > Github can perform a better role. All of you as committers are
> already
> > > > there and it's always better to work with one system rather with two.
> > The
> > > > colors and labels of the GitHub as very easy to notice.
> > > >
> > > > Either way, what ever you decide something needs to be change. Either
> > > Jira
> > > > will be more informative or move to GitHub.
> > > >
> > > > Thank you all for your good work :)
> > >
> >
>

Re: It's very hard to become a committer on the project

[Sumit Maheshwari <su...@gmail.com>]

Strong +1 for moving to GitHub from Jira.

On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman <wa...@gmail.com>
wrote:

> Are there Apache rules preventing us from switching to GitHub Issues?
>
> That seems like it might better fit much of Airflow's user base.
>
>
> On Sun, Sep 16, 2018, 9:21 AM Jeff Payne <jp...@bombora.com> wrote:
>
> > I agree that Jira could be better utilized. I read the original
> > conversation on the mailing list about how Jira should be used (or if it
> > should be used at all) and I'm still unclear about why it was picked over
> > just using github issues. It refers to a dashboard, which I've yet to
> > investigate, but Jira is much more than just dashboards.
> >
> > If this project is going to use Jira, then:
> >
> > 1) It would be great to see moderation and labeling of the Jira issues by
> > the main contributors to make it easier for people to break into
> > contributing.
> > 2) It would also be nice if the initial conversation of whether or not an
> > issue warrants development at all happened on the Jira issue, or at least
> > some acknowledgement by the main contributors.
> > 3) Larger enhancements and efforts or vague suggestions still get
> > discussed on the dev mailing list before a Jira is even opened, but after
> > that, the discussion moves to the Jira, with a link back to the mailing
> > list email for reference.
> > 4) The discussion on the PR is only concerned with HOW the change/fix is
> > implemented.
> >
> > Get Outlook for Android<https://aka.ms/ghei36>
> >
> > ________________________________
> > From: James Meickle <jm...@quantopian.com.INVALID>
> > Sent: Sunday, September 16, 2018 7:46:58 AM
> > To: dev@airflow.apache.org
> > Subject: Re: It's very hard to become a committer on the project
> >
> > Definitely agree with this. I'm not always opposed to JIRA for projects,
> > but the way it's being used for this project makes it very hard to break
> > into contributing. The split between GH and JIRA is also painful since
> > there's no automatic integration of them.
> >
> > On Sun, Sep 16, 2018 at 9:29 AM airflowuser
> > <ai...@protonmail.com.invalid> wrote:
> >
> > > Hello all,
> > >
> > > I'm struggling finding tickets to address and while discussing it on
> chat
> > > others reported they had the same problem when they began working on
> the
> > > project.
> > >
> > > The problem is due to:
> > > 1. It's very hard to locate tickets on Jira. The categories are a mess,
> > > versions are not enforced. each use can tag,label and set priority at
> his
> > > will. No one monitor or overwrite it
> > > 2. It's impossible for a new committer to  find issues which can be
> > > easy-fix and a "good first issue".
> > >
> > > My suggestions:
> > > 1. Looking at the ticket system there are usually less than 10 new
> > tickets
> > > a day. It won't take too much time for someone with knowledge on the
> > > project to properly tag  the ticket.
> > >
> > > 2. I think that most of you don't even check the Jira. Most of you
> submit
> > > PRs and 5 seconds before opening a ticket (just because you must).
> There
> > is
> > > no doubt that the Jira is a "side" system which doesn't really perform
> > it's
> > > job.
> > >
> > > Take a look at this:
> > > https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> > > a member of the community asks for committers for input but no one
> > > replies. I doubt this is because no one has input.. I am sure that if a
> > PR
> > > was submitted you had comments. It's simply because you don't see it.
> > This
> > > is why I think the current Jira does't function properly. I think that
> > > Github can perform a better role. All of you as committers are already
> > > there and it's always better to work with one system rather with two.
> The
> > > colors and labels of the GitHub as very easy to notice.
> > >
> > > Either way, what ever you decide something needs to be change. Either
> > Jira
> > > will be more informative or move to GitHub.
> > >
> > > Thank you all for your good work :)
> >
>

Re: It's very hard to become a committer on the project

[George Leslie-Waksman <wa...@gmail.com>]

Are there Apache rules preventing us from switching to GitHub Issues?

That seems like it might better fit much of Airflow's user base.


On Sun, Sep 16, 2018, 9:21 AM Jeff Payne <jp...@bombora.com> wrote:

> I agree that Jira could be better utilized. I read the original
> conversation on the mailing list about how Jira should be used (or if it
> should be used at all) and I'm still unclear about why it was picked over
> just using github issues. It refers to a dashboard, which I've yet to
> investigate, but Jira is much more than just dashboards.
>
> If this project is going to use Jira, then:
>
> 1) It would be great to see moderation and labeling of the Jira issues by
> the main contributors to make it easier for people to break into
> contributing.
> 2) It would also be nice if the initial conversation of whether or not an
> issue warrants development at all happened on the Jira issue, or at least
> some acknowledgement by the main contributors.
> 3) Larger enhancements and efforts or vague suggestions still get
> discussed on the dev mailing list before a Jira is even opened, but after
> that, the discussion moves to the Jira, with a link back to the mailing
> list email for reference.
> 4) The discussion on the PR is only concerned with HOW the change/fix is
> implemented.
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> ________________________________
> From: James Meickle <jm...@quantopian.com.INVALID>
> Sent: Sunday, September 16, 2018 7:46:58 AM
> To: dev@airflow.apache.org
> Subject: Re: It's very hard to become a committer on the project
>
> Definitely agree with this. I'm not always opposed to JIRA for projects,
> but the way it's being used for this project makes it very hard to break
> into contributing. The split between GH and JIRA is also painful since
> there's no automatic integration of them.
>
> On Sun, Sep 16, 2018 at 9:29 AM airflowuser
> <ai...@protonmail.com.invalid> wrote:
>
> > Hello all,
> >
> > I'm struggling finding tickets to address and while discussing it on chat
> > others reported they had the same problem when they began working on the
> > project.
> >
> > The problem is due to:
> > 1. It's very hard to locate tickets on Jira. The categories are a mess,
> > versions are not enforced. each use can tag,label and set priority at his
> > will. No one monitor or overwrite it
> > 2. It's impossible for a new committer to  find issues which can be
> > easy-fix and a "good first issue".
> >
> > My suggestions:
> > 1. Looking at the ticket system there are usually less than 10 new
> tickets
> > a day. It won't take too much time for someone with knowledge on the
> > project to properly tag  the ticket.
> >
> > 2. I think that most of you don't even check the Jira. Most of you submit
> > PRs and 5 seconds before opening a ticket (just because you must). There
> is
> > no doubt that the Jira is a "side" system which doesn't really perform
> it's
> > job.
> >
> > Take a look at this:
> > https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> > a member of the community asks for committers for input but no one
> > replies. I doubt this is because no one has input.. I am sure that if a
> PR
> > was submitted you had comments. It's simply because you don't see it.
> This
> > is why I think the current Jira does't function properly. I think that
> > Github can perform a better role. All of you as committers are already
> > there and it's always better to work with one system rather with two. The
> > colors and labels of the GitHub as very easy to notice.
> >
> > Either way, what ever you decide something needs to be change. Either
> Jira
> > will be more informative or move to GitHub.
> >
> > Thank you all for your good work :)
>

Re: It's very hard to become a committer on the project

[Jeff Payne <jp...@bombora.com>]

I agree that Jira could be better utilized. I read the original conversation on the mailing list about how Jira should be used (or if it should be used at all) and I'm still unclear about why it was picked over just using github issues. It refers to a dashboard, which I've yet to investigate, but Jira is much more than just dashboards.

If this project is going to use Jira, then:

1) It would be great to see moderation and labeling of the Jira issues by the main contributors to make it easier for people to break into contributing.
2) It would also be nice if the initial conversation of whether or not an issue warrants development at all happened on the Jira issue, or at least some acknowledgement by the main contributors.
3) Larger enhancements and efforts or vague suggestions still get discussed on the dev mailing list before a Jira is even opened, but after that, the discussion moves to the Jira, with a link back to the mailing list email for reference.
4) The discussion on the PR is only concerned with HOW the change/fix is implemented.

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: James Meickle <jm...@quantopian.com.INVALID>
Sent: Sunday, September 16, 2018 7:46:58 AM
To: dev@airflow.apache.org
Subject: Re: It's very hard to become a committer on the project

Definitely agree with this. I'm not always opposed to JIRA for projects,
but the way it's being used for this project makes it very hard to break
into contributing. The split between GH and JIRA is also painful since
there's no automatic integration of them.

On Sun, Sep 16, 2018 at 9:29 AM airflowuser
<ai...@protonmail.com.invalid> wrote:

> Hello all,
>
> I'm struggling finding tickets to address and while discussing it on chat
> others reported they had the same problem when they began working on the
> project.
>
> The problem is due to:
> 1. It's very hard to locate tickets on Jira. The categories are a mess,
> versions are not enforced. each use can tag,label and set priority at his
> will. No one monitor or overwrite it
> 2. It's impossible for a new committer to  find issues which can be
> easy-fix and a "good first issue".
>
> My suggestions:
> 1. Looking at the ticket system there are usually less than 10 new tickets
> a day. It won't take too much time for someone with knowledge on the
> project to properly tag  the ticket.
>
> 2. I think that most of you don't even check the Jira. Most of you submit
> PRs and 5 seconds before opening a ticket (just because you must). There is
> no doubt that the Jira is a "side" system which doesn't really perform it's
> job.
>
> Take a look at this:
> https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> a member of the community asks for committers for input but no one
> replies. I doubt this is because no one has input.. I am sure that if a PR
> was submitted you had comments. It's simply because you don't see it. This
> is why I think the current Jira does't function properly. I think that
> Github can perform a better role. All of you as committers are already
> there and it's always better to work with one system rather with two. The
> colors and labels of the GitHub as very easy to notice.
>
> Either way, what ever you decide something needs to be change. Either Jira
> will be more informative or move to GitHub.
>
> Thank you all for your good work :)

Re: It's very hard to become a committer on the project

[James Meickle <jm...@quantopian.com.INVALID>]

Definitely agree with this. I'm not always opposed to JIRA for projects,
but the way it's being used for this project makes it very hard to break
into contributing. The split between GH and JIRA is also painful since
there's no automatic integration of them.

On Sun, Sep 16, 2018 at 9:29 AM airflowuser
<ai...@protonmail.com.invalid> wrote:

> Hello all,
>
> I'm struggling finding tickets to address and while discussing it on chat
> others reported they had the same problem when they began working on the
> project.
>
> The problem is due to:
> 1. It's very hard to locate tickets on Jira. The categories are a mess,
> versions are not enforced. each use can tag,label and set priority at his
> will. No one monitor or overwrite it
> 2. It's impossible for a new committer to  find issues which can be
> easy-fix and a "good first issue".
>
> My suggestions:
> 1. Looking at the ticket system there are usually less than 10 new tickets
> a day. It won't take too much time for someone with knowledge on the
> project to properly tag  the ticket.
>
> 2. I think that most of you don't even check the Jira. Most of you submit
> PRs and 5 seconds before opening a ticket (just because you must). There is
> no doubt that the Jira is a "side" system which doesn't really perform it's
> job.
>
> Take a look at this:
> https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-2999
> a member of the community asks for committers for input but no one
> replies. I doubt this is because no one has input.. I am sure that if a PR
> was submitted you had comments. It's simply because you don't see it. This
> is why I think the current Jira does't function properly. I think that
> Github can perform a better role. All of you as committers are already
> there and it's always better to work with one system rather with two. The
> colors and labels of the GitHub as very easy to notice.
>
> Either way, what ever you decide something needs to be change. Either Jira
> will be more informative or move to GitHub.
>
> Thank you all for your good work :)