A beautiful thing about documentation is that you can (and should) put a copyright and license statement right in the content.
It would be best if you can include a proper copyright header in the source form, but if it is technically impossible (or really, really hard), then it can be excluded or replaced with some form of best-effort to provide copyright and license information. While we're hijacking the discussion, copyright headers should be included in the source of all forms of content, included configuration, properties, and metadata. Again, unless it is either technically impossible or just really really hard to do so. Wayne On Thu, Jul 13, 2017 at 5:06 AM, Christoph Daniel Schulze < [email protected]> wrote: > Hi everyone, > > to piggyback on this discussion, depending on the documentation system > used it may be impossible to include a copyright header in the > documentation files. Is that a problem in any way? > > Cheers, > Chris > -- Wayne Beaton Director of Open Source Projects The Eclipse Foundation
_______________________________________________ incubation mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation
