[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bpfk] What I'm going to do.



On Thu, Oct 14, 2010 at 11:43, Robin Lee Powell <rlpowell@digitalkingdom.org> wrote:
On Thu, Oct 14, 2010 at 11:38:47AM -0700, Theodore Reed wrote:
> On Thu, Oct 14, 2010 at 00:19, Robin Lee Powell <rlpowell@digitalkingdom.org
> > wrote:
>
> >
> > OK, so.  The urge to just Go Fix Shit has been growing in me.  I
> > think there's actually not all that much to do if I can get people
> > in a room for concentrated time to work on it.
> >
> > So, here's what's going to happen.
> >
> > 1.  Lindar is working on examples, basic cleanup, and search of past
> > contention for everything.
> >
> > 2.  I have diffs for the CLL; I will go through them, possibly with
> > others, and approve the result as the new CLL.
> >
> > 3.  Possibly in parallel, somebody converts the current CLL in git
> > to docbook.
> >
> > 4.  I, some other bay area Lojbanists, and a *very* few people via
> > voice chat, sit down for serious, concentrated sessions of Fixing
> > Shit.  The results I want here look, in my head, a lot like what Bob
> > originally asked for, actually.  To wit:
> >
> >  - a series of numbered alternative proposals; there might be three
> >    {ni} proposals, for example.  Somewhere (I'm thinking in a setup
> >    like shapado.com, but suggestions *very* welcome here) is a
> >    repository of the proposals *and the justifications for each
> >    option*.  Each proposal is associated with CLL changes and word
> >    definitons.
>
> We could do these as branches in git, maybe?

It's not just going to be CLL changes; it's going to be word list
stuff and commentary and so on.

The ideal is having a jvs2 that can handle checkpoints/versioning,
and then the proposal just becomes "see git #### in CLL repo ; see
jvs2 checkpoint ### ; here's my justification for this proposal".
See http://www.lojban.org/tiki/tiki-index.php?page=Dictionary for
more commentary on the pipe dream that is jvs2.


I suspect that checkpointing will be insufficient. You'll need the ability to actually branch or have mutually exclusive sets, rather than a point-to-point history. Maybe just tags or something. 

--
You received this message because you are subscribed to the Google Groups "BPFK" group.
To post to this group, send email to bpfk-list@googlegroups.com.
To unsubscribe from this group, send email to bpfk-list+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.