Hi Patrick. Using readthedocs.io to deploy your documentation is fine. This would be considered an external resource <https://www.eclipse.org/projects/handbook/#resources-external>; there's some more about them in the handbook. No formal permission is required, but there are some branding and level playing field requirements.
I'm pretty sure that you're doing this already, but will take the opportunity to reinforce that the sources for the documentation are project content (i.e., they must be stored in a Git repo that is managed by the Eclipse Foundation on behalf of the project). Regarding the copyright headers, there are two options outlined in the handbook <https://www.eclipse.org/projects/handbook/#ip-copyright-headers> (and repeated by the documentation generator <https://www.eclipse.org/projects/tools/documentation.php?id=iot.cyclonedds> ). - Copyright (c) {year} {owner}[ and others]; or - Copyright (c) {date} Contributors to the Eclipse Foundation HTH, Wayne On Fri, Jan 31, 2020 at 11:02 AM Patrick Masselink < [email protected]> wrote: > Hi all, > > I'm working on readthedocs support for hosting Eclipse CycloneDDS > <https://github.com/eclipse-cyclonedds/cyclonedds> documentation. I've > found other Eclipse projects already using readthedocs (i.e. IoT-Testware > <https://iottestware.readthedocs.io/en/master/>) but still I'd like to > ask if there are any potential concerns. > > Note the 3rd party tooling involved (Sphinx, doxygen, texlive etc.) is > already required today, to build CycloneDDS documentation. My contribution > will mostly involve configuration for automated readthedocs builds. Once > the mechanism is in place i will apply for automatic RTD builds on > pull-requests > <https://blog.readthedocs.com/building-docs-for-pull-requests/>, to > encourage contributors to add and improve documentation and to verify PRs > don't break the docs build. > > I intend to use a copyright notice similar to IoT-Testware (i.e. Copyright > 2020, Eclipse CycloneDDS Contributors) and will also include the license > <https://github.com/eclipse-cyclonedds/cyclonedds/blob/master/LICENSE>. > > Can I go ahead and once finished just do a pull-request? Or do we need any > formal permission or i.e. a review of the artifacts we intend to publish? > > Thanks, > > Patrick Masselink > _______________________________________________ > incubation mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/incubation > -- Wayne Beaton Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________ incubation mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/incubation
