From ewa at python.org Fri Apr 1 16:46:44 2016 From: ewa at python.org (Ewa Jodlowska) Date: Fri, 1 Apr 2016 15:46:44 -0500 Subject: [Pycon-mobile-guide] File to create the Basic Guide Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Guide_Basics (1).xls Type: application/vnd.ms-excel Size: 48640 bytes Desc: not available URL: From builders at guidebook.zendesk.com Mon Apr 4 13:02:36 2016 From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook)) Date: Mon, 04 Apr 2016 17:02:36 +0000 Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team! In-Reply-To: References: <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com> Message-ID: ##- 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/?name=pycon-2016-guidebook-data.zip ---------------------------------------------- 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/?name=Guide_Basics.xls ---------------------------------------------- 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] -------------- next part -------------- An HTML attachment was scrubbed... URL: From felixc at felixcrux.com Tue Apr 5 19:55:15 2016 From: felixc at felixcrux.com (Felix Crux) Date: Tue, 05 Apr 2016 19:55:15 -0400 Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team! In-Reply-To: <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com> References: <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com> Message-ID: <1459900515.1135358.570171161.1173F552@webmail.messagingengine.com> 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: From felixc at felixcrux.com Tue Apr 5 20:05:22 2016 From: felixc at felixcrux.com (Felix Crux) Date: Tue, 05 Apr 2016 20:05:22 -0400 Subject: [Pycon-mobile-guide] Data export feature requests Message-ID: <1459901122.1146014.570173905.3062FB92@webmail.messagingengine.com> 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 From ewa at python.org Wed Apr 6 17:16:12 2016 From: ewa at python.org (Ewa Jodlowska) Date: Wed, 6 Apr 2016 16:16:12 -0500 Subject: [Pycon-mobile-guide] Data export feature requests In-Reply-To: <1459901122.1146014.570173905.3062FB92@webmail.messagingengine.com> References: <1459901122.1146014.570173905.3062FB92@webmail.messagingengine.com> Message-ID: Hi Felix, Thanks again for beginning to work on the mobile guide setup. Some of the export issues will definitely need to be addressed for 2017. It is probably a mix of Caktus (or future vendor) needing to look at the export for issues and partially may be due to the schedule being imported this year. I am cc'ing in Brandon because he will be addressing these issues for 2017 and should also keep this aspect in mind. Do you know if the info has been loaded into gears yet? I do not see it when I log into https://gears.guidebook.com. Once I can login, I can certainly help piece things together. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 On Tue, Apr 5, 2016 at 7:05 PM, Felix Crux wrote: > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pycon.brandon at gmail.com Thu Apr 7 17:01:53 2016 From: pycon.brandon at gmail.com (Brandon Rhodes) Date: Thu, 7 Apr 2016 17:01:53 -0400 Subject: [Pycon-mobile-guide] Data export feature requests In-Reply-To: References: <1459901122.1146014.570173905.3062FB92@webmail.messagingengine.com> Message-ID: Thanks for opening formal issues, Felix, so that I can keep up with these! I predict that I'll be able to accomplish a few this weekend, and punt the hard ones til 2017. By the end of the weekend, I suppose, we'll know which are which. :) On Wed, Apr 6, 2016 at 5:16 PM, Ewa Jodlowska wrote: > Hi Felix, > > Thanks again for beginning to work on the mobile guide setup. > > Some of the export issues will definitely need to be addressed for 2017. > It is probably a mix of Caktus (or future vendor) needing to look at the > export for issues and partially may be due to the schedule being imported > this year. I am cc'ing in Brandon because he will be addressing these > issues for 2017 and should also keep this aspect in mind. > > Do you know if the info has been loaded into gears yet? I do not see it > when I log into https://gears.guidebook.com. Once I can login, I can > certainly help piece things together. > > > > Best regards, > > Ewa > Director of Operations > Python Software Foundation > Cell: 415-319-5237 > > On Tue, Apr 5, 2016 at 7:05 PM, Felix Crux wrote: > >> 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 >> > > -- Brandon Rhodes PyCon 2016 Conference Chair pycon.brandon at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From felixc at felixcrux.com Sun Apr 10 13:11:40 2016 From: felixc at felixcrux.com (Felix Crux) Date: Sun, 10 Apr 2016 13:11:40 -0400 Subject: [Pycon-mobile-guide] Items needed for mobile guide Message-ID: <1460308300.2837012.574395705.495FD323@webmail.messagingengine.com> Hi Ewa et al., Most of the stuff for the guide I can figure out, but there are a few items that I'll need from others. None are urgent. I think this is all of them: 1) Venue floor plan. I know you're already working on this since you mentioned it in a previous email, but I'm listing it here for completeness. 2) Surveys. I believe there was a basic post-tutorial survey set up last year. We can re-use it or design a new one from scratch. We can have different ones for talks vs. tutorials, etc. 3) YouTube page URL. I'm guessing this hasn't been set up yet, but it would be great if we could link to it before the conference, so people know where to check once videos start being uploaded. That... actually might be it! I'll update this thread if anything new comes up. Cheers, -- Felix From felixc at felixcrux.com Sun Apr 10 12:59:27 2016 From: felixc at felixcrux.com (Felix Crux) Date: Sun, 10 Apr 2016 12:59:27 -0400 Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team! In-Reply-To: <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com> References: <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com> Message-ID: <20160410165927.GA1034@mir.felixcrux.com> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: pycon-2016-guidebook-data.zip Type: application/zip Size: 10531464 bytes Desc: not available URL: From ewa at python.org Mon Apr 11 15:14:16 2016 From: ewa at python.org (Ewa Jodlowska) Date: Mon, 11 Apr 2016 14:14:16 -0500 Subject: [Pycon-mobile-guide] Items needed for mobile guide In-Reply-To: <1460308300.2837012.574395705.495FD323@webmail.messagingengine.com> References: <1460308300.2837012.574395705.495FD323@webmail.messagingengine.com> Message-ID: Hi Felix - You are amazing! I was going to send you a ping that we had added room names to talks and tutorials but you spotted it on your own over the weekend. On Sun, Apr 10, 2016 at 12:11 PM, Felix Crux wrote: > Hi Ewa et al., > > Most of the stuff for the guide I can figure out, but there are a few > items that I'll need from others. None are urgent. I think this is all of > them: > > 1) Venue floor plan. I know you're already working on this since you > mentioned it in a previous email, but I'm listing it here for completeness. > Yes and as soon as it is done, I will send it to you. It looks like Guidebook will be able to add location markers for all of the talks and sessions so then people can see a geo marks for the places they want to go. > > 2) Surveys. I believe there was a basic post-tutorial survey set up last > year. We can re-use it or design a new one from scratch. We can have > different ones for talks vs. tutorials, etc. > The survey data gathered through Guidebook was almost impossible to turn into useful charts and graphs. It was only good for open ended questions. Because of this, we will go back to SurveyMonkey for the surveys. Once gears is setup, Betsy and I can go in and add in the survey links to help out. > > 3) YouTube page URL. I'm guessing this hasn't been set up yet, but it > would be great if we could link to it before the conference, so people know > where to check once videos start being uploaded. > I have asked David for a new URL and will send soon. Thanks again for getting this all done. -------------- next part -------------- An HTML attachment was scrubbed... URL: From felixc at felixcrux.com Mon Apr 11 15:14:38 2016 From: felixc at felixcrux.com (Felix Crux) Date: Mon, 11 Apr 2016 15:14:38 -0400 Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team! In-Reply-To: References: <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com> <20160410165927.GA1034@mir.felixcrux.com> Message-ID: <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com> No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (

)? If it doesn't matter I'll likely go with paragraphs. What about other formatting, like Markdown headings; should they be turned into

s etc? Bolded text that's currently **like this** into or ? Or is everything else fine? Cheers, -- Felix -- Felix From builders at guidebook.zendesk.com Mon Apr 11 14:19:37 2016 From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook)) Date: Mon, 11 Apr 2016 18:19:37 +0000 Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team! In-Reply-To: References: <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com> <20160410165927.GA1034@mir.felixcrux.com> Message-ID: ##- 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 11, 11:19 AM Hi Felix, I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task. I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful. Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, Apr 10, 10:01 AM 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 Attachment(s): pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip ---------------------------------------------- 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/?name=pycon-2016-guidebook-data.zip ---------------------------------------------- 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/?name=Guide_Basics.xls ---------------------------------------------- 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] -------------- next part -------------- An HTML attachment was scrubbed... URL: From builders at guidebook.zendesk.com Mon Apr 11 15:17:19 2016 From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook)) Date: Mon, 11 Apr 2016 19:17:19 +0000 Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team! In-Reply-To: References: <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com> <20160410165927.GA1034@mir.felixcrux.com> <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com> Message-ID: ##- 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 11, 12:17 PM Hi Felix, Great to hear! For line breaks please you \ for single breaks and \\ for double. Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks? Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long! Thank you! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, Apr 11, 12:14 PM No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (

)? If it doesn't matter I'll likely go with paragraphs. What about other formatting, like Markdown headings; should they be turned into

s etc? Bolded text that's currently **like this** into or ? Or is everything else fine? Cheers, -- Felix -- Felix ---------------------------------------------- Carmen Kuncz, Apr 11, 11:19 AM Hi Felix, I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task. I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful. Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, Apr 10, 10:01 AM 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 Attachment(s): pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip ---------------------------------------------- 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/?name=pycon-2016-guidebook-data.zip ---------------------------------------------- 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/?name=Guide_Basics.xls ---------------------------------------------- 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] -------------- next part -------------- An HTML attachment was scrubbed... URL: From felixc at felixcrux.com Mon Apr 11 18:49:28 2016 From: felixc at felixcrux.com (Felix Crux) Date: Mon, 11 Apr 2016 18:49:28 -0400 Subject: [Pycon-mobile-guide] Items needed for mobile guide In-Reply-To: References: <1460308300.2837012.574395705.495FD323@webmail.messagingengine.com> Message-ID: <20160411224928.GA986@mir.felixcrux.com> It was just lucky timing :) I'll be doing a new export about once a week and checking for differences (one of the big benefits of automating as much as possible). If anything shows up, I'll highlight it and pass it on to Guidebook. Sounds good on all those items! Thanks for taking care of everything, -- Felix From felixc at felixcrux.com Mon Apr 11 19:10:35 2016 From: felixc at felixcrux.com (Felix Crux) Date: Mon, 11 Apr 2016 19:10:35 -0400 Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team! In-Reply-To: References: <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com> <20160410165927.GA1034@mir.felixcrux.com> <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com> Message-ID: <20160411231035.GB986@mir.felixcrux.com> Sounds good; I'll switch all newlines to
s. The reason I ask about bold etc. is that currently all descriptions (talks, speakers, tutorials, all of them) are in a text-based format called Markdown (but I'd be happy to convert it to whatever works for you). Markdown looks very much like plain text (it's meant to), but it actually contains formatting instructions. For example, italics are denoted by surrounding text in asterisks *like this*, and **double asterisks** mean bold. There's also stuff like links, and headings, which look like: ### I'm a heading! You can see some examples of this in the tutorials_schedule.csv file. Check out the tutorial called "Making an Impact with Python Natural Language Processing Tools". You can see how it looks online here: https://us.pycon.org/2016/schedule/presentation/1778/ Note how the description contains text like: ### Python Development Environment and how that becomes a headline on the web page. There are also links, like the one that reads: "[Python](http://python.org)". Finally, there's text that shows up in a fixed-width font using backticks (`), like `virtualenv`. Those examples would typically be translated into HTML tags like

, , and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix



On Mon, Apr 11 07:17, Carmen Kuncz (Guidebook) wrote:
> ##- 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 11, 12:17 PM
> 
> Hi Felix,
> 
> Great to hear! For line breaks please you \ for single breaks and \\ for double.
> Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?
> 
> Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!
> 
> Thank you!
> 
> Best,
> 
> Carmen
> 
> Carmen Kuncz
> Customer Success Associate
> Guidebook
> 
> ----------------------------------------------
> 
> Felix Crux, Apr 11, 12:14 PM
> 
> No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.
> 
> What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?
> 
> Cheers,
> 
> -- 
> Felix
> 
> -- 
> Felix
> 
> ----------------------------------------------
> 
> Carmen Kuncz, Apr 11, 11:19 AM
> 
> Hi Felix,
> 
> I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.
> 
> I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.
> 
> Best,
> 
> Carmen
> 
> Carmen Kuncz
> Customer Success Associate
> Guidebook
> 
> ----------------------------------------------
> 
> Felix Crux, Apr 10, 10:01 AM
> 
> 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
> 
> Attachment(s):
> pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip
> 
> ----------------------------------------------
> 
> 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/?name=pycon-2016-guidebook-data.zip
> 
> ----------------------------------------------
> 
> 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/?name=Guide_Basics.xls
> 
> ----------------------------------------------
> 
> 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]

From felixc at felixcrux.com  Mon Apr 11 20:10:41 2016
From: felixc at felixcrux.com (Felix Crux)
Date: Mon, 11 Apr 2016 20:10:41 -0400
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide
 Building Team!
In-Reply-To: 
References: 
 
 
 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 
Message-ID: <20160412001041.GC986@mir.felixcrux.com>

That sounds great; thank you for the info! That's pretty much all the kinds
of formatting Markdown has, so that makes things much easier. I'll work on
this over the next few evenings and have an updated version for you later
this week. Thanks for the help!

-- 
Felix


On Tue, Apr 12 12:08, Carmen Kuncz (Guidebook) wrote:
> ##- 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 11, 5:08 PM
> 
> Hi Felix,
> 
> I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \ 
> I hope this clarifies everything! Please let me know if you have any other questions!
> 
> Best,
> 
> Carmen
> 
> Carmen Kuncz
> Customer Success Associate
> Guidebook
> 
> ----------------------------------------------
> 
> Felix Crux, Apr 11, 4:11 PM
> 
> Sounds good; I'll switch all newlines to 
s.
> 
> The reason I ask about bold etc. is that currently all descriptions (talks,
> speakers, tutorials, all of them) are in a text-based format called Markdown
> (but I'd be happy to convert it to whatever works for you).
> 
> Markdown looks very much like plain text (it's meant to), but it actually
> contains formatting instructions. For example, italics are denoted by
> surrounding text in asterisks *like this*, and **double asterisks** mean
> bold. There's also stuff like links, and headings, which look like:
> 
>  ### I'm a heading!
> 
> You can see some examples of this in the tutorials_schedule.csv file. Check
> out the tutorial called "Making an Impact with Python Natural Language
> Processing Tools". You can see how it looks online here:
> https://us.pycon.org/2016/schedule/presentation/1778/
> 
> Note how the description contains text like:
>  ### Python Development Environment
> and how that becomes a headline on the web page. There are also links, like
> the one that reads: "[Python](http://python.org)". Finally, there's text
> that shows up in a fixed-width font using backticks (`), like `virtualenv`.
> 
> Those examples would typically be translated into HTML tags like 
, ,
> and 
 or .
> 
> If you can summarize for me what formatting exactly the app can handle, I
> can convert everything to use it. For things that aren't supported (like
> bold) I'll at least remove the extra stuff, so we don't get silly
> double-asterisks in the app text.
> 
> Sorry for the mixup; I don't know what formatting the app can use, so I left
> everything in Markdown and mentioned it in the original email. I'd be happy
> to convert it to whatever works! Cheers,
> 
> --
> Felix
> 
> ----------------------------------------------
> 
> Carmen Kuncz, Apr 11, 12:17 PM
> 
> Hi Felix,
> 
> Great to hear! For line breaks please you \ for single breaks and \\ for double.
> Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?
> 
> Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!
> 
> Thank you!
> 
> Best,
> 
> Carmen
> 
> Carmen Kuncz
> Customer Success Associate
> Guidebook
> 
> ----------------------------------------------
> 
> Felix Crux, Apr 11, 12:14 PM
> 
> No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.
> 
> What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?
> 
> Cheers,
> 
> -- 
> Felix
> 
> -- 
> Felix
> 
> ----------------------------------------------
> 
> Carmen Kuncz, Apr 11, 11:19 AM
> 
> Hi Felix,
> 
> I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.
> 
> I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.
> 
> Best,
> 
> Carmen
> 
> Carmen Kuncz
> Customer Success Associate
> Guidebook
> 
> ----------------------------------------------
> 
> Felix Crux, Apr 10, 10:01 AM
> 
> 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
> 
> Attachment(s):
> pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip
> 
> ----------------------------------------------
> 
> 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/?name=pycon-2016-guidebook-data.zip
> 
> ----------------------------------------------
> 
> 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/?name=Guide_Basics.xls
> 
> ----------------------------------------------
> 
> 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]

-- 
Felix

From builders at guidebook.zendesk.com  Mon Apr 11 20:08:45 2016
From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook))
Date: Tue, 12 Apr 2016 00:08:45 +0000
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building
 Team!
In-Reply-To: 
 
References: 
 
 
 
 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
Message-ID: 

##- 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 11, 5:08 PM

Hi Felix,

I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \s.

The reason I ask about bold etc. is that currently all descriptions (talks,
speakers, tutorials, all of them) are in a text-based format called Markdown
(but I'd be happy to convert it to whatever works for you).

Markdown looks very much like plain text (it's meant to), but it actually
contains formatting instructions. For example, italics are denoted by
surrounding text in asterisks *like this*, and **double asterisks** mean
bold. There's also stuff like links, and headings, which look like:

 ### I'm a heading!

You can see some examples of this in the tutorials_schedule.csv file. Check
out the tutorial called "Making an Impact with Python Natural Language
Processing Tools". You can see how it looks online here:
https://us.pycon.org/2016/schedule/presentation/1778/

Note how the description contains text like:
 ### Python Development Environment
and how that becomes a headline on the web page. There are also links, like
the one that reads: "[Python](http://python.org)". Finally, there's text
that shows up in a fixed-width font using backticks (`), like `virtualenv`.

Those examples would typically be translated into HTML tags like 
, ,
and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 12:17 PM

Hi Felix,

Great to hear! For line breaks please you \ for single breaks and \\ for double.
Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?

Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!

Thank you!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 12:14 PM

No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.

What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?

Cheers,

-- 
Felix

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 11:19 AM

Hi Felix,

I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.

I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 10, 10:01 AM

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

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=Guide_Basics.xls

----------------------------------------------

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From builders at guidebook.zendesk.com  Mon Apr 11 20:21:37 2016
From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook))
Date: Tue, 12 Apr 2016 00:21:37 +0000
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building
 Team!
In-Reply-To: 
 
References: 
 
 
 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
Message-ID: 

##- 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 11, 5:21 PM

Hi Felix,

Great thank you so much! I very much appreciate it. I just had a conversation with my manager about the html tags and he warned me that italics and u are currently not working on our software.

Sorry for the conflicting information! Thank you!

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 5:11 PM

That sounds great; thank you for the info! That's pretty much all the kinds
of formatting Markdown has, so that makes things much easier. I'll work on
this over the next few evenings and have an updated version for you later
this week. Thanks for the help!

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 5:08 PM

Hi Felix,

I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \s.

The reason I ask about bold etc. is that currently all descriptions (talks,
speakers, tutorials, all of them) are in a text-based format called Markdown
(but I'd be happy to convert it to whatever works for you).

Markdown looks very much like plain text (it's meant to), but it actually
contains formatting instructions. For example, italics are denoted by
surrounding text in asterisks *like this*, and **double asterisks** mean
bold. There's also stuff like links, and headings, which look like:

 ### I'm a heading!

You can see some examples of this in the tutorials_schedule.csv file. Check
out the tutorial called "Making an Impact with Python Natural Language
Processing Tools". You can see how it looks online here:
https://us.pycon.org/2016/schedule/presentation/1778/

Note how the description contains text like:
 ### Python Development Environment
and how that becomes a headline on the web page. There are also links, like
the one that reads: "[Python](http://python.org)". Finally, there's text
that shows up in a fixed-width font using backticks (`), like `virtualenv`.

Those examples would typically be translated into HTML tags like 
, ,
and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 12:17 PM

Hi Felix,

Great to hear! For line breaks please you \ for single breaks and \\ for double.
Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?

Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!

Thank you!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 12:14 PM

No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.

What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?

Cheers,

-- 
Felix

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 11:19 AM

Hi Felix,

I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.

I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 10, 10:01 AM

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

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=Guide_Basics.xls

----------------------------------------------

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From builders at guidebook.zendesk.com  Thu Apr 14 15:10:11 2016
From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook))
Date: Thu, 14 Apr 2016 19:10:11 +0000
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building
 Team!
In-Reply-To: 
 
References: 
 
 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
Message-ID: 

##- 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 14, 12:10 PM

Hi Felix,

Thank you so much for getting this back to me! I am going to start uploading this content! I hope a preview will be available for you within the next couple days! I will keep you updated on my progress and let you know if I run into any problems with the HTML!

Thanks again!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 13, 5:24 PM

All right; that should do it! Attached is the latest version of the data.

The most notable change is of course that all the Markdown has been converted
to HTML. There are a few other things included too:

* New posters: "Building Python with Gradle" and "The Breathing Earth"
* New bios: Gina Schmalzle and Stephen Holsapple
* New sponsor: Heroku
* Updated sponsor logos for Clover Health, PDT, and Keystone
* Several updated talk descriptions and speaker bios

How does it look? Let me know if any of the formatting is causing trouble, and
I'd be happy to tweak it some more. Approximately when could we start playing
around with a preview of the guide? Thanks!

-- 
Felix

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

Carmen Kuncz, Apr 11, 5:21 PM

Hi Felix,

Great thank you so much! I very much appreciate it. I just had a conversation with my manager about the html tags and he warned me that italics and u are currently not working on our software.

Sorry for the conflicting information! Thank you!

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 5:11 PM

That sounds great; thank you for the info! That's pretty much all the kinds
of formatting Markdown has, so that makes things much easier. I'll work on
this over the next few evenings and have an updated version for you later
this week. Thanks for the help!

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 5:08 PM

Hi Felix,

I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \s.

The reason I ask about bold etc. is that currently all descriptions (talks,
speakers, tutorials, all of them) are in a text-based format called Markdown
(but I'd be happy to convert it to whatever works for you).

Markdown looks very much like plain text (it's meant to), but it actually
contains formatting instructions. For example, italics are denoted by
surrounding text in asterisks *like this*, and **double asterisks** mean
bold. There's also stuff like links, and headings, which look like:

 ### I'm a heading!

You can see some examples of this in the tutorials_schedule.csv file. Check
out the tutorial called "Making an Impact with Python Natural Language
Processing Tools". You can see how it looks online here:
https://us.pycon.org/2016/schedule/presentation/1778/

Note how the description contains text like:
 ### Python Development Environment
and how that becomes a headline on the web page. There are also links, like
the one that reads: "[Python](http://python.org)". Finally, there's text
that shows up in a fixed-width font using backticks (`), like `virtualenv`.

Those examples would typically be translated into HTML tags like 
, ,
and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 12:17 PM

Hi Felix,

Great to hear! For line breaks please you \ for single breaks and \\ for double.
Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?

Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!

Thank you!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 12:14 PM

No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.

What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?

Cheers,

-- 
Felix

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 11:19 AM

Hi Felix,

I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.

I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 10, 10:01 AM

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

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=Guide_Basics.xls

----------------------------------------------

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From ewa at python.org  Thu Apr 21 10:55:14 2016
From: ewa at python.org (Ewa Jodlowska)
Date: Thu, 21 Apr 2016 09:55:14 -0500
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide
 Building Team!
In-Reply-To: 
References: 
 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 
Message-ID: 

Hi Carmen,

Can we access our guide in gears yet? I would love to be able to access to
Guidebook promotional material as I am working on printing signs for our
conference this week.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

On Thu, Apr 14, 2016 at 2:10 PM, Carmen Kuncz (Guidebook) <
builders at guidebook.zendesk.com> wrote:

> ##- 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
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 14, 12:10 PM
> Hi Felix,
>
> Thank you so much for getting this back to me! I am going to start
> uploading this content! I hope a preview will be available for you within
> the next couple days! I will keep you updated on my progress and let you
> know if I run into any problems with the HTML!
>
> Thanks again!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 13, 5:24 PM
>
> All right; that should do it! Attached is the latest version of the data.
>
> The most notable change is of course that all the Markdown has been
> converted
> to HTML. There are a few other things included too:
>
> * New posters: "Building Python with Gradle" and "The Breathing Earth"
> * New bios: Gina Schmalzle and Stephen Holsapple
> * New sponsor: Heroku
> * Updated sponsor logos for Clover Health, PDT, and Keystone
> * Several updated talk descriptions and speaker bios
>
> How does it look? Let me know if any of the formatting is causing trouble,
> and
> I'd be happy to tweak it some more. Approximately when could we start
> playing
> around with a preview of the guide? Thanks!
>
> --
> Felix
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:21 PM
> Hi Felix,
>
> Great thank you so much! I very much appreciate it. I just had a
> conversation with my manager about the html tags and he warned me that
> italics and u are currently not working on our software.
>
> Sorry for the conflicting information! Thank you!
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 5:11 PM
>
> That sounds great; thank you for the info! That's pretty much all the kinds
> of formatting Markdown has, so that makes things much easier. I'll work on
> this over the next few evenings and have an updated version for you later
> this week. Thanks for the help!
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:08 PM
> Hi Felix,
>
> I was not aware of Markdown. I also was misinformed about bold html. The
> following tags will work within our template: a, b, br, i, ul, li, p,
> h1-h6, span, , 
> I hope this clarifies everything! Please let me know if you have any other
> questions!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 4:11 PM
>
> Sounds good; I'll switch all newlines to 
s.
>
> The reason I ask about bold etc. is that currently all descriptions (talks,
> speakers, tutorials, all of them) are in a text-based format called
> Markdown
> (but I'd be happy to convert it to whatever works for you).
>
> Markdown looks very much like plain text (it's meant to), but it actually
> contains formatting instructions. For example, italics are denoted by
> surrounding text in asterisks *like this*, and **double asterisks** mean
> bold. There's also stuff like links, and headings, which look like:
>
> ### I'm a heading!
>
> You can see some examples of this in the tutorials_schedule.csv file. Check
> out the tutorial called "Making an Impact with Python Natural Language
> Processing Tools". You can see how it looks online here:
> https://us.pycon.org/2016/schedule/presentation/1778/
>
> Note how the description contains text like:
> ### Python Development Environment
> and how that becomes a headline on the web page. There are also links, like
> the one that reads: "[Python](http://python.org)". Finally, there's text
> that shows up in a fixed-width font using backticks (`), like `virtualenv`.
>
> Those examples would typically be translated into HTML tags like 
, ,
> and 
 or .
>
> If you can summarize for me what formatting exactly the app can handle, I
> can convert everything to use it. For things that aren't supported (like
> bold) I'll at least remove the extra stuff, so we don't get silly
> double-asterisks in the app text.
>
> Sorry for the mixup; I don't know what formatting the app can use, so I
> left
> everything in Markdown and mentioned it in the original email. I'd be happy
> to convert it to whatever works! Cheers,
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 12:17 PM
> Hi Felix,
>
> Great to hear! For line breaks please you 
 for single breaks and
> 

 for double.
> Unfortunately our software does not allow for us to included bolded
> formatting. However, I dont see any bolded text in the files you have sent
> me so far? I only see the need for line breaks?
>
> Once I have the updated materials (the schedule is complete so that is not
> necessary), the process for me uploaded the content shouldn't take very
> long!
>
> Thank you!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 12:14 PM
>
> No problem; I'll get that to you ASAP. Would it be better to use line
> breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with
> paragraphs.
>
> What about other formatting, like Markdown headings; should they be turned
> into 
s etc? Bolded text that's currently **like this** into  or
> ? Or is everything else fine?
>
> Cheers,
>
> --
> Felix
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 11:19 AM
> Hi Felix,
>
> I have been working on the guide but have run into a bit of a time
> consuming task. For our templates, in order to maintain the format we need
> to add html tags for the line breaks. Is there anyway for you to pull the
> descriptions, abstracts,presenter information, etc for each list with html
> tags? I just completed the schedule but it required me manually adding tags
> to each individual item description which is quite a time consuming task.
>
> I will continue to work on maintaining the format and I appreciate your
> patience. If there is anyway we can get the html format within the
> descriptions please let me know as this would be extraordinarily helpful.
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 10, 10:01 AM
>
> 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
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Felix Crux]
>
> *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
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
> 
>
> [image: Katie Herr]
>
> *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. Delivered by Zendesk
> .
> [N2DQPZ-696N]
>
> _______________________________________________
> Pycon-mobile-guide mailing list
> Pycon-mobile-guide at python.org
> https://mail.python.org/mailman/listinfo/pycon-mobile-guide
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From builders at guidebook.zendesk.com  Thu Apr 21 19:04:38 2016
From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook))
Date: Thu, 21 Apr 2016 23:04:38 +0000
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building
 Team!
In-Reply-To: 
 
 
References: 
 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
Message-ID: 

##- 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 21, 4:04 PM

Hi Ewa,

I am still working on the guide. There is a mix of last year and this year's stuff on it. I will work on trying to get you access to the guide tomorrow!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 21, 7:55 AM

Hi Carmen,

Can we access our guide in gears yet? I would love to be able to access to Guidebook promotional material as I am working on printing signs for our conference this week.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 14, 12:10 PM

Hi Felix,

Thank you so much for getting this back to me! I am going to start uploading this content! I hope a preview will be available for you within the next couple days! I will keep you updated on my progress and let you know if I run into any problems with the HTML!

Thanks again!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 13, 5:24 PM

All right; that should do it! Attached is the latest version of the data.

The most notable change is of course that all the Markdown has been converted
to HTML. There are a few other things included too:

* New posters: "Building Python with Gradle" and "The Breathing Earth"
* New bios: Gina Schmalzle and Stephen Holsapple
* New sponsor: Heroku
* Updated sponsor logos for Clover Health, PDT, and Keystone
* Several updated talk descriptions and speaker bios

How does it look? Let me know if any of the formatting is causing trouble, and
I'd be happy to tweak it some more. Approximately when could we start playing
around with a preview of the guide? Thanks!

-- 
Felix

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

Carmen Kuncz, Apr 11, 5:21 PM

Hi Felix,

Great thank you so much! I very much appreciate it. I just had a conversation with my manager about the html tags and he warned me that italics and u are currently not working on our software.

Sorry for the conflicting information! Thank you!

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 5:11 PM

That sounds great; thank you for the info! That's pretty much all the kinds
of formatting Markdown has, so that makes things much easier. I'll work on
this over the next few evenings and have an updated version for you later
this week. Thanks for the help!

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 5:08 PM

Hi Felix,

I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \s.

The reason I ask about bold etc. is that currently all descriptions (talks,
speakers, tutorials, all of them) are in a text-based format called Markdown
(but I'd be happy to convert it to whatever works for you).

Markdown looks very much like plain text (it's meant to), but it actually
contains formatting instructions. For example, italics are denoted by
surrounding text in asterisks *like this*, and **double asterisks** mean
bold. There's also stuff like links, and headings, which look like:

 ### I'm a heading!

You can see some examples of this in the tutorials_schedule.csv file. Check
out the tutorial called "Making an Impact with Python Natural Language
Processing Tools". You can see how it looks online here:
https://us.pycon.org/2016/schedule/presentation/1778/

Note how the description contains text like:
 ### Python Development Environment
and how that becomes a headline on the web page. There are also links, like
the one that reads: "[Python](http://python.org)". Finally, there's text
that shows up in a fixed-width font using backticks (`), like `virtualenv`.

Those examples would typically be translated into HTML tags like 
, ,
and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 12:17 PM

Hi Felix,

Great to hear! For line breaks please you \ for single breaks and \\ for double.
Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?

Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!

Thank you!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 12:14 PM

No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.

What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?

Cheers,

-- 
Felix

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 11:19 AM

Hi Felix,

I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.

I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 10, 10:01 AM

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

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=Guide_Basics.xls

----------------------------------------------

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From builders at guidebook.zendesk.com  Fri Apr 22 15:26:41 2016
From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook))
Date: Fri, 22 Apr 2016 19:26:41 +0000
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building
 Team!
In-Reply-To: 
 
References: 
 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
Message-ID: 

##- 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 22, 12:26 PM

Hi Ewa and Felix,

The guide has been update with all content sent with the exception of the "presentations" folder. I hope to have this last part of the guide done soon!

Are either one of you familiar with Builder and or have an account within it?

Please let me know so I can get you set up with how to preview the guide!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Carmen Kuncz, Apr 21, 4:04 PM

Hi Ewa,

I am still working on the guide. There is a mix of last year and this year's stuff on it. I will work on trying to get you access to the guide tomorrow!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 21, 7:55 AM

Hi Carmen,

Can we access our guide in gears yet? I would love to be able to access to Guidebook promotional material as I am working on printing signs for our conference this week.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 14, 12:10 PM

Hi Felix,

Thank you so much for getting this back to me! I am going to start uploading this content! I hope a preview will be available for you within the next couple days! I will keep you updated on my progress and let you know if I run into any problems with the HTML!

Thanks again!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 13, 5:24 PM

All right; that should do it! Attached is the latest version of the data.

The most notable change is of course that all the Markdown has been converted
to HTML. There are a few other things included too:

* New posters: "Building Python with Gradle" and "The Breathing Earth"
* New bios: Gina Schmalzle and Stephen Holsapple
* New sponsor: Heroku
* Updated sponsor logos for Clover Health, PDT, and Keystone
* Several updated talk descriptions and speaker bios

How does it look? Let me know if any of the formatting is causing trouble, and
I'd be happy to tweak it some more. Approximately when could we start playing
around with a preview of the guide? Thanks!

-- 
Felix

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

Carmen Kuncz, Apr 11, 5:21 PM

Hi Felix,

Great thank you so much! I very much appreciate it. I just had a conversation with my manager about the html tags and he warned me that italics and u are currently not working on our software.

Sorry for the conflicting information! Thank you!

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 5:11 PM

That sounds great; thank you for the info! That's pretty much all the kinds
of formatting Markdown has, so that makes things much easier. I'll work on
this over the next few evenings and have an updated version for you later
this week. Thanks for the help!

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 5:08 PM

Hi Felix,

I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \s.

The reason I ask about bold etc. is that currently all descriptions (talks,
speakers, tutorials, all of them) are in a text-based format called Markdown
(but I'd be happy to convert it to whatever works for you).

Markdown looks very much like plain text (it's meant to), but it actually
contains formatting instructions. For example, italics are denoted by
surrounding text in asterisks *like this*, and **double asterisks** mean
bold. There's also stuff like links, and headings, which look like:

 ### I'm a heading!

You can see some examples of this in the tutorials_schedule.csv file. Check
out the tutorial called "Making an Impact with Python Natural Language
Processing Tools". You can see how it looks online here:
https://us.pycon.org/2016/schedule/presentation/1778/

Note how the description contains text like:
 ### Python Development Environment
and how that becomes a headline on the web page. There are also links, like
the one that reads: "[Python](http://python.org)". Finally, there's text
that shows up in a fixed-width font using backticks (`), like `virtualenv`.

Those examples would typically be translated into HTML tags like 
, ,
and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 12:17 PM

Hi Felix,

Great to hear! For line breaks please you \ for single breaks and \\ for double.
Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?

Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!

Thank you!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 12:14 PM

No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.

What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?

Cheers,

-- 
Felix

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 11:19 AM

Hi Felix,

I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.

I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 10, 10:01 AM

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

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=Guide_Basics.xls

----------------------------------------------

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From ewa at python.org  Mon Apr 25 15:09:48 2016
From: ewa at python.org (Ewa Jodlowska)
Date: Mon, 25 Apr 2016 14:09:48 -0500
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide
 Building Team!
In-Reply-To: 
References: 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 
 
Message-ID: 

Hi Carmen,

Thank you for working on this. I have an account on
https://gears.guidebook.com/ and so does Felix. Mine is under ewa at python.org
and I believe Felix's is under felixc at felixcrux.com.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

On Fri, Apr 22, 2016 at 2:26 PM, Carmen Kuncz (Guidebook) <
builders at guidebook.zendesk.com> wrote:

> ##- 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
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 22, 12:26 PM
> Hi Ewa and Felix,
>
> The guide has been update with all content sent with the exception of the
> "presentations" folder. I hope to have this last part of the guide done
> soon!
>
> Are either one of you familiar with Builder and or have an account within
> it?
>
> Please let me know so I can get you set up with how to preview the guide!
>
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 21, 4:04 PM
> Hi Ewa,
>
> I am still working on the guide. There is a mix of last year and this
> year's stuff on it. I will work on trying to get you access to the guide
> tomorrow!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 21, 7:55 AM
>
> Hi Carmen,
>
> Can we access our guide in gears yet? I would love to be able to access to
> Guidebook promotional material as I am working on printing signs for our
> conference this week.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 14, 12:10 PM
> Hi Felix,
>
> Thank you so much for getting this back to me! I am going to start
> uploading this content! I hope a preview will be available for you within
> the next couple days! I will keep you updated on my progress and let you
> know if I run into any problems with the HTML!
>
> Thanks again!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 13, 5:24 PM
>
> All right; that should do it! Attached is the latest version of the data.
>
> The most notable change is of course that all the Markdown has been
> converted
> to HTML. There are a few other things included too:
>
> * New posters: "Building Python with Gradle" and "The Breathing Earth"
> * New bios: Gina Schmalzle and Stephen Holsapple
> * New sponsor: Heroku
> * Updated sponsor logos for Clover Health, PDT, and Keystone
> * Several updated talk descriptions and speaker bios
>
> How does it look? Let me know if any of the formatting is causing trouble,
> and
> I'd be happy to tweak it some more. Approximately when could we start
> playing
> around with a preview of the guide? Thanks!
>
> --
> Felix
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:21 PM
> Hi Felix,
>
> Great thank you so much! I very much appreciate it. I just had a
> conversation with my manager about the html tags and he warned me that
> italics and u are currently not working on our software.
>
> Sorry for the conflicting information! Thank you!
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 5:11 PM
>
> That sounds great; thank you for the info! That's pretty much all the kinds
> of formatting Markdown has, so that makes things much easier. I'll work on
> this over the next few evenings and have an updated version for you later
> this week. Thanks for the help!
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:08 PM
> Hi Felix,
>
> I was not aware of Markdown. I also was misinformed about bold html. The
> following tags will work within our template: a, b, br, i, ul, li, p,
> h1-h6, span, , 
> I hope this clarifies everything! Please let me know if you have any other
> questions!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 4:11 PM
>
> Sounds good; I'll switch all newlines to 
s.
>
> The reason I ask about bold etc. is that currently all descriptions (talks,
> speakers, tutorials, all of them) are in a text-based format called
> Markdown
> (but I'd be happy to convert it to whatever works for you).
>
> Markdown looks very much like plain text (it's meant to), but it actually
> contains formatting instructions. For example, italics are denoted by
> surrounding text in asterisks *like this*, and **double asterisks** mean
> bold. There's also stuff like links, and headings, which look like:
>
> ### I'm a heading!
>
> You can see some examples of this in the tutorials_schedule.csv file. Check
> out the tutorial called "Making an Impact with Python Natural Language
> Processing Tools". You can see how it looks online here:
> https://us.pycon.org/2016/schedule/presentation/1778/
>
> Note how the description contains text like:
> ### Python Development Environment
> and how that becomes a headline on the web page. There are also links, like
> the one that reads: "[Python](http://python.org)". Finally, there's text
> that shows up in a fixed-width font using backticks (`), like `virtualenv`.
>
> Those examples would typically be translated into HTML tags like 
, ,
> and 
 or .
>
> If you can summarize for me what formatting exactly the app can handle, I
> can convert everything to use it. For things that aren't supported (like
> bold) I'll at least remove the extra stuff, so we don't get silly
> double-asterisks in the app text.
>
> Sorry for the mixup; I don't know what formatting the app can use, so I
> left
> everything in Markdown and mentioned it in the original email. I'd be happy
> to convert it to whatever works! Cheers,
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 12:17 PM
> Hi Felix,
>
> Great to hear! For line breaks please you 
 for single breaks and
> 

 for double.
> Unfortunately our software does not allow for us to included bolded
> formatting. However, I dont see any bolded text in the files you have sent
> me so far? I only see the need for line breaks?
>
> Once I have the updated materials (the schedule is complete so that is not
> necessary), the process for me uploaded the content shouldn't take very
> long!
>
> Thank you!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 12:14 PM
>
> No problem; I'll get that to you ASAP. Would it be better to use line
> breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with
> paragraphs.
>
> What about other formatting, like Markdown headings; should they be turned
> into 
s etc? Bolded text that's currently **like this** into  or
> ? Or is everything else fine?
>
> Cheers,
>
> --
> Felix
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 11:19 AM
> Hi Felix,
>
> I have been working on the guide but have run into a bit of a time
> consuming task. For our templates, in order to maintain the format we need
> to add html tags for the line breaks. Is there anyway for you to pull the
> descriptions, abstracts,presenter information, etc for each list with html
> tags? I just completed the schedule but it required me manually adding tags
> to each individual item description which is quite a time consuming task.
>
> I will continue to work on maintaining the format and I appreciate your
> patience. If there is anyway we can get the html format within the
> descriptions please let me know as this would be extraordinarily helpful.
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 10, 10:01 AM
>
> 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
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Felix Crux]
>
> *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
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
> 
>
> [image: Katie Herr]
>
> *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. Delivered by Zendesk
> .
> [N2DQPZ-696N]
>
> _______________________________________________
> Pycon-mobile-guide mailing list
> Pycon-mobile-guide at python.org
> https://mail.python.org/mailman/listinfo/pycon-mobile-guide
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From builders at guidebook.zendesk.com  Mon Apr 25 18:31:19 2016
From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook))
Date: Mon, 25 Apr 2016 22:31:19 +0000
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building
 Team!
In-Reply-To: 
 
 
References: 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
Message-ID: 

##- 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 25, 3:31 PM

Hi Ewa and Felix,

I just sent you both invitations to be admins on the guide. Our new website is builder.guidebook.com, please refrain from using gears!

Please let me know if you have any questions! I should have the last bit of content uploaded soon!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 25, 12:09 PM

Hi Carmen,

Thank you for working on this. I have an account on https://gears.guidebook.com/ and so does Felix. Mine is under ewa at python.org and I believe Felix's is under felixc at felixcrux.com. 

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 22, 12:26 PM

Hi Ewa and Felix,

The guide has been update with all content sent with the exception of the "presentations" folder. I hope to have this last part of the guide done soon!

Are either one of you familiar with Builder and or have an account within it?

Please let me know so I can get you set up with how to preview the guide!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Carmen Kuncz, Apr 21, 4:04 PM

Hi Ewa,

I am still working on the guide. There is a mix of last year and this year's stuff on it. I will work on trying to get you access to the guide tomorrow!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 21, 7:55 AM

Hi Carmen,

Can we access our guide in gears yet? I would love to be able to access to Guidebook promotional material as I am working on printing signs for our conference this week.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 14, 12:10 PM

Hi Felix,

Thank you so much for getting this back to me! I am going to start uploading this content! I hope a preview will be available for you within the next couple days! I will keep you updated on my progress and let you know if I run into any problems with the HTML!

Thanks again!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 13, 5:24 PM

All right; that should do it! Attached is the latest version of the data.

The most notable change is of course that all the Markdown has been converted
to HTML. There are a few other things included too:

* New posters: "Building Python with Gradle" and "The Breathing Earth"
* New bios: Gina Schmalzle and Stephen Holsapple
* New sponsor: Heroku
* Updated sponsor logos for Clover Health, PDT, and Keystone
* Several updated talk descriptions and speaker bios

How does it look? Let me know if any of the formatting is causing trouble, and
I'd be happy to tweak it some more. Approximately when could we start playing
around with a preview of the guide? Thanks!

-- 
Felix

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

Carmen Kuncz, Apr 11, 5:21 PM

Hi Felix,

Great thank you so much! I very much appreciate it. I just had a conversation with my manager about the html tags and he warned me that italics and u are currently not working on our software.

Sorry for the conflicting information! Thank you!

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 5:11 PM

That sounds great; thank you for the info! That's pretty much all the kinds
of formatting Markdown has, so that makes things much easier. I'll work on
this over the next few evenings and have an updated version for you later
this week. Thanks for the help!

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 5:08 PM

Hi Felix,

I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \s.

The reason I ask about bold etc. is that currently all descriptions (talks,
speakers, tutorials, all of them) are in a text-based format called Markdown
(but I'd be happy to convert it to whatever works for you).

Markdown looks very much like plain text (it's meant to), but it actually
contains formatting instructions. For example, italics are denoted by
surrounding text in asterisks *like this*, and **double asterisks** mean
bold. There's also stuff like links, and headings, which look like:

 ### I'm a heading!

You can see some examples of this in the tutorials_schedule.csv file. Check
out the tutorial called "Making an Impact with Python Natural Language
Processing Tools". You can see how it looks online here:
https://us.pycon.org/2016/schedule/presentation/1778/

Note how the description contains text like:
 ### Python Development Environment
and how that becomes a headline on the web page. There are also links, like
the one that reads: "[Python](http://python.org)". Finally, there's text
that shows up in a fixed-width font using backticks (`), like `virtualenv`.

Those examples would typically be translated into HTML tags like 
, ,
and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 12:17 PM

Hi Felix,

Great to hear! For line breaks please you \ for single breaks and \\ for double.
Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?

Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!

Thank you!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 12:14 PM

No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.

What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?

Cheers,

-- 
Felix

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 11:19 AM

Hi Felix,

I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.

I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 10, 10:01 AM

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

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=Guide_Basics.xls

----------------------------------------------

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From felixc at felixcrux.com  Mon Apr 25 20:57:40 2016
From: felixc at felixcrux.com (Felix Crux)
Date: Mon, 25 Apr 2016 20:57:40 -0400
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide
 Building Team!
In-Reply-To: 
References: 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 
Message-ID: <1461632260.1476398.589467641.37D3D4F6@webmail.messagingengine.com>

Thanks Carmen!
 
I can confirm I've now got access (had to click "accept" on the
invitation in the top right dropdown menu). I'll look through it over
the next few days and let you know if anything comes up.
 
I'll also get you new cover art & venue details to replace last year's.
 
I know I asked about this in the original email, but is there anything I
can do to make it easier to link speakers to their talks? Last year I
did it manually, but if there's something I can provide like a
spreadsheet in a certain format, I'd be happy to do so. Otherwise I
guess they'll need to be done by hand?
 
Cheers,
 
 
 
On Mon, Apr 25, 2016, at 18:31, Carmen Kuncz (Guidebook) wrote:
> ##- 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 Kun
> *Carmen Kuncz* (Guidebook)
> Apr 25, 3:31 PM
> Hi Ewa and Felix,
>
> I just sent you both invitations to be admins on the guide. Our new
> website is builder.guidebook.com, please refrain from using gears!
>
> Please let me know if you have any questions! I should have the last
> bit of content uploaded soon!
>
> Best,
>
> Carmen
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
>


> Ewa Jodlow
> *Ewa Jodlowska*
> Apr 25, 12:09 PM
> Hi Carmen,
> Thank you for working on this. I have an account on
> https://gears.guidebook.com/ and so does Felix. Mine is under
> ewa at python.org and I believe Felix's is under felixc at felixcrux.com.
> Best regards,
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>


> Carmen Kun
> *Carmen Kuncz* (Guidebook)
> Apr 22, 12:26 PM
> Hi Ewa and Felix,
>
> The guide has been update with all content sent with the exception of
> the "presentations" folder. I hope to have this last part of the guide
> done soon!
>
> Are either one of you familiar with Builder and or have an account
> within it?
>
> Please let me know so I can get you set up with how to preview
> the guide!
>
> Best,
>
> Carmen
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
>


> Carmen Kun
> *Carmen Kuncz* (Guidebook)
> Apr 21, 4:04 PM
> Hi Ewa,
>
> I am still working on the guide. There is a mix of last year and this
> year's stuff on it. I will work on trying to get you access to the
> guide tomorrow!
>
> Best,
>
> Carmen
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
>


> Ewa Jodlow
> *Ewa Jodlowska*
> Apr 21, 7:55 AM
> Hi Carmen,
> Can we access our guide in gears yet? I would love to be able to
> access to Guidebook promotional material as I am working on printing
> signs for our conference this week.
> Best regards,
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>


> Carmen Kun
> *Carmen Kuncz* (Guidebook)
> Apr 14, 12:10 PM
> Hi Felix,
>
> Thank you so much for getting this back to me! I am going to start
> uploading this content! I hope a preview will be available for you
> within the next couple days! I will keep you updated on my progress
> and let you know if I run into any problems with the HTML!
>
> Thanks again!
>
> Best,
>
> Carmen
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
>


> Felix Crux
> *Felix Crux*
> Apr 13, 5:24 PM
> All right; that should do it! Attached is the latest version of
> the data.
> The most notable change is of course that all the Markdown has been
> converted
> to HTML. There are a few other things included too:
> * New posters: "Building Python with Gradle" and "The Breathing Earth"
> * New bios: Gina Schmalzle and Stephen Holsapple
> * New sponsor: Heroku
> * Updated sponsor logos for Clover Health, PDT, and Keystone
> * Several updated talk descriptions and speaker bios
> How does it look? Let me know if any of the formatting is causing
> trouble, and
> I'd be happy to tweak it some more. Approximately when could we
> start playing
> around with a preview of the guide? Thanks!
> --
> Felix
> Attachment(s)
> pycon-2016-guidebook-data.zip[1]
>


> Carmen Kun
> *Carmen Kuncz* (Guidebook)
> Apr 11, 5:21 PM
> Hi Felix,
>
> Great thank you so much! I very much appreciate it. I just had a
> conversation with my manager about the html tags and he warned me that
> italics and u are currently not working on our software.
>
> Sorry for the conflicting information! Thank you!
>
> Carmen
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
>


> Felix Crux
> *Felix Crux*
> Apr 11, 5:11 PM
> That sounds great; thank you for the info! That's pretty much all
> the kinds
> of formatting Markdown has, so that makes things much easier.
> I'll work on
> this over the next few evenings and have an updated version for
> you later
> this week. Thanks for the help!
> --
> Felix
>


> Carmen Kun
> *Carmen Kuncz* (Guidebook)
> Apr 11, 5:08 PM
> Hi Felix,
>
> I was not aware of Markdown. I also was misinformed about bold html.
> The following tags will work within our template: a, b, br, i, ul, li,
> p, h1-h6, span, ,?
> I hope this clarifies everything! Please let me know if you have any
> other questions!
>
> Best,
>
> Carmen
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
>


> Felix Crux
> *Felix Crux*
> Apr 11, 4:11 PM
> Sounds good; I'll switch all newlines to 
s.
> The reason I ask about bold etc. is that currently all
> descriptions (talks,
> speakers, tutorials, all of them) are in a text-based format called
> Markdown
> (but I'd be happy to convert it to whatever works for you).
> Markdown looks very much like plain text (it's meant to), but it
> actually
> contains formatting instructions. For example, italics are denoted by
> surrounding text in asterisks *like this*, and **double
> asterisks** mean
> bold. There's also stuff like links, and headings, which look like:
> ### I'm a heading!
> You can see some examples of this in the tutorials_schedule.csv
> file. Check
> out the tutorial called "Making an Impact with Python Natural Language
> Processing Tools". You can see how it looks online here:
> https://us.pycon.org/2016/schedule/presentation/1778/
> Note how the description contains text like:
>  ### Python Development Environment
> and how that becomes a headline on the web page. There are also
> links, like
> the one that reads: "[Python](http://python.org)". Finally,
> there's text
> that shows up in a fixed-width font using backticks (`), like
> `virtualenv`.
> Those examples would typically be translated into HTML tags like
> 
, ,
> and 
 or .
> If you can summarize for me what formatting exactly the app can
> handle, I
> can convert everything to use it. For things that aren't
> supported (like
> bold) I'll at least remove the extra stuff, so we don't get silly
> double-asterisks in the app text.
> Sorry for the mixup; I don't know what formatting the app can use,
> so I left
> everything in Markdown and mentioned it in the original email. I'd
> be happy
> to convert it to whatever works! Cheers,
> --
> Felix
>


> Carmen Kun
> *Carmen Kuncz* (Guidebook)
> Apr 11, 12:17 PM
> Hi Felix,
>
> Great to hear! For line breaks please you 
 for single breaks and
> 

 for double.
> Unfortunately our software does not allow for us to included bolded
> formatting. However, I dont see any bolded text in the files you have
> sent me so far? I only see the need for line breaks?
>
> Once I have the updated materials (the schedule is complete so that is
> not necessary), the process for me uploaded the content shouldn't take
> very long!
>
> Thank you!
>
> Best,
>
> Carmen
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
>


> Felix Crux
> *Felix Crux*
> Apr 11, 12:14 PM
> No problem; I'll get that to you ASAP. Would it be better to use line
> breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go
> with paragraphs.
> What about other formatting, like Markdown headings; should they be
> turned into 
s etc? Bolded text that's currently **like this** into
>  or ? Or is everything else fine?
> Cheers,
> --
> Felix
> --
> Felix
>


> Carmen Kun
> *Carmen Kuncz* (Guidebook)
> Apr 11, 11:19 AM
> Hi Felix,
>
> I have been working on the guide but have run into a bit of a time
> consuming task. For our templates, in order to maintain the format we
> need to add html tags for the line breaks. Is there anyway for you to
> pull the descriptions,?abstracts,presenter information, etc for each
> list?with html tags? I just completed the schedule but it required me
> manually adding tags to each individual item description which is
> quite a time consuming task.
>
> I will continue to work on maintaining the format and I appreciate
> your patience. If there is anyway we can get the html format within
> the descriptions please let me know as this would be extraordinarily
> helpful.
>
> Best,
>
> Carmen
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
>


> Felix Crux
> *Felix Crux*
> Apr 10, 10:01 AM
> 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
> Attachment(s)
> pycon-2016-guidebook-data.zip[2]
>


> Carmen Kun
> *Carmen Kuncz* (Guidebook)
> 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
> *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[3]
>


> Carmen Kun
> *Carmen Kuncz* (Guidebook)
> 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 Jodlow
> *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 Kun
> *Carmen Kuncz* (Guidebook)
> 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 Kun
> *Carmen Kuncz* (Guidebook)
> 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 Jodlow
> *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 Kun
> *Carmen Kuncz* (Guidebook)
> 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 Jodlow
> *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 Kun
> *Carmen Kuncz* (Guidebook)
> 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 Jodlow
> *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 Kun
> *Carmen Kuncz* (Guidebook)
> 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[4]
>


> Katie Herr
> *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.  Delivered by Zendesk[5].
> [N2DQPZ-696N]
>
 

Links:

  1. https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?name=pycon-2016-guidebook-data.zip
  2. https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip
  3. https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?name=pycon-2016-guidebook-data.zip
  4. https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?name=Guide_Basics.xls
  5. http://www.zendesk.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From ewa at python.org  Mon Apr 25 21:01:47 2016
From: ewa at python.org (Ewa Jodlowska)
Date: Mon, 25 Apr 2016 20:01:47 -0500
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide
 Building Team!
In-Reply-To: 
References: 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 
 
 
 
Message-ID: 

Hi Carmen,

Thanks for the new link. I am able to view the 2016 guide. Is it OK to
already the "promote" section? This way I can print the posters for onsite.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

On Mon, Apr 25, 2016 at 5:31 PM, Carmen Kuncz (Guidebook) <
builders at guidebook.zendesk.com> wrote:

> ##- 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
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 25, 3:31 PM
> Hi Ewa and Felix,
>
> I just sent you both invitations to be admins on the guide. Our new
> website is builder.guidebook.com, please refrain from using gears!
>
> Please let me know if you have any questions! I should have the last bit
> of content uploaded soon!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 25, 12:09 PM
>
> Hi Carmen,
>
> Thank you for working on this. I have an account on
> https://gears.guidebook.com/ and so does Felix. Mine is under
> ewa at python.org and I believe Felix's is under felixc at felixcrux.com.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 22, 12:26 PM
> Hi Ewa and Felix,
>
> The guide has been update with all content sent with the exception of the
> "presentations" folder. I hope to have this last part of the guide done
> soon!
>
> Are either one of you familiar with Builder and or have an account within
> it?
>
> Please let me know so I can get you set up with how to preview the guide!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 21, 4:04 PM
> Hi Ewa,
>
> I am still working on the guide. There is a mix of last year and this
> year's stuff on it. I will work on trying to get you access to the guide
> tomorrow!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 21, 7:55 AM
>
> Hi Carmen,
>
> Can we access our guide in gears yet? I would love to be able to access to
> Guidebook promotional material as I am working on printing signs for our
> conference this week.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 14, 12:10 PM
> Hi Felix,
>
> Thank you so much for getting this back to me! I am going to start
> uploading this content! I hope a preview will be available for you within
> the next couple days! I will keep you updated on my progress and let you
> know if I run into any problems with the HTML!
>
> Thanks again!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 13, 5:24 PM
>
> All right; that should do it! Attached is the latest version of the data.
>
> The most notable change is of course that all the Markdown has been
> converted
> to HTML. There are a few other things included too:
>
> * New posters: "Building Python with Gradle" and "The Breathing Earth"
> * New bios: Gina Schmalzle and Stephen Holsapple
> * New sponsor: Heroku
> * Updated sponsor logos for Clover Health, PDT, and Keystone
> * Several updated talk descriptions and speaker bios
>
> How does it look? Let me know if any of the formatting is causing trouble,
> and
> I'd be happy to tweak it some more. Approximately when could we start
> playing
> around with a preview of the guide? Thanks!
>
> --
> Felix
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:21 PM
> Hi Felix,
>
> Great thank you so much! I very much appreciate it. I just had a
> conversation with my manager about the html tags and he warned me that
> italics and u are currently not working on our software.
>
> Sorry for the conflicting information! Thank you!
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 5:11 PM
>
> That sounds great; thank you for the info! That's pretty much all the kinds
> of formatting Markdown has, so that makes things much easier. I'll work on
> this over the next few evenings and have an updated version for you later
> this week. Thanks for the help!
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:08 PM
> Hi Felix,
>
> I was not aware of Markdown. I also was misinformed about bold html. The
> following tags will work within our template: a, b, br, i, ul, li, p,
> h1-h6, span, , 
> I hope this clarifies everything! Please let me know if you have any other
> questions!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 4:11 PM
>
> Sounds good; I'll switch all newlines to 
s.
>
> The reason I ask about bold etc. is that currently all descriptions (talks,
> speakers, tutorials, all of them) are in a text-based format called
> Markdown
> (but I'd be happy to convert it to whatever works for you).
>
> Markdown looks very much like plain text (it's meant to), but it actually
> contains formatting instructions. For example, italics are denoted by
> surrounding text in asterisks *like this*, and **double asterisks** mean
> bold. There's also stuff like links, and headings, which look like:
>
> ### I'm a heading!
>
> You can see some examples of this in the tutorials_schedule.csv file. Check
> out the tutorial called "Making an Impact with Python Natural Language
> Processing Tools". You can see how it looks online here:
> https://us.pycon.org/2016/schedule/presentation/1778/
>
> Note how the description contains text like:
> ### Python Development Environment
> and how that becomes a headline on the web page. There are also links, like
> the one that reads: "[Python](http://python.org)". Finally, there's text
> that shows up in a fixed-width font using backticks (`), like `virtualenv`.
>
> Those examples would typically be translated into HTML tags like 
, ,
> and 
 or .
>
> If you can summarize for me what formatting exactly the app can handle, I
> can convert everything to use it. For things that aren't supported (like
> bold) I'll at least remove the extra stuff, so we don't get silly
> double-asterisks in the app text.
>
> Sorry for the mixup; I don't know what formatting the app can use, so I
> left
> everything in Markdown and mentioned it in the original email. I'd be happy
> to convert it to whatever works! Cheers,
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 12:17 PM
> Hi Felix,
>
> Great to hear! For line breaks please you 
 for single breaks and
> 

 for double.
> Unfortunately our software does not allow for us to included bolded
> formatting. However, I dont see any bolded text in the files you have sent
> me so far? I only see the need for line breaks?
>
> Once I have the updated materials (the schedule is complete so that is not
> necessary), the process for me uploaded the content shouldn't take very
> long!
>
> Thank you!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 12:14 PM
>
> No problem; I'll get that to you ASAP. Would it be better to use line
> breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with
> paragraphs.
>
> What about other formatting, like Markdown headings; should they be turned
> into 
s etc? Bolded text that's currently **like this** into  or
> ? Or is everything else fine?
>
> Cheers,
>
> --
> Felix
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 11:19 AM
> Hi Felix,
>
> I have been working on the guide but have run into a bit of a time
> consuming task. For our templates, in order to maintain the format we need
> to add html tags for the line breaks. Is there anyway for you to pull the
> descriptions, abstracts,presenter information, etc for each list with html
> tags? I just completed the schedule but it required me manually adding tags
> to each individual item description which is quite a time consuming task.
>
> I will continue to work on maintaining the format and I appreciate your
> patience. If there is anyway we can get the html format within the
> descriptions please let me know as this would be extraordinarily helpful.
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 10, 10:01 AM
>
> 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
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Felix Crux]
>
> *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
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
> 
>
> [image: Katie Herr]
>
> *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. Delivered by Zendesk
> .
> [N2DQPZ-696N]
>
> _______________________________________________
> Pycon-mobile-guide mailing list
> Pycon-mobile-guide at python.org
> https://mail.python.org/mailman/listinfo/pycon-mobile-guide
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From ewa at python.org  Mon Apr 25 21:09:43 2016
From: ewa at python.org (Ewa Jodlowska)
Date: Mon, 25 Apr 2016 20:09:43 -0500
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide
 Building Team!
In-Reply-To: <1461632260.1476398.589467641.37D3D4F6@webmail.messagingengine.com>
References: 
 
 <1459735284.3006054.567827066.5726B810@webmail.messagingengine.com>
 <20160410165927.GA1034@mir.felixcrux.com>
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 
 <1461632260.1476398.589467641.37D3D4F6@webmail.messagingengine.com>
Message-ID: 

On Mon, Apr 25, 2016 at 7:57 PM, Felix Crux  wrote:

> Thanks Carmen!
>
> I can confirm I've now got access (had to click "accept" on the invitation
> in the top right dropdown menu). I'll look through it over the next few
> days and let you know if anything comes up.
>
> I'll also get you new cover art & venue details to replace last year's.
>

FYI - I updated the cover art. Feel free to improve upon it though :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From ewa at python.org  Tue Apr 26 10:23:10 2016
From: ewa at python.org (Ewa Jodlowska)
Date: Tue, 26 Apr 2016 09:23:10 -0500
Subject: [Pycon-mobile-guide] Adding SurveyMonkey Links to Guidebook
Message-ID: 

Hi all,

Just a FYI:

Betsy will be adding survey links to tutorials this week. We are adding
them to the "LINKS" part of each tutorial.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From builders at guidebook.zendesk.com  Tue Apr 26 13:55:53 2016
From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook))
Date: Tue, 26 Apr 2016 17:55:53 +0000
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building
 Team!
In-Reply-To: <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 
 
References: 
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 <1461632260.1476398.589467641.37D3D4F6@webmail.messagingengine.com>
 
 
Message-ID: 

##- 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 26, 10:55 AM

Hi Felix and Ewa,

Yes, you can already use the promote section! Please send along anything else you would like me to add. I only have to upload the "presentations" folder that was sent, everything else should be done!

Felix, we have a linking template that will make it easy on my end! I will reach out if I run into any issues and need assistance!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 25, 6:09 PM

Thanks Carmen!
 
I can confirm I've now got access (had to click "accept" on the invitation in the top right dropdown menu). I'll look through it over the next few days and let you know if anything comes up.
 
I'll also get you new cover art & venue details to replace last year's.


FYI - I updated the cover art. Feel free to improve upon it though :)

----------------------------------------------

Ewa Jodlowska, Apr 25, 6:01 PM

Hi Carmen,

Thanks for the new link. I am able to view the 2016 guide. Is it OK to already the "promote" section? This way I can print the posters for onsite.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Felix Crux, Apr 25, 5:57 PM

Thanks Carmen!
 
I can confirm I've now got access (had to click "accept" on the
invitation in the top right dropdown menu). I'll look through it over
the next few days and let you know if anything comes up.
 
I'll also get you new cover art & venue details to replace last year's.
 
I know I asked about this in the original email, but is there anything I
can do to make it easier to link speakers to their talks? Last year I
did it manually, but if there's something I can provide like a
spreadsheet in a certain format, I'd be happy to do so. Otherwise I
guess they'll need to be done by hand?
 
Cheers,

----------------------------------------------

Carmen Kuncz, Apr 25, 3:31 PM

Hi Ewa and Felix,

I just sent you both invitations to be admins on the guide. Our new website is builder.guidebook.com, please refrain from using gears!

Please let me know if you have any questions! I should have the last bit of content uploaded soon!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 25, 12:09 PM

Hi Carmen,

Thank you for working on this. I have an account on https://gears.guidebook.com/ and so does Felix. Mine is under ewa at python.org and I believe Felix's is under felixc at felixcrux.com. 

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 22, 12:26 PM

Hi Ewa and Felix,

The guide has been update with all content sent with the exception of the "presentations" folder. I hope to have this last part of the guide done soon!

Are either one of you familiar with Builder and or have an account within it?

Please let me know so I can get you set up with how to preview the guide!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Carmen Kuncz, Apr 21, 4:04 PM

Hi Ewa,

I am still working on the guide. There is a mix of last year and this year's stuff on it. I will work on trying to get you access to the guide tomorrow!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 21, 7:55 AM

Hi Carmen,

Can we access our guide in gears yet? I would love to be able to access to Guidebook promotional material as I am working on printing signs for our conference this week.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 14, 12:10 PM

Hi Felix,

Thank you so much for getting this back to me! I am going to start uploading this content! I hope a preview will be available for you within the next couple days! I will keep you updated on my progress and let you know if I run into any problems with the HTML!

Thanks again!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 13, 5:24 PM

All right; that should do it! Attached is the latest version of the data.

The most notable change is of course that all the Markdown has been converted
to HTML. There are a few other things included too:

* New posters: "Building Python with Gradle" and "The Breathing Earth"
* New bios: Gina Schmalzle and Stephen Holsapple
* New sponsor: Heroku
* Updated sponsor logos for Clover Health, PDT, and Keystone
* Several updated talk descriptions and speaker bios

How does it look? Let me know if any of the formatting is causing trouble, and
I'd be happy to tweak it some more. Approximately when could we start playing
around with a preview of the guide? Thanks!

-- 
Felix

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

Carmen Kuncz, Apr 11, 5:21 PM

Hi Felix,

Great thank you so much! I very much appreciate it. I just had a conversation with my manager about the html tags and he warned me that italics and u are currently not working on our software.

Sorry for the conflicting information! Thank you!

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 5:11 PM

That sounds great; thank you for the info! That's pretty much all the kinds
of formatting Markdown has, so that makes things much easier. I'll work on
this over the next few evenings and have an updated version for you later
this week. Thanks for the help!

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 5:08 PM

Hi Felix,

I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \s.

The reason I ask about bold etc. is that currently all descriptions (talks,
speakers, tutorials, all of them) are in a text-based format called Markdown
(but I'd be happy to convert it to whatever works for you).

Markdown looks very much like plain text (it's meant to), but it actually
contains formatting instructions. For example, italics are denoted by
surrounding text in asterisks *like this*, and **double asterisks** mean
bold. There's also stuff like links, and headings, which look like:

 ### I'm a heading!

You can see some examples of this in the tutorials_schedule.csv file. Check
out the tutorial called "Making an Impact with Python Natural Language
Processing Tools". You can see how it looks online here:
https://us.pycon.org/2016/schedule/presentation/1778/

Note how the description contains text like:
 ### Python Development Environment
and how that becomes a headline on the web page. There are also links, like
the one that reads: "[Python](http://python.org)". Finally, there's text
that shows up in a fixed-width font using backticks (`), like `virtualenv`.

Those examples would typically be translated into HTML tags like 
, ,
and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 12:17 PM

Hi Felix,

Great to hear! For line breaks please you \ for single breaks and \\ for double.
Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?

Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!

Thank you!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 12:14 PM

No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.

What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?

Cheers,

-- 
Felix

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 11:19 AM

Hi Felix,

I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.

I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 10, 10:01 AM

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

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=Guide_Basics.xls

----------------------------------------------

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From ewa at python.org  Tue Apr 26 14:47:20 2016
From: ewa at python.org (Ewa Jodlowska)
Date: Tue, 26 Apr 2016 13:47:20 -0500
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide
 Building Team!
In-Reply-To: 
References:  <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 <1461632260.1476398.589467641.37D3D4F6@webmail.messagingengine.com>
 
 
 <8AED94E7-665C-4200-9001-5B5CD407FA61@felixcrux.com>
 
 
 
Message-ID: 

Hi Carmen -

I tried to download the poster for Guidebook promotion but the link is
super long. Is there a way to shorten it? I am attaching an image of what
it looks like now.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

On Tue, Apr 26, 2016 at 12:55 PM, Carmen Kuncz (Guidebook) <
builders at guidebook.zendesk.com> wrote:

> ##- 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
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 26, 10:55 AM
> Hi Felix and Ewa,
>
> Yes, you can already use the promote section! Please send along anything
> else you would like me to add. I only have to upload the "presentations"
> folder that was sent, everything else should be done!
>
> Felix, we have a linking template that will make it easy on my end! I will
> reach out if I run into any issues and need assistance!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 25, 6:09 PM
>
> Thanks Carmen!
>
> I can confirm I've now got access (had to click "accept" on the invitation
> in the top right dropdown menu). I'll look through it over the next few
> days and let you know if anything comes up.
>
> I'll also get you new cover art & venue details to replace last year's.
>
> FYI - I updated the cover art. Feel free to improve upon it though :)
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 25, 6:01 PM
>
> Hi Carmen,
>
> Thanks for the new link. I am able to view the 2016 guide. Is it OK to
> already the "promote" section? This way I can print the posters for onsite.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 25, 5:57 PM
>
> Thanks Carmen!
>
> I can confirm I've now got access (had to click "accept" on the
> invitation in the top right dropdown menu). I'll look through it over
> the next few days and let you know if anything comes up.
>
> I'll also get you new cover art & venue details to replace last year's.
>
> I know I asked about this in the original email, but is there anything I
> can do to make it easier to link speakers to their talks? Last year I
> did it manually, but if there's something I can provide like a
> spreadsheet in a certain format, I'd be happy to do so. Otherwise I
> guess they'll need to be done by hand?
>
> Cheers,
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 25, 3:31 PM
> Hi Ewa and Felix,
>
> I just sent you both invitations to be admins on the guide. Our new
> website is builder.guidebook.com, please refrain from using gears!
>
> Please let me know if you have any questions! I should have the last bit
> of content uploaded soon!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 25, 12:09 PM
>
> Hi Carmen,
>
> Thank you for working on this. I have an account on
> https://gears.guidebook.com/ and so does Felix. Mine is under
> ewa at python.org and I believe Felix's is under felixc at felixcrux.com.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 22, 12:26 PM
> Hi Ewa and Felix,
>
> The guide has been update with all content sent with the exception of the
> "presentations" folder. I hope to have this last part of the guide done
> soon!
>
> Are either one of you familiar with Builder and or have an account within
> it?
>
> Please let me know so I can get you set up with how to preview the guide!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 21, 4:04 PM
> Hi Ewa,
>
> I am still working on the guide. There is a mix of last year and this
> year's stuff on it. I will work on trying to get you access to the guide
> tomorrow!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 21, 7:55 AM
>
> Hi Carmen,
>
> Can we access our guide in gears yet? I would love to be able to access to
> Guidebook promotional material as I am working on printing signs for our
> conference this week.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 14, 12:10 PM
> Hi Felix,
>
> Thank you so much for getting this back to me! I am going to start
> uploading this content! I hope a preview will be available for you within
> the next couple days! I will keep you updated on my progress and let you
> know if I run into any problems with the HTML!
>
> Thanks again!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 13, 5:24 PM
>
> All right; that should do it! Attached is the latest version of the data.
>
> The most notable change is of course that all the Markdown has been
> converted
> to HTML. There are a few other things included too:
>
> * New posters: "Building Python with Gradle" and "The Breathing Earth"
> * New bios: Gina Schmalzle and Stephen Holsapple
> * New sponsor: Heroku
> * Updated sponsor logos for Clover Health, PDT, and Keystone
> * Several updated talk descriptions and speaker bios
>
> How does it look? Let me know if any of the formatting is causing trouble,
> and
> I'd be happy to tweak it some more. Approximately when could we start
> playing
> around with a preview of the guide? Thanks!
>
> --
> Felix
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:21 PM
> Hi Felix,
>
> Great thank you so much! I very much appreciate it. I just had a
> conversation with my manager about the html tags and he warned me that
> italics and u are currently not working on our software.
>
> Sorry for the conflicting information! Thank you!
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 5:11 PM
>
> That sounds great; thank you for the info! That's pretty much all the kinds
> of formatting Markdown has, so that makes things much easier. I'll work on
> this over the next few evenings and have an updated version for you later
> this week. Thanks for the help!
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:08 PM
> Hi Felix,
>
> I was not aware of Markdown. I also was misinformed about bold html. The
> following tags will work within our template: a, b, br, i, ul, li, p,
> h1-h6, span, , 
> I hope this clarifies everything! Please let me know if you have any other
> questions!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 4:11 PM
>
> Sounds good; I'll switch all newlines to 
s.
>
> The reason I ask about bold etc. is that currently all descriptions (talks,
> speakers, tutorials, all of them) are in a text-based format called
> Markdown
> (but I'd be happy to convert it to whatever works for you).
>
> Markdown looks very much like plain text (it's meant to), but it actually
> contains formatting instructions. For example, italics are denoted by
> surrounding text in asterisks *like this*, and **double asterisks** mean
> bold. There's also stuff like links, and headings, which look like:
>
> ### I'm a heading!
>
> You can see some examples of this in the tutorials_schedule.csv file. Check
> out the tutorial called "Making an Impact with Python Natural Language
> Processing Tools". You can see how it looks online here:
> https://us.pycon.org/2016/schedule/presentation/1778/
>
> Note how the description contains text like:
> ### Python Development Environment
> and how that becomes a headline on the web page. There are also links, like
> the one that reads: "[Python](http://python.org)". Finally, there's text
> that shows up in a fixed-width font using backticks (`), like `virtualenv`.
>
> Those examples would typically be translated into HTML tags like 
, ,
> and 
 or .
>
> If you can summarize for me what formatting exactly the app can handle, I
> can convert everything to use it. For things that aren't supported (like
> bold) I'll at least remove the extra stuff, so we don't get silly
> double-asterisks in the app text.
>
> Sorry for the mixup; I don't know what formatting the app can use, so I
> left
> everything in Markdown and mentioned it in the original email. I'd be happy
> to convert it to whatever works! Cheers,
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 12:17 PM
> Hi Felix,
>
> Great to hear! For line breaks please you 
 for single breaks and
> 

 for double.
> Unfortunately our software does not allow for us to included bolded
> formatting. However, I dont see any bolded text in the files you have sent
> me so far? I only see the need for line breaks?
>
> Once I have the updated materials (the schedule is complete so that is not
> necessary), the process for me uploaded the content shouldn't take very
> long!
>
> Thank you!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 12:14 PM
>
> No problem; I'll get that to you ASAP. Would it be better to use line
> breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with
> paragraphs.
>
> What about other formatting, like Markdown headings; should they be turned
> into 
s etc? Bolded text that's currently **like this** into  or
> ? Or is everything else fine?
>
> Cheers,
>
> --
> Felix
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 11:19 AM
> Hi Felix,
>
> I have been working on the guide but have run into a bit of a time
> consuming task. For our templates, in order to maintain the format we need
> to add html tags for the line breaks. Is there anyway for you to pull the
> descriptions, abstracts,presenter information, etc for each list with html
> tags? I just completed the schedule but it required me manually adding tags
> to each individual item description which is quite a time consuming task.
>
> I will continue to work on maintaining the format and I appreciate your
> patience. If there is anyway we can get the html format within the
> descriptions please let me know as this would be extraordinarily helpful.
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 10, 10:01 AM
>
> 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
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Felix Crux]
>
> *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
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
> 
>
> [image: Katie Herr]
>
> *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. Delivered by Zendesk
> .
> [N2DQPZ-696N]
>
> _______________________________________________
> Pycon-mobile-guide mailing list
> Pycon-mobile-guide at python.org
> https://mail.python.org/mailman/listinfo/pycon-mobile-guide
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-04-26 at 1.45.50 PM.png
Type: image/png
Size: 26326 bytes
Desc: not available
URL: 

From builders at guidebook.zendesk.com  Tue Apr 26 17:01:58 2016
From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook))
Date: Tue, 26 Apr 2016 21:01:58 +0000
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building
 Team!
In-Reply-To: <20160411231035.GB986@mir.felixcrux.com>
 
 
References:  <20160411231035.GB986@mir.felixcrux.com>
 <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 <1461632260.1476398.589467641.37D3D4F6@webmail.messagingengine.com>
 
 
 
Message-ID: 

##- 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 26, 2:01 PM

Hi Ewa,

I have changed it to "http://guidebook.com/g/pycon2016" please let me know if you would like it change it to something else!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 26, 11:47 AM

Hi Carmen - 

I tried to download the poster for Guidebook promotion but the link is super long. Is there a way to shorten it? I am attaching an image of what it looks like now.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

Attachment(s):
Screen Shot 2016-04-26 at 1.45.50 PM.png - https://support.guidebook.com/attachments/token/iaSl7nrPA5v9029GQ3iivK5RZ/?name=Screen+Shot+2016-04-26+at+1.45.50+PM.png

----------------------------------------------

Carmen Kuncz, Apr 26, 10:55 AM

Hi Felix and Ewa,

Yes, you can already use the promote section! Please send along anything else you would like me to add. I only have to upload the "presentations" folder that was sent, everything else should be done!

Felix, we have a linking template that will make it easy on my end! I will reach out if I run into any issues and need assistance!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 25, 6:09 PM

Thanks Carmen!
 
I can confirm I've now got access (had to click "accept" on the invitation in the top right dropdown menu). I'll look through it over the next few days and let you know if anything comes up.
 
I'll also get you new cover art & venue details to replace last year's.


FYI - I updated the cover art. Feel free to improve upon it though :)

----------------------------------------------

Ewa Jodlowska, Apr 25, 6:01 PM

Hi Carmen,

Thanks for the new link. I am able to view the 2016 guide. Is it OK to already the "promote" section? This way I can print the posters for onsite.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Felix Crux, Apr 25, 5:57 PM

Thanks Carmen!
 
I can confirm I've now got access (had to click "accept" on the
invitation in the top right dropdown menu). I'll look through it over
the next few days and let you know if anything comes up.
 
I'll also get you new cover art & venue details to replace last year's.
 
I know I asked about this in the original email, but is there anything I
can do to make it easier to link speakers to their talks? Last year I
did it manually, but if there's something I can provide like a
spreadsheet in a certain format, I'd be happy to do so. Otherwise I
guess they'll need to be done by hand?
 
Cheers,

----------------------------------------------

Carmen Kuncz, Apr 25, 3:31 PM

Hi Ewa and Felix,

I just sent you both invitations to be admins on the guide. Our new website is builder.guidebook.com, please refrain from using gears!

Please let me know if you have any questions! I should have the last bit of content uploaded soon!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 25, 12:09 PM

Hi Carmen,

Thank you for working on this. I have an account on https://gears.guidebook.com/ and so does Felix. Mine is under ewa at python.org and I believe Felix's is under felixc at felixcrux.com. 

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 22, 12:26 PM

Hi Ewa and Felix,

The guide has been update with all content sent with the exception of the "presentations" folder. I hope to have this last part of the guide done soon!

Are either one of you familiar with Builder and or have an account within it?

Please let me know so I can get you set up with how to preview the guide!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Carmen Kuncz, Apr 21, 4:04 PM

Hi Ewa,

I am still working on the guide. There is a mix of last year and this year's stuff on it. I will work on trying to get you access to the guide tomorrow!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 21, 7:55 AM

Hi Carmen,

Can we access our guide in gears yet? I would love to be able to access to Guidebook promotional material as I am working on printing signs for our conference this week.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 14, 12:10 PM

Hi Felix,

Thank you so much for getting this back to me! I am going to start uploading this content! I hope a preview will be available for you within the next couple days! I will keep you updated on my progress and let you know if I run into any problems with the HTML!

Thanks again!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 13, 5:24 PM

All right; that should do it! Attached is the latest version of the data.

The most notable change is of course that all the Markdown has been converted
to HTML. There are a few other things included too:

* New posters: "Building Python with Gradle" and "The Breathing Earth"
* New bios: Gina Schmalzle and Stephen Holsapple
* New sponsor: Heroku
* Updated sponsor logos for Clover Health, PDT, and Keystone
* Several updated talk descriptions and speaker bios

How does it look? Let me know if any of the formatting is causing trouble, and
I'd be happy to tweak it some more. Approximately when could we start playing
around with a preview of the guide? Thanks!

-- 
Felix

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

Carmen Kuncz, Apr 11, 5:21 PM

Hi Felix,

Great thank you so much! I very much appreciate it. I just had a conversation with my manager about the html tags and he warned me that italics and u are currently not working on our software.

Sorry for the conflicting information! Thank you!

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 5:11 PM

That sounds great; thank you for the info! That's pretty much all the kinds
of formatting Markdown has, so that makes things much easier. I'll work on
this over the next few evenings and have an updated version for you later
this week. Thanks for the help!

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 5:08 PM

Hi Felix,

I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \s.

The reason I ask about bold etc. is that currently all descriptions (talks,
speakers, tutorials, all of them) are in a text-based format called Markdown
(but I'd be happy to convert it to whatever works for you).

Markdown looks very much like plain text (it's meant to), but it actually
contains formatting instructions. For example, italics are denoted by
surrounding text in asterisks *like this*, and **double asterisks** mean
bold. There's also stuff like links, and headings, which look like:

 ### I'm a heading!

You can see some examples of this in the tutorials_schedule.csv file. Check
out the tutorial called "Making an Impact with Python Natural Language
Processing Tools". You can see how it looks online here:
https://us.pycon.org/2016/schedule/presentation/1778/

Note how the description contains text like:
 ### Python Development Environment
and how that becomes a headline on the web page. There are also links, like
the one that reads: "[Python](http://python.org)". Finally, there's text
that shows up in a fixed-width font using backticks (`), like `virtualenv`.

Those examples would typically be translated into HTML tags like 
, ,
and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 12:17 PM

Hi Felix,

Great to hear! For line breaks please you \ for single breaks and \\ for double.
Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?

Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!

Thank you!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 12:14 PM

No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.

What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?

Cheers,

-- 
Felix

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 11:19 AM

Hi Felix,

I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.

I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 10, 10:01 AM

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

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=Guide_Basics.xls

----------------------------------------------

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From ewa at python.org  Tue Apr 26 17:23:06 2016
From: ewa at python.org (Ewa Jodlowska)
Date: Tue, 26 Apr 2016 16:23:06 -0500
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide
 Building Team!
In-Reply-To: 
References:  <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 <1461632260.1476398.589467641.37D3D4F6@webmail.messagingengine.com>
 
 
 
 <20160411231035.GB986@mir.felixcrux.com>
 
 
 
Message-ID: 

This is great - thank you!

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

On Tue, Apr 26, 2016 at 4:01 PM, Carmen Kuncz (Guidebook) <
builders at guidebook.zendesk.com> wrote:

> ##- 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
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 26, 2:01 PM
> Hi Ewa,
>
> I have changed it to "http://guidebook.com/g/pycon2016" please let me
> know if you would like it change it to something else!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 26, 11:47 AM
>
> Hi Carmen -
>
> I tried to download the poster for Guidebook promotion but the link is
> super long. Is there a way to shorten it? I am attaching an image of what
> it looks like now.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> Attachment(s)
> Screen Shot 2016-04-26 at 1.45.50 PM.png
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 26, 10:55 AM
> Hi Felix and Ewa,
>
> Yes, you can already use the promote section! Please send along anything
> else you would like me to add. I only have to upload the "presentations"
> folder that was sent, everything else should be done!
>
> Felix, we have a linking template that will make it easy on my end! I will
> reach out if I run into any issues and need assistance!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 25, 6:09 PM
>
> Thanks Carmen!
>
> I can confirm I've now got access (had to click "accept" on the invitation
> in the top right dropdown menu). I'll look through it over the next few
> days and let you know if anything comes up.
>
> I'll also get you new cover art & venue details to replace last year's.
>
> FYI - I updated the cover art. Feel free to improve upon it though :)
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 25, 6:01 PM
>
> Hi Carmen,
>
> Thanks for the new link. I am able to view the 2016 guide. Is it OK to
> already the "promote" section? This way I can print the posters for onsite.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 25, 5:57 PM
>
> Thanks Carmen!
>
> I can confirm I've now got access (had to click "accept" on the
> invitation in the top right dropdown menu). I'll look through it over
> the next few days and let you know if anything comes up.
>
> I'll also get you new cover art & venue details to replace last year's.
>
> I know I asked about this in the original email, but is there anything I
> can do to make it easier to link speakers to their talks? Last year I
> did it manually, but if there's something I can provide like a
> spreadsheet in a certain format, I'd be happy to do so. Otherwise I
> guess they'll need to be done by hand?
>
> Cheers,
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 25, 3:31 PM
> Hi Ewa and Felix,
>
> I just sent you both invitations to be admins on the guide. Our new
> website is builder.guidebook.com, please refrain from using gears!
>
> Please let me know if you have any questions! I should have the last bit
> of content uploaded soon!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 25, 12:09 PM
>
> Hi Carmen,
>
> Thank you for working on this. I have an account on
> https://gears.guidebook.com/ and so does Felix. Mine is under
> ewa at python.org and I believe Felix's is under felixc at felixcrux.com.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 22, 12:26 PM
> Hi Ewa and Felix,
>
> The guide has been update with all content sent with the exception of the
> "presentations" folder. I hope to have this last part of the guide done
> soon!
>
> Are either one of you familiar with Builder and or have an account within
> it?
>
> Please let me know so I can get you set up with how to preview the guide!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 21, 4:04 PM
> Hi Ewa,
>
> I am still working on the guide. There is a mix of last year and this
> year's stuff on it. I will work on trying to get you access to the guide
> tomorrow!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Ewa Jodlow]
>
> *Ewa Jodlowska*
>
> Apr 21, 7:55 AM
>
> Hi Carmen,
>
> Can we access our guide in gears yet? I would love to be able to access to
> Guidebook promotional material as I am working on printing signs for our
> conference this week.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 14, 12:10 PM
> Hi Felix,
>
> Thank you so much for getting this back to me! I am going to start
> uploading this content! I hope a preview will be available for you within
> the next couple days! I will keep you updated on my progress and let you
> know if I run into any problems with the HTML!
>
> Thanks again!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 13, 5:24 PM
>
> All right; that should do it! Attached is the latest version of the data.
>
> The most notable change is of course that all the Markdown has been
> converted
> to HTML. There are a few other things included too:
>
> * New posters: "Building Python with Gradle" and "The Breathing Earth"
> * New bios: Gina Schmalzle and Stephen Holsapple
> * New sponsor: Heroku
> * Updated sponsor logos for Clover Health, PDT, and Keystone
> * Several updated talk descriptions and speaker bios
>
> How does it look? Let me know if any of the formatting is causing trouble,
> and
> I'd be happy to tweak it some more. Approximately when could we start
> playing
> around with a preview of the guide? Thanks!
>
> --
> Felix
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:21 PM
> Hi Felix,
>
> Great thank you so much! I very much appreciate it. I just had a
> conversation with my manager about the html tags and he warned me that
> italics and u are currently not working on our software.
>
> Sorry for the conflicting information! Thank you!
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 5:11 PM
>
> That sounds great; thank you for the info! That's pretty much all the kinds
> of formatting Markdown has, so that makes things much easier. I'll work on
> this over the next few evenings and have an updated version for you later
> this week. Thanks for the help!
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 5:08 PM
> Hi Felix,
>
> I was not aware of Markdown. I also was misinformed about bold html. The
> following tags will work within our template: a, b, br, i, ul, li, p,
> h1-h6, span, , 
> I hope this clarifies everything! Please let me know if you have any other
> questions!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 4:11 PM
>
> Sounds good; I'll switch all newlines to 
s.
>
> The reason I ask about bold etc. is that currently all descriptions (talks,
> speakers, tutorials, all of them) are in a text-based format called
> Markdown
> (but I'd be happy to convert it to whatever works for you).
>
> Markdown looks very much like plain text (it's meant to), but it actually
> contains formatting instructions. For example, italics are denoted by
> surrounding text in asterisks *like this*, and **double asterisks** mean
> bold. There's also stuff like links, and headings, which look like:
>
> ### I'm a heading!
>
> You can see some examples of this in the tutorials_schedule.csv file. Check
> out the tutorial called "Making an Impact with Python Natural Language
> Processing Tools". You can see how it looks online here:
> https://us.pycon.org/2016/schedule/presentation/1778/
>
> Note how the description contains text like:
> ### Python Development Environment
> and how that becomes a headline on the web page. There are also links, like
> the one that reads: "[Python](http://python.org)". Finally, there's text
> that shows up in a fixed-width font using backticks (`), like `virtualenv`.
>
> Those examples would typically be translated into HTML tags like 
, ,
> and 
 or .
>
> If you can summarize for me what formatting exactly the app can handle, I
> can convert everything to use it. For things that aren't supported (like
> bold) I'll at least remove the extra stuff, so we don't get silly
> double-asterisks in the app text.
>
> Sorry for the mixup; I don't know what formatting the app can use, so I
> left
> everything in Markdown and mentioned it in the original email. I'd be happy
> to convert it to whatever works! Cheers,
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 12:17 PM
> Hi Felix,
>
> Great to hear! For line breaks please you 
 for single breaks and
> 

 for double.
> Unfortunately our software does not allow for us to included bolded
> formatting. However, I dont see any bolded text in the files you have sent
> me so far? I only see the need for line breaks?
>
> Once I have the updated materials (the schedule is complete so that is not
> necessary), the process for me uploaded the content shouldn't take very
> long!
>
> Thank you!
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 11, 12:14 PM
>
> No problem; I'll get that to you ASAP. Would it be better to use line
> breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with
> paragraphs.
>
> What about other formatting, like Markdown headings; should they be turned
> into 
s etc? Bolded text that's currently **like this** into  or
> ? Or is everything else fine?
>
> Cheers,
>
> --
> Felix
>
> --
> Felix
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> Apr 11, 11:19 AM
> Hi Felix,
>
> I have been working on the guide but have run into a bit of a time
> consuming task. For our templates, in order to maintain the format we need
> to add html tags for the line breaks. Is there anyway for you to pull the
> descriptions, abstracts,presenter information, etc for each list with html
> tags? I just completed the schedule but it required me manually adding tags
> to each individual item description which is quite a time consuming task.
>
> I will continue to work on maintaining the format and I appreciate your
> patience. If there is anyway we can get the html format within the
> descriptions please let me know as this would be extraordinarily helpful.
>
> Best,
>
> Carmen
>
> Carmen Kuncz
> Customer Success Associate
> Guidebook
>
> [image: Felix Crux]
>
> *Felix Crux*
>
> Apr 10, 10:01 AM
>
> 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
>
> Attachment(s)
> pycon-2016-guidebook-data.zip
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Felix Crux]
>
> *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
> 
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
>
> [image: Ewa Jodlow]
>
> *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
>
> [image: Carmen Kun]
>
> *Carmen Kuncz* (Guidebook)
>
> 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
> 
>
> [image: Katie Herr]
>
> *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. Delivered by Zendesk
> .
> [N2DQPZ-696N]
>
> _______________________________________________
> Pycon-mobile-guide mailing list
> Pycon-mobile-guide at python.org
> https://mail.python.org/mailman/listinfo/pycon-mobile-guide
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From builders at guidebook.zendesk.com  Thu Apr 28 18:51:53 2016
From: builders at guidebook.zendesk.com (Carmen Kuncz (Guidebook))
Date: Thu, 28 Apr 2016 22:51:53 +0000
Subject: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building
 Team!
In-Reply-To: <20160412001041.GC986@mir.felixcrux.com>
 
 
References:  <20160412001041.GC986@mir.felixcrux.com>
 <20160414002318.GA992@mir.felixcrux.com>
 
 
 <1461632260.1476398.589467641.37D3D4F6@webmail.messagingengine.com>
 
 
 
 
Message-ID: 

##- 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 28, 3:51 PM

Hi Ewa and Felix,

All content has been uploaded to the guide with a couple exceptions:
-Sponsor Logos
-Linking speakers to their talks

I will have this final content uploaded by early next week. I want to thank the both of you for your patience as I build this guide. There is a lot of information to input and it is taking me longer than anticipated!

Would the two of you please go through what I have uploaded so far and let me know if anything else needs to be added or edited with the exception of what is mentioned above?

Additionally, there are a few things that were sent that when opened appeared blank on my end. These items are listed below:

-Education Summit Bios
-Lightning Talk Bios
-Open Space Bios
-Special Events Schedule
-Captioning Sponsors
-Coffee Sponsors
-Financial Aid Sponsor
-Education Summit Presentations
-Lightning Talk Presentations
-Open Space Presentations

Lastly, I want to let the two of you know that I will be out of the office from tomorrow, April 29th Until Monday May 2nd. I will be checking my email sparingly incase anything urgent arises. But if I am not available to speak feel free to contact support at guidebook.com and someone on my team will be happy to help out!

Let me know your thoughts on the guide!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 26, 2:23 PM

This is great - thank you!

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 26, 2:01 PM

Hi Ewa,

I have changed it to "http://guidebook.com/g/pycon2016" please let me know if you would like it change it to something else!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 26, 11:47 AM

Hi Carmen - 

I tried to download the poster for Guidebook promotion but the link is super long. Is there a way to shorten it? I am attaching an image of what it looks like now.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

Attachment(s):
Screen Shot 2016-04-26 at 1.45.50 PM.png - https://support.guidebook.com/attachments/token/iaSl7nrPA5v9029GQ3iivK5RZ/?name=Screen+Shot+2016-04-26+at+1.45.50+PM.png

----------------------------------------------

Carmen Kuncz, Apr 26, 10:55 AM

Hi Felix and Ewa,

Yes, you can already use the promote section! Please send along anything else you would like me to add. I only have to upload the "presentations" folder that was sent, everything else should be done!

Felix, we have a linking template that will make it easy on my end! I will reach out if I run into any issues and need assistance!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 25, 6:09 PM

Thanks Carmen!
 
I can confirm I've now got access (had to click "accept" on the invitation in the top right dropdown menu). I'll look through it over the next few days and let you know if anything comes up.
 
I'll also get you new cover art & venue details to replace last year's.


FYI - I updated the cover art. Feel free to improve upon it though :)

----------------------------------------------

Ewa Jodlowska, Apr 25, 6:01 PM

Hi Carmen,

Thanks for the new link. I am able to view the 2016 guide. Is it OK to already the "promote" section? This way I can print the posters for onsite.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Felix Crux, Apr 25, 5:57 PM

Thanks Carmen!
 
I can confirm I've now got access (had to click "accept" on the
invitation in the top right dropdown menu). I'll look through it over
the next few days and let you know if anything comes up.
 
I'll also get you new cover art & venue details to replace last year's.
 
I know I asked about this in the original email, but is there anything I
can do to make it easier to link speakers to their talks? Last year I
did it manually, but if there's something I can provide like a
spreadsheet in a certain format, I'd be happy to do so. Otherwise I
guess they'll need to be done by hand?
 
Cheers,

----------------------------------------------

Carmen Kuncz, Apr 25, 3:31 PM

Hi Ewa and Felix,

I just sent you both invitations to be admins on the guide. Our new website is builder.guidebook.com, please refrain from using gears!

Please let me know if you have any questions! I should have the last bit of content uploaded soon!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 25, 12:09 PM

Hi Carmen,

Thank you for working on this. I have an account on https://gears.guidebook.com/ and so does Felix. Mine is under ewa at python.org and I believe Felix's is under felixc at felixcrux.com. 

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 22, 12:26 PM

Hi Ewa and Felix,

The guide has been update with all content sent with the exception of the "presentations" folder. I hope to have this last part of the guide done soon!

Are either one of you familiar with Builder and or have an account within it?

Please let me know so I can get you set up with how to preview the guide!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Carmen Kuncz, Apr 21, 4:04 PM

Hi Ewa,

I am still working on the guide. There is a mix of last year and this year's stuff on it. I will work on trying to get you access to the guide tomorrow!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Ewa Jodlowska, Apr 21, 7:55 AM

Hi Carmen,

Can we access our guide in gears yet? I would love to be able to access to Guidebook promotional material as I am working on printing signs for our conference this week.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

----------------------------------------------

Carmen Kuncz, Apr 14, 12:10 PM

Hi Felix,

Thank you so much for getting this back to me! I am going to start uploading this content! I hope a preview will be available for you within the next couple days! I will keep you updated on my progress and let you know if I run into any problems with the HTML!

Thanks again!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 13, 5:24 PM

All right; that should do it! Attached is the latest version of the data.

The most notable change is of course that all the Markdown has been converted
to HTML. There are a few other things included too:

* New posters: "Building Python with Gradle" and "The Breathing Earth"
* New bios: Gina Schmalzle and Stephen Holsapple
* New sponsor: Heroku
* Updated sponsor logos for Clover Health, PDT, and Keystone
* Several updated talk descriptions and speaker bios

How does it look? Let me know if any of the formatting is causing trouble, and
I'd be happy to tweak it some more. Approximately when could we start playing
around with a preview of the guide? Thanks!

-- 
Felix

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

Carmen Kuncz, Apr 11, 5:21 PM

Hi Felix,

Great thank you so much! I very much appreciate it. I just had a conversation with my manager about the html tags and he warned me that italics and u are currently not working on our software.

Sorry for the conflicting information! Thank you!

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 5:11 PM

That sounds great; thank you for the info! That's pretty much all the kinds
of formatting Markdown has, so that makes things much easier. I'll work on
this over the next few evenings and have an updated version for you later
this week. Thanks for the help!

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 5:08 PM

Hi Felix,

I was not aware of Markdown. I also was misinformed about bold html. The following tags will work within our template: a, b, br, i, ul, li, p, h1-h6, span, \, \s.

The reason I ask about bold etc. is that currently all descriptions (talks,
speakers, tutorials, all of them) are in a text-based format called Markdown
(but I'd be happy to convert it to whatever works for you).

Markdown looks very much like plain text (it's meant to), but it actually
contains formatting instructions. For example, italics are denoted by
surrounding text in asterisks *like this*, and **double asterisks** mean
bold. There's also stuff like links, and headings, which look like:

 ### I'm a heading!

You can see some examples of this in the tutorials_schedule.csv file. Check
out the tutorial called "Making an Impact with Python Natural Language
Processing Tools". You can see how it looks online here:
https://us.pycon.org/2016/schedule/presentation/1778/

Note how the description contains text like:
 ### Python Development Environment
and how that becomes a headline on the web page. There are also links, like
the one that reads: "[Python](http://python.org)". Finally, there's text
that shows up in a fixed-width font using backticks (`), like `virtualenv`.

Those examples would typically be translated into HTML tags like 
, ,
and 
 or .

If you can summarize for me what formatting exactly the app can handle, I
can convert everything to use it. For things that aren't supported (like
bold) I'll at least remove the extra stuff, so we don't get silly
double-asterisks in the app text.

Sorry for the mixup; I don't know what formatting the app can use, so I left
everything in Markdown and mentioned it in the original email. I'd be happy
to convert it to whatever works! Cheers,

--
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 12:17 PM

Hi Felix,

Great to hear! For line breaks please you \ for single breaks and \\ for double.
Unfortunately our software does not allow for us to included bolded formatting. However, I dont see any bolded text in the files you have sent me so far? I only see the need for line breaks?

Once I have the updated materials (the schedule is complete so that is not necessary), the process for me uploaded the content shouldn't take very long!

Thank you!

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 11, 12:14 PM

No problem; I'll get that to you ASAP. Would it be better to use line breaks (
) or paragraphs (
)? If it doesn't matter I'll likely go with paragraphs.

What about other formatting, like Markdown headings; should they be turned into 
s etc? Bolded text that's currently **like this** into  or ? Or is everything else fine?

Cheers,

-- 
Felix

-- 
Felix

----------------------------------------------

Carmen Kuncz, Apr 11, 11:19 AM

Hi Felix,

I have been working on the guide but have run into a bit of a time consuming task. For our templates, in order to maintain the format we need to add html tags for the line breaks. Is there anyway for you to pull the descriptions, abstracts,presenter information, etc for each list with html tags? I just completed the schedule but it required me manually adding tags to each individual item description which is quite a time consuming task.

I will continue to work on maintaining the format and I appreciate your patience. If there is anyway we can get the html format within the descriptions please let me know as this would be extraordinarily helpful.

Best,

Carmen

Carmen Kuncz
Customer Success Associate
Guidebook

----------------------------------------------

Felix Crux, Apr 10, 10:01 AM

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

Attachment(s):
pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=pycon-2016-guidebook-data.zip

----------------------------------------------

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/?name=Guide_Basics.xls

----------------------------------------------

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: