Thomas,
The proposal is for credentials to remain in PMC, and in-effect committers
sending a request to tweet. Here some relevant advice on do's and don'ts
from ASF for social media. I have pasted it as is.
- Feel free to share stories about your project, whether they come from
the
The link that I provided gives context about how projects overall work. I
find that useful to understand before embarking into further discussion.
And I also found some more guidance regarding social media activity:
http://www.apache.org/foundation/marks/socialmedia
My preference is that the
I prefer option 2 at least till there is a critical mass of social activity
and awareness happening outside around apex that we don't need to tweet
actively on the community page.
Thanks
On Thu, Feb 2, 2017 at 10:31 AM, Amol Kekre wrote:
> Thomas,
> The discussion is not
Thomas,
The discussion is not about handle being operated outside PMC. It is
perfectly fine to have handle credentials accessible to only PMC members. I
started this discussion to get Apex community opinion on guidelines on what
gets tweeted. The ASF does not have a formal guideline on twitter. So
Note this is follow-up from a previous discussion on the PMC list.
I think the decision on activity for the ApacheApex handle should be with
the PMC and the handle should be operated by PMC members.
See http://apache.org/foundation/how-it-works.html for more context about
roles and
+1 I strongly agree since the community is growing. As a community, we need
to be able to publish updates and relevant content to followers. All
committers having access to publish tweets makes community inclusive.
Regards,
Ashwin.
On Feb 1, 2017 4:43 PM, "Amol Kekre"
I want to see what the community feels about posting tweets on ApacheApex
handle. My thoughts are that the committers should have the right to post a
tweek on ApacheApex. For contributors and anyone else, we could have a
mechanism where they request it on dev@apex.apache.org and a committer can