Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
still with placeholder dates until SFC approves too
|
|
Typos detected during the voting period which do not affect the
meaning of any sentence:
- s/agress/agrees/
- ... from time to time, ... (added "to time")
Acked-by: Ricardo Garcia <rgarcia@igalia.com> (for the election commitee)
|
|
Just for easier reading
v2: Rebase since members the change to special voting criteria did not
pass.
|
|
This time we did not forget about that, unlike with the SPI merger.
Only substantial edit SFC suggested is dropping the rules for changes
at the very bottom, becuase that's already redudant with the
by-laws/governance rules.
|
|
Will be updated if the bylaw changes pass with the new date.
|
|
SFC suggested this, but under the CoC policy the Board (Governance
Committee in the future) enacted this is already the case. But it's
always good to be explicit.
|
|
- Expand DRM
- Add some missing commas in the Notices section
- Style fixes SFC suggested in a few different places
- A pile of typos
|
|
Replace he/him/his with they/them/their and drop the
generic masculine line.
Part of general cleanups SFC suggested.
Split out from all other typo fixes and minor cleanups to keep the
latter more readable.
|
|
- Add SFC terminlogy
- drop the sentence that X.Org membership doesn't include SPI membership
- Add SFC conflict of interest policy to Member Declaration of Interest
- replace SPI with SFC including footnotes and links
- Drop section on signing contracts, only SFC does that
- Drop/adjust of Financial Liaison section, Change Checks/Drafts/etc.
section and Banking Arrangements section to put SFC fully in charge
of our financial assets
- Add Relationship to SFC Fiscal Sponsorship Agreement section.
Requested by SFC to make it clear our rules are subordinate to any
governance rules SFC has, and that any changes also need to be
approved by SFC before they can be enacted.
These are all the functional core changes required by SFC so we can
join them as a project.
|
|
or any other law, since legally only SFC exists with any powers. We've
tried to reconstruct the history of why this Act has specific
meanings, but could not find anyone who was around back then. This
might be leftovers from quite a few X.org reconstitutions ago.
|
|
- s/By-Laws/Governance Rules/
- Rename X.org Foundation to X.org Project
- s/Foundation/Project
- s/Board of Directors/X.Org Governance Committee/
- s/Director/Leadership Member/
- s/Officer/Administrative Member/
- s/Secretary/Authorized Representative/
- s/Treasurer/Financial Liaison/
- "lesser committees" instead of just committees
These have all been requested by SFC to avoid confusion with SFC's
functions and bodies.
|
|
|
|
The leadership of freedesktop.org (fd.o) has recently expressed interest
in having an elected governing body. Given the tight connection between
fd.o and X.Org and the fact that X.Org has such a governing body it
seemed obvious to consider extending X.Org's mandate to fd.o.
Quite a bit of background on fd.o leading up to this has been covered by
Daniel Stone at XDC 2018 [2] and was covered really well by Jake Edge of
LWN [1].
One question that is briefly addressed in the LWN article and was
thoroughly discussed by members of the X.Org boards, Daniel Stone, and
others in hallway discussions is the question of whether to extend the
X.Org membership to projects hosted on fd.o but outside the purpose of
the X.Org foundation as enacted in its bylaws.
Most people I talked to would prefer not to dilute X.Org's mission and
extend membership only to contributors of projects that follow X.Org's
purpose as enacted in its bylaws. Other projects can continue to be
hosted on fd.o but won't receive X.Org membership for the mere reason of
being hosted on fd.o.
[1] https://lwn.net/Articles/767258/
[2] https://youtu.be/s22B3E7rUTs
v3:
- Clarify what support of fd.o projects entails without formalizing a
two-tier system for fd.o projects that fall under X.Org's mandate and
those who don't
- Add link to Daniel's talk at XDC2018
v2:
- Subject line that better describes the intention
- Briefly describe reasons behind this change
- Drop expanding membership eligibility
Acked-by: Daniel Stone <daniel@fooishbar.org>
|
|
|
|
Reviewed-by: Bryce Harrington <bryce@osg.samsung.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Note the clunky 'cut -c 2-' bit is to strip off the leading backslash.
I couldn't figure out a better way to deal with that, since I need to
escape the % char in the git-log command, but the escape char still gets
passed through to the command and ends up in the .info file.
Currently the date shows up like:
Thu, 2 Feb 2017 16:02:08 -0500
maybe we want to tweak that.
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Reviewed-by: Alex Deucher <alexdeucher@gmail.com>
|
|
Reviewed-by: Bryce Harrington <bryce@osg.samsung.com>
Reviewed-by: Alex Deucher <alexdeucher@gmail.com>
|
|
|
|
Reviewed-by: Alex Deucher <alexdeucher@gmail.com>
|
|
Reviewed-by: Alex Deucher <alexdeucher@gmail.com>
|
|
Reviewed-by: Alex Deucher <alexdeucher@gmail.com>
|
|
Based on MemberAgreement02Apr2004.pdf
(md5sum: 649027b96db32abee63c5ee6844c270c)
|
|
Since we'll reuse it for member's agreement doc
|
|
|
|
This is not necessary anymore because all the transactions need to be approved
by SPI. The treasurer's role would become "the person who is regularly in
contact with SPI's treasurer". This person has no authority and cannot be
in legal trouble so everything is fine.
|
|
|
|
This line states when the bylaws were accepted by the members, not the board.
Change it to the last date of the election period.
|
|
|
|
|
|
|
|
Suggested by Egbert Eich
|
|
|
|
|
|
|
|
|
|
Thanks Emil ;)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|