emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] Move ox-koma-letter into core?
Date: Sun, 19 Jan 2014 15:20:35 +0100	[thread overview]
Message-ID: <87k3dwaw98.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87mwisrrv8.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 19 Jan 2014 15:03:23 +0100")

Achim Gratz <Stromeko@nexgo.de> writes:

> The first question is what do we want contrib to be?  

So let's start with this one.

contrib/ *was* a staging area for stuff that were meant to go into
core at some point---i.e. when they get mature enough and when the
copyright assignments are sorted out.

For most libraries, contrib/ *is not* a staging area anymore.

So for now, having stuff in contrib/ means something like

  "These libraries are contributed by Org users and you can get their
  latest version by downloading the .tar.gz, the .zip, by cloning Org
  repo or by install org-plus-contrib from Org ELPA."

The core idea is that stuff from contrib get more love than random
github Org libraries: Org maintainers do fix stuff in there from time
to time (compiler warnings, etc.)

I think:

1) this core idea is fine, but I'm for applying it to Org ELPA instead
   of the Org contrib/ directory.

2) it would be cleaner if org-in-emacs and org-repo would be the same.

My point of view is that of the users, who get easily lost in those
distinctions. 


> If it's a staging
> area for things that are not-quite-ready yet, then these things should
> either be removed if they aren't getting finished or moved into core
> when they are.  Plus, since maint goes to Emacs, but master is not, it
> should be in master as soon as the copyright questions are resolved.

It is *not* a staging area only.

> If it's becoming a dump of stuff that will never make it into core
> because it isn't acceptable for Emacs proper for whatever reason, then
> I'd reason that it should be removed as well, independently of whether
> it's kept alive outside of Org or not.

I'm against dumping not-for-core libraries.

And that precisely because it's good to have libraries close to
Org's list/devs that I'd prefer the Org ELPA solution.

>> If so, we would need some Git guru (Achim?) to help with filtering
>> the Org repo, and I could help with setting up the Org ELPA packages.
>
> If you are suggesting to remove the history of contrib from Org's repo,
> then I'm against it.  

Why?

-- 
 Bastien

  reply	other threads:[~2014-01-19 14:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 23:08 [RFC] Move ox-koma-letter into core? Nicolas Goaziou
2014-01-18 11:55 ` Rasmus
2014-01-18 18:10 ` Carsten Dominik
2014-01-19 13:19   ` Bastien
2014-01-19 14:03     ` Achim Gratz
2014-01-19 14:20       ` Bastien [this message]
2014-01-20 17:38         ` Achim Gratz
2014-01-20 18:12           ` Bastien
2014-01-20 19:10             ` Achim Gratz
2014-01-20 20:05               ` Bastien
2014-01-21  1:12                 ` Rasmus
2014-01-21  2:50                 ` Eric Schulte
2014-01-21 10:52                   ` Bastien
2014-01-21 15:50                     ` Nick Dokos
2014-01-21 15:57                       ` Bastien
2014-01-21 18:31                     ` Achim Gratz
2014-01-21 19:10                       ` Bastien
2014-01-21  8:22                 ` Detlef Steuer
2014-01-21 18:19                 ` Achim Gratz
2014-01-21 19:08                   ` Bastien
2014-01-27 14:36     ` Bastien
2014-01-29 13:53       ` Nicolas Goaziou
2014-01-29 14:02         ` Bastien
2014-02-07 10:35           ` Nicolas Goaziou
2014-02-07 10:47             ` Bastien
2014-02-07 17:08               ` Nicolas Goaziou
2014-02-07 17:28                 ` Rasmus
2014-02-07 17:37                 ` Thomas S. Dye
2014-02-08 13:17                 ` Bastien
2014-02-17 19:10   ` Viktor Rosenfeld
2014-02-17 21:56     ` Thomas S. Dye
2014-02-19 20:33       ` Viktor Rosenfeld
2014-02-20 13:29         ` Rasmus
2014-02-20 22:32           ` Alan L Tyree
2014-03-04  9:35         ` Bastien
2014-02-17 22:25     ` Rasmus
2014-03-10 18:12     ` Greg Troxel
2014-01-18 21:15 ` Alan Schmitt

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 \
    --in-reply-to=87k3dwaw98.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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 read-only IMAP folder(s) and NNTP newsgroup(s).