On Oct 10, 2012, at 3:12 PM, Magnus Hagander wrote:
> On Wed, Oct 10, 2012 at 9:09 PM, Jonathan S. Katz
> <jonathan.katz@excoventures.com> wrote:
>> On Oct 10, 2012, at 2:57 PM, Magnus Hagander wrote:
>>
>>> On Wed, Oct 10, 2012 at 8:44 PM, Jonathan S. Katz
>>> <jonathan.katz@excoventures.com> wrote:
>>>> On Oct 10, 2012, at 2:37 PM, Josh Berkus wrote:
>>>>
>>>>>
>>>>>> If we go the website route, Selena and I had started code for the new site pugs site, perhaps some of this code
couldbe reused: http://git.postgresql.org/gitweb/?p=pgpugs.git;a=summary
>>>>>
>>>>> Oh, I didn't even know about this project. Looks like you lost momentum
>>>>> about a year ago. How much functionality did you actually get done?
>>>>
>>>> Just looked at the code - listing the pugs by geographical region was done(-ish, really needed a couple of more
lines) and it looks like it could include posts from the PUG blogs. You could edit what pugs were visible in the list
fromthe Django admin that was setup. The functionality from this code rewrite was to mirror the old PUG site.
>>>>
>>>> Getting the pug list done would be minimal work. Unless we plan on relaunching the pugs.postgresql.org site, It
wouldprobably be a better endeavor to take the data models, simplify them slightly, and put them into the main -www
codebase,as well as the listing code.
>>>
>>> I would suggest going with whatever is the simplest. At least starting
>>> there. Once we've proven to ourselves that we have the manpower to
>>> maintain that, we can start considering doing something more advanced.
>>>
>>> Thus, +1 for a simple pugs listing/app on the main website. We already
>>> have planet to aggregate blogs, and there are a bazillion different
>>> sites out there that can host your personal blog for you.
>>
>> So by "app" is it safe to assume "Django app within pgweb" as opposed to a separate project? If that is the case, I
canmove over the appropriate code relatively quickly.
>
> Yes.
OK. Working on a patch. Need to adapt it a bit to the pgweb conventions.
Jonathan
