Minutes of the board meeting of May 6, 2019
"philip.chimento--- via foundation-announce" <[email protected]> Wed, 5 Jun 2019 21:47:37 -0700
| Newsgroups | gmane.comp.gnome.foundation.announce |
|---|---|
| Message-ID | <CAHbXgc3u-xGiBJbtEhSnYKbT_8XFGRJ0L5SK9rTno6HNHwwVNA__23228.3240578667$1559819134$gmane$org@mail.gmail.com> |
--===============2833329420260008332==
Content-Type: multipart/alternative; boundary="0000000000006f6a93058aa06aab"
--0000000000006f6a93058aa06aab
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
=3D Foundation Board Minutes for Monday 6th May 2019, 14:30 UTC =3D
Wiki location: https://wiki.gnome.org/FoundationBoard/Minutes/20190506
=3D=3D Attending =3D=3D
* KatGerasimova
* NuritziSanchez
* NeilMcGovern
* RosannaYuen
* PhilipChimento
* CarlosSoriano
* AllanDay
* FedericoMenaQuintero
=3D=3D Regrets =3D=3D
* RobMcQueen
=3D=3D Agenda =3D=3D
* Travel Committee status
* LAS co-hosting proposal
* GNOME Software definition proposal
=3D=3D Minutes =3D=3D
* Travel committee status
* Philip: There were a lot more pending requests than I thought at first
glance. I started processing them thanks to Germ=C3=A1n's detailed document=
ation
and we are now caught up on sponsorship requests and reimbursements. I
contacted Guillaume Gomez and he's still interested in volunteering.
* Nuritzi: Umang Jain is interested to join the committee as well.
* Neil: I have looked into how the Foundation could make things easier.
I don't yet have any recommendations, but am still working on it. Currently
I don't have a good picture of what is the most time consuming part.
* Philip: A huge bottleneck is the tools: RT and nextcloud. Another
time suck is the verification of flight searches, which should become much
easier under the draft sponsorship policy which we will hopefully adopt
soon. Germ=C3=A1n's documentation is here:
https://wiki.gnome.org/Travel/ApplicationProcess
* Nuritzi: If we are planning to appoint new people into the travel
committee, we should train them as early as possible before the GUADEC rush=
.
* Philip: I propose not appointing them now, but first giving the travel
committee a heads up.
* '''ACTION''': Philip - Communicate to the travel committee our
intention to appoint more people to the committee
* '''ACTION''': Federico - Introduce Guillaume to the board on Discourse
* '''ACTION''': Nuritzi - Introduce Umang to the board on Discourse
* LAS co-hosting proposal
* Nuritzi: There have not been too many edits since the last time we
discussed it. The main changes have been about fundraising and how any
surplus is split after the event. Sponsorship from organizations that
donate to both GNOME and KDE will be considered "joint sponsorship".
* Nuritzi: Regarding branding, the conference is pursuing a visual
identity which is distinct from both KDE and GNOME, but there are designers
from both communities contributing.
* Nuritzi: The committee is currently blocked on sending out the call
for locations and would like the GNOME board to vote on the proposal.
* Philip: When did the name change from Libre Application Summit to
Linux Application Summit?
* Nuritzi: Quite early on. We thought that Libre implied that only
representatives of free software applications were welcome at the
conference.
* Carlos: How do we determine which organizations are considered "joint
sponsorship"?
* Nuritzi: Looking at whether they donate to GNOME and/or KDE
conferences regularly in other years.
* Carlos: Do we have representation in the group that decides things
around fundraising?
* Nuritzi: Yes, Sri has expressed interest.
* Carlos: The Contributor Covenant is mainly for online situations,
could that pose a problem when applied to a conference?
* Nuritzi: We consulted with the code of conduct committee about this.
* Federico: The language in the Contributor Covenant is quite similar
to the GNOME events code of conduct already.
* Nuritzi: We are considering adding some of the details from the
GNOME events code of conduct, such as how to report incidents.
* Allan: At some time early in the process I would like the committee to
present to the board. Otherwise I don't see an opportunity to provide
feedback.
* Nuritzi: Can we do this as part of presenting the bid?
* Allan: We can make a note that the board would be able to provide
feedback on branding, fundraising, etc. at that point.
* Allan: Neil, what's your opinion on this document?
* Neil: The document has the right level of detail for this stage. We
would want more detail when a bid arrives. The main risk to the Foundation
here is if we ask people to put time into this and it ends up not
happening, and this document goes a long way towards de-risking that.
* Neil: I'm not sure the board needs to vote on this necessarily, as no
funds or trademarks are being committed.
* Carlos: Since the process is new and uncertain, voting would send a
clear message of support to the committee.
* Nuritzi: Would there be a way to remove some of the risks from the
branding? Would it help to present the branding before a bid arrives, if it
is ready? Would the board or the GNOME design team evaluate the branding?
* Allan: Since we have to approve the trademark use, the board has to
approve it. The GNOME design team can give input.
* Nuritzi: Allan, I would like to discuss this further with you to
figure out this process.
* The board formally acknowledges the proposal.
* GNOME software definition proposal
* Carlos, Rob, and Allan have finished drafting the proposal, which aims
to answer the question of how to define GNOME software.
* Carlos: The proposal splits things into two. There is "GNOME core"
software which can use the GNOME trademarks and identify itself as "GNOME",
and there is a group of "GNOME affiliates" consisting of applications that
apply for membership in the group.
* Allan: GNOME affiliates don't need to be hosted on GNOME
infrastructure, but the contributors are eligible for Foundation
membership. This potentially broadens our membership base.
* Allan: It could be controversial to admit members who are developing
applications on proprietary platform. However, we believe that if you are
developing a great GNOME-related application which is hosted on GitHub, you
should be able to join the Foundation and get support to attend GUADEC.
* Allan: The most potentially controversial item is if an application
doesn't meet the criteria for GNOME core, but previously did. This is part
of the reason why we have the GNOME affiliates, to provide a soft landing
place for these applications.
* Philip: Under what circumstances would an application drop out of
GNOME core?
* Allan: If a GNOME core application gets replaced by a newer GNOME
core application that fills the same niche, for example.
* Nuritzi: Is there anything blocking opening this up for community
consultation?
* Allan: We would like the board to give some approval.
* Nuritzi: What would be the alternative to this plan?
* Allan: Alternatively, we could open things up even wider and say
"everyone can be GNOME".
* Carlos: The problem with that is that we then have to be stricter
about who can use the trademark.
* Federico: Do we extend the GNOME affiliate status to apps, or do they
apply for it?
* Carlos: The plan is to have a committee or working group that
reviews applications.
* Federico: Do we require the GNOME affiliates to use particular parts
of the GNOME stack, such as GNOME configuration libraries? Do we make any
guarantees to GNOME affiliates, such as not breaking their applications, or
giving priority to bug fixes that affect their applications?
* Carlos: We are trying to keep it light. The goal is for the GNOME
affiliate to feel like they are part of GNOME by allowing them membership
in the Foundation and travel sponsorship. Otherwise we will have to have a
review committee to comb through the application code.
* Federico: Can the affiliates propose projects for GNOME's Google
Summer of Code and Outreachy spots?
* Carlos: Yes.
* We will continue to discuss this next week.
=3D=3D Actions =3D=3D
* '''Philip''' - Notify the travel committee of our intention to appoint
more people to the committee
* '''Federico''' - Introduce Guillaume Gomez to the board on Discourse
* '''Nuritzi''' - Introduce Umang Jain to the board on Discourse
--0000000000006f6a93058aa06aab
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">=3D Foundation Board Min=
utes for Monday 6th May 2019, 14:30 UTC =3D</div><div dir=3D"ltr"><br></div=
><div dir=3D"ltr">Wiki location: <a href=3D"https://wiki.gnome.org/Foundati=
onBoard/Minutes/20190506">https://wiki.gnome.org/FoundationBoard/Minutes/20=
190506</a></div><div dir=3D"ltr"><br>=3D=3D Attending =3D=3D<br><br>=C2=A0*=
KatGerasimova<br>=C2=A0* NuritziSanchez<br>=C2=A0* NeilMcGovern<br>=C2=A0*=
RosannaYuen<br>=C2=A0* PhilipChimento<br>=C2=A0* CarlosSoriano<br>=C2=A0* =
AllanDay<br>=C2=A0* FedericoMenaQuintero<br><br>=3D=3D Regrets =3D=3D<br><b=
r>=C2=A0* RobMcQueen<br><br>=3D=3D Agenda =3D=3D<br><br>=C2=A0* Travel Comm=
ittee status<br>=C2=A0* LAS co-hosting proposal<br>=C2=A0* GNOME Software d=
efinition proposal<br><br>=3D=3D Minutes =3D=3D<br><br>=C2=A0* Travel commi=
ttee status<br>=C2=A0=C2=A0 * Philip: There were a lot more pending request=
s than I thought at first glance. I started processing them thanks to Germ=
=C3=A1n's detailed documentation and we are now caught up on sponsorshi=
p requests and reimbursements. I contacted Guillaume Gomez and he's sti=
ll interested in volunteering.<br>=C2=A0=C2=A0 * Nuritzi: Umang Jain is int=
erested to join the committee as well.<br>=C2=A0=C2=A0 * Neil: I have looke=
d into how the Foundation could make things easier. I don't yet have an=
y recommendations, but am still working on it. Currently I don't have a=
good picture of what is the most time consuming part.<br>=C2=A0=C2=A0=C2=
=A0=C2=A0 * Philip: A huge bottleneck is the tools: RT and nextcloud. Anoth=
er time suck is the verification of flight searches, which should become mu=
ch easier under the draft sponsorship policy which we will hopefully adopt =
soon. Germ=C3=A1n's documentation is here: <a href=3D"https://wiki.gnom=
e.org/Travel/ApplicationProcess">https://wiki.gnome.org/Travel/ApplicationP=
rocess</a><br>=C2=A0=C2=A0 * Nuritzi: If we are planning to appoint new peo=
ple into the travel committee, we should train them as early as possible be=
fore the GUADEC rush.<br>=C2=A0=C2=A0 * Philip: I propose not appointing th=
em now, but first giving the travel committee a heads up.<br>=C2=A0=C2=A0 *=
'''ACTION''': Philip - Communicate to the travel c=
ommittee our intention to appoint more people to the committee<br>=C2=A0=C2=
=A0 * '''ACTION''': Federico - Introduce Guillaume =
to the board on Discourse<br>=C2=A0=C2=A0 * '''ACTION''=
': Nuritzi - Introduce Umang to the board on Discourse<br><br>=C2=A0* L=
AS co-hosting proposal<br>=C2=A0=C2=A0 * Nuritzi: There have not been too m=
any edits since the last time we discussed it. The main changes have been a=
bout fundraising and how any surplus is split after the event. Sponsorship =
from organizations that donate to both GNOME and KDE will be considered &qu=
ot;joint sponsorship".<br>=C2=A0=C2=A0 * Nuritzi: Regarding branding, =
the conference is pursuing a visual identity which is distinct from both KD=
E and GNOME, but there are designers from both communities contributing.<br=
>=C2=A0=C2=A0 * Nuritzi: The committee is currently blocked on sending out =
the call for locations and would like the GNOME board to vote on the propos=
al.<br>=C2=A0=C2=A0 * Philip: When did the name change from Libre Applicati=
on Summit to Linux Application Summit?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Nuritz=
i: Quite early on. We thought that Libre implied that only representatives =
of free software applications were welcome at the conference.<br>=C2=A0=C2=
=A0 * Carlos: How do we determine which organizations are considered "=
joint sponsorship"?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Nuritzi: Looking at =
whether they donate to GNOME and/or KDE conferences regularly in other year=
s.<br>=C2=A0=C2=A0 * Carlos: Do we have representation in the group that de=
cides things around fundraising?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Nuritzi: Yes=
, Sri has expressed interest.<br>=C2=A0=C2=A0 * Carlos: The Contributor Cov=
enant is mainly for online situations, could that pose a problem when appli=
ed to a conference?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Nuritzi: We consulted wit=
h the code of conduct committee about this.<br>=C2=A0=C2=A0=C2=A0=C2=A0 * F=
ederico: The language in the Contributor Covenant is quite similar to the G=
NOME events code of conduct already.<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Nuritzi:=
We are considering adding some of the details from the GNOME events code o=
f conduct, such as how to report incidents.<br>=C2=A0=C2=A0 * Allan: At som=
e time early in the process I would like the committee to present to the bo=
ard. Otherwise I don't see an opportunity to provide feedback.<br>=C2=
=A0=C2=A0=C2=A0=C2=A0 * Nuritzi: Can we do this as part of presenting the b=
id?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Allan: We can make a note that the board =
would be able to provide feedback on branding, fundraising, etc. at that po=
int.<br>=C2=A0=C2=A0 * Allan: Neil, what's your opinion on this documen=
t?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Neil: The document has the right level of =
detail for this stage. We would want more detail when a bid arrives. The ma=
in risk to the Foundation here is if we ask people to put time into this an=
d it ends up not happening, and this document goes a long way towards de-ri=
sking that.<br>=C2=A0=C2=A0 * Neil: I'm not sure the board needs to vot=
e on this necessarily, as no funds or trademarks are being committed.<br>=
=C2=A0=C2=A0=C2=A0=C2=A0 * Carlos: Since the process is new and uncertain, =
voting would send a clear message of support to the committee.<br>=C2=A0=C2=
=A0 * Nuritzi: Would there be a way to remove some of the risks from the br=
anding? Would it help to present the branding before a bid arrives, if it i=
s ready? Would the board or the GNOME design team evaluate the branding?<br=
>=C2=A0=C2=A0=C2=A0=C2=A0 * Allan: Since we have to approve the trademark u=
se, the board has to approve it. The GNOME design team can give input.<br>=
=C2=A0=C2=A0=C2=A0=C2=A0 * Nuritzi: Allan, I would like to discuss this fur=
ther with you to figure out this process.<br>=C2=A0=C2=A0 * The board forma=
lly acknowledges the proposal.<br><br>=C2=A0* GNOME software definition pro=
posal<br>=C2=A0=C2=A0 * Carlos, Rob, and Allan have finished drafting the p=
roposal, which aims to answer the question of how to define GNOME software.=
<br>=C2=A0=C2=A0 * Carlos: The proposal splits things into two. There is &q=
uot;GNOME core" software which can use the GNOME trademarks and identi=
fy itself as "GNOME", and there is a group of "GNOME affilia=
tes" consisting of applications that apply for membership in the group=
.<br>=C2=A0=C2=A0 * Allan: GNOME affiliates don't need to be hosted on =
GNOME infrastructure, but the contributors are eligible for Foundation memb=
ership. This potentially broadens our membership base.<br>=C2=A0=C2=A0 * Al=
lan: It could be controversial to admit members who are developing applicat=
ions on proprietary platform. However, we believe that if you are developin=
g a great GNOME-related application which is hosted on GitHub, you should b=
e able to join the Foundation and get support to attend GUADEC.<br>=C2=A0=
=C2=A0 * Allan: The most potentially controversial item is if an applicatio=
n doesn't meet the criteria for GNOME core, but previously did. This is=
part of the reason why we have the GNOME affiliates, to provide a soft lan=
ding place for these applications.<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Philip: Un=
der what circumstances would an application drop out of GNOME core?<br>=C2=
=A0=C2=A0=C2=A0=C2=A0 * Allan: If a GNOME core application gets replaced by=
a newer GNOME core application that fills the same niche, for example.<br>=
=C2=A0=C2=A0 * Nuritzi: Is there anything blocking opening this up for comm=
unity consultation?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Allan: We would like the =
board to give some approval.<br>=C2=A0=C2=A0 * Nuritzi: What would be the a=
lternative to this plan?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Allan: Alternatively=
, we could open things up even wider and say "everyone can be GNOME&qu=
ot;.<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Carlos: The problem with that is that we=
then have to be stricter about who can use the trademark.<br>=C2=A0=C2=A0 =
* Federico: Do we extend the GNOME affiliate status to apps, or do they app=
ly for it?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Carlos: The plan is to have a comm=
ittee or working group that reviews applications.<br>=C2=A0=C2=A0 * Federic=
o: Do we require the GNOME affiliates to use particular parts of the GNOME =
stack, such as GNOME configuration libraries? Do we make any guarantees to =
GNOME affiliates, such as not breaking their applications, or giving priori=
ty to bug fixes that affect their applications?<br>=C2=A0=C2=A0=C2=A0=C2=A0=
* Carlos: We are trying to keep it light. The goal is for the GNOME affili=
ate to feel like they are part of GNOME by allowing them membership in the =
Foundation and travel sponsorship. Otherwise we will have to have a review =
committee to comb through the application code.<br>=C2=A0=C2=A0=C2=A0=C2=A0=
* Federico: Can the affiliates propose projects for GNOME's Google Sum=
mer of Code and Outreachy spots?<br>=C2=A0=C2=A0=C2=A0=C2=A0 * Carlos: Yes.=
<br>=C2=A0=C2=A0 * We will continue to discuss this next week.<br><br>=3D=
=3D Actions =3D=3D<br>=C2=A0* '''Philip''' - Notify=
the travel committee of our intention to appoint more people to the commit=
tee<br>=C2=A0* '''Federico''' - Introduce Guillaume=
Gomez to the board on Discourse<br>=C2=A0* '''Nuritzi''=
;' - Introduce Umang Jain to the board on Discourse<br><br></div></div>=
</div>
--0000000000006f6a93058aa06aab--
--===============2833329420260008332==
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
--===============2833329420260008332==--