[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cross-project-issues-dev] Info Center for Neon.3
- From: Frederic Gurr <frederic.gurr@xxxxxxxxxxx>
- Date: Thu, 27 Apr 2017 18:52:43 +0200
- Delivered-to: email@example.com
- Organization: Eclipse Foundation Europe GmbH
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
Sorry for the late reply. See comments inline.
On 13.04.2017 16:27, Gunnar Wagenknecht wrote:
>> On 13. Apr 2017, at 07:52, Frederic Gurr <frederic.gurr@xxxxxxxxxxx> wrote:
>> I have to disagree on that one. I'm pretty sure that quite a lot of
>> people rely on documentation for old releases.
> Frederic, I'm basically challenging two things:
> 1) How different and relevant really is old documentation?
> - I don't really by into the "misleading" or "confusing" argument
> - API/JavaDoc as well as plug-in development doc is the same
> - discovering features and api in newer doc could lead to additional motivation for adopting newer versions
>From my own experience dealing with updates for RCP based products, I
know that APIs definitely "went missing" (eg. presentation API) without
a sufficient migration guide. So it is IMHO very valuable to have old
documentation, be able to compare it and find it with a simple Google
search (instead of having to start 3 different versions of Eclipse,
start the clunky help browser and use the rudimentary search).
> 2) Spending valuable Foundation resources on things only a small subset of people need
> - IMHO IT time would be better invested focusing on a reliable infrastructure and services for projects and committers.
That's why we already automated most of the info center generation. So
this will limit maintenance to an absolute minimum.
> - If there are commercial interests in providing old documentation, companies should be able to come up with options themselves.
> - (Commercial) products based on RCP/IDE rarely rely on help.eclipse.org - they either host or ship their own help.
> - Help is (always was) included in old versions of Eclipse.
> If I recall, the goal of help.eclipse.org was to have a public service committers/developers/contributors could link/refer to when helping other users. IMHO it's also a valuable source when searching/researching something.
Yes, So let's keep up this great public service and not artificially cut
> Thus, in the interest of keeping things simple and being pragmatic, I suggest to only host the latest documentation on help.eclipse.org.
To be clear, I definitely don't want to increase time and effort spent
on the info center. My intention was just to find out if the community
sees a value in having an info center for every service release. Since
that does not seem to be the case, it's now even less work than before
(thanks to automation).