Re: [openstack-dev] [tc] [all] TC Report 43

2017-10-31 Thread Thierry Carrez 
Mike Perez wrote:
> On 11:17 Oct 25, Flavio Percoco wrote:
>> On 24/10/17 19:26 +0100, Chris Dent wrote:
>>> It's clear that anyone and everyone _could_ write their own blogs and
>>> syndicate to the [OpenStack planet](http://planet.openstack.org/) but
>>> this doesn't have the same panache and potential cadence as an
>>> official thing _might_. It comes down to people having the time. Eking
>>> out the time for this blog, for example, can be challenging.
>>>
>>> Since this is the second [week in a
>>> row](https://anticdent.org/tc-report-42.html) that Josh showed up with
>>> an idea, I wonder what next week will bring?
>>
>> I might not be exactly the same but, I think the superuser's blog could be a
>> good place to do some of this writing. There are posts of various kinds in 
>> that
>> blog: technical, community, news, etc. I wonder how many folks from the
>> community are aware of it and how many would be willing to contribute to it 
>> too.
>> Contributing to the superuser's blog is quite simple, really.
> 
> Anne used to do TC updates and they were posted to the OpenStack Blog:
> 
> https://www.openstack.org/blog/category/technical-committee-updates/

Those were actually officially published by the Technical Committee
(prepared by the "communications" workgroup that Anne was leading), so
they were reviewed by TC members and represented the consensual view.

There are really only two options:

Editorial content to some official publication, where the posts are
vetted by a review committee for correctness/consensus: that's what
SuperUser is doing, and what the "official blog" was(?) doing.

Personal content, where opinionated blogs are automatically aggregated
with minimal on-topic checks: that's what the planet is doing.

(Sometimes, a personal blog post makes great SuperUser content and is
copied over)

We could add a specific, technically-focused editorial outlet, or we
could set up a specific, technically-focused personal blog aggregator.
But I feel like we could also reuse the SuperUser publication and the
existing Planet. The main issue seems to be the lack of produced
content, rather than lack of discoverability of the existing outlets...

-- 
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] [tc] [all] TC Report 43

2017-10-30 Thread Mike Perez 
On 11:17 Oct 25, Flavio Percoco wrote:
> On 24/10/17 19:26 +0100, Chris Dent wrote:
> >It's clear that anyone and everyone _could_ write their own blogs and
> >syndicate to the [OpenStack planet](http://planet.openstack.org/) but
> >this doesn't have the same panache and potential cadence as an
> >official thing _might_. It comes down to people having the time. Eking
> >out the time for this blog, for example, can be challenging.
> >
> >Since this is the second [week in a
> >row](https://anticdent.org/tc-report-42.html) that Josh showed up with
> >an idea, I wonder what next week will bring?
> 
> I might not be exactly the same but, I think the superuser's blog could be a
> good place to do some of this writing. There are posts of various kinds in 
> that
> blog: technical, community, news, etc. I wonder how many folks from the
> community are aware of it and how many would be willing to contribute to it 
> too.
> Contributing to the superuser's blog is quite simple, really.

Anne used to do TC updates and they were posted to the OpenStack Blog:

https://www.openstack.org/blog/category/technical-committee-updates/

-- 
Mike Perez


pgpHJDadMERqZ.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] [tc] [all] TC Report 43

2017-10-25 Thread Flavio Percoco 

On 24/10/17 19:26 +0100, Chris Dent wrote:

# TC Participation

At last Thursday's [office
hours](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-10-19.log.html#t2017-10-19T15:01:02)
Emilien asked, as a thought experiment, what people thought of the
idea of TC term limits. In typical office hours fashion, this quickly
went off into a variety of topics, some only tangentially related to
term limits.

To summarize, incompletely, the pro-reason is: Make room and
opportunities for new leadership. The con-reason is: Maintain a degree
of continuity.

This led to some discussion of the value of "history and baggage" and
whether such things are a keel or anchor in managing the nautical
metaphor of OpenStack. We did not agree, which is probably good
because somewhere in the middle is likely true.

Things then circled back to the nature of the TC: court of last resort
or something with a more active role in executive leadership. If the former,
who does the latter? Many questions related to significant change are
never resolved because it is not clear who does these things.

There's a camp that says "the people who step up to do it". In my experience
this is a statement made by people in a position of privilege and may
(intentionally or otherwise) exclude others or lead to results which have
unintended consequences.

This then led to meandering about the nature of facilitation.

(Like I said, a variety of topics.)

We did not resolve these questions except to confirm that the only way
to address these things is to engage with not just the discussion, but
also the work.


Sad I couldn't attend this office hour :(

I would love to see this idea being explored further. Perhaps a mailing list
thread, then a resolution (Depending on the ML thread feedback) and some f2f
conversations at the next PTG (or even the forum.

Emilien, up to start the thread?
Flavio


# OpenStack Technical Blog

Josh Harlow showed up with [an
idea](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-10-19.log.html#t2017-10-19T18:19:30).
An OpenStack equivalent of the [kubernetes
blog](http://blog.kubernetes.io/), focused on interesting technology
in OpenStack. This came up again on
[Friday](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-10-20.log.html#t2017-10-20T18:13:01).

It's clear that anyone and everyone _could_ write their own blogs and
syndicate to the [OpenStack planet](http://planet.openstack.org/) but
this doesn't have the same panache and potential cadence as an
official thing _might_. It comes down to people having the time. Eking
out the time for this blog, for example, can be challenging.

Since this is the second [week in a
row](https://anticdent.org/tc-report-42.html) that Josh showed up with
an idea, I wonder what next week will bring?


I might not be exactly the same but, I think the superuser's blog could be a
good place to do some of this writing. There are posts of various kinds in that
blog: technical, community, news, etc. I wonder how many folks from the
community are aware of it and how many would be willing to contribute to it too.
Contributing to the superuser's blog is quite simple, really.

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

Re: [openstack-dev] [tc] [all] TC Report 43

2017-10-24 Thread Clay Gerrard 
On Tue, Oct 24, 2017 at 11:26 AM, Chris Dent  wrote:

>
>
> Since this is the second [week in a
> row](https://anticdent.org/tc-report-42.html) that Josh showed up with
> an idea, I wonder what next week will bring?
>
>
^ That's pretty cool.  Thanks for sending this as always Chris.

-Clay
__
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] [tc] [all] TC Report 43

2017-10-24 Thread Chris Dent 


# Welcome New TC Members

Main news to report about the OpenStack Technical Committee (TC) is that
the elections have finished and there are some new members. The three
incumbents that ran returned for another year, meaning three new
people join. There's more information in a [superuser
article](http://superuser.openstack.org/articles/openstack-tc-pike-elections/).
Welcome and congratulations to everyone.

After each election a new chair is selected. Any member of the TC may
be the chair, self-nomination is done by posting a review. The traditional
chair, Thierry, has posted [his
nomination](https://review.openstack.org/#/c/514553/1).

A [welcome
message](http://lists.openstack.org/pipermail/openstack-tc/2017-October/001477.html)
was posted to the TC mailing list with information and references for
how things work.

# TC Participation

At last Thursday's [office
hours](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-10-19.log.html#t2017-10-19T15:01:02)
Emilien asked, as a thought experiment, what people thought of the
idea of TC term limits. In typical office hours fashion, this quickly
went off into a variety of topics, some only tangentially related to
term limits.

To summarize, incompletely, the pro-reason is: Make room and
opportunities for new leadership. The con-reason is: Maintain a degree
of continuity.

This led to some discussion of the value of "history and baggage" and
whether such things are a keel or anchor in managing the nautical
metaphor of OpenStack. We did not agree, which is probably good
because somewhere in the middle is likely true.

Things then circled back to the nature of the TC: court of last resort
or something with a more active role in executive leadership. If the former,
who does the latter? Many questions related to significant change are
never resolved because it is not clear who does these things.

There's a camp that says "the people who step up to do it". In my experience
this is a statement made by people in a position of privilege and may
(intentionally or otherwise) exclude others or lead to results which have
unintended consequences.

This then led to meandering about the nature of facilitation.

(Like I said, a variety of topics.)

We did not resolve these questions except to confirm that the only way
to address these things is to engage with not just the discussion, but
also the work.

# OpenStack Technical Blog

Josh Harlow showed up with [an
idea](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-10-19.log.html#t2017-10-19T18:19:30).
An OpenStack equivalent of the [kubernetes
blog](http://blog.kubernetes.io/), focused on interesting technology
in OpenStack. This came up again on
[Friday](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-10-20.log.html#t2017-10-20T18:13:01).

It's clear that anyone and everyone _could_ write their own blogs and
syndicate to the [OpenStack planet](http://planet.openstack.org/) but
this doesn't have the same panache and potential cadence as an
official thing _might_. It comes down to people having the time. Eking
out the time for this blog, for example, can be challenging.

Since this is the second [week in a
row](https://anticdent.org/tc-report-42.html) that Josh showed up with
an idea, I wonder what next week will bring?

--
Chris Dent  (⊙＿⊙') https://anticdent.org/
freenode: cdent tw: @anticdent__
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