In the ticket, @churchyard asks:
Do I assume correctly that the discussion topic will be created by whoever announces the change on devel-announce and a link to it will be included in the announcement email?
If people naturally hit Reply on the announcement email and that reply goes to the devel list, do you plan to try directing the people to the forum or not? I am afraid this could create a discussion that is scattered across two disconnected places.
Which is a good point.
Keeping the tradition of announcing changes on devel-announce is meant to mitigate one of the biggest concerns raised: email comes to you; you don’t have to seek it out. While you can subscribe to get emailed when something is posted here (see Guide to interacting with this site by email), it’s a different interface and people would have to actively subscribe.
Plus, broadcast announcements are well-suited to mailing lists.
But, I don’t want to make the fragmentation problem worse. Possible approaches are:
Idea 1: If discussion starts on devel, gently point people here instead.
Pros: Easy, up front
Cons: Constant work, annoying for everyone, can’t be enforced
Idea 2: Preemptively lock threads so they can’t be replied to
Pros: None really. But a possibility.
Cons: Not even sure how to lock threads in mailman, just know we’ve done it before on rare occasions. Not obvious: locked threads can still be replied to, just won’t get posted, so that’s not great.
Idea 3: Decouple devel-announce from devel, set reply-to to bounce
Pros: Relatively easy, mostly solves problem
Cons: People who are only subscribed to devel will have to change behavior or miss out. Also, breaks easy devel list discussion for other announcements.
Idea 4: Decouple devel-announce from devel, somehow link replies into thread
Pros: Reply to devel-announce remains easy
Cons: Requires writing and running some bridge app. Replies are “write only” from the devel-announce side.
Idea 5: Don’t send anything to devel-announce after all
Cons: Devalues devel-announce instantly. Requires people to change behavior to subscribe here.
Idea 6: Only send abstract to devel-announce
Pros: Easy. Doesn’t require devel-announce or devel-list changes, and still reaches existing subscribers
Cons: Not as useful as getting the whole thing
After thinking about it, my suggestion is the last one — send only an abstract to devel-announce. The devel-announce messages could prominently point to the Discussion thread, and also include instructions on subscribing to #change-proposal, either for all posts and replies or just first posts (the latter would be like subscribing just to (a subset of) devel-announce).
I don’t love this, but it’s kind of a price we pay for trying this one step at a time rather than everything all at once. (If we removed devel and kept just devel-announce, we wouldn’t have this problem.)
Anyone have a better idea?