Exploring ManifoldCF ramifications

2010-09-21 Thread Karl Wright
Folks, The ManifoldCF name possibility leads to some challenges as far as our documentation is concerned. I thought that it might be a good idea during the vote to explore those to see what people thought. Here are some examples of how Apache Connectors Framework might get used in text: Apache

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Karl Wright
So, clearly, we need better names to work with, since the original list has led to another impass. Look at http://thesaurus.com/browse/multiple for some thesaurus equivalents of multiple or manifold. Some interesting ones: aggregate conglomerate legion diversiform multifold The first two are

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Karl Wright
The exception naming issue is noted, but that's really a separate problem. The IOException exception comes from the IO subsystem, and it's the base exception of everything from an encoding exception through a socket problem through a timeout. ACFException is a similar base exception class,

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Jack Krupansky
I concur with having a base class for all ACF exceptions, and then the specific exceptions extend that base. -- Jack Krupansky -- From: Karl Wright daddy...@gmail.com Sent: Tuesday, September 21, 2010 10:08 AM To:

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Jack Krupansky
My interpretation from the beginning is that there is a formal name prefixed with Apache that would get used external to the project to refer to the project, but then within the project we would just use the shorthand name, whether that means simply dropping the Apache or abbreviating the name

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Mark Miller
On 9/21/10 10:08 AM, Karl Wright wrote: The exception naming issue is noted, but that's really a separate problem. The IOException exception comes from the IO subsystem, and it's the base exception of everything from an encoding exception through a socket problem through a timeout.

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Upayavira
Butting in here. You can 'twist' the manifold word in other ways, e.g. manifolio, or some such - full name The Apache Manifolio Connector Framework, short name manifolio. Upayavira On Tue, 2010-09-21 at 10:26 -0400, Jack Krupansky wrote: My interpretation from the beginning is that there is a

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Jack Krupansky
That's a perfect example of what I was trying to suggest and avoids the usage problems. Although it has too many syllables for my taste, but that's just me. -- Jack Krupansky -- From: Upayavira u...@odoko.co.uk Sent: Tuesday, September 21, 2010

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Karl Wright
Multifold is a real word but is rarely used, which is why it seemed to solve all the problems too. Karl On Tue, Sep 21, 2010 at 10:49 AM, Jack Krupansky jack.krupan...@lucidimagination.com wrote: That's a perfect example of what I was trying to suggest and avoids the usage problems. Although it

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Karl Wright
If you are looking for non-existent words built out of parts that nevertheless have meanings, try these: manilink, manicon, maniweb, manisource multicon, multiweb heterolink, heteroweb, heterosource Karl On Tue, Sep 21, 2010 at 11:00 AM, Karl Wright daddy...@gmail.com wrote: Multifold is a

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Jack Krupansky
It sounds like the vote is moot pending resolution of the doc/code usage issue, but I'll go ahead and withdraw my vote at least temporarily pending further evolution of the issue. Are we going to reopen name suggestions? I few I had: Congo [Con for connectors] RepoMan [Repo for Repositories]

Re: [VOTE] Pick either Apache Connectors Framework or Apache ManifoldCF

2010-09-21 Thread Karl Wright
Jack has withdrawn his vote, and I withdraw mine as well. We are going to open name nominations again, since we have apparently all had ideas since the last round that may be to people's liking. A new vote will be called to select among the new nominations, and the winner of that will go up

Re: Exploring ManifoldCF ramifications

2010-09-21 Thread Jack Krupansky
That sounds fine with me. Assuming by ACF you mean the full name Apache Connectors Framework with ACF as the local informal name, although in practice maybe everybody would refer to it, even externally, as ACF as well, as was with LCF. -- Jack Krupansky

Soliciting more potential names for the project formerly known as LCF

2010-09-21 Thread Karl Wright
We're going to have another round of name selection, based on feedback from the board. We've also pretty much decided that the last round did not have sufficient breadth, so here's an open solicitation call for potential names for the next round. So hold on to your hats, and throw your

Re: Soliciting more potential names for the project formerly known as LCF

2010-09-21 Thread Jack Krupansky
I few more from my noon walk: Recon [Re from Repository and con from connectors] Reconn Conx [ala Connects] - treat these four as one for initial voting, then separate Conex Connx Connex Reconx [ala Repository and Connects] - ditto Reconex Reconnx Reconnex Contor [Con and tor from Connector]