From muthukannan.subramanian at mavs.uta.edu Wed May 9 02:50:43 2018 From: muthukannan.subramanian at mavs.uta.edu (Subramanian, Muthu Kannan) Date: Wed, 9 May 2018 06:50:43 +0000 Subject: [Pycon-sprints] Dress Code for Sprints Message-ID: Hi I just graduated from UT Arlington and this is my first time into PyCon. Can you let me know the appropriate dress code for sprints ? I am travelling from Arlington, Texas and I am excited to attend PyCon. Thanks, Muthu -------------- next part -------------- An HTML attachment was scrubbed... URL: From betsy at python.org Wed May 9 07:25:09 2018 From: betsy at python.org (Betsy Waliszewski) Date: Wed, 9 May 2018 07:25:09 -0400 Subject: [Pycon-sprints] [pycon-reg] Dress Code for Sprints In-Reply-To: References: Message-ID: Hi, There is no dress code for development sprints :-). Best, Betsy On Wed, May 9, 2018 at 2:50 AM, Subramanian, Muthu Kannan < muthukannan.subramanian at mavs.uta.edu> wrote: > Hi > > I just graduated from UT Arlington and this is my first time into PyCon. > > Can you let me know the appropriate dress code for sprints ? > > > > I am travelling from Arlington, Texas and I am excited to attend PyCon. > > > > Thanks, > > Muthu > > > > _______________________________________________ > pycon-reg mailing list > pycon-reg at python.org > https://mail.python.org/mailman/listinfo/pycon-reg > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From muthukannan.subramanian at mavs.uta.edu Wed May 9 15:26:17 2018 From: muthukannan.subramanian at mavs.uta.edu (Subramanian, Muthu Kannan) Date: Wed, 9 May 2018 19:26:17 +0000 Subject: [Pycon-sprints] [pycon-reg] Dress Code for Sprints In-Reply-To: References:

Message-ID: Thank you. From: Betsy Waliszewski Sent: Wednesday, May 9, 2018 6:25 AM To: Subramanian, Muthu Kannan Cc: pycon-sprints at python.org; pycon-reg at python.org Subject: Re: [pycon-reg] Dress Code for Sprints Hi, There is no dress code for development sprints :-). Best, Betsy On Wed, May 9, 2018 at 2:50 AM, Subramanian, Muthu Kannan > wrote: Hi I just graduated from UT Arlington and this is my first time into PyCon. Can you let me know the appropriate dress code for sprints ? I am travelling from Arlington, Texas and I am excited to attend PyCon. Thanks, Muthu _______________________________________________ pycon-reg mailing list pycon-reg at python.org https://mail.python.org/mailman/listinfo/pycon-reg -------------- next part -------------- An HTML attachment was scrubbed... URL: From chalmer.lowe at gmail.com Mon May 14 15:38:37 2018 From: chalmer.lowe at gmail.com (Chalmer Lowe) Date: Mon, 14 May 2018 15:38:37 -0400 Subject: [Pycon-sprints] Asheesh's quick notes from yesterday's sprint workshop In-Reply-To: References: Message-ID: Asheesh: thanks for gathering this feedback. excellent stuff. more to do to help improve the content, but definitely rewarding to see the good feedback from the attendees. chalmer Chalmer Lowe, MS President, Dark Art of Coding http://darkartofcoding.com/ Chairman, Python Education Summit https://us.pycon.org/2015/events/edusummit/ On Mon, May 14, 2018 at 1:05 PM, Asheesh Laroia wrote: > > > *Happy feedback* > "Really good git instructions." > > "The walk thru on Git was awesome. Also like the 'big picture' section on > pages to delve deeper after exercises. Thanks a lot!" > > "Everything was amazing." > > "The helpers were amazing." > > "I finally understand forking" > > Read more: https://docs.google.com/spreadsheets/d/1XP2O7nbfja_ > bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit?ouid=112785794878603790169&usp= > sheets_home&ths=true > > > *Asheesh's notes* > > - It was effective! > > - Thanks hugely to Chalmer and Jeff for all their work on the content. > Students appreciated the content -- everything from the call-outs for > further reading to the thoughtful diagrams and lecture. > > - ~30% of people left within ~1 hour, but I think that was fine. They > asked us if there was more content after the self-paced stuff; there is > sort-of (there's an emotional appeal at the end for people to take good > care of themselves during sprints) and there isn't sort-of, so we said, > sure, go ahead and leave, enjoy! I think this was the right choice. > > - We ended at 7:35, aka 2h5m duration. That's good; we told people it'd be > 2 hours in duration. > > - We got ~45 pieces of feedback, which is ~25-50% response rate, which is > effing huge. Full feedback here: https://docs.google.com/ > spreadsheets/d/1XP2O7nbfja_bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit#gid=0 > Sticky notes at the end are good for gathering feedback! > > - We had ~80 people, of which iirc ~10% seemed to be women. > > - GitHub blacklisted our IP address for /login temporarily; some people > thought this would be a big problem, but I think it would fix itself within > ~30 seconds every time it happened, so it only affected a small number of > people for a short amount of time. > > - People really liked the tutorial. > > - Scheduling the time block is an issue still. We had a conflict with the > conference dinner. Oh well! > > - Many people came who want to take this material to other conferences: > Someone talked to Chalmer about a Russian translation; Nicholle James > (CC'd) wants to bring something like it to DjangoCon US; Meghan last year > talked about running something similar at PyCascades (CC'd); some people > talked about bringing it to ChiPy, the Chicago Python user group. > > - People are hungry for more written material on the PyCon site before > sprints -- for example, a link to the tutorial, since it's self-driven. > > - We started with ~18 teaching assistants for ~80 students. I told them > that most could dissipate within 30 min if there wasn't much load on TAs. > There wasn't much load on TAs, so they did. That was fine. In the future, > since we now can be quite confident we can find teaching assistants, we can > consider changing the format so that it's one TA to ~5-6 students, and then > they make a personal connection to a TA. This would require a very > different room layout! I personally have had great experiences with a > format like this; I've also personally set up an activity oriented around > small groups, which we can consider using in the future perhaps: > http://wiki.openhatch.org/Open_Source_Comes_to_Campus/Curriculum/Git (but > we can also run the existing Chalmer tutorial in small groups just fine, so > long as we have a separate repo for each small group; that way we limit > merge conflicts to 5-6 people). > > For other thoughts, read the feedback. > > Asheesh. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chalmer.lowe at gmail.com Mon May 14 16:08:31 2018 From: chalmer.lowe at gmail.com (Chalmer Lowe) Date: Mon, 14 May 2018 16:08:31 -0400 Subject: [Pycon-sprints] Asheesh's quick notes from yesterday's sprint workshop In-Reply-To: References:

Message-ID: Good call, Jeff. For the moment, I added this to the bottom of Asheesh's feedback sheet so that all feedback is in one place. We should incorporate it into the repo as Issues or something so that all upgrades can get tracked. Chalmer Lowe, MS President, Dark Art of Coding http://darkartofcoding.com/ Chairman, Python Education Summit https://us.pycon.org/2015/events/edusummit/ On Mon, May 14, 2018 at 3:55 PM, Jeffrey Eliasen wrote: > Thanks so much for your involvement and help! We should incorporate the TA > resources into a "Preprarations for the TAs" page. > > ---------- > > jeffrey k eliasen - technologist, philosopher, agent of change > blog | linkedin > | google+ > | facebook > | twitter > > > On May 14, 2018, at 13:08, Asheesh Laroia wrote: > > Also here's the doc I made to gather thoughts about TAs, which may be > useful as a reference next year. > > https://docs.google.com/document/d/1cU5dM588ZbkovcXM7GxE5INjXAOkC > o90H93v_1ipDdg/edit > > On Mon, May 14, 2018 at 1:05 PM Asheesh Laroia > wrote: > >> >> >> *Happy feedback* >> "Really good git instructions." >> >> "The walk thru on Git was awesome. Also like the 'big picture' section on >> pages to delve deeper after exercises. Thanks a lot!" >> >> "Everything was amazing." >> >> "The helpers were amazing." >> >> "I finally understand forking" >> >> Read more: https://docs.google.com/spreadsheets/d/1XP2O7nbfja_ >> bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit?ouid=112785794878603790169&usp= >> sheets_home&ths=true >> >> >> *Asheesh's notes* >> >> - It was effective! >> >> - Thanks hugely to Chalmer and Jeff for all their work on the content. >> Students appreciated the content -- everything from the call-outs for >> further reading to the thoughtful diagrams and lecture. >> >> - ~30% of people left within ~1 hour, but I think that was fine. They >> asked us if there was more content after the self-paced stuff; there is >> sort-of (there's an emotional appeal at the end for people to take good >> care of themselves during sprints) and there isn't sort-of, so we said, >> sure, go ahead and leave, enjoy! I think this was the right choice. >> >> - We ended at 7:35, aka 2h5m duration. That's good; we told people it'd >> be 2 hours in duration. >> >> - We got ~45 pieces of feedback, which is ~25-50% response rate, which is >> effing huge. Full feedback here: https://docs.google.com/ >> spreadsheets/d/1XP2O7nbfja_bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit#gid=0 >> Sticky notes at the end are good for gathering feedback! >> >> - We had ~80 people, of which iirc ~10% seemed to be women. >> >> - GitHub blacklisted our IP address for /login temporarily; some people >> thought this would be a big problem, but I think it would fix itself within >> ~30 seconds every time it happened, so it only affected a small number of >> people for a short amount of time. >> >> - People really liked the tutorial. >> >> - Scheduling the time block is an issue still. We had a conflict with the >> conference dinner. Oh well! >> >> - Many people came who want to take this material to other conferences: >> Someone talked to Chalmer about a Russian translation; Nicholle James >> (CC'd) wants to bring something like it to DjangoCon US; Meghan last year >> talked about running something similar at PyCascades (CC'd); some people >> talked about bringing it to ChiPy, the Chicago Python user group. >> >> - People are hungry for more written material on the PyCon site before >> sprints -- for example, a link to the tutorial, since it's self-driven. >> >> - We started with ~18 teaching assistants for ~80 students. I told them >> that most could dissipate within 30 min if there wasn't much load on TAs. >> There wasn't much load on TAs, so they did. That was fine. In the future, >> since we now can be quite confident we can find teaching assistants, we can >> consider changing the format so that it's one TA to ~5-6 students, and then >> they make a personal connection to a TA. This would require a very >> different room layout! I personally have had great experiences with a >> format like this; I've also personally set up an activity oriented around >> small groups, which we can consider using in the future perhaps: >> http://wiki.openhatch.org/Open_Source_Comes_to_Campus/Curriculum/Git >> (but we can also run the existing Chalmer tutorial in small groups just >> fine, so long as we have a separate repo for each small group; that way we >> limit merge conflicts to 5-6 people). >> >> For other thoughts, read the feedback. >> >> Asheesh. >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From asheesh at asheesh.org Mon May 14 13:05:10 2018 From: asheesh at asheesh.org (Asheesh Laroia) Date: Mon, 14 May 2018 13:05:10 -0400 Subject: [Pycon-sprints] Asheesh's quick notes from yesterday's sprint workshop Message-ID: *Happy feedback* "Really good git instructions." "The walk thru on Git was awesome. Also like the 'big picture' section on pages to delve deeper after exercises. Thanks a lot!" "Everything was amazing." "The helpers were amazing." "I finally understand forking" Read more: https://docs.google.com/spreadsheets/d/1XP2O7nbfja_bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit?ouid=112785794878603790169&usp=sheets_home&ths=true *Asheesh's notes* - It was effective! - Thanks hugely to Chalmer and Jeff for all their work on the content. Students appreciated the content -- everything from the call-outs for further reading to the thoughtful diagrams and lecture. - ~30% of people left within ~1 hour, but I think that was fine. They asked us if there was more content after the self-paced stuff; there is sort-of (there's an emotional appeal at the end for people to take good care of themselves during sprints) and there isn't sort-of, so we said, sure, go ahead and leave, enjoy! I think this was the right choice. - We ended at 7:35, aka 2h5m duration. That's good; we told people it'd be 2 hours in duration. - We got ~45 pieces of feedback, which is ~25-50% response rate, which is effing huge. Full feedback here: https://docs.google.com/spreadsheets/d/1XP2O7nbfja_bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit#gid=0 Sticky notes at the end are good for gathering feedback! - We had ~80 people, of which iirc ~10% seemed to be women. - GitHub blacklisted our IP address for /login temporarily; some people thought this would be a big problem, but I think it would fix itself within ~30 seconds every time it happened, so it only affected a small number of people for a short amount of time. - People really liked the tutorial. - Scheduling the time block is an issue still. We had a conflict with the conference dinner. Oh well! - Many people came who want to take this material to other conferences: Someone talked to Chalmer about a Russian translation; Nicholle James (CC'd) wants to bring something like it to DjangoCon US; Meghan last year talked about running something similar at PyCascades (CC'd); some people talked about bringing it to ChiPy, the Chicago Python user group. - People are hungry for more written material on the PyCon site before sprints -- for example, a link to the tutorial, since it's self-driven. - We started with ~18 teaching assistants for ~80 students. I told them that most could dissipate within 30 min if there wasn't much load on TAs. There wasn't much load on TAs, so they did. That was fine. In the future, since we now can be quite confident we can find teaching assistants, we can consider changing the format so that it's one TA to ~5-6 students, and then they make a personal connection to a TA. This would require a very different room layout! I personally have had great experiences with a format like this; I've also personally set up an activity oriented around small groups, which we can consider using in the future perhaps: http://wiki.openhatch.org/Open_Source_Comes_to_Campus/Curriculum/Git (but we can also run the existing Chalmer tutorial in small groups just fine, so long as we have a separate repo for each small group; that way we limit merge conflicts to 5-6 people). For other thoughts, read the feedback. Asheesh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From asheesh at asheesh.org Mon May 14 13:08:04 2018 From: asheesh at asheesh.org (Asheesh Laroia) Date: Mon, 14 May 2018 13:08:04 -0400 Subject: [Pycon-sprints] Asheesh's quick notes from yesterday's sprint workshop In-Reply-To: References: Message-ID: Also here's the doc I made to gather thoughts about TAs, which may be useful as a reference next year. https://docs.google.com/document/d/1cU5dM588ZbkovcXM7GxE5INjXAOkCo90H93v_1ipDdg/edit On Mon, May 14, 2018 at 1:05 PM Asheesh Laroia wrote: > > > *Happy feedback* > "Really good git instructions." > > "The walk thru on Git was awesome. Also like the 'big picture' section on > pages to delve deeper after exercises. Thanks a lot!" > > "Everything was amazing." > > "The helpers were amazing." > > "I finally understand forking" > > Read more: > https://docs.google.com/spreadsheets/d/1XP2O7nbfja_bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit?ouid=112785794878603790169&usp=sheets_home&ths=true > > > *Asheesh's notes* > > - It was effective! > > - Thanks hugely to Chalmer and Jeff for all their work on the content. > Students appreciated the content -- everything from the call-outs for > further reading to the thoughtful diagrams and lecture. > > - ~30% of people left within ~1 hour, but I think that was fine. They > asked us if there was more content after the self-paced stuff; there is > sort-of (there's an emotional appeal at the end for people to take good > care of themselves during sprints) and there isn't sort-of, so we said, > sure, go ahead and leave, enjoy! I think this was the right choice. > > - We ended at 7:35, aka 2h5m duration. That's good; we told people it'd be > 2 hours in duration. > > - We got ~45 pieces of feedback, which is ~25-50% response rate, which is > effing huge. Full feedback here: > https://docs.google.com/spreadsheets/d/1XP2O7nbfja_bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit#gid=0 > Sticky notes at the end are good for gathering feedback! > > - We had ~80 people, of which iirc ~10% seemed to be women. > > - GitHub blacklisted our IP address for /login temporarily; some people > thought this would be a big problem, but I think it would fix itself within > ~30 seconds every time it happened, so it only affected a small number of > people for a short amount of time. > > - People really liked the tutorial. > > - Scheduling the time block is an issue still. We had a conflict with the > conference dinner. Oh well! > > - Many people came who want to take this material to other conferences: > Someone talked to Chalmer about a Russian translation; Nicholle James > (CC'd) wants to bring something like it to DjangoCon US; Meghan last year > talked about running something similar at PyCascades (CC'd); some people > talked about bringing it to ChiPy, the Chicago Python user group. > > - People are hungry for more written material on the PyCon site before > sprints -- for example, a link to the tutorial, since it's self-driven. > > - We started with ~18 teaching assistants for ~80 students. I told them > that most could dissipate within 30 min if there wasn't much load on TAs. > There wasn't much load on TAs, so they did. That was fine. In the future, > since we now can be quite confident we can find teaching assistants, we can > consider changing the format so that it's one TA to ~5-6 students, and then > they make a personal connection to a TA. This would require a very > different room layout! I personally have had great experiences with a > format like this; I've also personally set up an activity oriented around > small groups, which we can consider using in the future perhaps: > http://wiki.openhatch.org/Open_Source_Comes_to_Campus/Curriculum/Git (but > we can also run the existing Chalmer tutorial in small groups just fine, so > long as we have a separate repo for each small group; that way we limit > merge conflicts to 5-6 people). > > For other thoughts, read the feedback. > > Asheesh. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeff at jke.net Mon May 14 15:55:03 2018 From: jeff at jke.net (Jeffrey Eliasen) Date: Mon, 14 May 2018 15:55:03 -0400 Subject: [Pycon-sprints] Asheesh's quick notes from yesterday's sprint workshop In-Reply-To: References: Message-ID: Thanks so much for your involvement and help! We should incorporate the TA resources into a "Preprarations for the TAs" page. ---------- jeffrey k eliasen - technologist, philosopher, agent of change blog | linkedin | google+ | facebook | twitter > On May 14, 2018, at 13:08, Asheesh Laroia wrote: > > Also here's the doc I made to gather thoughts about TAs, which may be useful as a reference next year. > > https://docs.google.com/document/d/1cU5dM588ZbkovcXM7GxE5INjXAOkCo90H93v_1ipDdg/edit > > On Mon, May 14, 2018 at 1:05 PM Asheesh Laroia > wrote: > Happy feedback > > "Really good git instructions." > > "The walk thru on Git was awesome. Also like the 'big picture' section on pages to delve deeper after exercises. Thanks a lot!" > > "Everything was amazing." > > "The helpers were amazing." > > "I finally understand forking" > > Read more: https://docs.google.com/spreadsheets/d/1XP2O7nbfja_bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit?ouid=112785794878603790169&usp=sheets_home&ths=true > > Asheesh's notes > > - It was effective! > > - Thanks hugely to Chalmer and Jeff for all their work on the content. Students appreciated the content -- everything from the call-outs for further reading to the thoughtful diagrams and lecture. > > - ~30% of people left within ~1 hour, but I think that was fine. They asked us if there was more content after the self-paced stuff; there is sort-of (there's an emotional appeal at the end for people to take good care of themselves during sprints) and there isn't sort-of, so we said, sure, go ahead and leave, enjoy! I think this was the right choice. > > - We ended at 7:35, aka 2h5m duration. That's good; we told people it'd be 2 hours in duration. > > - We got ~45 pieces of feedback, which is ~25-50% response rate, which is effing huge. Full feedback here: https://docs.google.com/spreadsheets/d/1XP2O7nbfja_bBtzBfY65fzlQQDwol-kZrijxUvMBGZU/edit#gid=0 Sticky notes at the end are good for gathering feedback! > > - We had ~80 people, of which iirc ~10% seemed to be women. > > - GitHub blacklisted our IP address for /login temporarily; some people thought this would be a big problem, but I think it would fix itself within ~30 seconds every time it happened, so it only affected a small number of people for a short amount of time. > > - People really liked the tutorial. > > - Scheduling the time block is an issue still. We had a conflict with the conference dinner. Oh well! > > - Many people came who want to take this material to other conferences: Someone talked to Chalmer about a Russian translation; Nicholle James (CC'd) wants to bring something like it to DjangoCon US; Meghan last year talked about running something similar at PyCascades (CC'd); some people talked about bringing it to ChiPy, the Chicago Python user group. > > - People are hungry for more written material on the PyCon site before sprints -- for example, a link to the tutorial, since it's self-driven. > > - We started with ~18 teaching assistants for ~80 students. I told them that most could dissipate within 30 min if there wasn't much load on TAs. There wasn't much load on TAs, so they did. That was fine. In the future, since we now can be quite confident we can find teaching assistants, we can consider changing the format so that it's one TA to ~5-6 students, and then they make a personal connection to a TA. This would require a very different room layout! I personally have had great experiences with a format like this; I've also personally set up an activity oriented around small groups, which we can consider using in the future perhaps: http://wiki.openhatch.org/Open_Source_Comes_to_Campus/Curriculum/Git (but we can also run the existing Chalmer tutorial in small groups just fine, so long as we have a separate repo for each small group; that way we limit merge conflicts to 5-6 people). > > For other thoughts, read the feedback. > > Asheesh. -------------- next part -------------- An HTML attachment was scrubbed... URL: