Re: [cross-project-issues-dev] Source code in simrel aggregate repo

[David M Williams <david_williams@xxxxxxxxxx>]

I'll add to Planning Council Agenda, but
you might "work you point of view" through your Planning Council
rep ... with a specific proposal. I'm not sure "EPP" vs. "Common
Repo" changes that much (just in my opinion) since the common repo
has been seen as primarily for "end users" (granted, some end
users are "developers of plugins") so it'd be nice to have concise
clear statement of what projects "should do", in general. But,
yes, you (anyone) can always ask specific projects to do it differently
... we have no prohibition against it. I know for WTP, many years ago,
it was decided not to include source, simply because it was felt developers
"knew how to get the source" from WTP's project and no reason
to burden everyone else with it. [And, believe me, the Planning Council
has discussed many times and could never even come up with a good definition
of "SDK" :)  ... well, you know, one that applied to all
Eclipse projects.]. 

This history is one of the reasons we
(me especially) recommend people do not "build against" the common
repo ... but, instead build against each individual project they want ...
but I know that advise usually goes unheeded (but was happy when I once
saw you give the same advice :) 

Thanks for your efforts, 




From:      
 "Konstantin Komissarchik"
<konstantin.komissarchik@xxxxxxxxxx>
To:      
 "'Cross project
issues'" <cross-project-issues-dev@xxxxxxxxxxx>, 
Date:      
 08/01/2013 02:18 PM
Subject:    
   Re: [cross-project-issues-dev]
Source code in simrel aggregate repo
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

I suspect that what has happened in at least
some of the cases is that the requirements of the corresponding EPP package
drove what was contributed to the simrel repository. A natural effect,
but not ideal, since the user base for the simrel repo is more diverse
in their requirements.
 
Should this continue to be at project’s
discretion or should contributing source to simrel repo be a requirement?
I doubt that projects would object to contributing source if asked, but
maybe it would be better spelled out up front.
 
- Konstantin
 
 
From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: Thursday, August 01, 2013 10:50 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Source code in simrel aggregate
repo
 
This has always been viewed to be the contributing
project's decision. (Which ... is true in general ... some projects do
not contribute ALL their features to common repo; such as perhaps not examples,
perhaps not some of the rarer functions, etc.). I know for WTP, it was
thought best to minimize download (so no source ... last I knew), since
it was intended for people developing web apps ... not for people developing
plugins for WTP. 

Hope that answers what you were asking. 
  




From:        "Konstantin
Komissarchik" <konstantin.komissarchik@xxxxxxxxxx>
To:        "'Cross
project issues'" <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        08/01/2013
12:58 PM 
Subject:        [cross-project-issues-dev]
Source code in simrel aggregate repo 
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

---

As part of working on the definition for Eclipse Ultimate Edition, I have
discovered that a number of prominent projects do not contribute source
to the simrel repo. Before I start opening bugs, is there prior context
or discussion on whether or not source code should be in the simrel repo?
Note that I am not asking whether source code should be in a particular
package as that’s dependent on the user that the package is targeting.
  
Thanks, 
  
- Konstantin_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev