apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amol Kekre <a...@datatorrent.com>
Subject Re: [DISCUSS] Tweets from ApacheApex handle
Date Thu, 02 Feb 2017 18:31:55 GMT
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 far
there are two proposals

1. Only do release tweets, and do retweet of tweets on individual handle by
requesting PMC on dev@; no special consideration to committers
2. Have a more open policy on original tweets, and in addition retweet of
tweets on individual handle by request PMC on dev@; take up committer's
request as semi-binding.

In #1, the release-tweets are clear, so nothing else go through. In #2 PMC
member can do a trust-but-verify that the tweet is relevant to Apex; which
makes is semi-binding, not binding.


On Wed, Feb 1, 2017 at 7:34 PM, Thomas Weise <thw@apache.org> wrote:

> 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 responsibilities.
> What gets posted on the handle should be evaluated with ASF hat on.
> I also think that direct tweets (read on for retweets) should be restricted
> to official PMC communication (releases etc.). All other tweets should come
> from individual handles. I like the idea of retweet suggestions on the dev@
> list.
> Thomas
> On Wed, Feb 1, 2017 at 4:43 PM, Amol Kekre <amol@datatorrent.com> wrote:
> > 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
> > help out. In essence we treat tweet same as code. I would expect
> committers
> > to ensure that the tweet is related to Apex, I believe that will more or
> > less remain true.
> >
> > Aside from this, I think the release-manager should be expected to post
> > release tweets on ApacheApex handle.
> >
> > Thoughts?
> >
> > Thks
> > Amol
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message