From: gi1242+zsh@gmail.com
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: Julien Nicoulaud <julien.nicoulaud@gmail.com>,
Mailing-list zsh-workers <zsh-workers@zsh.org>
Subject: Re: GH:zsh-users/zsh-completions.
Date: Mon, 16 Oct 2017 11:26:12 -0400 [thread overview]
Message-ID: <20171016152611.GK31613@andrew.cmu.edu> (raw)
In-Reply-To: <6529.1508164192@thecus.kiddle.eu>
On Mon, Oct 16, 2017 at 04:29:52PM +0200, Oliver Kiddle wrote:
>> I believe a significant part of the contributions we had were because the
>> project is hosted on github It attracts an audience of contributors that
>> are not familiar with the "classic way" (mailing list, IRC, patches, and
>> different process for a each project), and it makes it very easy for
>> "drive-by" contributions and learning by example, which fits well to
>> completions. It also easy to review/provide feedback and iterate on
>> patches (eg: https://github.com/zsh-users/zsh-completions/pull/512)
>
> I'm sure you're right here.
>
> Does anyone else have views on allowing a github model for completion
> functions? Most of my arguments against github usage don't really
> apply if we're only talking about completions for commands.
My $0.02, since I contributed a completion script recently: I didn't
find clear instructions on contributing on the main web page. I went to
the tracker, and saw a note there. Then I didn't know if I could post to
the list without being subscribed, so I subscribed. Confirmed. And then
I submitted.
That's a lot of steps, and perhaps not everyone will do this.
Perhaps you could have a direct note on the main webpage on your
preferred contribution mechanism? Also allow people to contribute
without subscribing. (Hopefully in a way that doesn't get you insane
amounts of spam.)
Finally, if you're considering the new forking model for people
submitting patches, can I suggest GitLab
https://about.gitlab.com/
as an alternative to GitHub. Its feature set is comparable to GitHub,
and is completely open source.
GI
PS: Looking through your git logs looks like I sent you a bunch of
completions in 2011/12. And then nothing until recently. I'll check
if to see if I have any more local completion improvements that
might be useful and send them along.
--
Marketer to coder: "You start coding. I'll go find out what they want."
next prev parent reply other threads:[~2017-10-16 15:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7240.1507973844@thecus.kiddle.eu>
2017-10-14 14:44 ` GH:zsh-users/zsh-completions Julien Nicoulaud
2017-10-14 16:49 ` GH:zsh-users/zsh-completions Eric Cook
2017-10-16 14:29 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-16 15:11 ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 15:24 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-16 15:42 ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 17:49 ` GH:zsh-users/zsh-completions gi1242+zsh
2017-10-17 21:09 ` GH:zsh-users/zsh-completions Joey Pabalinas
2017-10-18 16:23 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-19 1:09 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-19 4:03 ` GH:zsh-users/zsh-completions Aaron Schrab
2017-10-19 5:24 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-11-01 23:33 ` ChangeLogs (Re: GH:zsh-users/zsh-completions.) Oliver Kiddle
2017-11-01 23:46 ` Bart Schaefer
2017-11-02 20:09 ` Oliver Kiddle
2017-10-19 1:31 ` GH:zsh-users/zsh-completions Joey Pabalinas
2017-10-19 14:37 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-10-30 23:38 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-11-01 16:35 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-11-01 22:58 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-16 23:00 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-16 20:04 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-10-17 7:53 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-17 8:41 ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 15:26 ` gi1242+zsh [this message]
2017-10-17 9:35 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-19 18:25 ` GH:zsh-users/zsh-completions Daniel Tameling
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=20171016152611.GK31613@andrew.cmu.edu \
--to=gi1242+zsh@gmail.com \
--cc=julien.nicoulaud@gmail.com \
--cc=okiddle@yahoo.co.uk \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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).