Re: Minutes of the board meeting of September 18, 2018

2018-10-10 Thread Philip Chimento via foundation-list
On Fri, Sep 28, 2018 at 11:17 PM  wrote:

> [...snip original minutes...]
> 
>
> By request, here is an excerpt from the minutes from the meeting of May
> 15, 2018, which was private at the time pending an announcement and now
> public, along with a list of the attendees of that meeting. See
> https://gitlab.gnome.org/Teams/Board/issues/60
>
> Wiki location of the full minutes of that meeting:
> https://wiki.gnome.org/FoundationBoard/Minutes/20180515
>
> == Attending ==
>
>  * NuritziSanchez
>  * CarlosSoriano
>  * AllanDay
>  * MegFord (planned early departure)
>  * DidierRoche (planned late attendance)
>  * NeilMcGovern
>  * RosannaYuen
>
> == Regrets ==
>
>  * AlexandreFranke
>  * CosimoCecchi
>
> == Minutes ==
>
>  * Events code of conduct (Allan)
>   * We've had the events code of conduct proposal on the table for some
> time now. Board members have had chance to review it. Only Alexandre has
> raised concerns. These include:
> * GDPR - Neil doesn't think this affects the events code of conduct
> (in a blocking way) and thinks that any issues can be dealt with at a later
> date
> * Release parties: do we have guidelines for what release parties
> should follow?
> * Concern about prohibiting speech based on it being "offensive",
> since this could be subjective.
> * Question about prohibiting weapons: does this include pepper spray,
> multi-tools
>* Two potential amendments have been discussed with Alexandre:
> * 1. Add a sentence to the photography policy: “If press photographers
> are present, the event organizer will ask them to comply with this policy.”
> * 2. Remove the section of the incident reporting page that encourages
> reporting incidents that you might have observed ("if you see someone
> violating the Code of Conduct")
>  * Nuritzi - observing incidents can make people feel
> uncomfortable/unwelcome. Neil - if you observe a crime, you report it.
>   * VOTE: accept the events code of conduct that has been presented (
> https://wiki.gnome.org/Diversity/CoCWorkingGroup/DraftEventsCoC/ ) as
> official GNOME Foundation policy, for all future events
>* Passed unanimously
>   * VOTE: 1st amendment
> * Passed unanimously
>* Didier joined at this point.
>   * VOTE: 2nd amendment
>* -1 unanimous, (Carlos cites concerns that have been expressed to him
> by community members)
> Meg leaves.
>

At Alexandre's request (see comment on
https://gitlab.gnome.org/Teams/Board/issues/60), I am clarifying explicitly
in this addendum that Alexandre Franke was not present at the above board
meeting (see list of attendees), and that in the following board meeting he
went on the record stating that he disagreed with the outcome of the above
votes.
___
foundation-list mailing list
foundation-list@gnome.org
https://mail.gnome.org/mailman/listinfo/foundation-list


Minutes of the board meeting of September 18, 2018

2018-09-29 Thread Philip Chimento via foundation-list
Wiki location: https://wiki.gnome.org/FoundationBoard/Minutes/20180918

Next meeting date Tuesday, September 25th 2018, 15:30 UTC

== Attending ==

 * AllanDay
 * NuritziSanchez
 * PhilipChimento
 * RosannaYuen
 * CarlosSoriano
 * KatGerasimova
 * FedericoMenaQuintero
 * NeilMcGovern
 * RobMcQueen

== Agenda ==

 * GUADEC dates
 * Discuss hackfest agenda (Kat)
 * Committee requirements (Kat)
 * (semi-urgent) SeaGL trip approval (Neil)
 * Review compensation committee charter (Rob, see
https://gitlab.gnome.org/Community/Board/issues/78)
 * Funding Outreachy intern spots (Philip) - see board-list,
https://gitlab.gnome.org/Community/Board/issues/83
 * COSCON'18 speaker invitation (Nuritzi)
 * LAS GNOME report (Nuritzi)
 * Review to-do GitLab issues -
https://gitlab.gnome.org/Community/Board/issues?label_name%5B%5D=To-Do
 * From issue 39 (devolved conference bidding process) - how can we
allocate conference budget for CoC-enforcement training for one or two of
the local organizers? (Federico)

== Minutes ==

 * GUADEC dates
   * Kat polled our ex-interns and general consensus is end of August. The
local team would also prefer end of August.
   * The options are July 5–10 or August 23–28.
   * Allan: Is August 23–28 going to conflict with the release cycle?
 * Kat: Can we move the release schedule?
 * Carlos: Usually no, because of the downstream distributions.
 * Philip: During the last weeks of the release cycle is actually
better than right before the feature freeze like this year's GUADEC.
   * Nuritzi: Does this affect our other conferences such as GNOME.Asia? We
should not prevent core members from going to both conferences. No need to
move this date, but we should let the GNOME.Asia organizers know that they
need to keep this date in mind.
   * Federico: The concern last time we discussed this was conflict with
school semesters starting.
 * The dates are inconvenient for Rosanna and Federico.
   * Kat: The end of July isn't an option because it conflicts with Debconf.
   * Nuritzi: When is Akademy next year? - They are still on the call for
hosts, so the date is not known yet.
   * '''VOTE''': Set dates of GUADEC 2019 to be August 23-28.
 * +1 Nuritzi, Kat, Carlos, Allan, Philip, Federico. Abstained: Rob
 * Note from Philip, Federico, Rob: This date seems not-ideal, but also
seems the best out of a number of not-ideal options.
   * Nuritzi: Can we let bidding teams know what the board considers ideal
dates?
 * Kat: This should be a broader discussion with the conference
organizers.
 * Philip: Would be good to set what those dates are based on, e.g. no
earlier than the stipend payments of the internships, no later than the
beginning of school semesters in X country, with exceptions possible.
 * Kat: Announcing is the job of the GUADEC team; they can work with
Engagement on this.
   * '''ACTION''' - Allan: add a comment to our GitLab issue about setting
a date range.

 * Hackfest agenda
   * Current agenda, after making the changes discussed in this meeting:
 * [[https://wiki.gnome.org/Hackfests/New|Hackfest policy]]
 * Financial policies and transparency (Nuritzi)
 * Fundraising & campaigns (Carlos)
 * Approve budget for next year (Nuritzi)
 * Committee check-ins (Nuritzi)
 * Topics for future rounds of GNOME internships (Philip)
 * Community check-ins (Philip)
 * Board & Foundation planning
 * Project-wide Code of Conduct (Federico)
 * Cross-project hackfests (Kat)
 * Travel sponsorship policy (Philip)
 * "Hacking time" (Allan)
   * Kat: Let's keep the agenda relatively light so we have time to work on
things.
   * Neil: Work out a timeline for the day, and what we're going to discuss
at what times, to maximize the efficiency of our time.
   * Nuritzi: We should pre-plan lunch options.
   * Nuritzi: We should also figure out which day we want to hold the
community event. How about Thursday evening?
   * Neil booked a hotel for everyone already.
   * Nuritzi: Are there whiteboards? - Kat: Yes
   * '''ACTION''' - Philip: Add the things mentioned here to the agenda
   * '''ACTION''' - Nuritzi: Plan out a schedule for the days

 * Committee requirements
   * https://gitlab.gnome.org/Community/Board/issues/67
   * What's the status of this?
   * Nuritzi: The engagement committee discussed it, but didn't get all the
way through the items.
   * Philip: Sent an email to the travel committee mailing list.
   * Federico: Sent an email to the CoC committee mailing list.
   * Rob: Will send an email to the sponsorship committee mailing list.
   * Carlos: Will send an email to the membership committee mailing list.
   * Philip: Rob, Carlos, feel free to adapt my email text.

 * SeaGL trip approval
   * Neil: We've been offered a booth, at SeaGL, November 7-9 in Seattle.
   * Neil and Rosanna are going to attend, and combine it with a trip to
Denver to talk to James Donnelly (LuNEL) on work for Odoo.
   * Nuritzi: Any talks or