[CentOS-devel] Is this the right channel to address the board?

After a chat with Karsten the repo is ok to live here: 'https://git.centos.org/centos/board'

-- 
 Brian Stinson
brian at bstinson.com



On Thu, May 21, 2020, at 06:16, Leigh Griffin wrote:
> 
> 
> On Wed, May 20, 2020 at 8:03 AM Karsten Wade <kwade at redhat.com> wrote:
>> Circling back on this, our Board discussion last week was fruitful 
>>  toward solving this.
>> 
>>  We'd like to use git.centos.org as an issue tracker for interacting with 
>>  the Board and for tracking our various efforts. We're moving from 
>>  largely manual processes, which we've been creating since the addition 
>>  of CentOS Stream made it necessary to re-consider CentOS as a 
>>  contributor project in need of active, visible leaders.
>> 
>>  What is the next step? I'm ready to build out the repo, figure out what 
>>  different personas need, and so on.
> 
> 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. 
>> 
>> Best,
>> 
>>  - Karsten
>> 
>>  On 5/13/20 2:43 AM, Aoife Moloney wrote:
>>  > 
>>  > 
>>  > On Wed, May 13, 2020 at 7:34 AM Leigh Griffin <lgriffin at redhat.com 
>>  > <mailto:lgriffin at redhat.com>> wrote:
>>  > 
>>  > 
>>  > 
>>  > On Tue, May 12, 2020, 23:54 Karsten Wade <kwade at redhat.com
>>  > <mailto:kwade at redhat.com>> wrote:
>>  > 
>>  > 
>>  > On 5/6/20 6:31 AM, Rich Bowen wrote:
>>  > > I must lead with this: It is with great trepidation that I
>>  > even write
>>  > > this message, because I have no desire to burn bridges. I
>>  > currently
>>  > > enjoy a cordial working relationship with everyone on the
>>  > board, and,
>>  > > without exception, have great respect for each of them
>>  > personally. But
>>  > > it is my job to point out that the board's method of engaging
>>  > with the
>>  > > community isn't working.
>>  > 
>>  > Thanks all for bringing this discussion along, we seem to have
>>  > arrived
>>  > at "yes and what tool." :) In parallel we need to have some idea
>>  > of the
>>  > personas of the people using this tool.
>>  > 
>>  > For some more context about Rich's email:
>>  > 
>>  > I asked Rich to start this thread when he asked me this
>>  > question. I said
>>  > then and here, it's true we do not have clear processes for getting
>>  > things heard and approved/denied by the Board.
>>  > 
>>  > As a Director and as the current Board Secretary, I am highly
>>  > interested
>>  > and somewhat desperate to solve those problems -- my task list
>>  > for the
>>  > Board and the Project is a bit unruly and dependent on other
>>  > humans to
>>  > move things along. The practice of open source software projects
>>  > reminds
>>  > us that I shouldn't be solving that problem in isolation, without
>>  > transparency and the collaboration that comes with it.
>>  > 
>>  > So let's work on it together. Let's figure out a reasonable
>>  > process that
>>  > will work right now, and iterate on it as needed over time.
>>  > 
>>  > There are a number of people who care about CentOS as a project,
>>  > let's
>>  > call them "project stakeholders". They all wish to engage with the
>>  > project leadership for guidance and approval around various efforts.
>>  > 
>>  > Can we use this thread to define those stakeholder personas,
>>  > what kinds
>>  > of things/ways they need to engage with the Board, and how we
>>  > can make
>>  > that happen?`
>>  > 
>>  > 
>>  > The CPE team is one such persona who need to engage with the Board
>>  > for key decisions and info sharing on technical projects we are
>>  > undertaking that might impact CentOS as a whole. We also want a 2
>>  > way conversation on requirements and needs that the Board, on behalf
>>  > of the Community, may wish for us to undertake e.g. service
>>  > creation/ modification. Actions here might impact the Community from
>>  > a technical or user interaction perspective so a public tracker is
>>  > key to allow transparency into the conversations.
>>  > 
>>  > 
>>  > I have a feeling there are some folks here experienced with helping
>>  > define functional requirements and user personas, you are hereby
>>  > invited
>>  > to help this discussion move forward.
>>  > 
>>  > 
>>  > My entire professional background is in this area, I'm happy to
>>  > help where my time will allow. I'm also happy to offer the services
>>  > of our Product Owner Aoife Moloney to help capture this who also
>>  > works in this manner day in day out.
>>  > 
>>  > 
>>  > +1, I'm more than happy to work out how best to engage with the CentOS 
>>  > Board from the CPE team side, with the board :) And any tooling/methods 
>>  > we identify as having potential success can also be scaled to allow for 
>>  > the wider project stakeholder groups to engage in this manner also & 
>>  > happy to use this thread as suggested for working this out with everyone 
>>  > collectively.
>>  > 
>>  > From the CPE side, we are a stakeholder to the CentOS Project and are 
>>  > happy to file requests/issues through a public tracker as mentioned 
>>  > above. If you opt to track through issues.redhat.com 
>>  > <http://issues.redhat.com>, or pagure.io <http://pagure.io>, creating 
>>  > labels to identify types of tickets will help the review process if the 
>>  > board only meets monthly.
>>  > You could honestly have labels for anything - hardware request, travel, 
>>  > new feature approval, etc. Continue to use the devel list for open 
>>  > discussion and feedback and by adding the link to your issue tracker in 
>>  > your email signature, there will be easy and quick access for people to 
>>  > file their request directly from conversational engagement on the email 
>>  > thread to a formal trackable request to the board to action.
>>  > 
>>  > I have ideas and am happy to help here, it benefits us all to have this 
>>  > clarity. So lets decide what tool first - does the board have a 
>>  > preference? You will be the ones using it! :)
>>  > 
>>  > 
>>  > Best regards,
>>  > 
>>  > - Karsten
>>  > --
>>  > Karsten Wade [he/him/his]| Senior Community Architect | @quaid
>>  > Red Hat Open Source Program Office (OSPO) : @redhatopen
>>  > https://community.redhat.com | https://next.redhat.com |
>>  > https://osci.io
>>  > https://theopensourceway.org |
>>  > https://github.com/theopensourceway/guide
>>  > 
>>  > _______________________________________________
>>  > CentOS-devel mailing list
>>  > CentOS-devel at centos.org <mailto:CentOS-devel at centos.org>
>>  > https://lists.centos.org/mailman/listinfo/centos-devel
>>  > 
>>  > _______________________________________________
>>  > CentOS-devel mailing list
>>  > CentOS-devel at centos.org <mailto:CentOS-devel at centos.org>
>>  > https://lists.centos.org/mailman/listinfo/centos-devel
>>  > 
>>  > 
>>  > 
>>  > -- 
>>  > 
>>  > Aoife Moloney
>>  > 
>>  > Product Owner
>>  > 
>>  > Community Platform Engineering Team
>>  > 
>>  > Red Hat EMEA <https://www.redhat.com>
>>  > 
>>  > Communications House
>>  > 
>>  > Cork Road
>>  > 
>>  > Waterford <mailto:Waterford>
>>  > 
>>  > <https://www.redhat.com>
>>  > 
>>  > 
>>  > _______________________________________________
>>  > CentOS-devel mailing list
>>  > CentOS-devel at centos.org
>>  > https://lists.centos.org/mailman/listinfo/centos-devel
>>  > 
>> 
>>  -- 
>>  Karsten Wade [he/him/his]| Senior Community Architect | @quaid
>>  Red Hat Open Source Program Office (OSPO) : @redhatopen
>> https://community.redhat.com | https://next.redhat.com | https://osci.io
>> https://theopensourceway.org | https://github.com/theopensourceway/guide
>> 
>>  _______________________________________________
>>  CentOS-devel mailing list
>> CentOS-devel at centos.org
>> https://lists.centos.org/mailman/listinfo/centos-devel
> 
> 
> -- 
> Leigh Griffin

> Engineering Manager

> Red Hat Waterford <https://www.redhat.com/>

> Communications House

> Cork Road, Waterford City

> lgriffin at redhat.com 
> M: +353877545162 IM: lgriffin

> @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> 
 <https://red.ht/sig>
> 
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel at centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20200528/f7666c1c/attachment-0002.html>