Strong +1 for moving to GitHub from Jira. On Mon, Sep 17, 2018 at 12:35 PM George Leslie-Waksman <waks...@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 <jpa...@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 <jmeic...@quantopian.com.INVALID> > > Sent: Sunday, September 16, 2018 7:46:58 AM > > To: d...@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 > > <airflowu...@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 :) > > >
