Hello!
I believe that there was a Code Sprint at Pycon to work on the MM 3.0 UI (and other items). Is there any place I can go to read about what has been implemented thus far in MM 3.0 and what features are still outstanding with regards to MM 3.0 and in particular the UI?
Thanks, Jen
On Mar 17, 2010, at 03:41 PM, Jennifer Redman wrote:
I believe that there was a Code Sprint at Pycon to work on the MM 3.0 UI (and other items). Is there any place I can go to read about what has been implemented thus far in MM 3.0 and what features are still outstanding with regards to MM 3.0 and in particular the UI?
Hi Jen,
We did sprint on the MM3 web ui at Pycon, and I've been meaning to review the work and publicize it more. Florian, Jon, and Craig did some good work on that side while I was reworking the REST infrastructure.
Their branches are here:
https://code.edge.launchpad.net/mailmanweb
We decided to use Django and see how far we could get. I think the experiment worked well and I'm inclined to go with Django moving forward. Perhaps Florian can speak more about this, where he plans to go and how we can get more people involved in this effort. I think he and Patrick were even considering putting up an experimental server so that we can being to play with it.
-Barry
- Barry Warsaw barry@list.org:
On Mar 17, 2010, at 03:41 PM, Jennifer Redman wrote:
I believe that there was a Code Sprint at Pycon to work on the MM 3.0 UI (and other items). Is there any place I can go to read about what has been implemented thus far in MM 3.0 and what features are still outstanding with regards to MM 3.0 and in particular the UI?
Hi Jen,
We did sprint on the MM3 web ui at Pycon, and I've been meaning to review the work and publicize it more. Florian, Jon, and Craig did some good work on that side while I was reworking the REST infrastructure.
Their branches are here:
https://code.edge.launchpad.net/mailmanweb
We decided to use Django and see how far we could get. I think the experiment worked well and I'm inclined to go with Django moving forward. Perhaps Florian can speak more about this, where he plans to go and how we can get more people involved in this effort. I think he and Patrick were even considering putting up an experimental server so that we can being to play with it.
The server is up and almost ready to play with. Florian wanted to check a few things the other day and ping you offlist on this and that.
p@rick
Hi all,
there are still a few things to do but I'm hopeful I can get things ready over the weekend. My goal is to have a simple django skeleton running that talks to the rest server in a working MM3-environment. I will update the wiki with info on what is where and also outline some of the things we discussed during the sprint so everyone interested can get themselves up to speed.
Cheers Florian
Am 18.03.2010 um 13:32 schrieb Barry Warsaw:
On Mar 18, 2010, at 06:32 AM, Patrick Ben Koetter wrote:
The server is up and almost ready to play with. Florian wanted to check a few things the other day and ping you offlist on this and that.
Awesome! -Barry
On Mar 19, 2010, at 09:18 AM, Florian Fuchs wrote:
there are still a few things to do but I'm hopeful I can get things ready over the weekend. My goal is to have a simple django skeleton running that talks to the rest server in a working MM3-environment. I will update the wiki with info on what is where and also outline some of the things we discussed during the sprint so everyone interested can get themselves up to speed.
Sounds great Florian, thanks. I think once we get the framework going and put a test server up, we're going to get a lot of folks interested in helping us flesh out the web ui. At least I hope so! :)
-Barry
On Fri, Mar 19, 2010 at 6:52 AM, Barry Warsaw barry@list.org wrote:
On Mar 19, 2010, at 09:18 AM, Florian Fuchs wrote:
there are still a few things to do but I'm hopeful I can get things ready over the weekend. My goal is to have a simple django skeleton running that talks to the rest server in a working MM3-environment. I will update the
wiki
with info on what is where and also outline some of the things we
discussed
during the sprint so everyone interested can get themselves up to
speed.Mailman-Developers mailing list
Since Django is being used for the web-interface I'm curious about the implications for the ORM. Since MM 3.0 is using STORM - do you plan to just not use the built-in Django ORM and go with STORM - or are you going to wind up with 2 different database interfaces?
Thanks, Jen
Dear All, do you have some screenshots about the upcoming Mailman3 UI? I have been Googling for some time but I didn't got appropriate results.
Yours, Zoltan
Kovács Zoltán writes:
Dear All, do you have some screenshots about the upcoming Mailman3 UI? I have been Googling for some time but I didn't got appropriate results.
If you think screenshots of the UI are important, then Mailman 3 is not for you, yet. Please have some patience, it will be coming in a few weeks I would guess.
On Mar 23, 2010, at 12:53 PM, Stephen J. Turnbull wrote:
Kovács Zoltán writes:
Dear All, do you have some screenshots about the upcoming Mailman3 UI? I have been Googling for some time but I didn't got appropriate results.
If you think screenshots of the UI are important, then Mailman 3 is not for you, yet. Please have some patience, it will be coming in a few weeks I would guess.
Correct. Florian will hopefully soon announce a public playground for the web ui. It's fairly simplistic right now, but we're working on ramping up participation in its development, so stay tuned!
-Barry
Since Django is being used for the web-interface I'm curious about the implications for the ORM. Since MM 3.0 is using STORM - do you plan to just not use the built-in Django ORM and go with STORM - or are you going to wind up with 2 different database interfaces?
Hi Jen,
so far the plan is to have the UI completely separated from the mailman core and have the two communicate via REST. So I guess there is no reason not to use the Django ORM. But - at the risk of missing something right now: I am not quite sure if the UI will even need an own database at all if the data is stored by the mailman core.
Cheers Florian
On Mar 22, 2010, at 01:46 PM, Jennifer Redman wrote:
Since Django is being used for the web-interface I'm curious about the implications for the ORM. Since MM 3.0 is using STORM - do you plan to just not use the built-in Django ORM and go with STORM - or are you going to wind up with 2 different database interfaces?
Great question. I'm not a Django expert so I'm open to suggestions, but since these are in a sense separate projects and their primary (only?) integration point is the REST API, I think it would be okay to use the Django ORM for the web ui and Storm for the core engine. Ideally, the web ui would only have enough model code for it to do its job, possibly including caching where necessary, storing and accessing most of the core data in the engine via REST.
The place where things might get tricky is in authentication, and I'm not really sure what the right answer is. My sense is that if we can store that in the core and provide it over REST that will work better.
-Barry
participants (6)
-
Barry Warsaw -
Florian Fuchs -
Jennifer Redman -
Kovács Zoltán -
Patrick Ben Koetter -
Stephen J. Turnbull