From: Bozhidar Batsov <bozhidar@batsov.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>,
Daniel Colascione <dancol@dancol.org>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Project systems (again)
Date: Sat, 19 Apr 2014 11:55:00 +0300 [thread overview]
Message-ID: <CAM9Zgm2hyx_35GPQWOb=z0PvpTGrtUUmYY1sefozooxs-yaSyg@mail.gmail.com> (raw)
In-Reply-To: <87mwfiraz8.fsf@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
On 18 April 2014 17:03, Dmitry Gutov <dgutov@yandex.ru> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > FWIW, I'd prefer that you work with EDE developers to improve and
> > extend what they have; starting from scratch (or almost from scratch)
> > sounds like waste of effort, especially since some of the EDE is
> > already in Emacs.
>
> I disagree: this wouldn't be starting from scratch.
>
> Projectile is one such existing system that people use, and a generic
> interface would allow for better integration with other packages, even
> those that choose to be project-management-system-agnostic, which is
> generally a good choice.
>
> Personally, I use Projectile already, and switching to EDE wouldn't be
> an improvement for my use. As a bonus, its primary developer (Bozhidar
> Batsov) already has copyright assignment on file, so it wouldn't be
> inconceivable to add it to GNU ELPA soon or eventually. But of course,
> there will be other contributors to take care of.
>
>
Btw, Projectile was the reason I signed the copyright assignment in the
first place. Stefan approached me a few years back
about including it into ELPA, but for some reason we never actually got to
doing this.
Projectile is not without its quirks, but I'm fairly certain its one of the
best project management options around. What's most important, however, is
that it's pretty well battle tested - thousands of users have been using it
over the last 3 years and have submitted numerous bug reports, feature
requests and patches. Starting for scratch would reset the counter on all
(most) of that. I'm certainly biased, but I think focusing more effort on
improving Projectile makes more sense than implementing an alternative
solution.
[-- Attachment #2: Type: text/html, Size: 2253 bytes --]
next prev parent reply other threads:[~2014-04-19 8:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 21:52 Project systems (again) Daniel Colascione
2014-04-18 6:37 ` Eli Zaretskii
2014-04-18 7:07 ` Daniel Colascione
2014-04-18 7:50 ` Eli Zaretskii
2014-04-18 7:58 ` Daniel Colascione
2014-04-18 8:49 ` Eli Zaretskii
2014-04-19 1:45 ` Eric M. Ludlam
2014-04-19 14:26 ` Stefan Monnier
2014-04-19 19:37 ` Eric M. Ludlam
2014-04-18 15:52 ` Stefan Monnier
2014-04-18 18:37 ` Alex Ott
2014-04-18 14:03 ` Dmitry Gutov
2014-04-19 8:55 ` Bozhidar Batsov [this message]
2014-04-19 14:28 ` Stefan Monnier
2014-04-19 16:52 ` Daniel Colascione
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='CAM9Zgm2hyx_35GPQWOb=z0PvpTGrtUUmYY1sefozooxs-yaSyg@mail.gmail.com' \
--to=bozhidar@batsov.com \
--cc=dancol@dancol.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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.