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 P
+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 ha
+1 to option 1
-Robert Middleton
On Wed, Dec 29, 2021 at 2:33 PM Christian Grobmeier
wrote:
>
> Hello,
>
> as discussed in another thread, this is a vote about the future of log4j 1.
> This vote stays open for the usual 72h.
> Options are explained below.
>
> You can vote for:
>
> [ ] +1, Opti
[X] +1, Option 1
Gary
On Wed, Dec 29, 2021 at 2:33 PM Christian Grobmeier
wrote:
> Hello,
>
> as discussed in another thread, this is a vote about the future of log4j
> 1. This vote stays open for the usual 72h.
> Options are explained below.
>
> You can vote for:
>
> [ ] +1, Option 1
> [ ]
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 privat
