[Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team!

[Felix Crux]

I'm resending the email below to the pycon-mobile-guide at python.org
mailing list to keep everyone in the loop, because I just got a
bounceback from the mailing list server saying the mail was rejected
(presumably because of the *enormous* attachment).
 
I've left off the attachment this time, as this is just informational ­—
so hopefully this time it gets delivered :)
 
 
On Sun, Apr 3, 2016, at 22:01, Felix Crux wrote:
> Hi Carmen,
>
> Please find attached an initial attempt at bundling up all the content
> into a usable export. I hope it's workable  enough to get things
> going, but I'll follow up shortly with whatever is else is needed.
>
> The attached zip file should contain comma-separated (.csv) files with
> the details of all the talks, speakers, etc. The first line of each
> file has headings describing what each column is. Note that some rows
> (particularly speaker bios and talk descriptions) contain embedded
> newlines, but all of those entries should additionally be enclosed in
> double quotation marks. The files are UTF-8 encoded, and several of
> the speakers do have names containing non-ASCII characters like 'Ł',
> 'é', etc, so that's worth watching out for. There are also logo images
> for all the sponsors in the zip file.
>
> *Talk descriptions are currently exported as raw, unprocessed,
> Markdown*. I'm not sure what kind of formatting Guidebook supports,
> so I've left that as-is for now. If there's something more useful I
> can convert it to, just let me know. I do think we'll want to
> figure out how to process that formatting and get it reflected in
> the app, though.
>
> There's currently nothing in the data export that *links speakers to
> their talks*, which I know the app can do. If there's some data format
> that can be bulk-imported to your systems to get that automatically,
> just let me know and I'd be happy to work on it. In previous years,
> however, we just linked them up manually.
>
> Please don't hesitate to *let me know if there's any way I can
> process or rework the data* to make it easier for you/your tools to
> work with -- the nice thing about being a programming conference is
> we're generally happy to build our own tools to make things simpler!
> I would much rather put in the work on my end to automate whatever
> data processing you need to make it possible to bulk-upload changes,
> instead of having you or me need to go in and fix things manually
> one-by-one.
>
> At present, this is the* list of issues/missing data *that I'm aware
> of and am working on:
> * Keynote speakers are not included in the speaker bios.
> * Plenary sessions (e.g. keynotes, opening remarks) are just listed as
>   "plenary" with no description in the schedule.
> * Special events (e.g. PyLadies auction, 5K run, dinners) are not
>   included in the schedule (special_events_schedule.csv is empty).
> * Meals/breaks show up once per track/room, but they really should
>   just be listed once.
> * "Special" pages such as venue information, code of conduct, etc. may
>   need to be input manually - I don't mind doing it.
> * Speaker photos are not included (maybe that's OK -- we didn't have
>   them last year either).
> * As mentioned earlier, some text is in raw Markdown; and I don't know
>   if that's a format Guidebook can ingest.
> * Floor plan map is on its way, and we'll need to link talks to the
>   room they're in.
> * Some general information still TBD; I will get it to you ASAP (see
>   below).
>
> Finally, here's the *info your requested in in the Guide Basics
> spreadsheet*:
> Guide Name: PyCon 2016
> Guide Start Date: 2016-05-28
> Guide End Date: 2016-06-05
> Timezone: Pacific Daylight Time (PDT) (UTC -7)
> General Information, Venue, Icon, Cover Image, Maps: I will get these
> to you ASAP, or just fill them in myself and let you know.
> Facebook: https://www.facebook.com/us.pycon.org
> Twitter: https://twitter.com/pycon
> YouTube: Not set up yet, will let you know
> Photos: No (I think, for now at least)
> RSS Feed: http://pycon.blogspot.com/feeds/posts/default?alt=rss
> Homepage: https://us.pycon.org/2016/
> Feedback/Surveys: I believe we'll use this, but I don't think the
> survey has been designed yet. Will get it to you.
> Notifications: Sure, let's have this.
> My Schedule: Definitely want this feature.
> Notes: Sounds good.
> Live polling: I don't think we'll use this.
>
> All right, I think that's most of it for now? Sorry for the enormous
> email; I'm trying to be very thorough both to keep everyone in the
> loop and to remind myself of exactly what work I still need to do!
>
> Again, please don't hesitate to let me know if I can change or process
> the data in any way to make it easier for you, or if anything in the
> export looks weird -- it's all automated, so it's entirely possible
> something broken snuck through without human review.
>
> Cheers; all the best!
>
> --
> Felix
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-mobile-guide/attachments/20160405/d60c0f40/attachment.html>