Fixed
Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
[Empty comment from Monorail migration]
ma...@gmail.com <ma...@gmail.com> #3
[Empty comment from Monorail migration]
lu...@gmail.com <lu...@gmail.com> #4
[Empty comment from Monorail migration]
lu...@gmail.com <lu...@gmail.com> #5
As far as I remember, one of the reasons we documented ES as experimental was because none of us maintainers were/are using it in production.
I've heard that there are some users running ES in production now though. Would it be good to do a survey of the community to find out which versions (both of ES and of Gerrit) are actually being used in the wild? Is this something that the community managers can drive?
[Monorail components: Community]
I've heard that there are some users running ES in production now though. Would it be good to do a survey of the community to find out which versions (both of ES and of Gerrit) are actually being used in the wild? Is this something that the community managers can drive?
[Monorail components: Community]
da...@gmail.com <da...@gmail.com> #6
I think so yes; thanks. Now part of our near backlog.
There could be other Gerrit components to poll about; cf.https://crbug.com/gerrit/12211 .
There could be other Gerrit components to poll about; cf.
ek...@google.com <ek...@google.com> #7
Make a dedicated short survey for this to get this resolved quickly.
lu...@gmail.com <lu...@gmail.com> #8
[Empty comment from Monorail migration]
ma...@gmail.com <ma...@gmail.com> #9
Form proposal sent for review to some of us here.
Let me know if you cannot see it but would like to.
Once done reviewing, I can send the form/survey to the community mailing list.
-How much time to allow for collecting responses?
I'd propose by end of May, to give organizations a chance at figuring that out for themselves.
Let me know if you cannot see it but would like to.
Once done reviewing, I can send the form/survey to the community mailing list.
-How much time to allow for collecting responses?
I'd propose by end of May, to give organizations a chance at figuring that out for themselves.
ek...@google.com <ek...@google.com> #10
Looks good. I have just a couple of suggestions:
- Expand on the "both discontinued" statement to make it clearer what is meant. This is referring to the fact that those ES versions have reached EOL upstream, and support for them has been discontinued in Gerrit.
- I think it would be useful to also ask which version of Gerrit is being used. Then we can make a better judgement about whether it's safe to discontinue ES support in Gerrit's stable releases. Additionally it would help to decide in which stable branch we're going to remove the "experimental" caveat from the documentation.
- Expand on the "both discontinued" statement to make it clearer what is meant. This is referring to the fact that those ES versions have reached EOL upstream, and support for them has been discontinued in Gerrit.
- I think it would be useful to also ask which version of Gerrit is being used. Then we can make a better judgement about whether it's safe to discontinue ES support in Gerrit's stable releases. Additionally it would help to decide in which stable branch we're going to remove the "experimental" caveat from the documentation.
ma...@gmail.com <ma...@gmail.com> #11
Thanks David.
- I added a "Discontinued Elasticsearch versions" section from your first suggestion above, with a few more words and upstream reference.
- I added 2 questions based on your second suggestion; good point as well.
I also added a trailing note about the survey end date (May end).
And I added Edwin's email suggestions to the survey intro.
I altered some questions to fit the "no Elasticsearch use" case in; thanks Edwin.
Can one of the form reviewer(s) test it, or I can send it as is; let me know.
- I added a "Discontinued Elasticsearch versions" section from your first suggestion above, with a few more words and upstream reference.
- I added 2 questions based on your second suggestion; good point as well.
I also added a trailing note about the survey end date (May end).
And I added Edwin's email suggestions to the survey intro.
I altered some questions to fit the "no Elasticsearch use" case in; thanks Edwin.
Can one of the form reviewer(s) test it, or I can send it as is; let me know.
ma...@gmail.com <ma...@gmail.com> #12
The form looks good now. I think it's OK to send it, but let's wait for comments from anyone else.
ek...@google.com <ek...@google.com> #13
I just realized that I forgot David (O.), so I just invited him to the form.
I'm done receiving go-aheads from everyone else by now.
I'm then planning to post the survey on Monday morning my time.
-This is so that I
1. can check David-O's comments if any, and
2. skip the lower email attendance /week-end.
I'm done receiving go-aheads from everyone else by now.
I'm then planning to post the survey on Monday morning my time.
-This is so that I
1. can check David-O's comments if any, and
2. skip the lower email attendance /week-end.
ek...@google.com <ek...@google.com> #14
> I just realized that I forgot David (O.), so I just invited him to the form.
Thanks, looks good. I have not found a way how to comment on the
Form document, answering here:
Can we add additional question if ES not used currently:
Are your organization considering/planning to switch to using Elasticsearch in near future?
Possible further question if asnwer to the above question is Yes/No:
Yes:
What specific version?
No:
Why not?
Thanks, looks good. I have not found a way how to comment on the
Form document, answering here:
Can we add additional question if ES not used currently:
Are your organization considering/planning to switch to using Elasticsearch in near future?
Possible further question if asnwer to the above question is Yes/No:
Yes:
What specific version?
No:
Why not?
is...@google.com <is...@google.com> #15
Thanks David. -Done.
Survey form is posted to the list now; awaiting responses...
We will monitor upcoming responses until May end.
I'm setting this Issue to Started under my name until then.
Responses should teach us how to tackle versions and beta-ness of ES in Gerrit.
Survey form is posted to the list now; awaiting responses...
We will monitor upcoming responses until May end.
I'm setting this Issue to Started under my name until then.
Responses should teach us how to tackle versions and beta-ness of ES in Gerrit.
Description
This issue is about setting up this meeting.
Things to do:
- find suitable time to accommodate different time zones
- reserve room at the hackathon location
- allow remote participants to join
- David Pursehouse would like us to use
- initialize the agenda for the next meeting
- send out invitations