Open Stack

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. 

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. 

Cheers,
Allison

Allison Price
OpenStack Foundation
allison at openstack.org


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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171127/c749a227/attachment.html>