Mark Sapiro writes:
> Well, Steve channeled me earlier, so I'll return the favor.
And did it with extreme precision and accuracy. Sorry if I created
any misunderstandings.
The only thing I have to add is that mailman-users@python.org is not
going away. Furthermore, I expect that Mark and I,
Phil Stracchino writes:
> On 2020-02-28 05:44, Stephen J. Turnbull wrote:
> > str in Python 1, and the history of Mailman as an MLM for an American
> > rock band (who needs no steekin' accents, we just hammer and bend the
> > strings!)
>
> This is clearly a story I didn't know. :) And
Brian Carpenter writes:
> On 2/28/20 1:55 PM, Mark Sapiro wrote:
> > Quite a few core settings are not exposed in Postorius but we're
> > chipping away at that.
>
> Is there a list somewhere to see what core settings have not been
> exposed in Postorius yet?
Implicit in the Postorius UI
@mailman-users
I'm going to get into a lot of design here, so I'm moving the thread to
mailman-develop...@python.org. Reply-To set; please respect. Brian
kept in Reply-To as a courtesy, don't know if he's subscribed over there.
@mailman-developers Brian is planning to develop an alternative web
On 2/28/20 1:55 PM, Mark Sapiro wrote:
Quite a few core settings are not exposed in Postorius but we're
chipping away at that.
Is there a list somewhere to see what core settings have not been
exposed in Postorius yet?
--
Please let me know if you need further assistance.
Thank you for
On 2/28/20 10:24 AM, Jim Popovitch via Mailman-Users wrote:
>
> I think that is Brian's and a lot of other people's concern. 3 years to
> implement something into MM3 that was a core feature in MM2. I realize
> this next question is going to sound bombastic, I assure you it's not
> meant that
On Fri, 2020-02-28 at 10:07 -0800, Mark Sapiro wrote:
> On 2/28/20 6:17 AM, Jim Popovitch via Mailman-Users wrote:
> > On Fri, 2020-02-28 at 19:52 +0900, Stephen J. Turnbull wrote:
> > > Brian Carpenter writes:
> > >
> > > > I have hired a professional PHP developer to begin work on a new
> > >
On 2/28/20 6:17 AM, Jim Popovitch via Mailman-Users wrote:
> On Fri, 2020-02-28 at 19:52 +0900, Stephen J. Turnbull wrote:
>> Brian Carpenter writes:
>>
>> > I have hired a professional PHP developer to begin work on a new
>> > admin/forum interface for Mailman 3.
>>
>> Too bad. I really
On 2/28/20 5:52 AM, Stephen J. Turnbull wrote:
Too bad. I really sympathize with your goals but am unlikely to be
able to contribute directly to implementation (assuming an eventual
open-sourcing). Never learned PHP, not going to do it anytime soon.
That's OK, the point of REST is so*you*
On 2020-02-28 05:44, Stephen J. Turnbull wrote:
> Mailman has the opposite problem. We *wish* str was Unicode from the
> get-go, but it wasn't, and Mailman 2 is rife with potential encoded/
> decoded confusion because of the nature of email and the dual usage of
> str in Python 1, and the history
On Fri, 2020-02-28 at 19:52 +0900, Stephen J. Turnbull wrote:
> Brian Carpenter writes:
>
> > I have hired a professional PHP developer to begin work on a new
> > admin/forum interface for Mailman 3.
>
> Too bad. I really sympathize with your goals but am unlikely to be
> able to contribute
Brian Carpenter writes:
> I have hired a professional PHP developer to begin work on a new
> admin/forum interface for Mailman 3.
Too bad. I really sympathize with your goals but am unlikely to be
able to contribute directly to implementation (assuming an eventual
open-sourcing). Never
Phil Stracchino writes:
> Rewriting without breaking is hard.
True.
> There is a Python framework called Twisted.
Not an example appropriate to Mailman, though. The Twisted people were
doing amazing things with str, to which Unicode was irrelevant, because
their job was to shovel bytes from
13 matches
Mail list logo
