Itamar:
Correct - replying to topics via email is supported. We're trying very hard to ensure that people who rely primarily on email aren't left out, so we've double checked to ensure that if you want to interact primarily through email, you'll definitely be able to (receiving all new posts via email, replying to those via email, et cetera.) Jörg: Some of those reasons you've mentioned are motivating factors for the move to an open-source platform like Discourse. Some features like the ability to download your own posts are already built-in, such as the feature shown below: <https://lh3.googleusercontent.com/-fNtYF8_sGlw/VS6sD7p2SVI/AAAAAAAAACw/uaHykWji6RM/s1600/Screen%2BShot%2B2015-04-15%2Bat%2B12.11.29%2BPM.png> In addition, unlike google groups, Discourse has a very comprehensive API that *anyone* would be able to leverage to export data however they would like. And again, if email is the preferred method, you could always subscribe to everything and just rely on email archives as well. On Wednesday, April 15, 2015 at 12:08:21 PM UTC-6, Jörg Prante wrote: > > I know I can not influence the decision for Discourse, so here are just my > 2 ¢. > > The move should also consider that users who register with the new forum > should have the right to export their own contributions to download them > similar to Google takeaway function for Gmail / G+ account. > > Also, it would be a an advance to add a license note, compatible to the > Open Data Commons License http://opendatacommons.org/licenses/ to the > user contributions. This would ensure long term archiving / harvesting / > text-and-data-mining rights by the community. No one knows which system > comes after Discourse. > > If such licensing terms could be applied, I would find a file dump service > very useful. Discourse allows a Postgresql dump of a forum, and I would > appreciate regular data dumps that are made available to the public. Maybe > to the Internet Archive, like https://archive.org/details/stackexchange > > I support all suggestions which prefer forum access by email. I use emails > since 1989 and I can not make friends with systems that remind me of toys > and eyecandy like Google Wave http://en.wikipedia.org/wiki/Apache_Wave > and offer "likes" like Facebook. I don't need that crap. > > Best, > > Jörg > > > On Wed, Apr 15, 2015 at 7:20 PM, Leslie Hawthorn <leslie....@elastic.co > <javascript:>> wrote: > >> >> >> On Wed, Apr 15, 2015 at 9:02 AM, Ivan Brusic <iv...@brusic.com >> <javascript:>> 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....@elastic.co >>> <javascript:>> 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 <iv...@brusic.com >>>> <javascript:>> 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....@elastic.co >>>>> <javascript:>> 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 elasticsearc...@googlegroups.com <javascript:>. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/elasticsearch/CAHj2c4A6M4LfRUaEeTQbFx16%3D%2Bi5cvuzunB0f3rbQaeP312COQ%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/elasticsearch/CAHj2c4A6M4LfRUaEeTQbFx16%3D%2Bi5cvuzunB0f3rbQaeP312COQ%40mail.gmail.com?utm_medium=email&utm_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 elasticsearc...@googlegroups.com <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQD0j7gqvO1yZQ48mOyCef1ijoRBqgTN%3D_chcYn_AYy00A%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQD0j7gqvO1yZQ48mOyCef1ijoRBqgTN%3D_chcYn_AYy00A%40mail.gmail.com?utm_medium=email&utm_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 elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/CAHj2c4Catt84uQTY9xJEQGggE6o5gU9Q5uQ%3DnKQD9Bp3T%3D%3Dfmg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/elasticsearch/CAHj2c4Catt84uQTY9xJEQGggE6o5gU9Q5uQ%3DnKQD9Bp3T%3D%3Dfmg%40mail.gmail.com?utm_medium=email&utm_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/18588a3f-7448-46d0-ac3c-2fcabb760a05%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
