- From: AJ Christensen <
>
- To: "
" <
>
- Subject: [chef] Re: Re: Re: Re: Re: What if we killed the mailing list altogether...
- Date: Thu, 27 Nov 2014 07:29:29 +1300
JK's analysis here of Discourse here is on-point. I'd consider
supporting an RFC that detailed these as benefits over GGRo for a
future-switch.
The badge system in discourse is pretty sweet, if you contribute
different types of topics, replies, etc, you can gamify that shit.
Trust your users, whatever. Fits with the LT stuff we're pushing.
Here's some info re: Discourse' anti-spam:
-- User trust levels:
https://meta.discourse.org/t/what-do-user-trust-levels-do/4924
--
https://meta.discourse.org/t/what-about-the-spam-problem/2724/8
--
http://samsaffron.com/archive/2011/10/04/Spam+bacon+sausage+and+blog+spam+a+JavaScript+approach
My prime considerations are around: anti-spam, moderation, muting. I'd
like to be able to banhammer users so I don't see 'em (mute) or their
unfortunately curiosity-inspiring troll-threads. I expect that this
behavior could be channeled into more effective thread management or
moderation, but I'd settle for an individual mute for now :)
--aj
On Thu, Nov 27, 2014 at 6:56 AM, John Keiser
<
>
wrote:
>
Let's rephrase then :)
>
>
> We're moving to Google Groups shortly, that's absolutely the right
>
> decision. Is it worth moving to Discourse later?
>
>
>
Discourse has mailing list support, according to its website, so we need not
>
lose anything at all by using it. I've used Google Groups before, but not
>
so much Discourse. Here's the relevant advantages over Google Groups I see
>
just looking at the feature list:
>
>
Markdown support, with consistent, rich formatting
>
Embeddable on the Chef website, so new visitors can feel they are still
>
under the same roof
>
Single Sign-On
>
Sticky posts
>
@ summoning
>
Trust system to identify people who consistently help
>
Muting, flagging, etc.
>
>
I haven't figured out any disadvantages here--if there are any Discourse
>
features that make it worse, or if there are any Groups features that
>
Discourse is missing or does worse at. Help me out?
>
>
--John
>
>
On Wed, Nov 26, 2014 at 8:13 AM, Adam Jacob
>
<
>
>
wrote:
>
>
>
> I'm not blocking groups :) I was just asking. :)
>
>
>
> On Nov 26, 2014 8:09 AM, "Brian Hatfield"
>
> <
>
>
> wrote:
>
>>
>
>> I'm also perfectly happy with a standard mailing list. In particular,
>
>> other open-source projects that I care about also have mailing lists in a
>
>> similar form, which makes it easy for me to filter and follow projects
>
>> that
>
>> I am interested in.
>
>>
>
>> In my opinion, there is a surprising difference between
>
>> tools-that-send-emails and an honest-to-goodness mailing list.
>
>>
>
>> Your project requirements sound sane, however. Google groups is a common
>
>> answer, as mentioned earlier; in fact, I thought we were already using
>
>> Google groups because I wasn't paying attention.
>
>>
>
>> On Wed, Nov 26, 2014 at 11:04 AM, John de la Garza
>
>> <
>
>
>> wrote:
>
>>>
>
>>> I'm a fan of keeping the mailing list.
>
>>>
>
>>> On Wed, Nov 26, 2014 at 10:19 AM, Nathen Harvey
>
>>> <
>
>
>>> wrote:
>
>>> >
>
>>> >
>
>>> > On Tue, Nov 25, 2014 at 7:39 PM, Adam Jacob
>
>>> > <
>
>
>>> > wrote:
>
>>> >>
>
>>> >> And just moved all of our conversation over to Discourse?
>
>>> >>
>
>>> >
>
>>> > If only because it's questions like this that have killed the
>
>>> > migration in
>
>>> > the past. We get into analysis paralysis about which tool should we
>
>>> > migrate
>
>>> > to. We analyze the pros and cons of each. Try some of them out and
>
>>> > then
>
>>> > give up on the project because, while a priority, it doesn't have a
>
>>> > high
>
>>> > enough priority to maintain our attention span.
>
>>> >
>
>>> > Our goals in this project include:
>
>>> >
>
>>> > * Migrate off of an in-house managed mail list system
>
>>> > * Provide "mail in" and "mail out" on a reliable, easy-to-use platform
>
>>> > * Provide an archive of previous mail list content
>
>>> >
>
>>> > I'm all for debate and looking at alternate solutions but this will
>
>>> > prolong
>
>>> > the migration process and may even stall it out completely again.
>
>>> >
>
>>> > There is a proposal on StackExchange [0] for a Chef group. As of this
>
>>> > morning, it still needs 30 more questions with a score of 10 or more
>
>>> > to move
>
>>> > on to the next phase. Help get behind that if you think it's
>
>>> > appropriate.
>
>>> >
>
>>> > Google groups, with all of it's challenges, is stable, reliable, and
>
>>> > easy-to-use.
>
>>> >
>
>>> > My vote is to move forward with the approved RFC [1] and I think we're
>
>>> > on
>
>>> > track to complete that work by the end of the calendar year.
>
>>> >
>
>>> >
>
>>> >
>
>>> >>
>
>>> >> http://www.discourse.org/
>
>>> >>
>
>>> >> Adam
>
>>> >
>
>>> >
>
>>> > [0]: http://area51.stackexchange.com/proposals/77609/chef
>
>>> > [1]:
>
>>> >
>
>>> > https://github.com/opscode/chef-rfc/blob/master/rfc028-mailing-list-migration.md
>
>>> >
>
>>
>
>>
>
- [chef] Re: Re: What if we killed the mailing list altogether..., (continued)
Archive powered by MHonArc 2.6.16.