Re: Review Board

2013-03-10 Thread Kay Schenk
On Fri, Mar 8, 2013 at 1:47 PM, Rob Weir  wrote:

> On Fri, Mar 8, 2013 at 4:21 PM, janI  wrote:
> > On 8 March 2013 22:16, Rob Weir  wrote:
> >
> >> On Fri, Mar 8, 2013 at 3:51 PM, Dave Fisher 
> wrote:
> >> > Only if we are going to become a Review Then Commit project.
> >> >
> >>
> >> I was thinking more of whether it would be useful for working with
> >> patch contributions from contributors.
> >>
> >
> > Just be careful not to set level too high for volunteers, in my opinion
> the
> > mailing list is more than enough, no need for extra layers to complicate
> > matters.
> >
>
> That's exactly the issue.  The mailing list is so busy that new
> volunteers get lost, and their patches as well.  And if they toss
> their patches to bugzilla, the patches can easily be lost there was
> well.  So the question is whether a dedicated place for patches, with
> no distracting complications, would be preferred.
>
> -Rob
>

>From my perspective, I think we deal with patches to the mailing list, with
our preferred [PATCH] tag, or not, pretty well. From BZ, maybe no so much.

I would guess that historically, members of the head of a specific
OpenOffice project were copied on bugs for that area, e.g. "math" or "gsl"
etc.  I'm looking at our current bug categories.

Right now, all the issues changes go to  iss...@apache.openoffice.org.

What would be good is an easy way for volunteer developers to add
themselves to the CC list for a whole group of bugs based on
category/component. This would somewhat mimic the oversight that had been
in place in the past. So, do we have a way to do a bulk CC add for a group
of issues?  I took a quick look just now and nothing emerged.

This wouldn't guarantee that patches wouldn't fall through the cracks but
might help with the situation.

Thoughts?



> > rgds
> > Jan I.
> >
> >>
> >> -Rob
> >>
> >>
> >> > Otherwise I think it becomes yet another system to learn how to use.
> >> >
> >> > On Mar 8, 2013, at 9:10 AM, Rob Weir wrote:
> >> >
> >> >> https://reviews.apache.org
> >> >>
> >> >> I didn't know that this existed at Apache.  Should we be using it?
> >> >>
> >> >> -Rob
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >> >>
> >> >
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 

MzK

"Achieving happiness requires the right combination of Zen and Zin."


Re: Review Board

2013-03-10 Thread janI
On 10 March 2013 10:51, Andrea Pescetti  wrote:

> On 08/03/2013 Rob Weir wrote:
>
>> That's exactly the issue.  The mailing list is so busy that new
>> volunteers get lost, and their patches as well.  And if they toss
>> their patches to bugzilla, the patches can easily be lost there was
>> well.  So the question is whether a dedicated place for patches, with
>> no distracting complications, would be preferred.
>>
>
> Maybe. But I would leave the decision to those who are actually handling
> patches. And, unless they prefer new tools, I would continue to store
> patches in Bugzilla and avoid yet another system, yet another registration
> for new volunteers, yet another workflow to learn.
>
+1

>
> Regards,
>   Andrea.
>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


Re: Review Board

2013-03-10 Thread Andrea Pescetti

On 08/03/2013 Rob Weir wrote:

That's exactly the issue.  The mailing list is so busy that new
volunteers get lost, and their patches as well.  And if they toss
their patches to bugzilla, the patches can easily be lost there was
well.  So the question is whether a dedicated place for patches, with
no distracting complications, would be preferred.


Maybe. But I would leave the decision to those who are actually handling 
patches. And, unless they prefer new tools, I would continue to store 
patches in Bugzilla and avoid yet another system, yet another 
registration for new volunteers, yet another workflow to learn.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Review Board

2013-03-09 Thread Daniel Shahaf
Dave Fisher wrote on Fri, Mar 08, 2013 at 15:35:31 -0800:
> 
> On Mar 8, 2013, at 1:47 PM, Rob Weir wrote:
> 
> > On Fri, Mar 8, 2013 at 4:21 PM, janI  wrote:
> >> On 8 March 2013 22:16, Rob Weir  wrote:
> >> 
> >>> On Fri, Mar 8, 2013 at 3:51 PM, Dave Fisher  wrote:
>  Only if we are going to become a Review Then Commit project.
>  
> >>> 
> >>> I was thinking more of whether it would be useful for working with
> >>> patch contributions from contributors.
> >>> 
> >> 
> >> Just be careful not to set level too high for volunteers, in my opinion the
> >> mailing list is more than enough, no need for extra layers to complicate
> >> matters.
> >> 
> > 
> > That's exactly the issue.  The mailing list is so busy that new
> > volunteers get lost, and their patches as well.  And if they toss
> > their patches to bugzilla, the patches can easily be lost there was
> > well.  So the question is whether a dedicated place for patches, with
> > no distracting complications, would be preferred.
> 
> If there are volunteers who will do RTC work for new code contributors
> then this might be an improvement to bug tracking.

FWIW, over at Subversion we (a) have a 'patch' label in the bug tracker,
(b) have a volunteer who pings [patch] threads that have petered out
without the patch being either applie or rejected.

http://subversion.apache.org/docs/community-guide/roles#patch-manager

Perhaps one or both of these ideas would be useful here.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Review Board

2013-03-08 Thread Dave Fisher

On Mar 8, 2013, at 1:47 PM, Rob Weir wrote:

> On Fri, Mar 8, 2013 at 4:21 PM, janI  wrote:
>> On 8 March 2013 22:16, Rob Weir  wrote:
>> 
>>> On Fri, Mar 8, 2013 at 3:51 PM, Dave Fisher  wrote:
 Only if we are going to become a Review Then Commit project.
 
>>> 
>>> I was thinking more of whether it would be useful for working with
>>> patch contributions from contributors.
>>> 
>> 
>> Just be careful not to set level too high for volunteers, in my opinion the
>> mailing list is more than enough, no need for extra layers to complicate
>> matters.
>> 
> 
> That's exactly the issue.  The mailing list is so busy that new
> volunteers get lost, and their patches as well.  And if they toss
> their patches to bugzilla, the patches can easily be lost there was
> well.  So the question is whether a dedicated place for patches, with
> no distracting complications, would be preferred.

If there are volunteers who will do RTC work for new code contributors then 
this might be an improvement to bug tracking.

Regards,
Dave


> 
> -Rob
> 
>> rgds
>> Jan I.
>> 
>>> 
>>> -Rob
>>> 
>>> 
 Otherwise I think it becomes yet another system to learn how to use.
 
 On Mar 8, 2013, at 9:10 AM, Rob Weir wrote:
 
> https://reviews.apache.org
> 
> I didn't know that this existed at Apache.  Should we be using it?
> 
> -Rob
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org
 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Review Board

2013-03-08 Thread Rob Weir
On Fri, Mar 8, 2013 at 4:21 PM, janI  wrote:
> On 8 March 2013 22:16, Rob Weir  wrote:
>
>> On Fri, Mar 8, 2013 at 3:51 PM, Dave Fisher  wrote:
>> > Only if we are going to become a Review Then Commit project.
>> >
>>
>> I was thinking more of whether it would be useful for working with
>> patch contributions from contributors.
>>
>
> Just be careful not to set level too high for volunteers, in my opinion the
> mailing list is more than enough, no need for extra layers to complicate
> matters.
>

That's exactly the issue.  The mailing list is so busy that new
volunteers get lost, and their patches as well.  And if they toss
their patches to bugzilla, the patches can easily be lost there was
well.  So the question is whether a dedicated place for patches, with
no distracting complications, would be preferred.

-Rob

> rgds
> Jan I.
>
>>
>> -Rob
>>
>>
>> > Otherwise I think it becomes yet another system to learn how to use.
>> >
>> > On Mar 8, 2013, at 9:10 AM, Rob Weir wrote:
>> >
>> >> https://reviews.apache.org
>> >>
>> >> I didn't know that this existed at Apache.  Should we be using it?
>> >>
>> >> -Rob
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> >>
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> > For additional commands, e-mail: dev-h...@openoffice.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Review Board

2013-03-08 Thread janI
On 8 March 2013 22:16, Rob Weir  wrote:

> On Fri, Mar 8, 2013 at 3:51 PM, Dave Fisher  wrote:
> > Only if we are going to become a Review Then Commit project.
> >
>
> I was thinking more of whether it would be useful for working with
> patch contributions from contributors.
>

Just be careful not to set level too high for volunteers, in my opinion the
mailing list is more than enough, no need for extra layers to complicate
matters.

rgds
Jan I.

>
> -Rob
>
>
> > Otherwise I think it becomes yet another system to learn how to use.
> >
> > On Mar 8, 2013, at 9:10 AM, Rob Weir wrote:
> >
> >> https://reviews.apache.org
> >>
> >> I didn't know that this existed at Apache.  Should we be using it?
> >>
> >> -Rob
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


Re: Review Board

2013-03-08 Thread Rob Weir
On Fri, Mar 8, 2013 at 3:51 PM, Dave Fisher  wrote:
> Only if we are going to become a Review Then Commit project.
>

I was thinking more of whether it would be useful for working with
patch contributions from contributors.

-Rob


> Otherwise I think it becomes yet another system to learn how to use.
>
> On Mar 8, 2013, at 9:10 AM, Rob Weir wrote:
>
>> https://reviews.apache.org
>>
>> I didn't know that this existed at Apache.  Should we be using it?
>>
>> -Rob
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Review Board

2013-03-08 Thread Kay Schenk
On Fri, Mar 8, 2013 at 12:51 PM, Dave Fisher  wrote:

> Only if we are going to become a Review Then Commit project.
>
> Otherwise I think it becomes yet another system to learn how to use.
>

I agree with Dave on this.  I don't see a particular need. But,
interesting, none the less.



>
> On Mar 8, 2013, at 9:10 AM, Rob Weir wrote:
>
> > https://reviews.apache.org
> >
> > I didn't know that this existed at Apache.  Should we be using it?
> >
> > -Rob
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 

MzK

"Achieving happiness requires the right combination of Zen and Zin."


Re: Review Board

2013-03-08 Thread Dave Fisher
Only if we are going to become a Review Then Commit project.

Otherwise I think it becomes yet another system to learn how to use.

On Mar 8, 2013, at 9:10 AM, Rob Weir wrote:

> https://reviews.apache.org
> 
> I didn't know that this existed at Apache.  Should we be using it?
> 
> -Rob
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org