##March 26, 2015 ###progress
- Conferences: proposal for Gluecon
- Conferences/workshops: met with Everett about OpenStack 101 workshop at QCon
- Conferences/workshops: practiced Pycon workshop material
- OSS program: managed billing issues
- Sponsorships: fielded requests
- Outreach: worked with Ken to re-imagine outreach roles on the DevEx team
###plans
- tmpnb blog post for Kyle and Ash to review March 30
- draft of text and viz for outreach activity (for website or blog post) to Ken? March 31
- robots.txt work with Kyle March 30-April 1
- continue conversations with Ken
- continue OSS program management
- continue Pycon workshop prep until April 8
- abstract and outline for OpenStack 101 workshop at QCon March 26
###problems
- OSS program billing issues are so so painful
##March 19, 2015 ###progress (partial week):
- rax.io/Crew: final feedback and survey results to rax.io workshops instructors
- Conferences: developed curriculum for Pycon 101 workshop (lead teacher)
- Conferences: reviewed material for Pycon Data Analysis workshop (TAing)
- OSS program: managed billing issues
- event sponsorships: fielded requests for sponsorships
###plans:
- OSS program: manage accounts and help customers
- OSS program: jiffy-ticketing development
- Conferences: submit proposals to GlueCon and SOTM
- tmpnb: blog post
###problems:
- None
##March 12, 2015 ETO from March 9-16
##March 5, 2015
###progress:
- rax.io: created and sent survey to workshop participants; created a repository of workshop material that could be used for Racker technical training
- event sponsorships: fielded requests for sponsorships
- developer.rackspace.com: created issues and sketched plans for commmunity subpages; troubleshooted issues with externally-facing email addresses
- OSS program: provided technical support for OSS program participants; onboarded new customers; managed billing issues
###plans:
- ETO March 9-16
- jiffy-ticketing: ongoing
- PyCon: workshop prep ongoing until April 8
- OSS program: verifying status of accounts ongoing task
- OSS program: providing outreach to customers in the program ongoing task
###problems:
##February 26, 2015
###progress:
- rax.io: attended rax.io and co-organized workshop track
- event sponsorships: fielded requests for sponsorships
- developer.rackspace.com: launched new community page on d.r.c. and updated global nav: https://developer.rackspace.com/community/
- OSS program: provided technical support for OSS program participants; onboarded new customers; managed billing issues
###plans:
- jiffy-ticketing - handling auth/token validation with lefty and encore api Mar 3
- jiffy-ticketing - releasing code for account data parser and on internal github Mar 3
- OSS program: verifying status of accounts ongoing task
- OSS program: providing outreach to customers in the program ongoing task
###problems: None
##February 19, 2015
###progress:
- rax.io: released workshop tickets and handled workshop registration; handled logistics with Workplace Services; mentored workshop instructors
- event sponsorships: fielded requests for sponsorships; submitted a PR to remove sponsorship form from developer.rackspace.com
- developer.rackspace.com: submitted PR with new community page text that highlights our team's OSS contributions, event sponsorship program, and OSS hosting program
- OSS program: fielded questions about Usage Overview bug; provided technical support for OSS program participants; onboarded new customers
- jiffy-ticketing: researched Click for building CLIs and internal Python tools that handle token validation
###plans:
- rax.io: attending conference and leading workshop track Feb 23-27
- jiffy-ticketing - handling auth/token validation with lefty and encore api Feb 27
- jiffy-ticketing - releasing code for account data parser and on internal github Feb 27
- OSS program: verifying status of accounts ongoing task
- OSS program: providing outreach to customers in the program ongoing task
- tmpnb: writing a "setting up tmpnb for your meetup" post for the dev blog Feb 27
- nbviewer: adding search functionality - feature won't be complete before end of sprint, but I will finish preliminary steps and possible pair-programming with Kyle Kelley during rax.io to complete Feb 27
###problems:
- OSS program: I'm concerned that we haven't communicated anything about the Usage Overview bug to our customers receiving discounts in the OSS and developer+ programs
##February 12, 2015
###progress:
- countdown to rax.io: handled workshop instructor and speaker scheduling and communication; engaged in preliminary hackday planning
- event sponsorships: fielded requests for sponsorships; created templates for internal conference and meetup sponsorship requests
- OSS program: began work on jiffy-ticketing; onboarded new customers; provided technical support for existing OSS program participants
###plans:
- rax.io: releasing tickets for workshops and facilitating workshop content creation and sharing Feb 13
- rax.io: planning to attend the conference the second week of upcoming sprint Feb 23-27
- event sponsorships: removing request form from d.r.c and replacing the community page with data and text about events/communities we have supported Feb 16/17
- jiffy-ticketing - handling auth/token-validation with lefty and encore api Feb 18
- jiffy-ticketing - releasing code for account data parser and on internal github Feb 20
- OSS program: verifying status of accounts ongoing task
- OSS program: outreach to customers in the program ongoing task
- tmpnb: writing a "setting up tmpnb for your meetup" post for the dev blog Feb 20
- nbviewer: adding search functionality - feature won't be complete before end of sprint, but I will finish preliminary steps and possible pair-programming with Kyle Kelley during rax.io to complete Feb 20
###problems:
- OSS programs: challenges getting cost data on accounts, will investigate contacting [email protected] for cost/spend analysis on accounts; customer account was sent to a collection agency even though the accounts team promised they had taken care of the issue
- rax.io: conference planning is taking up lots of time; trying to limit participation but finding it difficult. (edited)