Minutes of the board meeting of June 22, 2020
Ekaterina Gerasimova <[email protected]> Sat, 11 Jul 2020 09:17:59 +0100
| Newsgroups | gmane.comp.gnome.foundation.announce |
|---|---|
| Message-ID | <CAM2D-RqyWihmGkCqKZAyL1ub2gvunF7SCC00_nB9PKR74Rm3pA@mail.gmail.com> |
--===============8577860266513485029==
Content-Type: multipart/alternative; boundary="00000000000020eb7a05aa2619a2"
--00000000000020eb7a05aa2619a2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Wiki location: https://wiki.gnome.org/FoundationBoard/Minutes/20200622
=3D Meeting of the GNOME Foundation Board of Directors, 22 June 2020, 14:30
UTC =3D
=3D=3D Attending =3D=3D
* TristanVanBerkom
* FedericoMenaQuintero
* AllanDay
* CarlosSoriano
* NeilMcGovern
* PhilipChimento
* RosannaYuen
* RobertMcQueen
=3D=3D Regrets =3D=3D
* BrittYazel
=3D=3D Agenda =3D=3D
* Approve minutes of 8 June
* GNOME software definition & GNOME Circle initiative
* Board handover arrangements
=3D=3D Minutes =3D=3D
* Approve minutes of 8 June
* Philip: There is a domain name mentioned in the minutes that the
Foundation would potentially purchase.
* We decide to redact it so that it doesn't get scooped.
* No other changes were submitted.
* Minutes are approved, pending the above correction.
* GNOME software definition & GNOME Circle initiative
* Allan: This has been a long-standing item and I'm glad to be finishing
it up. We've discussed these before, so I'll just go through what's new.
The first item is the release team becoming a committee. We decided to
stick to the bare essentials for the release team committee's charter, just
covering the trademark issue where the board devolves the power to decide
what is GNOME and what can use the Foundation's trademarks to the release
team committee. The draft charter is at
https://gitlab.gnome.org/Teams/Board/-/issues/166
* Tristan: While it is all about the Foundation's trademarks, we don't
mention trademarks in the charter. Should we?
* Carlos: I don't think so. This seems like a policy implementation
detail that the board is still responsible for. The board just needs to
keep in touch with the release team about the requirements for the
trademark.
* Tristan: I agree, but I think it should be documented somewhere.
* Allan: The trademark policy is part of the last item in the slate
we'll be voting on.
* Allan: The GNOME Circle committee has a draft charter at
https://gitlab.gnome.org/Teams/Board/-/issues/167 I'm volunteering myself
for the committee as well, to help bootstrap it. As we've discussed, this
affects who can become a member of the Foundation.
* Allan: The last item is the policy on official GNOME software, the
draft of which is at https://gitlab.gnome.org/Teams/Board/-/issues/165. The
domain name has been removed from the policy since we haven't resolved that
question yet.
* Tristan: You had already sent an announcement for what would be under
the remit of these committees, correct?
* Allan: The announcement was published on Discourse, but as a
proposal.
* Tristan: So what is our vote on today? To create the committees,
make the proposal into a policy, and point the committees to it?
* Allan: That's a good question. The release team's activities don't
change, but there will of course be a transition period where the GNOME
Circle committee is bootstrapped and the infrastructure for the GNOME
Circle is created on !GitLab. In practice, if there are difficulties with
the implementation, then they will take it back to the board to amend the
policy.
* Tristan: My point is that the original proposal for these committees
had a lot more detail. Do the committees know what is expected of them?
What if the implementation turns out to be different from our intention?
* Carlos: I agree, but I think the answer is that we need to
anticipate that by being in a close loop with the GNOME Circle committee
during the bootstrap period, not by making the charter more detailed.
* Allan: In practice, we do the same with other committees, we can
make course adjustments.
* Allan: The part about projects with an existing fiscal sponsor has
been removed, because it turned out to be confusing in the proposal. We
intend to leave this up to the committee's discretion.
* Rob: Fiscal sponsorship is a nonprofit term of art, so although it
may not communicate very well because people might not know what it is, it
is unambiguous. I do think it's important to specify it.
* Tristan: It would be odd for a project to be both a GNOME Circle and
an Apache project, for example.
* Allan: We could add this back to the GNOME Circle committee charter,
and I don't think it would be that confusing, because projects looking to
apply would be looking at a more user-friendly description.
* Carlos: I agree, we can include this guideline and the committee can
discuss with the board if they want to deviate from it.
* Rob: We do need to be intentional that the GNOME Circle projects
further the GNOME mission, because being in the GNOME Circle affects how
the Foundation's budget is spent.
* Neil: The expectation would be that if a GNOME Circle project became
big, then they would move to full fiscal sponsorship.
* Rob: I think we should add a non-normative statement: "It is
intended that projects seeking membership of GNOME Circle are not already
members of another non-profit fiscal sponsor organization."
* Tristan: I agree.
* Allan: We will add this to the policy as a statement of intent.
* VOTE: Approve the following:
1. Create a new committee, "The Release Team", as described in
https://gitlab.gnome.org/Teams/Board/-/issues/166 Appoint the existing
members of the Release Team as committee members:
* Abderrahim Kitouni
* Andre Klapper
* Javier Jardon
* Matthias Clasen
* Michael Catanzaro (chair)
* Emmanuele Bassi
* Tristan Van Berkom
* Jordan Petridis
2. Create a new committee, the "GNOME Circle" committee, as described
in https://gitlab.gnome.org/Teams/Board/-/issues/167 Appoint the following
committee members:
* Allan Day (chair)
* J Arun Mani
* Mart=C3=ADn Abente Lahaye
* Jordan Petridis
3. Adopt the GNOME Foundation policy on official GNOME software, as
described in issue https://gitlab.gnome.org/Teams/Board/-/issues/165
* +1 unanimous
* Board handover arrangements
* Allan: The new board takes effect at midnight tonight. There is a
training tomorrow for new and returning board members. The following week,
the new board will vote on officers, so Carlos will remain treasurer until
that vote occurs. Then, in a couple of weeks, we will have the handover
meeting, which the outgoing directors are encouraged to attend. The one
question I had was when do we cut off access for the outgoing directors? It
seems it would be useful to retain that access until the handover meeting.
* Tristan: It seems important to have access to !GitLab issues for the
handover meeting.
* Rob: It's less important to have overlap now that we have
overlapping directors.
* Tristan: The mailing list could have sensitive information.
* Allan: Let's remove access to the mailing list and chat channel, and
retain access to !GitLab until after the handover meeting.
--00000000000020eb7a05aa2619a2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Wiki location:=C2=A0<a href=3D"https://wiki.gnome.org/Foun=
dationBoard/Minutes/20200622" target=3D"_blank">https://wiki.gnome.org/Foun=
dationBoard/Minutes/20200622</a><br><div><br></div><div>=3D Meeting of the =
GNOME Foundation Board of Directors, 22 June 2020, 14:30 UTC =3D<br><br>=3D=
=3D Attending =3D=3D<br><br>=C2=A0* TristanVanBerkom<br>=C2=A0* FedericoMen=
aQuintero<br>=C2=A0* AllanDay<br>=C2=A0* CarlosSoriano<br>=C2=A0* NeilMcGov=
ern<br>=C2=A0* PhilipChimento<br>=C2=A0* RosannaYuen<br>=C2=A0* RobertMcQue=
en<br><br>=3D=3D Regrets =3D=3D<br><br>=C2=A0* BrittYazel<br><br>=3D=3D Age=
nda =3D=3D<br><br>=C2=A0* Approve minutes of 8 June<br>=C2=A0* GNOME softwa=
re definition & GNOME Circle initiative<br>=C2=A0* Board handover arran=
gements<br><br>=3D=3D Minutes =3D=3D<br><br>=C2=A0* Approve minutes of 8 Ju=
ne<br>=C2=A0 =C2=A0* Philip: There is a domain name mentioned in the minute=
s that the Foundation would potentially purchase.<br>=C2=A0 =C2=A0 =C2=A0* =
We decide to redact it so that it doesn't get scooped.<br>=C2=A0 =C2=A0=
* No other changes were submitted.<br>=C2=A0 =C2=A0* Minutes are approved, =
pending the above correction.<br><br>=C2=A0* GNOME software definition &=
; GNOME Circle initiative<br>=C2=A0 =C2=A0* Allan: This has been a long-sta=
nding item and I'm glad to be finishing it up. We've discussed thes=
e before, so I'll just go through what's new. The first item is the=
release team becoming a committee. We decided to stick to the bare essenti=
als for the release team committee's charter, just covering the tradema=
rk issue where the board devolves the power to decide what is GNOME and wha=
t can use the Foundation's trademarks to the release team committee. Th=
e draft charter is at <a href=3D"https://gitlab.gnome.org/Teams/Board/-/iss=
ues/166">https://gitlab.gnome.org/Teams/Board/-/issues/166</a><br>=C2=A0 =
=C2=A0 =C2=A0* Tristan: While it is all about the Foundation's trademar=
ks, we don't mention trademarks in the charter. Should we?<br>=C2=A0 =
=C2=A0 =C2=A0* Carlos: I don't think so. This seems like a policy imple=
mentation detail that the board is still responsible for. The board just ne=
eds to keep in touch with the release team about the requirements for the t=
rademark.<br>=C2=A0 =C2=A0 =C2=A0* Tristan: I agree, but I think it should =
be documented somewhere.<br>=C2=A0 =C2=A0 =C2=A0* Allan: The trademark poli=
cy is part of the last item in the slate we'll be voting on.<br>=C2=A0 =
=C2=A0* Allan: The GNOME Circle committee has a draft charter at <a href=3D=
"https://gitlab.gnome.org/Teams/Board/-/issues/167">https://gitlab.gnome.or=
g/Teams/Board/-/issues/167</a> I'm volunteering myself for the committe=
e as well, to help bootstrap it. As we've discussed, this affects who c=
an become a member of the Foundation.<br>=C2=A0 =C2=A0* Allan: The last ite=
m is the policy on official GNOME software, the draft of which is at <a hre=
f=3D"https://gitlab.gnome.org/Teams/Board/-/issues/165">https://gitlab.gnom=
e.org/Teams/Board/-/issues/165</a>. The domain name has been removed from t=
he policy since we haven't resolved that question yet.<br>=C2=A0 =C2=A0=
* Tristan: You had already sent an announcement for what would be under the=
remit of these committees, correct?<br>=C2=A0 =C2=A0 =C2=A0* Allan: The an=
nouncement was published on Discourse, but as a proposal.<br>=C2=A0 =C2=A0 =
=C2=A0* Tristan: So what is our vote on today? To create the committees, ma=
ke the proposal into a policy, and point the committees to it?<br>=C2=A0 =
=C2=A0 =C2=A0* Allan: That's a good question. The release team's ac=
tivities don't change, but there will of course be a transition period =
where the GNOME Circle committee is bootstrapped and the infrastructure for=
the GNOME Circle is created on !GitLab. In practice, if there are difficul=
ties with the implementation, then they will take it back to the board to a=
mend the policy.<br>=C2=A0 =C2=A0 =C2=A0* Tristan: My point is that the ori=
ginal proposal for these committees had a lot more detail. Do the committee=
s know what is expected of them? What if the implementation turns out to be=
different from our intention?<br>=C2=A0 =C2=A0 =C2=A0* Carlos: I agree, bu=
t I think the answer is that we need to anticipate that by being in a close=
loop with the GNOME Circle committee during the bootstrap period, not by m=
aking the charter more detailed.<br>=C2=A0 =C2=A0 =C2=A0* Allan: In practic=
e, we do the same with other committees, we can make course adjustments.<br=
>=C2=A0 =C2=A0* Allan: The part about projects with an existing fiscal spon=
sor has been removed, because it turned out to be confusing in the proposal=
. We intend to leave this up to the committee's discretion.<br>=C2=A0 =
=C2=A0 =C2=A0* Rob: Fiscal sponsorship is a nonprofit term of art, so altho=
ugh it may not communicate very well because people might not know what it =
is, it is unambiguous. I do think it's important to specify it.<br>=C2=
=A0 =C2=A0 =C2=A0* Tristan: It would be odd for a project to be both a GNOM=
E Circle and an Apache project, for example.<br>=C2=A0 =C2=A0 =C2=A0* Allan=
: We could add this back to the GNOME Circle committee charter, and I don&#=
39;t think it would be that confusing, because projects looking to apply wo=
uld be looking at a more user-friendly description.<br>=C2=A0 =C2=A0 =C2=A0=
* Carlos: I agree, we can include this guideline and the committee can disc=
uss with the board if they want to deviate from it.<br>=C2=A0 =C2=A0 =C2=A0=
* Rob: We do need to be intentional that the GNOME Circle projects further =
the GNOME mission, because being in the GNOME Circle affects how the Founda=
tion's budget is spent.<br>=C2=A0 =C2=A0 =C2=A0* Neil: The expectation =
would be that if a GNOME Circle project became big, then they would move to=
full fiscal sponsorship.<br>=C2=A0 =C2=A0 =C2=A0* Rob: I think we should a=
dd a non-normative statement: =C2=A0"It is intended that projects seek=
ing membership of GNOME Circle are not already members of another non-profi=
t fiscal sponsor organization."<br>=C2=A0 =C2=A0 =C2=A0* Tristan: I ag=
ree.<br>=C2=A0 =C2=A0 =C2=A0* Allan: We will add this to the policy as a st=
atement of intent.<br>=C2=A0 =C2=A0* VOTE: Approve the following:<br>=C2=A0=
=C2=A0 =C2=A01. Create a new committee, "The Release Team", as d=
escribed in <a href=3D"https://gitlab.gnome.org/Teams/Board/-/issues/166">h=
ttps://gitlab.gnome.org/Teams/Board/-/issues/166</a> Appoint the existing m=
embers of the Release Team as committee members:<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0* Abderrahim Kitouni<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0* Andre Klapper<br=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0* Javier Jardon<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0*=
Matthias Clasen<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0* Michael Catanzaro (chair)<=
br>=C2=A0 =C2=A0 =C2=A0 =C2=A0* Emmanuele Bassi<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0* Tristan Van Berkom<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0* Jordan Petridis<br>=
=C2=A0 =C2=A0 =C2=A02. Create a new committee, the "GNOME Circle"=
committee, as described in <a href=3D"https://gitlab.gnome.org/Teams/Board=
/-/issues/167">https://gitlab.gnome.org/Teams/Board/-/issues/167</a> Appoin=
t the following committee members:<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0* Allan Da=
y (chair)<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0* J Arun Mani<br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0* Mart=C3=ADn Abente Lahaye<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0* Jorda=
n Petridis<br>=C2=A0 =C2=A0 =C2=A03. Adopt the GNOME Foundation policy on o=
fficial GNOME software, as described in issue <a href=3D"https://gitlab.gno=
me.org/Teams/Board/-/issues/165">https://gitlab.gnome.org/Teams/Board/-/iss=
ues/165</a><br>=C2=A0 =C2=A0* +1 unanimous<br><br>=C2=A0* Board handover ar=
rangements<br>=C2=A0 =C2=A0* Allan: The new board takes effect at midnight =
tonight. There is a training tomorrow for new and returning board members. =
The following week, the new board will vote on officers, so Carlos will rem=
ain treasurer until that vote occurs. Then, in a couple of weeks, we will h=
ave the handover meeting, which the outgoing directors are encouraged to at=
tend. The one question I had was when do we cut off access for the outgoing=
directors? It seems it would be useful to retain that access until the han=
dover meeting.<br>=C2=A0 =C2=A0 =C2=A0* Tristan: It seems important to have=
access to !GitLab issues for the handover meeting.<br>=C2=A0 =C2=A0 =C2=A0=
* Rob: It's less important to have overlap now that we have overlapping=
directors.<br>=C2=A0 =C2=A0 =C2=A0* Tristan: The mailing list could have s=
ensitive information.<br>=C2=A0 =C2=A0 =C2=A0* Allan: Let's remove acce=
ss to the mailing list and chat channel, and retain access to !GitLab until=
after the handover meeting.<br></div></div>
--00000000000020eb7a05aa2619a2--
--===============8577860266513485029==
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
--===============8577860266513485029==--