From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 15263431FBF for ; Thu, 8 May 2014 13:15:21 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.798 X-Spam-Level: X-Spam-Status: No, score=-0.798 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJHQTe19krUR for ; Thu, 8 May 2014 13:15:12 -0700 (PDT) Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 7A4C7431FAE for ; Thu, 8 May 2014 13:15:12 -0700 (PDT) Received: by mail-oa0-f43.google.com with SMTP id l6so3764163oag.30 for ; Thu, 08 May 2014 13:15:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Z/4tNTfffqg11yHfP2uZOQD2ovTbRaVoUlYeOiQHjNE=; b=YmQYeqWoWslMsAmbfCJDJ2jL1IgMTOBgRg9T7b4hDCVWTwtXXeyPBzzbY4tSI7DVJJ hkoQIxcd60999YvPuisrXUvfuuhgCGMrVs/3XcGfdtuTgHqCKdlnCuJKV1jwcabcdvHW aVnaxwVcKVzHPz/7Y1sL+Lum1qk0hm5ccReADTI5miDPiDGYw7pH39HowI9WkwKydpxe m+Fk6WGPgWE5h17CzzL1YAa1kBG9zettEYlKI5fPaxqfRjHC2VlzW+T9sdDuDHuaG1aC o+gkADIhwTrLq4BifUYfVSqWSnUnBGVCB3rm0M/5T8/JbC3zFLzT5VKiu2W4xP7R5/Ex tZSg== X-Received: by 10.182.109.201 with SMTP id hu9mr6708748obb.77.1399580112012; Thu, 08 May 2014 13:15:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.105.242 with HTTP; Thu, 8 May 2014 13:14:51 -0700 (PDT) In-Reply-To: References: <87iopgkaiz.fsf@nikula.org> <20140508101325.GC23124@vilya.m0g.net> From: "Wael M. Nasreddine" Date: Thu, 8 May 2014 13:14:51 -0700 Message-ID: Subject: Re: Github? To: guyzmo+notmuch@m0g.net, notmuch@notmuchmail.org Content-Type: multipart/alternative; boundary=001a11c2db146972ec04f8e92304 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 20:15:21 -0000 --001a11c2db146972ec04f8e92304 Content-Type: text/plain; charset=UTF-8 On Thu, May 8, 2014 at 12:54 PM, Wael Nasreddine wrote: > Hi everyone, > > I didn't see the previous email about it, thank you Jani for the link. It > looks like you guys have your hands full and everything setup the way you > like it, so here's what I'll do myself (if it's acceptable with you, > otherwise I'll just remove everything): > > - Revert my changes (except for the CI) > - Set a cron job to update the mirror hourly for the Github user wanting > to fork. > - Remove the Issues, Pull Request and the Wiki > - Add a "mirror of .." to the description on top of the page > - Manually update the contrib/ bindings/ as they change in here and maybe > automate it later. > Can you guys at least consider splitting contrib/ and bindings/ into their own repo? It will make it easier for people to use the go bindings (for example) or to include the vim plugin as a submodule (or Vundle bundle). > > For the automatic pusher, I'll have to skip the README changes. > > Wael > > > On Thu May 08 2014 at 3:16:29 AM, Guyzmo wrote: > >> Hi, >> >> On Thu, May 08, 2014 at 09:40:45AM +0100, Eric wrote: >> > On Thu, 08 May 2014 09:13:56 +0200, Jani Nikula >> wrote: >> > > On Thu, 08 May 2014, Wael Nasreddine >> wrote: >> [...] >> > >> Any thoughts on moving to Github? >> > > http://mid.gmane.org/87wqea7c37.fsf@nikula.org >> > Exactly! >> >> it feels like there's an echo in the room ;-) >> >> > >> I took the liberty of making the first move by >> > >> creating https://github.com/notmuch and splitting the contrib/ and >> binding/ >> > >> into their own repository (conserving all their history). >> > > I am concerned people will mistake that for the official notmuch >> > > repository. >> > Me too! I am just a (happy) user here, but I do know that the sort >> > of confusion that might arise can work against acceptance of a piece >> > of software. I think that doing this without waiting for feedback, >> > especially from the people who do most of the work on notmuch, is >> > somewhat high-handed. >> >> well, because of git's fundamental feature to be distributed, I see >> no reason why notmuch couldn't have a *mirror* on github, as well as on >> gitorious or bitbucket. As long as the description says explicitly: >> >> *mirror of the http://git.notmuchmail.org/git/notmuch repository* >> >> and that the README.md starts by giving where the official repo is, >> and explains how to submit patches. And *always* refuse to merge in pull >> requests. A good thing would be to have it automatically kept in sync >> with the original repository, and a nice way to do it would be to create >> a post-receive hook on the principal repository. >> >> As a nice side effect of doing this, we'll stop having users >> complain about "not being on github"... Even though they should >> understand that this is github that has a design flaw not being able to >> track forks coming from outside of github, or getting out of github. >> >> my 2 cents, >> >> -- >> Guyzmo >> _______________________________________________ >> notmuch mailing list >> notmuch@notmuchmail.org >> http://notmuchmail.org/mailman/listinfo/notmuch >> > -- Wael Nasreddine | Software Engineer | wael.nasreddine@gmail.com | (650) 735-1773 --001a11c2db146972ec04f8e92304 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, May 8, 2014 at 12:54 PM, Wael Nasreddine <wael.nasreddine@gma= il.com> wrote:
Hi everyone,

I didn't see the previ= ous email about it, thank you Jani for the link. It looks like you guys hav= e your hands full and everything setup the way you like it, so here's w= hat I'll do myself (if it's acceptable with you, otherwise I'll= just remove everything):

- Revert my changes (except for the CI)
- Set= a cron job to update the mirror hourly for the Github user wanting to fork= .
- Remove the Issues, Pull Request and the Wiki
- Add = a "mirror of .." to the description on top of the page
- Manually update the contrib/ bindings/ as they change in here and ma= ybe automate it later.

Can you guys at least consider splitting contrib/ and bi= ndings/ into their own repo? It will make it easier for people to use the g= o bindings (for example) or to include the vim plugin as a submodule (or Vu= ndle bundle).
=C2=A0

For the automatic pus= her, I'll have to skip the README changes.

= Wael


On Thu May 08 2014 at 3:16:29 AM, Guyzmo <guyzmo+notmuch@m0g.n= et> wrote:
Hi,

On Thu, May 08, 2014 at 09:40:45AM +0100, Eric wrote:
> On Thu, 08 May 2014 09:13:56 +0200, Jani Nikula <jani@nikula.org> wrote:
> > On Thu, 08 May 2014, Wael Nasreddine <wael.nasreddine@gmail.com> wr= ote:
[...]
> >> Any thoughts on moving to Github?
> > http://mid.gmane.org/87wqea7c37.fsf@nikula.org
> Exactly!

it feels like there's an echo in the room ;-)

> >> I took the liberty of making the first move by
> >> creating https://github.com/notmuch and splitting the contrib/ and binding/=
> >> into their own repository (conserving all their history).
> > I am concerned people will mistake that for the official notmuch<= br> > > repository.
> Me too! I am just a (happy) user here, but I do know that the sort
> of confusion that might arise can work against acceptance of a piece > of software. I think that doing this without waiting for feedback,
> especially from the people who do most of the work on notmuch, is
> somewhat high-handed.

=C2=A0 =C2=A0 well, because of git's fundamental feature to be distribu= ted, =C2=A0I see
no reason why notmuch couldn't have a *mirror* on github, as well =C2= =A0as on
gitorious or bitbucket. As long as the description says explicitly:

*mirror of the http://git.notmuchmail.org/git/notmuch repositor= y*

=C2=A0 =C2=A0 and that the README.md starts by giving where the official = =C2=A0repo is,
and explains how to submit patches. And *always* refuse to merge in pull requests. A good thing would be to have it =C2=A0automatically =C2=A0kept = =C2=A0in sync
with the original repository, and a nice way to do it would be to create a post-receive hook on the principal repository.

=C2=A0 =C2=A0 As a nice =C2=A0side =C2=A0effect =C2=A0of =C2=A0doing =C2=A0= this, =C2=A0we'll =C2=A0stop =C2=A0having users
complain =C2=A0about =C2=A0"not =C2=A0being =C2=A0on =C2=A0github"= ;... =C2=A0Even =C2=A0though =C2=A0they =C2=A0should
understand that this is github that has a design flaw not being =C2=A0able = to
track forks coming from outside of github, or getting out of github.

my 2 cents,

--
Guyzmo
_______________________________________________
notmuch mailing list
notmuch@notmuc= hmail.org
http://notmuchmail.org/mailman/listinfo/notmuch



--
Wael Nasreddine=C2=A0|=C2= =A0Software Engineer=C2=A0| =C2=A0wael.nasreddine@gmail.com=C2=A0| =C2=A0(650) 735-1773

--001a11c2db146972ec04f8e92304--