<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 20, 2020 at 8:03 AM Karsten Wade <<a href="mailto:kwade@redhat.com">kwade@redhat.com</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">Circling back on this, our Board discussion last week was fruitful <br>
toward solving this.<br>
<br>
We'd like to use <a href="http://git.centos.org" rel="noreferrer" target="_blank">git.centos.org</a> as an issue tracker for interacting with <br>
the Board and for tracking our various efforts. We're moving from <br>
largely manual processes, which we've been creating since the addition <br>
of CentOS Stream made it necessary to re-consider CentOS as a <br>
contributor project in need of active, visible leaders.<br>
<br>
What is the next step? I'm ready to build out the repo, figure out what <br>
different personas need, and so on.<br></blockquote><div><br></div><div>Is the intention here we just log an issue and it becomes a conversation topic? That's my interpretation of this, if that's the case, we just need the actual repo created and it works organically from there. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Best,<br>
<br>
- Karsten<br>
<br>
On 5/13/20 2:43 AM, Aoife Moloney wrote:<br>
> <br>
> <br>
> On Wed, May 13, 2020 at 7:34 AM Leigh Griffin <<a href="mailto:lgriffin@redhat.com" target="_blank">lgriffin@redhat.com</a> <br>
> <mailto:<a href="mailto:lgriffin@redhat.com" target="_blank">lgriffin@redhat.com</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On Tue, May 12, 2020, 23:54 Karsten Wade <<a href="mailto:kwade@redhat.com" target="_blank">kwade@redhat.com</a><br>
> <mailto:<a href="mailto:kwade@redhat.com" target="_blank">kwade@redhat.com</a>>> wrote:<br>
> <br>
> <br>
> On 5/6/20 6:31 AM, Rich Bowen wrote:<br>
> > I must lead with this: It is with great trepidation that I<br>
> even write<br>
> > this message, because I have no desire to burn bridges. I<br>
> currently<br>
> > enjoy a cordial working relationship with everyone on the<br>
> board, and,<br>
> > without exception, have great respect for each of them<br>
> personally. But<br>
> > it is my job to point out that the board's method of engaging<br>
> with the<br>
> > community isn't working.<br>
> <br>
> Thanks all for bringing this discussion along, we seem to have<br>
> arrived<br>
> at "yes and what tool." :) In parallel we need to have some idea<br>
> of the<br>
> personas of the people using this tool.<br>
> <br>
> For some more context about Rich's email:<br>
> <br>
> I asked Rich to start this thread when he asked me this<br>
> question. I said<br>
> then and here, it's true we do not have clear processes for getting<br>
> things heard and approved/denied by the Board.<br>
> <br>
> As a Director and as the current Board Secretary, I am highly<br>
> interested<br>
> and somewhat desperate to solve those problems -- my task list<br>
> for the<br>
> Board and the Project is a bit unruly and dependent on other<br>
> humans to<br>
> move things along. The practice of open source software projects<br>
> reminds<br>
> us that I shouldn't be solving that problem in isolation, without<br>
> transparency and the collaboration that comes with it.<br>
> <br>
> So let's work on it together. Let's figure out a reasonable<br>
> process that<br>
> will work right now, and iterate on it as needed over time.<br>
> <br>
> There are a number of people who care about CentOS as a project,<br>
> let's<br>
> call them "project stakeholders". They all wish to engage with the<br>
> project leadership for guidance and approval around various efforts.<br>
> <br>
> Can we use this thread to define those stakeholder personas,<br>
> what kinds<br>
> of things/ways they need to engage with the Board, and how we<br>
> can make<br>
> that happen?`<br>
> <br>
> <br>
> The CPE team is one such persona who need to engage with the Board<br>
> for key decisions and info sharing on technical projects we are<br>
> undertaking that might impact CentOS as a whole. We also want a 2<br>
> way conversation on requirements and needs that the Board, on behalf<br>
> of the Community, may wish for us to undertake e.g. service<br>
> creation/ modification. Actions here might impact the Community from<br>
> a technical or user interaction perspective so a public tracker is<br>
> key to allow transparency into the conversations.<br>
> <br>
> <br>
> I have a feeling there are some folks here experienced with helping<br>
> define functional requirements and user personas, you are hereby<br>
> invited<br>
> to help this discussion move forward.<br>
> <br>
> <br>
> My entire professional background is in this area, I'm happy to<br>
> help where my time will allow. I'm also happy to offer the services<br>
> of our Product Owner Aoife Moloney to help capture this who also<br>
> works in this manner day in day out.<br>
> <br>
> <br>
> +1, I'm more than happy to work out how best to engage with the CentOS <br>
> Board from the CPE team side, with the board :) And any tooling/methods <br>
> we identify as having potential success can also be scaled to allow for <br>
> the wider project stakeholder groups to engage in this manner also & <br>
> happy to use this thread as suggested for working this out with everyone <br>
> collectively.<br>
> <br>
> From the CPE side, we are a stakeholder to the CentOS Project and are <br>
> happy to file requests/issues through a public tracker as mentioned <br>
> above. If you opt to track through <a href="http://issues.redhat.com" rel="noreferrer" target="_blank">issues.redhat.com</a> <br>
> <<a href="http://issues.redhat.com" rel="noreferrer" target="_blank">http://issues.redhat.com</a>>, or <a href="http://pagure.io" rel="noreferrer" target="_blank">pagure.io</a> <<a href="http://pagure.io" rel="noreferrer" target="_blank">http://pagure.io</a>>, creating <br>
> labels to identify types of tickets will help the review process if the <br>
> board only meets monthly.<br>
> You could honestly have labels for anything - hardware request, travel, <br>
> new feature approval, etc. Continue to use the devel list for open <br>
> discussion and feedback and by adding the link to your issue tracker in <br>
> your email signature, there will be easy and quick access for people to <br>
> file their request directly from conversational engagement on the email <br>
> thread to a formal trackable request to the board to action.<br>
> <br>
> I have ideas and am happy to help here, it benefits us all to have this <br>
> clarity. So lets decide what tool first - does the board have a <br>
> preference? You will be the ones using it! :)<br>
> <br>
> <br>
> Best regards,<br>
> <br>
> - Karsten<br>
> --<br>
> Karsten Wade [he/him/his]| Senior Community Architect | @quaid<br>
> Red Hat Open Source Program Office (OSPO) : @redhatopen<br>
> <a href="https://community.redhat.com" rel="noreferrer" target="_blank">https://community.redhat.com</a> | <a href="https://next.redhat.com" rel="noreferrer" target="_blank">https://next.redhat.com</a> |<br>
> <a href="https://osci.io" rel="noreferrer" target="_blank">https://osci.io</a><br>
> <a href="https://theopensourceway.org" rel="noreferrer" target="_blank">https://theopensourceway.org</a> |<br>
> <a href="https://github.com/theopensourceway/guide" rel="noreferrer" target="_blank">https://github.com/theopensourceway/guide</a><br>
> <br>
> _______________________________________________<br>
> CentOS-devel mailing list<br>
> <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a>><br>
> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
> <br>
> _______________________________________________<br>
> CentOS-devel mailing list<br>
> <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a>><br>
> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
> <br>
> <br>
> <br>
> -- <br>
> <br>
> Aoife Moloney<br>
> <br>
> Product Owner<br>
> <br>
> Community Platform Engineering Team<br>
> <br>
> Red Hat EMEA <<a href="https://www.redhat.com" rel="noreferrer" target="_blank">https://www.redhat.com</a>><br>
> <br>
> Communications House<br>
> <br>
> Cork Road<br>
> <br>
> Waterford <mailto:<a href="mailto:Waterford" target="_blank">Waterford</a>><br>
> <br>
> <<a href="https://www.redhat.com" rel="noreferrer" target="_blank">https://www.redhat.com</a>><br>
> <br>
> <br>
> _______________________________________________<br>
> CentOS-devel mailing list<br>
> <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
> <br>
<br>
-- <br>
Karsten Wade [he/him/his]| Senior Community Architect | @quaid<br>
Red Hat Open Source Program Office (OSPO) : @redhatopen<br>
<a href="https://community.redhat.com" rel="noreferrer" target="_blank">https://community.redhat.com</a> | <a href="https://next.redhat.com" rel="noreferrer" target="_blank">https://next.redhat.com</a> | <a href="https://osci.io" rel="noreferrer" target="_blank">https://osci.io</a><br>
<a href="https://theopensourceway.org" rel="noreferrer" target="_blank">https://theopensourceway.org</a> | <a href="https://github.com/theopensourceway/guide" rel="noreferrer" target="_blank">https://github.com/theopensourceway/guide</a><br>
<br>
_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:capitalize"><span>Leigh</span> <span>Griffin</span></p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:12px;margin:0px;text-transform:capitalize"><span>Engineering Manager</span></p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;margin:0px 0px 4px;font-size:12px"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat <span>Waterford</span></a></p><div style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-bottom:4px"><span><p style="font-size:12px;margin:0px">Communications House</p></span><span><p style="font-size:12px;margin:0px">Cork Road, Waterford City</p></span></div><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;margin:0px;font-size:12px"><span style="margin:0px;padding:0px"><a href="mailto:lgriffin@redhat.com" style="color:rgb(0,0,0);margin:0px" target="_blank">lgriffin@redhat.com</a> </span> <span><br>M: <a href="tel:+353877545162" style="color:rgb(0,0,0);margin:0px" target="_blank">+353877545162</a> </span> <span>IM: <span>lgriffin</span></span></p><div style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:12px;margin-bottom:8px"><div><a href="https://twitter.com/redhatjobs" title="twitter" style="background:url("https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/3780bd4ede961ef3cd4108b8c0e80186/web-icon-twitter.png") 0px 50%/13px no-repeat transparent;color:rgb(0,0,0);display:inline-block;line-height:20px;padding-left:12px" target="_blank"><span style="margin-left:2px">@redhatjobs</span></a> <a href="https://www.facebook.com/redhatjobs" title="Facebook" style="background:url("https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/220b85e2f100025e94cb1bcd993bd51d/web-icon-facebook.png") 0px 50%/11px no-repeat transparent;color:rgb(0,0,0);display:inline-block;line-height:20px;padding-left:13px" target="_blank"><span>redhatjobs</span></a> <a href="https://instagram.com/redhatjobs" title="instagram" style="background:url("https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/54485ca6f22795449a0d650524e55f62/web-icon-instagram.png") 0px 50%/11px no-repeat transparent;color:rgb(0,0,0);display:inline-block;line-height:20px;padding-left:11px;margin-left:8px;padding-bottom:1px" target="_blank"><span style="margin-left:4px">@redhatjobs</span></a> </div></div><div style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-top:12px"><table border="0"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"><img src="https://static.redhat.com/libs/redhat/brand-assets/latest/corp/logo.png" width="90" height="auto"></a></td></tr></tbody></table></div><div style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px"></div></div></div></div></div></div></div></div></div></div></div></div>