[DISCUSS] List Apache Cassandra as a "company" on LinkedIn

[Erick Ramirez <er...@apache.org>]

I wanted to bring this up again from Benjamin's original thread
<https://lists.apache.org/thread/p1ql8bs51bjvj50c3535rxkp2bn051fk>. I agree
with Melissa and I really think there's a lot of value in creating a
company page on LinkedIn in addition to the "C* Community" group. There is
a bigger potential for us from a marketing perspective to promote Cassandra
to a wider audience with a company page. For what it's worth, Apache Pulsar
<https://www.linkedin.com/company/apachepulsar/> already does this. Off the
top of my head, here are some notable points:

LinkedIn company page:

   - ✅ users can "follow" the page and see posts in their feed
   - ✅ users can @-tag Cassandra in their own posts
   - ✅ reach a wider network on LinkedIn
   - ✅ promote new contributors publicly

LinkedIn group:

   - ✅ great for building a community
   - ✅ deeper discussion on topics
   - 👎 users need to join the group
   - 👎 posts are only visible to members

Is there an appetite from the project to pursue this? Cheers!

On Thu, 10 Mar 2022 at 06:06, Melissa Logan <me...@constantia.io> wrote:

> I agree there should be an official LinkedIn page for the project hosted
> by the community. It's an easy way for people to stay current.
>
> If the goal of the new LinkedIn page is to publicly and broadly share what
> the Cassandra community is doing, one solution would be to change the new
> Cassandra page from a "group" page to a "company" page.
>
> Company pages show all posts publicly by default, and admins don't have to
> manage requests to join. Anyone can "follow" the page and see/share the
> posts -- while only allowing community admins to publish. This would also
> require less care and feeding from community admins. (What I don't know if
> it's easy to "convert" a group page to company or if it requires starting
> from scratch.)
>
> Then, admins of the existing "group" page could repost any/all items from
> the community page to keep people informed.
>
> This solution could help both pages achieve their goals of spreading the
> word about Cassandra.
>
> --
> Melissa Logan (she/her)
> Principal, Constantia.io
> LinkedIn <https://www.linkedin.com/in/mklogan/> | Twitter
> <https://twitter.com/Melissa_B2B>
>

Re: [DISCUSS] List Apache Cassandra as a "company" on LinkedIn

[Benjamin Lerer <b....@gmail.com>]

I created a company page for Apache Cassandra with the same admin as the
group.
I will update the page over the coming days to give it a nicer look. :-)

Le mer. 30 mars 2022 à 23:46, Patrick McFadin <pm...@gmail.com> a écrit :

> Oh and +1 to the idea of making Apache Cassandra a company on LinkedIn.
> Same energy as the Twitter handle. Outgoing updates from the project.
>
> On Wed, Mar 30, 2022 at 2:41 PM Patrick McFadin <pm...@gmail.com>
> wrote:
>
>> I agree that is a problem. In the past, I have tried to make these as
>> inclusive as possible by offering multiple time zones, recording every
>> meeting, and posting it on YouTube with an email sent to dev@. What we
>> can't substitute in a mailing list is the energy that comes from
>> brainstorming, which is kind of a feature of people interested in this sort
>> of thing for the project. Just like meeting once or twice a year at
>> ApacheCon. It's part of an overall package of community vibrancy and none
>> of it is exclusive.
>>
>> One thing that occurred to me is that everything is getting dumped on dev@.
>> Is it time for a marketing@ list for Cassandra?
>>
>> Patrick
>>
>> On Wed, Mar 30, 2022 at 12:00 PM Eric Evans <ee...@apache.org> wrote:
>>
>>>
>>>
>>> On Wed, Mar 30, 2022 at 3:35 AM Benjamin Lerer <bl...@apache.org>
>>> wrote:
>>>
>>>> Thank Erick for raising the discussion.
>>>> My apologies for not responding before. The original thread raised
>>>> several questions for me and I needed time to think about them.
>>>> One question is the Linkedin Company vs Group one. I must admit that it
>>>> makes sense but the whole story made me realize my lack of understanding of
>>>> how Linkedin works and wanted to explore that more deeply than I did before
>>>> creating the group.
>>>> Another thing that the thread made me realize is that there are several
>>>> people interested in being involved in C* marketing/Public Relations and
>>>> that we probably need to do the things in a more mature and open way.
>>>> Partick and I would like to organize a contributor meeting focused on
>>>> Apache Cassandra marketing to give a chance to everybody to join and
>>>> discuss how we could do things better if people are interested.
>>>> I feel that it would help us to evolve in this area
>>>>
>>>
>>> Please bear in mind that contributor meetings like these are exclusive
>>> by nature; There is no time suitable for every timezone, not everyone has
>>> equal connectivity, and those who don't natively speak English might
>>> struggle to keep pace in real time (to name just a few reasons).  This is
>>> probably why the ASF is so adamant about the use of email.
>>>
>>> --
>>> Eric Evans
>>> eevans@apache.org
>>>
>>

Re: [DISCUSS] List Apache Cassandra as a "company" on LinkedIn

[Patrick McFadin <pm...@gmail.com>]

Oh and +1 to the idea of making Apache Cassandra a company on LinkedIn.
Same energy as the Twitter handle. Outgoing updates from the project.

On Wed, Mar 30, 2022 at 2:41 PM Patrick McFadin <pm...@gmail.com> wrote:

> I agree that is a problem. In the past, I have tried to make these as
> inclusive as possible by offering multiple time zones, recording every
> meeting, and posting it on YouTube with an email sent to dev@. What we
> can't substitute in a mailing list is the energy that comes from
> brainstorming, which is kind of a feature of people interested in this sort
> of thing for the project. Just like meeting once or twice a year at
> ApacheCon. It's part of an overall package of community vibrancy and none
> of it is exclusive.
>
> One thing that occurred to me is that everything is getting dumped on dev@.
> Is it time for a marketing@ list for Cassandra?
>
> Patrick
>
> On Wed, Mar 30, 2022 at 12:00 PM Eric Evans <ee...@apache.org> wrote:
>
>>
>>
>> On Wed, Mar 30, 2022 at 3:35 AM Benjamin Lerer <bl...@apache.org> wrote:
>>
>>> Thank Erick for raising the discussion.
>>> My apologies for not responding before. The original thread raised
>>> several questions for me and I needed time to think about them.
>>> One question is the Linkedin Company vs Group one. I must admit that it
>>> makes sense but the whole story made me realize my lack of understanding of
>>> how Linkedin works and wanted to explore that more deeply than I did before
>>> creating the group.
>>> Another thing that the thread made me realize is that there are several
>>> people interested in being involved in C* marketing/Public Relations and
>>> that we probably need to do the things in a more mature and open way.
>>> Partick and I would like to organize a contributor meeting focused on
>>> Apache Cassandra marketing to give a chance to everybody to join and
>>> discuss how we could do things better if people are interested.
>>> I feel that it would help us to evolve in this area
>>>
>>
>> Please bear in mind that contributor meetings like these are exclusive by
>> nature; There is no time suitable for every timezone, not everyone has
>> equal connectivity, and those who don't natively speak English might
>> struggle to keep pace in real time (to name just a few reasons).  This is
>> probably why the ASF is so adamant about the use of email.
>>
>> --
>> Eric Evans
>> eevans@apache.org
>>
>

Re: [DISCUSS] List Apache Cassandra as a "company" on LinkedIn

[Patrick McFadin <pm...@gmail.com>]

I agree that is a problem. In the past, I have tried to make these as
inclusive as possible by offering multiple time zones, recording every
meeting, and posting it on YouTube with an email sent to dev@. What we
can't substitute in a mailing list is the energy that comes from
brainstorming, which is kind of a feature of people interested in this sort
of thing for the project. Just like meeting once or twice a year at
ApacheCon. It's part of an overall package of community vibrancy and none
of it is exclusive.

One thing that occurred to me is that everything is getting dumped on dev@.
Is it time for a marketing@ list for Cassandra?

Patrick

On Wed, Mar 30, 2022 at 12:00 PM Eric Evans <ee...@apache.org> wrote:

>
>
> On Wed, Mar 30, 2022 at 3:35 AM Benjamin Lerer <bl...@apache.org> wrote:
>
>> Thank Erick for raising the discussion.
>> My apologies for not responding before. The original thread raised
>> several questions for me and I needed time to think about them.
>> One question is the Linkedin Company vs Group one. I must admit that it
>> makes sense but the whole story made me realize my lack of understanding of
>> how Linkedin works and wanted to explore that more deeply than I did before
>> creating the group.
>> Another thing that the thread made me realize is that there are several
>> people interested in being involved in C* marketing/Public Relations and
>> that we probably need to do the things in a more mature and open way.
>> Partick and I would like to organize a contributor meeting focused on
>> Apache Cassandra marketing to give a chance to everybody to join and
>> discuss how we could do things better if people are interested.
>> I feel that it would help us to evolve in this area
>>
>
> Please bear in mind that contributor meetings like these are exclusive by
> nature; There is no time suitable for every timezone, not everyone has
> equal connectivity, and those who don't natively speak English might
> struggle to keep pace in real time (to name just a few reasons).  This is
> probably why the ASF is so adamant about the use of email.
>
> --
> Eric Evans
> eevans@apache.org
>

Re: [DISCUSS] List Apache Cassandra as a "company" on LinkedIn

[Eric Evans <ee...@apache.org>]

On Wed, Mar 30, 2022 at 3:35 AM Benjamin Lerer <bl...@apache.org> wrote:

> Thank Erick for raising the discussion.
> My apologies for not responding before. The original thread raised several
> questions for me and I needed time to think about them.
> One question is the Linkedin Company vs Group one. I must admit that it
> makes sense but the whole story made me realize my lack of understanding of
> how Linkedin works and wanted to explore that more deeply than I did before
> creating the group.
> Another thing that the thread made me realize is that there are several
> people interested in being involved in C* marketing/Public Relations and
> that we probably need to do the things in a more mature and open way.
> Partick and I would like to organize a contributor meeting focused on
> Apache Cassandra marketing to give a chance to everybody to join and
> discuss how we could do things better if people are interested.
> I feel that it would help us to evolve in this area
>

Please bear in mind that contributor meetings like these are exclusive by
nature; There is no time suitable for every timezone, not everyone has
equal connectivity, and those who don't natively speak English might
struggle to keep pace in real time (to name just a few reasons).  This is
probably why the ASF is so adamant about the use of email.

--
Eric Evans
eevans@apache.org

Re: [DISCUSS] List Apache Cassandra as a "company" on LinkedIn

[Benjamin Lerer <bl...@apache.org>]

Thank Erick for raising the discussion.
My apologies for not responding before. The original thread raised several
questions for me and I needed time to think about them.
One question is the Linkedin Company vs Group one. I must admit that it
makes sense but the whole story made me realize my lack of understanding of
how Linkedin works and wanted to explore that more deeply than I did before
creating the group.
Another thing that the thread made me realize is that there are several
people interested in being involved in C* marketing/Public Relations and
that we probably need to do the things in a more mature and open way.
Partick and I would like to organize a contributor meeting focused on
Apache Cassandra marketing to give a chance to everybody to join and
discuss how we could do things better if people are interested.
I feel that it would help us to evolve in this area

Le mer. 30 mars 2022 à 03:01, Paulo Motta <pa...@gmail.com> a
écrit :

> I was unpleasantly surprised to find out that Linkedin group posts are not
> visible outside of the group, which greatly reduces post visibility. I
> originally supported the group creation because I thought the posts would
> be visible outside the group but this doesn't seem to be the case.
>
> The only thing that bothers me about having a company page is that the
> project is not technically a company, but if this is not breaking any
> Linkedin ToS and there is precedence in other Apache projects I think it
> makes sense to create the company page to give more visibility to community
> posts.
>
> I just don't see much value in keeping the group if we decide to create
> the company page, since we may risk duplicating effort and attention. I
> don't think Linkedin is the place for technical discussions since we have
> other forums for that, I see it more as a marketing channel.
>
> Em ter., 29 de mar. de 2022 às 21:41, Erick Ramirez <
> erickramirezau@apache.org> escreveu:
>
>> I wanted to bring this up again from Benjamin's original thread
>> <https://lists.apache.org/thread/p1ql8bs51bjvj50c3535rxkp2bn051fk>. I
>> agree with Melissa and I really think there's a lot of value in creating a
>> company page on LinkedIn in addition to the "C* Community" group. There is
>> a bigger potential for us from a marketing perspective to promote Cassandra
>> to a wider audience with a company page. For what it's worth, Apache
>> Pulsar <https://www.linkedin.com/company/apachepulsar/> already does
>> this. Off the top of my head, here are some notable points:
>>
>> LinkedIn company page:
>>
>>    - ✅ users can "follow" the page and see posts in their feed
>>    - ✅ users can @-tag Cassandra in their own posts
>>    - ✅ reach a wider network on LinkedIn
>>    - ✅ promote new contributors publicly
>>
>> LinkedIn group:
>>
>>    - ✅ great for building a community
>>    - ✅ deeper discussion on topics
>>    - 👎 users need to join the group
>>    - 👎 posts are only visible to members
>>
>> Is there an appetite from the project to pursue this? Cheers!
>>
>> On Thu, 10 Mar 2022 at 06:06, Melissa Logan <me...@constantia.io>
>> wrote:
>>
>>> I agree there should be an official LinkedIn page for the project hosted
>>> by the community. It's an easy way for people to stay current.
>>>
>>> If the goal of the new LinkedIn page is to publicly and broadly share
>>> what the Cassandra community is doing, one solution would be to change the
>>> new Cassandra page from a "group" page to a "company" page.
>>>
>>> Company pages show all posts publicly by default, and admins don't have
>>> to manage requests to join. Anyone can "follow" the page and see/share the
>>> posts -- while only allowing community admins to publish. This would also
>>> require less care and feeding from community admins. (What I don't know if
>>> it's easy to "convert" a group page to company or if it requires starting
>>> from scratch.)
>>>
>>> Then, admins of the existing "group" page could repost any/all items
>>> from the community page to keep people informed.
>>>
>>> This solution could help both pages achieve their goals of spreading the
>>> word about Cassandra.
>>>
>>> --
>>> Melissa Logan (she/her)
>>> Principal, Constantia.io
>>> LinkedIn <https://www.linkedin.com/in/mklogan/> | Twitter
>>> <https://twitter.com/Melissa_B2B>
>>>
>>

Re: [DISCUSS] List Apache Cassandra as a "company" on LinkedIn

[Paulo Motta <pa...@gmail.com>]

I was unpleasantly surprised to find out that Linkedin group posts are not
visible outside of the group, which greatly reduces post visibility. I
originally supported the group creation because I thought the posts would
be visible outside the group but this doesn't seem to be the case.

The only thing that bothers me about having a company page is that the
project is not technically a company, but if this is not breaking any
Linkedin ToS and there is precedence in other Apache projects I think it
makes sense to create the company page to give more visibility to community
posts.

I just don't see much value in keeping the group if we decide to create the
company page, since we may risk duplicating effort and attention. I don't
think Linkedin is the place for technical discussions since we have other
forums for that, I see it more as a marketing channel.

Em ter., 29 de mar. de 2022 às 21:41, Erick Ramirez <
erickramirezau@apache.org> escreveu:

> I wanted to bring this up again from Benjamin's original thread
> <https://lists.apache.org/thread/p1ql8bs51bjvj50c3535rxkp2bn051fk>. I
> agree with Melissa and I really think there's a lot of value in creating a
> company page on LinkedIn in addition to the "C* Community" group. There is
> a bigger potential for us from a marketing perspective to promote Cassandra
> to a wider audience with a company page. For what it's worth, Apache
> Pulsar <https://www.linkedin.com/company/apachepulsar/> already does
> this. Off the top of my head, here are some notable points:
>
> LinkedIn company page:
>
>    - ✅ users can "follow" the page and see posts in their feed
>    - ✅ users can @-tag Cassandra in their own posts
>    - ✅ reach a wider network on LinkedIn
>    - ✅ promote new contributors publicly
>
> LinkedIn group:
>
>    - ✅ great for building a community
>    - ✅ deeper discussion on topics
>    - 👎 users need to join the group
>    - 👎 posts are only visible to members
>
> Is there an appetite from the project to pursue this? Cheers!
>
> On Thu, 10 Mar 2022 at 06:06, Melissa Logan <me...@constantia.io> wrote:
>
>> I agree there should be an official LinkedIn page for the project hosted
>> by the community. It's an easy way for people to stay current.
>>
>> If the goal of the new LinkedIn page is to publicly and broadly share
>> what the Cassandra community is doing, one solution would be to change the
>> new Cassandra page from a "group" page to a "company" page.
>>
>> Company pages show all posts publicly by default, and admins don't have
>> to manage requests to join. Anyone can "follow" the page and see/share the
>> posts -- while only allowing community admins to publish. This would also
>> require less care and feeding from community admins. (What I don't know if
>> it's easy to "convert" a group page to company or if it requires starting
>> from scratch.)
>>
>> Then, admins of the existing "group" page could repost any/all items from
>> the community page to keep people informed.
>>
>> This solution could help both pages achieve their goals of spreading the
>> word about Cassandra.
>>
>> --
>> Melissa Logan (she/her)
>> Principal, Constantia.io
>> LinkedIn <https://www.linkedin.com/in/mklogan/> | Twitter
>> <https://twitter.com/Melissa_B2B>
>>
>