Received-SPF: none (google.com: me@v4hn.de does not designate permitted sender hosts) client-ip=85.13.134.113;
Date: Fri, 16 May 2014 11:19:48 +0200
From: v4hn <me@v4hn.de>
To: lojban@googlegroups.com
Subject: Re: [lojban] Re: Lojban's leadership and how I don't give a shit
 about it
Message-ID: <20140516091948.GG4119@samsa.fritz.box>
References: <ea1b88d5-3c46-4f71-907a-d9e593d145d3@googlegroups.com>
 <20140516015036.1f762326@aol.com>
 <cd216817-2b4b-4fc4-8f63-7c66962956a1@googlegroups.com>
 <CAMKwHj1S+C96u2axT24gqLDD4uAXUYvfrbUAU-og++o5OJDX5Q@mail.gmail.com>
 <CAMKwHj1F0JS6yGoBm2sM-BzYS82+Stk9B46=_ggnSr4sZUUHsw@mail.gmail.com>
 <CAMDmBpHryuJheG2whOcE9-0hzGpP-g8-c+Z4stGpxdpoiGK3jA@mail.gmail.com>
 <CAMKwHj2BCH7BKEEBOYeXcj=i_VYOD_YQ_ZBSV-dNYf6hLETHbw@mail.gmail.com>
 <CAMKwHj0jYTGA4Y0Xv5LoLzW+pp+LeAnLaexO9dGD7WPxAbcEaA@mail.gmail.com>
 <a85e4c4b-55f6-49d4-a878-5976aac9e0da@googlegroups.com>
 <CAMKwHj3rhZ6DFK7u+qY3Xd9ho3EWcUA_wX0EHT9py+JdEEDD3w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="IuhbYIxU28t+Kd57"
Content-Disposition: inline
In-Reply-To: <CAMKwHj3rhZ6DFK7u+qY3Xd9ho3EWcUA_wX0EHT9py+JdEEDD3w@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
X-Spam_score: -0.0
X-Spam_score_int: 0
X-Spam_bar: /


--IuhbYIxU28t+Kd57
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

coi rodo

First of all, I don't have a problem with selpa'i
doing administrational work, but I'm still not sure what
is actually proposed here - and I believe it's partly unclear
to the proposer as well.

I believe Jonathan points out the more basic
problem behind this "election": When you talk about
"merging changes officially", do you want to lift the syntax freeze?
Here, I agree with Jonathan. Neither Robin nor selpa'i would be allowed
to do that to the best of my knowledge.

The freeze is undone the moment it's clear what every cmavo available
in the language _as is_ means in current usage - which has to be accepted
by "standard" camxes at least. Yes, I mean _current_ usage - selpa'i himself
seemed to misunderstand this when I met him last year.
This is not about documenting something outdated for ages.=20
It's about documenting the language in official syntax,
as used by todays community.

However, I do see a problem to decide whether the documentation is complete.
I believe lorxus raised this question months ago:
It looks like only "Contact Spatial FAhA3" (locked for ages by Arnt Johanse=
n?)
and "Termsets CEhE NUhI NUhU PEhE" have not been checkpointed.
What does "TOC - Impact" mean in the section "Logical Connectives"?
Are all the other sections considered to be complete? Do they have to be
"checkpointed" again?
Neither of these are my area of expertise, so I can't really contribute.
But given that there are people around who can "rap in lojban", I still don=
't
understand why they propose lots of changes in syntax, but are unable to ra=
ise
guided discussions on what these last few words mean.

Back to the problem: After writing documentation for words to the byfy page=
s,
when/how/by whom will they be accepted officially?


mi'e la .van. mu'o

--IuhbYIxU28t+Kd57
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTddgzAAoJEKCfEUk/PuMm+/gP/ikylo9WqmTmea5I7L8hRO6w
F7EkGzd1Rdg8ojxfXCTFcxl1nQR/WhY+x1r+knVvHQV1gyekKf7yJ2iAyRYk0AgZ
L6U892cXbh9ptXgY9yXqPafZZ1RvGcRyrPADLVTMAV3OQJJEnjR5D3Yy6G10sSAx
/yY2EIvqdcp/csddvVOsWWu2Zs8BEdJnXpb9Ct5Y9pggsvDgJ6PBchtsIyrOXJMB
NZu13Mb5kD2/0UfS75OT+dUL9MRIlhIYwCIwuKBcoy4g9ajesHauYYyYDOTTGSjl
Redm934bFpdXfiuSxE3+FHRnbxHru0b4s6q6w/q8qCfFyM+bPlSTugefuP/JbUP/
m+kH8SkPic856AL7BShw4NTMl6fN6wsMDE5IF4t7Tb2tOuo5IqewCESsn6pJJdbL
SwLHxPQ87BRs6DPzymhJkhE7VbagvNYNus0AlhGgCdW3zmZ32ohtSFGec+Axju8B
udbd5oDVKwqVirhQyUfvHssEzFreQe/cCYOyGOC7q5sVKJQ7RQOBBgG8ek9iqZ80
ydVu3mUZbJrpjgXjeaiOldwNyKaJZWOKppsf5NfR7iv5Fk4IuIfsXMLNm+3hJWA5
V+/DrHvaKl5efHuixeaiUcER/XW88UxExfMcsw++GtjEp5ukxm2ei0jtxcDTLRwi
tqphDzu6/4q/jv+2ZPU9
=xcj1
-----END PGP SIGNATURE-----

--IuhbYIxU28t+Kd57--