accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4144) User Manual PDF doesn't include copyright or license information
Date Fri, 12 Feb 2016 21:25:18 GMT


ASF GitHub Bot commented on ACCUMULO-4144:

GitHub user ctubbsii opened a pull request:

    ACCUMULO-4144 Add copyright/license info to manual

    This is a best effort to pass scrutiny. Personally, I find this confusing... references
to software guarantees which don't apply to docs, confusing reference to "using this file",
etc. Additional clarification was requested in LEGAL-235, but this is an attempt to make progress
in the interim.

You can merge this pull request into a Git repository by running:

    $ git pull ACCUMULO-4144

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #69
commit 2f5c0e14a4f6f62183b4a4e016b059fba50df1ba
Author: Christopher Tubbs <>
Date:   2016-02-12T21:20:51Z

    ACCUMULO-4144 Add copyright/license info to manual


> User Manual PDF doesn't include copyright or license information
> ----------------------------------------------------------------
>                 Key: ACCUMULO-4144
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.6.5, 1.7.0, 1.8.0, 2.0.0
>            Reporter: Sean Busbey
>            Priority: Minor
> We publish the user manual PDF outside of our normal site (in the maven repo), but the
generated PDF doesn't have any kind of copyright statement or a note about licensing.
> Since this is definitely published externally (and as a part of our release handling)
it seems like it should have some indication. Even though it's a "binary format" strictly
speaking, it's consumed as text by humans so we should give them some pointers.
> It seems like it should go on either the title page or a page immediately following it?

This message was sent by Atlassian JIRA

View raw message