{"id":8076,"date":"2017-03-07T14:00:25","date_gmt":"2017-03-07T20:00:25","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=8076"},"modified":"2017-03-07T14:02:51","modified_gmt":"2017-03-07T20:02:51","slug":"helping-ptg-attendees-and-other-developers-get-to-the-openstack-summit","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/helping-ptg-attendees-and-other-developers-get-to-the-openstack-summit\/","title":{"rendered":"Helping PTG attendees and other developers get to the OpenStack Summit"},"content":{"rendered":"

Although the OpenStack design events have changed, developers and operators still have a critical perspective to bring to the OpenStack Summits. At the PTG, a common whisper heard in the hallways was, “I really want to be at the Summit, but my [boss\/HR\/approver] doesn’t understand why I should be there.” To help you out, we took our original “Dear Boss”<\/a> letter and made a few edits for the PTG crowd. If you’re a contributor or developer who wasn’t able to attend the PTG, with a few edits, this letter can also work for you. (Not great with words? Foundation wordsmith Anne can help you out–anne at openstack.org)<\/p>\n

 <\/p>\n

Dear<\/span> [Boss]<\/b>,<\/span><\/p>\n

 <\/p>\n

I would like to attend the OpenStack Summit in Boston, May 8-11, 2017. At the Pike Project Team Gathering in Atlanta (PTG), I was able to learn more about the new development event model for OpenStack. In the past I attended the Summit to participate in the Design Summit, which encapsulated the feedback and planning as well as design and development of creating OpenStack releases. One challenge was that the Design Summit did not leave enough time for \u201chead down\u201d work within upstream project teams (some teams ended up traveling to team-specific mid-cycle sprints to compensate for that). At the Pike PTG, we were able to kickstart the Pike cycle development, working heads down for a full week. We made great progress on both single project and OpenStack-wide goals, which will improve the software for all users, including our organization.<\/span><\/p>\n

 <\/p>\n

Originally, I\u2013\u2013and many other devs\u2013\u2013were under the impression that we no longer needed to attend the OpenStack Summit. However, after a week at the PTG, I see that I have a valuable role to play at the Summit\u2019s \u201cForum\u201d component. The Forum is where I can gather direct feedback and requirements from operators and users, and express my opinion and our organization\u2019s about OpenStack\u2019s future direction. The Forum will let me engage with other groups with similar challenges, project desires and solutions.<\/span><\/p>\n

 <\/p>\n

While our original intent may have been to send me only to the PTG, I would strongly like us to reconsider. The Summit is still an integral part of the OpenStack design process, and I think my attendance is beneficial to both my professional development and our organization. Because of my participation in the PTG, I received a free pass to the Summit, which I must redeem by March 14. \u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\n

 <\/p>\n

Thank you for considering my request.<\/span>
\n[Your Name]<\/b><\/p>\n","protected":false},"excerpt":{"rendered":"

Although the OpenStack design events have changed, developers and operators still have a critical perspective to bring to the OpenStack Summits. At the PTG, a common whisper heard in the hallways was, “I really want to be at the Summit, but my [boss\/HR\/approver] doesn’t understand why I should be there.” To help you out, we… Read more »<\/a><\/p>\n","protected":false},"author":68,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8076"}],"collection":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/users\/68"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=8076"}],"version-history":[{"count":2,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8076\/revisions"}],"predecessor-version":[{"id":8078,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8076\/revisions\/8078"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=8076"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=8076"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=8076"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}