
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Either Jimmy or I can help community members get a login to the blog, and once a post is ready to be published, either of us could push it live. </div><div class=""><br class=""></div><div class="">We do not have someone that is currently seeking out content for the blog. Superuser is managed more closely on a day-to-day basis with a more traditional editorial process. If there is anyone from the dev community that would like to help seek out content / contributors, that would be welcomed and greatly appreciated. </div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Allison</div><div class="">

<br class=""><div class="">

<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Allison Price</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">OpenStack Foundation</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"><a href="mailto:allison@openstack.org" class="">allison@openstack.org</a></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=""><br class=""></div>

</div>

<br class=""><div><blockquote type="cite" class=""><div class="">On Nov 27, 2017, at 2:01 PM, Joshua Harlow <<a href="mailto:harlowja@fastmail.com" class="">harlowja@fastmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">How does one get a login or submit things to <a href="http://openstack.org/blog?" class="">openstack.org/blog?</a><br class=""><br class="">Is there any editor actively seeking out things (and reviewing) for folks to write (a part time job I would assume?).<br class=""><br class="">Josh<br class=""><br class="">Allison Price wrote:<br class=""><blockquote type="cite" class="">I agree with Jimmy that <a href="http://openstack.org/blog" class="">openstack.org/blog</a> <<a href="http://openstack.org/blog" class="">http://openstack.org/blog</a>><br class="">would be a great location for content like this, especially since the<br class="">main piece of content is the OpenStack-dev ML digest that Mike creates<br class="">weekly. Like Flavio mentioned, Superuser is another resource we can<br class="">leverage for tutorials or new features. Both the blog and Superuser are<br class="">Wordpress, enabling contributions from anyone with a login and content<br class="">to share.<br class=""><br class="">Superuser and the OpenStack blog is already syndicated with Planet<br class="">OpenStack for folks who have already subscribed to the Planet OpenStack<br class="">feed.<br class=""><br class="">Allison<br class=""><br class="">Allison Price<br class="">OpenStack Foundation Marketing<br class=""><a href="mailto:allison@openstack.org" class="">allison@openstack.org</a> <<a href="mailto:allison@openstack.org" class="">mailto:allison@openstack.org</a>><br class=""><br class=""><br class=""><br class=""><blockquote type="cite" class="">On Nov 27, 2017, at 1:44 PM, Joshua Harlow <<a href="mailto:harlowja@fastmail.com" class="">harlowja@fastmail.com</a><br class=""><<a href="mailto:harlowja@fastmail.com" class="">mailto:harlowja@fastmail.com</a>>> wrote:<br class=""><br class="">Doug Hellmann wrote:<br class=""><blockquote type="cite" class="">Excerpts from Joshua Harlow's message of 2017-11-27 10:54:02 -0800:<br class=""><blockquote type="cite" class="">Flavio Percoco wrote:<br class=""><blockquote type="cite" class="">Greetings,<br class=""><br class="">Last Thursday[0], at the TC office hours, we brainstormed a bit around<br class="">the idea<br class="">of having a tech blog. This idea came first from Joshua Harlow and it<br class="">was then<br class="">briefly discussed at the summit too.<br class=""><br class="">The idea, we have gathered, is to have a space where the community<br class="">could<br class="">write<br class="">technical posts about OpenStack. The idea is not to have an aggregator<br class="">(that's<br class="">what our planet[1] is for) but a place to write original and curated<br class="">content.<br class="">During the conversation, we argued about what kind of content would be<br class="">acceptable for this platform. Here are some ideas of things we could<br class="">have there:<br class=""><br class="">- Posts that are dev-oriented (e.g: new functions on an oslo lib)<br class="">- Posts that facilitate upstream development (e.g: My awesome dev<br class="">setup)<br class="">- Deep dive into libvirt internals<br class="">- ideas?<br class=""><br class="">As Chris Dent pointed out on that conversation, we should avoid<br class="">making this<br class="">place a replacement for things that would otherwise go on the mailing<br class="">list -<br class="">activity reports, for example. Having dev news in this platform, we<br class="">would<br class="">overlap with things that go already on the mailing list and, arguably,<br class="">we would<br class="">be defeating the purpose of the platform. But, there might be room for<br class="">both(?)<br class=""><br class="">Ultimately, we should avoid topics promoting new features in<br class="">services as<br class="">that's what<br class="">superuser[2] is for.<br class=""><br class="">So, what are your thoughts about this? What kind of content would you<br class="">rather<br class="">have posted here? Do you like the idea at all?<br class=""></blockquote>Yes, I like it :)<br class=""><br class="">I want a place that is like <a href="http://blog.kubernetes.io/" class="">http://blog.kubernetes.io/</a><br class=""><br class="">With say an editor that solicits (and backlogs topics and stories and<br class="">such) various developers/architects at various companies and creates a<br class="">actually human curated place for developers and technology and<br class="">architecture to be spot-lighted.<br class=""><br class="">To me personal blogs can be used for this, sure, but that sort of misses<br class="">the point of having a place that is targeted for this (and no I don't<br class="">really care about finding and subscribing to 100+ random joe blogs that<br class="">I will never look at more than once). Ideally that place would not<br class="">become `elitist` as some others have mentioned in this thread (ie, don't<br class="">pick an elitist editor? lol).<br class=""><br class="">The big desire for me is to actually have a editor (a person or people)<br class="">involved that is keeping such a blog going and editing it and curating<br class="">it and ensuring it gets found in google searches and is *developer*<br class="">focused...<br class=""></blockquote><br class="">Are you volunteering? :-)<br class=""></blockquote><br class="">You don't want me to be an editor ;)<br class=""><br class=""><blockquote type="cite" class=""><br class="">Doug<br class=""><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a><br class=""><<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">mailto:OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></blockquote><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a><br class=""><<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">mailto:OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></blockquote><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></blockquote><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></div></blockquote></div><br class=""></div></body></html>