From: "Karen M. Sandler" <karen@sfconservancy.org>
To: Overseers mailing list <overseers@sourceware.org>
Subject: Re: SFC offers project membership to Sourceware; three video-chat discussion times with SFC available
Date: Sat, 10 Sep 2022 13:55:47 -0400 [thread overview]
Message-ID: <8f4b73fb87d4619126f3594041e8bb22@sfconservancy.org> (raw)
In-Reply-To: <1d8df057d6a7891e7af38de89a17b99f@sfconservancy.org>
On 2022-09-09 10:55, Karen M. Sandler via Overseers wrote:
> On 2022-09-08 15:16, Daniel Pono Takamori via Overseers wrote:
>
>> We'd like to have a meeting where anyone can join and ask questions
>> about the agreement or anything else about joining SFC. We'll be
>> hosting
>> 3 calls to let community members join when is best for them: 15:00 UTC
>> Friday, 18:00 UTC Saturday and 17:00 UTC Monday on BigBlueButton.
>> We'll
>> post the links to this mailing list right before the calls.
The second of these meetings is happening in about 5 minutes at the top
of the hour!
You can join here:
https://bbb.sfconservancy.org/b/kar-yiq-pkx-amt
To join this meeting by phone, dial:
+1-718-247-9666
Then enter 27353 as the conference PIN number.
I am including the notes from the first one below.
If you can't make this one, we're doing another at 17:00 UTC Monday also
on BigBlueButton.
> And here are the links to the agreements:
>
>> https://sfconservancy.org/docs/sponsorship-agreement-template.pdf
>> https://sfconservancy.org/docs/sponsorship-agreement-template.odt
>>
>> We're in the middle of updating our template to improve it a little
>> bit,
>> but there are no substantive changes. The most important section is
>> building the governance section 6, for which the template has various
>> suggested structures.
>
Rough Notes from previous meeting:
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.
next prev parent reply other threads:[~2022-09-10 17:55 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 [this message]
2022-09-10 22:32 ` SFC video-chat discussion meeting notes Mark Wielaard
2022-09-12 16:34 ` 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=8f4b73fb87d4619126f3594041e8bb22@sfconservancy.org \
--to=karen@sfconservancy.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).