Hi Jeff,
Jeff McAffer wrote:
Scott,
I did not mean to imply you were not
just that the bridge must be crossed at some point.
I also totally agree and understand
the issues. Equinox has a significant incubation element that has
experienced many multi-month delays waiting for IP issues. I don't
see it as a big/corporate vs. small/independent issue. Its more the
projects that are exploring new areas and touching lots of new/external
technologies. TPTP for example currently has more than double the
outstanding CQs than all of the Technology projects combined.
I don't disagree with your observations about the problems encountered
by all projects. Small projects, however, generally have fewer
people/resources to deal with all the associated 'busy work'
requirements (e.g. filling out CQ's, communicating with foundation and
library authors) in parallel with having/wanting to move forward with
design/development/deployment/support/documentation, etc. So all I'm
saying is that the effects are in practice larger on the small projects
that are touching new/external technologies (as it's a more significant
drain on their resources).
In any event, as you know, the
Foundation
is currently taking a number of different steps to address the
situation
and the backlog is dropping. We'll have to wait and see how this
evolves.
Yeah, I agree. I'm hopeful that progress is being made/will be made
next week.
Scott
Jeff
Hi Jeff/Remy,
As the one who has been 'walking the IP walk' for ECF for nearly two
years
now I can tell you we're doing what's required.
Unfortunately, in my view this has been at significant cost to ECF's
speed
of progress. The 'heavyweightness' of the IP process hampers small
projects much more than large/corp supported ones...and as you know it
hampers the large ones to a significant degree.
Scott
Jeff McAffer wrote:
Absolutely. Nothing has changed in the process. ANY project
wanting to use ANY third party lib/code MUST file a CQ with the
foundation.
In the event that that lib/version has already been approved for
use in another project AND that approval was scoped for "all",
this is pretty much of a rubber stamp (but needed nonetheless). You
iwll not pass a release review without having walked the walk.
Jeff
Hi everyone,
Well, ECF still needs to go through legal, though, no? I mean, after
ip process + sent out into Orbit. So claims the Orbit FAQ [1].
[1] - http://wiki.eclipse.org/index.php/Orbit_Faq
Regards,
Rem
On 12/8/06, Scott Lewis <slewis@xxxxxxxxxxxxx>
wrote:
>
> Hi Jeff,
>
> Happily, httpclient 3.0 and dependencies are already going
through
the
> approval process for Mylar...and they've agreed to do the bundling.
>
> So...yeah.
>
> Scott
>
> Jeff McAffer wrote:
>
>
> Scott Lewis wrote on 12/07/2006 09:23:19 PM:
>
> > > On 12/8/06, Scott Lewis <slewis@xxxxxxxxxxxxx>
wrote:
> > >> As of last night, I have the ECF file transfer
API provider
> implemented
> > >> using apache httpclient 3.0.1.
> > >
> > > Where can we get the org.apache.commons bundle that
> > > org.eclipse.ecf.provider.filetransfer currently has
a
> Require-Bundle
> > > on?
> >
> > Bother. I thought org.apache.commons bundle was now
part of the
> > platform distribution. I guess it must have been
installed by Mylar
> > (which I also have installed) and/or WindowBuilder. I
suppose for the
> > time being I'll have to track it down as jar and put in
that
> > provider.filetransfer as jar.
>
> Of course, you are going to go through the contribution
questionnaire
> process right?
>
> And contribute bundlings of these libs to Orbit?
>
> Damn, I'm on a roll with you guys :-)
> Jeff ________________________________
>
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>
>
>
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>
>
>
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
|
