Talk:Callisto Coordinated Update Sites
My comments (Kim Moir platform-releng) :-)
(1)There is a problem with the url http://update.eclipse.org/updates/callisto/
Currently, the platform team stores all its updates in this directory
and subdirectories such as these
So I don't know that this is the best url for Callisto
given that we already have platform content in that directory we can't change the Apache alias for platform because this has been hardcoded in our feature.xmls the unix permissions on the directory mean that the platform team would need to retain ownership in order to continue update the content in the existing update sites.
[dmw: agreed, we should have 'callisto' first in the URL, and keep it "parallel" other Eclipse projects]
(2)Providing Callisto as a single download comprising all 10 projects provides better exposure to the newer projects. By the same token, it also forces people to download stuff that they may not necessarily want or ever use, thus significantly increasing the strain on the distribution infrastructure. It is also rather overwhelming for a new eclipse user. My point is, perhaps there is a better way to educate users and provide choice while simultaneously exposing the full breadth of functionality available with Callisto.
[dmw: yep, this is the question to be answered empiracally and via community feedback ... but if we get one packaging working ... a few others should be easy --- though, I'd never want to get to the point of a Callisto user having more than, say, 4 or 5 choices ... those users that want more fine grained control than that will have to use project update URLs]
[nickb] I agree that making people download EVERYTHING is both overkill and will overtax the infrastructure. However, as David points out, "enabling" projects like EMF and GEF are required for the more newb-friendly projects, so could we have a set of screenshots just showing people how to use UM and the various requirements they need to check off in order to get the projects they want? I like what WTP has done for their UM site, for example.
By the way, I'm working on a tool to track download stats for EMF (and later, other projects who want to implement it), which combines
- a PHP script which runs SQL queries at the eclipse.org download stats database,
- a set of 3 cronjobs (actually, one shell script w/ three different options) for nightly/weekly/monthly querying using that interface, and
- a web UI to display those results for trending and overall results (eg., combining monthly data across a year or weekly data across a quarter; or comparing 4 consecutive weeks to see if downloads increase or decrease over time)
The purpose for us is:
- to track how many hits we get in a day/week/month (survey says: over 2 million EMF jar downloads and 80,000 zip downloads in Dec & Jan)
- to track how those hits change overtime
- to determine which files are more popular than others (ie., should the Callisto UM site include XSD? survey says: "*xsd*"&&!"*emf*" to "*emf*" =~ 20:1 (zips), which means EMF-only and EMF SDK (incl. XSD) zip downloads are 20x more downloaded than XSD-only zips)
- to compare UM installs vs. zip downloads, to see which is more prominently used (survey says: jars to zips =~ 19:1)
If you feel these tools/stats would be of value to other projects, I'd be happy to volunteer the code (and time to help set it up) for any other Callisto projects you'd like to track. See /cvsroot/org.eclipse/www/emf/downloads/
Sizes involved with Calisto
Nick, thanks. I'm writing this mostly to experiment with "talking" to "talk" :)
Not sure how it will be displayed.
First, your tool does sound very interesting ... I personally won't have time to investigate it much for a while, but I'd think we'd want these sorts of stats for all Eclipse projects!
Since several have voiced concerned over size of Callisto, I guess we should start to estimate its size.
Here's my off hand estimates of "runtime" sizes of several components (in MegaBytes). These are mostly guesses at this point (but a few I'm "updated" recently), but if enough people provide estimate, we'll get a little better idea of what tradeoffs are.
[Callisto meisters: feel free to update your portions of table to be accurate ... using current milestones, or previous release milestones as estimates. Any rough estimate will do.]
If we literally included each (sub) project as a choice, that would be 15 choices ... which I think is too many for what I've thought Callisto was for. Perhaps someone could propose some concrete "groupings" that would satisfy majority of users (though, I'm pessimistic if we could reach much agreement?)
If we go that route, though, I don't think we would need to do anything, except maybe to get the platform plugin to provide all 10 "discovery sites"?
Also, maybe our friendly webmaster could comment on if these "increases in size" are of the size to be of concern .... such as is 75 Megs, say, that much different than 150? Is 150 that much different that 300? (I know "twice as big" sounds like a lot ... but .. its not like 10 times as much). And with our improved "nearest mirror" support, maybe it wouldn't matter?).
|Project||Runtime Size||SDK Size|
|Business Intelligence and Reporting Tools (BIRT)||3||?|
|C/C++ IDE (CDT)||10||?|
|Data Tools Platform (DTP)||6||?|
|Eclipse Modeling Framework (EMF, SDO, XSD)||7||?|
|Eclipse Project (Platform only)||15||?|
|Eclipse Project (PDE, JDT)||60||?|
|Graphical Editing Framework (GEF)||3||?|
|Graphical Modeling Framework (GMF)||6||?|
|Test and Performance Tools Platform (TPTP)||10||?|
|Visual Editor (VE, JEM)||5||?|
|Web Tools Platform (WTP, WST, JST)||25||45|