Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-29 Thread Joshua Harlow 

Thierry Carrez wrote:

Jimmy McArthur wrote:

Thierry Carrez wrote:

Historically blog.o.o used to be our only blog outlet, so almost
anything would go in:

"OpenStack Events Sponsorship Webinar"
"New Foundation Gold Members&  Corporate Sponsors"
"HP Announces Private Beta Program for OpenStack Cloud"
"2016 OpenStack T-Shirt Design Contest"

What Josh wants is a curated technical blog, so if we reused blog.o.o
for this (and I think it's a good idea), we'd likely want to have a bit
more rules on what's appropriate.

Agreed. It's almost solely used for developer digest now and isn't
frequently updated. Most of the promotion of sponsors and news goes into
o.o/News, SuperUser, or one of our other marketing channels. It's a good
time for the community to repurpose it :)


Perfect, we have a plan.

Before we make it tech-only and boring, let us all take a minute to
remember the OpenStack jingle:

https://www.openstack.org/blog/2011/07/openstack-the-best-sounding-cloud/



Errr, ummm, woah, lol

We might need to work on our DJ skills, lol

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-29 Thread Jean-Philippe Evrard 
On 29 November 2017 at 11:30, Thierry Carrez  wrote:
> Jimmy McArthur wrote:
>> Thierry Carrez wrote:
>>> Historically blog.o.o used to be our only blog outlet, so almost
>>> anything would go in:
>>>
>>> "OpenStack Events Sponsorship Webinar"
>>> "New Foundation Gold Members & Corporate Sponsors"
>>> "HP Announces Private Beta Program for OpenStack Cloud"
>>> "2016 OpenStack T-Shirt Design Contest"
>>>
>>> What Josh wants is a curated technical blog, so if we reused blog.o.o
>>> for this (and I think it's a good idea), we'd likely want to have a bit
>>> more rules on what's appropriate.
>>
>> Agreed. It's almost solely used for developer digest now and isn't
>> frequently updated. Most of the promotion of sponsors and news goes into
>> o.o/News, SuperUser, or one of our other marketing channels. It's a good
>> time for the community to repurpose it :)
>
> Perfect, we have a plan.
>
> Before we make it tech-only and boring, let us all take a minute to
> remember the OpenStack jingle:
>
> https://www.openstack.org/blog/2011/07/openstack-the-best-sounding-cloud/

I haven't moved. Then I laughed. Thanks for that share Thierry!

>
> --
> Thierry Carrez (ttx)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-29 Thread Thierry Carrez 
Jimmy McArthur wrote:
> Thierry Carrez wrote:
>> Historically blog.o.o used to be our only blog outlet, so almost
>> anything would go in:
>>
>> "OpenStack Events Sponsorship Webinar"
>> "New Foundation Gold Members & Corporate Sponsors"
>> "HP Announces Private Beta Program for OpenStack Cloud"
>> "2016 OpenStack T-Shirt Design Contest"
>>
>> What Josh wants is a curated technical blog, so if we reused blog.o.o
>> for this (and I think it's a good idea), we'd likely want to have a bit
>> more rules on what's appropriate.
> 
> Agreed. It's almost solely used for developer digest now and isn't
> frequently updated. Most of the promotion of sponsors and news goes into
> o.o/News, SuperUser, or one of our other marketing channels. It's a good
> time for the community to repurpose it :)

Perfect, we have a plan.

Before we make it tech-only and boring, let us all take a minute to
remember the OpenStack jingle:

https://www.openstack.org/blog/2011/07/openstack-the-best-sounding-cloud/

-- 
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-28 Thread Jimmy McArthur 
Please feel free to reach out to me if you're interested in contributing 
and/or playing editor. I'll be happy to get anyone that needs it a login.


Cheers,
Jimmy

Mike Perez wrote:

On 10:45 Nov 28, Jimmy McArthur wrote:

Thierry Carrez wrote:

What Josh wants is a curated technical blog, so if we reused blog.o.o
for this (and I think it's a good idea), we'd likely want to have a bit
more rules on what's appropriate.

Agreed. It's almost solely used for developer digest now and isn't
frequently updated. Most of the promotion of sponsors and news goes into
o.o/News, SuperUser, or one of our other marketing channels. It's a good
time for the community to repurpose it :)


+1 from me to bring more life to the blog than just the dev digest!

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-28 Thread Mike Perez 
On 10:45 Nov 28, Jimmy McArthur wrote:
> Thierry Carrez wrote:
> >
> >What Josh wants is a curated technical blog, so if we reused blog.o.o
> >for this (and I think it's a good idea), we'd likely want to have a bit
> >more rules on what's appropriate.
> 
> Agreed. It's almost solely used for developer digest now and isn't
> frequently updated. Most of the promotion of sponsors and news goes into
> o.o/News, SuperUser, or one of our other marketing channels. It's a good
> time for the community to repurpose it :)

+1 from me to bring more life to the blog than just the dev digest!

-- 
Mike Perez (thingee)


pgpdODcUhXcyI.pgp
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-28 Thread Jimmy McArthur 



Thierry Carrez wrote:

Flavio Percoco wrote:

On 27/11/17 13:14 -0600, Jimmy McArthur wrote:

Joshua Harlow wrote:

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...

This is basically what https://www.openstack.org/blog/ is for. It's
using Wordpress. It's developer-centric. Anyone can submit to it and
we have editors that can publish it. We also have pretty solid SEO.

Interestingly enough, not many folks are (were) aware of this. It was not
brought up during the discussion at the forum. I'm glad you did, though.

If we already have a platform for this then I would say we need to
promote it
more and find someone (Josh? ;) that will actively seek for content.

Thanks for pointing us to o.o/blog, Jimmy.


Historically blog.o.o used to be our only blog outlet, so almost
anything would go in:

"OpenStack Events Sponsorship Webinar"
"New Foundation Gold Members&  Corporate Sponsors"
"HP Announces Private Beta Program for OpenStack Cloud"
"2016 OpenStack T-Shirt Design Contest"

What Josh wants is a curated technical blog, so if we reused blog.o.o
for this (and I think it's a good idea), we'd likely want to have a bit
more rules on what's appropriate.


Agreed. It's almost solely used for developer digest now and isn't 
frequently updated. Most of the promotion of sponsors and news goes into 
o.o/News, SuperUser, or one of our other marketing channels. It's a good 
time for the community to repurpose it :)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-28 Thread Thierry Carrez 
Flavio Percoco wrote:
> On 27/11/17 13:14 -0600, Jimmy McArthur wrote:
>>
>>
>> Joshua Harlow wrote:
>>> 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...
>>
>> This is basically what https://www.openstack.org/blog/ is for. It's
>> using Wordpress. It's developer-centric. Anyone can submit to it and
>> we have editors that can publish it. We also have pretty solid SEO.
> 
> Interestingly enough, not many folks are (were) aware of this. It was not
> brought up during the discussion at the forum. I'm glad you did, though.
> 
> If we already have a platform for this then I would say we need to
> promote it
> more and find someone (Josh? ;) that will actively seek for content.
> 
> Thanks for pointing us to o.o/blog, Jimmy.

Historically blog.o.o used to be our only blog outlet, so almost
anything would go in:

"OpenStack Events Sponsorship Webinar"
"New Foundation Gold Members & Corporate Sponsors"
"HP Announces Private Beta Program for OpenStack Cloud"
"2016 OpenStack T-Shirt Design Contest"

What Josh wants is a curated technical blog, so if we reused blog.o.o
for this (and I think it's a good idea), we'd likely want to have a bit
more rules on what's appropriate.

-- 
Thierry Carrez (ttx)



signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-28 Thread Flavio Percoco 

On 27/11/17 13:14 -0600, Jimmy McArthur wrote:



Joshua Harlow wrote:

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...


This is basically what https://www.openstack.org/blog/ is for. It's
using Wordpress. It's developer-centric. Anyone can submit to it and
we have editors that can publish it. We also have pretty solid SEO.


Interestingly enough, not many folks are (were) aware of this. It was not
brought up during the discussion at the forum. I'm glad you did, though.

If we already have a platform for this then I would say we need to promote it
more and find someone (Josh? ;) that will actively seek for content.

Thanks for pointing us to o.o/blog, Jimmy.
Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Allison Price 
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
alli...@openstack.org


> On Nov 27, 2017, at 2:01 PM, Joshua Harlow  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 
>> 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
>> alli...@openstack.org 
>> 
>> 
>> 
>>> On Nov 27, 2017, at 1:44 PM, Joshua Harlow >> > 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-requ...@lists.openstack.org
 ?subject:unsubscribe

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Joshua Harlow 

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 
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
alli...@openstack.org 




On Nov 27, 2017, at 1:44 PM, Joshua Harlow > 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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Doug Hellmann 
Excerpts from Joshua Harlow's message of 2017-11-27 11:44:54 -0800:
> 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 ;)

I think you'd be great as an Acquisitions Editor. That's a role at
a publisher that goes out looking for people to write about interesting
things, sometimes starting with the topic and finding the person
and sometimes vice versa. To launch something like this, we need
someone to recruit writers. You have a good eye for "interesting"
and you clearly have a vision for what this content should look
like. Give it some thought.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Allison Price 
I agree with Jimmy that 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
alli...@openstack.org



> On Nov 27, 2017, at 1:44 PM, Joshua Harlow  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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Joshua Harlow 

Jay Pipes wrote:

On 11/27/2017 01:54 PM, Joshua Harlow wrote:

I want a place that is like http://blog.kubernetes.io/


You know that's not for developers (only) of k8s, right? That's for
users, marketers, product managers, etc.


We don't have to exactly copy it (that was not the intention).

But looking at the following it seems like its slightly more than that.

'This post is written by Kelsey Hightower, Staff Developer Advocate at 
Google, and Sandra Guo, Product Manager at Google.'


'Today's post is by Lantao Liu, Software Engineer at Google, and Mike 
Brown, Open Source Developer Advocate at IBM.'


'Editor's note: this post is part of a series of in-depth articles on 
what's new in Kubernetes 1.8. Today’s post comes from Ahmet Alp Balkan, 
Software Engineer, Google.'


'Editor's note: Today’s post by Frank Budinsky, Software Engineer, IBM, 
Andra Cismaru, Software Engineer, Google, and Israel Shalom, Product 
Manager, Google, is the second post in a three-part series on Istio. It 
offers a closer look at request routing and policy management.'


^ A lot of engineers in that (not just product folks, though there are 
some yes..).




So, when you say *for developers*, what exactly do you mean? Are you
referring to developers of OpenStack projects or are you referring to
*users* of cloud services -- i.e. application developers?


People like jay and josh and dims and ..., or future jay (jr) and josh 
(jr) folks...



Best,
-jay

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Joshua Harlow 

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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Jimmy McArthur 



Joshua Harlow wrote:
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... 


This is basically what https://www.openstack.org/blog/ is for. It's 
using Wordpress. It's developer-centric. Anyone can submit to it and we 
have editors that can publish it. We also have pretty solid SEO.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Doug Hellmann 
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? :-)

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Jay Pipes 

On 11/27/2017 01:54 PM, Joshua Harlow wrote:

I want a place that is like http://blog.kubernetes.io/


You know that's not for developers (only) of k8s, right? That's for 
users, marketers, product managers, etc.


So, when you say *for developers*, what exactly do you mean? Are you 
referring to developers of OpenStack projects or are you referring to 
*users* of cloud services -- i.e. application developers?


Best,
-jay

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Joshua Harlow 

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...




[0]
http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-11-23.log.html#t2017-11-23T15:01:25

[1] http://planet.openstack.org/
[2] http://superuser.openstack.org/

Flavio

--
@flaper87
Flavio Percoco

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Melvin Hillsman 
On Mon, Nov 27, 2017 at 8:16 AM, Dan Prince  wrote:

>
>
> On Mon, Nov 27, 2017 at 8:55 AM, 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.
>>
>
> Why not just write article's on existing blogs, link them into planet, and
> then if they are really good promote them at a higher level?
>
> Having a separate blog that is maintained by a few seems a bit elitist to
> me.
>
> Dan
>

+1


>
>> 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
>>
>
> What is really missing in our current infrastructure setup that really
> prevents any of the above?
>

+1


>
>
>> - 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?
>>
>> [0] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23op
>> enstack-tc.2017-11-23.log.html#t2017-11-23T15:01:25
>> [1] http://planet.openstack.org/
>> [2] http://superuser.openstack.org/
>>
>> Flavio
>>
>> --
>> @flaper87
>> Flavio Percoco
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

My .02, I would like to encourage in general we try to streamline and make
more effective what we already do versus adding more and remove excess.


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Amrith Kumar 
I don't see much of a point in an OpenStack Technical blog. After all,
those who want to blog likely already have blogs that are syndicated
through the OpenStack digest mechanism.

What problem or existing shortcoming is sought to be addressed by this
blog? And is there some reason that existing (individual) blogs can't be
used for this?

The issue may be centralization and longevity which, given the transient
nature of all of our involvement in OpenStack is a perfectly legitimate
concern. But, I'd like that this be articulated clearly if it is in fact
the issue.

-amrith


On Mon, Nov 27, 2017 at 9:16 AM, Dan Prince  wrote:

>
>
> On Mon, Nov 27, 2017 at 8:55 AM, 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.
>>
>
> Why not just write article's on existing blogs, link them into planet, and
> then if they are really good promote them at a higher level?
>
> Having a separate blog that is maintained by a few seems a bit elitist to
> me.
>
> Dan
>
>
>> 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
>>
>
> What is really missing in our current infrastructure setup that really
> prevents any of the above?
>
>
>> - 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?
>>
>> [0] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23op
>> enstack-tc.2017-11-23.log.html#t2017-11-23T15:01:25
>> [1] http://planet.openstack.org/
>> [2] http://superuser.openstack.org/
>>
>> Flavio
>>
>> --
>> @flaper87
>> Flavio Percoco
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Dan Prince 
On Mon, Nov 27, 2017 at 8:55 AM, 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.
>

Why not just write article's on existing blogs, link them into planet, and
then if they are really good promote them at a higher level?

Having a separate blog that is maintained by a few seems a bit elitist to
me.

Dan


> 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
>

What is really missing in our current infrastructure setup that really
prevents any of the above?


> - 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?
>
> [0] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23op
> enstack-tc.2017-11-23.log.html#t2017-11-23T15:01:25
> [1] http://planet.openstack.org/
> [2] http://superuser.openstack.org/
>
> Flavio
>
> --
> @flaper87
> Flavio Percoco
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Flavio Percoco 

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?

[0] 
http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-11-23.log.html#t2017-11-23T15:01:25
[1] http://planet.openstack.org/
[2] http://superuser.openstack.org/

Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev