Re: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF
I think we still can use abbreviations, sparingly, where there is unlikely to be a collision and where the added length is a detriment. For example: environment variable MCF_HOME jar prefix, e.g mcf-core.jar webapp name, e.g. mcf-crawler-ui.war I just didn't want there to be an issue with either the documentation or, especially, the source tree, again. Long form permissibility is still open, but I'm just sticking with ManifoldCF as the only project name/handle, for now. Karl On Tue, Oct 5, 2010 at 12:48 AM, Jack Krupansky jack.krupan...@lucidimagination.com wrote: That sounds good, and it is great to finally see the project naming move towards a final form that can stand up to even the most rigorous challenge. Long live ManifoldCF! That said, we may still choose to informally refer to MCF or mcf, although we should of course promote the proper name, either as ManifoldCF or Apache ManifoldCF (or Apache Manifold Connectors Framework?), as often and widely as possible. Did we ever settle whether that long-form name with CF expanded was okay for descriptive purposes even if the official Apache project name is Apache ManifoldCF? -- Jack Krupansky -- From: Karl Wright daddy...@gmail.com Sent: Monday, October 04, 2010 9:56 AM To: connectors-dev@incubator.apache.org Subject: Re: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF On reflection, I've actually decided to just use manifoldcf everywhere, just because that's least likely to run into problems in the long run. Karl On Sun, Oct 3, 2010 at 9:35 PM, Karl Wright daddy...@gmail.com wrote: I think using mcf in the package name and the names of the webapps will likely be fine. I'm less worried about everything else. Grant, any comments? Karl On Sun, Oct 3, 2010 at 8:58 PM, Jack Krupansky jack.krupan...@lucidimagination.com wrote: I'm okay with all of that, but with a question whether we can get away with using an abbreviation in org.apache.mcf as opposed to org.apache.manifoldcf. And then, whether the graduated project would be at http://mcf.apache.org; or http://manifoldcf.apache.org;. I have no idea whether there might be pushback higher up on that, but my inclination is to go ahead with using mcf. I'll defer to Karl as to whether he wants to verify our assumption through/with Grant/et al or just go ahead. -- Jack Krupansky -- From: Karl Wright daddy...@gmail.com Sent: Sunday, October 03, 2010 7:35 PM To: connectors-dev connectors-dev@incubator.apache.org Subject: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF The vote passes. Barely. Total count +1. Although I believe we didn't hear from lots of folks that made ManifoldCF their #1 choice last time. So, our new name is ManifoldCF. I'm thinking this will translate to: org.apache.mcf MCFException MCF abbreviation ManifoldCF full name webapps mcf-crawler-ui, mcf-authority-service, mcf-api-service ... and I can begin to change the tree around probably by tomorrow morning. Sound okay to everyone? Karl
Re: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF
That sounds good, and it is great to finally see the project naming move towards a final form that can stand up to even the most rigorous challenge. Long live ManifoldCF! That said, we may still choose to informally refer to MCF or mcf, although we should of course promote the proper name, either as ManifoldCF or Apache ManifoldCF (or Apache Manifold Connectors Framework?), as often and widely as possible. Did we ever settle whether that long-form name with CF expanded was okay for descriptive purposes even if the official Apache project name is Apache ManifoldCF? -- Jack Krupansky -- From: Karl Wright daddy...@gmail.com Sent: Monday, October 04, 2010 9:56 AM To: connectors-dev@incubator.apache.org Subject: Re: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF On reflection, I've actually decided to just use manifoldcf everywhere, just because that's least likely to run into problems in the long run. Karl On Sun, Oct 3, 2010 at 9:35 PM, Karl Wright daddy...@gmail.com wrote: I think using mcf in the package name and the names of the webapps will likely be fine. I'm less worried about everything else. Grant, any comments? Karl On Sun, Oct 3, 2010 at 8:58 PM, Jack Krupansky jack.krupan...@lucidimagination.com wrote: I'm okay with all of that, but with a question whether we can get away with using an abbreviation in org.apache.mcf as opposed to org.apache.manifoldcf. And then, whether the graduated project would be at http://mcf.apache.org; or http://manifoldcf.apache.org;. I have no idea whether there might be pushback higher up on that, but my inclination is to go ahead with using mcf. I'll defer to Karl as to whether he wants to verify our assumption through/with Grant/et al or just go ahead. -- Jack Krupansky -- From: Karl Wright daddy...@gmail.com Sent: Sunday, October 03, 2010 7:35 PM To: connectors-dev connectors-dev@incubator.apache.org Subject: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF The vote passes. Barely. Total count +1. Although I believe we didn't hear from lots of folks that made ManifoldCF their #1 choice last time. So, our new name is ManifoldCF. I'm thinking this will translate to: org.apache.mcf MCFException MCF abbreviation ManifoldCF full name webapps mcf-crawler-ui, mcf-authority-service, mcf-api-service ... and I can begin to change the tree around probably by tomorrow morning. Sound okay to everyone? Karl
[RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF
The vote passes. Barely. Total count +1. Although I believe we didn't hear from lots of folks that made ManifoldCF their #1 choice last time. So, our new name is ManifoldCF. I'm thinking this will translate to: org.apache.mcf MCFException MCF abbreviation ManifoldCF full name webapps mcf-crawler-ui, mcf-authority-service, mcf-api-service ... and I can begin to change the tree around probably by tomorrow morning. Sound okay to everyone? Karl
