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 private list or similar).
For non-release type posts, I think it would make sense for lazy approval type consensus or something along those lines. We could also take a look at what other PMCs do with their social media accounts. — Matt Sicker > On Dec 31, 2021, at 06:57, Volkan Yazıcı <vol...@yazi.ci> wrote: > > +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 <boa...@gmail.com> wrote: >> >> 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, major version releases like 2.x -> 3.x, etc). While the dev list >> remains our official place to discuss development, it would be immensely >> useful for communicating with our wider user base about changes that may be >> more relevant to them than to active developers and contributors. >> >> What do you all think? If we do make accounts, would it make sense to >> divide them into accounts like @log4j, @log4net, @log4cxx, etc., or should >> they be created like a common account for the whole Logging PMC? And which >> social media sites would be best to use here? Twitter is an obvious choice, >> but there could also be other tech-heavy social media sites that would also >> benefit. >> -- >> Matt Sicker >> >>
