Sender: lojban@googlegroups.com
Date: Tue, 21 Nov 2017 14:04:05 -0800 (PST)
From: sukender1@gmail.com
To: lojban <lojban@googlegroups.com>
Message-Id: <322158ae-e6ad-49b0-9dba-0dddf71609f1@googlegroups.com>
In-Reply-To: <4aefe693-e504-4518-09e5-d82a360c333c@posteo.net>
References: <ef141db1-9811-4d44-8458-972ddffdd883@googlegroups.com>
 <78156dc5-1fb3-4e9d-992c-a8f30facc4fd@googlegroups.com>
 <SY3PR01MB0873C992D556B090F308980EEB510@SY3PR01MB0873.ausprd01.prod.outlook.com>
 <CACf3dPnmCuGXQtxQOOrP9T9pDthhthx3rnoCdaFoai+fM8M6Wg@mail.gmail.com>
 <SY3PR01MB08733806D926A36CF1726EB0EB560@SY3PR01MB0873.ausprd01.prod.outlook.com>
 <CACf3dPncGvkjQjbxL4MV_omG0R-e66V1CDcZFrt2hVU8iYWf0w@mail.gmail.com>
 <963393d6-a9f1-4232-be13-b4ee76eb69e1@googlegroups.com>
 <e7d4a3d5-4cd9-435d-bd3f-90c011172a10@googlegroups.com>
 <A9240133-B357-4747-941D-BF28F3CCAE8C@free.fr>
 <eb1c7ed2-ec39-476d-b9dc-11f835e9623c@googlegroups.com>
 <ae9b9cae-0420-475b-a0e8-8efb3452ef1e@googlegroups.com>
 <7d063690-0550-45d6-9779-3334ac8e17b5@googlegroups.com>
 <e3a723d2-8b62-4338-bc8a-147f03d6d3f4@googlegroups.com>
 <4aefe693-e504-4518-09e5-d82a360c333c@posteo.net>
Subject: Re: [lojban] Re: CLL and modern Lojban
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_9087_1137756880.1511301845588"
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
X-Spam_score: -1.3
X-Spam_score_int: -12
X-Spam_bar: -

------=_Part_9087_1137756880.1511301845588
Content-Type: multipart/alternative; 
	boundary="----=_Part_9088_287520258.1511301845588"

------=_Part_9088_287520258.1511301845588
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Le mardi 21 novembre 2017 22:10:24 UTC+1, Gregorio Guidi a =C3=A9crit :
>
> On 11/21/2017 03:08 PM, suke...@gmail.com <javascript:> wrote:=20
> > ***=20
> >=20
> > @all:=20
> > Now about submissions to update the CLL... Let's imagine a second we=20
> > have an unique and active board (say "LLGBPFKCoders", or whatever),=20
> > and adequate tools. What would be an efficient submission protocol?=20
> > Here are two drafts:=20
> >=20
> > [...]=20
> >=20
> > That's even simpler, but removes the ability to make tiny changes once=
=20
> > validated. What's your opinion?=20
> >=20
>
> The community should be able to send pull requests with proposed changes=
=20
> to the CLL. The LLG, as owner of the CLL, should appoint a recognized=20
> member of the community as release manager in charge of the official=20
> repository, with the power to accept/reject patches, set a roadmap and=20
> make releases (CLL 1.2, 1.3, 2.0, ...).=20
>
> Just my 2 cents.=20
>
> mi'e la .greg.=20
>


What I feel interesting is centralizing stuff within the LLG, which is the=
=20
logical (historical?) choice I guess. And the "release manager" is=20
something surely interesting too.
But I fear this proposal would turn into another dead-end. We may end with=
=20
someone inactive, or which blocks anything, as currently.

I'm thinking about giving more decisions to the community, but as Gleki=20
pointed out, most may just be unable to make a choice. I will integrate=20
your ideas in my text proposal.
Thanks.

--=20
You received this message because you are subscribed to the Google Groups "=
lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at https://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

------=_Part_9088_287520258.1511301845588
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br>Le mardi 21 novembre 2017 22:10:24 UTC+1, Gregorio=
 Guidi a =C3=A9crit=C2=A0:<blockquote class=3D"gmail_quote" style=3D"margin=
: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">On 1=
1/21/2017 03:08 PM, <a href=3D"javascript:" target=3D"_blank" gdf-obfuscate=
d-mailto=3D"oRqXIIu0AwAJ" rel=3D"nofollow" onmousedown=3D"this.href=3D&#39;=
javascript:&#39;;return true;" onclick=3D"this.href=3D&#39;javascript:&#39;=
;return true;">suke...@gmail.com</a> wrote:
<br>&gt; ***
<br>&gt;
<br>&gt; @all:
<br>&gt; Now about submissions to update the CLL... Let&#39;s imagine a sec=
ond we=20
<br>&gt; have an unique and active board (say &quot;LLGBPFKCoders&quot;, or=
 whatever),=20
<br>&gt; and adequate tools. What would be an efficient submission protocol=
?=20
<br>&gt; Here are two drafts:
<br>&gt;
<br>&gt; [...]
<br>&gt;
<br>&gt; That&#39;s even simpler, but removes the ability to make tiny chan=
ges once=20
<br>&gt; validated. What&#39;s your opinion?
<br>&gt;
<br>
<br>The community should be able to send pull requests with proposed change=
s=20
<br>to the CLL. The LLG, as owner of the CLL, should appoint a recognized=
=20
<br>member of the community as release manager in charge of the official=20
<br>repository, with the power to accept/reject patches, set a roadmap and=
=20
<br>make releases (CLL 1.2, 1.3, 2.0, ...).
<br>
<br>Just my 2 cents.
<br>
<br>mi&#39;e la .greg.
<br></blockquote><div><br></div><div><br></div><div>What I feel interesting=
 is centralizing stuff within the LLG, which is the logical (historical?) c=
hoice I guess. And the &quot;release manager&quot; is something surely inte=
resting too.</div><div>But I fear this proposal would turn into another dea=
d-end.=C2=A0We may end with someone inactive, or which blocks anything, as =
currently.<br></div><div><br></div><div>I&#39;m thinking about giving more =
decisions to the community, but as Gleki pointed out, most may just be unab=
le to make a choice. I will integrate your ideas in my text proposal.</div>=
<div>Thanks.</div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;lojban&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:lojban+unsubscribe@googlegroups.com">lojban+unsub=
scribe@googlegroups.com</a>.<br />
To post to this group, send email to <a href=3D"mailto:lojban@googlegroups.=
com">lojban@googlegroups.com</a>.<br />
Visit this group at <a href=3D"https://groups.google.com/group/lojban">http=
s://groups.google.com/group/lojban</a>.<br />
For more options, visit <a href=3D"https://groups.google.com/d/optout">http=
s://groups.google.com/d/optout</a>.<br />

------=_Part_9088_287520258.1511301845588--

------=_Part_9087_1137756880.1511301845588--