Michael G Schwern wrote:
> On 2012.7.25 4:48 PM, Eric Wong wrote:
> > We need to use something. Right now our choice of mailer is the best
> > choice for _existing_ contributors.
>
> I believe this entire discussion can be reduced to that right there.
>
> If your process is optimized for existi
Michael G Schwern wrote:
>Do we care about getting new contributors?
Not if the cost is too high, no. I personally do think it is
important to make life easy for new contributors, not because that
will somehow compel them to work for me for free, but because it's
On 2012.7.25 4:48 PM, Eric Wong wrote:
> We need to use something. Right now our choice of mailer is the best
> choice for _existing_ contributors.
I believe this entire discussion can be reduced to that right there.
If your process is optimized for existing contributors, it will work well for
e
Michael G Schwern wrote:
> On 2012.7.24 7:55 PM, Eric Wong wrote:
> > Except git is also a "new specialized tool". Your examples are exactly
> > why I'm saddened many projects only adopted git, but not the workflow
> > which _built_ git (and Linux).
>
> Github also has broad spectrum utility. I
On 2012.7.24 10:54 PM, Jonathan Nieder wrote:
>> And again, it *does not have to be zero sum*. It doesn't have to be email VS
>> GUI. You can have your cake and eat it too.
>
> I assume you're talking about web-based interfaces that have gateways
> to email, that produce inboxes like this:
>
>
Michael G Schwern wrote:
> And again, it *does not have to be zero sum*. It doesn't have to be email VS
> GUI. You can have your cake and eat it too.
I assume you're talking about web-based interfaces that have gateways
to email, that produce inboxes like this:
24 Jul 02:46 GitHub [github]
6 matches
Mail list logo
