Freedesktop <> GitLab | Notes and Follow-Up from 2020-02-03
Michael Schultheiss
president at spi-inc.org
Wed Mar 25 19:27:36 UTC 2020
Apologies for the delay - I've been having some e-mail issues. I'll
reach out with my availability shortly.
Nuritzi Sanchez wrote:
> Hi All,
>
> Lyude and I just had a great short meeting and I'm including our notes below.
>
> Michael, Lyude and Eric have some next steps before we can move ahead with
> payment. Please see the TODOs for each one of you below.
>
> @Michael -- are you able to hop on a short call? I think it'd be the easiest
> way to push the agreement forward. Here's a link to my calendar so you can find
> a time that works for you: Nuritzi's calendar [1].
>
> @Everyone else - our next regular meeting is on Monday, April 30th at 17:00
> UTC. I'll send out an agenda before the call and will try to identify necessary
> vs optional guests. In the meantime, Daniel S. and Benjamin will be meeting
> with some team members from GitLab in order to move the technical issues
> forward.
>
> If you have things to add to the agenda, please do so any time: Meeting Agenda
> and Notes [2]. You can also ping me on Gitter or Telegram @nuritzi or email me
> if you have questions before our next meeting.
>
> Until next time, have a great week, and I hope you all stay safe and healthy!
>
> Best,
> Nuritzi
>
> [1] https://calendly.com/nuritzi
> [2] https://docs.google.com/document/d/
> 1S3sdoI4EEW0dmeXSqutfAp9mXJmCkR5uuLn_hmXV2es/edit#heading=h.2pv8zjz15p9k
>
> 2020-03-16
>
> Attendees:
>
> • Nuritzi
>
> • Lyude
>
>
> Agenda and Notes:
>
> 1. Follow up on Freedesktop <> GitLab Agreement / Update on adding Freedesktop
> as a vendor
>
> 1. Update: Agreement must be signed before payment can be made.
>
> 1. Once we figure out which org the invoice will come from and send
> the billing contact info to GitLab accounting, then GitLab will
> send Eric an email with info on how to add bank info and all that
> for the payment.
>
> 2. TODO: @Michael from SPI should take a look at the contract and make any
> edits.
>
> 3. TODO: Create an invoice for GitLab for the $9K USD payment. @Lyude to
> get board approval for invoice. @Eric to generate it
>
> 1. Lyude thinks there might need to be an X.Org vote for that. Next
> board director meeting is: next week, but she will try to get it
> via email sooner.
>
> 2. Invoice will be most likely from SPI. Eric will be the billing
> contact.
>
>
> On Fri, Mar 13, 2020 at 1:58 PM Nuritzi Sanchez <nsanchez at gitlab.com> wrote:
>
> Thanks, Daniel!
>
> Michael -- it's nice to e-meet you! Are you available next Monday, March
> 16th at 17:00 UTC for a 30 min meeting? Please see below.
>
> Re: Regular Meetings
> Thanks for adding your availability, everyone!
>
> It looks like Mondays at 17:00 UTC will work best for everyone except for
> Benjamin. I think that's ok for now since we can schedule more technical
> discussions with Benjamin when needed.
>
> I sent a calendar invitation to those whom we've identified as main
> stakeholders.
>
> X.Org board - would you like me to send an invitation to the members at x.org
> so that you get reminders of the calls? Let me know and I can add the email
> (and/or individuals) to the existing calendar event.
>
> Re: Next Meeting
> Our next meeting is scheduled for Monday, March 16th at 17:00 UTC.
>
> Items to discuss [1]:
> □ Update on agreement
> □ Update on adding Freedesktop as a vendor
> Proposed Attendees:
> □ Michael
> □ Eric
> □ Lyude (optional)
> Any more topics to add?
> Let me know what you think. Anyone is free to join the meeting btw. I just
> want to be mindful of your time, so am adding a proposed attendee list.
>
> I think this meeting will be quite short and may also depend on Michael's
> availability. Let's default to having it since it's late today on a Friday,
> but we can definitely cancel and work asynchronously on these two things
> for now. I just want to have regular meetings scheduled so we maintain
> momentum.
>
> Re: Technical Meeting
> I also would like to propose a more technical discussion on Wednesday,
> March 18th at 14:00 UTC between @Daniel Stone, @Benjamin, and some of our
> engineers. I'll send out a calendar invitation for that time, and if it
> doesn't work, we can reschedule it.
>
> Have a great weekend!
>
> Best,
> Nuritzi
>
> [1] https://docs.google.com/document/d/
> 1S3sdoI4EEW0dmeXSqutfAp9mXJmCkR5uuLn_hmXV2es/edit#
>
> On Fri, Mar 13, 2020 at 1:11 PM Daniel Vetter <daniel.vetter at ffwll.ch>
> wrote:
>
> Hi Nuritzi,
>
> Apologies for the late reply, somehow your message here ended up in
> spam (with a fishing warning on top) in my gmail inbox here :-/ For the
> contract I think we need SPI to check the details, they need to sign it
> in the end. Adding Michael as SPI president for that.
>
> Michael, quoted mail below has the full context, tldr is we're working
> on a contract with gitlab (the company) to support the transition of
> fd.o to gitlab (the code hosting software). Here's the direct gdoc link
> with the draft from gitlab.
>
> https://docs.google.com/document/d/
> 1fdawIsMSZWy_JzCRgUrTUbtghAooIsm4pwmTfCSSlE4/edit
>
> Cheers, Daniel
>
> On Thu, Mar 12, 2020 at 2:41 PM Nuritzi Sanchez <nsanchez at gitlab.com>
> wrote:
>
> Hi again,
>
> I'm back from SCALE18x (I feel just fine, but let's see...), and I
> wanted to follow-up here. I realized that nobody entered in their
> availability into the meeting poll (including myself!), so I've now
> added my availability. :)
>
> @Lyude and @Daniel Stone -- can you please add your availability to
> the meeting poll [1]? I think that as long as a few of us meeting
> regularly we can make sure this all keeps moving forward. I think
> that at minimum, maybe Lyude and I can meet regularly at two week
> intervals.
>
> Lyude, if you can also take a look at the draft Freedesktop <>
> GitLab Agreement [2], that would be helpful. We can do some of this
> asynch, and have efficient meetings for things we need to discuss,
> and in order to keep momentum going.
>
> Best,
> Nuritzi
>
> [1] https://framadate.org/1d3ePoLDpsuUQole
> [2] https://docs.google.com/document/d/
> 1fdawIsMSZWy_JzCRgUrTUbtghAooIsm4pwmTfCSSlE4/edit
>
>
> On Fri, Mar 6, 2020 at 12:14 PM Nuritzi Sanchez <
> nsanchez at gitlab.com> wrote:
>
> Hi All,
>
> It was great meeting some of you earlier this week! For those
> who could not attend the meeting, I'm including the meeting
> notes below.
>
> I've been at conferences this week, so I'll follow up again
> next week with more progress, but I wanted to send out a few
> updates sooner than later.
>
> Updates:
> ■ Regular meeting poll: Here is a meeting poll [1] so that we
> can find a regular meeting slot that would work for
> meetings every 2 weeks. We agreed to only have these
> meetings if needed. Our next meeting would be
> sometime during the week of March 16th.
>
> @Lyude @Daniel Stone @Eric @Benjamin -- you were identified
> as the people most likely to be part of our regular
> meetings. Can you please add your availability to the poll?
>
>
> ■ Technical discussion: I'd like to get some of our engineers
> to join one of our upcoming calls. I'll follow up on this
> subject again next week because we may have some more
> questions for you before we can identify the right people
> to join the call.
>
> ■ Agreement and payment: I've added some more specifics to
> the Freedesktop <> GitLab Agreement [2] based on our
> conversation. @Lyude can you please take a look? I'm not
> sure when to name SPI vs Freedesktop vs X.Org, so if you
> have any input there, please let me know. I'm also trying
> to get information for how to proceed with setting you up
> as a vendor since things may have changed since we
> originally tried to set you up. Will follow up on this next
> week.
> Please let me know if you have any questions, or need anything
> else. Have a great weekend, everyone!
>
> Best,
> Nuritzi
>
> [1] https://framadate.org/1d3ePoLDpsuUQole
> [2] https://docs.google.com/document/d/
> 1fdawIsMSZWy_JzCRgUrTUbtghAooIsm4pwmTfCSSlE4/edit
>
>
> 2020-03-03 | Meeting Notes
>
> Link to notes: Agenda & Notes | Freedesktop <> GitLab
>
> (https://docs.google.com/document/d/
> 1S3sdoI4EEW0dmeXSqutfAp9mXJmCkR5uuLn_hmXV2es/edit#)
>
>
> When: 2020-03-03 at 18:00 UTC
>
>
> Attendees:
>
> ■ Nuritzi Sanchez
>
> ■ David Planella
>
> ■ Daniel Stone
>
> ■ Daniel Vetter
>
> ■ Lyude Paul
>
> ■ Harry Wentland
>
>
> Agenda:
>
> ■ Intros
>
> ★ Nuritzi: She/Her, will be the main point of contact on
> Gitlab side. Based in California, USA
>
> ★ David Planella: He/Him, will be fading into the
> background as Nuritzi ramps up. Based in Germany.
>
> ★ Daniel V: He/Him, helping to pull in sponsors, now also
> trying to do it for freedesktop.
>
> ★ Lyude: She/Her, Secretary for X.Org, based in Boston,
> with X.Org for a little under a year.
>
> ★ Harry: He/Him, X.Org board for 3 years, Toronto area
>
> ★ Daniel Stone: He/Him, based in London, freedesktop
> Admin for about 15 years!, originally spoke with
> Eliran, then David, then Nuritzi. Want to make sure
> that everyone is involved who needs to be involved, so
> that not all communications and interaction are
> channeled through Daniel S.
>
> ■ Sync on stakeholders from each side and overall status
>
> ★ SPI is parent foundation, X.org is non-profit, fd.o
> merged with X.org
>
> ★ Fd.o initially provided hosting for x.org, but also
> other projects, GStreamer, etc. There was a need to
> grow as an organization and to have structure - fd.o is
> a service for hosting X.org projects
>
> ★ X.org Board
>
> ★ Fd.o service provided by the foundation, Daniel S. is
> accountable to the Board as the admin.
>
> ■ Public information vs private
>
> ★ What should privacy setting be on these meeting notes?
> The link is shared on the x.org board mailing list
>
> ★ Keep settings as they are
>
> ■ Review current financial commitments / Review draft
> agreement: Freedesktop <> GitLab Agreement (right now this
> is a generic agreement, we need to add the correct terms in
> order to move forward with it and get Freedesktop
> officially set up as a vendor)
>
> ★ Is SPI still the legal entity that would sign the
> agreement?
>
> ★ Terms Summary (from Eliran’s notes):
>
> ◎ GitLab to sponsor the GCP billing costs:
>
> ● Original verbal agreement:
>
> △ Term: 24 months
>
> △ Monthly cap on bill: $250/month (hosting
> costs only) => total of $6000
>
> ● Most recent notes:
>
> △ "the numbers for Jan-Apr were":
>
> • $2176.35
>
> • $2452.41
>
> • $2684.22
>
> • $1443.22
>
> △ That makes a total of $8,756.20, for 4
> months
>
> △ Daniel: yes, that sounds about right, the
> basic thing was that GitLab was going to
> help with some of the initial ramp up.
>
> △ Vendor information should be X.Org + SPI.
> Eric should be able to help with all of
> this.
>
> △ David: we can make it something like a
> blanket amount of $9K
>
> ■ Review Freedesktop upstream issues and create next steps
> for technical solution-finding
>
> ★ Pipeline one could be low hanging fruit
>
> ★ David: here are some of the issues Daniel S. has opened
> in the past, which might also be relevant. There are
> probably others either filed by other fd.o members or
> that the fd.o team is subscribed to
>
> ■ Review any other pain points
>
> ★ Mentioned by Daniel S: Pages + CN
>
> ★ Big pain point: no kernel repos on gitlab
>
> ◎ Main issue is that have deployed omnibus
> (effectively a single container) and lots of ppl
> depending on GitLab pages, needs to be on a single
> container, Don’t have the option to break out into
> different pods. Limits daily amts. Kernel will
> overwhelm.
>
> ◎ Adding the kernel repos would most probably
> overwhelm the current cluster
>
> ◎ No capacity to have custom infrastructure, it has
> to go through one of the standard omnibus packages
> or Helm charts
>
> ★ Pages: still not on cloud
>
> ★ Not enough SysAdmin time. How does Benjamin’s help
> affect this?
>
> ◎ Not sure, admin time is a mix of personal time
>
> ★ Currently analysing where data is going, where to
> optimize things
>
> ◎ Would help to have guidance from GitLab from
> someone who could go through that process, could
> share practices/snippets, etc.
>
> ◎ About ⅔ of the current bill is network bandwidth,
> need to optimize
>
>
> Next Steps
>
> ■ Meetings: Once every two weeks, check in via email, send an
> agenda before the meeting so people know when they should
> join
>
> ★ Nuritzi: will send out a framadate to find time for a
> bi-weekly meeting every two weeks
>
> ■ Fill out agreement with more detail, send for review to all
> stakeholders
>
> ■ Follow up with vendor issue with Eric and make sure SPI and
> X.Org are set up as vendors
>
> ■ Set up a call with members from the GitLab engineering team
> + freedesktop/x.org
>
>
> --
> Nuritzi SanchezSenior Open Source Program Manager | GitLab
> [lFQxFbGYJpI6]
>
> Create, Collaborate, and Deploy together
> Free Trial | Upgrade Now | Contact Support | Community
>
>
>
> --
> Nuritzi Sanchez | She/HerSenior Open Source Program Manager |
> GitLab[lFQxFbGYJpI6]
>
> Create, Collaborate, and Deploy together
> Free Trial | Upgrade Now | Contact Support | Community | GitLab for
> Open Source
> _______________________________________________
> members at foundation.x.org: X.Org Foundation Members
> Archives: https://foundation.x.org/cgi-bin/mailman/private/members
> Info: https://foundation.x.org/cgi-bin/mailman/listinfo/members
>
>
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
>
>
>
> --
> Nuritzi Sanchez | She/HerSenior Open Source Program Manager | GitLab
> [lFQxFbGYJpI6]
>
> Create, Collaborate, and Deploy together
> Free Trial | Upgrade Now | Contact Support | Community | GitLab for Open
> Source
>
>
>
> --
> Nuritzi Sanchez | She/HerSenior Open Source Program Manager | GitLab
> [lFQxFbGYJpI6]
>
> Create, Collaborate, and Deploy together
> Free Trial | Upgrade Now | Contact Support | Community | GitLab for Open Source
--
----------------------------
Michael Schultheiss
E-mail: president at spi-inc.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://foundation.x.org/archives/members/attachments/20200325/09ebbbd1/attachment.sig>
More information about the members
mailing list