Re: A More Welcoming Community

From: Kristen Shaker (kristen_at_[hidden])
Date: 2024-09-24 20:58:40

The emails aren't meant to be spammy. They're supposed to help orient
people who are new to a service or a community and encourage them to
engage. You provide valuable information about what your service/community
is, what it stands for, where the important resources are, etc. You do it
in a sequence so no one gets one monolithic welcome email that is hard to
digest. We're creating new logos and engaging more on social media which
are both strategies pulled from a marketing playbook.

Anyway, it was just a suggestion. Feel free to ignore it.

On Tue, Sep 24, 2024 at 3:32 PM Andrzej Krzemienski <akrzemi1_at_[hidden]>
wrote:

>
>
> wt., 24 wrz 2024 o 17:32 Kristen Shaker via Boost <boost_at_[hidden]>
> napisał(a):
>
>> Agreed with the sentiment that new joiners should be added to what in the
>> marketing world is referred to as a "Welcome Sequence." 3 - 4 emails
>> designed to engage new users, provide them with context about what a
>> product/service is during a time when they are most receptive to engaging.
>>
>
> I don't know about that. It depends on what type of community we want to
> be.
> I always thought of Boost as a place where people of honest motivation
> reflect, discuss, and exchange ideas.
> Giving the impression of marketing-like influencing might put off people
> who value the atmosphere of honesty.
> I personally would hate to receive a bunch of "spam" email, only because I
> subscribed to a group for technical content.
>
> Regards,
> &rzej;
>
> [BTW, remember about the no-top-posting policy.]
>
>
>>
>> On Mon, Sep 23, 2024 at 3:09 PM Marshall Clow via Boost <
>> boost_at_[hidden]> wrote:
>>
>> > On Sep 23, 2024, at 12:01 PM, Peter Dimov via Boost <
>> boost_at_[hidden]>
>> > wrote:
>> > >
>> > > Vinnie Falco wrote:
>> > >> You said that it was inconvenient to report a bug, and I agree. You
>> > have to sign
>> > >> up for the list, wait for the email verification, then post by
>> sending
>> > an email,
>> > >> and then wait for the moderator to approve it. And then you have to
>> > wait for
>> > >> the replies.
>> > >>
>> > >> Here is an idea: we can present a web page "report an issue" which
>> > combines
>> > >> the process of posting a message and signing up for the mailing list.
>> > We can
>> > >> use OAuth, to also allow for Google or GitHub credentials to be used
>> for
>> > >> skipping the verification step. This would streamline the process.
>> The
>> > counter-
>> > >> argument is that these users should be using GitHub issues. There are
>> > >> advantages to each method. Through the mailing list, we get more
>> > activity and
>> > >> a consolidated view of needs. Through GitHub we get better technology
>> > and
>> > >> global visibility.
>> > >
>> > > Our current procedure for reporting issues in general is (1) users
>> open
>> > issues in
>> > > boostorg/boost, (2) Marshall occasionally looks at them and moves
>> them to
>> > > the appropriate repo.
>> >
>> > I would prefer saying “If Marshall can figure out where they should go,
>> > then he moves them to the appropriate repo”
>> >
>> > But that could be considered a distinction w/o a difference.
>> >
>> > > This can probably be improved. :-)
>> >
>> > Oh, yeah.
>> >
>> > — Marshall
>> >
>> >
>> >
>> > _______________________________________________
>> > Unsubscribe & other changes:
>> > http://lists.boost.org/mailman/listinfo.cgi/boost
>> >
>>
>> _______________________________________________
>> Unsubscribe & other changes:
>> http://lists.boost.org/mailman/listinfo.cgi/boost
>>
>