Re: Minutes of the GNOME Foundation Board meeting of 12 October 2020
Philip Chimento via foundation-announce <[email protected]> Thu, 14 Jan 2021 14:39:21 -0800
| Newsgroups | gmane.comp.gnome.foundation.announce |
|---|---|
| Message-ID | <CAHbXgc3h0Z+8B8sSNum+osrBG7KfUnkhCqxqdMoCpS9U752+=w@mail.gmail.com> |
--===============6729743933046564944== Content-Type: multipart/alternative; boundary="000000000000f2a7d705b8e3ed64" --000000000000f2a7d705b8e3ed64 Content-Type: text/plain; charset="UTF-8" Re-sending this to the list due to a technical problem. On Tue, Nov 17, 2020 at 10:57 AM Philip Chimento <[email protected]> wrote: > Wiki location: https://wiki.gnome.org/FoundationBoard/Minutes/20201012 > > = Regular meeting of the GNOME Foundation Board of Directors, 12 October > 2020, 15:00 UTC = > > == Attending == > > Directors: > * FedericoMenaQuintero > * KatGerasimova > * RobertMcQueen > * AllanDay > * FelipeBorges > * PhilipChimento > > Non-directors: > * ShaunMcCance > * RosannaYuen > * NeilMcGovern > * GarethMarlow > > == Regrets == > > * ReginaNkemchorAdejo > > == Discussion agenda == > > * Status of secretarial duties > * Review monthly meeting cadence > * Review in-progress tickets > * Strategy discussion > * Review progress so far > * Introduction to OKRs > * Discussion: mission, vision, objectives > > == Minutes == > > * Status of secretarial duties > * Backlog has been published. > * Kat: can we reduce approval time? > * Philip: current process was designed when we had weekly meetings. > * Kat to start an issue in GitLab to review the process. > > * Review monthly meeting cadence > * https://gitlab.gnome.org/Teams/Board/-/issues/184 > * Kat: it's harder to keep track of everything with monthly meetings > than it had been with weekly or fortnightly meetings. > * Rob: is Neil getting enough feedback/communication from the board? > * Neil: monthly meetings work well in terms of communication from the > board. Anything else can be followed up by email > * Rob: from my perspective, enjoying the reduced time commitment and > increased focus, but too soon to say whether it's working well enough for > the Foundation. need to keep an eye on reporting to ensure that Board (and > wider community) has visibility to ongoing initiatives. > * Kat: the new format does work well to make sure we don't let longer > term plans fall through the cracks > * Allan: structure works well, but we're lacking content. We are seeing > a drop in activities that individual directors are leading. We need to make > sure that we are delegating more and letting board members lead initiatives. > * Philip: Can we plan the dates of the year's meetings in advance? > * Allan: They are always the second Monday of the month. I'll send a > list around. > > * Review in-progress tickets > * Follow up on mailing list. > > [Shaun leaves] > > * Strategy discussion > * Allan reviews progress so far > * Introduction to OKRs > * Rob: a measurable way of tracking goals by using initiatives with > measurable key results to achieve objectives set as part of the strategy. > Activities which support the Foundation's objectives can then be handed out > to teams/employees. > * Discussion: mission, vision, objectives > * Gareth: I helped the board work through some of the strategy > brainstorming in February. Executive coach. Help people with culture, > mission, vision, etc. > * Round table on Vision and Mission statements: > * Federico: Drop "promote" from vision statement. Maybe we should > include making it financially attractive to develop for GNOME. > * Felipe: Great that we are adopting a framework to have these > conversations. Important to address "sustainability" > * Kat: This is a concrete way to set out actions/initiatives which > will help us achieve our objectives. > * Philip: Feel that it's a reversal of ownership of goals (the board > was hands off previously regarding implementation) and it's a good process > to arrive at goals. > * Rob: This will give Neil a more opinionated steer from the board > which will help Neil set out how we will achieve our objectives. > * Gareth: board needs to hand over a set of outcomes to Neil and Neil > can then return to the board with a set of actions that can be taken to get > there which the board can then approve. > * Allan: "respects and empowers" in the vision statement could > benefit from a bit of work. We should look at this more from an ecosystem > point of view rather than a platform. Is the mission too insular? And is > "access" sufficient - do we not want to address appeal and desirability too? > * Neil: it is important that the board owns this top level > initiative. Mission statement - feels wordy and long, addressing community > and ecosystem. It would be useful to have sustainability in there too, but > not sure how to fit three concepts in there. > * Gareth: it needs to be a focus that's kept in mind so it doesn't > become just a statement on the website. You could add the concept of > sustainability without making it too wordy. > * Rob: "<VERB> a diverse and sustainable ecosystem around free > software desktop and applications." > * Federico: how can we improve feedback loop from users who customise > the software to be useful for them and upstream? How to make it easier for > those people to contribute? Should this process be central to the mission > statement, or a second-level objective? > * Gareth: Is this already established in the fact that this is Free > Software? > * Federico: Rust community makes these contributions more visible. > The process is GNOME is very informal in comparison and not well defined. > * Rob: if we're inclusive, we end up with diversity. Diversity and > inclusion are mission-level goals, and we should go into more details in > the objectives. > * Objective suggestions: > * Rob: inclusive contribution process with financial > incentive/compensation > * Philip: take it broader. Allow people to participate regardless > of employment/free time status. > * Philip: getting our accessibility back to top notch. > * Kat: make it easy for anyone to contribute > * Felipe: produce an ecosystem that respects user privacy > * Federico: always have excellent development documentation > * Allan: have an inspiring and attractive public image > * Rob: sustainable and well run foundation / invest in channels to > grow user base > * Philip: stay competitive with cutting edge technology from > proprietary tech > * Felipe: continue to catalyse projects and new technologies > * Federico: have a pulse on how people move around with regards to > joining/leaving the project > * Allan: be in a place where we are aware of and tackle structural > issues that we and similar projects face > * Allan: engage employers - both existing and new potential ones > * Kat: be versatile enough to be engaging to a diverse community > * Gareth: Some of the above are more end points/outcomes and some > initiatives. Sort list into outcome/tasks. If tasks are not connected to an > outcome, rewrite it. > * Allan: who will do what/when? > * Rob: working group to refine the objectives. Endless have offered to > use some of their funds towards this. Get some perspective from the > industry outside the Free Software community. > * Rob will take on the task of agreeing an ultimate objective with the > board. > * Allan: bring this into every monthly call until it is defined to keep > the momentum up? > * Felipe and Kat interested in joining the working group to refine > objectives > [Rob leaves] > * Kat to set up call for working group (Allan will join too) > * Allan: working group should aim to report back at next month's meeting > * Gareth: good idea to use the monthly call to get the vision and > mission finished. > > == Notices == > > Next meeting will be 9th November 2020, 15:00 - 17:00 UTC. We will have a > quarterly finance meeting, including a finance report. > > -- Philip --000000000000f2a7d705b8e3ed64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">Re-sending this to the list due to a tech= nical problem.<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla= ss=3D"gmail_attr">On Tue, Nov 17, 2020 at 10:57 AM Philip Chimento <<a h= ref=3D"mailto:[email protected]">[email protected]</a>> = wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0= px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir= =3D"ltr"><div>Wiki location: <a href=3D"https://wiki.gnome.org/FoundationBo= ard/Minutes/20201012" target=3D"_blank">https://wiki.gnome.org/FoundationBo= ard/Minutes/20201012</a></div><div><br></div><div>=3D Regular meeting of th= e GNOME Foundation Board of Directors, 12 October 2020, 15:00 UTC =3D</div>= <br>=3D=3D Attending =3D=3D<br><br>Directors:<br>=C2=A0* FedericoMenaQuinte= ro<br>=C2=A0* KatGerasimova<br>=C2=A0* RobertMcQueen<br>=C2=A0* AllanDay<br= >=C2=A0* FelipeBorges<br>=C2=A0* PhilipChimento<br><br>Non-directors:<br>= =C2=A0* ShaunMcCance<br>=C2=A0* RosannaYuen<br>=C2=A0* NeilMcGovern<br>=C2= =A0* GarethMarlow<br><br>=3D=3D Regrets =3D=3D<br><br>=C2=A0* ReginaNkemcho= rAdejo<br><br>=3D=3D Discussion agenda =3D=3D<br><br>=C2=A0* Status of secr= etarial duties<br>=C2=A0* Review monthly meeting cadence<br>=C2=A0* Review = in-progress tickets<br>=C2=A0* Strategy discussion<br>=C2=A0 * Review progr= ess so far<br>=C2=A0 * Introduction to OKRs<br>=C2=A0 * Discussion: mission= , vision, objectives<br><br>=3D=3D Minutes =3D=3D<br><br>=C2=A0* Status of = secretarial duties<br>=C2=A0 =C2=A0* Backlog has been published.<br>=C2=A0 = =C2=A0* Kat: can we reduce approval time?<br>=C2=A0 =C2=A0* Philip: current= process was designed when we had weekly meetings.<br>=C2=A0 =C2=A0* Kat to= start an issue in GitLab to review the process.<br><br>=C2=A0* Review mont= hly meeting cadence<br>=C2=A0 =C2=A0* <a href=3D"https://gitlab.gnome.org/T= eams/Board/-/issues/184" target=3D"_blank">https://gitlab.gnome.org/Teams/B= oard/-/issues/184</a><br>=C2=A0 =C2=A0* Kat: it's harder to keep track = of everything with monthly meetings than it had been with weekly or fortnig= htly meetings.<br>=C2=A0 =C2=A0* Rob: is Neil getting enough feedback/commu= nication from the board?<br>=C2=A0 =C2=A0* Neil: monthly meetings work well= in terms of communication from the board. Anything else can be followed up= by email<br>=C2=A0 =C2=A0* Rob: from my perspective, enjoying the reduced = time commitment and increased focus, but too soon to say whether it's w= orking well enough for the Foundation. need to keep an eye on reporting to = ensure that Board (and wider community) has visibility to ongoing initiativ= es.<br>=C2=A0 =C2=A0* Kat: the new format does work well to make sure we do= n't let longer term plans fall through the cracks<br>=C2=A0 =C2=A0* All= an: structure works well, but we're lacking content. We are seeing a dr= op in activities that individual directors are leading. We need to make sur= e that we are delegating more and letting board members lead initiatives.<b= r>=C2=A0 =C2=A0* Philip: Can we plan the dates of the year's meetings i= n advance?<br>=C2=A0 =C2=A0* Allan: They are always the second Monday of th= e month. I'll send a list around.<br><br>=C2=A0* Review in-progress tic= kets<br>=C2=A0 =C2=A0* Follow up on mailing list.<br><br>[Shaun leaves]<br>= <br>=C2=A0* Strategy discussion<br>=C2=A0 =C2=A0* Allan reviews progress so= far<br>=C2=A0 =C2=A0* Introduction to OKRs<br>=C2=A0 =C2=A0 =C2=A0* Rob: a= measurable way of tracking goals by using initiatives with measurable key = results to achieve objectives set as part of the strategy. Activities which= support the Foundation's objectives can then be handed out to teams/em= ployees.<br>=C2=A0 =C2=A0* Discussion: mission, vision, objectives<br>=C2= =A0 =C2=A0 =C2=A0* Gareth: I helped the board work through some of the stra= tegy brainstorming in February. Executive coach. Help people with culture, = mission, vision, etc.<br>=C2=A0 =C2=A0 =C2=A0* Round table on Vision and Mi= ssion statements:<br>=C2=A0 =C2=A0 =C2=A0* Federico: Drop "promote&quo= t; from vision statement. Maybe we should include making it financially att= ractive to develop for GNOME.<br>=C2=A0 =C2=A0 =C2=A0* Felipe: Great that w= e are adopting a framework to have these conversations. Important to addres= s "sustainability"<br>=C2=A0 =C2=A0 =C2=A0* Kat: This is a concre= te way to set out actions/initiatives which will help us achieve our object= ives.<br>=C2=A0 =C2=A0 =C2=A0* Philip: Feel that it's a reversal of own= ership of goals (the board was hands off previously regarding implementatio= n) and it's a good process to arrive at goals.<br>=C2=A0 =C2=A0 =C2=A0*= Rob: This will give Neil a more opinionated steer from the board which wil= l help Neil set out how we will achieve our objectives.<br>=C2=A0 =C2=A0 = =C2=A0* Gareth: board needs to hand over a set of outcomes to Neil and Neil= can then return to the board with a set of actions that can be taken to ge= t there which the board can then approve.<br>=C2=A0 =C2=A0 =C2=A0* Allan: &= quot;respects and empowers" in the vision statement could benefit from= a bit of work. We should look at this more from an ecosystem point of view= rather than a platform. Is the mission too insular? And is "access&qu= ot; sufficient - do we not want to address appeal and desirability too?<br>= =C2=A0 =C2=A0 =C2=A0* Neil: it is important that the board owns this top le= vel initiative. Mission statement - feels wordy and long, addressing commun= ity and ecosystem. It would be useful to have sustainability in there too, = but not sure how to fit three concepts in there.<br>=C2=A0 =C2=A0 =C2=A0* G= areth: it needs to be a focus that's kept in mind so it doesn't bec= ome just a statement on the website. You could add the concept of sustainab= ility without making it too wordy.<br>=C2=A0 =C2=A0 =C2=A0* Rob: "<= VERB> a diverse and sustainable ecosystem around free software desktop a= nd applications."<br>=C2=A0 =C2=A0 =C2=A0* Federico: how can we improv= e feedback loop from users who customise the software to be useful for them= and upstream? How to make it easier for those people to contribute? Should= this process be central to the mission statement, or a second-level object= ive?<br>=C2=A0 =C2=A0 =C2=A0* Gareth: Is this already established in the fa= ct that this is Free Software?<br>=C2=A0 =C2=A0 =C2=A0* Federico: Rust comm= unity makes these contributions more visible. The process is GNOME is very = informal in comparison and not well defined.<br>=C2=A0 =C2=A0 =C2=A0* Rob: = if we're inclusive, we end up with diversity. Diversity and inclusion a= re mission-level goals, and we should go into more details in the objective= s.<br>=C2=A0 =C2=A0* Objective suggestions:<br>=C2=A0 =C2=A0 =C2=A0* Rob: i= nclusive contribution process with financial incentive/compensation<br>=C2= =A0 =C2=A0 =C2=A0 =C2=A0* Philip: take it broader. Allow people to particip= ate regardless of employment/free time status.<br>=C2=A0 =C2=A0 =C2=A0* Phi= lip: getting our accessibility back to top notch. <br>=C2=A0 =C2=A0 =C2=A0*= Kat: make it easy for anyone to contribute<br>=C2=A0 =C2=A0 =C2=A0* Felipe= : produce an ecosystem that respects user privacy<br>=C2=A0 =C2=A0 =C2=A0* = Federico: always have excellent development documentation<br>=C2=A0 =C2=A0 = =C2=A0* Allan: have an inspiring and attractive public image<br>=C2=A0 =C2= =A0 =C2=A0* Rob: sustainable and well run foundation / invest in channels t= o grow user base<br>=C2=A0 =C2=A0 =C2=A0* Philip: stay competitive with cut= ting edge technology from proprietary tech<br>=C2=A0 =C2=A0 =C2=A0* Felipe:= continue to catalyse projects and new technologies<br>=C2=A0 =C2=A0 =C2=A0= * Federico: have a pulse on how people move around with regards to joining/= leaving the project<br>=C2=A0 =C2=A0 =C2=A0* Allan: be in a place where we = are aware of and tackle structural issues that we and similar projects face= <br>=C2=A0 =C2=A0 =C2=A0* Allan: engage employers - both existing and new p= otential ones<br>=C2=A0 =C2=A0 =C2=A0* Kat: be versatile enough to be engag= ing to a diverse community<br>=C2=A0 =C2=A0* Gareth: Some of the above are = more end points/outcomes and some initiatives. Sort list into outcome/tasks= . If tasks are not connected to an outcome, rewrite it. <br>=C2=A0 =C2=A0* = Allan: who will do what/when?<br>=C2=A0 =C2=A0* Rob: working group to refin= e the objectives. Endless have offered to use some of their funds towards t= his. Get some perspective from the industry outside the Free Software commu= nity.<br>=C2=A0 =C2=A0* Rob will take on the task of agreeing an ultimate o= bjective with the board.<br>=C2=A0 =C2=A0* Allan: bring this into every mon= thly call until it is defined to keep the momentum up?<br>=C2=A0 =C2=A0* Fe= lipe and Kat interested in joining the working group to refine objectives<b= r>[Rob leaves]<br>=C2=A0 =C2=A0* Kat to set up call for working group (Alla= n will join too)<br>=C2=A0 =C2=A0* Allan: working group should aim to repor= t back at next month's meeting<br>=C2=A0 =C2=A0* Gareth: good idea to u= se the monthly call to get the vision and mission finished.<br><br>=3D=3D N= otices =3D=3D<br><br>Next meeting will be 9th November 2020, 15:00 - 17:00 = UTC. We will have a quarterly finance meeting, including a finance report.<= br><br></div> </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g= mail_signature">Philip</div></div> --000000000000f2a7d705b8e3ed64-- --===============6729743933046564944== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ foundation-announce mailing list [email protected] https://mail.gnome.org/mailman/listinfo/foundation-announce --===============6729743933046564944==--