[GSoC-2010] MPWA

[Joshua Root]

On 2010-3-23 19:08 , Pratul Kalia wrote:
> On Tue, Mar 23, 2010 at 1:56 AM, William Siegrist <wsiegrist at apple.com> wrote:
>> I'm not sure making the entire app a Trac plugin would help, and it seems to me like it would just add hurdles to work around. You could create a Trac plugin that adds MPWA data to Trac's UI, but in my opinion, MPWA itself should be a separate app. You can assume both the plugin and the web app have access to each other's database, or you can rely on RPC between the two.
>>
>> As for SSO, you (and anyone else) should just plan to fake it during GSoC and let me (as the Mac OS Forge admin) integrate it later. Django has a very nice pluggable auth system which makes this easy, so I like that choice personally.
>>
> 
> So Django does seem to have the upper hand here. I think a second app
> would be fine, but then I would want to replace the current set of PHP
> scripts (that make up macports.org) and put that content in the Django
> website as well.

The existing web site could certainly use some love, but don't let
updating it sidetrack you from the primary objective.

> As for the way Trac and Django will talk to each other, or if that is
> even required, I will need to know what exactly the Django app is
> supposed to do. Nevertheless, RPC will be the way to go.

We definitely want some features that require data sharing between the
two. Off the top of my head: each port's MPWA entry/page/whatever should
include links to the tickets filed against it; and when a user creates a
new ticket, the Port field should be used to look up the maintainer and
automatically assign to them.

These aren't features you necessarily have to implement during GSoC, but
your design should be such that they are not hard to add.

- Josh