Received: from mail-oi1-f184.google.com ([209.85.167.184]:48682) by stodi.digitalkingdom.org with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from ) id 1h1Vxw-00059T-9q; Wed, 06 Mar 2019 04:48:11 -0800 Received: by mail-oi1-f184.google.com with SMTP id p65sf6283459oib.15; Wed, 06 Mar 2019 04:48:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe; bh=/tWaQxqymSRwt01qwoAtsh4QmMPwULYNQJ6iin/aC0c=; b=sQdqgy2BVxsC88QdsrXPlRhI/ZQGlqqM1UGRIydqAkF6GMtH2UXmW9hgoXNWklmNM2 gd75fOi7g2nuzVl70THLbGXkdxE5zkZg6MUpsIHy6E3fnFTwuF9zUE6f5EFpT5UaVI8m LeVXn8dh1v50x8iU8D2/GG6tTnB0vPd+WUjhemoCyNtrNo+qjwtvqZjupCSTobqlXIUh pPd5fcmLHkENNnjiBr1lJHwOLUaOH8UTOWqUgrUyopun0Kr7ZTVAoorrai9abc12JvDN Cgesk+1CmIcfclsOqys+VdqjNtr+eKsyWQm+asSnFFcFSt0wj0oIv4WUTs8135DscH34 fE6w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=/tWaQxqymSRwt01qwoAtsh4QmMPwULYNQJ6iin/aC0c=; b=WzSBo5O31fbvuYNdFRW4AIVTh6AKrqrIGnu817jTyPJ9eNjewqp1jt5ewM1tA567NP za9qQDcC0ap76UNV5vVo+MPbia1s1ztvtVC6bqTdjb652KvN+0hGpjZNb8e5XemEcRXn kfDmf+byLwNkEf1pxKV33mXD01haS+BAOwJBr/d9rDvlLSQSngNIGHstlvp5Zuhn56Lb jrdeBpqs6npSO/7YRDLZJ/MU2AY4H+Qr8P22z09vgTgUKXvZvg2TP9kILimvG9kCsW+e sbz84ZbfbDcDzQGpMDI6eL11/d1bSMyM1BxbO+7jpLJAZlwqATgNucy1QMugIs4zrvD6 JzHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=sender:x-gm-message-state:date:from:to:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=/tWaQxqymSRwt01qwoAtsh4QmMPwULYNQJ6iin/aC0c=; b=aXvQc+kQvSkkXao4ScFJRSv30TV+iXEOpJMN8jCQceeLGosD2unrr8QMVUkKxJBjFt CVhgPxxWVtWNa6np2K6mPQfOj/C07/M2AKFheHdyCiEbW4qAn0QdyfJZ26eKB6VnYSzJ cDWbrfsSAwZ1BcDcvVRfBewQRxG+roQgh8chPDLW8+JZBjq50wJ1P0bH59ZX8+7jd1TT yyCYJA5P5WjKoR8i2SkMEJd1I/gJ/t4gFgSvuXdJJ85oVucxWXFUVJMCuVGVK/SigVbb yOlkQPxMhZ1oInwd8AUFP3ctZjYdaFGYGOKMEmSbLXGjaliCIS7kszBq08mTdbyYnYpk 6b9w== Sender: bpfk-list@googlegroups.com X-Gm-Message-State: APjAAAWknvOZID8DtQn4yROLFGe8UkZOI5OXjioWm3BhyOfap9wU5ViH F3cbsopACMxn77vJk7DDOUY= X-Google-Smtp-Source: APXvYqxejIwTFaRn1ZlmXghtpYfG224PlpImYT0vBtkJOUOQjq8DCshJo/BuyZJFXAPKvv0yOLWHFA== X-Received: by 2002:aca:5143:: with SMTP id f64mr1539919oib.137.1551876481795; Wed, 06 Mar 2019 04:48:01 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 2002:aca:3189:: with SMTP id x131ls439385oix.2.gmail; Wed, 06 Mar 2019 04:48:01 -0800 (PST) X-Received: by 2002:aca:d7c3:: with SMTP id o186mr1574202oig.28.1551876481069; Wed, 06 Mar 2019 04:48:01 -0800 (PST) Date: Wed, 6 Mar 2019 04:48:00 -0800 (PST) From: guskant To: BPFK Message-Id: In-Reply-To: References: Subject: [bpfk] Re: Salutations! MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_224_132505069.1551876480568" X-Original-Sender: gusni.kantu@gmail.com Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: X-Spam-Checked-In-Group: bpfk-list@googlegroups.com X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -2.8 (--) X-Spam_score: -2.8 X-Spam_score_int: -27 X-Spam_bar: -- Content-Length: 12064 ------=_Part_224_132505069.1551876480568 Content-Type: multipart/alternative; boundary="----=_Part_225_723998563.1551876480569" ------=_Part_225_723998563.1551876480569 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable coi la eris I once insisted that any non-fluent lojban speakers may join BPFK:=20 https://groups.google.com/d/msg/bpfk-list/SXxIpMLgL5s/6aS8ec5oCgAJ I wrote:=20 i pe'i lo tcini no'u lo nu kakne lo nu pilno la lojban cu na'e sarcu lo nu= =20 me byfy kei sei ku'i ka'e banzu tcini i lo canaiba pilno be la lojban cu .e'a kansa mi'o lo nu jdice fi lo ka=20 bangu=20 i la'a lo ji'a no'e tavla fo la lojban cu kakne lo nu jimpe lo lojbo jufra= =20 kei sepi'o lo fanva tutci a lo vlaste Translation: I think that the condition of ability of speaking lojban is not necessary= =20 for being a member of bpfk, though it can be a sufficient condition. I allow that our activity of defining the language property is accompanied= =20 by people who don't but will do use lojban. Perhaps people who don't speak lojban much have also the ability of=20 understanding lojban statements using translation tools or dictionaries. To say more precisely, I don't oppose myelf to using English for discussing= =20 the structure of lojban, both about syntax or semantics.=20 I am not very fluent in English, but I can use dictionaries for=20 participating the discussion. The difference is only that who has difficulties in participating the=20 discussion: ones who are not fluent in lojban, or ones who are not fluent= =20 in English. I belong not to the former but to the latter, but I will allow= =20 to discuss in English, because fluent English speakers are majority among= =20 lojban users, while fluent lojban speakers are minority among lojban users. However, please be noted that I oppose myself to using English for defining= =20 lojban words. I once wrote the reason why the lojban words must be defined= =20 by lojban: https://groups.google.com/d/msg/lojban/hAfNwSdXl4A/iiIA8XV9C9gJ As for using Github, I suggested it in an LLG meeting when I was a member= =20 of it. It is a good method, but you need to define clearly who are=20 responsible for pulling requests, adding a member, defining the power of=20 each member. Otherwise the result will be similar to the unsystematic group= =20 organized by some unknown volunteers: https://github.com/lojban . They once= =20 published a feature under discussion as if it were an official feature. mi'e la guskant Le mercredi 6 mars 2019 04:41:03 UTC, la .eris. a =C3=A9crit : > > Coi rodo, > > I just spent half an hour writing out a long post with lots attitudinals= =20 > and humor and the like, but it appears to have disappeared into the ether= ,=20 > so this will be rather brief. There is currently discussion at the LLG=20 > Members Meeting about what to do with the BPFK. Instructions for how to g= et=20 > to that meeting are posted in many places. A summary of my proposal follo= ws. > > I want to create an RFC process, whereby anyone could make proposals (in= =20 > English) for changes to Lojban. There would then be public discussion and= a=20 > decision by some body, possibly the BPFK and possibly someone else. I'm n= ot=20 > some radical who wants to change everything. Almost all of the language= =20 > change proposals that I particularly want done aren't of my creation. For= =20 > instance, I'd like to merge CAI into UI. I also kind of like the NOIhA=20 > proposal and the indicator ko'oi, among other such changes. I don't want = to=20 > add malglico or ruin everything; I just want somewhere that language chan= ge=20 > could happen (with peer review and at least semi-official adoption, not= =20 > just by adding an experimental cmavo and waiting to see if they catch on= =20 > without any hope of them ever entering the official language). The detail= s=20 > of the RFC process haven't been determined yet, although I have some stro= ng=20 > opinions (to use GitHub, for one). > > I would also like to open up membership in the BPFK to people who aren't= =20 > fluent. There are some people, like me, who haven't become fluent in Lojb= an=20 > yet, but would still like to have a voice in language discussions and can= =20 > still be trusted to participate productively without breaking everything.= =20 > This would mean that discussions would be in English, which is really a= =20 > necessity anyway, since the RFCs would be in English and not everyone=20 > submitting ideas would be able to speak English. > > I'd also like to get documentation, including the CLL, up to date. I=20 > propose that the BPFK (or its successor) assume responsibility for=20 > maintaining documentation. There are several people who have expressed=20 > interest in participating under something like my suggestion, and I expec= t=20 > that some of them will also help update documentation if that is part of= =20 > the job.=20 > > This is not the original posting of my proposal, and many arguments and= =20 > counterarguments have already been raised. I hope you will join the meeti= ng=20 > and comment, or become active there if you are currently present but=20 > inactive. > > mi'e .eris. > --=20 You received this message because you are subscribed to the Google Groups "= BPFK" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list+unsubscribe@googlegroups.com. To post to this group, send email to bpfk-list@googlegroups.com. Visit this group at https://groups.google.com/group/bpfk-list. For more options, visit https://groups.google.com/d/optout. ------=_Part_225_723998563.1551876480569 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
coi la eris

I once insisted = that any non-fluent lojban speakers may join BPFK:
https://g= roups.google.com/d/msg/bpfk-list/SXxIpMLgL5s/6aS8ec5oCgAJ

I wrote:
i pe'i lo tcini no'u lo nu kak= ne lo nu pilno la lojban cu na'e sarcu lo nu me byfy kei sei ku'i k= a'e banzu tcini
i lo canaiba pilno be la lojban cu .e'a k= ansa mi'o lo nu jdice fi lo ka bangu=C2=A0
i la'a lo ji'a = no'e tavla fo la lojban cu kakne lo nu jimpe lo lojbo jufra kei sepi= 9;o lo fanva tutci a lo vlaste

Translation:
<= div>I think that the condition of ability of speaking lojban is not necessary for being a member of bpfk, though it can be a sufficient condition.
=
I allow that our activity of defining the language property is accompa= nied by people who don't but will do use lojban.
Perhaps people who don't speak lojban much have also the ability of understand= ing=20 lojban statements using translation tools or dictionaries.

To say more precisely, I don't oppose myelf to using English for=20 discussing the structure of lojban, both about syntax or semantics.
I am not very fluent in English, but I can use dictionaries for par= ticipating the discussion.
The difference is only that who has difficulties in participating the=20 discussion: ones who are not fluent in lojban, or ones who are not=20 fluent in English. I belong not to the former but to the latter, but I=20 will allow to discuss in English, because fluent English speakers are=20 majority among lojban users, while fluent lojban speakers are minority=20 among lojban users.

However, please be=20 noted that I oppose myself to using English for defining lojban words. I once wrote the reason why the lojban words must be defined by lojban:
https://groups.google.com/d/msg/lojban/hAfNwSdXl4A/iiIA8XV9C9gJ

As for using Github, I suggested it in an LLG meeting when I was a member=20 of it. It is a good method, but you need to define clearly who are=20 responsible for pulling requests, adding a member, defining the power of each member. Otherwise the result will be similar to the unsystematic=20 group organized by some unknown volunteers: https://github.com/lojban .=20 They once published a feature under discussion as if it were an official feature.

mi'e la guskant

=
Le mercredi 6 mars 2019 04:41:03 UTC, la .eris. a =C3=A9crit=C2=A0:
Coi rodo,
I just spent half an hour writing out a long post with lots att= itudinals and humor and the like, but it appears to have disappeared into t= he ether, so this will be rather brief. There is currently discussion at th= e LLG Members Meeting about what to do with the BPFK. Instructions for how = to get to that meeting are posted in many places. A summary of my proposal = follows.

I want to create an RFC process, whereby = anyone could make proposals (in English) for changes to Lojban. There would= then be public discussion and a decision by some body, possibly the BPFK a= nd possibly someone else. I'm not some radical who wants to change ever= ything. Almost all of the language change proposals that I particularly wan= t done aren't of my creation. For instance, I'd like to merge CAI i= nto UI. I also kind of like the NOIhA proposal and the indicator ko'oi,= among other such changes. I don't want to add malglico or ruin everyth= ing; I just want somewhere that language change could happen (with peer rev= iew and at least semi-official adoption, not just by adding an experimental= cmavo and waiting to see if they catch on without any hope of them ever en= tering the official language). The details of the RFC process haven't b= een determined yet, although I have some strong opinions (to use GitHub, fo= r one).

I would also like to open up membership in= the BPFK to people who aren't fluent. There are some people, like me, = who haven't become fluent in Lojban yet, but would still like to have a= voice in language discussions and can still be trusted to participate prod= uctively without breaking everything. This would mean that discussions woul= d be in English, which is really a necessity anyway, since the RFCs would b= e in English and not everyone submitting ideas would be able to speak Engli= sh.

I'd also like to get documentation, includ= ing the CLL, up to date. I propose that the BPFK (or its successor) assume = responsibility for maintaining documentation. There are several people who = have expressed interest in participating under something like my suggestion= , and I expect that some of them will also help update documentation if tha= t is part of the job.=C2=A0

This is not the origin= al posting of my proposal, and many arguments and counterarguments have alr= eady been raised. I hope you will join the meeting and comment, or become a= ctive there if you are currently present but inactive.

=
mi'e .eris.

--
You received this message because you are subscribed to the Google Groups &= quot;BPFK" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list= +unsubscribe@googlegroups.com.
To post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at h= ttps://groups.google.com/group/bpfk-list.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_225_723998563.1551876480569-- ------=_Part_224_132505069.1551876480568--