dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hutterer <peter.hutterer-Pf4JEFdB4epeoWH0uzbU5w@public.gmane.org>
To: Harry Wentland <harry.wentland-5C7GfCeVMHo@public.gmane.org>
Cc: xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.org,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	wayland-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	members@x.org,
	mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	xorg-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
Subject: Re: [RFC] Allow fd.o to join forces with X.Org
Date: Tue, 16 Oct 2018 16:17:04 +1000	[thread overview]
Message-ID: <20181016061704.GA6771@jelly> (raw)
In-Reply-To: <20181015144924.22734-1-harry.wentland-5C7GfCeVMHo@public.gmane.org>

On Mon, Oct 15, 2018 at 10:49:24AM -0400, Harry Wentland wrote:
> 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 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/
> 
> v2:
>  - Subject line that better describes the intention
>  - Briefly describe reasons behind this change
>  - Drop expanding membership eligibility
> ---
> 
> We're looking for feedback and comments on this patch. If it's not
> widely controversial the final version of the patch will be put to a
> vote at the 2019 X.Org elections.
> 
> The patch applies to the X.Org bylaws git repo, which can be found at
> https://gitlab.freedesktop.org/xorgfoundation/bylaws
> 
> Happy commenting.
> 
> Harry
> 
> bylaws.tex | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/bylaws.tex b/bylaws.tex
> index 4ab35a4f7745..44ff4745963b 100644
> --- a/bylaws.tex
> +++ b/bylaws.tex
> @@ -14,7 +14,7 @@ BE IT ENACTED AND IT IS HEREBY ENACTED as a By-law of the X.Org Foundation
>  
>  The purpose of the X.Org Foundation shall be to:
>  \begin{enumerate}[(i)\hspace{.2cm}]
> -	\item Research, develop, support, organize, administrate, standardize,
> +	\item \label{1} Research, develop, support, organize, administrate, standardize,
>  	promote, and defend a free and open accelerated graphics stack. This
>  	includes, but is not limited to, the following projects: DRM, Mesa,
>  	Wayland and the X Window System,
> @@ -24,6 +24,11 @@ The purpose of the X.Org Foundation shall be to:
>  
>  	\item Support and educate the general community of users of this
>  	graphics stack.
> +
> +	\item Support free and open source projects through the freedesktop.org
> +	infrastructure. For projects outside the scope of item (\ref{1}) support
> +	extends to project hosting only.
> +

Yes to the idea but given that the remaining 11 pages cover all the legalese
for xorg I think we need to add at least a section of what "project hosting"
means. Even if it's just a "includes but is not limited to blah".  And some
addition to 4.1 Powers is needed to spell out what the BoD can do in regards
to fdo. 

Cheers,
   Peter


>  \end{enumerate}
>  
>  \article{INTERPRETATION}
> -- 
> 2.19.1
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

  parent reply	other threads:[~2018-10-16  6:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 14:49 [RFC] Allow fd.o to join forces with X.Org Harry Wentland
     [not found] ` <20181015144924.22734-1-harry.wentland-5C7GfCeVMHo@public.gmane.org>
2018-10-15 16:45   ` Eric Engestrom
2018-10-16  6:17   ` Peter Hutterer [this message]
2018-10-17 12:05     ` Daniel Stone
2018-10-17 12:37       ` Daniel Vetter
     [not found]         ` <CAKMK7uHoOqC7hH9PemUDuzU8Nmuo7hDij+PTGdiBJH_AQcsqvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-26  0:13           ` Peter Hutterer
2018-10-26 10:57             ` Daniel Vetter
2018-10-26 11:08               ` Daniel Stone
2018-10-26 11:22                 ` Daniel Vetter
     [not found]                   ` <CAKMK7uGi_yG6PDWBvo55j=ooJbnhadaOr7f6GHu9Uq9_Ge6rvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-29 13:24                     ` Wentland, Harry
2018-10-29 13:46                       ` Daniel Vetter

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=20181016061704.GA6771@jelly \
    --to=peter.hutterer-pf4jefdb4epeowh0uzbu5w@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=harry.wentland-5C7GfCeVMHo@public.gmane.org \
    --cc=members@x.org \
    --cc=mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=wayland-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=xorg-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org \
    --cc=xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.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