> Is it somehow possible to be a "member" of this account to indicate that
> we have PMC status, or is that not possible within the LinkedIn
> membership/permissions model?

Yes, Arrow Committers and PMC Members may wish to add Apache Arrow to the
Experience section of their LinkedIn profiles.

To do this you must fill in three required fields:
1 - position
2 - month of start date
3 - year of start date

If you wish to do this, I suggest filling the position field with
"Committer", "PMC Member", or "PMC Chair" (whichever is appropriate) and
filling the start date according to when your membership was announced on
the dev mailing list. In the case of PMC Members or Chairs, you can add
multiple entries (some with end dates) to show your different positions
over time.

Those who add Apache Arrow to the Experience section of their LinkedIn
profiles will appear in the list of people affiliated with Apache Arrow at
https://www.linkedin.com/company/apache-arrow/people/.

I intend to occasionally check the list of people in that list to ensure no
one is misrepresenting themself. LinkedIn allows company admins to report
such misrepresentations [10].

Thank you,
Ian

[10] https://www.linkedin.com/help/linkedin/answer/a540867

On Fri, May 24, 2024 at 12:35 PM Antoine Pitrou <anto...@python.org> wrote:

>
> Is it somehow possible to be a "member" of this account to indicate that
> we have PMC status, or is that not possible within the LinkedIn
> membership/permissions model?
>
>
>
> Le 24/05/2024 à 18:04, Ian Cook a écrit :
> > Following the discussion [1] earlier this year about the status of the
> > Apache Arrow Twitter / X account [2], I have seen several news stories
> > citing declines in use of X and increases in use of LinkedIn (for example
> > [3]). Anecdotally I have seen that the types of conversations about open
> > source data technologies that in the past would have taken place on
> Twitter
> > are now often taking place on Linkedin.
> >
> > Many other ASF projects now have LinkedIn pages ([4][5][6][7] to name a
> > few). LinkedIn does not provide a type of account or page specifically
> for
> > open source projects, but the norm among other ASF projects is to use
> > LinkedIn company pages. It appears that a company page is the only
> suitable
> > type of LinkedIn page for this purpose.
> >
> > After reviewing the ASF best practices for project social media accounts
> > [8], I created a LinkedIn company page for Apache Arrow [9]. I configured
> > the page so that the hyphen in the URL is optional; the
> > unhyphenated version redirects to the hyphenated version.
> >
> > Permissions for LinkedIn company pages are managed by assigning roles for
> > the page to one or more LinkedIn user accounts. There are no credentials
> to
> > be shared. I assigned Raúl Cumplido's LinkedIn account as superadmin user
> > for this page. Raúl is a member of the PMC and is the person who
> currently
> > manages our X account. My LinkedIn account is secure and I have verified
> > with Raúl that his LinkedIn account is secure (strong password used, MFA
> > enabled).
> >
> > As discussed in [1], this page could be used to cross-post the same
> content
> > that is currently being posted to X. For now this can be done manually;
> > perhaps later we can use a syndication tool. This page also gives
> LinkedIn
> > users the ability to tag "@Apache Arrow" in their LinkedIn posts,
> comments,
> > and articles.
> >
> > I invite further discussion on the use of this LinkedIn page.
> >
> > Thank you,
> > Ian
> >
> > [1] https://lists.apache.org/thread/nyoq9t114t2ko8f3jflzn9dzcsljvptq
> > [2] https://x.com/ApacheArrow
> > [3]
> >
> https://techcrunch.com/2024/03/28/linkedin-targets-users-caught-between-tiktok-and-twitter-world-games-videos/
> > [4] https://www.linkedin.com/company/apacheiceberg/
> > [5] https://www.linkedin.com/company/apache-hudi/
> > [6] https://www.linkedin.com/company/apachespark/
> > [7] https://www.linkedin.com/company/doris-apache/
> > [8] https://www.apache.org/foundation/marks/socialmedia
> > [9] https://www.linkedin.com/company/apache-arrow
> >
>

Reply via email to