On 29/06/2014 20:51, Marvin Humphrey wrote:
This isn't what I had in mind -- I was proposing to hide most or all of that
documentation, allowing us to air out the implementation before dealing with
publicizing the API. I still think that's a better plan... but you've
contributed so much, Nick, that I'd rather find a way to bend and bring us
together.
If cloaking isn't an option, an you give me a month to deal with those four
issues I listed above? I will deprioritize everything else to work on them,
including the release process reform initiative I've been pushing on
legal-discuss@apache, the return of the Lucy Book Club, and some internal
$work projects. It turns out that in the end, getting Clownfish right is what
I care about most.
I don't see much use in releasing Lucy 0.4 with an opaque version of
Clownfish. There aren't any major new features in the 0.4 release so Lucy
users can stick with 0.3 as well. I'm more concerned with not delaying the
Clownfish release any longer.
Regarding the four issues you mentioned:
> * Replace `::` with `.` as a namespacing separator.
> * Prevent subclassing of most Clownfish core classes.
> * Review names of core classes: VTable -> Class, VArray -> Array.
These should be more or less trivial.
> * Prefer fully qualified namespacing parcels, e.g. 'org.apache.lucy'.
This is more involved. For the record, here are some related threads:
http://s.apache.org/6wE
http://s.apache.org/VUJ
If you think it's important to get this sorted before we release Clownfish,
then, by all means, take your time. I'd be happy to help with any tasks that
can be parallelized.
Nick
