[jira] [Commented] (PYLUCENE-63) can not install pylucene on linux with proxy

[ https://issues.apache.org/jira/browse/PYLUCENE-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532651#comment-17532651 ] lisa.shi commented on PYLUCENE-63: -- thank you for your help. your answer is very helpful > can not

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

Hi Yuting, thanks for your feedback. For your information, we have a general issue to improve our contribution workflow: LUCENE-10543 , and this is actually a sub-task of it. You and anyone can contribute to it by leaving comments, creating

Re: automaton incremental updates

Hi I'm not sure if I understood your question correctly, but a normal way lucene update an existing automaton is to intersect or union it with another one (the new one with the updated data), those operations' code are collected here:

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

Hi Tomoko, Thanks for raising this discussion! As a new member of the Lucene community, I'm also confused by the input components when creating a Jira issue. I struggled with previewing my text and had to edit it after creating a Jira issue or a comment, and I just found that each re-edit would

Re: automaton incremental updates

Hi, I can't answer your question but I remember this issue - https://issues.apache.org/jira/browse/LUCENE-10010 Tomoko 2022年5月6日(金) 2:47 Petar Dambovaliev : > Hello, > > I was looking for a way to update Non/Deterministic finite automatons with > new data. > Some people pointed out that

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

I'm not going to thoroughly discuss the migration path from Jira to GitHub here, but generally, the rough image in my mind is the same as Jan described - "Milestone" for version tracking, and "labels" for other purposes (issue types, component types, etc.). As for the proposal of in-house

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

I agree with that. What annoys me is that I have to open a fake issue in Jira. I think we should allow people to open GitHub PR or issues. It gets reported also to mailing list. If a Lucene committer does not want to use GitHub, heshe can just download the PR as patch file and apply. Same for

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

Thanks for starting this thread, Tomoko! Being fairly new to the community, I can recall some early teething issues and offer a newcomer's perspective. Jira took a while to get familiar with. I had used GitHub issues before, for Elasticsearch and Opensearch. Having used Jira now, makes me like

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

> Is the original Jira -> GitHub move just a change of defaults or are we, > once moved to GitHub, not letting people use Jira at all anymore ? Nothing has been decided - it's all open for debate. I just want to re-state the idea (at least as I heard it) behind this proposed move is to make

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

On Thu, 5 May 2022, Jan Høydahl wrote: ASF has officially blessed use of github issues as alternative to Jira. They are not going to setup a private GitLab or tool X. While GitLab is nice, I don't think the main intention with the proposal was to inroduce yet another platform where

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

ASF has officially blessed use of github issues as alternative to Jira. They are not going to setup a private GitLab or tool X. While GitLab is nice, I don't think the main intention with the proposal was to inroduce yet another platform where contributors need to register an account and learn

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

Is anyone familiar with using GitHub (or maybe GitLab I suppose) for tracking metadata about the issue -- something JIRA excels at? For example the version of our project that a given PR is released in -- aka the JIRA "Fix Version"? ~ David Smiley Apache Lucene/Solr Search Developer

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

> On May 5, 2022, at 08:49, Tomoko Uchida wrote: > >  > It's really interesting to me to hear how others feel comfortable (or > discomfortable) with the tools! > > I myself am not an expert of either JIra or GitHub, and actually have no > feelings on which tool is better. > The only

automaton incremental updates

Hello, I was looking for a way to update Non/Deterministic finite automatons with new data. Some people pointed out that "Lucene is doing that. You should ask them how they do it.". So here i am. I would appreciate it if someone can point me in the right direction so i can see how you are doing

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

OK, I think it's a healthy discussion everyone can make an assertion (agreement or disagreement, or whatever else). I'd ask all just one thing - if you criticize or strongly oppose any tools, please present references that support your opinion. Thank you, Tomoko 2022年5月6日(金) 1:17 Andi Vajda :

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

> On May 5, 2022, at 08:41, Ishan Chattopadhyaya > wrote: > >  > (Repeating in public what I mentioned in private) > > > I'm generally opposed to this idea because GitHub has been known to take > political decisions to cut off access to developers just because of their >

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

It's really interesting to me to hear how others feel comfortable (or discomfortable) with the tools! I myself am not an expert of either JIra or GitHub, and actually have no feelings on which tool is better. The only motivation for my proposal was, "consolidate the conversation platform and

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

(Repeating in public what I mentioned in private) I'm generally opposed to this idea because GitHub has been known to take political decisions to cut off access to developers just because of their nationality/region etc. As a community, we should stay politically neutral and not rely on GitHub

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

Given how JIRA has become a monster of a product with different markup syntax for each version, and bugs everywhere (does not even work on mobile), I'm no longer the JIRA fan I once was. In Solr we already use github issues for the Solr-Operator sub project

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

Ah sorry, if I unintentionally went off the track. Thanks for your comments - I'll keep this thread for a sufficient period of time and read all messages. It's an open discussion and any comments from all developers (PMC members, committers, contributors) are welcomed and respected. Tomoko

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

On Thu, May 5, 2022 at 8:14 AM Tomoko Uchida wrote: > > Just for a supplement - I did not know that either, but I think it's not only > abouit Jira. > I've seen several times developers in China sometimes struggle also with > connecting to GitHub - may be due to the so-called Great Firewall. >

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

> The original motivation for the > INFRA issue linked above is interesting to me. I didn't know > contributors from China struggled to access Apache JIRA. Just for a supplement - I did not know that either, but I think it's not only abouit Jira. I've seen several times developers in China

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

On Thu, May 5, 2022 at 7:49 AM Michael Sokolov wrote: > 5. I find the Github commenting UI confusing -- what is the difference > between conversation and review comments? How can I reply to a > comment? What if I want to batch up a bunch of replies and send one > email with all of them? Maybe

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

I'd like to see some discussion of pros/cons. Personally I don't have a lot of experience working with github's issue system, while I have grown comfortable with JIRA over the years, in spite of its warts. Here are a few things I like and *don't* like about both systems (mostly JIRA), but I don't

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

On Wed, May 4, 2022 at 10:24 PM Tomoko Uchida wrote: > > According to the INFRA issue for the RocketMQ project (Michael McCandless > gave the pointer in a comment on the issue; thanks!), a PMC agreement or Vote > result is needed for the decision. >