[ucc] Events on the website

[Samuel Spencer]

I've installed a test website here:
http://theodore.ucc.asn.au/ucc/

This took a few minutes to get setup and it provides more than what we need.
Its supported, open-source, can use OpenID and is pretty.
The big issue will be modifying the template to change the look, but
we can make up a nice site, thats easy to keep up to date.

If anyone wants to fiddle with this, let me know and I'll set up a
test account to play around with.

Can anyone suggest a reason not to do this?


Over the next day or two I will look at m
On Wed, Feb 18, 2009 at 9:36 AM, Samuel Spencer <theodore at ucc.asn.au> wrote:
> Is there a reason we can't start using a hosted solution for things like this?
> I'd be really interested as to peoples ideas like "Google Apps for your domain".
>
> With something like this we can offload a lot of the day-to-day
> drugery of email/calendars/list management, while still maintaining
> administrative control.
>
> We can free up club resources (eg. machine time) for other club
> projects, we can see our uptime increase for these services and it
> will mean if we have issues in the machine room we can still have some
> form of communication.
>
> I understand the reasoning behind the idea of us wanting to
> run/manage/host all of these in house, but there has to come a point
> where the knowledge we give students is out-weighed by ease-of-use.
>
> Also, while I'm putting ideas that will probably get shot down out
> there, anyone against the idea of trying to migrate the club website
> to a fully-fledged CMS. Maybe Joomla? While moin-moin will be
> suggested, I'm against it solely because of the idea of a flat-file
> based cms.
>
>
>
> On Tue, Feb 17, 2009 at 11:37 PM, James Andrewartha
> <trs80 at ucc.gu.uwa.edu.au> wrote:
>> On Tue, 17 Feb 2009, David Adam wrote:
>>
>>> Known issues:
>>>  - Can't have more than 31 days worth of events in a list. Not a problem
>>>    for the index page but a bit crappy for infobase/events/.
>>
>> I went looking for where the limit is in the code, but I gave up (Bedework
>> is a textbook example of how Java forces overengineered architecture just
>> to gain some dynamic flexibility) and just tested days > 31 to find the
>> error, but it seems to be happily accepting them now. I've upped the event
>> page to list 75 days worth.
>>
>>>  - Really slow. Workaround might be to cache the JSON feed somewhere on
>>>    /services (+/- gzip) and pull that instead.
>>
>> For some reason it's less slow when the twitter script is disabled. I've
>> swapped them around so the upcoming events comes first and it's quick as.
>>
>> --
>> # TRS-80              trs80(a)ucc.gu.uwa.edu.au #/ "Otherwise Bub here will do \
>> # UCC Wheel Member     http://trs80.ucc.asn.au/ #|  what squirrels do best     |
>> [ "There's nobody getting rich writing          ]|  -- Collect and hide your   |
>> [  software that I know of" -- Bill Gates, 1980 ]\  nuts." -- Acid Reflux #231 /
>>
>
>
>
> --
> --- Insert witty signature here ---
>



-- 
--- Insert witty signature here ---