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