- What's your team's name https://wiki.openstack.org/wiki/Operation_Docs_SIG - Who's leading or active in this team Sean McGinnis, Chris Morgan, Erik McCormick - What's this team recently plan or doing This SIG is just getting going. The first task was to adopt some orphaned docs so they have a home for code changes and a way to publish. That has been done (Sean M). Next we want to significantly improve those documents (operators guide, HA guide, arch guide). HA guide is under heavy rewrite by Adam Speirs. The others we have only got as far as minor tweaks so far. We have been discussing breaking the install instructions part of the operators guide into a separate document since that's an extremely broad and somewhat controversal topic all by itself. Another urgent thing is to improve the getting started info, as the instructions on how to have development environment "merely" for the openstack doc tools is a bit summarised and assumes some technical expertise. We want to make it obvious how to build and modify these documents if you have never touched any of the key tools before. - How people can join this team? We've handled this within the Ops Meetups team meetings and in person at meetups and summits so far since it's mostly the same people. We have discussed having a separate regular meeting but have not set one up so far. So, for now, join the IRC meeting or reach out via the openstack-discuss mailing list. - What's your most needed help interns of actions or technical features? Contributions to the above mentioned documents. We did get expressions of interest in this work at the Berlin ops meetup. - Which team (or who) you think that have a part in above help request (high potentially is fine)? The core docs team and the translations team have been helping and that is appreciated, - Anything else you wish to share to attendees? Nothing at this time. On Tue, Mar 26, 2019 at 12:44 AM Rico Lin <rico.lin.guanyu@gmail.com> wrote:
Dear all SIG and WG members
I would like to ask for three favors from each group. Thank you for your kindly help.
tl;dr: 1. As an action from [3], we will have a forum `Help most needed for SIGs and WGs` [4]. And would like to ask each group kindly provide me the following help most needed information, including
- What's your team's name - Who's leading or active in this team - What's this team recently plan or doing - How people can join this team? - What's your most needed help interns of actions or technical features? - Which team (or who) you think that have a part in above help request (high potentially is fine)? - Anything else you wish to share to attendees?
2. update help most needed section in [1]. So anyone can understand what help your group needs. Also, TCs and UCs will have a better view of how group effort been working in the community and how community priority should be if regarding SIGs and WGs. 3. Also, consider your needs as a community goal? Add it in [2] now.
-------------------------------------------longer version--------------------------------------------------- ( don't worry, not like I can do a super long readable article, but under the power of line-counting this is longer and still readable for sure!)
1. Back in the last summit, we have a forum [3] to talk about how can we help to expose SIGs and WGs. As an action, We will host a forum in coming Denver summit, to talk about `Help most needed for SIGs and WGs` [4]. This forum will present the most needed help from SIGs and WGs. By plan to also invite everyone (will try to invite people from each team and group) in the community to join this forum. We might get attention from people and potentially helpers:). Therefore, I do wish to have participants from every group. Please kindly provide me the following help most needed information, including
- What's your team's name - Who's leading or active in this team - What's this team recently plan or doing - How people can join this team? - What's your most needed help interns of actions or technical features? - Which team (or who) you think that have a part in above help request (high potentially is fine)? - Anything else you wish to share to attendees?
I will try to reach out to each team too, but if you already have answers to the above questions, that will be super! Since we might get around 16 groups, will try to get to the ` most needed help` part for everyone. But hopefully, we can still give some time if any attendee is really interested in helping. We gonna get more focus on what's the needs and how we can help to make progress of it, so it won't be like another BoF or Project update for you. Also, it's a forum so I won't give my hope to have a video recorder, which makes the second part more essential.
2. Update help most needed section in [1]. So anyone can understand what help you need. Also, TCs and UCs will have a better view of how group effort been working in the community and how community priority should be. Possibly and hopefully organizations/users/people might find matching their inner plan and sending people to help. Now if your group are willing to help with the forum, this action should be easy. And as I mention we're going to have a forum [4], It will be benefit to have such a document ready for anyone who's not coming to summit.
3. Is this needed suitable as a community goal [2]? Since we're also discussing community goal in #openstack-tc and ML, I think this might be a good chance to raise your needs into suggestion as our goal [2] if you find it fit with community goal definition.
As one of the Meta SIG chairs, I will try hard to make all SIG's life easier. So let me know if above action doesn't fit with your group or if you find it hard with making progress with your SIG mission.
[1] https://github.com/openstack/governance/blob/master/reference/help-most-need... [2] https://etherpad.openstack.org/p/community-goals [3] https://etherpad.openstack.org/p/expose-sigs-and-wgs [4] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23612/he... -- May The Force of OpenStack Be With You,
*Rico Lin*irc: ricolin
-- Chris Morgan <mihalis68@gmail.com>