Re: [OpenStack-Infra] Proposed changes to how we run our meeting

[Jimmy Mcarthur]

Clark Boylan 
November 18, 2018 at 1:09 PM
Hello everyone,

In Berlin there was a forum session on dealing with timezones and 
language barriers. There were a couple related ideas that came out of 
that session. In particular that having meetings only when there is a 
strong agenda helps people avoid staying up all night for nothing and 
that listing an agenda ahead of time can help non english speakers 
better prepare for the meeting.
This is a GREAT idea.  Not just for English speakers, but for everyone. 
I'm a big fan of not having meetings just to fill time.


Both ideas seem sound to me and I think we should try to implement 
them for the Infra team. I propose that we require agenda updates 24 
hours prior to the meeting start time and if there are no agenda 
updates we cancel the meeting. Curious to hear if others think this 
will be helpful and if 24 hours is enough lead time to be helpful.
Love the 24 hour lead time. Looking forward to seeing how this works and 
hope it can be adopted across other projects.


We'll have our meeting this Tuesday (with this item on the agenda), 
but it would probably also be good to use the mailing list for 
feedback as I think that gives us a broader set of potential feedback.


Thanks for taking the lead on this Clark!  Nice work :)


Thank you,
Clark

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Proposed changes to how we run our meeting

[Melvin Hillsman]

++

On Sun, Nov 18, 2018 at 2:32 PM Jeremy Stanley  wrote:

> On 2018-11-18 11:09:29 -0800 (-0800), Clark Boylan wrote:
> [...]
> > I propose that we require agenda updates 24 hours prior to the
> > meeting start time and if there are no agenda updates we cancel
> > the meeting. Curious to hear if others think this will be helpful
> > and if 24 hours is enough lead time to be helpful.
> [...]
>
> Sounds great to me, thanks for considering putting these ideas into
> practice!
> --
> Jeremy Stanley
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Proposed changes to how we run our meeting

[Jeremy Stanley]

On 2018-11-18 11:09:29 -0800 (-0800), Clark Boylan wrote:
[...]
> I propose that we require agenda updates 24 hours prior to the
> meeting start time and if there are no agenda updates we cancel
> the meeting. Curious to hear if others think this will be helpful
> and if 24 hours is enough lead time to be helpful.
[...]

Sounds great to me, thanks for considering putting these ideas into
practice!
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Proposed changes to how we run our meeting

[Clark Boylan]

Hello everyone,

In Berlin there was a forum session on dealing with timezones and language 
barriers. There were a couple related ideas that came out of that session. In 
particular that having meetings only when there is a strong agenda helps people 
avoid staying up all night for nothing and that listing an agenda ahead of time 
can help non english speakers better prepare for the meeting.

Both ideas seem sound to me and I think we should try to implement them for the 
Infra team. I propose that we require agenda updates 24 hours prior to the 
meeting start time and if there are no agenda updates we cancel the meeting. 
Curious to hear if others think this will be helpful and if 24 hours is enough 
lead time to be helpful.

We'll have our meeting this Tuesday (with this item on the agenda), but it 
would probably also be good to use the mailing list for feedback as I think 
that gives us a broader set of potential feedback.

Thank you,
Clark

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Sysadmin

[Clark Boylan]

On Sat, Nov 17, 2018, at 9:34 AM, Mathias Gutehall wrote:
> Hi all,
> 
> I just wanted to check if there’s any need for a sysadmin with long 
> experience with Unix/Linux systems in this project? I’m based in Sweden 
> and have been working as a sysadmin since 1995 and since the 3 years 
> with cloud services.

We are always happy to have more help running the community developer 
infrastructure. A good place to start is probably with this document, 
https://docs.openstack.org/infra/system-config/project.html, as it gives a high 
level overview of how we operate and are organized.

To summarize here quickly, we are a community effort to build and run developer 
tooling. We use code review and automated deployment tooling which allows 
people to contribute without having root. If you'd like to get involved and 
become a root the process for that is to start through the code review system 
and take advantage of our automated deployments.

I like to encourage individuals find a task that interests them and start from 
there. Some of the big efforts we currently have are:

1. Modernize configuration management
1a. Convert to ansible for configuration management (gerrit 
topic:update-cfg-mgmt)
1b. Update puppet 3 to puppet 4 since the ansible conversion won't happen 
immediately (gerrit topic:puppet-4)
1c. Use docker images and containers to deploy software, particularly that 
which we install from source
2. IRC bot update to handle the large number of channels we talk to with common 
tooling
3. Gerrit upgrade to 2.15 (may be related to 1a and 1c)
4. OpenDev transition, though this is new and doesn't have many concrete 
actions yet.

There are other items as well. Feel free to follow up with this list, myself or 
on IRC if any of this does interest you and we can go from there.

Hope this helps,
Clark

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra