On Mon, Jan 1, 2018 at 7:51 PM, Dan Book <grinnz@gmail.com> wrote: > Unlike most normal businesses, we don't have a way of observing what our > 'customers' do, at least not in a straightforward manner, other than > looking at what's on CPAN and at end-user applications that actually get > popular. So while the calls for involving the greater community and less > isolation in the mailing list are great, they don't mean much unless > someone has ideas on how this can be done. blogs.perl.org and similar > platforms are a start, but the core issue is that the users of Perl are > highly disjointed across various disciplines and practices which do not all > (or even mostly) sit in the same community forum. > I propose that this mailing list does not exist in isolation, but is very much public, and serves as a platform where volunteers from the greater community can get involved. If someone does not volunteer to get involved, you can't effectively reach them anyway. And spreading the involvement just means making it less accessible. I'm not a porter, yet I've been subscribed to this list for years, primarily to keep up with the development, occasionally to speak my mind. This is where I go in order to learn what is going on. This is where I go to give feedback. Having it all in one place is convenient. If these discussions are spread across blogs.perl.org and similar platforms, I'll not be able to keep up. The problem is not isolation. If there is a problem with involvement, it is that people have not been educated as to how to get involved. EirikThread Previous | Thread Next