| Re: [mdt-papyrus.dev] [Documentation] Mixing main and extra plugins documentation |
|
Hi, From what I understood it’s for marketing reason, to promote extra in the core feature. I asked the same question some time ago [1] and here is the whole discussion [2] Regards, Benoit 1:
https://dev.eclipse.org/mhonarc/lists/mdt-papyrus.dev/msg02295.html 2:
https://dev.eclipse.org/mhonarc/lists/mdt-papyrus.dev/msg02310.html De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian Damus Hi, Mauricio, See some replies in-line, below. Christian On 28 June, 2016 at 09:13:08, ALFEREZ SALINAS Edward Mauricio (mauricio.alferez@xxxxxx) wrote:
This was the main point of the explanation when I asked the same question. 😉
Or, perhaps not so much “promotion” as just letting users be aware of what capabilities there are that may be of use to them.
I agree. Documentation should be published and installed together with the software; an installation should not document capabilities that it has not implemented.
Well, I don’t know about that. Documentation is not software, so the separation of concerns doesn’t really apply. But, I think it is sufficient that Papyrus advertises a Component Discovery
function that provides awareness of and access to these extra components. If the description of the capabilities of these various components in the discovery index isn’t good enough to let users know how useful a component may be in his or her work, then
that should be fixed. I would like to see the documentation for the extras packaged together with those features in the Extras repository, factored out of the main distribution.
|