Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Difference between revisions of "Talk:Mailing lists"

From FlightGear wiki
Jump to: navigation, search
(Headings: Capital first letter; New section: Bug reports on mailing lists?)
(Moved additional info to main page as references)
 
Line 9: Line 9:
  
 
--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 10:58, 20 April 2015 (EDT)
 
--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 10:58, 20 April 2015 (EDT)
 
== Additional info ==
 
{{FGCquote
 
  |One additional thing to keep in mind is that our flightgear-commitlogs<br/>
 
mailing list has a maximum message size configured to 160Kb.  Messages<br/>
 
larger than this get sent over to the list moderator.  That may be why some<br/>
 
of these messages are delayed.  I mentioned this to Torsten offline and it<br/>
 
sounded like he had some ideas for ensuring that extra long diffs get<br/>
 
trimmed to a reasonable size for a mailing list.
 
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33913347/
 
    |title=<nowiki>Re: [Flightgear-devel] [Flightgear-commitlogs] [FGData] FlightGear
 
data - next generation branch next updated.
 
7b595eca19e1bfb83ae330c02f2eeec5e9c9da58</nowiki>
 
    |author=<nowiki>Curtis Olson</nowiki>
 
    |date=<nowiki>2015-04-19</nowiki>
 
  }}
 
}}
 
 
{{FGCquote
 
  |Both the post-commit-email and<br/>
 
git-multimail scripts have an option for this (hooks.emailmaxlines and<br/>
 
multimailhook.emailMaxLines respectively).  Maybe 10,000 lines would<br/>
 
be a good limit?  The interesting part of the diff might be preceded<br/>
 
by a lot of 'noise', especially if multiple files are touched, so long<br/>
 
messages are not a bad thing.  And as this is a read-only list, users<br/>
 
won't be attaching large binary files to their messages.  So would it<br/>
 
be good, in addition to setting these line limits, to increase the<br/>
 
size limit a little?  It will be hard to match line number to a KB<br/>
 
number, so it might save admins from having to check and accept<br/>
 
messages via the Mailman web interface.  It could be a good long term<br/>
 
time saver.<br/>
 
 
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33913630/
 
    |title=<nowiki>Re: [Flightgear-devel] [Flightgear-commitlogs] [FGData] FlightGear
 
data - next generation branch next updated.
 
7b595eca19e1bfb83ae330c02f2eeec5e9c9da58</nowiki>
 
    |author=<nowiki>Edward d'Auvergne</nowiki>
 
    |date=<nowiki>2015-04-19</nowiki>
 
  }}
 
}}
 
 
{{FGCquote
 
  |The default mailman option is 40kb, so we have doubled the allowable size<br/>
 
twice now. :-)  I don't have a big emotional attachment to the current<br/>
 
limit, but I suspect that it's starting to get close to being big enough.<br/>
 
I don't think too many people are going to spend the time to review a 160Kb<br/>
 
diff in an email browser ... at that point there are probably better tools<br/>
 
for evaluating the differences.  I think Torsten is planning to experiment<br/>
 
with limiting the message sizes as a first step.  But going forward we can<br/>
 
certainly tune the numbers on both the sending side and the mailing list<br/>
 
side and move towards a more optimal balance.
 
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33913846/
 
    |title=<nowiki>Re: [Flightgear-devel] [Flightgear-commitlogs] [FGData] FlightGear
 
data - next generation branch next updated.
 
7b595eca19e1bfb83ae330c02f2eeec5e9c9da58</nowiki>
 
    |author=<nowiki>Curtis Olson</nowiki>
 
    |date=<nowiki>2015-04-19</nowiki>
 
  }}
 
}}
 
  
 
== Bug reports on mailing lists? ==
 
== Bug reports on mailing lists? ==

Latest revision as of 05:14, 13 May 2016

Template for mailing list URLs

we should set up a template for the rows in the table, so that we can easily reuse/localize everything elsewhere (as per the git/repo link templates)

  • address
  • archives
  • subscribe
  • comments
  • description (localized)
  • status

--Hooray (talk) 10:58, 20 April 2015 (EDT)

Bug reports on mailing lists?

Is not that bad advice? Should not bug reports be redirected to the issue tracker in order to lessen unproductive/disruptive noise, in particular on the developer mailing list?

Johan G (Talk | contribs) 16:50, 10 May 2015 (EDT)