From: Dmitry Gutov <dgutov@yandex.ru>
To: Tim Cross <theophilusx@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Emacs developers <emacs-devel@gnu.org>,
rms@gnu.org, me@nschum.de
Subject: Re: company.el status?
Date: Wed, 27 Mar 2013 07:28:53 +0400 [thread overview]
Message-ID: <51526775.4030506@yandex.ru> (raw)
In-Reply-To: <CAC=50j9e_TCnSL=bBqSOwoeGi28o7YJZ=XSFv6EUbqLpCZQwtg@mail.gmail.com>
On 27.03.2013 6:56, Tim Cross wrote:
> My question as well. While I won't lose any sleep should we give up on
> bzr and move to git, I am very concerned regarding further fracturing of
> the emacs ecosystem if that means using a platform which is using
> non-free tools. Git != GitHub.
I believe I presented some reasons why a project might want to use
GitHub over hosting solely at gnu.org.
> Lets have all official emacs packages use
> git, but on gnu.org <http://gnu.org>. If we start moving things out to
> various other locations, before long, we will have forks and different
Forks are good, the power to create one is one of the main freedoms
provided by free software licenses.
If a project has people taking its code and running in different
directions, it means the project is in demand, and it increases the
probability that those people either contribute back, or maybe create
something newer and more exciting.
> versions all over the place, leaving an envrionment where only the
> determined and experienced emacser has any hope - all new users will run
> a mile.
As long as GNU ELPA is easy to contribute to and the project maintainer
is willing, there shouldn't be any problems.
Now, if you're actually using the package, how about contributing some
code? I'm currently the sole developer, and I'm not in any danger of
splitting into several people anytime soon.
--Dmitry
next prev parent reply other threads:[~2013-03-27 3:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 17:37 company.el status? Dmitry Gutov
2013-03-07 18:03 ` Thierry Volpiatto
2013-03-07 20:50 ` Dmitry Gutov
2013-03-08 7:39 ` Thierry Volpiatto
2013-03-09 3:10 ` Stefan Monnier
2013-03-09 12:23 ` Thierry Volpiatto
2013-03-09 12:46 ` Xue Fuqiao
2013-03-09 13:38 ` Stefan Monnier
2013-03-09 14:59 ` Thierry Volpiatto
2013-03-09 15:50 ` Stefan Monnier
2013-03-07 18:27 ` Nikolaj Schumacher
2013-03-07 20:43 ` Dmitry Gutov
2013-03-08 11:17 ` Nikolaj Schumacher
2013-03-08 21:25 ` Dmitry Gutov
2013-03-08 22:52 ` Richard Stallman
2013-03-08 23:50 ` Dmitry Gutov
[not found] ` <B74660D8-9994-4E4C-A7C3-C1A1B9BD899A@mit.edu>
2013-03-09 0:11 ` Dmitry Gutov
2013-03-09 8:19 ` Eli Zaretskii
2013-03-27 2:56 ` Tim Cross
2013-03-27 3:28 ` Dmitry Gutov [this message]
2013-03-27 5:37 ` Stephen J. Turnbull
2013-03-10 1:15 ` Richard Stallman
2013-03-09 3:11 ` Stefan Monnier
2013-03-09 10:05 ` Dmitry Gutov
2013-03-09 13:38 ` Nikolaj Schumacher
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51526775.4030506@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=me@nschum.de \
--cc=rms@gnu.org \
--cc=theophilusx@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.