On 08/26/2014 05:42 PM, Kevin Fenzi wrote:
On Tue, 26 Aug 2014 16:46:40 +0200
Honza Horak <hhorak@xxxxxxxxxx> wrote:
...snip...
I'm not against each group doing a summary, but as noted by Josh,
sometimes the summaries are very repetitive ( ...still working on
implemeting roles... etc)
List of proposed MLs to send this summary to:
server@xxxxxxxxxxxxxxxxxxxxxxx
desktop@xxxxxxxxxxxxxxxxxxxxxxx
cloud@xxxxxxxxxxxxxxxxxxxxxxx
env-and-stacks@xxxxxxxxxxxxxxxxxxxxxxx
devel@xxxxxxxxxxxxxxxxxxxxxxx
This is turning into my new pet peeve. ;)
Cross posting to bunches of lists is not a good idea, IMHO.
* It means the person posting the summary has to be subscribed to every
single list they are sending to.
* It means if anyone hits reply to all they have to be subscribed to
every single list or deal with rejections/bounces/moderation.
I think the best thing would be to mail just one list: devel.
All right, I see the point, cross posting does not seem to be very
useful, devel@ or meetingminutes@ seem to be more appropriate way.
However, that's actually what we do already and I feel like it does not
work very well. People need to pay attention to catch the meeting
minutes they care about and since there is no summary of what is
happening beyond meetings (on the group's mailing list or even any place
else), it is almost impossible to stay tuned for non-members.
Failing that, I think the best way we can do cross posting right now is
for people to send seperate copies of an email to each list they want
to post to, follow discussion on all those lists, and then do another
sum up post if there's important feedback from only one list.
Just going back to the original idea -- my goal in the first place was
to have a simple way for everybody who is interested in what working
groups work on to learn about that quickly. Bringing this message to
other groups directly was supposed to prevent people to forget staying
tuned.
Honza
Comments, ideas or better solutions are welcome as usually, but I
might be offline until Sunday, so do not expect any answers from me
in that time :)
Fair enough.
kevin
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
