On Thu, Aug 22, 2019 at 11:33 AM Ryan Blue 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
> perpetual
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
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 b
>
> 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 于2019年8月17日周六 上午2:
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
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 wrote:
> Hi Team,
>
