These are great questions. I figure any PMC member should feel free to post
release related announcements there. For responding to users, I think we can
start with our own accounts and use the shared one for when the PMC wants to
make a shared statement (which can be agreed on through the
+1 (for separate Twitter accounts)
Great initiative!
I would also appreciate a soft instruction list.
* Can any PMC member post?
* Are the posts subject to review by PMC?
* Will we use the account to respond to other Tweets?
On Thu, Dec 30, 2021 at 11:40 PM Matt Sicker wrote:
> We recently
I think thats long overdue and recall we had a component Twitter account for
log4php.
Later today I will check if I can find the passwords.
The component is dormant, but its worth having access shared with the PMC still
https://twitter.com/log4php/
--
The Apache Software Foundation
V.P., Data
+1 for accounts per project
-d
On December 31, 2021 01:02:08 Remko Popma wrote:
I also like this idea and agree with separate accounts for each component.
On Fri, Dec 31, 2021 at 7:48 AM Gary Gregory wrote:
Great idea. I would suggest one account for the each component. I'm not
sure
I also like this idea and agree with separate accounts for each component.
On Fri, Dec 31, 2021 at 7:48 AM Gary Gregory wrote:
> Great idea. I would suggest one account for the each component. I'm not
> sure anyone but the PMC would care about a logging services account.
>
> Gary
>
> On Thu,
Great idea. I would suggest one account for the each component. I'm not
sure anyone but the PMC would care about a logging services account.
Gary
On Thu, Dec 30, 2021, 17:40 Matt Sicker wrote:
> We recently had an idea discussed on a video call about potentially
> starting some Twitter et al.
We recently had an idea discussed on a video call about potentially starting
some Twitter et al. accounts for announcing releases, release candidates, and
larger upcoming changes to subprojects (e.g., changing the minimum major
version of the underlying programming language or build tooling,
