Received: from localhost ([::1]:51356 helo=stodi.digitalkingdom.org) by stodi.digitalkingdom.org with esmtp (Exim 4.80.1) (envelope-from ) id 1YgyOe-0006my-PE; Sat, 11 Apr 2015 09:36:41 -0700 Received: from mail-qk0-f178.google.com ([209.85.220.178]:33688) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YgyOM-0006lq-JT for llg-members@lojban.org; Sat, 11 Apr 2015 09:36:33 -0700 Received: by qkx62 with SMTP id 62so86334030qkx.0 for ; Sat, 11 Apr 2015 09:36:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=yX56zzyZVyJJxPJOieDFW8knGkH0LEwDBdJY/H7h/3s=; b=r/HWZx2lBKLF+5rafrvAP+w3I9yUulQoUgfmA0sxEFQGQvU1zvvxMZTEK+QrQQPdNv OW59VZWfHZimjYM9XG4g6GqfM9vb2t1BUHJ4BtkCgv5oda4LiVgi4WIalX34/6Z86IEj jKJZxx//0KXdjZgZCpBqMJIlIGvk91WKf+T208CwSLjPrgs9swhFcWlpXOHuLl9OAnIQ 34qIwUJ99vzn5T4bivykJOp72giUqpgkNVQYyg98FipwP+PaBLua3JyQykx21k8vhlPw 1n87fg4WDvkRv/YEIJ/esbPwCpP6m5ztMLlzL5jcJCax2Nvy90cq5gDQJ/KGQ76hPyEn Qojw== X-Received: by 10.55.52.18 with SMTP id b18mr13543774qka.85.1428770176183; Sat, 11 Apr 2015 09:36:16 -0700 (PDT) Received: from caliban.fios-router.home (pool-100-33-73-219.nycmny.fios.verizon.net. [100.33.73.219]) by mx.google.com with ESMTPSA id m68sm1736526qge.15.2015.04.11.09.36.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 11 Apr 2015 09:36:14 -0700 (PDT) From: Riley Martinez-Lynch Message-Id: <2D9C1C26-76B3-47B4-8DD2-6C1DCE18D495@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Date: Sat, 11 Apr 2015 12:36:13 -0400 References: <55283D76.2050606@lojban.org> To: llg-members@lojban.org In-Reply-To: X-Mailer: Apple Mail (2.1510) X-Spam-Score: -2.0 (--) X-Spam_score: -2.0 X-Spam_score_int: -19 X-Spam_bar: -- Subject: [Llg-members] jbovlaste X-BeenThere: llg-members@lojban.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: llg-members@lojban.org Content-Type: multipart/mixed; boundary="===============7203428242045908150==" Errors-To: llg-members-bounces@lojban.org --===============7203428242045908150== Content-Type: multipart/alternative; boundary="Apple-Mail=_CDF51214-CB83-40A3-BEAE-3E5850DAFD74" --Apple-Mail=_CDF51214-CB83-40A3-BEAE-3E5850DAFD74 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Apr 11, 2015, at 1:43 AM, Gleki Arxokuna = wrote: > Riley, I'm asking you to report on all possible problems with your = python version of Jbovlaste/Vlasisku including financial ones and the = problem of the free time. >=20 > ke'u, please say a word about that because at least I see it as an = important project that I'm not able to contribute to at all (and no = similar software exists outside Lojbanistan). I don't see the current state of development jbovlaste 2 as problematic, = though I recognize it is not moving quickly enough for certain = lojbanists not to be named. ;) I started working on jbovlaste about a year ago, initially assisting = with the addition of languages and troubleshooting bulk imports, and = then fixing various bugs. As I started to get to know the software, I = came to realize that it was actually composed of three separate = projects: jbovlaste itself provides the web interface, including the = editor, and the dictionary exports; searching is powered by jiten, an = RFC 2229 server; classification and validation of new words used vlatai = from the jbofihe project. An immediate challenge was that both jiten and jbofihe had fallen into = obscurity, their initial developers having long since moved on to other = things. It was easy enough to recover the source code for jiten and make = the necessary changes. But jbofihe, which consists of a hand-crafted = parser, seemed daunting to change. It also seemed apparent that the = "camxes" family of parsers had supplanted it as the focus of active = development, and that camxes was integrated into the BPFK process, = whereas jbofihe had no formal status. So when it was time to update = jbovlaste to use the BPFK morphology rules, I decided to build on camxes = instead. I built the new morphological classifier/validator in python, which had = been previously discussed as the most appropriate language to use for = the next version of jbovlaste: Currently it is executed in a separate = process, like the original vlatai, but if and when the rest of jbovlaste = is implemented in python, this won't be necessary. I've also made good = progress on a python replacement for jiten which could similarly be = integrated into a python-powered jbovlaste. A plausible path to jbovlaste 2 might look like this: Start with = vlasisku. Update it to connect to the database instead of building its = own data source from an XML dump. In the first phase of the transition = between jbovlaste 1 and jbovlaste 2, jbovlaste 2 would handle searching = and browsing the database, but adding and editing content and exporting = data would continue to be handled by jbovlaste 1. Once jbovlaste 2 has = taken over all of the functions, jbovlaste 1 could be retired and we = could take up the feature backlog. My efforts since November have been directed to meeting business, but = with the meeting nearing its conclusion, I've returned to developing = camxes-py. My first task has been to update vlatai.py to incorporate the = changes to BPFK morphology that have been made since October so that = they can be integrated into jbovlaste. durka42 has seriously = contributed. The parser is likely to absorb most of my lojban software time for the = next few months, but there's no reason that someone else couldn't work = on retrofitting vlasisku to interface with the database, or on other = components such as producing printable dictionaries. I've hear rumors = that such work might already be under way. Replacing jbovlaste is a needful thing. We're making steady progress in = that direction, and I'd encourage anybody who want to get involved to do = so. That said, I feel it's much less urgent than some other work, most = notably, keeping CLL in print. If anybody reading this is looking for a = project, I would encourage them first to get involved with proofing and = preparing the CLL 1.1 candidate. Robin may be able to best advise about = what needs to be done, but there are a number of tasks that have been = logged here, and could be taken up by motivated parties without too much = guidance: = https://github.com/lojban/cll/milestones/Prince%20volunteers%20formatting%= 20review There is also a continuous build (thanks to durka42) which makes it = possible for editors to contribute without having to take on all the = technical overhead of installing and administrating their own build: http://alexburka.com/lojban/prince.php I hope this answers your questions, gleki, but please follow up as = needed. --Riley= --Apple-Mail=_CDF51214-CB83-40A3-BEAE-3E5850DAFD74 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii gleki.is.my.name@gmail.com&= gt; wrote:
Riley, I'm = asking you to report on all possible problems with your python = version of Jbovlaste/Vlasisku including financial ones and the problem = of the free time.

ke'u, please say a word about that because at = least I see it as an important project that I'm not able to contribute = to at all (and no similar software exists outside = Lojbanistan).

I = don't see the current state of development jbovlaste 2 as problematic, = though I recognize it is not moving quickly enough for certain = lojbanists not to be named. ;)

I started = working on jbovlaste about a year ago, initially assisting with the = addition of languages and troubleshooting bulk imports, and then fixing = various bugs. As I started to get to know the software, I came to = realize that it was actually composed of three separate projects: = jbovlaste itself provides the web interface, including the editor, and = the dictionary exports; searching is powered by jiten, an RFC 2229 = server; classification and validation of new words used vlatai from the = jbofihe project.

An immediate challenge was = that both jiten and jbofihe had fallen into obscurity, their initial = developers having long since moved on to other things. It was easy = enough to recover the source code for jiten and make the necessary = changes. But jbofihe, which consists of a hand-crafted parser, = seemed daunting to change. It also seemed apparent that the = "camxes" family of parsers had supplanted it as the focus of active = development, and that camxes was integrated into the BPFK process, = whereas jbofihe had no formal status. So when it was time to update = jbovlaste to use the BPFK morphology rules, I decided to build on camxes = instead.

I built the new morphological = classifier/validator in python, which had been previously discussed as = the most appropriate language to use for the next version of jbovlaste: = Currently it is executed in a separate process, like the original = vlatai, but if and when the rest of jbovlaste is implemented in python, = this won't be necessary. I've also made good progress on a python = replacement for jiten which could similarly be integrated into a = python-powered jbovlaste.

A plausible path to = jbovlaste 2 might look like this: Start with vlasisku. Update it to = connect to the database instead of building its own data source from an = XML dump. In the first phase of the transition between jbovlaste 1 and = jbovlaste 2, jbovlaste 2 would handle searching and browsing the = database, but adding and editing content and exporting data would = continue to be handled by jbovlaste 1. Once jbovlaste 2 has taken = over all of the functions, jbovlaste 1 could be retired and we could = take up the feature backlog.

My efforts since = November have been directed to meeting business, but with the meeting = nearing its conclusion, I've returned to developing camxes-py. My first = task has been to update vlatai.py to incorporate the changes = to BPFK morphology that have been made since October so that they = can be integrated into jbovlaste. durka42 has seriously = contributed.

The parser is likely to absorb = most of my lojban software time for the next few months, but there's no = reason that someone else couldn't work on retrofitting vlasisku to = interface with the database, or on other components such as producing = printable dictionaries. I've hear rumors that such work might already be = under way.

Replacing jbovlaste is a needful = thing. We're making steady progress in that direction, and I'd = encourage anybody who want to get involved to do so. That said, I feel = it's much less urgent than some other work, most notably, keeping = CLL in print. If anybody reading this is looking for a project, I would = encourage them first to get involved with proofing and preparing the CLL = 1.1 candidate. Robin may be able to best advise about what needs to be = done, but there are a number of tasks that have been logged here, and = could be taken up by motivated parties without too much = guidance:


There is also a continuous = build (thanks to durka42) which makes it possible for editors to = contribute without having to take on all the technical overhead of = installing and administrating their own = build:


I hope this answers your = questions, gleki, but please follow up as = needed.

--Riley
= --Apple-Mail=_CDF51214-CB83-40A3-BEAE-3E5850DAFD74-- --===============7203428242045908150== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Llg-members mailing list Llg-members@lojban.org http://mail.lojban.org/mailman/listinfo/llg-members --===============7203428242045908150==--