<div dir="ltr"><div dir="ltr">I definitely like the idea of a pop-up team in the house.<div><br></div><div>I also tend to agree with the opinion about visibility for a pop-up team.</div><div>We definitely need something with quick workflow. And allow people directly start communicate and working on the goal.</div><div><br></div><div>Here's what I think we should do in advance.</div><div><br></div><div>1. To clear ways that we have to trigger cross-project development. To clear the path and to document.</div><div><br></div><div>People have been trying a few formats to work on cross-project spec. After time, some prove useful and gaining momentum on the way. And some getting less.</div><div>But we never try to stop at a point and declare what's the way we should do cross-project. And I'm pretty sure that's very confused for a lot of people who might not always as a part of this community. To give official recognition for ways that we think will cover the patch, and to officially announce the unofficial for methods (which we might already done with in ML/Meeting, but it's worth to bringing it to a more visible place.).</div><div>And most importantly to have it documented in our develop guidelines, so message we send will be crystal clear for all of us all the time.</div><div><br></div><div>If we can keep broadcast around and tell people how they can set-up for their requirement, than we actually get better chance to have more people trying the right way of engage with us and give really useful feedback.</div><div><br></div><div>IMO, to use SIG as long-term (and repository demanded) path, and have a pop-up team for short term trace sounds like a fully covered for me. </div><div><br></div><div> 2. Remove annoying channels.<br></div><div>I like the idea if only use a single irc channel to communicate for multiple purpose</div><div><br></div><div>I feel the lack of time to work through multiple channels and in multiple communities. Which is really annoying.</div><div>So if we can have a general irc channel like openstack-dev, and allow popup-teams move to specific irc channel if they see fit. To consider have better visibility, a single channel for multiple team cores and leads to be awarded of some pop-up works will definitely a benefit. I mean, how many people actually capable to trace that much channel dally and happen to have time to join development? Isn't that's why we comes up with `openstack-discussion` for most mail to be in place? The down side is that we didn't have tag filter for irc. but that's also a good thing to actually know about works for pop-up teams.</div><div><br></div><div>3. Gaining visibility and official blessing</div><div>As agree on comments about gaining visibility, a session for all SIGs and pop-up teams to shout out and raise their own most wanted help out.</div><div>We can do it in one single session and give 3-5 minutes for each team. Any one also feel this is a good idea too?</div><div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 14, 2019 at 9:15 PM Thierry Carrez <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Adam Spiers wrote:<br>
> Ildiko Vancsa <<a href="mailto:ildiko.vancsa@gmail.com" target="_blank">ildiko.vancsa@gmail.com</a>> wrote:<br>
>>> On 2019. Feb 11., at 23:26, Adam Spiers <<a href="mailto:aspiers@suse.com" target="_blank">aspiers@suse.com</a>> wrote: <br>
>>> [snip…]<br>
>>><br>
>>>> To help with all this I would start the experiment with wiki pages <br>
>>>> and etherpads as these are all materials you can point to without <br>
>>>> too much formality to follow so the goals, drivers, supporters and <br>
>>>> progress are visible to everyone who’s interested and to the TC to <br>
>>>> follow-up on.<br>
>>>> Do we expect an approval process to help with or even drive either <br>
>>>> of the crucial steps I listed above? <br>
>>><br>
>>> I'm not sure if it would help. But I agree that visibility is <br>
>>> important, and by extension also discoverability. To that end I <br>
>>> think it would be worth hosting a central list of popup initiatives <br>
>>> somewhere which links to the available materials for each initiative. <br>
>>> Maybe it doesn't matter too much whether that central list is simply <br>
>>> a wiki page or a static web page managed by Gerrit under a governance <br>
>>> repo or similar. <br>
>><br>
>> I would start with a wiki page as it stores history as well and it’s <br>
>> easier to edit. Later on if we feel the need to be more formal we can <br>
>> move to a static web page and use Gerrit. <br>
> <br>
> Sounds good to me. Do we already have some popup teams? If so we could <br>
> set this up straight away.<br>
<br>
To continue this discussion, I just set up a basic page with an example <br>
team at:<br>
<br>
<a href="https://wiki.openstack.org/wiki/Popup_Teams" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Popup_Teams</a><br>
<br>
Feel free to improve the description and example entry.<br>
<br>
-- <br>
Thierry Carrez (ttx)<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="background-image:none"><div style="font-size:small"><div><table border="0" cellpadding="0" cellspacing="0" style="color:rgb(0,0,0);font-size:medium;font-family:verdana"><tbody><tr><td colspan="3" align="left" valign="center"><span style="font-size:13px;font-family:verdana">May The Force of Open<font color="#ff0000">Stack</font> Be With You,</span> <br><b><i><font face="georgia, serif" size="4">Rico Lin<br></font></i></b>irc: ricolin</td></tr><tr><td colspan="3" align="left" valign="center" style="height:10px;border-bottom:1px dashed rgb(221,221,221)"></td></tr><tr><td colspan="3"></td></tr></tbody></table><br></div></div></div><font size="2" face="tahoma, sans-serif" color="#999999"></font></div></div></div></div></div></div></div></div></div></div>