[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[pdt-dev] Vendor-specific download links on PDT downloads page

Greetings PDT developers,

The PDT download page [1] provides only one link to PDT 3.0 release code, and that link is to a vendor-branded non-eclipse.org site. Note that links to vendor-specific pages are okay, but certain steps need to be taken to ensure that the project itself is presented in a vendor-neutral manner (this is a key part of operating an open project).

According to our guidelines [2], that link needs to have some text that indicates that the link will take the user to an external site; further, it must also open a new tab or window (to complete the delineation between Eclipse and non-Eclipse content).

If I recall correctly, the reason for hosting the all-in-one is so that some content that cannot be distributed from eclipse.org can be included. This is okay. However, the code that is hosted at eclipse.org really must be able to stand on its own and some version of it must be accessible from an eclipse.org server in a vendor-neutral manner.

Since the eclipse.org PDT code is accessible via the Indigo repository, I assume that it must also be directly accessible through a project p2 repository. You might consider including a link to that repository (though users tend to not find these links all that useful).  Note that the updatesiteurl specified in the project metadata points to a very old version of PDT. This entry should either be updated or removed.

  • Add some words on the download page that state that the 3.0 version of PDT can be easily added to an Eclipse installation via the Indigo repository;
  • Make the changes to the external link as suggested above; and
  • Add some words to the external link that describe it as an 'alternative' distribution


[1] http://www.eclipse.org/pdt/downloads/
[2] http://wiki.eclipse.org/Links_to_non-eclipse.org_content
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton

PNG image

GIF image