Raku
There's no effective way to communicate something to all people with commit bits in the different Raku repos and organizations
Say we need to deploy something across all the rakuverse: the 5 or 6 organizations in them, and also to the individual persons which have the commit bit in repos and are not included in any team
Maybe we should establish as a policy not allowing that, but still.
An example has been changing Perl 6 into Raku (a change that, BTW, is still ongoing, at least in the community modules). Or contributing to the advent calendar. Or changes in the rakuverse (like deprecation notices for META6.json). Or, as is the case that has actually triggered it, the need to use authenticated pulls in Docker and how Raku as organization is going to deal with that (hint: we still don't know, but when we know, we'll need to tell everyone).
Other examples would be outreach activities. Or need to vote for a new RSC member. There are many use cases.
Currently, there's no way of doing it. None of the current channels are attended in big enough quantities to actually reach everyone. #raku-dev might be the closest thing there is, but an announcement might get lost within the whole conversation, and if people are not in there, they will not get notified.
So, I think we need a mandatory channel (that is, if you have the commit bit somewhere, you need to be there) to say things like "Please contact this and that to deploy this or that to the repositories you work with". I think it's much better if it's an announcement-only channel, and if just a few people (or maybe just the RSC or core team)...
Come to think of it, I don't even know if the core team has that kind of thing, other than issues in the core team repositories
... have the privs to post in it. What do you think?
JJ knows about this issue already, but another case has come up with some surprising confusion about what the left and right hands are doing:
https://www.nntp.perl.org/group/perl.perl6.users/2021/03/msg9797.html
Following the discussion on the mailing list, I'd like to leave very brief notes of my vision of solution for this issue.
-
My proposal is to start an official blog at news.raku.org.
-
The blog would be under full control of RSC.
-
It must serve as the official channel of posting news about new compiler and/or VM releases, organizational events, articles, and any other activities important for Raku development.
I don't focus particularly on Rakudo and MoarVM in this item in case more compilers are developed in the future.
-
Anyone can request to post information they consider relevant and important for Raku development. It could be announcement of new projects, events, articles, etc. It would be up to RSC or chosen representative to decide if the information worth posting in the official blog.
-
The posts can be duplicated in a mailing list. In this case the mailing list is a subsidiary channel, similar to RSS/Atom feeds.
If no objections posted to this proposal, I will try to make a PR out of it as soon as I get a spare hour for this. Otherwise if somebody overtake me on this task I wouldn't mind whatsoever. :)
One thing I'm seeing repeatedly in recent threads is the use of the term "official" as in "official channel", and in Raku nee' Perl 6 we always tried to avoid designating things as "official" in the sense of being "primary" or "most blessed".
I'm fine if it's a "main channel", but "official" implies way too much top-down structure, especially when coupled with "anyone can request" in the fourth point (which implies an "approval" process for someone to be able to communicate).
If you want disparate projects to be aware of what others are doing, it needs to be open and easy to make it known, and not regulated or filtered through another group (unless we have a large panel of volunteer moderators just willing to do this).
As for documentation, it's entirely reasonable for there to be multiple documentation sites and projects, each with different purposes and targets. In the book world, having multiple presentations (books) about a language or programming environment is seen as healthy for the ecosystem, not an unwise duplication of resources.
Pm
On Sun, Mar 14, 2021 at 02:34:22PM -0700, Vadim Belman wrote:
Following the discussion on the mailing list, I'd like to leave very brief notes of my vision of solution for this issue.
- My proposal is to start an official blog at news.raku.org.
- The blog would be under full control of RSC.
- It must serve as the official channel of posting news about new compiler and/or VM releases. I don't focus on Rakudo and MoarVM in case more compilers are developed in the future.
- Anyone can request to post information they consider relevant and important for Raku development. It could be announcement of new projects, events, articles, etc. It would be up to RSC or chosen representative to decide if the information worth posting in the official blog.
- The posts can be duplicated in a mailing list. In this case the mailing list is a subsidiary channel, similar to RSS/Atom feeds.
If no objections posted to this proposal, I will try to make a PR out of it as soon as I get a spare hour for this. Otherwise if somebody overtake me on this task I wouldn't mind whatsoever. :)
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/Raku/problem-solving/issues/246#issuecomment-798984037
We have several options, none of which is great. Mailing lists (harder to manage now that we're not part of the p5 devops ecosystem), blogs, the weekly, the raku web site, the wikis...
Regarding the documentation item mentioned by doomvox, I am trying to get all the ongoing items listed under the wiki at https://github.com/Raku/doc/wiki. (And in putting that together have already found a bunch of items in RSC meeting minutes that I personally wasn't aware of).
