You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by Karl Wright <da...@gmail.com> on 2011/12/08 14:02:22 UTC

Delivery of source of integration packages for 0.4-incubating

Hi Folks,

The manifoldcf 0.4-incubating release does not include sources for the
following components that are meant to be installed on repositories,
in order to enable the corresponding connector:

- the solr 3.x security plugin
- the solr 4.x security plugin
- the SharePoint 3.0 MCPermissions.asmx web service
- the Meridio user lookup web service

I have put together all of these under
https://svn.apache.org/repos/asf/incubator/lcf/integration.  Each of
them has their own license, notice, etc.  My plan was to release them
independently and somewhat before ManifoldCF 0.4-incubating, as
separate packages with different names and version numbers (e.g.
"Apache SharePoint 3.0 ManifoldCF Plugin",
"apache-sharepoint-3.0-manifoldcf-plugin-0.1-incubating").

First, some things to note:
(1) I have no intention to deliver anything other than source
zips/tar.gzs for these, and of course corresponding signature files.
(2) I have no idea what the incubator release process should look like
for something like this.  Tommaso, what do you think?  Should we put
the packages up and request an incubator vote on each one?

I'd like to get the ball rolling quickly, before the holidays mess us
up, since these are prerequisites for the main 0.4 release.

Karl

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
> PS. As for component naming, "Apache SharePoint 3.0 ManifoldCF Plugin"
> is a bit unfortunate since it could be read as compoing from an
> "Apache SharePoint" project! A better one would be "Apache ManifoldCF
> plugin for SharePoint 3.0".

Yup, I already noticed (and changed) this.  It's called "Apache
ManifoldCF SharePoint 3.0 Plugin" now.
Karl

On Fri, Dec 9, 2011 at 11:32 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Fri, Dec 9, 2011 at 5:07 PM, Karl Wright <da...@gmail.com> wrote:
>> These components rev based on the repository or search engine, not
>> based on ManifoldCF, and their dependencies are primarily on the
>> repository or search engine, not on ManifoldCF.  Some of them can only
>> be built on Windows, for instance, and some require different versions
>> of Java than the base version we need to build the main ManifoldCF
>> code.  I posted about this perhaps 2.5 months ago, and repeated my
>> query a few times; nobody seemed to have a better idea than to make
>> each plugin essentially a separate package.
>
> Sorry for missing the discussion at the time. It still sounds like
> conditional compiling would be a good solution to this, but you
> certainly understand the issues better so I trust your judgement here.
>
> To answer your original questions 1 and 2:
>
> 1) It sounds like it would be best to also include binaries as a part
> of the component releases if we're in any case going to be including
> those bits in the main ManifoldCF release.
>
> 2) As Tommaso already noted, the release process is essentially the
> same regardless of the kind of component being released.
>
> PS. As for component naming, "Apache SharePoint 3.0 ManifoldCF Plugin"
> is a bit unfortunate since it could be read as compoing from an
> "Apache SharePoint" project! A better one would be "Apache ManifoldCF
> plugin for SharePoint 3.0".
>
> BR,
>
> Jukka Zitting

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
> 1) It sounds like it would be best to also include binaries as a part
> of the component releases if we're in any case going to be including
> those bits in the main ManifoldCF release.

Apache release guidelines say that you MUST release a -src.zip and
-src.tgz that contains no binaries.  You may optionally release a
-bin.zip and -bin.tgz package that contains compiled binaries as well.
 I was trying for the minimum effort, but if the mentors agree that we
should have the two additional binary packages for each component I
will withdraw my [VOTE] post from earlier and create binary targets.
Is this the consensus?

Karl

On Fri, Dec 9, 2011 at 11:32 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Fri, Dec 9, 2011 at 5:07 PM, Karl Wright <da...@gmail.com> wrote:
>> These components rev based on the repository or search engine, not
>> based on ManifoldCF, and their dependencies are primarily on the
>> repository or search engine, not on ManifoldCF.  Some of them can only
>> be built on Windows, for instance, and some require different versions
>> of Java than the base version we need to build the main ManifoldCF
>> code.  I posted about this perhaps 2.5 months ago, and repeated my
>> query a few times; nobody seemed to have a better idea than to make
>> each plugin essentially a separate package.
>
> Sorry for missing the discussion at the time. It still sounds like
> conditional compiling would be a good solution to this, but you
> certainly understand the issues better so I trust your judgement here.
>
> To answer your original questions 1 and 2:
>
> 1) It sounds like it would be best to also include binaries as a part
> of the component releases if we're in any case going to be including
> those bits in the main ManifoldCF release.
>
> 2) As Tommaso already noted, the release process is essentially the
> same regardless of the kind of component being released.
>
> PS. As for component naming, "Apache SharePoint 3.0 ManifoldCF Plugin"
> is a bit unfortunate since it could be read as compoing from an
> "Apache SharePoint" project! A better one would be "Apache ManifoldCF
> plugin for SharePoint 3.0".
>
> BR,
>
> Jukka Zitting

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Fri, Dec 9, 2011 at 5:07 PM, Karl Wright <da...@gmail.com> wrote:
> These components rev based on the repository or search engine, not
> based on ManifoldCF, and their dependencies are primarily on the
> repository or search engine, not on ManifoldCF.  Some of them can only
> be built on Windows, for instance, and some require different versions
> of Java than the base version we need to build the main ManifoldCF
> code.  I posted about this perhaps 2.5 months ago, and repeated my
> query a few times; nobody seemed to have a better idea than to make
> each plugin essentially a separate package.

Sorry for missing the discussion at the time. It still sounds like
conditional compiling would be a good solution to this, but you
certainly understand the issues better so I trust your judgement here.

To answer your original questions 1 and 2:

1) It sounds like it would be best to also include binaries as a part
of the component releases if we're in any case going to be including
those bits in the main ManifoldCF release.

2) As Tommaso already noted, the release process is essentially the
same regardless of the kind of component being released.

PS. As for component naming, "Apache SharePoint 3.0 ManifoldCF Plugin"
is a bit unfortunate since it could be read as compoing from an
"Apache SharePoint" project! A better one would be "Apache ManifoldCF
plugin for SharePoint 3.0".

BR,

Jukka Zitting

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
Hi Jukka,

These components rev based on the repository or search engine, not
based on ManifoldCF, and their dependencies are primarily on the
repository or search engine, not on ManifoldCF.  Some of them can only
be built on Windows, for instance, and some require different versions
of Java than the base version we need to build the main ManifoldCF
code.  I posted about this perhaps 2.5 months ago, and repeated my
query a few times; nobody seemed to have a better idea than to make
each plugin essentially a separate package.  (The produced binaries
are included in the main ManifoldCF release.)

Thanks,
Karl

On Fri, Dec 9, 2011 at 11:01 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Thu, Dec 8, 2011 at 2:02 PM, Karl Wright <da...@gmail.com> wrote:
>> The manifoldcf 0.4-incubating release does not include sources for the
>> following components that are meant to be installed on repositories,
>
> Is there a particular reason why we shouldn't keep these components
> inside the main trunk and thus include them also in 0.4-incubating?
>
> BR,
>
> Jukka Zitting

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Thu, Dec 8, 2011 at 2:02 PM, Karl Wright <da...@gmail.com> wrote:
> The manifoldcf 0.4-incubating release does not include sources for the
> following components that are meant to be installed on repositories,

Is there a particular reason why we shouldn't keep these components
inside the main trunk and thus include them also in 0.4-incubating?

BR,

Jukka Zitting

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
Still nothing.

Would be great to get some answers to these questions.

Karl

On Tue, Dec 13, 2011 at 1:00 AM, Karl Wright <da...@gmail.com> wrote:
> 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 <ju...@gmail.com> wrote:
>> Hi,
>>
>> On Fri, Dec 9, 2011 at 3:14 PM, Karl Wright <da...@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

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
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 <ju...@gmail.com> wrote:
> Hi,
>
> On Fri, Dec 9, 2011 at 3:14 PM, Karl Wright <da...@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

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
Your understanding is correct, and if I can find no better solution I
will move the package to Google Code.  I've contacted the guy who
might be able to help, but no response so far.

Karl

On Fri, Dec 9, 2011 at 10:44 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Fri, Dec 9, 2011 at 3:14 PM, Karl Wright <da...@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

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Fri, Dec 9, 2011 at 3:14 PM, Karl Wright <da...@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

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
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?

Karl

On Fri, Dec 9, 2011 at 9:04 AM, Karl Wright <da...@gmail.com> wrote:
> Then is your advice to drop the entire connector?
> Karl
>
> On Fri, Dec 9, 2011 at 8:52 AM, Jukka Zitting <ju...@gmail.com> wrote:
>> Hi,
>>
>> On Fri, Dec 9, 2011 at 2:45 PM, Karl Wright <da...@gmail.com> wrote:
>>> So, what we have out of this is a redistributable .msi, and test code,
>>> and that's it.
>>> [...]
>>> Assuming I get nowhere with the consultant, what is your advice about
>>> the plugin?
>>
>> If we don't have (and can't reproduce) the source for the plugin, then
>> it needs to be dropped as it's by definition not open source.
>>
>> BR,
>>
>> Jukka Zitting

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
Then is your advice to drop the entire connector?
Karl

On Fri, Dec 9, 2011 at 8:52 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Fri, Dec 9, 2011 at 2:45 PM, Karl Wright <da...@gmail.com> wrote:
>> So, what we have out of this is a redistributable .msi, and test code,
>> and that's it.
>> [...]
>> Assuming I get nowhere with the consultant, what is your advice about
>> the plugin?
>
> If we don't have (and can't reproduce) the source for the plugin, then
> it needs to be dropped as it's by definition not open source.
>
> BR,
>
> Jukka Zitting

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Fri, Dec 9, 2011 at 2:45 PM, Karl Wright <da...@gmail.com> wrote:
> So, what we have out of this is a redistributable .msi, and test code,
> and that's it.
> [...]
> Assuming I get nowhere with the consultant, what is your advice about
> the plugin?

If we don't have (and can't reproduce) the source for the plugin, then
it needs to be dropped as it's by definition not open source.

BR,

Jukka Zitting

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
Hi Tommaso,

I've called a vote on three of the plugin packages.  The fourth, the
Meridio plugin, has some issues.

The first issue is that it includes Setup.Exe from Microsoft's dot net
framework, and I'm unclear what the license is.  I'm pretty sure it is
redistributable but I don't know whether it is approved for Apache.

The second issue is that this particular plugin we do not have
complete source code for.  The code was developed by Meridio as an
extension to their platform; MetaCarta purchased their time to do the
work, and they agreed to a redistribution license.  However, repeated
attempts to get the code itself were unsuccessful.  Later, Meridio was
purchased by Autonomy, and shortly thereafter it was no longer
possible to reach any of the original people we'd been dealing with.
MetaCarta opened a ticket with Autonomy for the code delivery, but
they claimed they could not locate it, and to this day the ticket
remains open. :-/

So, what we have out of this is a redistributable .msi, and test code,
and that's it.

I *do* have the name of a consultant who we worked with to develop the
connector itself.  It is possible that he would be able to
re-implement the service, but I don't know whether he'd do it for
free.  I'll ping him and see where it leads.

Assuming I get nowhere with the consultant, what is your advice about
the plugin?

Karl

On Fri, Dec 9, 2011 at 3:08 AM, Karl Wright <da...@gmail.com> wrote:
>> Why only sources? I guess (not checked yet) the Sharepoint / Meridio ones
>> could not be redistributed as binaries with an Apache License but I think
>> the Solr stuff can be.
>
> The binaries are actually checked into the main ManifoldCF tree, and
> are delivered with ManifoldCF.
>
>> We may create a module called "MCF-integration" which aggregates the
>> sources for each of these modules.
>> I've seen this being done in the past where the source release contained
>> all the modules' sources while the single source artifacts could be
>> retrieved from the Apache Maven repository.
>
> The update/release cycle for each component is different.  For
> instance, I wouldn't anticipate releasing the SharePoint/Meridio
> release again for years, perhaps.
>
> Thanks!
> Karl
>
> On Fri, Dec 9, 2011 at 1:21 AM, Tommaso Teofili
> <to...@gmail.com> wrote:
>> Hi all
>>
>> 2011/12/8 Karl Wright <da...@gmail.com>
>>
>>> Hi Folks,
>>>
>>> The manifoldcf 0.4-incubating release does not include sources for the
>>> following components that are meant to be installed on repositories,
>>> in order to enable the corresponding connector:
>>>
>>> - the solr 3.x security plugin
>>> - the solr 4.x security plugin
>>> - the SharePoint 3.0 MCPermissions.asmx web service
>>> - the Meridio user lookup web service
>>>
>>> I have put together all of these under
>>> https://svn.apache.org/repos/asf/incubator/lcf/integration.  Each of
>>> them has their own license, notice, etc.  My plan was to release them
>>> independently and somewhat before ManifoldCF 0.4-incubating, as
>>> separate packages with different names and version numbers (e.g.
>>> "Apache SharePoint 3.0 ManifoldCF Plugin",
>>> "apache-sharepoint-3.0-manifoldcf-plugin-0.1-incubating").
>>>
>>> First, some things to note:
>>> (1) I have no intention to deliver anything other than source
>>> zips/tar.gzs for these, and of course corresponding signature files.
>>>
>>
>> Why only sources? I guess (not checked yet) the Sharepoint / Meridio ones
>> could not be redistributed as binaries with an Apache License but I think
>> the Solr stuff can be.
>>
>>
>>> (2) I have no idea what the incubator release process should look like
>>> for something like this.  Tommaso, what do you think?  Should we put
>>> the packages up and request an incubator vote on each one?
>>>
>>
>> We may create a module called "MCF-integration" which aggregates the
>> sources for each of these modules.
>> I've seen this being done in the past where the source release contained
>> all the modules' sources while the single source artifacts could be
>> retrieved from the Apache Maven repository.
>>
>> Otherwise if you want to have separate source packages being released
>> separately then yes we have to call a vote on general@ for each of them.
>>
>>
>>> I'd like to get the ball rolling quickly, before the holidays mess us
>>> up, since these are prerequisites for the main 0.4 release.
>>>
>>> Karl
>>>
>>
>> Tommaso

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Karl Wright <da...@gmail.com>.
> Why only sources? I guess (not checked yet) the Sharepoint / Meridio ones
> could not be redistributed as binaries with an Apache License but I think
> the Solr stuff can be.

The binaries are actually checked into the main ManifoldCF tree, and
are delivered with ManifoldCF.

> We may create a module called "MCF-integration" which aggregates the
> sources for each of these modules.
> I've seen this being done in the past where the source release contained
> all the modules' sources while the single source artifacts could be
> retrieved from the Apache Maven repository.

The update/release cycle for each component is different.  For
instance, I wouldn't anticipate releasing the SharePoint/Meridio
release again for years, perhaps.

Thanks!
Karl

On Fri, Dec 9, 2011 at 1:21 AM, Tommaso Teofili
<to...@gmail.com> wrote:
> Hi all
>
> 2011/12/8 Karl Wright <da...@gmail.com>
>
>> Hi Folks,
>>
>> The manifoldcf 0.4-incubating release does not include sources for the
>> following components that are meant to be installed on repositories,
>> in order to enable the corresponding connector:
>>
>> - the solr 3.x security plugin
>> - the solr 4.x security plugin
>> - the SharePoint 3.0 MCPermissions.asmx web service
>> - the Meridio user lookup web service
>>
>> I have put together all of these under
>> https://svn.apache.org/repos/asf/incubator/lcf/integration.  Each of
>> them has their own license, notice, etc.  My plan was to release them
>> independently and somewhat before ManifoldCF 0.4-incubating, as
>> separate packages with different names and version numbers (e.g.
>> "Apache SharePoint 3.0 ManifoldCF Plugin",
>> "apache-sharepoint-3.0-manifoldcf-plugin-0.1-incubating").
>>
>> First, some things to note:
>> (1) I have no intention to deliver anything other than source
>> zips/tar.gzs for these, and of course corresponding signature files.
>>
>
> Why only sources? I guess (not checked yet) the Sharepoint / Meridio ones
> could not be redistributed as binaries with an Apache License but I think
> the Solr stuff can be.
>
>
>> (2) I have no idea what the incubator release process should look like
>> for something like this.  Tommaso, what do you think?  Should we put
>> the packages up and request an incubator vote on each one?
>>
>
> We may create a module called "MCF-integration" which aggregates the
> sources for each of these modules.
> I've seen this being done in the past where the source release contained
> all the modules' sources while the single source artifacts could be
> retrieved from the Apache Maven repository.
>
> Otherwise if you want to have separate source packages being released
> separately then yes we have to call a vote on general@ for each of them.
>
>
>> I'd like to get the ball rolling quickly, before the holidays mess us
>> up, since these are prerequisites for the main 0.4 release.
>>
>> Karl
>>
>
> Tommaso

Re: Delivery of source of integration packages for 0.4-incubating

Posted by Tommaso Teofili <to...@gmail.com>.
Hi all

2011/12/8 Karl Wright <da...@gmail.com>

> Hi Folks,
>
> The manifoldcf 0.4-incubating release does not include sources for the
> following components that are meant to be installed on repositories,
> in order to enable the corresponding connector:
>
> - the solr 3.x security plugin
> - the solr 4.x security plugin
> - the SharePoint 3.0 MCPermissions.asmx web service
> - the Meridio user lookup web service
>
> I have put together all of these under
> https://svn.apache.org/repos/asf/incubator/lcf/integration.  Each of
> them has their own license, notice, etc.  My plan was to release them
> independently and somewhat before ManifoldCF 0.4-incubating, as
> separate packages with different names and version numbers (e.g.
> "Apache SharePoint 3.0 ManifoldCF Plugin",
> "apache-sharepoint-3.0-manifoldcf-plugin-0.1-incubating").
>
> First, some things to note:
> (1) I have no intention to deliver anything other than source
> zips/tar.gzs for these, and of course corresponding signature files.
>

Why only sources? I guess (not checked yet) the Sharepoint / Meridio ones
could not be redistributed as binaries with an Apache License but I think
the Solr stuff can be.


> (2) I have no idea what the incubator release process should look like
> for something like this.  Tommaso, what do you think?  Should we put
> the packages up and request an incubator vote on each one?
>

We may create a module called "MCF-integration" which aggregates the
sources for each of these modules.
I've seen this being done in the past where the source release contained
all the modules' sources while the single source artifacts could be
retrieved from the Apache Maven repository.

Otherwise if you want to have separate source packages being released
separately then yes we have to call a vote on general@ for each of them.


> I'd like to get the ball rolling quickly, before the holidays mess us
> up, since these are prerequisites for the main 0.4 release.
>
> Karl
>

Tommaso