Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1635216270.1241731125578.JavaMail.jira@brutus>
Date: Thu, 7 May 2009 14:18:45 -0700 (PDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-259) [doc]  submission formats listing
In-Reply-To: <289820782.1115174227223.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707119#action_12707119 ] 

Kathey Marsden commented on DERBY-259:
--------------------------------------

Shouldn't documentation submissions be as a patch  in dita format? I would like to close this Won't fix.  I don't think we should explicitly encourage other formats although of course they could still be attached to issues if folks want to provide content without building the docs etc.  I'd like to close this Won't fix.


> [doc]  submission formats listing
> ---------------------------------
>
>                 Key: DERBY-259
>                 URL: https://issues.apache.org/jira/browse/DERBY-259
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>         Environment: Any
>            Reporter: scott hutinger
>
> A complete listing of submission formats for content need to be compiled.  They should be listed in a prefered listing, then in order of non-prefered, but with specific restrictions ( please try to do this type of restrictions) in order of least wanted.
> For example, if you are going to send in a document in this format, please try to send in the graphics if files that were imported/copied into the final document.
> I would stress that the important portion is the submission, and the second being the file format.  If they have time to use a format that is easy for release, then that is fine.  If they don't want to mess with the final output format, this is also fine.
> Also, noted that Forrest and OpenOffice License types might not mesh with Apache.org.  This was brought up in forrest and asked by Ross (May 2005). 
> If this is a problem, then possibly Microsoft product outputs don't have a problem?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.