[Sugar-devel] Bug tracking Vs Patch review

[Simon Schampijer]

Hi,

as a maintainer my 2 cents on the issue:

a) The review tools are interchangeable, whether we on the mailing list 
or in trac does not make the core issues go away:

- it is work
- takes time
- and it takes certain discipline.

I for myself, have a certain amount of time I can spend on reviews and I 
try my best to keep up with my queue. And I see all the kind of 
different issues why sometimes it takes long or stuff gets outdated. 
Either the submitter does not follow up or the bottleneck is on my side, 
sometimes the patch is not ready, has technical issues, we need a design 
etc. If this is using trac or mailing list, it does not matter, the 
important part is that both sides agree on a process and reserve time 
for the review and follow up.

b) Yes, Sugar is different than the Linux Kernel. We have UI, which 
makes patches/features having to go through a non technical agreement. 
Hence that is why people like Gary spend their evenings to help figuring 
those things out. At the moment this is a loose agreement to ask for 
feedback. This is meant to help the developer in that he can focus on 
code and help Sugar to have a consistent idea and workflow. It does not 
mean that we can not learn from the workflow the kernel people have of 
course.

c) And yes, we have another audience: The Feature process is meant to 
help to integrate people/deployments that are not even able to code a 
feature themselves. They can propose additions to the platform that 
others can pick up. We might not have seen so much non-developers use of 
it but I hope that it will be more widely used in the future.

And please, don't mix everything into one discussion!

Regards,
    Simon