Mailman 3 May 2016 - Pycon-mobile-guide

[Guidebook] Update: Intro to Guide Building Team!
by Carmen Kuncz (Guidebook) June 2, 2016

June 2, 2016

##- 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/?… ---------------------------------------------- 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, \<a\>, \<a href & strong. 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 <br>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 <h3>, <a>, and <pre> or <code>. 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 \<br\> for single breaks and \<br\>\<br\> 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 (<br>) or paragraphs (<p>)? If it doesn't matter I'll likely go with paragraphs. What about other formatting, like Markdown headings; should they be turned into <h1>s etc? Bolded text that's currently **like this** into <strong> or <b>? 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/?… ---------------------------------------------- Carmen Kuncz, Apr 4, 10:02 AM Hi Felix, Thank you for sending this along! I will take a look at everything and start working on inputing this information to the guide within the next few days! I will reach out if I have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, Apr 3, 7:01 PM Hi Carmen, Please find attached an initial attempt at bundling up all the content into a usable export. I hope it's workable enough to get things going, but I'll follow up shortly with whatever is else is needed. The attached zip file should contain comma-separated (.csv) files with the details of all the talks, speakers, etc. The first line of each file has headings describing what each column is. Note that some rows (particularly speaker bios and talk descriptions) contain embedded newlines, but all of those entries should additionally be enclosed in double quotation marks. The files are UTF-8 encoded, and several of the speakers do have names containing non-ASCII characters like 'Ł', 'é', etc, so that's worth watching out for. There are also logo images for all the sponsors in the zip file. *Talk descriptions are currently exported as raw, unprocessed, Markdown*. I'm not sure what kind of formatting Guidebook supports, so I've left that as-is for now. If there's something more useful I can convert it to, just let me know. I do think we'll want to figure out how to process that formatting and get it reflected in the app, though. There's currently nothing in the data export that *links speakers to their talks*, which I know the app can do. If there's some data format that can be bulk-imported to your systems to get that automatically, just let me know and I'd be happy to work on it. In previous years, however, we just linked them up manually. Please don't hesitate to *let me know if there's any way I can process or rework the data* to make it easier for you/your tools to work with -- the nice thing about being a programming conference is we're generally happy to build our own tools to make things simpler! I would much rather put in the work on my end to automate whatever data processing you need to make it possible to bulk-upload changes, instead of having you or me need to go in and fix things manually one-by-one. At present, this is the* list of issues/missing data *that I'm aware of and am working on: * Keynote speakers are not included in the speaker bios. * Plenary sessions (e.g. keynotes, opening remarks) are just listed as "plenary" with no description in the schedule. * Special events (e.g. PyLadies auction, 5K run, dinners) are not included in the schedule (special_events_schedule.csv is empty). * Meals/breaks show up once per track/room, but they really should just be listed once. * "Special" pages such as venue information, code of conduct, etc. may need to be input manually - I don't mind doing it. * Speaker photos are not included (maybe that's OK -- we didn't have them last year either). * As mentioned earlier, some text is in raw Markdown; and I don't know if that's a format Guidebook can ingest. * Floor plan map is on its way, and we'll need to link talks to the room they're in. * Some general information still TBD; I will get it to you ASAP (see below). Finally, here's the *info your requested in in the Guide Basics spreadsheet*: Guide Name: PyCon 2016 Guide Start Date: 2016-05-28 Guide End Date: 2016-06-05 Timezone: Pacific Daylight Time (PDT) (UTC -7) General Information, Venue, Icon, Cover Image, Maps: I will get these to you ASAP, or just fill them in myself and let you know. Facebook: https://www.facebook.com/us.pycon.org Twitter: https://twitter.com/pycon YouTube: Not set up yet, will let you know Photos: No (I think, for now at least) RSS Feed: http://pycon.blogspot.com/feeds/posts/default?alt=rss Homepage: https://us.pycon.org/2016/ Feedback/Surveys: I believe we'll use this, but I don't think the survey has been designed yet. Will get it to you. Notifications: Sure, let's have this. My Schedule: Definitely want this feature. Notes: Sounds good. Live polling: I don't think we'll use this. All right, I think that's most of it for now? Sorry for the enormous email; I'm trying to be very thorough both to keep everyone in the loop and to remind myself of exactly what work I still need to do! Again, please don't hesitate to let me know if I can change or process the data in any way to make it easier for you, or if anything in the export looks weird -- it's all automated, so it's entirely possible something broken snuck through without human review. Cheers; all the best! -- Felix Attachment(s): pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?… ---------------------------------------------- Carmen Kuncz, Mar 30, 12:18 PM Hi Ewa, No rush on getting the content to me! I just didn't want to miss a deadline for you! Please send me the content as you get it! Reach out if you have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Mar 30, 11:08 AM Hi Carmen, Thank you for checking in! I am not yet ready to start this yet. I will begin the process on Friday of this week and I will ping you if there are any questions. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Mar 30, 11:00 AM Hi Ewa, Just checking in again to see if you have any guide content for me? I know we were initially shooting for an April 1st internal launch date! Please let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Carmen Kuncz, Mar 21, 10:06 AM Hi Ewa, Just checking in to see if you have any content for me to start building your guide? Let me know, I am excited to get started on this! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 2:01 PM Yes, that is my cell phone number. Talk to you tomorrow! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:58 PM Hi Ewa, 1 PM PST tomorrow will work great! Can I call you on the cell phone number you have listed below? If not please let me know which number is best to reach you at! Looking forward to our call! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 1:50 PM Hi Carmen, Let's chat at 1pm PT tomorrow. Have a good afternoon! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:25 PM Hi Ewa, Are you possibly available tomorrow? I am free to speak anytime between 10 AM PST to 4PM PST. Let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 12:22 PM Hi Carmen, Are you available this afternoon? I am available any time now until about 4pm CT. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 10:55 AM Hi Ewa, It's great to e-meet you! My name is Carmen, and I'll be working with you to create your guide. Lets start by scheduling a call to discuss your guide. This will help me get a good vision for your guide as well as to propose a tentative timeline for an on-time release! Please let me know your availability so we can schedule a time! I have attached a Guide Basics Spreadsheet (will appear as a link). Please take a brief look at it before our call! I'm very excited to get started! Let me know your availability and if you have any questions, feel free to reply to this thread (rather than creating a new ticket -- things can get messy rather fast). You can also call my direct extension at 650-319-7233 ext. 222. Thanks again, and I look forward to hearing back from you! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook Attachment(s): Guide_Basics.xls - https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?… ---------------------------------------------- Katie Herrgesell, Feb 17, 10:46 AM Hi Ewa, I would like to introduce you to our awesome guide building team! They are the experts that will handle the data entry for you, and will work to create an easy to use event guide. I have shared your event information with the customer success team, and someone will be contacting you within one business day to get started on your guide. Good luck! Best, Katie -- Katie Herrgesell Sr. Corporate Account Manager Office: 650.319.7233 ext 126 Mobile: 216.570.0531 www.guidebook.com -------------------------------- This email is a service from Guidebook. [N2DQPZ-696N]

4 11

[Guidebook] Update: Intro to Guide Building Team!
by Carmen Kuncz (Guidebook) May 28, 2016

May 28, 2016

##- 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/?… ---------------------------------------------- Carmen Kuncz, Apr 4, 10:02 AM Hi Felix, Thank you for sending this along! I will take a look at everything and start working on inputing this information to the guide within the next few days! I will reach out if I have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, Apr 3, 7:01 PM Hi Carmen, Please find attached an initial attempt at bundling up all the content into a usable export. I hope it's workable enough to get things going, but I'll follow up shortly with whatever is else is needed. The attached zip file should contain comma-separated (.csv) files with the details of all the talks, speakers, etc. The first line of each file has headings describing what each column is. Note that some rows (particularly speaker bios and talk descriptions) contain embedded newlines, but all of those entries should additionally be enclosed in double quotation marks. The files are UTF-8 encoded, and several of the speakers do have names containing non-ASCII characters like 'Ł', 'é', etc, so that's worth watching out for. There are also logo images for all the sponsors in the zip file. *Talk descriptions are currently exported as raw, unprocessed, Markdown*. I'm not sure what kind of formatting Guidebook supports, so I've left that as-is for now. If there's something more useful I can convert it to, just let me know. I do think we'll want to figure out how to process that formatting and get it reflected in the app, though. There's currently nothing in the data export that *links speakers to their talks*, which I know the app can do. If there's some data format that can be bulk-imported to your systems to get that automatically, just let me know and I'd be happy to work on it. In previous years, however, we just linked them up manually. Please don't hesitate to *let me know if there's any way I can process or rework the data* to make it easier for you/your tools to work with -- the nice thing about being a programming conference is we're generally happy to build our own tools to make things simpler! I would much rather put in the work on my end to automate whatever data processing you need to make it possible to bulk-upload changes, instead of having you or me need to go in and fix things manually one-by-one. At present, this is the* list of issues/missing data *that I'm aware of and am working on: * Keynote speakers are not included in the speaker bios. * Plenary sessions (e.g. keynotes, opening remarks) are just listed as "plenary" with no description in the schedule. * Special events (e.g. PyLadies auction, 5K run, dinners) are not included in the schedule (special_events_schedule.csv is empty). * Meals/breaks show up once per track/room, but they really should just be listed once. * "Special" pages such as venue information, code of conduct, etc. may need to be input manually - I don't mind doing it. * Speaker photos are not included (maybe that's OK -- we didn't have them last year either). * As mentioned earlier, some text is in raw Markdown; and I don't know if that's a format Guidebook can ingest. * Floor plan map is on its way, and we'll need to link talks to the room they're in. * Some general information still TBD; I will get it to you ASAP (see below). Finally, here's the *info your requested in in the Guide Basics spreadsheet*: Guide Name: PyCon 2016 Guide Start Date: 2016-05-28 Guide End Date: 2016-06-05 Timezone: Pacific Daylight Time (PDT) (UTC -7) General Information, Venue, Icon, Cover Image, Maps: I will get these to you ASAP, or just fill them in myself and let you know. Facebook: https://www.facebook.com/us.pycon.org Twitter: https://twitter.com/pycon YouTube: Not set up yet, will let you know Photos: No (I think, for now at least) RSS Feed: http://pycon.blogspot.com/feeds/posts/default?alt=rss Homepage: https://us.pycon.org/2016/ Feedback/Surveys: I believe we'll use this, but I don't think the survey has been designed yet. Will get it to you. Notifications: Sure, let's have this. My Schedule: Definitely want this feature. Notes: Sounds good. Live polling: I don't think we'll use this. All right, I think that's most of it for now? Sorry for the enormous email; I'm trying to be very thorough both to keep everyone in the loop and to remind myself of exactly what work I still need to do! Again, please don't hesitate to let me know if I can change or process the data in any way to make it easier for you, or if anything in the export looks weird -- it's all automated, so it's entirely possible something broken snuck through without human review. Cheers; all the best! -- Felix Attachment(s): pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?… ---------------------------------------------- Carmen Kuncz, Mar 30, 12:18 PM Hi Ewa, No rush on getting the content to me! I just didn't want to miss a deadline for you! Please send me the content as you get it! Reach out if you have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Mar 30, 11:08 AM Hi Carmen, Thank you for checking in! I am not yet ready to start this yet. I will begin the process on Friday of this week and I will ping you if there are any questions. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Mar 30, 11:00 AM Hi Ewa, Just checking in again to see if you have any guide content for me? I know we were initially shooting for an April 1st internal launch date! Please let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Carmen Kuncz, Mar 21, 10:06 AM Hi Ewa, Just checking in to see if you have any content for me to start building your guide? Let me know, I am excited to get started on this! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 2:01 PM Yes, that is my cell phone number. Talk to you tomorrow! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:58 PM Hi Ewa, 1 PM PST tomorrow will work great! Can I call you on the cell phone number you have listed below? If not please let me know which number is best to reach you at! Looking forward to our call! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 1:50 PM Hi Carmen, Let's chat at 1pm PT tomorrow. Have a good afternoon! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:25 PM Hi Ewa, Are you possibly available tomorrow? I am free to speak anytime between 10 AM PST to 4PM PST. Let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 12:22 PM Hi Carmen, Are you available this afternoon? I am available any time now until about 4pm CT. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 10:55 AM Hi Ewa, It's great to e-meet you! My name is Carmen, and I'll be working with you to create your guide. Lets start by scheduling a call to discuss your guide. This will help me get a good vision for your guide as well as to propose a tentative timeline for an on-time release! Please let me know your availability so we can schedule a time! I have attached a Guide Basics Spreadsheet (will appear as a link). Please take a brief look at it before our call! I'm very excited to get started! Let me know your availability and if you have any questions, feel free to reply to this thread (rather than creating a new ticket -- things can get messy rather fast). You can also call my direct extension at 650-319-7233 ext. 222. Thanks again, and I look forward to hearing back from you! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook Attachment(s): Guide_Basics.xls - https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?… ---------------------------------------------- Katie Herrgesell, Feb 17, 10:46 AM Hi Ewa, I would like to introduce you to our awesome guide building team! They are the experts that will handle the data entry for you, and will work to create an easy to use event guide. I have shared your event information with the customer success team, and someone will be contacting you within one business day to get started on your guide. Good luck! Best, Katie -- Katie Herrgesell Sr. Corporate Account Manager Office: 650.319.7233 ext 126 Mobile: 216.570.0531 www.guidebook.com -------------------------------- This email is a service from Guidebook. [N2DQPZ-696N]

4 15

Google and Caktus descriptions swapped on Guidebook?
by Brandon Rhodes May 27, 2016

May 27, 2016

Felix and Ewa — I am not sure who is live-updating Guidebook as we head into the final days here, but the Google and Caktus workshops in the final slot on Sunday have their descriptions backwards and swapped with each other. I can try fixing it later this afternoon if you are both too busy, though! -- Brandon Rhodes PyCon 2016 Conference Chair pycon.brandon(a)gmail.com

2 1

Re: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team!
by Felix Crux May 26, 2016

May 26, 2016

Hi Carmen, I've been using the app for a few days now and things look great! I really appreciate all the work that went into it, and I'm sorry there was such a last-minute scramble. There are just a two small things I noticed that I'm hoping are fixable: 1) It seems like some talk location links aren't working quite right. Some don't go to the map at all when I click them. Some others list rooms like 201-202 as two locations, so they show up in the guide as "multiple locations", when really that's just one big room (though, yeah, it's made by opening up the wall between two rooms). 2) It looks like there are still some text encoding issues, although almost everything seems fine. Picking on poor Łukasz Langa again, his name was showing up with a regular "L" (I fixed that one just now). Guillermo Pérez is another example; the é is missing entirely from his name (I left that one as-is so you can check it out). Any idea what's up with those names? Thanks again! On Thu, May 19, 2016, at 13:50, Ewa Jodlowska (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, Betsy > Waliszewski > > Ewa Jodlow > *Ewa Jodlowska* > May 19, 10:50 AM > Hi Carmen - > I checked it out and the YouTube link through works great. > Thanks again! > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 19, 10:44 AM > Hi Ewa, > > Great to hear that this workaround is fine! I have gone ahead and > disabled the original YouTube module! > > Please let me know if anything else needs to be done! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 19, 6:48 AM > Hi Carmen - the web view YouTube module is great! Let us proceed with > that workaround. > Can I disable the original YouTube module? > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 18, 3:52 PM > Hi Ewa, > > My team and I did some investigating and concluded there is a bug > within the web version that doesn't allow for YouTube to be connect > via the module. The bug will most likely not be fixed in time for your > conference. > > However, we did find a workaround! If we include a web view module of > the youtube channel it will work! We have added that to the guide now > for you to check out. The module is called "Web View YouTube" and > provides a link to YouTube page. We would be able to change the name > to YouTube and the icon to a YouTube icon as well. Would this > workaround work? > > Please check it out and let me know so I can edit it! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 18, 1:39 PM > Hi Carmen - > From the web version the YouTube link does not work. I do confirm that > from my phone app, it does work. > I will check out the Sponsor Workshop and schedule updates. > Thank you so much for working so diligently on all of our requests! We > appreciate you being so prompt with everything. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 18, 1:32 PM > Hi Ewa and Felix, > > A few updates!: > > -Sponsor tutorials have been added to the master schedule. The > schedule should be complete now with all tracks, descriptions, and > abstracts! > -Unfortunately the Sponsor Banner section randomly shows banner ads. > There is no way to dictate which comes first. > -Are you still experiencing issues with YouTube? I just opened the > YouTube channel successfully through the guide on an iOS device! > > Please let me know if you have any questions! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 18, 7:39 AM > When I try the YouTube link that Felix sent below, it works fine. > However when I click on it from the Guide, it takes me to the youtube > page that says "this channel does not exist" > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > > Ewa Jodlow > *Ewa Jodlowska* > May 18, 6:32 AM > Hi Carmen, > Under the Sponsor Banner section, I am unable to move the banners > around to dictate which one will come first, second, etc. Is > there a way for you to do it behind the scenes? I just need > Heroku to be first. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > > Felix Crux > *Felix Crux* > May 17, 4:40 PM > Yes, please, I think so, since the other schedules include them > as well. > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 17, 4:37 PM > Hi Felix, > > Awesome to hear YouTube now works! The new sponsor tutorials file you > sent over includes breaks and lunches (the original file did not > include this). Did you want these included? > > Please let me know! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Felix Crux > *Felix Crux* > May 17, 4:30 PM > Not sure if someone changed some settings on YouTube (maybe like > Carmen said it wasn't public?) but now when I go there I get > redirected to this URL: > https://www.youtube.com/channel/UCwTD5zJbsQGJN75MwbykYNw and when I > entered that into the Builder it works! > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 17, 4:21 PM > Hi Felix and Ewa, > > No worries! Thank you for sending this along > > My team has done some investigating into the YouTube Situation. I > think there is a problem with the link given. Additionally, when I > search for the channel it doesn't appear in Youtube. Can you try > checking to make sure that the channel is public? Additional it may > work for the person that owns the YouTube account to log ing and give > the url of the dashboard! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Felix Crux > *Felix Crux* > May 17, 4:21 PM > D'oh! Apparently Ewa was way faster than me and I didn't read my new > email before replying :) I've attached her version too, which has more > details! > > > On Tue, May 17, 2016, at 19:05, Felix Crux wrote: > > On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: > > > I cannot find a file that has dates and times for the sponsor > > > tutorials. Can someone please send one along? > > > > Ouch, sorry, that's my fault. I didn't catch the fact that our > > website's data exporter isn't including that information for > > sponsored tutorials, when it should. I will produce a data file for > > you manually and send it right away, and then right afterwards I'll > > file a bug with our site's developers asking for that information to > > be included in the future. Sorry about that! > > > > > > On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: > >> > Attachment(s) sponsor_tutorial.csv[1] > > Felix Crux > *Felix Crux* > May 17, 4:20 PM > Attached! > > > On Tue, May 17, 2016, at 19:05, Felix Crux wrote: > > On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: > > > I cannot find a file that has dates and times for the sponsor > > > tutorials. Can someone please send one along? > > > > Ouch, sorry, that's my fault. I didn't catch the fact that our > > website's data exporter isn't including that information for > > sponsored tutorials, when it should. I will produce a data file for > > you manually and send it right away, and then right afterwards I'll > > file a bug with our site's developers asking for that information to > > be included in the future. Sorry about that! > > > > > > On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: > >> > Attachment(s) sponsor-tutorials-schedule.csv[2] > > Felix Crux > *Felix Crux* > May 17, 4:05 PM > On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: > > I cannot find a file that has dates and times for the sponsor > > tutorials. Can someone please send one along? > > Ouch, sorry, that's my fault. I didn't catch the fact that our > website's data exporter isn't including that information for sponsored > tutorials, when it should. I will produce a data file for you manually > and send it right away, and then right afterwards I'll file a bug with > our site's developers asking for that information to be included in > the future. Sorry about that! > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 17, 3:54 PM > Hi Ewa and Felix, > > I have approved the guide! I am working on fixing the Youtube > situation! I cannot find a file that has dates and times for the > sponsor tutorials. Can someone please send one along? > > The talks and tutorials have been updated in the schedule! I think the > sponsor tutorial is the last part of the schedule needed! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 17, 3:51 PM > Hey Carmen - > Do you happen to know how long the guide approval process takes? Do we > have to wait until tomorrow to have it approved for publishing? > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > FYI - I have disabled YouTube for the time being so I could get the > guide in the publishing queue. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > On Tue, May 17, 2016 at 5:08 PM, Ewa Jodlowska <ewa(a)python.org> wrote: > No worries on getting all of that done by 5pm today! We can always > push updates up through May 28th. > Builder will not allow me to publish the guide though without > resolving the YouTube link error. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > On Tue, May 17, 2016 at 5:04 PM, Felix Crux > <felixc(a)felixcrux.com> wrote: > Thank you for your efforts! As long as we can push updates later we > can always tweak the details as we go. Please let me know if there's > anything I can do on my end to make it easier. > > Ewa Jodlow > *Ewa Jodlowska* > May 17, 3:14 PM > FYI - I have disabled YouTube for the time being so I could get the > guide in the publishing queue. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > No worries on getting all of that done by 5pm today! We can always > push updates up through May 28th. > Builder will not allow me to publish the guide though without > resolving the YouTube link error. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > On Tue, May 17, 2016 at 5:04 PM, Felix Crux > <felixc(a)felixcrux.com> wrote: > Thank you for your efforts! As long as we can push updates later we > can always tweak the details as we go. Please let me know if there's > anything I can do on my end to make it easier. > > Ewa Jodlow > *Ewa Jodlowska* > May 17, 3:09 PM > No worries on getting all of that done by 5pm today! We can always > push updates up through May 28th. > Builder will not allow me to publish the guide though without > resolving the YouTube link error. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > Thank you for your efforts! As long as we can push updates later we > can always tweak the details as we go. Please let me know if there's > anything I can do on my end to make it easier. > > Felix Crux > *Felix Crux* > May 17, 3:04 PM > Thank you for your efforts! As long as we can push updates later we > can always tweak the details as we go. Please let me know if there's > anything I can do on my end to make it easier. > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 17, 3:00 PM > Hi Felix, > > I have found a workaround to include the description and the abstract. > It is difficult because the tutorials schedule also has non listed > schedule items in the tutorials presentations folder like breakfast > for example. > > I am doing my absolute best to get this done by 5 PM today so you guys > can launch. However, I cannot guarantee it will be done by then. I > just finished fixing the talk sessions and am now getting through > tutorial and sponsor tutorials! I will keep you updated with my > progress! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Felix Crux > *Felix Crux* > May 17, 2:32 PM > Hi again, > > Were you able to find the data? I just got access to the files so I > can confirm and give you more details. While the files under pycon-2016-guidebook-data-2016-05- > 13/schedule/ (for example, talks_schedule.csv) only contain the > abstract, the ones under pycon-2016-guidebook-data-2016-05- > 13/presentations/ (e.g. talk.csv) have both the abstract and the > description. > > Does that work for you? Sorry for the mixup; I should've provided just > one file with all the data, but this was what I had access to right > off the bat and I didn't want to slow things down too much while I > copied things around. > > Felix Crux > *Felix Crux* > May 17, 11:10 AM > Hi Carmen, > That's great to hear; I'm super glad LibreOffice does the trick! > I'm at work right now without access to my home computer so I can't > check, but if the description and the abstract fields aren't both > present in the "schedule" files, they should at least be there in the > "talks", "tutorials" etc. files. > I can't remember the exact filenames right now, but check under the > "talks" folder instead of the "schedule" one? > If it's too much trouble to combine the data from two files then I can > try to get you one later this evening that puts it all in one place, > but I won't be able to do so right away. > Thanks, > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 17, 10:55 AM > Hi Felix, > > I opened the data in the LibreOffice and am getting no weird errors on > the data! The schedules sent over do not have a description in them, > only the abstract. A couple questions for clarification, is the > abstract column really the description? If you want the abstract and > description included in the description of each session do you have an > excel document for the schedule where the abstract is within the > description column or there is a column for abstract and description? > > It will take me a couple of hours to format the schedule and get it > uploaded. I want to be sure to hit the 5pm CT launch goal so please > get back to me as soon as possible so I can get started on the > editing! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 17, 9:03 AM > Hi Carmen - > Once you add the sponsor workshops to the master schedule, please let > us know. I will publish the app at that point. We are emailing all of > our attendees today at 5pm CT with the link. > Also - we have attempted to add our YouTube channel, but builder does > not want to accept the link. Can you please take a look at that for > us? The link is https://www.youtube.com/c/PyCon2016. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > Hi Carmen, > > 1) Sounds like the tutorial survey is gone, so all good here! > > 2) I think the easiest thing to do is just deactivate the "Speakers" > list, since everyone is listed already under their respective > categories (e.g. Talk Speakers, Tutorial Speakers, etc). If that's > OK with everyone, I think that's simplest? > > 3) No worries; thanks for fixing it! > > 4) That's interesting; it sounds like Excel isn't happy with UTF-8 > text. I don't have a Windows computer to check with, but some > searching online suggests that if one opens the files directly then > Excel is pretty bad at automatically detecting what kind of text > they contain. The workaround that people suggest is that instead of > opening by double-clicking or going to the File > Open menu one can > use Excel's "Import" functionality. I'm guessing that's under FIle > > Import or something similar. In the window that pops up it should > be possible to tell Excel explicitly that these are UTF-8 files. > However you may also have to specificy other things about the files > instead of Excel guessing them. The ones I can think of off the top > of my head are: file encoding is UTF-8, the values are comma- > separated, and the first row is column headings. Could you please > try that process and see if it works? In the meantime I'll also > investigate if there's anything I can change on my end to make > Excel pick this up automatically. Sorry for the confusion; UTF-8 is > pretty standard but I didn't know that Excel in particular has a > hard time with it. > > 5) That's great; thanks! Otherwise I can manually tweak it as we go; > it's not launch-blocking. > > 6) Yes please, if they're part of the Master Schedule that would be > best. Thank you! > > 7) Sounds like this mystery has been solved, so all is well! Just > wanted to make sure there weren't different sources of data > floating around. > > Thank you again for getting everything sorted! > > Felix Crux > *Felix Crux* > May 16, 7:40 PM > On Mon, May 16, 2016, at 19:19, Betsy Waliszewski wrote: > > I was the one that added: (language, stdlib, etc.). I thought it was > > missing. Sorry about that. > > No worries! I think it's fine either way; I just wanted to make sure I > didn't have an inconsistency in the data I was sending. Cheers! > > Felix Crux > *Felix Crux* > May 16, 7:37 PM > Hi Carmen, > > 1) Sounds like the tutorial survey is gone, so all good here! > > 2) I think the easiest thing to do is just deactivate the "Speakers" > list, since everyone is listed already under their respective > categories (e.g. Talk Speakers, Tutorial Speakers, etc). If that's > OK with everyone, I think that's simplest? > > 3) No worries; thanks for fixing it! > > 4) That's interesting; it sounds like Excel isn't happy with UTF-8 > text. I don't have a Windows computer to check with, but some > searching online suggests that if one opens the files directly then > Excel is pretty bad at automatically detecting what kind of text > they contain. The workaround that people suggest is that instead of > opening by double- clicking or going to the File > Open menu one > can use Excel's "Import" functionality. I'm guessing that's under > FIle > Import or something similar. In the window that pops up it > should be possible to tell Excel explicitly that these are UTF-8 > files. However you may also have to specificy other things about > the files instead of Excel guessing them. The ones I can think of > off the top of my head are: file encoding is UTF-8, the values are > comma-separated, and the first row is column headings. Could you > please try that process and see if it works? In the meantime I'll > also investigate if there's anything I can change on my end to make > Excel pick this up automatically. Sorry for the confusion; UTF-8 is > pretty standard but I didn't know that Excel in particular has a > hard time with it. > > 5) That's great; thanks! Otherwise I can manually tweak it as we go; > it's not launch-blocking. > > 6) Yes please, if they're part of the Master Schedule that would be > best. Thank you! > > 7) Sounds like this mystery has been solved, so all is well! Just > wanted to make sure there weren't different sources of data > floating around. > > Thank you again for getting everything sorted! > > Betsy Wali > *Betsy Waliszewski* > May 16, 4:19 PM > Hi Felix, > I was the one that added: (language, stdlib, etc.). I thought it was > missing. Sorry about that. > Betsy > Also, a question about that: in the data files I sent you, I tried to > convert the category "Python Core (language, stdlib, etc.)" to just > say "Python Core". As far as I can tell, the text "(language, stdlib, > etc.)" shouldn't show up anywhere. Yet I'm seeing it on some of the > talks in the guide. Did I miss converting the data somewhere, or did > you get different data from the conference website or something like > that? I'd prefer if we could stick to just the data in the exported > files that I sent over, since there are a number of minor tweaks like > that in it. > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 16, 3:58 PM > Hi Ewa and Felix, > > Below are the answers to all your questions. Please let me know if I > missed something! > > 1. The tutorial survey in the menu was copied over from last year (I > cloned last year's guide and some things carried over). Just say > the words and I can delete this item! It is not necessary to have! > > 2. I believe the speaker list was sent over to me in the folder of > initial data. It only included those names. Please let me know if > you would like me to remove the incomplete list or make edits! > > 3. I apologize for the abstract being listed twice, thank you for > catching that! We can have both the description and the abstract > in the description of a schedule item. I concatenated the two > columns in excel along with everything else included in the > description and must have made an error in the formula, I > apologize and will fix it! > > 4. Before I redo the schedule I need to clarify the non-ASCII text > with you! When I open the excel documents that were sent over, many > of the lines have the errors similar to the example you give me > (Weâ€™ll examine a number of popular licenses, and in what ways > they differ â€"). When I open the excel documents on my end, these > errors appear. They then appear in Builder because I use the data > from the excel document and format it in another excel document to > upload the information in Builder. Do you have data without these > errors? Or are you not seeing these errors when you open the excel > document on your end? Please let me know so we can figure out where > the disconnect and errors within the data is coming from! > > 5. Regarding the category in the description, I was following the > format of last year's guide! I will change it to how you listed it > below when I redo the schedule! > > 6. As far as Sponsor Tutorials, last year's guid has them listed as a > custom list, not in the schedule. If you would like me to add them > to the master schedule I can definitely get that done! Please just > let me know! > > 7. I am not sure if I understand what you are referring to when you > talk about Python Core? Can you give me a bit more details to > clarify? Thank you! > > I will get these edits done (which mainly are all within the master > schedule) once I receive confirmation on having the sponsor tutorials > included and more details about the ASCII text! Please let me know > your thoughts so we can move forward in a timely manner! > > Thank you! > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 15, 10:10 AM > Hi everyone! > I have a couple of random questions as we approach the launch! > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the > bottom of the main left-hand menu. Is that meant to be there, given > that the tutorials all seem to have their own survey link embedded > within their own page? > Hi Felix - I have disabled the "tutorial survey" link. > > Felix Crux > *Felix Crux* > May 15, 8:06 AM > Hi Carmen, > In addition to the "Speakers" issue mentioned in my previous email, > I've found a number of serious data problems when reviewing everything > in detail today. These are major issues that would prevent launching > the guide to the public in the near future. > 1) Talks/Tutorials have the "Abstract" listed twice, instead of the > "Description" field. For example, looking at my talk: > https://builder.guidebook.com/#/guides/66563/build/schedule/sessions/137160… > we can see that the text starts out with "Free/Open Source software > is...". If you then scroll down a bit, you can see it says > "Abstract" in bold, and then the same text repeats. However, the > Description part (which starts out with "Anyone who uses Open > Source...") just isn't present anywhere. I'm guessing something in > the data import on your side was supposed to put the description > first, followed by the abstract, but instead the abstract got > included twice. Including both would be best, but if something on > your end means that only one of the two can be used, I'd prefer to > have the description, not the abstract. > 2) All non-ASCII text has serious character encoding problems. In my > initial email I used the example of someone whose name contains the > letter "Ł" (Łukasz Langa). If you find him in the guide, you'll see > that he shows up as "ukasz Langa", i.e. the first letter of his > name is completely missing > (https://builder.guidebook.com/#/guides/66563/build/custom-list-items/540277…) > . The same thing happens in a bunch of other names and talk > descriptions. Using my talk again as an example > (https://builder.guidebook.com/#/guides/66563/build/schedule/sessions/137160…) > . There's a sentence in the abstract that should read "We’ll > examine a number of popular licenses, and in what ways they differ > — and how you can use them to achieve different goals." This > sentence uses a curly-quote in "We'll", and a dash between "ways > they differ" and "and how you can use them". In the Guidebook text, > however, that's all gone. Instead, the first time the abstract > shows up, those characters are completely missing; instead it says > "Well examine a number of popular licenses, and in what ways they > differ and how you can use them to achieve different goals." Note > the "well" instead of "we'll", and how the two clauses are just run > together without a dash between them. The second time the sentence > shows up in the second abstract, those characters are completely > mangled: "Weâ€™ll examine a number of popular licenses, and in what > ways they differ â€" and how you can use them to achieve different > goals." I'm guessing something in the import process isn't reading > UTF-8 encoded text properly. > 3) Sponsor tutorials do not show up in the Master Schedule. It looks > like they're entered as just a list, not as scheduled items? > There's no track for them and attendees can't add them to their > calendars. > 4) There are also a smaller item that I'm working on fixing from my > end, but if there's something you can do on your side to make the > changes automatically with your tools that would be great: Talks > aren't in tracks according to their categories and levels. Instead > the name of the category is just in the description. For example, > in my talk, it says "Novice - Community", instead of it being part > of the "Level: Novice", and "Category: Community" tracks. I've > fixed this for all the Tutorial sessions, and will work my way > through talks doing the same thing soon. > Also, a question about that: in the data files I sent you, I tried to > convert the category "Python Core (language, stdlib, etc.)" to just > say "Python Core". As far as I can tell, the text "(language, stdlib, > etc.)" shouldn't show up anywhere. Yet I'm seeing it on some of the > talks in the guide. Did I miss converting the data somewhere, or did > you get different data from the conference website or something like > that? I'd prefer if we could stick to just the data in the exported > files that I sent over, since there are a number of minor tweaks like > that in it. > On the plus side, I'm happy to report that the "Preview in app" export > seems to be working now. I'm guessing something was just stuck > yesterday, but it's fine now. > Thanks, > On Sat, May 14, 2016, at 13:33, Felix Crux wrote: > > Hi everyone! > > > > I have a couple of random questions as we approach the launch! > > > > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the > > bottom of the main left-hand menu. Is that meant to be there, given > > that the tutorials all seem to have their own survey link embedded > > within their own page? > > > > Carmen, I'm having trouble with the "Preview in app" export feature. > > After making changes on the web, I'm deleting the local copy on my > > phone and generating a new preview export on the website. However > > when I enter the password and download the new version it doesn't > > actually have any of my changes -- it's still the old one! Any idea > > of what I might be doing wrong? > > > > Also for Carmen: I'm a bit confused by the "Speakers" list in the > > main menu. It doesn't seem to contain all of the speakers, but I > > can't figure out what the pattern is of who is included and who's > > not. Is it just something left over that should be deleted? Or > > should it be updated to include everyone? > > > > I also ran another data export to pull a few last minute changes. > > There were only a few, so I've gone ahead and made all the changes > > to the guide already. I'm just mentioning it here and attaching the > > latest data export so that if anyone needs it we can all be working > > off the same base. > > > > Cheers! > > > > > > > > On Wed, May 04 11:55, Carmen Kuncz (Guidebook) wrote: > > > > > Felix Crux > *Felix Crux* > May 14, 10:34 AM > Hi everyone! > I have a couple of random questions as we approach the launch! > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the > bottom of the main left-hand menu. Is that meant to be there, given > that the tutorials all seem to have their own survey link embedded > within their own page? > Carmen, I'm having trouble with the "Preview in app" export feature. > After making changes on the web, I'm deleting the local copy on my > phone and generating a new preview export on the website. However when > I enter the password and download the new version it doesn't actually > have any of my changes -- it's still the old one! Any idea of what I > might be doing wrong? > Also for Carmen: I'm a bit confused by the "Speakers" list in the main > menu. It doesn't seem to contain all of the speakers, but I can't > figure out what the pattern is of who is included and who's not. Is it > just something left over that should be deleted? Or should it be > updated to include everyone? > I also ran another data export to pull a few last minute changes. > There were only a few, so I've gone ahead and made all the changes to > the guide already. I'm just mentioning it here and attaching the > latest data export so that if anyone needs it we can all be working > off the same base. > Cheers! > Attachment(s) pycon-2016-guidebook-data-2016-05-13.zip[3] > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 4, 4:55 PM > Hi Ewa and Felix, > > Requested edits have been made! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 4, 4:08 PM > Hi Ewa, > > Will do! Let me know about Heroku! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 4, 3:12 PM > Hmm ok then for the Lyft message I added the info as a custom list. > For the Heroku ad I will think about what to do :) > Thanks Carmen. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 4, 2:59 PM > Hi Ewa, > > Unfortunately that is not possible. We do use push notifications but > they cannot include an image. > > Please let me know if you have any other questions! > > Best, > > Carmen > > Carmen Kuncz Customer Success Associate Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 4, 2:48 PM > Hi Carmen - > I was thinking of more of a pop up message when the app is opened. Is > that possible? For the banner ads we will have our top sponsor logos > appearing. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 4, 1:04 PM > Hi Ewa, > > It sounds like you might be wanting banner ads? Where the ad appears > at the bottom of the app and when users click it it can bring them to > either a website or description (sounds like we will use the > description!) The banner ads appear in random order and rotate every > 5,10, 20, or 30 seconds! Up to you! > > Let me know your thoughts! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 4, 9:46 AM > Hi Carmen, > We need to add in two pop up messages for the Guide. Is it possible? > It would be great if we can rotate the two every time the app is > opened. If so, below is what we need: > * Lyft discount code. I am attaching the logo that can be used. The > text can be: > "COUPON CODE: PYCON 20% off coupon which can be used on 4 rides in the > geofenced area. The total discount off each ride cannot exceed $10" > * Keystone sponsor: I am attaching their pop-up design. If this size > does not work, please let me know. > Best regards, > Ewa Director of Operations Python Software Foundation Cell: 415-319- > 5237 > Attachment(s) 1024x768 (2).png[4] Logo Mighty Pink.png[5] > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 3, 5:23 PM > Hi Felix, > > Speakers have been linked and sponsor logos have been uploaded! I will > let you know when I have completed the list of edits you sent me! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 3, 10:19 AM > Hi Felix, > > I will make these edits throughout this week and let you know when I > have completed this as well as uploading the final bit of content! > Please reach out if you have any questions or any additional edits > that need to be made! > > Best, > > Carmen > Carmen Kuncz Customer Success Associate Guidebook > > > Felix Crux > *Felix Crux* > May 1, 4:27 PM > Thanks Carmen! I haven't had a chance to check it all out in depth > yet, but what I've seen so far looks good! > I've just run another data export to make sure we've got all the > latest content. I've attached it to this email. > The changes relative to last export (2016-04-13) are: > * Removed poster "Statistical Machine Translation with NLTK > (Reloaded)". > * Removed poster "The Art of Turtle Programming". > * Updated info for sponsor tutorial "IBM: Hands-on session: Developing > analytic applications using Apache Spark™ and Python". > * New sponsor tutorial: "Heroku 101: Deploying Python Web > Applications". > * Updated speaker name for talk "Diff It To Dig It". > * Updated description for talk "Prototyping New APIs with Flask". > * Updated description for tutorial " Efficient Python for High- > Performance Parallel Computing". > * Removed speaker Al Sweigart. > * Removed speaker Liling Tan. > * Updated bio for speaker Anton Malakhov. > * Updated bio for speaker Russia Madden. > * New sponsor tutorial speaker bio for David Taieb. > * Changed name for speaker Sep Ehr (to Seperman). > * New Coffee Sponsor "Indeed Prime". > * Changed Gold sponsor "Venmo" to "Venmo / Braintree". > * New Job Fair Sponsor "Amazon Web Services". > * New Job Fair Sponsor "Virtustream". > * Updated description for Keystone Sponsor "Heroku". > * New Platinum sponsor "New Relic". > * Updated description for Silver Sponsor "CrossCompute". > Phew! That list is longer than I expected; but most of the changes in > it are pretty small. > Thanks again for getting all the content in so we can preview it. I'll > try to confirm this week (or at the latest next weekend) that those > empty files are meant to be that way and let you know. > All the best, > Felix > Attachment(s) pycon-2016-guidebook-data-2016-05-01.zip[6] > > Carmen Kun > *Carmen Kuncz* (Guidebook) > 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(a)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 Jodlow > *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 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 > > > 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[7] > > 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 > > > 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 :) > > 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 > > 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, > > 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(a)python.org and I believe Felix's is under felixc(a)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[8] > > 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, <a>, <a href & strong. > > 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 <br>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 <h3>, > <a>, and <pre> or <code>. > 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 <br> for single breaks and > <br><br> 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 (<br>) or paragraphs (<p>)? If it doesn't matter I'll likely go > with paragraphs. > What about other formatting, like Markdown headings; should they be > turned into <h1>s etc? Bolded text that's currently **like this** into > <strong> or <b>? 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[9] > > 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[10] > > 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[11] > > 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[12]. > [N2DQPZ-696N] > Links: 1. https://support.guidebook.com/attachments/token/vvIsJM4n3kR1uWwCuoNvfF6Lt/?… 2. https://support.guidebook.com/attachments/token/rVVkLimDfMhSmLbaff25XMhBU/?… 3. https://support.guidebook.com/attachments/token/ZmLdVdosXdeYS6jlnGXqY6utb/?… 4. https://support.guidebook.com/attachments/token/9kX7GaszJwlxeJDeyfxLfopH1/?… 5. https://support.guidebook.com/attachments/token/mmPgsrklV1piXtoJ1RuPGxQPX/?… 6. https://support.guidebook.com/attachments/token/e59emWjkthWCFjOIqG5hqtUfD/?… 7. https://support.guidebook.com/attachments/token/iaSl7nrPA5v9029GQ3iivK5RZ/?… 8. https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?… 9. https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?… 10. https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?… 11. https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?… 12. http://www.zendesk.com

1 0

[Guidebook] Update: Intro to Guide Building Team!
by Carmen Kuncz (Guidebook) May 18, 2016

May 18, 2016

##- 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(a)python.org and I believe Felix's is under felixc(a)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/?… ---------------------------------------------- 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, \<a\>, \<a href & strong. 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 <br>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 <h3>, <a>, and <pre> or <code>. 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 \<br\> for single breaks and \<br\>\<br\> 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 (<br>) or paragraphs (<p>)? If it doesn't matter I'll likely go with paragraphs. What about other formatting, like Markdown headings; should they be turned into <h1>s etc? Bolded text that's currently **like this** into <strong> or <b>? 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/?… ---------------------------------------------- Carmen Kuncz, Apr 4, 10:02 AM Hi Felix, Thank you for sending this along! I will take a look at everything and start working on inputing this information to the guide within the next few days! I will reach out if I have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, Apr 3, 7:01 PM Hi Carmen, Please find attached an initial attempt at bundling up all the content into a usable export. I hope it's workable enough to get things going, but I'll follow up shortly with whatever is else is needed. The attached zip file should contain comma-separated (.csv) files with the details of all the talks, speakers, etc. The first line of each file has headings describing what each column is. Note that some rows (particularly speaker bios and talk descriptions) contain embedded newlines, but all of those entries should additionally be enclosed in double quotation marks. The files are UTF-8 encoded, and several of the speakers do have names containing non-ASCII characters like 'Ł', 'é', etc, so that's worth watching out for. There are also logo images for all the sponsors in the zip file. *Talk descriptions are currently exported as raw, unprocessed, Markdown*. I'm not sure what kind of formatting Guidebook supports, so I've left that as-is for now. If there's something more useful I can convert it to, just let me know. I do think we'll want to figure out how to process that formatting and get it reflected in the app, though. There's currently nothing in the data export that *links speakers to their talks*, which I know the app can do. If there's some data format that can be bulk-imported to your systems to get that automatically, just let me know and I'd be happy to work on it. In previous years, however, we just linked them up manually. Please don't hesitate to *let me know if there's any way I can process or rework the data* to make it easier for you/your tools to work with -- the nice thing about being a programming conference is we're generally happy to build our own tools to make things simpler! I would much rather put in the work on my end to automate whatever data processing you need to make it possible to bulk-upload changes, instead of having you or me need to go in and fix things manually one-by-one. At present, this is the* list of issues/missing data *that I'm aware of and am working on: * Keynote speakers are not included in the speaker bios. * Plenary sessions (e.g. keynotes, opening remarks) are just listed as "plenary" with no description in the schedule. * Special events (e.g. PyLadies auction, 5K run, dinners) are not included in the schedule (special_events_schedule.csv is empty). * Meals/breaks show up once per track/room, but they really should just be listed once. * "Special" pages such as venue information, code of conduct, etc. may need to be input manually - I don't mind doing it. * Speaker photos are not included (maybe that's OK -- we didn't have them last year either). * As mentioned earlier, some text is in raw Markdown; and I don't know if that's a format Guidebook can ingest. * Floor plan map is on its way, and we'll need to link talks to the room they're in. * Some general information still TBD; I will get it to you ASAP (see below). Finally, here's the *info your requested in in the Guide Basics spreadsheet*: Guide Name: PyCon 2016 Guide Start Date: 2016-05-28 Guide End Date: 2016-06-05 Timezone: Pacific Daylight Time (PDT) (UTC -7) General Information, Venue, Icon, Cover Image, Maps: I will get these to you ASAP, or just fill them in myself and let you know. Facebook: https://www.facebook.com/us.pycon.org Twitter: https://twitter.com/pycon YouTube: Not set up yet, will let you know Photos: No (I think, for now at least) RSS Feed: http://pycon.blogspot.com/feeds/posts/default?alt=rss Homepage: https://us.pycon.org/2016/ Feedback/Surveys: I believe we'll use this, but I don't think the survey has been designed yet. Will get it to you. Notifications: Sure, let's have this. My Schedule: Definitely want this feature. Notes: Sounds good. Live polling: I don't think we'll use this. All right, I think that's most of it for now? Sorry for the enormous email; I'm trying to be very thorough both to keep everyone in the loop and to remind myself of exactly what work I still need to do! Again, please don't hesitate to let me know if I can change or process the data in any way to make it easier for you, or if anything in the export looks weird -- it's all automated, so it's entirely possible something broken snuck through without human review. Cheers; all the best! -- Felix Attachment(s): pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?… ---------------------------------------------- Carmen Kuncz, Mar 30, 12:18 PM Hi Ewa, No rush on getting the content to me! I just didn't want to miss a deadline for you! Please send me the content as you get it! Reach out if you have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Mar 30, 11:08 AM Hi Carmen, Thank you for checking in! I am not yet ready to start this yet. I will begin the process on Friday of this week and I will ping you if there are any questions. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Mar 30, 11:00 AM Hi Ewa, Just checking in again to see if you have any guide content for me? I know we were initially shooting for an April 1st internal launch date! Please let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Carmen Kuncz, Mar 21, 10:06 AM Hi Ewa, Just checking in to see if you have any content for me to start building your guide? Let me know, I am excited to get started on this! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 2:01 PM Yes, that is my cell phone number. Talk to you tomorrow! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:58 PM Hi Ewa, 1 PM PST tomorrow will work great! Can I call you on the cell phone number you have listed below? If not please let me know which number is best to reach you at! Looking forward to our call! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 1:50 PM Hi Carmen, Let's chat at 1pm PT tomorrow. Have a good afternoon! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:25 PM Hi Ewa, Are you possibly available tomorrow? I am free to speak anytime between 10 AM PST to 4PM PST. Let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 12:22 PM Hi Carmen, Are you available this afternoon? I am available any time now until about 4pm CT. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 10:55 AM Hi Ewa, It's great to e-meet you! My name is Carmen, and I'll be working with you to create your guide. Lets start by scheduling a call to discuss your guide. This will help me get a good vision for your guide as well as to propose a tentative timeline for an on-time release! Please let me know your availability so we can schedule a time! I have attached a Guide Basics Spreadsheet (will appear as a link). Please take a brief look at it before our call! I'm very excited to get started! Let me know your availability and if you have any questions, feel free to reply to this thread (rather than creating a new ticket -- things can get messy rather fast). You can also call my direct extension at 650-319-7233 ext. 222. Thanks again, and I look forward to hearing back from you! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook Attachment(s): Guide_Basics.xls - https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?… ---------------------------------------------- Katie Herrgesell, Feb 17, 10:46 AM Hi Ewa, I would like to introduce you to our awesome guide building team! They are the experts that will handle the data entry for you, and will work to create an easy to use event guide. I have shared your event information with the customer success team, and someone will be contacting you within one business day to get started on your guide. Good luck! Best, Katie -- Katie Herrgesell Sr. Corporate Account Manager Office: 650.319.7233 ext 126 Mobile: 216.570.0531 www.guidebook.com -------------------------------- This email is a service from Guidebook. [N2DQPZ-696N]

4 18

[Guidebook] Update: Intro to Guide Building Team!
by Carmen Kuncz (Guidebook) May 17, 2016

May 17, 2016

##- 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, Betsy Waliszewski ---------------------------------------------- Carmen Kuncz, May 17, 4:21 PM Hi Felix and Ewa, No worries! Thank you for sending this along My team has done some investigating into the YouTube Situation. I think there is a problem with the link given. Additionally, when I search for the channel it doesn't appear in Youtube. Can you try checking to make sure that the channel is public? Additional it may work for the person that owns the YouTube account to log ing and give the url of the dashboard! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, May 17, 4:21 PM D'oh! Apparently Ewa was way faster than me and I didn't read my new email before replying :) I've attached her version too, which has more details! On Tue, May 17, 2016, at 19:05, Felix Crux wrote: > On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: > > I cannot find a file that has dates and times for the sponsor > > tutorials. Can someone please send one along? > > Ouch, sorry, that's my fault. I didn't catch the fact that our > website's data exporter isn't including that information for sponsored > tutorials, when it should. I will produce a data file for you manually > and send it right away, and then right afterwards I'll file a bug with > our site's developers asking for that information to be included in > the future. Sorry about that! > > > On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: >> Attachment(s): sponsor_tutorial.csv - https://support.guidebook.com/attachments/token/vvIsJM4n3kR1uWwCuoNvfF6Lt/?… ---------------------------------------------- Felix Crux, May 17, 4:20 PM Attached! On Tue, May 17, 2016, at 19:05, Felix Crux wrote: > On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: > > I cannot find a file that has dates and times for the sponsor > > tutorials. Can someone please send one along? > > Ouch, sorry, that's my fault. I didn't catch the fact that our > website's data exporter isn't including that information for sponsored > tutorials, when it should. I will produce a data file for you manually > and send it right away, and then right afterwards I'll file a bug with > our site's developers asking for that information to be included in > the future. Sorry about that! > > > On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: >> Attachment(s): sponsor-tutorials-schedule.csv - https://support.guidebook.com/attachments/token/rVVkLimDfMhSmLbaff25XMhBU/?… ---------------------------------------------- Felix Crux, May 17, 4:05 PM On Tue, May 17, 2016, at 18:54, Carmen Kuncz (Guidebook) wrote: > I cannot find a file that has dates and times for the sponsor > tutorials. Can someone please send one along? Ouch, sorry, that's my fault. I didn't catch the fact that our website's data exporter isn't including that information for sponsored tutorials, when it should. I will produce a data file for you manually and send it right away, and then right afterwards I'll file a bug with our site's developers asking for that information to be included in the future. Sorry about that! ---------------------------------------------- Carmen Kuncz, May 17, 3:54 PM Hi Ewa and Felix, I have approved the guide! I am working on fixing the Youtube situation! I cannot find a file that has dates and times for the sponsor tutorials. Can someone please send one along? The talks and tutorials have been updated in the schedule! I think the sponsor tutorial is the last part of the schedule needed! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, May 17, 3:51 PM Hey Carmen - Do you happen to know how long the guide approval process takes? Do we have to wait until tomorrow to have it approved for publishing? Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 FYI - I have disabled YouTube for the time being so I could get the guide in the publishing queue. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 On Tue, May 17, 2016 at 5:08 PM, Ewa Jodlowska <ewa(a)python.org> wrote: No worries on getting all of that done by 5pm today! We can always push updates up through May 28th. Builder will not allow me to publish the guide though without resolving the YouTube link error. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 On Tue, May 17, 2016 at 5:04 PM, Felix Crux <felixc(a)felixcrux.com> wrote: Thank you for your efforts! As long as we can push updates later we can always tweak the details as we go. Please let me know if there's anything I can do on my end to make it easier. ---------------------------------------------- Ewa Jodlowska, May 17, 3:14 PM FYI - I have disabled YouTube for the time being so I could get the guide in the publishing queue. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 No worries on getting all of that done by 5pm today! We can always push updates up through May 28th. Builder will not allow me to publish the guide though without resolving the YouTube link error. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 On Tue, May 17, 2016 at 5:04 PM, Felix Crux <felixc(a)felixcrux.com> wrote: Thank you for your efforts! As long as we can push updates later we can always tweak the details as we go. Please let me know if there's anything I can do on my end to make it easier. ---------------------------------------------- Ewa Jodlowska, May 17, 3:09 PM No worries on getting all of that done by 5pm today! We can always push updates up through May 28th. Builder will not allow me to publish the guide though without resolving the YouTube link error. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 Thank you for your efforts! As long as we can push updates later we can always tweak the details as we go. Please let me know if there's anything I can do on my end to make it easier. ---------------------------------------------- Felix Crux, May 17, 3:04 PM Thank you for your efforts! As long as we can push updates later we can always tweak the details as we go. Please let me know if there's anything I can do on my end to make it easier. ---------------------------------------------- Carmen Kuncz, May 17, 3:00 PM Hi Felix, I have found a workaround to include the description and the abstract. It is difficult because the tutorials schedule also has non listed schedule items in the tutorials presentations folder like breakfast for example. I am doing my absolute best to get this done by 5 PM today so you guys can launch. However, I cannot guarantee it will be done by then. I just finished fixing the talk sessions and am now getting through tutorial and sponsor tutorials! I will keep you updated with my progress! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, May 17, 2:32 PM Hi again, Were you able to find the data? I just got access to the files so I can confirm and give you more details. While the files under pycon-2016-guidebook-data-2016-05- 13/schedule/ (for example, talks_schedule.csv) only contain the abstract, the ones under pycon-2016-guidebook-data-2016-05- 13/presentations/ (e.g. talk.csv) have both the abstract and the description. Does that work for you? Sorry for the mixup; I should've provided just one file with all the data, but this was what I had access to right off the bat and I didn't want to slow things down too much while I copied things around. ---------------------------------------------- Felix Crux, May 17, 11:10 AM Hi Carmen, That's great to hear; I'm super glad LibreOffice does the trick! I'm at work right now without access to my home computer so I can't check, but if the description and the abstract fields aren't both present in the "schedule" files, they should at least be there in the "talks", "tutorials" etc. files. I can't remember the exact filenames right now, but check under the "talks" folder instead of the "schedule" one? If it's too much trouble to combine the data from two files then I can try to get you one later this evening that puts it all in one place, but I won't be able to do so right away. Thanks, ---------------------------------------------- Carmen Kuncz, May 17, 10:55 AM Hi Felix, I opened the data in the LibreOffice and am getting no weird errors on the data! The schedules sent over do not have a description in them, only the abstract. A couple questions for clarification, is the abstract column really the description? If you want the abstract and description included in the description of each session do you have an excel document for the schedule where the abstract is within the description column or there is a column for abstract and description? It will take me a couple of hours to format the schedule and get it uploaded. I want to be sure to hit the 5pm CT launch goal so please get back to me as soon as possible so I can get started on the editing! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, May 17, 9:03 AM Hi Carmen - Once you add the sponsor workshops to the master schedule, please let us know. I will publish the app at that point. We are emailing all of our attendees today at 5pm CT with the link. Also - we have attempted to add our YouTube channel, but builder does not want to accept the link. Can you please take a look at that for us? The link is https://www.youtube.com/c/PyCon2016. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 Hi Carmen, 1) Sounds like the tutorial survey is gone, so all good here! 2) I think the easiest thing to do is just deactivate the "Speakers" list, since everyone is listed already under their respective categories (e.g. Talk Speakers, Tutorial Speakers, etc). If that's OK with everyone, I think that's simplest? 3) No worries; thanks for fixing it! 4) That's interesting; it sounds like Excel isn't happy with UTF-8 text. I don't have a Windows computer to check with, but some searching online suggests that if one opens the files directly then Excel is pretty bad at automatically detecting what kind of text they contain. The workaround that people suggest is that instead of opening by double-clicking or going to the File > Open menu one can use Excel's "Import" functionality. I'm guessing that's under FIle > Import or something similar. In the window that pops up it should be possible to tell Excel explicitly that these are UTF-8 files. However you may also have to specificy other things about the files instead of Excel guessing them. The ones I can think of off the top of my head are: file encoding is UTF-8, the values are comma-separated, and the first row is column headings. Could you please try that process and see if it works? In the meantime I'll also investigate if there's anything I can change on my end to make Excel pick this up automatically. Sorry for the confusion; UTF-8 is pretty standard but I didn't know that Excel in particular has a hard time with it. 5) That's great; thanks! Otherwise I can manually tweak it as we go; it's not launch-blocking. 6) Yes please, if they're part of the Master Schedule that would be best. Thank you! 7) Sounds like this mystery has been solved, so all is well! Just wanted to make sure there weren't different sources of data floating around. Thank you again for getting everything sorted! ---------------------------------------------- Felix Crux, May 16, 7:40 PM On Mon, May 16, 2016, at 19:19, Betsy Waliszewski wrote: > I was the one that added: (language, stdlib, etc.). I thought it was > missing. Sorry about that. No worries! I think it's fine either way; I just wanted to make sure I didn't have an inconsistency in the data I was sending. Cheers! ---------------------------------------------- Felix Crux, May 16, 7:37 PM Hi Carmen, 1) Sounds like the tutorial survey is gone, so all good here! 2) I think the easiest thing to do is just deactivate the "Speakers" list, since everyone is listed already under their respective categories (e.g. Talk Speakers, Tutorial Speakers, etc). If that's OK with everyone, I think that's simplest? 3) No worries; thanks for fixing it! 4) That's interesting; it sounds like Excel isn't happy with UTF-8 text. I don't have a Windows computer to check with, but some searching online suggests that if one opens the files directly then Excel is pretty bad at automatically detecting what kind of text they contain. The workaround that people suggest is that instead of opening by double- clicking or going to the File > Open menu one can use Excel's "Import" functionality. I'm guessing that's under FIle > Import or something similar. In the window that pops up it should be possible to tell Excel explicitly that these are UTF-8 files. However you may also have to specificy other things about the files instead of Excel guessing them. The ones I can think of off the top of my head are: file encoding is UTF-8, the values are comma-separated, and the first row is column headings. Could you please try that process and see if it works? In the meantime I'll also investigate if there's anything I can change on my end to make Excel pick this up automatically. Sorry for the confusion; UTF-8 is pretty standard but I didn't know that Excel in particular has a hard time with it. 5) That's great; thanks! Otherwise I can manually tweak it as we go; it's not launch-blocking. 6) Yes please, if they're part of the Master Schedule that would be best. Thank you! 7) Sounds like this mystery has been solved, so all is well! Just wanted to make sure there weren't different sources of data floating around. Thank you again for getting everything sorted! ---------------------------------------------- Betsy Waliszewski, May 16, 4:19 PM Hi Felix, I was the one that added: (language, stdlib, etc.). I thought it was missing. Sorry about that. Betsy Also, a question about that: in the data files I sent you, I tried to convert the category "Python Core (language, stdlib, etc.)" to just say "Python Core". As far as I can tell, the text "(language, stdlib, etc.)" shouldn't show up anywhere. Yet I'm seeing it on some of the talks in the guide. Did I miss converting the data somewhere, or did you get different data from the conference website or something like that? I'd prefer if we could stick to just the data in the exported files that I sent over, since there are a number of minor tweaks like that in it. ---------------------------------------------- Carmen Kuncz, May 16, 3:58 PM Hi Ewa and Felix, Below are the answers to all your questions. Please let me know if I missed something! 1. The tutorial survey in the menu was copied over from last year (I cloned last year's guide and some things carried over). Just say the words and I can delete this item! It is not necessary to have! 2. I believe the speaker list was sent over to me in the folder of initial data. It only included those names. Please let me know if you would like me to remove the incomplete list or make edits! 3. I apologize for the abstract being listed twice, thank you for catching that! We can have both the description and the abstract in the description of a schedule item. I concatenated the two columns in excel along with everything else included in the description and must have made an error in the formula, I apologize and will fix it! 4. Before I redo the schedule I need to clarify the non-ASCII text with you! When I open the excel documents that were sent over, many of the lines have the errors similar to the example you give me (Weâ€™ll examine a number of popular licenses, and in what ways they differ â€"). When I open the excel documents on my end, these errors appear. They then appear in Builder because I use the data from the excel document and format it in another excel document to upload the information in Builder. Do you have data without these errors? Or are you not seeing these errors when you open the excel document on your end? Please let me know so we can figure out where the disconnect and errors within the data is coming from! 5. Regarding the category in the description, I was following the format of last year's guide! I will change it to how you listed it below when I redo the schedule! 6. As far as Sponsor Tutorials, last year's guid has them listed as a custom list, not in the schedule. If you would like me to add them to the master schedule I can definitely get that done! Please just let me know! 7. I am not sure if I understand what you are referring to when you talk about Python Core? Can you give me a bit more details to clarify? Thank you! I will get these edits done (which mainly are all within the master schedule) once I receive confirmation on having the sponsor tutorials included and more details about the ASCII text! Please let me know your thoughts so we can move forward in a timely manner! Thank you! Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, May 15, 10:10 AM Hi everyone! I have a couple of random questions as we approach the launch! Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the bottom of the main left-hand menu. Is that meant to be there, given that the tutorials all seem to have their own survey link embedded within their own page? Hi Felix - I have disabled the "tutorial survey" link. ---------------------------------------------- Felix Crux, May 15, 8:06 AM Hi Carmen, In addition to the "Speakers" issue mentioned in my previous email, I've found a number of serious data problems when reviewing everything in detail today. These are major issues that would prevent launching the guide to the public in the near future. 1) Talks/Tutorials have the "Abstract" listed twice, instead of the "Description" field. For example, looking at my talk: https://builder.guidebook.com/#/guides/66563/build/schedule/sessions/137160… we can see that the text starts out with "Free/Open Source software is...". If you then scroll down a bit, you can see it says "Abstract" in bold, and then the same text repeats. However, the Description part (which starts out with "Anyone who uses Open Source...") just isn't present anywhere. I'm guessing something in the data import on your side was supposed to put the description first, followed by the abstract, but instead the abstract got included twice. Including both would be best, but if something on your end means that only one of the two can be used, I'd prefer to have the description, not the abstract. 2) All non-ASCII text has serious character encoding problems. In my initial email I used the example of someone whose name contains the letter "Ł" (Łukasz Langa). If you find him in the guide, you'll see that he shows up as "ukasz Langa", i.e. the first letter of his name is completely missing (https://builder.guidebook.com/#/guides/66563/build/custom-list-items/540277…). The same thing happens in a bunch of other names and talk descriptions. Using my talk again as an example (https://builder.guidebook.com/#/guides/66563/build/schedule/sessions/137160…). There's a sentence in the abstract that should read "We’ll examine a number of popular licenses, and in what ways they differ — and how you can use them to achieve different goals." This sentence uses a curly-quote in "We'll", and a dash between "ways they differ" and "and how you can use them". In the Guidebook text, however, that's all gone. Instead, the first time the abstract shows up, those characters are completely missing; instead it says "Well examine a number of popular licenses, and in what ways they differ and how you can use them to achieve different goals." Note the "well" instead of "we'll", and how the two clauses are just run together without a dash between them. The second time the sentence shows up in the second abstract, those characters are completely mangled: "Weâ€™ll examine a number of popular licenses, and in what ways they differ â€" and how you can use them to achieve different goals." I'm guessing something in the import process isn't reading UTF-8 encoded text properly. 3) Sponsor tutorials do not show up in the Master Schedule. It looks like they're entered as just a list, not as scheduled items? There's no track for them and attendees can't add them to their calendars. 4) There are also a smaller item that I'm working on fixing from my end, but if there's something you can do on your side to make the changes automatically with your tools that would be great: Talks aren't in tracks according to their categories and levels. Instead the name of the category is just in the description. For example, in my talk, it says "Novice - Community", instead of it being part of the "Level: Novice", and "Category: Community" tracks. I've fixed this for all the Tutorial sessions, and will work my way through talks doing the same thing soon. Also, a question about that: in the data files I sent you, I tried to convert the category "Python Core (language, stdlib, etc.)" to just say "Python Core". As far as I can tell, the text "(language, stdlib, etc.)" shouldn't show up anywhere. Yet I'm seeing it on some of the talks in the guide. Did I miss converting the data somewhere, or did you get different data from the conference website or something like that? I'd prefer if we could stick to just the data in the exported files that I sent over, since there are a number of minor tweaks like that in it. On the plus side, I'm happy to report that the "Preview in app" export seems to be working now. I'm guessing something was just stuck yesterday, but it's fine now. Thanks, On Sat, May 14, 2016, at 13:33, Felix Crux wrote: > Hi everyone! > > I have a couple of random questions as we approach the launch! > > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the bottom of > the main left-hand menu. Is that meant to be there, given that the tutorials > all seem to have their own survey link embedded within their own page? > > Carmen, I'm having trouble with the "Preview in app" export feature. After > making changes on the web, I'm deleting the local copy on my phone and > generating a new preview export on the website. However when I enter the > password and download the new version it doesn't actually have any of my > changes -- it's still the old one! Any idea of what I might be doing wrong? > > Also for Carmen: I'm a bit confused by the "Speakers" list in the main menu. > It doesn't seem to contain all of the speakers, but I can't figure out > what the pattern is of who is included and who's not. Is it just something > left over that should be deleted? Or should it be updated to include everyone? > > I also ran another data export to pull a few last minute changes. There were > only a few, so I've gone ahead and made all the changes to the guide already. > I'm just mentioning it here and attaching the latest data export so that if > anyone needs it we can all be working off the same base. > > Cheers! > > > > On Wed, May 04 11:55, Carmen Kuncz (Guidebook) wrote: > > ---------------------------------------------- Felix Crux, May 14, 10:34 AM Hi everyone! I have a couple of random questions as we approach the launch! Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the bottom of the main left-hand menu. Is that meant to be there, given that the tutorials all seem to have their own survey link embedded within their own page? Carmen, I'm having trouble with the "Preview in app" export feature. After making changes on the web, I'm deleting the local copy on my phone and generating a new preview export on the website. However when I enter the password and download the new version it doesn't actually have any of my changes -- it's still the old one! Any idea of what I might be doing wrong? Also for Carmen: I'm a bit confused by the "Speakers" list in the main menu. It doesn't seem to contain all of the speakers, but I can't figure out what the pattern is of who is included and who's not. Is it just something left over that should be deleted? Or should it be updated to include everyone? I also ran another data export to pull a few last minute changes. There were only a few, so I've gone ahead and made all the changes to the guide already. I'm just mentioning it here and attaching the latest data export so that if anyone needs it we can all be working off the same base. Cheers! Attachment(s): pycon-2016-guidebook-data-2016-05-13.zip - https://support.guidebook.com/attachments/token/ZmLdVdosXdeYS6jlnGXqY6utb/?… ---------------------------------------------- Carmen Kuncz, May 4, 4:55 PM Hi Ewa and Felix, Requested edits have been made! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Carmen Kuncz, May 4, 4:08 PM Hi Ewa, Will do! Let me know about Heroku! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, May 4, 3:12 PM Hmm ok then for the Lyft message I added the info as a custom list. For the Heroku ad I will think about what to do :) Thanks Carmen. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, May 4, 2:59 PM Hi Ewa, Unfortunately that is not possible. We do use push notifications but they cannot include an image. Please let me know if you have any other questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, May 4, 2:48 PM Hi Carmen - I was thinking of more of a pop up message when the app is opened. Is that possible? For the banner ads we will have our top sponsor logos appearing. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, May 4, 1:04 PM Hi Ewa, It sounds like you might be wanting banner ads? Where the ad appears at the bottom of the app and when users click it it can bring them to either a website or description (sounds like we will use the description!) The banner ads appear in random order and rotate every 5,10, 20, or 30 seconds! Up to you! Let me know your thoughts! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, May 4, 9:46 AM Hi Carmen, We need to add in two pop up messages for the Guide. Is it possible? It would be great if we can rotate the two every time the app is opened. If so, below is what we need: * Lyft discount code. I am attaching the logo that can be used. The text can be: "COUPON CODE: PYCON 20% off coupon which can be used on 4 rides in the geofenced area. The total discount off each ride cannot exceed $10" * Keystone sponsor: I am attaching their pop-up design. If this size does not work, please let me know. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 Attachment(s): 1024x768 (2).png - https://support.guidebook.com/attachments/token/9kX7GaszJwlxeJDeyfxLfopH1/?… Logo Mighty Pink.png - https://support.guidebook.com/attachments/token/mmPgsrklV1piXtoJ1RuPGxQPX/?… ---------------------------------------------- Carmen Kuncz, May 3, 5:23 PM Hi Felix, Speakers have been linked and sponsor logos have been uploaded! I will let you know when I have completed the list of edits you sent me! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Carmen Kuncz, May 3, 10:19 AM Hi Felix, I will make these edits throughout this week and let you know when I have completed this as well as uploading the final bit of content! Please reach out if you have any questions or any additional edits that need to be made! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, May 1, 4:27 PM Thanks Carmen! I haven't had a chance to check it all out in depth yet, but what I've seen so far looks good! I've just run another data export to make sure we've got all the latest content. I've attached it to this email. The changes relative to last export (2016-04-13) are: * Removed poster "Statistical Machine Translation with NLTK (Reloaded)". * Removed poster "The Art of Turtle Programming". * Updated info for sponsor tutorial "IBM: Hands-on session: Developing analytic applications using Apache Spark™ and Python". * New sponsor tutorial: "Heroku 101: Deploying Python Web Applications". * Updated speaker name for talk "Diff It To Dig It". * Updated description for talk "Prototyping New APIs with Flask". * Updated description for tutorial " Efficient Python for High-Performance Parallel Computing". * Removed speaker Al Sweigart. * Removed speaker Liling Tan. * Updated bio for speaker Anton Malakhov. * Updated bio for speaker Russia Madden. * New sponsor tutorial speaker bio for David Taieb. * Changed name for speaker Sep Ehr (to Seperman). * New Coffee Sponsor "Indeed Prime". * Changed Gold sponsor "Venmo" to "Venmo / Braintree". * New Job Fair Sponsor "Amazon Web Services". * New Job Fair Sponsor "Virtustream". * Updated description for Keystone Sponsor "Heroku". * New Platinum sponsor "New Relic". * Updated description for Silver Sponsor "CrossCompute". Phew! That list is longer than I expected; but most of the changes in it are pretty small. Thanks again for getting all the content in so we can preview it. I'll try to confirm this week (or at the latest next weekend) that those empty files are meant to be that way and let you know. All the best, Felix Attachment(s): pycon-2016-guidebook-data-2016-05-01.zip - https://support.guidebook.com/attachments/token/e59emWjkthWCFjOIqG5hqtUfD/?… ---------------------------------------------- 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(a)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/?… ---------------------------------------------- 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(a)python.org and I believe Felix's is under felixc(a)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/?… ---------------------------------------------- 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, \<a\>, \<a href & strong. 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 <br>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 <h3>, <a>, and <pre> or <code>. 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 \<br\> for single breaks and \<br\>\<br\> 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 (<br>) or paragraphs (<p>)? If it doesn't matter I'll likely go with paragraphs. What about other formatting, like Markdown headings; should they be turned into <h1>s etc? Bolded text that's currently **like this** into <strong> or <b>? 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/?… ---------------------------------------------- Carmen Kuncz, Apr 4, 10:02 AM Hi Felix, Thank you for sending this along! I will take a look at everything and start working on inputing this information to the guide within the next few days! I will reach out if I have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, Apr 3, 7:01 PM Hi Carmen, Please find attached an initial attempt at bundling up all the content into a usable export. I hope it's workable enough to get things going, but I'll follow up shortly with whatever is else is needed. The attached zip file should contain comma-separated (.csv) files with the details of all the talks, speakers, etc. The first line of each file has headings describing what each column is. Note that some rows (particularly speaker bios and talk descriptions) contain embedded newlines, but all of those entries should additionally be enclosed in double quotation marks. The files are UTF-8 encoded, and several of the speakers do have names containing non-ASCII characters like 'Ł', 'é', etc, so that's worth watching out for. There are also logo images for all the sponsors in the zip file. *Talk descriptions are currently exported as raw, unprocessed, Markdown*. I'm not sure what kind of formatting Guidebook supports, so I've left that as-is for now. If there's something more useful I can convert it to, just let me know. I do think we'll want to figure out how to process that formatting and get it reflected in the app, though. There's currently nothing in the data export that *links speakers to their talks*, which I know the app can do. If there's some data format that can be bulk-imported to your systems to get that automatically, just let me know and I'd be happy to work on it. In previous years, however, we just linked them up manually. Please don't hesitate to *let me know if there's any way I can process or rework the data* to make it easier for you/your tools to work with -- the nice thing about being a programming conference is we're generally happy to build our own tools to make things simpler! I would much rather put in the work on my end to automate whatever data processing you need to make it possible to bulk-upload changes, instead of having you or me need to go in and fix things manually one-by-one. At present, this is the* list of issues/missing data *that I'm aware of and am working on: * Keynote speakers are not included in the speaker bios. * Plenary sessions (e.g. keynotes, opening remarks) are just listed as "plenary" with no description in the schedule. * Special events (e.g. PyLadies auction, 5K run, dinners) are not included in the schedule (special_events_schedule.csv is empty). * Meals/breaks show up once per track/room, but they really should just be listed once. * "Special" pages such as venue information, code of conduct, etc. may need to be input manually - I don't mind doing it. * Speaker photos are not included (maybe that's OK -- we didn't have them last year either). * As mentioned earlier, some text is in raw Markdown; and I don't know if that's a format Guidebook can ingest. * Floor plan map is on its way, and we'll need to link talks to the room they're in. * Some general information still TBD; I will get it to you ASAP (see below). Finally, here's the *info your requested in in the Guide Basics spreadsheet*: Guide Name: PyCon 2016 Guide Start Date: 2016-05-28 Guide End Date: 2016-06-05 Timezone: Pacific Daylight Time (PDT) (UTC -7) General Information, Venue, Icon, Cover Image, Maps: I will get these to you ASAP, or just fill them in myself and let you know. Facebook: https://www.facebook.com/us.pycon.org Twitter: https://twitter.com/pycon YouTube: Not set up yet, will let you know Photos: No (I think, for now at least) RSS Feed: http://pycon.blogspot.com/feeds/posts/default?alt=rss Homepage: https://us.pycon.org/2016/ Feedback/Surveys: I believe we'll use this, but I don't think the survey has been designed yet. Will get it to you. Notifications: Sure, let's have this. My Schedule: Definitely want this feature. Notes: Sounds good. Live polling: I don't think we'll use this. All right, I think that's most of it for now? Sorry for the enormous email; I'm trying to be very thorough both to keep everyone in the loop and to remind myself of exactly what work I still need to do! Again, please don't hesitate to let me know if I can change or process the data in any way to make it easier for you, or if anything in the export looks weird -- it's all automated, so it's entirely possible something broken snuck through without human review. Cheers; all the best! -- Felix Attachment(s): pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?… ---------------------------------------------- Carmen Kuncz, Mar 30, 12:18 PM Hi Ewa, No rush on getting the content to me! I just didn't want to miss a deadline for you! Please send me the content as you get it! Reach out if you have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Mar 30, 11:08 AM Hi Carmen, Thank you for checking in! I am not yet ready to start this yet. I will begin the process on Friday of this week and I will ping you if there are any questions. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Mar 30, 11:00 AM Hi Ewa, Just checking in again to see if you have any guide content for me? I know we were initially shooting for an April 1st internal launch date! Please let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Carmen Kuncz, Mar 21, 10:06 AM Hi Ewa, Just checking in to see if you have any content for me to start building your guide? Let me know, I am excited to get started on this! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 2:01 PM Yes, that is my cell phone number. Talk to you tomorrow! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:58 PM Hi Ewa, 1 PM PST tomorrow will work great! Can I call you on the cell phone number you have listed below? If not please let me know which number is best to reach you at! Looking forward to our call! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 1:50 PM Hi Carmen, Let's chat at 1pm PT tomorrow. Have a good afternoon! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:25 PM Hi Ewa, Are you possibly available tomorrow? I am free to speak anytime between 10 AM PST to 4PM PST. Let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 12:22 PM Hi Carmen, Are you available this afternoon? I am available any time now until about 4pm CT. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 10:55 AM Hi Ewa, It's great to e-meet you! My name is Carmen, and I'll be working with you to create your guide. Lets start by scheduling a call to discuss your guide. This will help me get a good vision for your guide as well as to propose a tentative timeline for an on-time release! Please let me know your availability so we can schedule a time! I have attached a Guide Basics Spreadsheet (will appear as a link). Please take a brief look at it before our call! I'm very excited to get started! Let me know your availability and if you have any questions, feel free to reply to this thread (rather than creating a new ticket -- things can get messy rather fast). You can also call my direct extension at 650-319-7233 ext. 222. Thanks again, and I look forward to hearing back from you! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook Attachment(s): Guide_Basics.xls - https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?… ---------------------------------------------- Katie Herrgesell, Feb 17, 10:46 AM Hi Ewa, I would like to introduce you to our awesome guide building team! They are the experts that will handle the data entry for you, and will work to create an easy to use event guide. I have shared your event information with the customer success team, and someone will be contacting you within one business day to get started on your guide. Good luck! Best, Katie -- Katie Herrgesell Sr. Corporate Account Manager Office: 650.319.7233 ext 126 Mobile: 216.570.0531 www.guidebook.com -------------------------------- This email is a service from Guidebook. [N2DQPZ-696N]

2 1

[Guidebook] Update: Intro to Guide Building Team!
by Carmen Kuncz (Guidebook) May 17, 2016

May 17, 2016

##- 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/?… ---------------------------------------------- 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, \<a\>, \<a href & strong. 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 <br>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 <h3>, <a>, and <pre> or <code>. 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 \<br\> for single breaks and \<br\>\<br\> 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 (<br>) or paragraphs (<p>)? If it doesn't matter I'll likely go with paragraphs. What about other formatting, like Markdown headings; should they be turned into <h1>s etc? Bolded text that's currently **like this** into <strong> or <b>? 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/?… ---------------------------------------------- Carmen Kuncz, Apr 4, 10:02 AM Hi Felix, Thank you for sending this along! I will take a look at everything and start working on inputing this information to the guide within the next few days! I will reach out if I have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Felix Crux, Apr 3, 7:01 PM Hi Carmen, Please find attached an initial attempt at bundling up all the content into a usable export. I hope it's workable enough to get things going, but I'll follow up shortly with whatever is else is needed. The attached zip file should contain comma-separated (.csv) files with the details of all the talks, speakers, etc. The first line of each file has headings describing what each column is. Note that some rows (particularly speaker bios and talk descriptions) contain embedded newlines, but all of those entries should additionally be enclosed in double quotation marks. The files are UTF-8 encoded, and several of the speakers do have names containing non-ASCII characters like 'Ł', 'é', etc, so that's worth watching out for. There are also logo images for all the sponsors in the zip file. *Talk descriptions are currently exported as raw, unprocessed, Markdown*. I'm not sure what kind of formatting Guidebook supports, so I've left that as-is for now. If there's something more useful I can convert it to, just let me know. I do think we'll want to figure out how to process that formatting and get it reflected in the app, though. There's currently nothing in the data export that *links speakers to their talks*, which I know the app can do. If there's some data format that can be bulk-imported to your systems to get that automatically, just let me know and I'd be happy to work on it. In previous years, however, we just linked them up manually. Please don't hesitate to *let me know if there's any way I can process or rework the data* to make it easier for you/your tools to work with -- the nice thing about being a programming conference is we're generally happy to build our own tools to make things simpler! I would much rather put in the work on my end to automate whatever data processing you need to make it possible to bulk-upload changes, instead of having you or me need to go in and fix things manually one-by-one. At present, this is the* list of issues/missing data *that I'm aware of and am working on: * Keynote speakers are not included in the speaker bios. * Plenary sessions (e.g. keynotes, opening remarks) are just listed as "plenary" with no description in the schedule. * Special events (e.g. PyLadies auction, 5K run, dinners) are not included in the schedule (special_events_schedule.csv is empty). * Meals/breaks show up once per track/room, but they really should just be listed once. * "Special" pages such as venue information, code of conduct, etc. may need to be input manually - I don't mind doing it. * Speaker photos are not included (maybe that's OK -- we didn't have them last year either). * As mentioned earlier, some text is in raw Markdown; and I don't know if that's a format Guidebook can ingest. * Floor plan map is on its way, and we'll need to link talks to the room they're in. * Some general information still TBD; I will get it to you ASAP (see below). Finally, here's the *info your requested in in the Guide Basics spreadsheet*: Guide Name: PyCon 2016 Guide Start Date: 2016-05-28 Guide End Date: 2016-06-05 Timezone: Pacific Daylight Time (PDT) (UTC -7) General Information, Venue, Icon, Cover Image, Maps: I will get these to you ASAP, or just fill them in myself and let you know. Facebook: https://www.facebook.com/us.pycon.org Twitter: https://twitter.com/pycon YouTube: Not set up yet, will let you know Photos: No (I think, for now at least) RSS Feed: http://pycon.blogspot.com/feeds/posts/default?alt=rss Homepage: https://us.pycon.org/2016/ Feedback/Surveys: I believe we'll use this, but I don't think the survey has been designed yet. Will get it to you. Notifications: Sure, let's have this. My Schedule: Definitely want this feature. Notes: Sounds good. Live polling: I don't think we'll use this. All right, I think that's most of it for now? Sorry for the enormous email; I'm trying to be very thorough both to keep everyone in the loop and to remind myself of exactly what work I still need to do! Again, please don't hesitate to let me know if I can change or process the data in any way to make it easier for you, or if anything in the export looks weird -- it's all automated, so it's entirely possible something broken snuck through without human review. Cheers; all the best! -- Felix Attachment(s): pycon-2016-guidebook-data.zip - https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?… ---------------------------------------------- Carmen Kuncz, Mar 30, 12:18 PM Hi Ewa, No rush on getting the content to me! I just didn't want to miss a deadline for you! Please send me the content as you get it! Reach out if you have any questions! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Mar 30, 11:08 AM Hi Carmen, Thank you for checking in! I am not yet ready to start this yet. I will begin the process on Friday of this week and I will ping you if there are any questions. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Mar 30, 11:00 AM Hi Ewa, Just checking in again to see if you have any guide content for me? I know we were initially shooting for an April 1st internal launch date! Please let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Carmen Kuncz, Mar 21, 10:06 AM Hi Ewa, Just checking in to see if you have any content for me to start building your guide? Let me know, I am excited to get started on this! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 2:01 PM Yes, that is my cell phone number. Talk to you tomorrow! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:58 PM Hi Ewa, 1 PM PST tomorrow will work great! Can I call you on the cell phone number you have listed below? If not please let me know which number is best to reach you at! Looking forward to our call! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 1:50 PM Hi Carmen, Let's chat at 1pm PT tomorrow. Have a good afternoon! Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 1:25 PM Hi Ewa, Are you possibly available tomorrow? I am free to speak anytime between 10 AM PST to 4PM PST. Let me know! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook ---------------------------------------------- Ewa Jodlowska, Feb 17, 12:22 PM Hi Carmen, Are you available this afternoon? I am available any time now until about 4pm CT. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 ---------------------------------------------- Carmen Kuncz, Feb 17, 10:55 AM Hi Ewa, It's great to e-meet you! My name is Carmen, and I'll be working with you to create your guide. Lets start by scheduling a call to discuss your guide. This will help me get a good vision for your guide as well as to propose a tentative timeline for an on-time release! Please let me know your availability so we can schedule a time! I have attached a Guide Basics Spreadsheet (will appear as a link). Please take a brief look at it before our call! I'm very excited to get started! Let me know your availability and if you have any questions, feel free to reply to this thread (rather than creating a new ticket -- things can get messy rather fast). You can also call my direct extension at 650-319-7233 ext. 222. Thanks again, and I look forward to hearing back from you! Best, Carmen Carmen Kuncz Customer Success Associate Guidebook Attachment(s): Guide_Basics.xls - https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?… ---------------------------------------------- Katie Herrgesell, Feb 17, 10:46 AM Hi Ewa, I would like to introduce you to our awesome guide building team! They are the experts that will handle the data entry for you, and will work to create an easy to use event guide. I have shared your event information with the customer success team, and someone will be contacting you within one business day to get started on your guide. Good luck! Best, Katie -- Katie Herrgesell Sr. Corporate Account Manager Office: 650.319.7233 ext 126 Mobile: 216.570.0531 www.guidebook.com -------------------------------- This email is a service from Guidebook. [N2DQPZ-696N]

2 4

Items needed for mobile guide
by Felix Crux May 17, 2016

May 17, 2016

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

2 11

Re: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team!
by Felix Crux May 16, 2016

May 16, 2016

On Mon, May 16, 2016, at 19:19, Betsy Waliszewski wrote: > I was the one that added: (language, stdlib, etc.). I thought it was > missing. Sorry about that. No worries! I think it's fine either way; I just wanted to make sure I didn't have an inconsistency in the data I was sending. Cheers! On Mon, May 16, 2016, at 19:19, Betsy Waliszewski (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, Betsy > Waliszewski > Betsy Wali > *Betsy Waliszewski* > May 16, 4:19 PM > Hi Felix, > I was the one that added: (language, stdlib, etc.). I thought it was > missing. Sorry about that. > Betsy > Also, a question about that: in the data files I sent you, I tried to > convert the category "Python Core (language, stdlib, etc.)" to just > say "Python Core". As far as I can tell, the text "(language, stdlib, > etc.)" shouldn't show up anywhere. Yet I'm seeing it on some of the > talks in the guide. Did I miss converting the data somewhere, or did > you get different data from the conference website or something like > that? I'd prefer if we could stick to just the data in the exported > files that I sent over, since there are a number of minor tweaks like > that in it. > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 16, 3:58 PM > Hi Ewa and Felix, > > Below are the answers to all your questions. Please let me know if I > missed something! > > 1. The tutorial survey in the menu was copied over from last year (I > cloned last year's guide and some things carried over). Just say > the words and I can delete this item! It is not necessary to have! > > 2. I believe the speaker list was sent over to me in the folder of > initial data. It only included those names. Please let me know if > you would like me to remove the incomplete list or make edits! > > 3. I apologize for the abstract being listed twice, thank you for > catching that! We can have both the description and the abstract > in the description of a schedule item. I concatenated the two > columns in excel along with everything else included in the > description and must have made an error in the formula, I > apologize and will fix it! > > 4. Before I redo the schedule I need to clarify the non-ASCII text > with you! When I open the excel documents that were sent over, many > of the lines have the errors similar to the example you give me > (Weâ€™ll examine a number of popular licenses, and in what ways > they differ â€"). When I open the excel documents on my end, these > errors appear. They then appear in Builder because I use the data > from the excel document and format it in another excel document to > upload the information in Builder. Do you have data without these > errors? Or are you not seeing these errors when you open the excel > document on your end? Please let me know so we can figure out where > the disconnect and errors within the data is coming from! > > 5. Regarding the category in the description, I was following the > format of last year's guide! I will change it to how you listed it > below when I redo the schedule! > > 6. As far as Sponsor Tutorials, last year's guid has them listed as a > custom list, not in the schedule. If you would like me to add them > to the master schedule I can definitely get that done! Please just > let me know! > > 7. I am not sure if I understand what you are referring to when you > talk about Python Core? Can you give me a bit more details to > clarify? Thank you! > > I will get these edits done (which mainly are all within the master > schedule) once I receive confirmation on having the sponsor tutorials > included and more details about the ASCII text! Please let me know > your thoughts so we can move forward in a timely manner! > > Thank you! > > Carmen > Carmen Kuncz > Customer Success Associate > Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 15, 10:10 AM > Hi everyone! > I have a couple of random questions as we approach the launch! > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the > bottom of > the main left-hand menu. Is that meant to be there, given that the > tutorials > all seem to have their own survey link embedded within their own page? > Hi Felix - I have disabled the "tutorial survey" link. > > Felix Crux > *Felix Crux* > May 15, 8:06 AM > Hi Carmen, > In addition to the "Speakers" issue mentioned in my previous email, > I've found a number of serious data problems when reviewing everything > in detail today. These are major issues that would prevent launching > the guide to the public in the near future. > 1) Talks/Tutorials have the "Abstract" listed twice, instead of the > "Description" field. For example, looking at my talk: > https://builder.guidebook.com/#/guides/66563/build/schedule/sessions/137160… > we can see that the text starts out with "Free/Open Source software > is...". If you then scroll down a bit, you can see it says > "Abstract" in bold, and then the same text repeats. However, the > Description part (which starts out with "Anyone who uses Open > Source...") just isn't present anywhere. I'm guessing something in > the data import on your side was supposed to put the description > first, followed by the abstract, but instead the abstract got > included twice. Including both would be best, but if something on > your end means that only one of the two can be used, I'd prefer to > have the description, not the abstract. > 2) All non-ASCII text has serious character encoding problems. In my > initial email I used the example of someone whose name contains the > letter "Ł" (Łukasz Langa). If you find him in the guide, you'll see > that he shows up as "ukasz Langa", i.e. the first letter of his > name is completely missing > (https://builder.guidebook.com/#/guides/66563/build/custom-list-items/540277…) > . The same thing happens in a bunch of other names and talk > descriptions. Using my talk again as an example > (https://builder.guidebook.com/#/guides/66563/build/schedule/sessions/137160…) > . There's a sentence in the abstract that should read "We’ll > examine a number of popular licenses, and in what ways they differ > — and how you can use them to achieve different goals." This > sentence uses a curly-quote in "We'll", and a dash between "ways > they differ" and "and how you can use them". In the Guidebook text, > however, that's all gone. Instead, the first time the abstract > shows up, those characters are completely missing; instead it says > "Well examine a number of popular licenses, and in what ways they > differ and how you can use them to achieve different goals." Note > the "well" instead of "we'll", and how the two clauses are just run > together without a dash between them. The second time the sentence > shows up in the second abstract, those characters are completely > mangled: "Weâ€™ll examine a number of popular licenses, and in what > ways they differ â€" and how you can use them to achieve different > goals." I'm guessing something in the import process isn't reading > UTF-8 encoded text properly. > 3) Sponsor tutorials do not show up in the Master Schedule. It looks > like they're entered as just a list, not as scheduled items? > There's no track for them and attendees can't add them to their > calendars. > 4) There are also a smaller item that I'm working on fixing from my > end, but if there's something you can do on your side to make the > changes automatically with your tools that would be great: Talks > aren't in tracks according to their categories and levels. Instead > the name of the category is just in the description. For example, > in my talk, it says "Novice - Community", instead of it being part > of the "Level: Novice", and "Category: Community" tracks. I've > fixed this for all the Tutorial sessions, and will work my way > through talks doing the same thing soon. > Also, a question about that: in the data files I sent you, I tried to > convert the category "Python Core (language, stdlib, etc.)" to just > say "Python Core". As far as I can tell, the text "(language, stdlib, > etc.)" shouldn't show up anywhere. Yet I'm seeing it on some of the > talks in the guide. Did I miss converting the data somewhere, or did > you get different data from the conference website or something like > that? I'd prefer if we could stick to just the data in the exported > files that I sent over, since there are a number of minor tweaks like > that in it. > On the plus side, I'm happy to report that the "Preview in app" export > seems to be working now. I'm guessing something was just stuck > yesterday, but it's fine now. > Thanks, > On Sat, May 14, 2016, at 13:33, Felix Crux wrote: > > Hi everyone! > > > > I have a couple of random questions as we approach the launch! > > > > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the > > bottom of > > the main left-hand menu. Is that meant to be there, given that the > > tutorials > > all seem to have their own survey link embedded within their > > own page? > > > > Carmen, I'm having trouble with the "Preview in app" export > > feature. After > > making changes on the web, I'm deleting the local copy on my > > phone and > > generating a new preview export on the website. However when I > > enter the > > password and download the new version it doesn't actually have > > any of my > > changes -- it's still the old one! Any idea of what I might be doing > > wrong? > > > > Also for Carmen: I'm a bit confused by the "Speakers" list in the > > main menu. > > It doesn't seem to contain all of the speakers, but I can't > > figure out > > what the pattern is of who is included and who's not. Is it just > > something > > left over that should be deleted? Or should it be updated to include > > everyone? > > > > I also ran another data export to pull a few last minute changes. > > There were > > only a few, so I've gone ahead and made all the changes to the guide > > already. > > I'm just mentioning it here and attaching the latest data export so > > that if > > anyone needs it we can all be working off the same base. > > > > Cheers! > > > > > > > > On Wed, May 04 11:55, Carmen Kuncz (Guidebook) wrote: > > > > > Felix Crux > *Felix Crux* > May 14, 10:34 AM > Hi everyone! > I have a couple of random questions as we approach the launch! > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the > bottom of > the main left-hand menu. Is that meant to be there, given that the > tutorials > all seem to have their own survey link embedded within their own page? > Carmen, I'm having trouble with the "Preview in app" export > feature. After > making changes on the web, I'm deleting the local copy on my phone and > generating a new preview export on the website. However when I > enter the > password and download the new version it doesn't actually have > any of my > changes -- it's still the old one! Any idea of what I might be > doing wrong? > Also for Carmen: I'm a bit confused by the "Speakers" list in the > main menu. > It doesn't seem to contain all of the speakers, but I can't figure out > what the pattern is of who is included and who's not. Is it just > something > left over that should be deleted? Or should it be updated to include > everyone? > I also ran another data export to pull a few last minute changes. > There were > only a few, so I've gone ahead and made all the changes to the guide > already. > I'm just mentioning it here and attaching the latest data export > so that if > anyone needs it we can all be working off the same base. > Cheers! > Attachment(s) > pycon-2016-guidebook-data-2016-05-13.zip[1] > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 4, 4:55 PM > Hi Ewa and Felix, > > Requested edits have been made! > > Best, > > Carmen > Carmen Kuncz > Customer Success Associate > Guidebook > > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 4, 4:08 PM > Hi Ewa, > > Will do! Let me know about Heroku! > > Best, > > Carmen > Carmen Kuncz > Customer Success Associate > Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 4, 3:12 PM > Hmm ok then for the Lyft message I added the info as a custom list. > For the Heroku ad I will think about what to do :) > Thanks Carmen. > Best regards, > Ewa > Director of Operations > Python Software Foundation > Cell: 415-319-5237 > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 4, 2:59 PM > Hi Ewa, > > Unfortunately that is not possible. We do use push notifications but > they cannot include an image. > > Please let me know if you have any other questions! > > Best, > > Carmen > > Carmen Kuncz > Customer Success Associate > Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 4, 2:48 PM > Hi Carmen - > I was thinking of more of a pop up message when the app is opened. Is > that possible? For the banner ads we will have our top sponsor logos > appearing. > Best regards, > Ewa > Director of Operations > Python Software Foundation > Cell: 415-319-5237 > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 4, 1:04 PM > Hi Ewa, > > It sounds like you might be wanting banner ads? Where the ad appears > at the bottom of the app and when users click it it can bring them to > either a website or description (sounds like we will use the > description!) The banner ads appear in random order and rotate every > 5,10, 20, or 30 seconds! Up to you! > > Let me know your thoughts! > > Best, > > Carmen > Carmen Kuncz > Customer Success Associate > Guidebook > > > Ewa Jodlow > *Ewa Jodlowska* > May 4, 9:46 AM > Hi Carmen, > We need to add in two pop up messages for the Guide. Is it possible? > It would be great if we can rotate the two every time the app is > opened. If so, below is what we need: > * Lyft discount code. I am attaching the logo that can be used. The > text can be: > "COUPON CODE: PYCON > 20% off coupon which can be used on 4 rides in the geofenced area. The > total discount off each ride cannot exceed $10" > * Keystone sponsor: I am attaching their pop-up design. If this size > does not work, please let me know. > Best regards, > Ewa > Director of Operations > Python Software Foundation > Cell: 415-319-5237 > Attachment(s) > 1024x768 (2).png[2] > Logo Mighty Pink.png[3] > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 3, 5:23 PM > Hi Felix, > > Speakers have been linked and sponsor logos have been uploaded! I will > let you know when I have completed the list of edits you sent me! > > Best, > > Carmen > Carmen Kuncz > Customer Success Associate > Guidebook > > > Carmen Kun > *Carmen Kuncz* (Guidebook) > May 3, 10:19 AM > Hi Felix, > > I will make these edits throughout this week and let you know when I > have completed this as well as uploading the final bit of content! > Please reach out if you have any questions or any additional edits > that need to be made! > > Best, > > Carmen > Carmen Kuncz > Customer Success Associate > Guidebook > > > Felix Crux > *Felix Crux* > May 1, 4:27 PM > Thanks Carmen! I haven't had a chance to check it all out in depth > yet, but > what I've seen so far looks good! > I've just run another data export to make sure we've got all > the latest > content. I've attached it to this email. > The changes relative to last export (2016-04-13) are: > * Removed poster "Statistical Machine Translation with NLTK > (Reloaded)". > * Removed poster "The Art of Turtle Programming". > * Updated info for sponsor tutorial "IBM: Hands-on session: > Developing analytic applications using Apache Spark™ and Python". > * New sponsor tutorial: "Heroku 101: Deploying Python Web > Applications". > * Updated speaker name for talk "Diff It To Dig It". > * Updated description for talk "Prototyping New APIs with Flask". > * Updated description for tutorial " Efficient Python for High- > Performance > Parallel Computing". > * Removed speaker Al Sweigart. > * Removed speaker Liling Tan. > * Updated bio for speaker Anton Malakhov. > * Updated bio for speaker Russia Madden. > * New sponsor tutorial speaker bio for David Taieb. > * Changed name for speaker Sep Ehr (to Seperman). > * New Coffee Sponsor "Indeed Prime". > * Changed Gold sponsor "Venmo" to "Venmo / Braintree". > * New Job Fair Sponsor "Amazon Web Services". > * New Job Fair Sponsor "Virtustream". > * Updated description for Keystone Sponsor "Heroku". > * New Platinum sponsor "New Relic". > * Updated description for Silver Sponsor "CrossCompute". > Phew! That list is longer than I expected; but most of the > changes in it > are pretty small. > Thanks again for getting all the content in so we can preview it. > I'll try > to confirm this week (or at the latest next weekend) that those > empty files > are meant to be that way and let you know. > All the best, > Felix > Attachment(s) > pycon-2016-guidebook-data-2016-05-01.zip[4] > > Carmen Kun > *Carmen Kuncz* (Guidebook) > 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(a)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 Jodlow > *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 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 > > > 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[5] > > 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 > > > 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 :) > > 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 > > 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, > > 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(a)python.org and I believe Felix's is under felixc(a)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[6] > > 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, <a>, <a href & strong. > > 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 <br>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 > <h3>, <a>, > and <pre> or <code>. > 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 <br> for single breaks and > <br><br> 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 (<br>) or paragraphs (<p>)? If it doesn't matter I'll likely go > with paragraphs. > What about other formatting, like Markdown headings; should they be > turned into <h1>s etc? Bolded text that's currently **like this** into > <strong> or <b>? 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[7] > > 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[8] > > 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[9] > > 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[10]. > [N2DQPZ-696N] > Links: 1. https://support.guidebook.com/attachments/token/ZmLdVdosXdeYS6jlnGXqY6utb/?… 2. https://support.guidebook.com/attachments/token/9kX7GaszJwlxeJDeyfxLfopH1/?… 3. https://support.guidebook.com/attachments/token/mmPgsrklV1piXtoJ1RuPGxQPX/?… 4. https://support.guidebook.com/attachments/token/e59emWjkthWCFjOIqG5hqtUfD/?… 5. https://support.guidebook.com/attachments/token/iaSl7nrPA5v9029GQ3iivK5RZ/?… 6. https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?… 7. https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?… 8. https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?… 9. https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?… 10. http://www.zendesk.com

1 0

Re: [Pycon-mobile-guide] [Guidebook] Update: Intro to Guide Building Team!
by Betsy Waliszewski May 16, 2016

May 16, 2016

Hi Felix, I was the one that added: (language, stdlib, etc.). I thought it was missing. Sorry about that. Betsy Also, a question about that: in the data files I sent you, I tried to convert the category "Python Core (language, stdlib, etc.)" to just say "Python Core". As far as I can tell, the text "(language, stdlib, etc.)" shouldn't show up anywhere. Yet I'm seeing it on some of the talks in the guide. Did I miss converting the data somewhere, or did you get different data from the conference website or something like that? I'd prefer if we could stick to just the data in the exported files that I sent over, since there are a number of minor tweaks like that in it. On Mon, May 16, 2016 at 3:58 PM, Carmen Kuncz (Guidebook) < builders(a)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) > > May 16, 3:58 PM > Hi Ewa and Felix, > > Below are the answers to all your questions. Please let me know if I > missed something! > > 1. The tutorial survey in the menu was copied over from last year (I > cloned last year's guide and some things carried over). Just say the words > and I can delete this item! It is not necessary to have! > > 2. I believe the speaker list was sent over to me in the folder of initial > data. It only included those names. Please let me know if you would like me > to remove the incomplete list or make edits! > > 3. I apologize for the abstract being listed twice, thank you for catching > that! We can have both the description and the abstract in the description > of a schedule item. I concatenated the two columns in excel along with > everything else included in the description and must have made an error in > the formula, I apologize and will fix it! > > 4. Before I redo the schedule I need to clarify the non-ASCII text with > you! When I open the excel documents that were sent over, many of the lines > have the errors similar to the example you give me (Weâ€™ll examine a > number of popular licenses, and in what ways they differ â€"). When I open > the excel documents on my end, these errors appear. They then appear in > Builder because I use the data from the excel document and format it in > another excel document to upload the information in Builder. Do you have > data without these errors? Or are you not seeing these errors when you open > the excel document on your end? Please let me know so we can figure out > where the disconnect and errors within the data is coming from! > > 5. Regarding the category in the description, I was following the format > of last year's guide! I will change it to how you listed it below when I > redo the schedule! > > 6. As far as Sponsor Tutorials, last year's guid has them listed as a > custom list, not in the schedule. If you would like me to add them to the > master schedule I can definitely get that done! Please just let me know! > > 7. I am not sure if I understand what you are referring to when you talk > about Python Core? Can you give me a bit more details to clarify? Thank you! > > I will get these edits done (which mainly are all within the master > schedule) once I receive confirmation on having the sponsor tutorials > included and more details about the ASCII text! Please let me know your > thoughts so we can move forward in a timely manner! > > Thank you! > > Carmen > > Carmen Kuncz > Customer Success Associate > Guidebook > > [image: Ewa Jodlow] > > *Ewa Jodlowska* > > May 15, 10:10 AM > > Hi everyone! > > I have a couple of random questions as we approach the launch! > > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the bottom > of > the main left-hand menu. Is that meant to be there, given that the > tutorials > all seem to have their own survey link embedded within their own page? > > Hi Felix - I have disabled the "tutorial survey" link. > > [image: Felix Crux] > > *Felix Crux* > > May 15, 8:06 AM > > Hi Carmen, > > In addition to the "Speakers" issue mentioned in my previous email, I've > found a number of serious data problems when reviewing everything in detail > today. These are major issues that would prevent launching the guide to the > public in the near future. > > 1) Talks/Tutorials have the "Abstract" listed twice, instead of the > "Description" field. For example, looking at my talk: > https://builder.guidebook.com/#/guides/66563/build/schedule/sessions/137160… > we can see that the text starts out with "Free/Open Source software is...". > If you then scroll down a bit, you can see it says "Abstract" in bold, and > then the same text repeats. However, the Description part (which starts out > with "Anyone who uses Open Source...") just isn't present anywhere. I'm > guessing something in the data import on your side was supposed to put the > description first, followed by the abstract, but instead the abstract got > included twice. Including both would be best, but if something on your end > means that only one of the two can be used, I'd prefer to have the > description, not the abstract. > > 2) All non-ASCII text has serious character encoding problems. In my > initial email I used the example of someone whose name contains the letter > "Ł" (Łukasz Langa). If you find him in the guide, you'll see that he shows > up as "ukasz Langa", i.e. the first letter of his name is completely > missing ( > https://builder.guidebook.com/#/guides/66563/build/custom-list-items/540277…). > The same thing happens in a bunch of other names and talk descriptions. > Using my talk again as an example ( > https://builder.guidebook.com/#/guides/66563/build/schedule/sessions/137160…). > There's a sentence in the abstract that should read "We’ll examine a number > of popular licenses, and in what ways they differ — and how you can use > them to achieve different goals." This sentence uses a curly-quote in > "We'll", and a dash between "ways they differ" and "and how you can use > them". In the Guidebook text, however, that's all gone. Instead, the first > time the abstract shows up, those characters are completely missing; > instead it says "Well examine a number of popular licenses, and in what > ways they differ and how you can use them to achieve different goals." Note > the "well" instead of "we'll", and how the two clauses are just run > together without a dash between them. The second time the sentence shows up > in the second abstract, those characters are completely mangled: "Weâ€™ll > examine a number of popular licenses, and in what ways they differ â€" and > how you can use them to achieve different goals." I'm guessing something in > the import process isn't reading UTF-8 encoded text properly. > > 3) Sponsor tutorials do not show up in the Master Schedule. It looks like > they're entered as just a list, not as scheduled items? There's no track > for them and attendees can't add them to their calendars. > > 4) There are also a smaller item that I'm working on fixing from my end, > but if there's something you can do on your side to make the changes > automatically with your tools that would be great: Talks aren't in tracks > according to their categories and levels. Instead the name of the category > is just in the description. For example, in my talk, it says "Novice - > Community", instead of it being part of the "Level: Novice", and "Category: > Community" tracks. I've fixed this for all the Tutorial sessions, and will > work my way through talks doing the same thing soon. > > Also, a question about that: in the data files I sent you, I tried to > convert the category "Python Core (language, stdlib, etc.)" to just say > "Python Core". As far as I can tell, the text "(language, stdlib, etc.)" > shouldn't show up anywhere. Yet I'm seeing it on some of the talks in the > guide. Did I miss converting the data somewhere, or did you get different > data from the conference website or something like that? I'd prefer if we > could stick to just the data in the exported files that I sent over, since > there are a number of minor tweaks like that in it. > > On the plus side, I'm happy to report that the "Preview in app" export > seems to be working now. I'm guessing something was just stuck yesterday, > but it's fine now. > > Thanks, > > On Sat, May 14, 2016, at 13:33, Felix Crux wrote: > > Hi everyone! > > > > I have a couple of random questions as we approach the launch! > > > > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the > bottom of > > the main left-hand menu. Is that meant to be there, given that the > tutorials > > all seem to have their own survey link embedded within their own page? > > > > Carmen, I'm having trouble with the "Preview in app" export feature. > After > > making changes on the web, I'm deleting the local copy on my phone and > > generating a new preview export on the website. However when I enter the > > password and download the new version it doesn't actually have any of my > > changes -- it's still the old one! Any idea of what I might be doing > wrong? > > > > Also for Carmen: I'm a bit confused by the "Speakers" list in the main > menu. > > It doesn't seem to contain all of the speakers, but I can't figure out > > what the pattern is of who is included and who's not. Is it just > something > > left over that should be deleted? Or should it be updated to include > everyone? > > > > I also ran another data export to pull a few last minute changes. There > were > > only a few, so I've gone ahead and made all the changes to the guide > already. > > I'm just mentioning it here and attaching the latest data export so that > if > > anyone needs it we can all be working off the same base. > > > > Cheers! > > > > > > > > On Wed, May 04 11:55, Carmen Kuncz (Guidebook) wrote: > > > > > [image: Felix Crux] > > *Felix Crux* > > May 14, 10:34 AM > > Hi everyone! > > I have a couple of random questions as we approach the launch! > > Ewa and/or Betsy, I noticed there's a "Tutorial Survey" link at the bottom > of > the main left-hand menu. Is that meant to be there, given that the > tutorials > all seem to have their own survey link embedded within their own page? > > Carmen, I'm having trouble with the "Preview in app" export feature. After > making changes on the web, I'm deleting the local copy on my phone and > generating a new preview export on the website. However when I enter the > password and download the new version it doesn't actually have any of my > changes -- it's still the old one! Any idea of what I might be doing wrong? > > Also for Carmen: I'm a bit confused by the "Speakers" list in the main > menu. > It doesn't seem to contain all of the speakers, but I can't figure out > what the pattern is of who is included and who's not. Is it just something > left over that should be deleted? Or should it be updated to include > everyone? > > I also ran another data export to pull a few last minute changes. There > were > only a few, so I've gone ahead and made all the changes to the guide > already. > I'm just mentioning it here and attaching the latest data export so that if > anyone needs it we can all be working off the same base. > > Cheers! > > Attachment(s) > pycon-2016-guidebook-data-2016-05-13.zip > <https://support.guidebook.com/attachments/token/ZmLdVdosXdeYS6jlnGXqY6utb/?…> > > [image: Carmen Kun] > > *Carmen Kuncz* (Guidebook) > > May 4, 4:55 PM > Hi Ewa and Felix, > > Requested edits have been made! > > Best, > > Carmen > > Carmen Kuncz > Customer Success Associate > Guidebook > > [image: Carmen Kun] > > *Carmen Kuncz* (Guidebook) > > May 4, 4:08 PM > Hi Ewa, > > Will do! Let me know about Heroku! > > Best, > > Carmen > > Carmen Kuncz > Customer Success Associate > Guidebook > > [image: Ewa Jodlow] > > *Ewa Jodlowska* > > May 4, 3:12 PM > > Hmm ok then for the Lyft message I added the info as a custom list. For > the Heroku ad I will think about what to do :) > > Thanks Carmen. > > Best regards, > > Ewa > Director of Operations > Python Software Foundation > Cell: 415-319-5237 > > [image: Carmen Kun] > > *Carmen Kuncz* (Guidebook) > > May 4, 2:59 PM > Hi Ewa, > > Unfortunately that is not possible. We do use push notifications but they > cannot include an image. > > Please let me know if you have any other questions! > > Best, > > Carmen > > > Carmen Kuncz > Customer Success Associate > Guidebook > > [image: Ewa Jodlow] > > *Ewa Jodlowska* > > May 4, 2:48 PM > > Hi Carmen - > > I was thinking of more of a pop up message when the app is opened. Is that > possible? For the banner ads we will have our top sponsor logos appearing. > > Best regards, > > Ewa > Director of Operations > Python Software Foundation > Cell: 415-319-5237 > > [image: Carmen Kun] > > *Carmen Kuncz* (Guidebook) > > May 4, 1:04 PM > Hi Ewa, > > It sounds like you might be wanting banner ads? Where the ad appears at > the bottom of the app and when users click it it can bring them to either a > website or description (sounds like we will use the description!) The > banner ads appear in random order and rotate every 5,10, 20, or 30 seconds! > Up to you! > > Let me know your thoughts! > > Best, > > Carmen > > Carmen Kuncz > Customer Success Associate > Guidebook > > [image: Ewa Jodlow] > > *Ewa Jodlowska* > > May 4, 9:46 AM > > Hi Carmen, > > We need to add in two pop up messages for the Guide. Is it possible? It > would be great if we can rotate the two every time the app is opened. If > so, below is what we need: > > * Lyft discount code. I am attaching the logo that can be used. The text > can be: > > "COUPON CODE: PYCON > 20% off coupon which can be used on 4 rides in the geofenced area. The > total discount off each ride cannot exceed $10" > > * Keystone sponsor: I am attaching their pop-up design. If this size does > not work, please let me know. > > Best regards, > > Ewa > Director of Operations > Python Software Foundation > Cell: 415-319-5237 > > Attachment(s) > 1024x768 (2).png > <https://support.guidebook.com/attachments/token/9kX7GaszJwlxeJDeyfxLfopH1/?…> > Logo Mighty Pink.png > <https://support.guidebook.com/attachments/token/mmPgsrklV1piXtoJ1RuPGxQPX/?…> > > [image: Carmen Kun] > > *Carmen Kuncz* (Guidebook) > > May 3, 5:23 PM > Hi Felix, > > Speakers have been linked and sponsor logos have been uploaded! I will let > you know when I have completed the list of edits you sent me! > > Best, > > Carmen > > Carmen Kuncz > Customer Success Associate > Guidebook > > [image: Carmen Kun] > > *Carmen Kuncz* (Guidebook) > > May 3, 10:19 AM > Hi Felix, > > I will make these edits throughout this week and let you know when I have > completed this as well as uploading the final bit of content! Please reach > out if you have any questions or any additional edits that need to be made! > > Best, > > Carmen > > Carmen Kuncz > Customer Success Associate > Guidebook > > [image: Felix Crux] > > *Felix Crux* > > May 1, 4:27 PM > > Thanks Carmen! I haven't had a chance to check it all out in depth yet, but > what I've seen so far looks good! > > I've just run another data export to make sure we've got all the latest > content. I've attached it to this email. > > The changes relative to last export (2016-04-13) are: > * Removed poster "Statistical Machine Translation with NLTK (Reloaded)". > * Removed poster "The Art of Turtle Programming". > * Updated info for sponsor tutorial "IBM: Hands-on session: > Developing analytic applications using Apache Spark™ and Python". > * New sponsor tutorial: "Heroku 101: Deploying Python Web Applications". > * Updated speaker name for talk "Diff It To Dig It". > * Updated description for talk "Prototyping New APIs with Flask". > * Updated description for tutorial " Efficient Python for High-Performance > Parallel Computing". > * Removed speaker Al Sweigart. > * Removed speaker Liling Tan. > * Updated bio for speaker Anton Malakhov. > * Updated bio for speaker Russia Madden. > * New sponsor tutorial speaker bio for David Taieb. > * Changed name for speaker Sep Ehr (to Seperman). > * New Coffee Sponsor "Indeed Prime". > * Changed Gold sponsor "Venmo" to "Venmo / Braintree". > * New Job Fair Sponsor "Amazon Web Services". > * New Job Fair Sponsor "Virtustream". > * Updated description for Keystone Sponsor "Heroku". > * New Platinum sponsor "New Relic". > * Updated description for Silver Sponsor "CrossCompute". > > Phew! That list is longer than I expected; but most of the changes in it > are pretty small. > > Thanks again for getting all the content in so we can preview it. I'll try > to confirm this week (or at the latest next weekend) that those empty files > are meant to be that way and let you know. > > All the best, > > Felix > > Attachment(s) > pycon-2016-guidebook-data-2016-05-01.zip > <https://support.guidebook.com/attachments/token/e59emWjkthWCFjOIqG5hqtUfD/?…> > > [image: Carmen Kun] > > *Carmen Kuncz* (Guidebook) > > 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(a)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 > > [image: Ewa Jodlow] > > *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 > > [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 > <https://support.guidebook.com/attachments/token/iaSl7nrPA5v9029GQ3iivK5RZ/?…> > > [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(a)python.org and I believe Felix's is under felixc(a)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 > <https://support.guidebook.com/attachments/token/vTYger3KM5atGgaGyejyfxn1z/?…> > > [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, <a>, <a href & strong. > > 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 <br>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 <h3>, <a>, > and <pre> or <code>. > > 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 <br> for single breaks and > <br><br> 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 (<br>) or paragraphs (<p>)? If it doesn't matter I'll likely go with > paragraphs. > > What about other formatting, like Markdown headings; should they be turned > into <h1>s etc? Bolded text that's currently **like this** into <strong> or > <b>? 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 > <https://support.guidebook.com/attachments/token/2uWGc5671n04hU0vFfPoILTm3/?…> > > [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 > <https://support.guidebook.com/attachments/token/zBF5xbh7MnXVep59QaASzZqyp/?…> > > [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 > <https://support.guidebook.com/attachments/token/Cpp6495RhyUf0XiLYDcLQL8hh/?…> > > [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 > <http://www.zendesk.com>. > [N2DQPZ-696N] > > _______________________________________________ > Pycon-mobile-guide mailing list > Pycon-mobile-guide(a)python.org > https://mail.python.org/mailman/listinfo/pycon-mobile-guide > > -- Betsy Waliszewski Python Software Foundation Event Coordinator / Administrator @betswaliszewski

1 0