Received: from mail-oi1-f192.google.com ([209.85.167.192]:44042) by stodi.digitalkingdom.org with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from ) id 1h1OMg-0007Ag-4q; Tue, 05 Mar 2019 20:41:14 -0800 Received: by mail-oi1-f192.google.com with SMTP id e65sf1826149oia.11; Tue, 05 Mar 2019 20:41:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:from:to:message-id:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=9kmdjeelLaoNBaNoXTW32xHqTzMXvI+lcGmOFpXkuIM=; b=bu41xlzlrtGU5HWK4aDHiXak9hQ+i9mLNGeXH80EKskvKQDJpCZGuUZMj1atgy6vao Wzdu5NqZUG3puzDbA5FeX1azRU6S1x8O5z79kIFG0qCBqwHU1iP2hVenY1e2ST9Ax7YE nv/acZTSSdefno1a069QX7v8sWVHbpFH3ldLX/ep+vBO0RmWX1lWTqdg6k1mjCm2wyW/ vDIhCQi32laOPT6V2S/HhfZ57wCOr4Bg4AXIniHdkhwrwvHXSgGvO5ZqCtIdPS6KuPTr 05F9Dw42DIwX5BC1NnQTleidYJ09Q2LiRHEDNqAK6PiUSGm3A6q26T83fnTYa4bk6rDF C2NA== 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:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe; bh=9kmdjeelLaoNBaNoXTW32xHqTzMXvI+lcGmOFpXkuIM=; b=GuQ+gvLlljB0Uz6oJgWZGgoL02LNShYa+0tidl8949yO5o/oIEVGXA+XzHiF1D7wkp vA6y/rdYJlMxgoR/PlWc+8rRhAcvDI//j7HYhbRfGmGcfuoJ4QRjjeP5FQE+Gyu9cd6d mdXxXibqF0KMBw6M418jR7ye+0ecPOj1YYzlojlObbKvXc6AXjWlWGJI1BGsaU/uudsM yQiJxYAUlqWnRt9nBqknCn6KE+uqhEp7cc6VZuM00yVlZjKYwV495xJ+P8BSx70e/oOx 7irrP1vBW2R3AqwbL38MUtXy47kApWUJ4X3EPr/a/620G2JZLFxyGjVU1/QEOP+S12Vv zI3w== Sender: bpfk-list@googlegroups.com X-Gm-Message-State: APjAAAVTPloRmTQNevKUJk1sGPDW4uTc8nv/W+dywFb5jO92HmfO1dUd cHejuAJSDIUUBT2z7uWydv4= X-Google-Smtp-Source: APXvYqy72rKVunjGFoYBy1NvFMP1l/3pWDX5QSep1VmNGyER39oOMr3u8ijia5Z0jEARXfQ938kD0w== X-Received: by 2002:a05:6830:1282:: with SMTP id z2mr3143186otp.249.1551847263628; Tue, 05 Mar 2019 20:41:03 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 2002:aca:c4c1:: with SMTP id u184ls225386oif.8.gmail; Tue, 05 Mar 2019 20:41:03 -0800 (PST) X-Received: by 2002:aca:4d6:: with SMTP id 205mr16730061oie.26.1551847263456; Tue, 05 Mar 2019 20:41:03 -0800 (PST) Received: by 2002:aca:c515:0:0:0:0:0 with SMTP id v21msoif; Tue, 5 Mar 2019 18:47:39 -0800 (PST) X-Received: by 2002:aca:c4cf:: with SMTP id u198mr303650oif.151.1551840459265; Tue, 05 Mar 2019 18:47:39 -0800 (PST) Date: Tue, 5 Mar 2019 18:47:39 -0800 (PST) From: "la .eris." To: BPFK Message-Id: Subject: [bpfk] Salutations! MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_98_778406468.1551840459076" X-Original-Sender: WizKarim@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-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -2.7 (--) X-Spam_score: -2.7 X-Spam_score_int: -26 X-Spam_bar: -- ------=_Part_98_778406468.1551840459076 Content-Type: multipart/alternative; boundary="----=_Part_99_1878907365.1551840459076" ------=_Part_99_1878907365.1551840459076 Content-Type: text/plain; charset="UTF-8" Coi rodo, I just spent half an hour writing out a long post with lots attitudinals and humor and the like, but it appears to have disappeared into the ether, so this will be rather brief. There is currently discussion at the 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 and possibly someone else. I'm not some radical who wants to change everything. Almost all of the language change proposals that I particularly want done aren't of my creation. For instance, I'd like to merge CAI into 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 everything; I just want somewhere that language change could happen (with peer review 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 entering the official language). The details of the RFC process haven't been determined yet, although I have some strong opinions (to use GitHub, for 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 productively without breaking everything. This would mean that discussions would be in English, which is really a necessity anyway, since the RFCs would be in English and not everyone submitting ideas would be able to speak English. I'd also like to get documentation, including 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 that is part of the job. This is not the original posting of my proposal, and many arguments and counterarguments have already been raised. I hope you will join the meeting and comment, or become active there if you are currently present but inactive. mi'e .eris. -- 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 email 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_99_1878907365.1551840459076 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Coi rodo,

I just spent half an hour wri= ting out a long post with lots attitudinals and humor and the like, but it = appears to have disappeared into the ether, so this will be rather brief. T= here is currently discussion at the LLG Members Meeting about what to do wi= th 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 and possibly someone else. I'm not som= e radical who wants to change everything. Almost all of the language change= proposals that I particularly want done aren't of my creation. For ins= tance, I'd like to merge CAI into UI. I also kind of like the NOIhA pro= posal and the indicator ko'oi, among other such changes. I don't wa= nt to add malglico or ruin everything; I just want somewhere that language = change could happen (with peer review and at least semi-official adoption, = not just by adding an experimental cmavo and waiting to see if they catch o= n without any hope of them ever entering the official language). The detail= s of the RFC process haven't been determined yet, although I have some = strong opinions (to use GitHub, for 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 y= et, but would still like to have a voice in language discussions and can st= ill be trusted to participate productively without breaking everything. Thi= s would mean that discussions would be in English, which is really a necess= ity anyway, since the RFCs would be in English and not everyone submitting = ideas would be able to speak English.

I'd also= like to get documentation, including the CLL, up to date. I propose that t= he BPFK (or its successor) assume responsibility for maintaining documentat= ion. There are several people who have expressed interest in participating = under something like my suggestion, and I expect that some of them will als= o help update documentation if that is part of the job.=C2=A0
This is not the original posting of my proposal, and many argum= ents and counterarguments have already been raised. I hope you will join th= e meeting and comment, or become active 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_99_1878907365.1551840459076-- ------=_Part_98_778406468.1551840459076--