Community
Participate
Working Groups
As Europa approaches, I think it is time to discuss what the main download page on eclipse.org (http://www.eclipse.org/downloads/) is going to contain and what it is going to look like. There are many potential issues to consider (or we could just leave it the way it is now - although if we choose that, I'd like it to be a deliberate decision rather than a no-action default). This bug is opened to gather input and suggestions from the larger Eclipse community about what the download page should contain. We want to make sure that the Europa revision of the main download page preserves the ability to navigate to all the projects' downloads. Similarly, the "community Callisto distros" was a popular option last year and thus a revised download page should include the promotion/navigation of those distros. What else?
From the Packaging Project point of view I would like to see something similar to the main eclipse.org page. There we have the 'Eclipse is used for ...' section with links to Enterprise Development, Embedded + Device Development, Rich Client Platform, Application Frameworks, and Language IDE. (BTW: We could also link to complete and ready-to-run packages from these sub-pages - what do you think?) The Packaging Project will provide download packages for different - use cases (Java Developer, Java Enterprise Developer, Web Developer, ...) - platforms (win32, linux, maxosx, ...) - and with/without installer This structure should be reflected in the design of the download web page. It must be easy for someone new to Eclipse to choose the right package - this is what we want to achieve with EPP. I think the (default) platform could be chosen by the webserver.
I would like to see the download page be refelctive of what is produced by the packaging project. IMHO, we should have 3-4 main downloads that point to the packages created by the packaging project. The options should be based on use case, ex 1) Java Developer, 2) Java EE Developer, 3) RCP Developer and 4) C/C++ Developer. WE will also likely need a link to the 'classic' SDK download but this should not be as prominent.
Although it might be a little drastic, I'd like it to at least be considered to force or encourage users to click through the Known Issues and Release Notes during the install (this could be either on the d/l page or as part of the installer). As someone who spends a lot of time answering the same newbie questions again and again, I think I can speak for a lot of the community when I say I wish more people would RTFM (that's Read The Friendly Manual :-) I've also copied this comment to Bug 176787 relating to the Packaging project (Eclipse Installer)
(In reply to comment #3) [snip] > force or encourage users to click through the Known Issues and Release Notes > during the install (this could be either on the d/l page or as part of the > installer). Tying this to bug 138783, where it is suggested that the click-throughs be removed.
Closing this as a dupe of bug 187879 *** This bug has been marked as a duplicate of bug 187879 ***
Closing.
