Re: [Mailman-Developers] Proposal for a new menu grouping in MM3webUI
Yeah, I took a look at what I wrote and I wasn't as clear as I thought I was. By SCHEDULED digest, I mean a digest sent out on a set time period or frequency (like Years, Months, Weeks, etc.). Those digests would have the volume number incremented and the digest number reset to 1. Any digests sent within (or BETWEEN) the scheduled digests time period / freq. for whatever reason - size, number of msgs - would increment the digest number only. If there are no digests/msgs to send, then the volume number does not increment. Thanks Mark, Chris On 5/24/2011 3:50 PM, Mark Sapiro wrote: > C Nulk wrote: > >> Thank you for the work also. I did view your latest diagram and the >> volume/digest issue seems to be correct. But just to make sure, the >> volume number is increased for every SCHEDULED digest sent out (with the >> digest number reset to 1). Next, any addition digests sent out BETWEEN >> scheduled digests (whether due to size of digest or number of messages >> in the digest) increase the digest number but not the volume number. If >> that is true, then I am in agreement with you :) because it mimics the >> magazine style of volume/issue. > > This is not the way it works in MM 2.1. In MM 2.1, the volume > increments and the issue resets to one for the first digest produced > in a new period, where period is Year, Quarter, Month, Week or Day as > set in Digest options -> digest_volume_frequency. The issue increments > for each digest produced in that period whether the digest is produced > 'periodically' or by size. If there are no posts/digests produced > during a period, the volume doesn't increment for that period. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Proposal for a new menu grouping in MM3webUI
On 5/25/11 7:25 AM, C Nulk wrote: > Yeah, I took a look at what I wrote and I wasn't as clear as I thought I > was. By SCHEDULED digest, I mean a digest sent out on a set time period > or frequency (like Years, Months, Weeks, etc.). Those digests would > have the volume number incremented and the digest number reset to 1. > Any digests sent within (or BETWEEN) the scheduled digests time period / > freq. for whatever reason - size, number of msgs - would increment the > digest number only. If there are no digests/msgs to send, then the > volume number does not increment. That is essentially what I thought you meant, and as I said, that's not how it works in Mailman 2.1 (See below) digest_volume_frequency and digest_send_periodic are separate, independent settings. digest_volume_frequency controls only when the volume number changes. digest_send_periodic controls whether or not a digest is sent when cron/senddigests runs (default, daily at noon). In any case, a digest is always sent when the size of the list's accumulated digest.mbox reaches digest_size_threshhold. I.e. there are no 'scheduled' digests other than the ones sent daily by cron/senddigests and those have no relation to the volume number. Even if digest_volume_frequency is Daily, and digest_send_periodic is Yes, and digests are sent at noon, a digest triggered on size at 09:00 will be issue number one of that day's volume if it's the first digest of the day. > On 5/24/2011 3:50 PM, Mark Sapiro wrote: >> >> This is not the way it works in MM 2.1. In MM 2.1, the volume >> increments and the issue resets to one for the first digest produced >> in a new period, where period is Year, Quarter, Month, Week or Day as >> set in Digest options -> digest_volume_frequency. The issue increments >> for each digest produced in that period whether the digest is produced >> 'periodically' or by size. If there are no posts/digests produced >> during a period, the volume doesn't increment for that period. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, CaliforniaBetter use your sense - B. Dylan ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] New Menu - Role Based Proposal
Hi there, I've picked up Patricks idea today and expanded the existing draft with a few other things, you can find both on http://wiki.list.org/display/DEV/New+Menu it would be brilliant if you'd compare both and see what you'd like and if there is still anything to improve. Only one little explanation: the colors in the mindmap show the ACL (at least in the role based one) - description in the upper left corner. Each item connected to the middle could be traded as a tab-like navigation e.g. http://wiki.list.org/display/DEV/benste%27s+GSoc+2011+-+page please bare in mind that these mockups don't represent any style ! - (only wackys idea of a combobox changeing the lists - thanks) the rest of the items are either heading or items, atm. I've noted only the fields which are present in the REST API, e.g. i didn't go into detail creating a new list as some values are readonly atm. -- Einen schönen Tag wünscht: Benedict Stein signature.asc Description: This is a digitally signed message part ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
