Two Questions: One General, the Other Specific
Salutations;
For context, I have been lurking on this site for a number of years now, in order to track the progress of this wonderful mailman3 project.
Further context, I am chair of a 66 unit condominium and pay for two lists provided by EMWD.com and get a hands on feel from an mailman3 operations perspective.
*Is there another site that might best communicate the future goals, plans, objectives, and time frames for mailman3 or is the status of the project at the state of being primarily reacting to problems, as evidenced in this problem solving forum, at least as it seems to me, with no offense meant or intended?*
Something I find surprising is a problem described in an image grab below relating to an inability to amend a list entry to include a name to be associated with an email address, as if the data needs to be immutable. When a workaround was unsuccessfully explored to delete the entry and then resubmit an amended entry but with the same already deleted email address, that was still refused, presumably because of pointers to archived data don't permit, but this seems like a particularly onerous restriction, or perhaps even a bug, or at least a severe design constraint. *Is this item on an existing to do list?*
*Comments please?*
Thank you in advance for any responses to the questions in bold to facilitate faster reading, etc.
Best regards.
Dave Wilson
On 2/26/21 12:10 PM, David Wilson wrote:
For context, I have been lurking on this site for a number of years now, in order to track the progress of this wonderful mailman3 project.
Further context, I am chair of a 66 unit condominium and pay for two lists provided by EMWD.com and get a hands on feel from an mailman3 operations perspective.
*Is there another site that might best communicate the future goals, plans, objectives, and time frames for mailman3 or is the status of the project at the state of being primarily reacting to problems, as evidenced in this problem solving forum, at least as it seems to me, with no offense meant or intended?*
Something I find surprising is a problem described in an image grab below relating to an inability to amend a list entry to include a name to be associated with an email address, as if the data needs to be immutable. When a workaround was unsuccessfully explored to delete the entry and then resubmit an amended entry but with the same already deleted email address, that was still refused, presumably because of pointers to archived data don't permit, but this seems like a particularly onerous restriction, or perhaps even a bug, or at least a severe design constraint. *Is this item on an existing to do list?*
The server that David's lists is on, is running the latest stable versions of Mailman 3, Postorius, and Hyperkitty in case that helps.
@David, we have the issue that you ran into mitigated to a great extent with our Affinity user interface. Just contact me via our support ticket system if you want to explore have your lists migrated to our Mailman 3 Affinity platform.
-- Brian Carpenter Harmonylists.com Emwd.com
On 2/26/21 9:10 AM, David Wilson wrote:
*Is there another site that might best communicate the future goals, plans, objectives, and time frames for mailman3 or is the status of the project at the state of being primarily reacting to problems, as evidenced in this problem solving forum, at least as it seems to me, with no offense meant or intended?*
We are a small project with few volunteers and no paid staff. While we would like to be able to devote significant time to future goals, plans and objectives, often we only have time and resources to devote to fixing immediate issues.
The way to get issues/objectives/etc. on our radar it to post them to the various sub-project issue trackers at <https://gitlab.com/groups/mailman>.
Something I find surprising is a problem described in an image grab below relating to an inability to amend a list entry to include a name to be associated with an email address, as if the data needs to be immutable. When a workaround was unsuccessfully explored to delete the entry and then resubmit an amended entry but with the same already deleted email address, that was still refused, presumably because of pointers to archived data don't permit, but this seems like a particularly onerous restriction, or perhaps even a bug, or at least a severe design constraint. *Is this item on an existing to do list?*
There has been much discussion of this on this list. See for example the recent thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/Z...>
This item is not on a ToDo list because even though <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...> asked for an issue to be filed, the most interested person refused to do so because of his assessment of our priorities <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...>.
And if you don't read the whole thread, at least see the response at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Brian Carpenter -
David Wilson -
Mark Sapiro