From: Bastien <email@example.com> To: Tim Cross <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Moving some lisp/ob-*.el files to org-contrib - your advice? Date: Tue, 04 May 2021 01:15:40 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Tim Cross's message of "Tue, 04 May 2021 08:19:53 +1000") Tim Cross <firstname.lastname@example.org> writes: > +1 on this and the list of proposed languages. Thanks for the feedback. > Do any of these ob-* files have FSF copyright i.e. author assigned > copyright to FSF. Just wondering, given the contrib package will live in > non-gnu repo, if this is something we need to be concerned about or not? All these ob-*.el files are part of Org core, so they are part of Emacs and require the authors to sign the FSF papers. So there is no real problem here. org-contrib.git contains files with a free software license: most of them are GPLv3+, a few of them GPVv2(+) and one (or two, from memory) is using a MIT license. So there is no blocker for org-contrib.git to be packaged as a NonGNU package. > Strikes me there is nothing written in stone here, so if a language > becomes popular and it has maintainers, we can always review the > decision to move it 'out' and when justified, move back into core. Yes - on the other hand, we don't want to move files out of Org's core too often. > I think it is good having a clear distinction and the idea that if your > using a contrib package, it is 'best effort only' and not guaranteed to > work with the most recent org version compared to 'core', which has an > expectation it works with most recent org version. Yes, this is also the idea. That's why I called for more maintainers for the ob-*.el files, but we're not there yet, and for now it would be too drastic IMHO to remove some ob-*.el for which we don't have a maintainer or we are not 100% sure they are compatible. But luckily enough, I don't think backward compatibility problems happen often with Babel files. -- Bastien
next prev parent reply other threads:[~2021-05-03 23:33 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-03 15:13 Bastien 2021-05-03 17:49 ` Timothy 2021-05-03 18:05 ` Bastien 2021-05-03 19:36 ` Palak Mathur 2021-05-03 19:44 ` Timothy 2021-05-03 19:47 ` Palak Mathur 2021-05-03 20:34 ` Bastien 2021-05-03 20:33 ` Bastien 2021-05-04 7:55 ` Eric S Fraga 2021-05-19 3:36 ` Jack Kamm 2021-05-03 20:52 ` Victor A. Stoichita 2021-05-04 10:19 ` Dr. Arne Babenhauserheide 2021-05-04 11:28 ` Bastien 2021-05-04 18:38 ` Victor A. Stoichita 2021-05-04 11:32 ` Bastien 2021-05-03 22:19 ` Tim Cross 2021-05-03 23:15 ` Bastien [this message] 2021-05-04 10:19 ` Dr. Arne Babenhauserheide 2021-05-04 11:10 ` Bastien 2021-09-26 8:17 ` Bastien 2021-05-06 9:19 ` Jean Louis 2021-05-06 9:39 ` Bastien 2021-05-14 18:23 ` Greg Minshall 2021-05-17 16:39 ` Greg Minshall 2021-09-26 12:50 ` Bastien Guerry 2021-10-02 17:11 ` Bastien Guerry
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Moving some lisp/ob-*.el files to org-contrib - your advice?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).