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 < erickramire...@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 <meli...@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> >> >
