I haven't heard back from Mr. Malcolm on this issue as yet, so I think it's time to consider how to move it out of Apache's svn to some other place. Initially I thought I'd just svn export it (complete with LICENSE and NOTICE and README), but then I realized there may be copyright issues since it is currently called "Apache ManifoldCF Meridio Plugin". Questions:
(1) Is it a problem to move it to Google Code with no name changes? (2) If I have to change the name, I could use either: "Meridio Plugin For Apache ManifoldCF" or "ManifoldCF Meridio Plugin" Which is better in your opinion? Karl On Fri, Dec 9, 2011 at 10:44 AM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > Hi, > > On Fri, Dec 9, 2011 at 3:14 PM, Karl Wright <daddy...@gmail.com> wrote: >> Essentially, this is a relatively minor piece of the whole Meridio >> connector puzzle. In my view it would be unfortunate to discard the >> rest of the puzzle because we did not have source for that one piece. >> If Apache found that problematic, it could easily be checked in under >> googlecode or some such, with a reference. What is Apache's position >> regarding that kind of solution? > > IIUC we're talking about an extra service that needs to be installed > along with the Meridio server being accessed. > > We could treat that as a system dependency just like we treat Meridio > itself. The only problem then would be for end users who want to use > the connector to figure out the licensing terms under which they can > use this extra component. > > Since we can't distribute it from Apache, it needs to be made > available from somewhere else preferably with good enough licensing > documentation. ManifoldCF can then point to that location from the > connector documentation. > > BR, > > Jukka Zitting
