Re: Forums Are Now Live at http://discuss.elastic.co
Apologies, I just saw this message. Are you still having access issues? Also, it is much faster to report trouble in #elasticsearch on Freenode if you are an IRC user. :) On Thu, May 28, 2015 at 4:55 AM, xinme...@163.com wrote: Can not visit https://discuss.elastic.co/ today. The website is loading all the time. 在 2015年5月5日星期二 UTC+8上午12:12:19，leslie.hawthorn写道： Hello everyone, We took in feedback on moving to a Discourse based forum for about a month, and it sounds like most of the folks who thought it might not be optimal were people who preferred to interact with mailing lists instead of forums. We're pretty confident the email functionality of Discourse will work well for our community, so we've gone ahead and rolled out the forums. You can visit them now and sign up for a user account at http://discuss.elastic.co. Registration is one time only and you can do so with any email address or authorizing via Facebook, GitHub, Google Accounts or Twitter. Once you've created your account, you can set up your preferences to receive email as often or as rarely as you would like. For those who'd prefer to interact solely via email, you can start doing so as soon as you've set these preferences. You can find full documentation on interacting with the forums solely via email here.[0] Some anticipated FAQs: 1) Should I ask for help using the forums on this mailing list? You're welcome to ask for help on this list, on IRC (#elasticsearch, #logstash or #kibana on Freenode) or within the forum in the Meta Elastic category. 2) Are you going to stop answering questions here? No, we're going to leave the mailing list active for at least 30 days so our entire community can kick the tires. Quoting our internal company FAQ for this very question: If our community members find Discourse to be suboptimal, we may make the choice to use the forums only for certain tasks and preserve the existing mailing lists. However, our goal is to provide a single source of truth for information on our products, so we're hoping the Discourse based forums really work for people. Our employees will be answering your questions with a pointer to a forum thread to encourage people to actually interact with the new resource, too. 3) So let's say that the forums work for people. What's the plan? We'll set these mailing lists to read-only ~30 days from now (June 1, 2015). We're still working with the creators of Discourse to do a full import of our mailing list archives, so once that task is complete the read-only archives will still be preserved, but you can search through all that collective knowledge in one place at http://discuss.elastic.co 4) Is there an FAQ for using the forums? We feel like the user interface for Discourse is pretty intuitive, but we have a short Notes on Using This Forum document [1] available to help you get started. 5) Where do I direct praise and pain points for the forums? Feedback on the forums should be posted to the Meta Elastic category. [2] You can update it via email using address discuss-meta [at] elastic [dot] co once you've set up your user account. 6) I have another question that you have not answered. What should I do? Please post a note in the Meta Elastic category, ping in IRC (I'm lh on Freenode, though anyone with ChanOps/Voice in #elasticsearch, #logstash and #kibana can help) or post a note in this thread. [0] - https://discuss.elastic.co/t/email-only-interaction-with-the-forums/106 [1] - https://discuss.elastic.co/t/notes-on-using-these-forums/118 [2] - https://discuss.elastic.co/c/meta Cheers, LH Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh Twitter: @lhawthorn -- Please update your bookmarks! We have moved to https://discuss.elastic.co/ --- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/68287801-937b-4deb-9f63-fc50f6f74774%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/68287801-937b-4deb-9f63-fc50f6f74774%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh Twitter: @lhawthorn Skype: mebelh Voice: +31 20 794 7300 -- Please update your bookmarks! We have moved to https://discuss.elastic.co/ --- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid
Re: Forums Are Now Live at http://discuss.elastic.co
It is entirely possible some of these items can be fixed. Investigating. Thank you for the candid feedback, Doug, Ivan and Jörg. Cheers, LH On Mon, May 11, 2015 at 10:24 PM, joergpra...@gmail.com joergpra...@gmail.com wrote: +1 for Doug and Ivan I'd also like to find the real names (which are available at Discuss because they are shown in the profile of a user) being added to the message view and the mail From header, for a more personal communication style. It would be easier to begin a reply with a greeting then. Hopefully this is received as a constructive feedback and not as moaning about Discuss software. Best, Jörg On Mon, May 11, 2015 at 12:03 AM, Doug Turnbull dturnb...@opensourceconnections.com wrote: Oh! I didn't see that. Thank you. I will look again. Yeah I actually like many things about discourse. I also like many of the low friction aspects of a mailing list. I am worried my email sounds too negative. I should list positives like great markdown support and much prettier and more legible emails. Discourse is phenomenal forum software. I honestly hope they can really bridge the gap effortlessly to have as part of their capabilities truly effortless implementation of a dev mailing list with an optional forum view. I'm sure I'll be using discourse to great effect (and it seems to be being used). So I could be completly wrong about all my points. :) Doug On Sunday, May 10, 2015, Ivan Brusic i...@brusic.com wrote: I should have added something similar to what does expressed in his last paragraph. My feedback was meant to be constructive. Despite this being a technical mailing list, I still appreciate a more personal touch. BTW, Doug, you can watch specific categories. There is a general watch-all setting that you might have turned on. Ivan On May 10, 2015 2:37 PM, Doug Turnbull dturnb...@opensourceconnections.com wrote: I agree. While I appreciate the experimentation, I hope discourse can get to a point where I can forget it's even a forum. Whereby everything can just truly feel like a native mailing list with a great deal less friction, but it's not there yet. Here's some of the missing features: - a signup process that's more an email subscription (just paste in an email address) without having to create any kind of forum account or profile. - the ability to reply to someone individually to their email address. The ability for others to email me directly without discourses PM feature. - It needs the ability to subscribe per topic. Things are a bit noisy right now (ie I'm not interested in log stash) - eliminate noreply in the email notifications. I don't feel like I should participate via email when I see this. Give it a friendly name. Right now use via email feels second class. But I think it's the most important thing. I'm likely to scan my low priority inbox where mailing list emails are sent. I'm going to struggle to remember to check in on and participate in a forum to help folks. It's another place to go and all my other OSS mailing lists come to my email and I can work with them seemlessly. So I'm likely to forget to check or possibly not want to bother with elastic which uses a different system. Yes, I do get the notifications, but it doesn't quite feel the same as a mailing list for the reasons above. It feels like a notification from another system. Anyway long and frank email. Forgive the bluntness. I just wanted to express hopefully useful feedback. I do appreciate the thoughtfulness here. I know elastic and discourse folks are very smart. Email truly can become a first class experience and keep some of the great things about discourse. Cheers! Doug On Sunday, May 10, 2015, Ivan Brusic i...@brusic.com wrote: I really do not care for the new mailing list. First of all, I can no longer see real names and email addresses. All I see is whatever nonsensical handle someone choose on sign up. Searching for Adrien no longer returns his latest posts. Second, since every email comes from nore...@discuss.elastic.co, I can no longer see who replied to a thread. All I see is the handle of the original poster. I can see the reply counts, but have no idea who the replies are from. Add both of these issues together, and the list has now become very impersonal. Cheers, Ivan On May 5, 2015 10:49 AM, Leslie Hawthorn leslie.hawth...@elastic.co wrote: Sadly, we cannot twibble bit to allow certain types of links but not others. However, we can adjust the forum settings to allow users to include links in their posts from the start of using the forum. I've done so. Let us know if you have any further issues. And, to reiterate what Tyler said earlier, it would be super awesome to put this feedback in the Meta Elastic category.[0] Why you may ask? 1) Employees from Discourse are keeping an eye on our forum to help us help you have a good experience. They're not reading
Re: Forums Are Now Live at http://discuss.elastic.co
Sadly, we cannot twibble bit to allow certain types of links but not others. However, we can adjust the forum settings to allow users to include links in their posts from the start of using the forum. I've done so. Let us know if you have any further issues. And, to reiterate what Tyler said earlier, it would be super awesome to put this feedback in the Meta Elastic category.[0] Why you may ask? 1) Employees from Discourse are keeping an eye on our forum to help us help you have a good experience. They're not reading this list, though. 2) Trying for the single source of truth mentioned in my original post. Thank you to everyone for the great feedback so far! [0] - https://discuss.elastic.co/c/meta or via email discuss+meta [at] elastic [dot] co Cheers, LH On Tue, May 5, 2015 at 12:57 AM, Nikolas Everett nik9...@gmail.com wrote: I think github and pastebins/gists shouldn't be considered against the limit. We ask people to use gist all the time and github issue or code links are a good thing to use as well. On May 4, 2015 5:40 PM, joergpra...@gmail.com joergpra...@gmail.com wrote: Thanks Shaunak, I appreciate that. I think it would be more than welcome to let others of the community also take the advantage of including Github issues into the forum software which contain numerous links: https://discuss.elastic.co/t/link-level-in-a-post/151 Best, Jörg On Mon, May 4, 2015 at 11:05 PM, shau...@elastic.co wrote: Hey Jörg, I've removed this restriction from your account. You should be able to post more than 2 links in a post now :) Shaunak On Monday, May 4, 2015 at 2:07:14 PM UTC-5, Jörg Prante wrote: It does not work. I can not post messages with links. After I try to post a new topic such as - snip To all of you who want to sneak at the features planned for ES 2.0, this issue collects some of it https://github.com/elastic/elasticsearch/issues/9970 Best, Jörg snip I receive a denial Sorry, new users can only put 2 links in a post. Beside the fact I included just one link, why this restriction? A bit sad that I am considered a new user after five years happily using ES but the machine is always right in the end ;) Jörg On Mon, May 4, 2015 at 6:58 PM, Leslie Hawthorn leslie@elastic.co wrote: On Mon, May 4, 2015 at 6:41 PM, Nikolas Everett nik...@gmail.com wrote: I suspect its read only while they sort out resourcing issues. Cache hit rate is likely quite high while readonly. On May 4, 2015 12:38 PM, Jürgen Wagner (DVT) juergen...@devoteam.com wrote: The site is read-only. No signups possible. Hmm... Our friends at Discourse have reported that the site outage has been resolved. They'll keep up with updates via their Twitter account: https://twitter.com/discourse/status/595268564493279232 In the meantime, please go forth and use the forums. If they fall over again we will work to ensure speedy resolution. Thanks for your patience, folks. Cheers, LH -- Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh Twitter: @lhawthorn -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHj2c4BDbbSBYHStNuY6wNZ0--JBtqSTQ-7bJoBapzZNfoXUFw%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAHj2c4BDbbSBYHStNuY6wNZ0--JBtqSTQ-7bJoBapzZNfoXUFw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a0dfa043-430e-4e1f-83e5-69d644651175%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/a0dfa043-430e-4e1f-83e5-69d644651175%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8smg%3Dy5BsdMxLjEOUE9QW5ZOpDUVBEU%3DnmRXT-bhTPQ%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8smg%3Dy5BsdMxLjEOUE9QW5ZOpDUVBEU%3DnmRXT-bhTPQ%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you
Re: Evaluating Moving to Discourse - Feedback Wanted
Hi David, On Fri, May 1, 2015 at 8:36 PM, David Reagan jer...@gmail.com wrote: Why do you find IRC unfriendly? Have you tried using a web based client like irccloud.com? I use webchat.freenode.net. There's a big difference between, Here's our live chat app. and Learn how to connect to IRC in order to use live chat. I actively avoided live chat for years simply because I had no interest in learning anything about IRC. For a new user, IRC is not friendly, especially if you are not a developer or are new to it. I hear you. I think those of us who have been using IRC for decades think it is easy. I know I find it more intuitive than HipChat. There's also the fact that you are told off if you post any code when asking for help. I could see it if the code sample was really long, but when people get told off when they post three or four lines of code, that's not friendly at all. This has happened to me, and I've seen it happen to others. (Not sure it if was in an ELK channel or not...) I sure hope not - we pride ourselves on having a courteous and welcoming community presence. Each channel has its own culture, and some are brusque or downright rude. That's not how we play it. :) Plus, figuring out how to start a private conversation, or set your status to away, or registering your username so others can't impersonate you, and so on is not obvious. I still haven't taken the time to figure it out. Yes, and a pointer to an FAQ doc isn't interesting when you want something to just work(TM). Ideally, we'd have something that functions similar to HipChat. Nice UI, and code snippets are automatically shortened unless you choose to show the full snippet. Worth thinking through, though I doubt we'll action this any time soon. We're doing our best to maintain good coverage in our IRC channels and folks would still prefer Elastic employees were around more often. Opening up yet another chat mechanism seems like a way to make sure even more people feel the same way. ;) Really appreciate the feedback! Cheers, LH --David Reagan On Fri, May 1, 2015 at 11:17 AM, Leslie Hawthorn leslie.hawth...@elastic.co wrote: On Fri, May 1, 2015 at 7:26 PM, David Reagan jer...@gmail.com wrote: Moving away from mailing lists for anything except announcements would be awesome. Forums are a much better way to have solid discussions with multiple people in. Email is fine, but when you add in more than a couple people, it gets confusing fast. Forums are also far more user friendly for people who haven't learned the various ways developers communicate. Thanks for your feedback! That said, if the forum idea is scrapped, please be sure to stick with Google Groups or something similar. Don't switch to something like the Debian user lists. Every time a search result pops up from a list like that when I am looking for help, I can never figure out if I've seen all the emails in the thread or not. The interface is just horrid. Google Groups at least has conversation view. Mailman is little painful, but with the latest release it's become a bit friendlier. On a similar subject, is there any chance we could get a real time chat app that is more user friendly than IRC? Does something exist that could sit on top of IRC and alleviate the IRC's user unfriendliness? Why do you find IRC unfriendly? Have you tried using a web based client like irccloud.com? Cheers, LH On Thursday, April 2, 2015 at 8:36:33 AM UTC-7, leslie.hawthorn wrote: Hello everyone, As we’ve begun to scale up development on three different open source projects, we’ve found Google Groups to be a difficult solution for dealing with all of our needs for community support. We’ve got multiple mailing lists going, which can be confusing for new folks trying to figure out where to go to ask a question. We’ve also found our lists are becoming noisy in the “good problem to have” kind of way. As we’ve seen more user adoption, and across such a wide variety of use cases, we’re getting widely different types of questions asked. For example, I can imagine that folks not using our Python client would rather not be distracted with emails about it. There’s also a few other strikes against Groups as a tool, such as the fact that it is no longer a supported product by Google, it provides no API hooks and it is not available for users in China. We’ve evaluated several options and we’re currently considering shuttering the elasticsearch-user and logstash-users Google Groups in favor of a Discourse forum. You can read more about Discourse at http://www.discourse.org We feel Discourse will allow us to provide a better experience for all of our users for a few reasons: * More fine grained conversation topics = less noise and better targeted discussions. e.g. we can offer a forum for each language client, individual logstash plugin or for each city to plan user group meetings, etc. * Facilitates
Re: Forums Are Now Live at http://discuss.elastic.co
On Mon, May 4, 2015 at 6:21 PM, Nikolas Everett nik9...@gmail.com wrote: On Mon, May 4, 2015 at 12:12 PM, leslie.hawthorn leslie.hawth...@elastic.co wrote: Hello everyone, We took in feedback on moving to a Discourse based forum for about a month, and it sounds like most of the folks who thought it might not be optimal were people who preferred to interact with mailing lists instead of forums. We're pretty confident the email functionality of Discourse will work well for our community, so we've gone ahead and rolled out the forums. You can visit them now and sign up for a user account at http://discuss.elastic.co. Registration is one time only and you can do so with any email address or authorizing via Facebook, GitHub, Google Accounts or Twitter. And its falling over. 503s everywhere. Thanks for the bug report. Addressing now Cheers, LH -- Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh Twitter: @lhawthorn Skype: mebelh Voice: +31 20 794 7300 -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHj2c4Ci7CE0rUqoBRgKZNLeU02%2BSY4NYSjn_LEYE6cGQfRW-w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Forums Are Now Live at http://discuss.elastic.co
On Mon, May 4, 2015 at 6:38 PM, Jürgen Wagner (DVT) juergen.wag...@devoteam.com wrote: The site is read-only. No signups possible. Hmm... Known issue - we're addressing. Whee! We'll update this thread when the issue is resolved. Cheers, LH -- Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh Twitter: @lhawthorn -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHj2c4CKwY4HnW9VVXVaJrF9gkB5Chm9An73OYjJ%3DLwT1nB%3D7g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Forums Are Now Live at http://discuss.elastic.co
On Mon, May 4, 2015 at 6:41 PM, Nikolas Everett nik9...@gmail.com wrote: I suspect its read only while they sort out resourcing issues. Cache hit rate is likely quite high while readonly. On May 4, 2015 12:38 PM, Jürgen Wagner (DVT) juergen.wag...@devoteam.com wrote: The site is read-only. No signups possible. Hmm... Our friends at Discourse have reported that the site outage has been resolved. They'll keep up with updates via their Twitter account: https://twitter.com/discourse/status/595268564493279232 In the meantime, please go forth and use the forums. If they fall over again we will work to ensure speedy resolution. Thanks for your patience, folks. Cheers, LH -- Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh Twitter: @lhawthorn -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHj2c4BDbbSBYHStNuY6wNZ0--JBtqSTQ-7bJoBapzZNfoXUFw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Evaluating Moving to Discourse - Feedback Wanted
On Fri, May 1, 2015 at 7:26 PM, David Reagan jer...@gmail.com wrote: Moving away from mailing lists for anything except announcements would be awesome. Forums are a much better way to have solid discussions with multiple people in. Email is fine, but when you add in more than a couple people, it gets confusing fast. Forums are also far more user friendly for people who haven't learned the various ways developers communicate. Thanks for your feedback! That said, if the forum idea is scrapped, please be sure to stick with Google Groups or something similar. Don't switch to something like the Debian user lists. Every time a search result pops up from a list like that when I am looking for help, I can never figure out if I've seen all the emails in the thread or not. The interface is just horrid. Google Groups at least has conversation view. Mailman is little painful, but with the latest release it's become a bit friendlier. On a similar subject, is there any chance we could get a real time chat app that is more user friendly than IRC? Does something exist that could sit on top of IRC and alleviate the IRC's user unfriendliness? Why do you find IRC unfriendly? Have you tried using a web based client like irccloud.com? Cheers, LH On Thursday, April 2, 2015 at 8:36:33 AM UTC-7, leslie.hawthorn wrote: Hello everyone, As we’ve begun to scale up development on three different open source projects, we’ve found Google Groups to be a difficult solution for dealing with all of our needs for community support. We’ve got multiple mailing lists going, which can be confusing for new folks trying to figure out where to go to ask a question. We’ve also found our lists are becoming noisy in the “good problem to have” kind of way. As we’ve seen more user adoption, and across such a wide variety of use cases, we’re getting widely different types of questions asked. For example, I can imagine that folks not using our Python client would rather not be distracted with emails about it. There’s also a few other strikes against Groups as a tool, such as the fact that it is no longer a supported product by Google, it provides no API hooks and it is not available for users in China. We’ve evaluated several options and we’re currently considering shuttering the elasticsearch-user and logstash-users Google Groups in favor of a Discourse forum. You can read more about Discourse at http://www.discourse.org We feel Discourse will allow us to provide a better experience for all of our users for a few reasons: * More fine grained conversation topics = less noise and better targeted discussions. e.g. we can offer a forum for each language client, individual logstash plugin or for each city to plan user group meetings, etc. * Facilitates discussions that are not generally happening on list now, such as best practices by use case or tips from moving to development to production * Easier for folks who are purely end users - and less used to getting peer support on a mailing list - to get help when they need it Obviously, Discourse does not function the exact same way as a mailing list - however, email interaction with Discourse is supported and will continue to allow you to participate in discussions over email (though there are some small issues related to in-line replies. [0]) We’re working with the Discourse team now as part of evaluating this transition, and we know they’re working to resolve this particular issue. We’re also still determining how Discourse will handle our needs for both user and list archive migration, and we’ll know the precise details of how that would work soon. (We’ll share when we have them.) The final goal would be to move Google Groups to read-only archives, and cut over to Discourse completely for community support discussions. We’re looking at making the cut over in ~30 days from today, but obviously that’s subject to the feedback we receive from all of you. We’re sharing this information to set expectations about time frame for making the switch. It’s not set in stone. Our highest priority is to ensure effective migration of our list archives and subscribers, which may mean a longer time horizon for deploying Discourse, as well. In the meantime, though, we wanted to communicate early and often and get your feedback. Would this change make your life better? Worse? Meh? Please share your thoughts with us so we can evaluate your feedback. We don’t take this switch lightly, and we want to understand how it will impact your overall workflow and experience. We’ll make regular updates to the list responding to incoming feedback and be completely transparent about how our thought processes evolve based on it. Thanks in advance! [0] - https://meta.discourse.org/t/migrating-from-google-groups/24695 Cheers, LH Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh
Re: Evaluating Moving to Discourse - Feedback Wanted
On Wed, Apr 15, 2015 at 9:02 AM, Ivan Brusic i...@brusic.com wrote: I should clarify that I have no issues moving to Discourse, as long as instantaneous email interaction is preserved, just wanted to point out that I see no issues with the mailing lists. Understood. The question is moot anyways since the change will happen regardless of our inputs. Actually, I'm maintaining our Forums pre-launch checklist where there's a line item for don't move forward based on community feedback. I respectfully disagree with your assessment that the change will happen regardless of input from the community. We asked for feedback for a reason. :) I hope we can subscribe to Discourse mailing lists without needing an account. You'll need an account, but it's a one-time login to set up your preferences and then read/interact solely via email. Cheers, LH Cheers, Ivan On Apr 13, 2015 7:13 PM, Leslie Hawthorn leslie.hawth...@elastic.co wrote: Thanks for your feedback, Ivan. There's no plan to remove threads from the forums, so information would always be archived there as well. Does that impact your thoughts on moving to Discourse? Folks, please keep the feedback coming! Cheers, LH On Sat, Apr 11, 2015 at 12:09 AM, Ivan Brusic i...@brusic.com wrote: As one of the oldest and most frequent users (before my sabbatical) of the mailing list, I just wanted to say that I never had an issue with it. It works. As long as I could continue using only email, I am happy. For realtime communication, there is the IRC channel. If prefer the mailing list since everything is archived. Ivan On Apr 2, 2015 5:36 PM, leslie.hawthorn leslie.hawth...@elastic.co wrote: Hello everyone, As we’ve begun to scale up development on three different open source projects, we’ve found Google Groups to be a difficult solution for dealing with all of our needs for community support. We’ve got multiple mailing lists going, which can be confusing for new folks trying to figure out where to go to ask a question. We’ve also found our lists are becoming noisy in the “good problem to have” kind of way. As we’ve seen more user adoption, and across such a wide variety of use cases, we’re getting widely different types of questions asked. For example, I can imagine that folks not using our Python client would rather not be distracted with emails about it. There’s also a few other strikes against Groups as a tool, such as the fact that it is no longer a supported product by Google, it provides no API hooks and it is not available for users in China. We’ve evaluated several options and we’re currently considering shuttering the elasticsearch-user and logstash-users Google Groups in favor of a Discourse forum. You can read more about Discourse at http://www.discourse.org We feel Discourse will allow us to provide a better experience for all of our users for a few reasons: * More fine grained conversation topics = less noise and better targeted discussions. e.g. we can offer a forum for each language client, individual logstash plugin or for each city to plan user group meetings, etc. * Facilitates discussions that are not generally happening on list now, such as best practices by use case or tips from moving to development to production * Easier for folks who are purely end users - and less used to getting peer support on a mailing list - to get help when they need it Obviously, Discourse does not function the exact same way as a mailing list - however, email interaction with Discourse is supported and will continue to allow you to participate in discussions over email (though there are some small issues related to in-line replies. [0]) We’re working with the Discourse team now as part of evaluating this transition, and we know they’re working to resolve this particular issue. We’re also still determining how Discourse will handle our needs for both user and list archive migration, and we’ll know the precise details of how that would work soon. (We’ll share when we have them.) The final goal would be to move Google Groups to read-only archives, and cut over to Discourse completely for community support discussions. We’re looking at making the cut over in ~30 days from today, but obviously that’s subject to the feedback we receive from all of you. We’re sharing this information to set expectations about time frame for making the switch. It’s not set in stone. Our highest priority is to ensure effective migration of our list archives and subscribers, which may mean a longer time horizon for deploying Discourse, as well. In the meantime, though, we wanted to communicate early and often and get your feedback. Would this change make your life better? Worse? Meh? Please share your thoughts with us so we can evaluate your feedback. We don’t take this switch lightly, and we want to understand how it will impact your overall workflow and experience. We’ll make regular
Re: Evaluating Moving to Discourse - Feedback Wanted
Thanks for your feedback, Ivan. There's no plan to remove threads from the forums, so information would always be archived there as well. Does that impact your thoughts on moving to Discourse? Folks, please keep the feedback coming! Cheers, LH On Sat, Apr 11, 2015 at 12:09 AM, Ivan Brusic i...@brusic.com wrote: As one of the oldest and most frequent users (before my sabbatical) of the mailing list, I just wanted to say that I never had an issue with it. It works. As long as I could continue using only email, I am happy. For realtime communication, there is the IRC channel. If prefer the mailing list since everything is archived. Ivan On Apr 2, 2015 5:36 PM, leslie.hawthorn leslie.hawth...@elastic.co wrote: Hello everyone, As we’ve begun to scale up development on three different open source projects, we’ve found Google Groups to be a difficult solution for dealing with all of our needs for community support. We’ve got multiple mailing lists going, which can be confusing for new folks trying to figure out where to go to ask a question. We’ve also found our lists are becoming noisy in the “good problem to have” kind of way. As we’ve seen more user adoption, and across such a wide variety of use cases, we’re getting widely different types of questions asked. For example, I can imagine that folks not using our Python client would rather not be distracted with emails about it. There’s also a few other strikes against Groups as a tool, such as the fact that it is no longer a supported product by Google, it provides no API hooks and it is not available for users in China. We’ve evaluated several options and we’re currently considering shuttering the elasticsearch-user and logstash-users Google Groups in favor of a Discourse forum. You can read more about Discourse at http://www.discourse.org We feel Discourse will allow us to provide a better experience for all of our users for a few reasons: * More fine grained conversation topics = less noise and better targeted discussions. e.g. we can offer a forum for each language client, individual logstash plugin or for each city to plan user group meetings, etc. * Facilitates discussions that are not generally happening on list now, such as best practices by use case or tips from moving to development to production * Easier for folks who are purely end users - and less used to getting peer support on a mailing list - to get help when they need it Obviously, Discourse does not function the exact same way as a mailing list - however, email interaction with Discourse is supported and will continue to allow you to participate in discussions over email (though there are some small issues related to in-line replies. [0]) We’re working with the Discourse team now as part of evaluating this transition, and we know they’re working to resolve this particular issue. We’re also still determining how Discourse will handle our needs for both user and list archive migration, and we’ll know the precise details of how that would work soon. (We’ll share when we have them.) The final goal would be to move Google Groups to read-only archives, and cut over to Discourse completely for community support discussions. We’re looking at making the cut over in ~30 days from today, but obviously that’s subject to the feedback we receive from all of you. We’re sharing this information to set expectations about time frame for making the switch. It’s not set in stone. Our highest priority is to ensure effective migration of our list archives and subscribers, which may mean a longer time horizon for deploying Discourse, as well. In the meantime, though, we wanted to communicate early and often and get your feedback. Would this change make your life better? Worse? Meh? Please share your thoughts with us so we can evaluate your feedback. We don’t take this switch lightly, and we want to understand how it will impact your overall workflow and experience. We’ll make regular updates to the list responding to incoming feedback and be completely transparent about how our thought processes evolve based on it. Thanks in advance! [0] - https://meta.discourse.org/t/migrating-from-google-groups/24695 Cheers, LH Leslie Hawthorn Director of Developer Relations http://elastic.co -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHj2c4A6M4LfRUaEeTQbFx16%3D%2Bi5cvuzunB0f3rbQaeP312COQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Evaluating Moving to Discourse - Feedback Wanted
Thank you for your feedback, Glen! We're currently planning to use the hosted platform. Folks, please keep the feedback coming. We value your opinion. Cheers, LH On Thu, Apr 9, 2015 at 5:23 PM, Glen Smith g...@smithsrock.com wrote: +1 for recognizing the challenge, proactively approaching it, clearly articulating the issues, and proposing a seemingly beneficial solution. Migrating off of gg would, IMO, be a good thing, for the reasons you stated, plus numerous consequences of the unsupported state. e.g. nobody is ever forever going to invest anything in improving the user interface. I confess to not having heard of discourse before. I like that it's GPL. Is the plan to use a Discourse-hosted instance, or for Elastic to launch its own? In summary, +1. Cheers. On Thursday, April 2, 2015 at 11:36:33 AM UTC-4, leslie.hawthorn wrote: Hello everyone, As we’ve begun to scale up development on three different open source projects, we’ve found Google Groups to be a difficult solution for dealing with all of our needs for community support. We’ve got multiple mailing lists going, which can be confusing for new folks trying to figure out where to go to ask a question. We’ve also found our lists are becoming noisy in the “good problem to have” kind of way. As we’ve seen more user adoption, and across such a wide variety of use cases, we’re getting widely different types of questions asked. For example, I can imagine that folks not using our Python client would rather not be distracted with emails about it. There’s also a few other strikes against Groups as a tool, such as the fact that it is no longer a supported product by Google, it provides no API hooks and it is not available for users in China. We’ve evaluated several options and we’re currently considering shuttering the elasticsearch-user and logstash-users Google Groups in favor of a Discourse forum. You can read more about Discourse at http://www.discourse.org http://www.google.com/url?q=http%3A%2F%2Fwww.discourse.orgsa=Dsntz=1usg=AFQjCNFQi_hMkuJsZ9_yWmYpibYIPzwS7w We feel Discourse will allow us to provide a better experience for all of our users for a few reasons: * More fine grained conversation topics = less noise and better targeted discussions. e.g. we can offer a forum for each language client, individual logstash plugin or for each city to plan user group meetings, etc. * Facilitates discussions that are not generally happening on list now, such as best practices by use case or tips from moving to development to production * Easier for folks who are purely end users - and less used to getting peer support on a mailing list - to get help when they need it Obviously, Discourse does not function the exact same way as a mailing list - however, email interaction with Discourse is supported and will continue to allow you to participate in discussions over email (though there are some small issues related to in-line replies. [0]) We’re working with the Discourse team now as part of evaluating this transition, and we know they’re working to resolve this particular issue. We’re also still determining how Discourse will handle our needs for both user and list archive migration, and we’ll know the precise details of how that would work soon. (We’ll share when we have them.) The final goal would be to move Google Groups to read-only archives, and cut over to Discourse completely for community support discussions. We’re looking at making the cut over in ~30 days from today, but obviously that’s subject to the feedback we receive from all of you. We’re sharing this information to set expectations about time frame for making the switch. It’s not set in stone. Our highest priority is to ensure effective migration of our list archives and subscribers, which may mean a longer time horizon for deploying Discourse, as well. In the meantime, though, we wanted to communicate early and often and get your feedback. Would this change make your life better? Worse? Meh? Please share your thoughts with us so we can evaluate your feedback. We don’t take this switch lightly, and we want to understand how it will impact your overall workflow and experience. We’ll make regular updates to the list responding to incoming feedback and be completely transparent about how our thought processes evolve based on it. Thanks in advance! [0] - https://meta.discourse.org/t/migrating-from-google-groups/24695 Cheers, LH Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh Twitter: @lhawthorn -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch
Re: Evaluating Moving to Discourse - Feedback Wanted
practices by use case or tips from moving to development to production * Easier for folks who are purely end users - and less used to getting peer support on a mailing list - to get help when they need it Obviously, Discourse does not function the exact same way as a mailing list - however, email interaction with Discourse is supported and will continue to allow you to participate in discussions over email (though there are some small issues related to in-line replies. [0]) We’re working with the Discourse team now as part of evaluating this transition, and we know they’re working to resolve this particular issue. We’re also still determining how Discourse will handle our needs for both user and list archive migration, and we’ll know the precise details of how that would work soon. (We’ll share when we have them.) The final goal would be to move Google Groups to read-only archives, and cut over to Discourse completely for community support discussions. We’re looking at making the cut over in ~30 days from today, but obviously that’s subject to the feedback we receive from all of you. We’re sharing this information to set expectations about time frame for making the switch. It’s not set in stone. Our highest priority is to ensure effective migration of our list archives and subscribers, which may mean a longer time horizon for deploying Discourse, as well. In the meantime, though, we wanted to communicate early and often and get your feedback. Would this change make your life better? Worse? Meh? Please share your thoughts with us so we can evaluate your feedback. We don’t take this switch lightly, and we want to understand how it will impact your overall workflow and experience. We’ll make regular updates to the list responding to incoming feedback and be completely transparent about how our thought processes evolve based on it. Thanks in advance! [0] - https://meta.discourse.org/t/migrating-from-google-groups/24695 Cheers, LH Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh Twitter: @lhawthorn -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a0c02cd4-231d-4ce5-adb7-7164de76a902%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/a0c02cd4-231d-4ce5-adb7-7164de76a902%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH6s0fxJOd8N44sMW92dzXcaQVj2BHkhn5-e%2BhgNCrRTC804Zw%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAH6s0fxJOd8N44sMW92dzXcaQVj2BHkhn5-e%2BhgNCrRTC804Zw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Leslie Hawthorn Director of Developer Relations http://elastic.co Other Places to Find Me: Freenode: lh Twitter: @lhawthorn Skype: mebelh Voice: +31 20 794 7300 -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHj2c4Cuer_%3DKb1_BERmnY4u_u%3DZ1W52C2AnBgRcGuAd6DwOmA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Sorry for the spam, folks .... Re: [High] =|) Watch X-Men: Days of Future Past 2014 Full Movie Online
Hello everyone, Sorry for the recent spam. User banned, and I'm heading clean up the online archives now. Cheers, LH -- Leslie Hawthorn Community Manager http://elasticsearch.com Other Places to Find Me: Freenode: lh Twitter: @lhawthorn Skype: mebelh Voice: +31 20 794 7300 -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAB5RFS-ZyXK64orrwiX0Qsk937OcpFEavBu_wRb0ZxJCkA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: ElasticSearch is down
Known issue and we're looking into it. Thanks for the bug report. We'll post here when we're back to live. Cheers, LH On Wed, Jun 18, 2014 at 10:45 PM, ElasticRabbit ayushsang...@gmail.com wrote: Just a note..!! -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7b75925c-3da7-4397-b33b-a4b2ea329fbe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Leslie Hawthorn Community Manager http://elasticsearch.com Other Places to Find Me: Freenode: lh Twitter: @lhawthorn Skype: mebelh Voice: +31 20 794 7300 -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAB5RFS-QV9d%2BnQia-yrdny8Y1dkBtE7qaoPbd0vi%2BFYSuxYaxA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: ElasticSearch Benchmark
Hi Jianjun, On Thu, Apr 10, 2014 at 3:02 PM, Jianjun Hu 4nexu...@gmail.com wrote: Hi all, How to do benchmark of the ElasticSearch? Thanks! The answer to this question is it depends. It would be very helpful to describe a bit more about what you are working on so people can give a better answer to you. :) Best, LH -- Leslie Hawthorn Community Manager http://elasticsearch.com Other Places to Find Me: Freenode: lh Twitter: @lhawthorn Skype: mebelh Voice: +31 20 794 7300 -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAB5RFS8y1oOQk7ehyrOnxDbf0KkL793suTnZtXKXZN1mtc3SBg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: ElasticSearch Benchmark
Hi Jianjun, Thank you for the additional details. I think we will need some more information but I will let someone who is better skilled at benchmarking Elasticsearch ask you about it. Welcome to the mailing list! We are happy to have you here and to help. Cheers, LH On Thu, Apr 10, 2014 at 3:42 PM, Jianjun Hu 4nexu...@gmail.com wrote: Hi Leslie, Thanks for your reply. We have some data in MySQL database and some PDF documents. We want to index them and let our user to use. So we decide to use the ElasticSearch. Before using the ElsaticSearch, we want to know the performance of the ElasticSearch, so we want to do benchmark of the ElasticSearch. However, we don't know how to do. I'm not sure if I express my question clearly. Best, Jianjun On Thursday, April 10, 2014 9:11:37 AM UTC-4, Leslie Hawthorn wrote: Hi Jianjun, On Thu, Apr 10, 2014 at 3:02 PM, Jianjun Hu 4nex...@gmail.com wrote: Hi all, How to do benchmark of the ElasticSearch? Thanks! The answer to this question is it depends. It would be very helpful to describe a bit more about what you are working on so people can give a better answer to you. :) Best, LH -- Leslie Hawthorn Community Manager http://elasticsearch.com Other Places to Find Me: Freenode: lh Twitter: @lhawthorn Skype: mebelh Voice: +31 20 794 7300 -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b6aa8d62-842a-4d2e-b184-0ef40530d47e%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/b6aa8d62-842a-4d2e-b184-0ef40530d47e%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Leslie Hawthorn Community Manager http://elasticsearch.com Other Places to Find Me: Freenode: lh Twitter: @lhawthorn Skype: mebelh Voice: +31 20 794 7300 -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAB5RFS-_2SRbUkc_yVU4W_fPPq4efXPKnB%2Bnmh%2B2cveKoq_BVQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: ELK source tar balls
I heard at FOSDEM that Peter Robinson was looking at packaging Elasticsearch for Fedora. You may want to check in with him to see if he's moved down that path. Cheers, LH -- Leslie Hawthorn Community Manager http://elasticsearch.com Other Places to Find Me: Freenode: lh Twitter: @lhawthorn Skype: mebelh Voice: +31 20 794 7300 On Thu, Mar 6, 2014 at 3:00 PM, Lukáš Vlček lukas.vl...@gmail.com wrote: Jörg IMO the best approach would be to do this in context on Fedora packaging, this means opening a ticket in appropriate system, where Fedora packaging issues are tracked and do the work in context of such ticket. This way it could get attention from the people that have a lot of experience in this domain. If you are fine with that I will try to find which forum is the right one. WDYT? Regards, Lukáš On Thu, Mar 6, 2014 at 11:58 AM, joergpra...@gmail.com joergpra...@gmail.com wrote: Yes, I'm aware of building the dependencies SRPMs too, and I agree it is a lot of work. Examining the Solr SRPM at https://bugzilla.redhat.com/show_bug.cgi?id=1025904 a lot of work has been already done regarding dependencies, and that encourages me to add the missing ones for ES. I think it is worth a try now that ES 1.0 is out. I'm unsure about how far I can proceed and if I find time to provide SRPMs for all future ES patch/bugfix versions. Maybe others are also interested in package maintaining and jump in, I'd welcome this. Jörg On Thu, Mar 6, 2014 at 11:24 AM, Lukáš Vlček lukas.vl...@gmail.com wrote: Jörg my point about shaded deps is that if you want to deliver crystal clear RPM from Fedora POW then you need to build source RPM first and then noarch RPM. Which means that you would first need to have all the shaded deps as a separate RPMs available in some RPM repo (and if they have transitive deps then these need to be also build as a standalone RPMs as well ... etc). At least that is how I understand this and it can be a lot of work if you want to support it long term and according to all Linux packaging standards. Regards, Lukáš -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eJZmPzDPrF%2B%2BVXJOx7dhHZ28%3DhvrUY%3DLyyKDCaFcRw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAO9cvUbmrUtDS%3D56rg7SA%3DD_K4PA7RrVrJQzYMip585e-0P-9g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAB5RFS8UKSn-AQQU4PYhncTEKgkjDkvtdpOkRnCZ8cWxhgqmFg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
