All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>
To: "qemu\@sfconservancy.org" <qemu@sfconservancy.org>
Cc: , QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Should we apply for GitLab's open source program?
Date: Wed, 16 Sep 2020 16:39:55 -0700	[thread overview]
Message-ID: <87zh5puw8k.fsf@ebb.org> (raw)
In-Reply-To: <20200908141701.GB7154@stefanha-x1.localdomain> (Stefan Hajnoczi's message of "Tue, 8 Sep 2020 15:17:01 +0100")

> On Fri, Sep 04, 2020 at 04:35:34PM +0100, Alex Bennée wrote:
>> Given our growing reliance on GitLab and the recent announcement about
>> free tier minutes:
>> 
>>   https://about.gitlab.com/pricing/faq-consumption-cicd/
>> 
>> is it time we officially apply for GitLab's Open Source Program:
>> 
>>   https://about.gitlab.com/solutions/open-source/program/

Sorry for my late response on this thread.  Since GitLab is requiring that
organizations be non-profits as part of this program, Conservancy will need
to coordinate your application with you as we're the parent non-profit for
this purpose.

Given my late reply, you may already be coordinating with my colleague Brett
about this, but I'll check in with him tomorrow to verify.

One thing to note is that my understanding is that most of what you're
getting access to through this program is proprietary software features that
GitLab offers as add-ons.  I really encourage you as a project not enable
such features, as ultimately you'll probably start to rely on them, and then
you'll be effectively relying on proprietary software infrastructure to
develop your project.

I'm also curious: is there something you need now from the GitLab software
that self-hosting might improve?
-- 
Bradley M. Kuhn - he/him
Policy Fellow & Hacker-in-Residence at Software Freedom Conservancy
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter


  reply	other threads:[~2020-09-17  0:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 15:35 Should we apply for GitLab's open source program? Alex Bennée
2020-09-04 16:08 ` Daniel P. Berrangé
2020-09-21 14:03   ` Daniel P. Berrangé
2020-09-21 14:39     ` Paolo Bonzini
2020-09-08 14:17 ` Stefan Hajnoczi
2020-09-16 23:39   ` Bradley M. Kuhn [this message]
2020-09-17  7:21     ` Paolo Bonzini
2020-09-17  8:32       ` Alex Bennée
2020-09-17  9:19         ` Daniel P. Berrangé
2022-02-17 11:42 ` Daniel P. Berrangé

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zh5puw8k.fsf@ebb.org \
    --to=bkuhn@sfconservancy.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu@sfconservancy.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.