notmuch development

2010-09-21 Thread Jameson Rollins 
On Tue, 21 Sep 2010 13:32:30 -0700, Carl Worth  wrote:
> Also, if anyone has any suggestions for things that we could do to
> improve things if I have to "disappear" again in the future, then I
> would be happy to do what I can.

Hey, Carl.  The most obvious thing I can think of is delegating some
lieutenants to handle processing patches.  There definitely are some
worthy candidates (who are kind of already doing this already).  Even if
they're not actually pushing patches into a canonical repo, they could
at least vet in-coming patches and prep things for your review.  If they
could present you with branches that are potentially "ready to go" it
might make things a lot easier for you, especially when you're in a
crunch.

jamie.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:

notmuch development

2010-09-21 Thread Carl Worth 
On Tue, 21 Sep 2010 17:05:12 -0400, Jameson Rollins  wrote:
> Hey, Carl.  The most obvious thing I can think of is delegating some
> lieutenants to handle processing patches.  There definitely are some
> worthy candidates (who are kind of already doing this already).  Even if
> they're not actually pushing patches into a canonical repo, they could
> at least vet in-coming patches and prep things for your review.  If they
> could present you with branches that are potentially "ready to go" it
> might make things a lot easier for you, especially when you're in a
> crunch.

Yes. Other people can definitely help me, particular as I gain trust in
their ability to review, accept, and reject patches in a similar way to
what I would have done myself.

I do like that patches are in general sent to the mailing list, and I'd
like that to continue. I use searches based on the list messages to
determine patches that I still need to review, (though, obviously I'm
quite a ways behind in this process).

As people review and accept patches, I'd love to receive mail addressed
specifically to me, (can copy the list as well, of course), with
pointers to git repositories that have "accepted" patches integrated
into them.

That will definitely help me prioritize pulling such patches into the
canonical repository.

-Carl

-- 
carl.d.worth at intel.com
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:

notmuch development

2010-09-21 Thread Carl Worth 
On Tue, 21 Sep 2010 11:38:46 -0400, Scott Henson  
wrote:
> It seems to me that development on notmuch has slowed down recently?  Lots
> of patches sitting in the patch queue and not much movement on the git
> repository?  Am I missing where the development is going on?

Yes. The git repository has been almost entirely stagnant for the last
several months. That was due to me not finding the chance to do notmuch
development on a regular basis for some months.

Fortunately, I've just recently (in the past week) started doing
development again, and I'm optimistic that I'll be able to keep this up
going forward.

Also, if anyone has any suggestions for things that we could do to
improve things if I have to "disappear" again in the future, then I
would be happy to do what I can.

-Carl

-- 
carl.d.worth at intel.com
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: 
<http://notmuchmail.org/pipermail/notmuch/attachments/20100921/d9190293/attachment.pgp>

notmuch development

2010-09-21 Thread Scott Henson 
It seems to me that development on notmuch has slowed down recently?  Lots
of patches sitting in the patch queue and not much movement on the git
repository?  Am I missing where the development is going on?

-- 
Scott Henson
-- next part --
An HTML attachment was scrubbed...
URL:

notmuch development

2010-09-21 Thread Scott Henson 
It seems to me that development on notmuch has slowed down recently?  Lots
of patches sitting in the patch queue and not much movement on the git
repository?  Am I missing where the development is going on?

-- 
Scott Henson
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: notmuch development

2010-09-21 Thread Carl Worth 
On Tue, 21 Sep 2010 11:38:46 -0400, Scott Henson sc...@foolishpride.org wrote:
 It seems to me that development on notmuch has slowed down recently?  Lots
 of patches sitting in the patch queue and not much movement on the git
 repository?  Am I missing where the development is going on?

Yes. The git repository has been almost entirely stagnant for the last
several months. That was due to me not finding the chance to do notmuch
development on a regular basis for some months.

Fortunately, I've just recently (in the past week) started doing
development again, and I'm optimistic that I'll be able to keep this up
going forward.

Also, if anyone has any suggestions for things that we could do to
improve things if I have to disappear again in the future, then I
would be happy to do what I can.

-Carl

-- 
carl.d.wo...@intel.com


pgpJtfQkKrbMK.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: notmuch development

2010-09-21 Thread Jameson Rollins 
On Tue, 21 Sep 2010 13:32:30 -0700, Carl Worth cwo...@cworth.org wrote:
 Also, if anyone has any suggestions for things that we could do to
 improve things if I have to disappear again in the future, then I
 would be happy to do what I can.

Hey, Carl.  The most obvious thing I can think of is delegating some
lieutenants to handle processing patches.  There definitely are some
worthy candidates (who are kind of already doing this already).  Even if
they're not actually pushing patches into a canonical repo, they could
at least vet in-coming patches and prep things for your review.  If they
could present you with branches that are potentially ready to go it
might make things a lot easier for you, especially when you're in a
crunch.

jamie.


pgpAVF4ACVmpG.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: notmuch development

2010-09-21 Thread Carl Worth 
On Tue, 21 Sep 2010 17:05:12 -0400, Jameson Rollins 
jroll...@finestructure.net wrote:
 Hey, Carl.  The most obvious thing I can think of is delegating some
 lieutenants to handle processing patches.  There definitely are some
 worthy candidates (who are kind of already doing this already).  Even if
 they're not actually pushing patches into a canonical repo, they could
 at least vet in-coming patches and prep things for your review.  If they
 could present you with branches that are potentially ready to go it
 might make things a lot easier for you, especially when you're in a
 crunch.

Yes. Other people can definitely help me, particular as I gain trust in
their ability to review, accept, and reject patches in a similar way to
what I would have done myself.

I do like that patches are in general sent to the mailing list, and I'd
like that to continue. I use searches based on the list messages to
determine patches that I still need to review, (though, obviously I'm
quite a ways behind in this process).

As people review and accept patches, I'd love to receive mail addressed
specifically to me, (can copy the list as well, of course), with
pointers to git repositories that have accepted patches integrated
into them.

That will definitely help me prioritize pulling such patches into the
canonical repository.

-Carl

-- 
carl.d.wo...@intel.com


pgp7EQIG7dpFt.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch