On 2 June 2013, Marc Weber <[email protected]> wrote:
> How to continue?
>
> Submit ideas here:
> http://vim-wiki.mawercer.de/wiki/vim74/devs-workflows.html
[...]
You mix up a number of mostly unrelated things.
(1) Mercurial and Git are virtually identical to one another in terms of
features. There are, of course, differences, but they are largely
irrelevant to this discussion.
(2) GitHub is not Git, but rather a centralized Git server, plus a bug
tracker, plus a number of nice "social" tools (other features are,
again, irrelevant to this discussion). Bitbucket is essentially the
same, the main differences being that its "social" tools are less
polished, it ofers Mercurial along with Git, and at this point it
seems to have fewer scaling problems than GitHub:
https://status.github.com/messages
http://status.bitbucket.org/
(3) Currently, Mercurial is not used as a DVCS for Vim development, but
rather as a central distribution point for the latest Vim sources,
with the additional convenience of keeping a history of patches. It
could well have been CVS instead with Bram as the only commiter, and
I beleve this is the gist of your gripe, not Mercurial itself.
So what you ask for is not a new workflow, but a complete overhaul
of the development process. You do try to solve somebody else's problem
after all. :)
About GitHub now. GitHub project started in ~2008. Back then, some
of us have been writing code for ~20 years, and we were generally doing
fine in our unenlightened ways. :) Back then GitHub was a Rails app that
shelled out to Git, and, while they do have a number of brilliant people
working at the site now, I'd humbly submit that some of that initial
architecture is still showing through. It's social features are really
nice these days, yes. But is it wise to start _depending_ on them?
Maybe not.
So, to answer your initial question: I'd personally like to see
Mercurial (or Git) used as a real DVCS (that is, people would start
submitting pull requests from their own repos). I'd also like to see a
more functional issue tracker in place, and people actually using it.
For the social features, I don't really care though. Things can be
coordinated just fine over a mailing list, like other projects do: see
f.i. Linux kernel, KDE, *BSD.
As for solving the "this patch" problem, I'd say "please merge my
commit 31bed2d" is pretty much equivalent to "please include the
attached patch".
Then again, all this rant is just my opinion, and I haven't
contributed anything useful to Vim in a while. Not sure why you (or
anybody else) would care about it, but since you asked... *shrug*
/lcd
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
