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

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 : > On 9/20/18 10:02 PM, Driesprong, Fokko wrote: > > us still have a full time job on the side :) Tomorrow I'll

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

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:

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

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

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

Some history. Recently we've moved the to Gitbox 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

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

>> 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

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

> 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

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

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

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

> On 18 Sep 2018, at 13:07, Ash Berlin-Taylor 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 >

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

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 wrote: > Before we could merge

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

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

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

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 Юли Волкова wrote: > Hi, Sid, thanks for some

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

I'll gladly give being triage nurse a shot. Get Outlook for Android 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

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

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

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

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

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

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

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 wrote: > I agree that Jira could be better utilized. I read the original > conversation on the mailing list about how

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

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,

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

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

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