public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Subject: SFC video-chat discussion meeting notes
Date: Sun, 11 Sep 2022 00:32:00 +0200	[thread overview]
Message-ID: <Yx0QYHM17DtXltTN@wildebeest.org> (raw)
In-Reply-To: <8f4b73fb87d4619126f3594041e8bb22@sfconservancy.org>

Here are the rough notes from the first two meetings.

The SFC will host another one at 17:00 UTC Monday also on BigBlueButton.
The link will be posted on the overseers mailinglist on Monday.

> Meeting 15:00 UTC, September 9
> 
> SFC staff shared links to the Fiscal Sponsorship Agreement template
> 
> Fiscal sponsorship agreement talks about the structure, what's the best way
> to describe it?
> Concern: is defining the scope of the project difficult? There are legacy
> projects, etc
> Projects hosted by Sourceware will not become SFC projects
> 
>     * may need to write this into the agreement
> 
> Sourceware is well resourced enough to bring more projects on
> 
> Discussion about longevity and succession of Sourceware
> Making sure that governance of the project is independent from any company
> 
> Discussed possible people to join the leadership committee
> Possibly anyone who has root should be on the committee?
> 
> SFC recommends reaching out personally to overseers who have been active
> over the last 10 years to make sure they've seen the discussion about
> joining SFC and if they'd like to be involved.

Meeting 18:00 UTC September 10

Reached out to a few people personally who have a longtime involvment
in projects and/or sourceware to see if they would be interested in
joining the PLC

Do member projects talk to each other?

  Sometimes they do and there are a few mailing lists to do it but in
  practice there hasn't been that much cross-project chatter. Recently
  there was a great conversation amongst our projects about
  GiveUpGitHub.org.

  SFC will announce soon an in person event that may be a good venue
  for more of this

Could SFC help hire logo or web designers?

    Definitely, we've hired multiple people in these roles in the last
    few years and will continue to do so.

    We like to favor small companies or individuals who use software
    freedom tools, but have also hired larger companies.

Conflict of interest policy: it is long, how will that work out with
so many projects being hosted?
https://sfconservancy.org/projects/policies/conflict-of-interest-policy.html

    The policy is really only an issue when the person is going to
    benefit financially from the project (or related situation)

    In practice this works out easily, conflicted parties simply
    recuse themselves from the relevant discussion

How do in kind donations work?

    Depending on the donation, we may need to track it on our books

    Charitable deductions are possible where helpful for companies

    Normally can evaluate logo placement or other sponsorship program

    Organizations could be encouraged to continue donating in-kind
    resources by formal recognition

Discussion about other fiscal sponsor options, what SFC offers and
what it doesn't, and different

    historical trajectories of projects that look for large amounts of
    funding vs. those who focus on long term survivability

  reply	other threads:[~2022-09-10 22:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 18:03 proposing Sourceware as Software Freedom Conservancy member project Frank Ch. Eigler
2022-09-01 14:19 ` Elena Zannoni
2022-09-01 18:10   ` Christopher Faylor
2022-09-02 10:14   ` Mark Wielaard
2022-09-01 18:45 ` Corinna Vinschen
2022-09-01 18:54   ` Frank Ch. Eigler
2022-09-02 10:51   ` Mark Wielaard
2022-09-02 11:47 ` Mark Wielaard
2022-09-05 12:20 ` Dodji Seketeli
2022-09-08 19:16 ` SFC offers project membership to Sourceware; three video-chat discussion times with SFC available Daniel Pono Takamori
2022-09-09 14:55   ` Karen M. Sandler
2022-09-10 17:55     ` Karen M. Sandler
2022-09-10 22:32       ` Mark Wielaard [this message]
2022-09-12 16:34         ` SFC video-chat discussion meeting notes Daniel Pono Takamori
2022-09-12 17:05           ` Daniel Pono Takamori
2022-09-12 19:09             ` Daniel Pono Takamori

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=Yx0QYHM17DtXltTN@wildebeest.org \
    --to=mark@klomp.org \
    --cc=overseers@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).