Sender: lojban@googlegroups.com
Received-SPF: pass (google.com: domain of gregorio.guidi@posteo.net designates 185.67.36.66 as permitted sender) client-ip=185.67.36.66;
Date: Tue, 07 Nov 2017 13:50:14 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <ee1d816d-a805-4ea0-a88f-c7c7847594bf@googlegroups.com>
References: <ef141db1-9811-4d44-8458-972ddffdd883@googlegroups.com> <78156dc5-1fb3-4e9d-992c-a8f30facc4fd@googlegroups.com> <CAJHgu=8BCaGqRkrD66zEtFiPkbG77EZ1u5N3uEO-+1bT96p1ig@mail.gmail.com> <d71e999e-78c0-48f5-9b6c-bf320ad478fc@googlegroups.com> <CAMKwHj1jizB+T9s6rAqPzMmSqFxC_eKsv3H10Ud2D4fRhZOH+A@mail.gmail.com> <2902921f-abf0-4482-b651-ad78066ec8d5@googlegroups.com> <ee1d816d-a805-4ea0-a88f-c7c7847594bf@googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [lojban] Re: CLL and modern Lojban
To: lojban <lojban@googlegroups.com>
From: Gregorio Guidi <gregorio.guidi@posteo.net>
Message-ID: <01C70FED-F7C2-4A61-A0F5-823DC93B0E8D@posteo.net>
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
X-Spam_score: -1.4
X-Spam_score_int: -13
X-Spam_bar: -

coi

I am a passive observer within the Lojban community, following on-and-off f=
or the past years and being interested particularly in the algorithmic aspe=
cts of Lojban structure and Lojban parsing.

I pick up the thread at this point juts to say that the issue raised resona=
tes a lot with me.

Trying to be very concrete: let's say I have some hours to dedicate to the =
project... is there some action that I could do that would increase the cha=
nces of reaching a CLL 2.0, or a 4th baseline grammar, or in general to hav=
e an updated specification of how "official" Lojban should be understood?

I would be happy to hear your suggestions!

mi'e la .greg.


On November 6, 2017 2:41:42 PM CET, guskant <gusni.kantu@gmail.com> wrote:
>Le lundi 6 novembre 2017 09:32:10 UTC, Benoit Neil a =C3=A9crit :
>> ...
>>
>> Anyway, if you say the BPFK works as I described, then I feel it's
>good=20
>> news. However:
>>
>>    - From afar, CLL seems a bit "stuck" at 1.1. Am I right? Do you
>think=20
>>    there would be some 1.x before 2.0 (ie. minor updates)?
>>   =20
>>
>
>You will find issues for CLL 1.2 here:
>
>https://github.com/lojban/cll/milestone/12
>
>The issues were already discussed by past lojbanists, and Cirko worked
>on=20
>introducing them into the next version of CLL. Gleki asked BPFK members
>for=20
>approval of them, and no one responded:
>
>https://groups.google.com/forum/#!topic/bpfk-list/jqVDF5z9LqA
>
>I, as a member of BPFK, am responsible for approving them, but I did
>not=20
>have enough time for that. Even if I have time for that, I can't
>imagine=20
>that I can approve any English texts written by an native English
>speaker=20
>because I'm very poor at English.
>
>You can freely approve them even if you are not a member of BPFK. If
>you=20
>want to do it as a member of BPFK, just post a message in Lojban to=20
>"bpfk-list" Google Group at the URL above, saying that you want to be a
>
>member, and you will be admitted.
>
>
>
>>    - As I said on #ckule (IRC), it might be a good idea to write on
>the=20
>>       front page the version of the CLL and its release date ;-)
>>   =20
>>
>
>I agree.
>
>=20
>
>>
>>    - Are some "betas" / "working branches" available (or will be=20
>>    available), so that people get a chance to have a look at before
>the=20
>>    official release?
>>    - Do you have in mind any plausible releases dates? I'm not asking
>for=20
>>    a contractual thing, of course! Just to have a vague idea in mind.
>>
>>
>
>You should find many branches at the github repository above. I have
>never=20
>contributed to the repository for some reasons:
>
>- the repository is governed by "the Lojban Coders' Group". I regard it
>as=20
>a kind of unofficial fans' group. Although the Group owns many official
>or=20
>pre-official contents, the owner(s) and the contributors are not equal
>to=20
>the members of BPFK or LLG. I am a member of BPFK and LLG, and I have
>never=20
>invited as a collaborator or an owner of the group. I once made a small
>
>pull request to another repository of the group, but it was ignored for
>
>almost one year.
>
>- I made some efforts on bpfk-list to remove grammatical difficulties
>or=20
>important logical defects, but we had always a stubborn defender of the
>
>current state. You can find such discussions with no conclusion in the=20
>bpfk-list Google Group above. Consequently, I have lost hope in
>updating=20
>CLL, and shifted myself to create a large personal commentary on the
>whole=20
>CLL ver.1.1.
>
>
>=20
>
>> Aside from that, and from my novice point of view, it seems that
>forks do=20
>> exist and seem significant. Isn't it a signal, asking for more
>updates in=20
>> the official CLL? Or do you feel that *some* people forking are
>simply=20
>> impatient having their proposals integrated? What is your point of
>view?
>>
>> la .sykyndyr.
>>
>> .i mi kamjunmre mi fi la .lojban. me'a lu .abu. pa li'u le ropno
>bangu bo=20
>> manri=20
>>
><https://en.wikipedia.org/wiki/Common_European_Framework_of_Reference_for_=
Languages>
>>
>
>
>lo'ai fi sa'ai fu le'ai ie pei=20
>i ji'a e'u lo'ai me'a lu .abu. pa li'u sa'ai li .abu pi'e pa le'ai ie
>pei
>
>=20
>
>> .i ganai la .lojban. pe mi toldra gi e'o o'anai ko dragau
>> (I self-evaluate my Lojban level as being less than A1, as for the
>CEFR=20
>>
><https://en.wikipedia.org/wiki/Common_European_Framework_of_Reference_for_=
Languages>.
>
>> Please correct my Lojban if I'm wrong!)
>>
>
>
>i na'i ma'i mi na'e toldra i po'o .au sajgau do lo xauzma be fi mi
>
>mi'e la guskant

--=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.