[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-architecture-council] [Bug 284552] Voting: Subclipse as default SVN support provider

https://bugs.eclipse.org/bugs/show_bug.cgi?id=284552  
Product/Component: Community / Cross-Project

Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eclipse.org-architecture-
                   |                            |council@xxxxxxxxxxx,
                   |                            |martin.oberhuber@xxxxxxxxxxx
                   |                            |om




--- Comment #10 from Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx>  2009-07-31 04:52:09 -0400 ---
(In reply to comment #9)
I'm copying the architecture council since this is more or less a frequently
asked question.

> But even if Subclipse is not an Eclipse project, can it still be bundled with
> common Eclipse downloads?

There is a small chance doing so -- the com.ibm.icu bundle and other 3rd party
bundles from Orbit are also distributed from Eclipse.org.

BUT

1. Eclipse.org can only distribute stuff that's 100% IP clean and licensed
   with a license compatible with the EPL. Note that just the EPL license
   is not sufficient, IP cleanliness must also be checked -- otherwise
   some developer could claim that stuff is licensed under EPL while it
   really infringes somebody's IP.

2. The IP cleanliness checks must be made at Eclipse.org -- either by an
   IP Review or by only having committers/contributors to the code which 
   have signed an Eclipse Committer Agreement (in which they basically 
   promise they won't ever infringe anybody's IP and abide by IP due 
   diligence).

3. Since Subclipse developers are not committers today, an IP Review / code
   scan would be necessary. Because of the effort and workload doing this, 
   it cannot be done too often. In other words, Subclipse would need to 
   commit to officially releasing their stuff at a given point in time, such
   that the IP review can then take place.
   Today, if I'm not mistaken, Subclipse more or less distributes weekly 
   builds from their update site but not well-defined releases.

There may be more obstacles, but these are the ones I can think of today. Fact
is, being an Eclipse project does come at a cost (release reviews, development
process, IP due diligence) but does give the benefit of 100% IP cleanliness
which commercial adopters of Eclipse.org technology value.

You cannot have the benefit (approved Eclipse.org download) without a cost. Who
would be willing to pay the cost?


-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.