On Tue, Jun 17, 2008 at 6:24 PM, Paul Boddie <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Here's a message from Ville Säävuori about the conference schedule which
> didn't make it to the list for some reason. I can't see whether there was a
> moderation problem in this case, but I'll gladly do moderation on this list
> if someone will let me into the moderators club.
>
> Paul
>
> P.S. There's a large e-mail from Jacob waiting in the moderation queue for the
> EuroPython list because it's a very big message containing some kind of
> template. I've left it in the queue so far because I don't want to either
> send a big message to lots of potentially angry people or to send a message
> without the main payload to such people. Maybe we can upload the template to
> the site.
>
> ---------- Forwarded Message ----------
>
> From: Ville Säävuori <[EMAIL PROTECTED]>
> Date: 16. kesäkuuta 2008 klo 0.44.07
> To: [email protected]
> Subject: Re: [Europython-improve] iCalendar of the conference schedule
>
> Hi all,
>
>>> The only PyCon-Tech *code* it uses is the CSS, plus many *ideas*
>>> which using PyCon-Tech last year gave us.
>
> The output is very well formed and therefore also quite easily
> parseable. Paul already provided us a simple script for parsing the
> schedule into an ical-file, and I would like to reproduce my app
> from last year and make all data available in easily searchable and
> mobile-ready form. The example parser from Paul is basically all I
> need for putting this data into database.
>
> My ideas for the schedule data have already been mostly implemented
> in the new PyCon-Tech code. I would like to have *my* conference
> schedule (to not impose these ideas on anyone who doesn't like them)
> have following functionality:
>
> - possibility to log in with OpenID (to customize things)
> - possibility to select sessions that I want to attend
> - possibility to browse this selection (== my customized schedule)
> in a format tailored for a mobile reader (for example smartphone/
> iphone)
> - simple search functionality for session and presenter details
> - more ways to browse the data trough cross-linking and tagging
> (browse by topic, level, author)
> - a possibility to comment sessions
>
> These are exactly the same ideas I already implemented last year (at
> first just for my own purposes, but eventually as a public site).
>
> [about structured data]
>>> Well, it was talked about, but nobody actually did anything ;)
>
> I'm willing (and very likely to) to do this again and share it as a
> complementary service for anyone who likes to read the schedule in a
> customized format. I understand that organizers have lots of things
> on theirs hands as the conference is getting closer so I don't want
> to be a burden to anyone with these ideas -- especially if someone
> thinks that they are bad or unnecassary. But I also am gladly
> willing to help to integrate these to the official site if needed.
>
> (I also want to point out that I implemented previously mentioned
> functionalities last year with Django in _one evening_ taking
> advance of the structured data provided, so I am not talking about a
> monumentally huge commitment.)
>
>>> I'm down to give a talk on the conferencing software at Vilnius,
>>> maybe
>>> it would be a good idea to get together and build in the iCal stuff
>>> for next year.
>
> I'm getting a slight feeling of NIH-syndrome here, since, AFAIK,
> PyCon-Tech system already produces iCal syndication. Would it be OK
> to just try to work on that codebase for next year or are their
> needs totally different from EPs?
The PyCon-Tech code needs a major overhaul. It suffered from massive
feature creep, and multiple CSS redesigns. In case anyone thinks that
PyCon-Tech should have been used for EuroPython this year, the answer
is no. ('Hell no' would be more accurate). I dont think it was a NIH
issue as much as a NTC (not that crap) issue. There is also the issue
of integration with the wiki to make things seemless.
My goal is to have the schedule code split off and as a separate
django app from the rest of PyCon-Tech (actually my plan which has
already started is to break it up completely to the point where only
the proposal system and worst case registration still remain). If that
can be done cleanly, then using the schedule system as a plugin wsgi
app (which will be supported shortly in django) will make generic
integration possible. (the javascript cruft will be broken up and
configurable with the default configuration being 'off' as well). All
of this would have been done this past year, but registration hell
consumed me.
I see no reason to have one all encompassing conference system, and
the potential for much harm if that does happen. With that said, some
sharing of resources including code is a good thing (tm) where
applicable.
-Doug
>
> Best regards,
>
> - VS
> _______________________________________________
> Europython-improve mailing list
> [email protected]
> http://mail.python.org/mailman/listinfo/europython-improve
>
_______________________________________________
Europython-improve mailing list
[email protected]
http://mail.python.org/mailman/listinfo/europython-improve
