Hello, I know that you have suggested that we use buildout to keep the version of wikkid separate from the launchpad code. However, on the LEP<https://dev.launchpad.net/LEP/Wiki>, people have expressed concern that doing it this way will create "problems like we had with loggerhead"- just not being completely integrated with the rest of launchpad. Also, though wikkid has most of the features that are needed, people might want to change it so that it is more suited toward launchpad, and keeping it separate may make this more difficult.
Let me know if you have any further thoughts on this issue; I'm proposing that we still use the wikkid code, but adapt it to be a launchpad application (lp.wiki), and not an external dependency. Thanks, Geoff On Sun, May 22, 2011 at 7:02 PM, Geoff <x...@xaav.tk> wrote: > Okay, I'll look into that. > > > On Sun, May 22, 2011 at 6:58 PM, Tim Penhey <t...@penhey.net> wrote: > >> On Mon, 23 May 2011 11:52:00 Geoff wrote: >> > Hello, >> > >> > I had created the module lp.wiki, and was about to code it myself. >> > >> > However, when I saw that you already had an application, I replaced the >> > module lp.wiki with wikkid, reducing the workload. >> > >> > We can discuss this further on launchpad-dev mailing list, okay? >> >> OK... this isn't how we'd do it. >> >> The preferred way would be to use buildout and store a version of wikkid >> in >> the download cache. That way we'd have views that operate using wikkid >> code, >> and also it is simpler to keep the LP version in sync with upstream. >> >> Tim >> > >
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
