Hi Matthew; thanks for your mail. Mailman (our mailing list manager)
doesn't support ad hoc sub-lists, so when we've got a thread that a
subset of subscribers are likely to want to discuss at length, we push
it to a GitHub issue: it keeps the discussion public but opt-in (GitHub
will auto-notify anyone who's previously commented on the thread and/or
anyone who chooses to subscribe), while reducing traffic on the list for
people who *aren't* interested in the details. If and when there's a
resolution to forward to the Steering Committee, a poll, or a concrete
proposal (e.g., changing the tools we use for building lessons), someone
can bring a short summary back to the main list. It's not perfect, but
it's worked pretty well so far.
Thanks,
Greg
p.s. if anyone wants to *make* it perfect (or at least better), a script
to take a selected thread from the Mailman archive and re-post messages
in order as comments on a GitHub issue would be very useful - so much so
that I will personally send a Software Carpentry t-shirt to whoever
builds it. For obvious reasons, though, please reply to me directly,
rather than to this list :-)
On 2016-05-06 11:47 AM, Matthew Brett wrote:
On Fri, May 6, 2016 at 11:40 AM, Greg Wilson
<[email protected]> wrote:
+1
I would ask that this discussion be moved to github.
thank you,
--titus
Why do you think the discussion should be moved to github? It's
certainly a tough discussion, but it seems like a legitimate one to
have on the discussion mailing list.
Best,
Matthew
--
Dr Greg Wilson
Director of Instructor Training
Software Carpentry Foundation
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
