You could create the issue if you are so inclined. The "author" metadata
of the issue might not be quite right but that's quite minor... and could
be ameliorated with mentioning the original author in the description.
Multiple sources of truth is troubling to me and of course complicates
I have a question for a PR like this -
https://github.com/apache/lucene-solr/pull/908/
This user is a first time contributor and now we have to ask the user to
create a tracking Jira for a PR before we can commit this - Is there a
process we can take that can make this smoother for the user?
PR
My 2 sents
I like the workflow of PR and code review in github.
But, I still prefer JIRA and I don't want it to replace it with github issues
On Tue, Sep 17, 2019 at 5:57 AM Jan Høydahl wrote:
>
> Is there any reason at all that we need to hold on to JIRA? ASF allows us to
> move all issue
: ASF has us legally covered, and from the foundation's side, GitHub
: issues is equal to JIRA issues and GitHub PRs are equal to patches in
: JIRA.
: > People that wish to continue using their Apache committer accounts to
: commit code may continue doing so on gitbox.apache.org with their
Yes I've used that GitHub issues interface many many times and IMHO and it
sucks. I put up with it because it's free and I'm not rich. I have a small
herd of stuff I have tossed up in git hub over the years across 2 accounts,
and I maintain JesterJ in GitHub... I'd move it to Jira in a heart beat
It seems like there are two discussions happening here
1> moving code _development_ to GitHub
2> moving JIRA to GitHub
I want to talk about <2>
Gus:
Have you looked at "issues" in GitHub? See:
https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc
On a _very_
We as a project won't need to worry about "system of record" or what MS will do
in the future. Really.
I encourage all to read INFRA's post about the ASF-GitHub agreement here
https://blogs.apache.org/infra/entry/apache-and-github-a-friendly
In the last paragraph it states:
> For many projects,
I wrote quickly and didn't expound much, let me clarify that my comments
are in reference to having bug tracking in GitHub. Using the mirror doesn't
bother me since the system of record is apache gitbox (the GitHub mirror is
WAY better UI than gitbox). Having the record of what bugs were resolved
Also, just FYI, I say that as someone that kind of prefers patches and JIRA
for 90% of what I do. I’ve been doing this same shit for like half my life,
I’m not looking for fancy new tools for the hell of it either. I like
patches. It’s just going to happen. And I see a huge pool of free resources
I think that is a little over the top.
As it is the majority of dev and pr's and action is moving to GitHub,
whether anyone is from Syria or not.
If we decided, like most other communities on Gods green earth, to tell our
community we are going GitHub first it and expect committers to not avoid
Ok, I buy that reason for leaving the ASF controlled mechanism.
On Tue, Sep 17, 2019 at 2:16 PM Chris Hostetter
wrote:
>
> : Is there any reason at all that we need to hold on to JIRA? ASF allows
> : us to move all issue handling over to GH, I'd like us to consider such a
> : move.
>
> In my
"means pressuring people into accepting the github TOS"
That's a really good point. Hadn't thought of that and it's definitely not
ok to put github in control (or make them able to force a sudden burden of
work when we don't like what they did). Apache should determine it's own
destiny, and for
: Is there any reason at all that we need to hold on to JIRA? ASF allows
: us to move all issue handling over to GH, I'd like us to consider such a
: move.
In my opinion, migrating from JIRA to Github "issues" would be a terrible
idea.
I have no objections to the goal of "encouraging" and
I think standardizing the approach to contributing would be a great thing.
It might mean not accommodating everyone's preference, but then it would
mean that the people who want to review are all on the same page. Else
people who prefer git will rarely look at patches, and the other way around.
I think I may prefer JIRA to GitHub Issues. I'm not sure.
Anyway, it's worth wondering if we can just move JIRA to GitHub. GitHub is
now a first class mirror for Apache that we can commit to, but they still
keep a primary copy of our code at Apache. Perhaps that is only a code
concern now though.
Well put Jason. I think we didn't discuss it in any further detail than
what you said right here -- basically cater to GitHub PRs and either
discourage or undocument "patch file" based contributions. That's it in a
sentence. We all nodded our head to that, albeit some of us like me
confess to
I missed the part of the meeting/lunch when our use of Github came up.
Can anyone that was present summarize the discussion in a little more
detail?
re: issues on github. There are challenges like avoiding
fragmentation and keeping multiple issue sources up to date, but those
are problems that
Ah.. The mythical committer just sitting around waiting to be “interested in
the issue” that you have created! Having said that, I think thats a separate
challenge!
> On Sep 17, 2019, at 12:38 AM, David Smiley wrote:
>
> +1 to all that Gus said. On a fresh project then indeed perhaps we
+1 to all that Gus said. On a fresh project then indeed perhaps we would
use GitHub issues but it's not nearly so compelling at this point with so
much rich history in JIRA, not to mention those issues being referenced in
commit messages.
Is the point to lower barriers for contributors that are
FWIW, One thing that needs to be figured out is how github would
accommodate security issues (or how the process for those issues would
change). Does github have the ability to assign roles and visibility
(could be I haven't really worked with organizations on GitHub, all my
clients have been on
Is there any reason at all that we need to hold on to JIRA? ASF allows us to
move all issue handling over to GH, I'd like us to consider such a move.
Until then, I made a script that "diffs" GH and JIRA and outputs a report, see
> On 16 Sep 2019, at 19:38, Yonik Seeley wrote:
>
> > - PR is opened - should automatically create a jira if it doesn’t exist yet
>
> What were the reasons behind this? Shouldn't a JIRA just be optional if we
> started with a PR?
That’s why we need to discuss this :)
I remember that at
> - PR is opened - should automatically create a jira if it doesn’t exist
yet
What were the reasons behind this? Shouldn't a JIRA just be optional if we
started with a PR?
-Yonik
> On 16 Sep 2019, at 17:55, Ishan Chattopadhyaya
> wrote:
>
>> Committers attending (at least some part of) the meeting, in no particular
>> order: Erik Hatcher, Anshum Gupta, David Smiley, Gus Heck, Noble Paul, Varun
>> Thacker, Ishan Chattopadhyaya, Tomás Löbbe, and yours truly.
>
>
> Committers attending (at least some part of) the meeting, in no particular
> order: Erik Hatcher, Anshum Gupta, David Smiley, Gus Heck, Noble Paul, Varun
> Thacker, Ishan Chattopadhyaya, Tomás Löbbe, and yours truly.
Also, Tim Allison, Joel Bernstein, Jason Gerlowski. (Did we miss out
someone
25 matches
Mail list logo
