From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jambunathan K Newsgroups: gmane.emacs.devel Subject: Re: [ELPA Submission] OpenDocumentText exporter for Orgmode Date: Wed, 15 Jun 2011 01:35:31 +0530 Message-ID: <81lix4p4ac.fsf@gmail.com> References: <81zkllh423.fsf@gmail.com> <87wrgoe7k0.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: dough.gmane.org 1308082096 27327 80.91.229.12 (14 Jun 2011 20:08:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 14 Jun 2011 20:08:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 14 22:08:12 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QWZuF-0003Dy-1e for ged-emacs-devel@m.gmane.org; Tue, 14 Jun 2011 22:08:11 +0200 Original-Received: from localhost ([::1]:46474 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QWZuD-0007VY-D3 for ged-emacs-devel@m.gmane.org; Tue, 14 Jun 2011 16:08:09 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:44987) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QWZs1-0006oc-RG for emacs-devel@gnu.org; Tue, 14 Jun 2011 16:05:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QWZrx-0002hS-SI for emacs-devel@gnu.org; Tue, 14 Jun 2011 16:05:53 -0400 Original-Received: from mail-px0-f179.google.com ([209.85.212.179]:40578) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QWZrx-0002hD-Bx for emacs-devel@gnu.org; Tue, 14 Jun 2011 16:05:49 -0400 Original-Received: by pxi2 with SMTP id 2so3509721pxi.38 for ; Tue, 14 Jun 2011 13:05:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:mail-followup-to :date:in-reply-to:message-id:user-agent:mime-version:content-type; bh=RLUwaCW9mCyqJKxftbLTJ9YALR3qouQ8gObB6TO/wD4=; b=bOCyDsVw6d0jiU46UneuD5LqtPeL/pBvojqy2L5FIccSiZTYa6pP9aA67pEdHNWM1U o7aW/tKjVw4fsLkWb6MKg8LT9z+hYLZX65yoJkoO2n4LGKVPR3B71L1LroyHV3Ay8t5q XbMi+mDPEg5pmLwfqry77zh0hHsVw4/qtLzcM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:mail-followup-to:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=aRYYDZHKQUqwjRnNrJc+SGKhUppFAwT6REtPCZMXbow8e6A0PdDoMv5loYSl1ka7Wy hBOH5Z9IQvFUd1Dww9n3WPWxomljCvAo32UDmYmlK5c+rN04snhI0gF6uWfQu3JN4iwp GefTSq4nKRjekymQLGKDX2IB3KslDqNJBSxI8= Original-Received: by 10.143.63.10 with SMTP id q10mr1223854wfk.291.1308081947680; Tue, 14 Jun 2011 13:05:47 -0700 (PDT) Original-Received: from JAMBU-NETBOOK ([122.174.182.176]) by mx.google.com with ESMTPS id p5sm5812274pbd.92.2011.06.14.13.05.44 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 14 Jun 2011 13:05:46 -0700 (PDT) Mail-Followup-To: Chong Yidong , emacs-devel@gnu.org In-Reply-To: <87wrgoe7k0.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 14 Jun 2011 11:50:23 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (windows-nt) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.212.179 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:140466 Archived-At: --=-=-= Content-Type: text/plain Chong Yidong writes: > Jambunathan K writes: > >> I would like to submit the "OpenDocumentText exporter for Orgmode" - the >> org-odt-YYYYMMDD.tar for inclusion in http://elpa.gnu.org/packages. >> >> The URL for `package-archives' is: >> http://repo.or.cz/w/org-mode/org-jambu.git/blob_plain/HEAD:/packages/ > > The link is broken. No it is not, it only seems so. The server (which is not a webserver, so to speak) is merely refusing to list the contents of the directory. Configure the package-archives with the above URL and the package will be visible. Here is the link to archive-contents and the tar file: http://repo.or.cz/w/org-mode/org-jambu.git/blob_plain/HEAD:/packages/archive-contentshttp://repo.or.cz/w/org-mode/org-jambu.git/blob_plain/HEAD:/packages/org-odt-20110613.tar Did you checkout README.html? http://repo.or.cz/w/org-mode/org-jambu.git/blob_plain/HEAD:/packages/README.html > >> 2. It is a "friendly fork" (or a "feature branch") of Orgmode and is not >> part of official Orgmode Repo (yet). > > Does it really have to duplicate the entire Org mode tree? Doesn't have to. > Why can't the "OpenDocumentText exporter" functionality be a single > Org module? There are three approaches that I can think of: 1. Roll out my own. 2. I can include *only* the modified and new files as a multi-file package and make org-odt dependent on a base version of org. 3. I can distribute my changes as plain old diff against a well-known revision of the parent module say org-20110613.tar. Case 1 => KISS. Self-contained and guaranteed to be consistent. No need to track dependencies. Case 2 => In this scenario, at the least, the package manager has to assure me that org-odt-YYYYMMDD.tar is overlaid on top of the parent package i.e., at the run time the feature `org-html' is *always* provided by org-odt package and not by org package. Case 3 => This scenario sounds like an ugly hack. In this case, the package server might have to maintain not only the latest org-YYYYMMDD.tar package but also the historical org-20110613.tar in it's archives. Do you see any issues with Case 2? > Also, could you explain in more detail whether/when this work is > slated to become part of org-mode? AFAICS, Bastien is in favor of inclusion (pending a review, ofcourse). I believe that the only thing that is slowing things down is the Life itself with it's non-negotiable demands. It is close to 3 months since I proposed a formal patch. I am simply impatient and restless. > I'm not sure it makes sense to include it as a separate package, if > it's soon going to be available via the Org daily package (or when Org > is synched to the Emacs repository) anyway. There is a strong case for package installers. It attracts more users and thereby eyeballs. Newbie users are averse to using git. Furthermore, even serious users rely on installers or stable released before diving deep. More importantly, I want that my little work to be available for posterity and not be lost in the corridors of frail memories or fickle servers. > > Also, could you explain in more detail whether/when this work is slated > to become part of org-mode? I'm not sure it makes sense to include it > as a separate package, if it's soon going to be available via the Org > daily package (or when Org is synched to the Emacs repository) anyway. > >> 4. The package bundles rnc files for OpenDocument format [3]. I need >> help from Emacs developers on what would be the right way to include >> the copyright notice. I would appreciate if someone could offer me a >> helping hand here. > > See etc/schema/README. I need help on two fronts: 1. There is are different schema files for 1.1 and 1.2 formats. Can I include them both? How should my schema locating file be composed in that case. 2. IANAL and I am anxious to DTRT. Does it suffice if I just include the copyright info from the rng file or do I also need to copy copyright info from the formal spec. (See attachments) If both 1.1 and 1.2 schemas is under included do I need to include for each of the instances. The spec is here: http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html RNG file is here: http://docs.oasis-open.org/office/v1.2/cs01/OpenDocument-v1.2-cs01-schema.rng Is there anything else I need to do? Jambunathan K. --=-=-= Content-Type: text/plain Content-Disposition: attachment; filename=CopyrightNotice-From-RNG-File.txt Content-Description: CopyrightNotice-From-RNG-File.txt Open Document Format for Office Applications (OpenDocument) Version 1.2 Committee Specification (CS) 01, 17 March 2011 Relax-NG Schema Copyright (c) OASIS Open 2002-2011. All Rights Reserved. All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. --=-=-= Content-Type: text/plain; charset=utf-8 Content-Disposition: attachment; filename=CopyrightNotice-From-TheSpecification.txt Content-Transfer-Encoding: quoted-printable Content-Description: CopyrightNotice-From-TheSpecification.txt Copyright =C2=A9 OASIS Open 2002=E2=80=932011. All Rights Reserved. All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so. OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims. The names "OASIS", =E2=80=9COpenDocument=E2=80=9D, =E2=80=9COpen Document F= ormat=E2=80=9D, and =E2=80=9CODF=E2=80=9D are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance. --=-=-= Content-Type: text/plain -- --=-=-=--