[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Policy for examples - and sdk's


I suspect the answer is entirely who the auidenance is ... if for "end user" then good policy to be part of "runtime" (which also includes "user doc" (from a callisto point of view ... doesn't mean that under the covers it might be in a seperate feature/plugin, for those that literally want just some minimum runtime).

But if for an "extender", then ... SDK. (and source and ISV doc included with SDK).

And in general, I think from Callisto's point of view ... should just be "runtimes" and "SDKs" ... with the biggest distinction being the audience of "end users" vs. "extenders" .. but, I'm sure, there's fuzzy areas.


Does this help? Have any examples in mind? (is that a pun?)







Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

03/06/2006 04:21 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject
[cross-project-issues-dev] Policy for examples






Having played around with the content from the callisto site, I would like to know what is the policy for projects to make their examples available:

- are they coming in the "runtime" feature?

- are they part of the SDK feature?

- are they coming separetly?


PaScaL
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev