Re: [Mailman-Developers] GSOC 2013 - Introduction and Project Discussion
On Sat, 2013-04-06 at 15:03 +0530, Udit Saxena wrote:
- Web Posting Interface.
I haven't really followed the GSoC ideas for MM3 this year but that line poped-up on my radar. Isn't this similar/overlapping to what HyperKitty already does? I don't think one would want to embed posting messages from the admin interface of mailman (postorious), so posting from an interface would have to deal with archives as well (since one might want to reply to an existing thread). That's the reasoning that brought me to the question above :)
Did I miss something?
Pierre
Pierre-Yves Chibon writes:
On Sat, 2013-04-06 at 15:03 +0530, Udit Saxena wrote:
- Web Posting Interface.
Isn't this similar/overlapping to what HyperKitty already does?
No. There's no reason why a web posting interface needs to interact with the archives; it can talk directly to Mailman core, and will need to do so for other features such as authentication, sister lists, and the like. You get archiving for free.
I don't think one would want to embed posting messages from the admin interface of mailman (postorious), so posting from an interface would have to deal with archives as well (since one might want to reply to an existing thread).
It could be as simple as embedding a button with an appropriate URL communicating the information needed to compose a message in the archive display interface. On the other hand, the posting interface to the archives could be a full separate subsystem, with a special- purpose browsing system oriented to rapidly selecting and yanking content from related messages.
It might make sense to embed the interface in HyperKitty, which also has to deal with authentication, at least. But since posting and browsing are separate features I tend to favor creating an appropriate protocol for web posting, independent of the archive protocol and implementation.
On 13-04-08 5:27 PM, Stephen J. Turnbull wrote:
Pierre-Yves Chibon writes:
On Sat, 2013-04-06 at 15:03 +0530, Udit Saxena wrote:
- Web Posting Interface.
Isn't this similar/overlapping to what HyperKitty already does?
No. There's no reason why a web posting interface needs to interact with the archives; it can talk directly to Mailman core, and will need to do so for other features such as authentication, sister lists, and the like. You get archiving for free.
I think Stephen covered most of it, but I just want to add that I had in mind that if we do the separate posting interface right, we might be able to use this as the beginnings of a way to integrate any existing forum software into Mailman, much like we want to gateway from newsgroups.
That said...
I'm totally ok with this particular project being entirely part of hyperkitty in the short-term, though, since it'll clearly be a nice fit there right now and goodness knows I don't want to deal with yet another django-standalone instance running just to post messages. ;) The only reason I didn't suggest this be part of hyperkitty in the project description is that when I was writing up project information, I didn't know if any of the hyperkitty team would have time to mentor. If one of the hyperkitty devs wants to take the lead on mentoring this project, that would work for me!
Terri
Let me suggest that it would be useful to have the student develop something which could act as a plug-in module for any website. If we assume that there is an optional archiver such as hyperkitty, there should be a mechanism to "seed" the submission (in-reply-to, quoted text, etc.). But, if the archiver is not present, the same submission mechanism could handle submissions for any website, with or without postorius present.
The interface should address user authentication, using, when available, credentials that have already been provided. But it should also accept un-authenticated submissions and interact with the system to implement the list policies.
It should be interesting to see just what the students propose.
-- Richard
On Apr 8, 2013, at 7:42 PM, Terri Oda <terri@zone12.com> wrote:
On 13-04-08 5:27 PM, Stephen J. Turnbull wrote:
Pierre-Yves Chibon writes:
On Sat, 2013-04-06 at 15:03 +0530, Udit Saxena wrote:
- Web Posting Interface.
Isn't this similar/overlapping to what HyperKitty already does?
No. There's no reason why a web posting interface needs to interact with the archives; it can talk directly to Mailman core, and will need to do so for other features such as authentication, sister lists, and the like. You get archiving for free.
I think Stephen covered most of it, but I just want to add that I had in mind that if we do the separate posting interface right, we might be able to use this as the beginnings of a way to integrate any existing forum software into Mailman, much like we want to gateway from newsgroups.
That said...
I'm totally ok with this particular project being entirely part of hyperkitty in the short-term, though, since it'll clearly be a nice fit there right now and goodness knows I don't want to deal with yet another django-standalone instance running just to post messages. ;) The only reason I didn't suggest this be part of hyperkitty in the project description is that when I was writing up project information, I didn't know if any of the hyperkitty team would have time to mentor. If one of the hyperkitty devs wants to take the lead on mentoring this project, that would work for me!
Terri
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/richard%40nfsnet.o...
Security Policy: http://wiki.list.org/x/QIA9
On Tue, 2013-04-09 at 08:27 +0900, Stephen J. Turnbull wrote:
Pierre-Yves Chibon writes:
On Sat, 2013-04-06 at 15:03 +0530, Udit Saxena wrote:
- Web Posting Interface.
Isn't this similar/overlapping to what HyperKitty already does?
No. There's no reason why a web posting interface needs to interact with the archives; it can talk directly to Mailman core, and will need to do so for other features such as authentication, sister lists, and the like. You get archiving for free.
How do you reply to a thread if you don't have access to the archives?
I don't think one would want to embed posting messages from the admin interface of mailman (postorious), so posting from an interface would have to deal with archives as well (since one might want to reply to an existing thread).
It could be as simple as embedding a button with an appropriate URL communicating the information needed to compose a message in the archive display interface. On the other hand, the posting interface to the archives could be a full separate subsystem, with a special- purpose browsing system oriented to rapidly selecting and yanking content from related messages.
It might make sense to embed the interface in HyperKitty, which also has to deal with authentication, at least. But since posting and browsing are separate features I tend to favor creating an appropriate protocol for web posting, independent of the archive protocol and implementation.
If it is thought as a different system then I understand. I was more confused if that was thought as part of HyperKitty as I believe it already does that to some extend (I'll let Aurélien specify to which extend).
Thanks for clarifying, Pierre
Pierre-Yves Chibon writes:
How do you reply to a thread if you don't have access to the archives?
The archives provide a URL to the web interface instead of a mailto URL.
If it is thought as a different system then I understand. I was more confused if that was thought as part of HyperKitty as I believe it already does that to some extend (I'll let Aurélien specify to which extend).
Sure.
participants (4)
-
Pierre-Yves Chibon -
Richard Wackerbarth -
Stephen J. Turnbull -
Terri Oda