On Thu, Aug 22, 2019 at 11:33 AM Ryan Blue <rb...@netflix.com.invalid> wrote: > > A big concern I have about using JIRA is that I think it is a barrier to > participation. If you want to open an issue, you need to have a JIRA account > and remember the credentials; in contrast most of our developer audience is > perpetually signed into Github. Once you've logged in to JIRA, then there are > several required fields with inconsistent use across projects. One of the > main reasons I see for using Github is that it makes it easier to participate. >
I guess it's a question of what kind of people do you want involved in your project. I've found that the ASF JIRA barrier is pretty effective at filtering out unserious contributors. GitHub has a serious "peanut gallery" problem, but you'll get to find out whether this affects Iceberg or not =) > I'd like to try to continue with Github issues. Some of JIRA's strengths have > analogs in Github that I think are good alternatives. We've been using > milestones to stay organized, for example. > > We should open an INFRA issue to fix the problem that non-committers can't > label issues or request reviews. I think that's an oversight in the > integration. > This is a fundamental issue with GitHub -- issue editing and repo push permission is coupled. So I don't think this can be fixed. > On Mon, Aug 19, 2019 at 11:04 AM Edgar Rodriguez > <edgar.rodrig...@airbnb.com.invalid> wrote: >> >> I don't have a strong preference. I've worked with both of them but I >> appreciate the simplicity of Github and the fast search. I feel like JIRA >> can become very complex quickly and also requires a lot of labels, versions, >> etc to track it so in that sense for Github it may also require some of this >> but probably a bit simpler; there's less fields to fill out in Github for an >> issue. >> >> I believe in both cases there's a need for curation of the issues, so I'd >> favor simplicity. >> >> Anyways, my two cents. >> Thanks. >> >> Cheers, >> Edgar >> >> On Sun, Aug 18, 2019 at 7:43 PM Saisai Shao <sai.sai.s...@gmail.com> wrote: >>>> >>>> The issue linking, Fix Version, and assignee features of JIRA are also >>>> helpful communication and organization tools. >>> >>> >>> Yes, I think so. Github issues seems a little bit simple, there're not so >>> many status to track the issue unless we create bunch of labels. >>> >>> Wes McKinney <wesmck...@gmail.com> 于2019年8月17日周六 上午2:37写道： >>>> >>>> One significant issue with GitHub issues for ASF projects is that >>>> non-committers cannot edit issue or PR metadata (labels, requesting >>>> reviews, etc). The lack of formalism around Resolved and Closed states can >>>> place an extra communication burden to explain why an issue is closed. >>>> Sometimes projects use GitHub labels like 'wontfix'. The issue linking, >>>> Fix Version, and assignee features of JIRA are also helpful communication >>>> and organization tools. >>>> >>>> In other projects I have found JIRA easier to keep a larger number of >>>> people, release milestones, and issues organized. I can't imagine changing >>>> to GitHub issues in Apache Arrow, for example >>>> >>>> On Fri, Aug 16, 2019, 1:19 PM Ryan Blue <rb...@netflix.com.invalid> wrote: >>>>> >>>>> I prefer to use github instead of JIRA because it is simpler and has >>>>> better search (in my opinion). I'm just one vote, though, so if most >>>>> people prefer to move to JIRA I'm open to it. >>>>> >>>>> What do you think is missing compared to JIRA? >>>>> >>>>> On Fri, Aug 16, 2019 at 3:09 AM Saisai Shao <sai.sai.s...@gmail.com> >>>>> wrote: >>>>>> >>>>>> Hi Team, >>>>>> >>>>>> Seems Iceberg project uses Github issues instead of JIRA. IMHO JIRA is >>>>>> more powerful and easy to manage, most of the Apache projects use JIRA >>>>>> to track everything, any plan to move to JIRA or we stick on using >>>>>> Github issues? >>>>>> >>>>>> Thanks >>>>>> Saisai >>>>> >>>>> >>>>> >>>>> -- >>>>> Ryan Blue >>>>> Software Engineer >>>>> Netflix >> >> >> >> -- >> Edgar Rodriguez > > > > -- > Ryan Blue > Software Engineer > Netflix
