Re: [Evolution-hackers] Patch Review process

[Amish Munshi <lists munshi biz>]

On Mon, 2005-05-09 at 20:05 +0530, Harish Krishnaswamy wrote:
> hi All,
> 
> During the irc meeting last week,  we discussed the pros and cons of 
> deprecating evolution-patches and using bugzilla as the treasure
> bag for patches.
> 
> 
> A quick recap of the main points in favor of Bugzilla - 
>       * we tend to 'lose' patches in e-p. Bugzilla is more sticky. 
>       * easier for downstream packagers to release updates. 
>       * b.g.o can be queried for un/reviewed patches.
> 
> the other side of the coin : 
>       * bgo is much slower than reading mails 
>       * you need to be on-line to pull down the patches.
> 
> Fresh thoughts, any ?
> 
> -Harish

This is an area which I have always wanted to work on (since 4 years).
Integrate a mailing lists with a POP/IMAP server and integrate that
further with a opensource based development tools (for eg. Bugzilla),
this project has never seen the day of light.

Harsh might have some ideas for the current problem (marking a cc to
him).


Idea 1 :
How about a small and simple utility that takes mails and puts them in
bugzilla? 
Forcasted problems - Spam 
Solutions - Authentication required for 


Till date there has been a lot of development over HTTP. What I propose
is a development on top of POP/IMAP/SMTP. This will mean we use
evolution as a frontend to bugzilla.

With evolution-data-server concept sky is the limit for what can be
acheived with this infrastucture.



Idea 2:
bugbuddy currently is used for only filing bugs, a similar tool can be
used for patches.


Amish.