On Tue, Apr 25, 2023 at 6:29 PM stan via devel
<devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
(snip)
>
> I've read all the responses to the announcement, and I don't think I've
> seen an architectural analysis.
> What communication requirements does a project like Fedora need?
> What is the theoretical optimal process for each requirement?
> Is there an existing optimal tool for each of those optimal
> processes?
> Are there sub optimal tools that can be used for multiple requirements?
> Is the loss of effectiveness / efficiency of using a sub optimal
> tool worth the reduction in the number of tools?
>
> This is trying to answer the question, "If there was a magic wand we
> could wave, and perfectly satisfy the communication needs of the
> fedora project, what would that look like?" And, "How would we get
> from here to there?"
+1 to this. I am mostly in camp "grumpy old man doesn't want to use
new program", but I think we can (and should!) have a discussion about
what things happen on the "devel" list.
Are there things that are currently handled via the "devel" mailing
list that don't necessarily need to be, and for which Discourse might
even be a better tool?
Emails sent to the devel list seem to mostly belong to these categories:
- announcement and discussion of Change Proposals
- announcement and coordination of breaking changes (like soname bumps
/ API changes)
- discussion of various RFCs / proposals which might eventually become
Change proposals
- various other announcements (packages {un,}orphaned, packages
{un,}retired, etc.)
- reports (rawhide compose report, rawhide QA report, SPDX conversion
progress, etc.)
- introductions of new packagers seeking sponsors
I don't think moving *everything* to Discourse is a good idea, since
the mailing list is a better *tool* for handling some of these things
- while Discourse might be the better tool for others.
For example (*not serious proposals, just some ideas in an effort to
make this discussion more productive and less black-and-white*):
- Change Proposals could be *announced* on the devel list, but
discussion could happen in a linked topic on Discourse
- announcement and coordination of breaking changes continues to be
handled via the mailing list
- RFCs and maybe-future-Change-Proposals are discussed on Discourse
(maybe with an announcement post on the mailing list)
- orphan/unorphan/retire/unretire announcements stay on the devel list
- reports stay on the devel list (or are moved to a separate "reports"
list that interested parties can subscribe to)
- introductions of new packagers happens in the "Introductions"
category on Discourse (which I believe already exists?)
Yes, most of these examples would be about moving
"discussion-like-things" to discourse while keeping
"announcement-like-things" on the mailing list. That should reduce the
volume of emails on the list dramatically, make it easier for people
to follow, and possibly move actual *discussion* to a tool that was
designed to handle *discussion*. It would also make it very easy to
subscribe to Discourse topics one is interested in, and ignore others.
Just my 2 euro-cents :)
Fabio
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
