Mailman 3 April 2016 - Pycon-mobile-guide

Re: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team!
by Felix Crux 10 Apr '16

10 Apr '16

Hi again! Please find attached the latest version of the data for the guide. Is there an ETA on when we could start playing around with a rough draft? It would be helpful even if it's in an incomplete state, since it would let us figure out what we might be overlooking. Currently I don't see anything for this year when I log on to https://builder.guidebook.com/#/guides/. There are a number of changes in this version of the data: * New sponsors: Flowroute and Netflix. * Sponsor logo changed: House Canary. * New/updated sponsor tutorials. * Schedules now show actual room to be used, not just e.g. "Session A". * Speaker bios added/updated. Let me know if you need anything! Cheers, -- Felix

1 0

Data export feature requests
by Felix Crux 08 Apr '16

08 Apr '16

Hi Ewa & co., Just a heads up that I've filed a few feature requests against the PyCon GitHub repository relating to data export features that would be useful for automating as much as possible of the mobile app creation process. None of these are "critical", nor do they need to be done this year — they're all things that I can manage manually. I don't know what this year's deal with Caktus looks like, or if you're coordinating with them regarding changes to the site's functionality, but I figure it's best to let you know in case it comes up. The list is: https://github.com/PyCon/pycon/issues/596 - Plenary session data is incomplete in program export https://github.com/PyCon/pycon/issues/597 - Keynote speaker bios are not present in program export https://github.com/PyCon/pycon/issues/598 - Speaker profile photos should be exportable https://github.com/PyCon/pycon/issues/599 - CMS pages should be exportable https://github.com/PyCon/pycon/issues/600 - Special events are not present in exported schedule Cheers! -- Felix

3 2

Re: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team!
by Felix Crux 06 Apr '16

06 Apr '16

I'm resending the email below to the pycon-mobile-guide(a)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

1 0

[Guidebook] Update: Intro to Guide Building Team!
by Carmen Kuncz (Guidebook) 04 Apr '16

04 Apr '16

##- Please type your reply above this line -## You are registered as a CC on this help desk request (support.guidebook.com/hc/requests/26702). Reply to this email to add a comment to the request. Other ccs: Felix Crux, Katie Herrgesell, Pycon-mobile-guide ---------------------------------------------- Carmen Kuncz, Apr 4, 10:02 AM Hi Felix, Thank you for sending this along! I will take a look at everything and start working on inputing this information to the guide within the next few days! I will reach out if I have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, Apr 3, 7:01 PM 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 Attachment(s): pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?… ---------------------------------------------- Carmen Kuncz, Mar 30, 12:18 PM Hi Ewa, No rush on getting the content to me! I just didn't want to miss a deadline for you! Please send me the content as you get it! Reach out if you have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Mar 30, 11:08 AM Hi Carmen, Thank you for checking in! I am not yet ready to start this yet. I will begin the process on Friday of this week and I will ping you if there are any questions. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Mar 30, 11:00 AM Hi Ewa, Just checking in again to see if you have any guide content for me? I know we were initially shooting for an April 1st internal launch date! Please let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Carmen Kuncz, Mar 21, 10:06 AM Hi Ewa, Just checking in to see if you have any content for me to start building your guide? Let me know, I am excited to get started on this! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 2:01 PM Yes, that is my cell phone number. Talk to you tomorrow! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:58 PM Hi Ewa, 1 PM PST tomorrow will work great! Can I call you on the cell phone number you have listed below? If not please let me know which number is best to reach you at! Looking forward to our call! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 1:50 PM Hi Carmen, Let's chat at 1pm PT tomorrow. Have a good afternoon! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:25 PM Hi Ewa, Are you possibly available tomorrow? I am free to speak anytime between 10 AM PST to 4PM PST. Let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 12:22 PM Hi Carmen, Are you available this afternoon? I am available any time now until about 4pm CT. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 10:55 AM Hi Ewa, It's great to e-meet you! My name is Carmen, and I'll be working with you to create your guide. Lets start by scheduling a call to discuss your guide. This will help me get a good vision for your guide as well as to propose a tentative timeline for an on-time release! Please let me know your availability so we can schedule a time! I have attached a Guide Basics Spreadsheet (will appear as a link). Please take a brief look at it before our call! I'm very excited to get started! Let me know your availability and if you have any questions, feel free to reply to this thread (rather than creating a new ticket -- things can get messy rather fast). You can also call my direct extension at 650-319-7233 ext. 222. Thanks again, and I look forward to hearing back from you! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook Attachment(s): Guide_Basics.xls - https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?… ---------------------------------------------- Katie Herrgesell, Feb 17, 10:46 AM Hi Ewa, I would like to introduce you to our awesome guide building team! They are the experts that will handle the data entry for you, and will work to create an easy to use event guide. I have shared your event information with the customer success team, and someone will be contacting you within one business day to get started on your guide. Good luck! Best, Katie -- Katie Herrgesell Sr. Corporate Account Manager Office: 650.319.7233 ext 126 Mobile: 216.570.0531 www.guidebook.com -------------------------------- This email is a service from Guidebook. [N2DQPZ-696N]

1 0

File to create the Basic Guide
by Ewa Jodlowska 01 Apr '16

01 Apr '16

Hi Felix, Not sure if you got this file or not when Carmen sent it out, but I am attaching here, just in case. If you do send her this, you might as well also send her the program export. We should have them add the abstracts as well for each tutorial/talk/poster. I have given you staff access to the site so you can download the export and anything else you may need to do. Once I get the pretty floor plan design, I will work on that and all sponsor things. Thanks so much for helping with this! I look forward to seeing you again at PyCon...just maybe not at a pirate restaurant ;) Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237

1 0