Re: Seeking Bugzilla Admin Volunteers

2012-01-23 Thread Rob Weir
On Thu, Jan 12, 2012 at 2:16 PM, Rob Weir robw...@apache.org wrote:
 As far as I have been able to determine, no one in the project seems
 to have the ability to do anything in our Bugzilla instance beyond the
 basic operations that any member of the public is able to do.   We
 need to get a handful of people to have some elevated permissions to
 edit bugs, edit components, etc., so we can manage the quality process
 for the upcoming 3.4 release.

 I'll enter a JIRA issue asking that myself, and whichever other
 committers want to be included, be added to a group that will have the
 following additional Bugzilla permissions:


I've gone ahead and enter the JIRA issue for this with Infra@:

https://issues.apache.org/jira/browse/INFRA-4350

Note that I did also request that all other accounts, other then the
named admins, be reset back to their basic permissions.  The new
admins can then quickly re-enable permissions for project members as
appropriate.   As David mentioned earlier in this thread, we'll want
to get into the practice of enabling a set of privileges for all
committers.


 - editbugs
 - editcomponents
 - canconfirm
 - editkeywords

 Having these additional permissions will especially be critical for
 those engaging in QA, I think.

 I'm not sure if Infra will do it (security concerns, etc.), but it
 would also be good to have one or two admin-level committers, with the
 editusers permission, so they can enable the above permissions for
 other users without going through Infra.

 So if you want to be on the initial batch, please respond to this note
 and let me know what your Bugzilla ID is. This is not necessarily the
 same as your Apache ID.   And if you don't yet have a Bugzilla account
 for the project, you can request one here:
 https://issues.apache.org/ooo/

 Thanks!

 -Rob


Re: Seeking Bugzilla Admin Volunteers

2012-01-23 Thread Rob Weir
On Mon, Jan 23, 2012 at 2:38 PM, Rob Weir robw...@apache.org wrote:
 On Thu, Jan 12, 2012 at 2:16 PM, Rob Weir robw...@apache.org wrote:
 As far as I have been able to determine, no one in the project seems
 to have the ability to do anything in our Bugzilla instance beyond the
 basic operations that any member of the public is able to do.   We
 need to get a handful of people to have some elevated permissions to
 edit bugs, edit components, etc., so we can manage the quality process
 for the upcoming 3.4 release.

 I'll enter a JIRA issue asking that myself, and whichever other
 committers want to be included, be added to a group that will have the
 following additional Bugzilla permissions:


 I've gone ahead and enter the JIRA issue for this with Infra@:

 https://issues.apache.org/jira/browse/INFRA-4350


Wow, that was fast!  Thanks to Tony, we now have a small group of BZ
admins for the project.

is there anything urgent we need to look at right now?  If not, maybe
a new thread on what we want to do.  Maybe simplification and
reduction in number of components? Clarification/adjustment of the
workflow?  What we have now is very confusing to users.

-Rob

 Note that I did also request that all other accounts, other then the
 named admins, be reset back to their basic permissions.  The new
 admins can then quickly re-enable permissions for project members as
 appropriate.   As David mentioned earlier in this thread, we'll want
 to get into the practice of enabling a set of privileges for all
 committers.


 - editbugs
 - editcomponents
 - canconfirm
 - editkeywords

 Having these additional permissions will especially be critical for
 those engaging in QA, I think.

 I'm not sure if Infra will do it (security concerns, etc.), but it
 would also be good to have one or two admin-level committers, with the
 editusers permission, so they can enable the above permissions for
 other users without going through Infra.

 So if you want to be on the initial batch, please respond to this note
 and let me know what your Bugzilla ID is. This is not necessarily the
 same as your Apache ID.   And if you don't yet have a Bugzilla account
 for the project, you can request one here:
 https://issues.apache.org/ooo/

 Thanks!

 -Rob


Re: Seeking Bugzilla Admin Volunteers

2012-01-18 Thread Wolf Halton
On Mon, Jan 16, 2012 at 9:06 PM, Rob Weir robw...@apache.org wrote:

 On Mon, Jan 16, 2012 at 8:50 PM, Wolf Halton wolf.hal...@gmail.com
 wrote:
  I volunteer.
 

 I'll need your BZ login ID, which is not necessarily the same as your
 Apache ID.

  http://sourcefreedom.com
  On Jan 12, 2012 2:16 PM, Rob Weir robw...@apache.org wrote:
 
  As far as I have been able to determine, no one in the project seems
  to have the ability to do anything in our Bugzilla instance beyond the
  basic operations that any member of the public is able to do.   We
  need to get a handful of people to have some elevated permissions to
  edit bugs, edit components, etc., so we can manage the quality process
  for the upcoming 3.4 release.
 
  I'll enter a JIRA issue asking that myself, and whichever other
  committers want to be included, be added to a group that will have the
  following additional Bugzilla permissions:
 
  - editbugs
  - editcomponents
  - canconfirm
  - editkeywords
 
  Having these additional permissions will especially be critical for
  those engaging in QA, I think.
 
  I'm not sure if Infra will do it (security concerns, etc.), but it
  would also be good to have one or two admin-level committers, with the
  editusers permission, so they can enable the above permissions for
  other users without going through Infra.
 
  So if you want to be on the initial batch, please respond to this note
  and let me know what your Bugzilla ID is. This is not necessarily the
  same as your Apache ID.   And if you don't yet have a Bugzilla account
  for the project, you can request one here:
  https://issues.apache.org/ooo/
 
  Thanks!
 
  -Rob
 


My bugzilla login is wolf.hal...@gmail.com

-- 
This Apt Has Super Cow Powers - http://sourcefreedom.com
Advancing Libraries Together - http://LYRASIS.org


Re: Seeking Bugzilla Admin Volunteers

2012-01-16 Thread Rob Weir
On Sun, Jan 15, 2012 at 10:05 AM, Dave Fisher dave2w...@comcast.net wrote:

 On Jan 15, 2012, at 1:49 AM, Andrea Pescetti wrote:

 Rob Weir wrote:
 Did you read anyone say that current privileges are going to be
 dropped?  I certainly did not say that.

 No, but that was a doubt I had: in the process of granting new privileges, 
 it might be that someone notices that a lot of people already have high 
 privileges, and that this group includes people currently unaffiliated with 
 the project. I was just making sure that current privileges are not dropped 
 now: this will still be an issue, but it can be dealt with separately.

 We need to have a common set of privileges for ALL committers. We should not 
 have to request it, it should be done.


That is a curious statement, considering that:

- committers are not automatically subscribed to ooo-private.

- committers are not automatically list moderators.  They need to request it.

- committers are not automatically blog editors.  They need to request it.

- committers are not automatically wiki editors or admins.  They need
to request it.

- committers are not automatically forum editors or admins.  They need
to request it.

So far as I can tell, the only thing that happens automatically for
committers is SVN access. And even that is not really automatic.

Given the above, I had no expectations that Bugzilla access for
committers would happen without request.  Do you have a reason to be
optimistic in this case?

And are you suggesting we wait for this to happen?  Or would it make
more sense to get a few volunteers, per my original note, and go
forward with that for now?

-Rob


 The PPMC should decide what the normal set of privileges should be for the 
 general community as well.

 Maybe as another thread this will noticed.

 I am really glad I rejected using BZ to discuss the website a few months ago 
 since no privileges with the AOO BZ have been assigned to anyone who wasn't 
 with the former project yet former members who have not continued with this 
 project still have privileges.

 This is a huge issue and ought to be addressed this week.

 Regards,
 Dave


 Regards,
  Andrea.



Re: Seeking Bugzilla Admin Volunteers

2012-01-16 Thread Rob Weir
On Sun, Jan 15, 2012 at 4:49 AM, Andrea Pescetti pesce...@apache.org wrote:
 Rob Weir wrote:

 Did you read anyone say that current privileges are going to be
 dropped?  I certainly did not say that.


 No, but that was a doubt I had: in the process of granting new privileges,
 it might be that someone notices that a lot of people already have high
 privileges, and that this group includes people currently unaffiliated with
 the project. I was just making sure that current privileges are not dropped
 now: this will still be an issue, but it can be dealt with separately.


That is something we need to deal with, eventually.  Having escalated
privileges associated with people no longer involved with the project
is bad for security. (Wasn't the vector of the last hack of the Apache
website via a XSS attack of bug tracking admin accounts?)

Remember, we can always add permissions back for someone if they did
not see and respond to this note.

Another option is to generate a report of all ID's with elevated
privileges and have that sent to ooo-private where we can decide next
steps.

-Rob

 Regards,
  Andrea.


Re: Seeking Bugzilla Admin Volunteers

2012-01-16 Thread Dave Fisher

On Jan 16, 2012, at 12:34 PM, Rob Weir wrote:

 On Sun, Jan 15, 2012 at 10:05 AM, Dave Fisher dave2w...@comcast.net wrote:
 
 On Jan 15, 2012, at 1:49 AM, Andrea Pescetti wrote:
 
 Rob Weir wrote:
 Did you read anyone say that current privileges are going to be
 dropped?  I certainly did not say that.
 
 No, but that was a doubt I had: in the process of granting new privileges, 
 it might be that someone notices that a lot of people already have high 
 privileges, and that this group includes people currently unaffiliated with 
 the project. I was just making sure that current privileges are not dropped 
 now: this will still be an issue, but it can be dealt with separately.
 
 We need to have a common set of privileges for ALL committers. We should not 
 have to request it, it should be done.
 
 
 That is a curious statement, considering that:

For the BZ to be useful to the community it must be possible for any 
contributor to have sufficient privileges to engage in the process.

In the project's that I work on like Apache POI everyone has BZ rights to 
create issues and change status. AFAIK it is very open and very helpful and 
actually leads to valuable conversations with users. Even if some are similar 
to a no its not a bug yes it is. No matter.

You are allowed basic rights to open, comment, update and close JIRA issues at 
Apache. Admin rights are special.

BTW - an open BZ provides another path for contributors to get attention and 
possibly become committers.

 
 - committers are not automatically subscribed to ooo-private.

So far, every committer is given the opportunity to do so. And it is 
exceedingly easy.

 - committers are not automatically list moderators.  They need to request it.
 
 - committers are not automatically blog editors.  They need to request it.
 
 - committers are not automatically wiki editors or admins.  They need
 to request it.

How much use has the project made of OOODEV cwiki vs. OOOUSERS cwiki? One is by 
request and the other is open to anyone.

IMO we should ask Infrastructure to drop OOODEV.

 
 - committers are not automatically forum editors or admins.  They need
 to request it.
 
 So far as I can tell, the only thing that happens automatically for
 committers is SVN access. And even that is not really automatic.

I watch the Infrastructure ML. It is part of the workflow when the PPMC 
requests the committer's id. An incubator committer is a more difficult setup 
than a TLP committer, there is an extra step for Apache CMS permission.

 
 Given the above, I had no expectations that Bugzilla access for
 committers would happen without request.  Do you have a reason to be
 optimistic in this case?

We have our own, separate BZ that is NOT part of the normal Apache BZ. Perhaps 
it was missed back in July, but we are responsible. That's the cost for keeping 
the old issue ids.


 
 And are you suggesting we wait for this to happen?

Given that we are accountable for this BZ we as the PPMC are responsible for 
its state.

  Or would it make
 more sense to get a few volunteers, per my original note, and go
 forward with that for now?

Yes, I agree that we need to get some volunteers. We should define what we want 
our BZ admins to do.

I would like to know the current mysterious closed policy and workflow in this 
custom BZ. It really bothers me that we have no clue who has authority and who 
doesn't. We are responsible.

I would like to discuss what the policy should become.  IMO - Open up normal, 
non-admin permissions to all of the project's committers. Also, open normal 
permissions up to the community as a whole. If someone abuses their privileges 
then remove them. The BZ admin will need to deal with Spammers.

Regards,
Dave

 
 -Rob
 
 
 The PPMC should decide what the normal set of privileges should be for the 
 general community as well.
 
 Maybe as another thread this will noticed.
 
 I am really glad I rejected using BZ to discuss the website a few months ago 
 since no privileges with the AOO BZ have been assigned to anyone who wasn't 
 with the former project yet former members who have not continued with this 
 project still have privileges.
 
 This is a huge issue and ought to be addressed this week.
 
 Regards,
 Dave
 
 
 Regards,
  Andrea.
 



Re: Seeking Bugzilla Admin Volunteers

2012-01-16 Thread Rob Weir
On Mon, Jan 16, 2012 at 5:18 PM, Dave Fisher dave2w...@comcast.net wrote:

 On Jan 16, 2012, at 12:34 PM, Rob Weir wrote:

 On Sun, Jan 15, 2012 at 10:05 AM, Dave Fisher dave2w...@comcast.net wrote:

 On Jan 15, 2012, at 1:49 AM, Andrea Pescetti wrote:

 Rob Weir wrote:
 Did you read anyone say that current privileges are going to be
 dropped?  I certainly did not say that.

 No, but that was a doubt I had: in the process of granting new privileges, 
 it might be that someone notices that a lot of people already have high 
 privileges, and that this group includes people currently unaffiliated 
 with the project. I was just making sure that current privileges are not 
 dropped now: this will still be an issue, but it can be dealt with 
 separately.

 We need to have a common set of privileges for ALL committers. We should 
 not have to request it, it should be done.


 That is a curious statement, considering that:

 For the BZ to be useful to the community it must be possible for any 
 contributor to have sufficient privileges to engage in the process.

 In the project's that I work on like Apache POI everyone has BZ rights to 
 create issues and change status. AFAIK it is very open and very helpful and 
 actually leads to valuable conversations with users. Even if some are similar 
 to a no its not a bug yes it is. No matter.

 You are allowed basic rights to open, comment, update and close JIRA issues 
 at Apache. Admin rights are special.

 BTW - an open BZ provides another path for contributors to get attention and 
 possibly become committers.


 - committers are not automatically subscribed to ooo-private.

 So far, every committer is given the opportunity to do so. And it is 
 exceedingly easy.

 - committers are not automatically list moderators.  They need to request it.

 - committers are not automatically blog editors.  They need to request it.

 - committers are not automatically wiki editors or admins.  They need
 to request it.

 How much use has the project made of OOODEV cwiki vs. OOOUSERS cwiki? One is 
 by request and the other is open to anyone.

 IMO we should ask Infrastructure to drop OOODEV.


 - committers are not automatically forum editors or admins.  They need
 to request it.

 So far as I can tell, the only thing that happens automatically for
 committers is SVN access. And even that is not really automatic.

 I watch the Infrastructure ML. It is part of the workflow when the PPMC 
 requests the committer's id. An incubator committer is a more difficult setup 
 than a TLP committer, there is an extra step for Apache CMS permission.


 Given the above, I had no expectations that Bugzilla access for
 committers would happen without request.  Do you have a reason to be
 optimistic in this case?

 We have our own, separate BZ that is NOT part of the normal Apache BZ. 
 Perhaps it was missed back in July, but we are responsible. That's the cost 
 for keeping the old issue ids.



 And are you suggesting we wait for this to happen?

 Given that we are accountable for this BZ we as the PPMC are responsible for 
 its state.

  Or would it make
 more sense to get a few volunteers, per my original note, and go
 forward with that for now?

 Yes, I agree that we need to get some volunteers. We should define what we 
 want our BZ admins to do.


OK.That is clearer.  When you previously said, We should not have
to request it, it should be done I took that as it should be
technologically done, and done automatically without request.  I see
now that you mean it should be done as a matter of our ordinary
process and workflow, although it may require a manual step.  +1 on
that.

 I would like to know the current mysterious closed policy and workflow in 
 this custom BZ. It really bothers me that we have no clue who has authority 
 and who doesn't. We are responsible.

 I would like to discuss what the policy should become.  IMO - Open up normal, 
 non-admin permissions to all of the project's committers. Also, open normal 
 permissions up to the community as a whole. If someone abuses their 
 privileges then remove them. The BZ admin will need to deal with Spammers.


+1   But is there any way we can have our own BZ Admin distribution
list?  It is extremely weird that I get BZ Admin emails for all
projects, including AOO, though I appear to have admin privileges for
none of them

 Regards,
 Dave


 -Rob


 The PPMC should decide what the normal set of privileges should be for the 
 general community as well.

 Maybe as another thread this will noticed.

 I am really glad I rejected using BZ to discuss the website a few months 
 ago since no privileges with the AOO BZ have been assigned to anyone who 
 wasn't with the former project yet former members who have not continued 
 with this project still have privileges.

 This is a huge issue and ought to be addressed this week.

 Regards,
 Dave


 Regards,
  Andrea.




RE: Seeking Bugzilla Admin Volunteers

2012-01-16 Thread Dennis E. Hamilton
+1 on our own BZ Admin list.  

 - Dennis

-Original Message-
From: Rob Weir [mailto:robw...@apache.org] 
Sent: Monday, January 16, 2012 14:39
To: ooo-dev@incubator.apache.org
Subject: Re: Seeking Bugzilla Admin Volunteers

[ ... ]
 I would like to discuss what the policy should become.  IMO - Open up normal, 
 non-admin permissions to all of the project's committers. Also, open normal 
 permissions up to the community as a whole. If someone abuses their 
 privileges then remove them. The BZ admin will need to deal with Spammers.


+1   But is there any way we can have our own BZ Admin distribution
list?  It is extremely weird that I get BZ Admin emails for all
projects, including AOO, though I appear to have admin privileges for
none of them

 Regards,
 Dave
[ ... ]



Re: Seeking Bugzilla Admin Volunteers

2012-01-16 Thread Wolf Halton
I volunteer.

http://sourcefreedom.com
On Jan 12, 2012 2:16 PM, Rob Weir robw...@apache.org wrote:

 As far as I have been able to determine, no one in the project seems
 to have the ability to do anything in our Bugzilla instance beyond the
 basic operations that any member of the public is able to do.   We
 need to get a handful of people to have some elevated permissions to
 edit bugs, edit components, etc., so we can manage the quality process
 for the upcoming 3.4 release.

 I'll enter a JIRA issue asking that myself, and whichever other
 committers want to be included, be added to a group that will have the
 following additional Bugzilla permissions:

 - editbugs
 - editcomponents
 - canconfirm
 - editkeywords

 Having these additional permissions will especially be critical for
 those engaging in QA, I think.

 I'm not sure if Infra will do it (security concerns, etc.), but it
 would also be good to have one or two admin-level committers, with the
 editusers permission, so they can enable the above permissions for
 other users without going through Infra.

 So if you want to be on the initial batch, please respond to this note
 and let me know what your Bugzilla ID is. This is not necessarily the
 same as your Apache ID.   And if you don't yet have a Bugzilla account
 for the project, you can request one here:
 https://issues.apache.org/ooo/

 Thanks!

 -Rob



Re: Seeking Bugzilla Admin Volunteers

2012-01-16 Thread Rob Weir
On Mon, Jan 16, 2012 at 8:50 PM, Wolf Halton wolf.hal...@gmail.com wrote:
 I volunteer.


I'll need your BZ login ID, which is not necessarily the same as your Apache ID.

 http://sourcefreedom.com
 On Jan 12, 2012 2:16 PM, Rob Weir robw...@apache.org wrote:

 As far as I have been able to determine, no one in the project seems
 to have the ability to do anything in our Bugzilla instance beyond the
 basic operations that any member of the public is able to do.   We
 need to get a handful of people to have some elevated permissions to
 edit bugs, edit components, etc., so we can manage the quality process
 for the upcoming 3.4 release.

 I'll enter a JIRA issue asking that myself, and whichever other
 committers want to be included, be added to a group that will have the
 following additional Bugzilla permissions:

 - editbugs
 - editcomponents
 - canconfirm
 - editkeywords

 Having these additional permissions will especially be critical for
 those engaging in QA, I think.

 I'm not sure if Infra will do it (security concerns, etc.), but it
 would also be good to have one or two admin-level committers, with the
 editusers permission, so they can enable the above permissions for
 other users without going through Infra.

 So if you want to be on the initial batch, please respond to this note
 and let me know what your Bugzilla ID is. This is not necessarily the
 same as your Apache ID.   And if you don't yet have a Bugzilla account
 for the project, you can request one here:
 https://issues.apache.org/ooo/

 Thanks!

 -Rob



Re: Seeking Bugzilla Admin Volunteers

2012-01-15 Thread Andrea Pescetti

Rob Weir wrote:

Did you read anyone say that current privileges are going to be
dropped?  I certainly did not say that.


No, but that was a doubt I had: in the process of granting new 
privileges, it might be that someone notices that a lot of people 
already have high privileges, and that this group includes people 
currently unaffiliated with the project. I was just making sure that 
current privileges are not dropped now: this will still be an issue, but 
it can be dealt with separately.


Regards,
  Andrea.


Re: Seeking Bugzilla Admin Volunteers

2012-01-15 Thread Dave Fisher

On Jan 15, 2012, at 1:49 AM, Andrea Pescetti wrote:

 Rob Weir wrote:
 Did you read anyone say that current privileges are going to be
 dropped?  I certainly did not say that.
 
 No, but that was a doubt I had: in the process of granting new privileges, it 
 might be that someone notices that a lot of people already have high 
 privileges, and that this group includes people currently unaffiliated with 
 the project. I was just making sure that current privileges are not dropped 
 now: this will still be an issue, but it can be dealt with separately.

We need to have a common set of privileges for ALL committers. We should not 
have to request it, it should be done.

The PPMC should decide what the normal set of privileges should be for the 
general community as well.

Maybe as another thread this will noticed.

I am really glad I rejected using BZ to discuss the website a few months ago 
since no privileges with the AOO BZ have been assigned to anyone who wasn't 
with the former project yet former members who have not continued with this 
project still have privileges.

This is a huge issue and ought to be addressed this week.

Regards,
Dave

 
 Regards,
  Andrea.



Re: Seeking Bugzilla Admin Volunteers

2012-01-14 Thread David McKay



On 13/01/12 23:07, Dennis E. Hamilton wrote:

Great!!

One thing to do: Go into your bugzilla account and change your e-mail address!  
The openoffice.org one will stop working eventually.  Also, when you make the 
change, your history and any issues that have your name on them in any way will 
be preserved under the new ID.

  - Dennis

-Original Message-
From: David McKay [mailto:dmc...@btconnect.com]
Sent: Friday, January 13, 2012 14:11
To: dennis.hamil...@acm.org
Cc: ooo-dev@incubator.apache.org; thegur...@apache.org
Subject: Re: Seeking Bugzilla Admin Volunteers

On 13/01/12 20:02, Dennis E. Hamilton wrote:

For David McKay, see if thegur...@apache.org is registered.

On the other hand, I would not elevate his privileges or ask that he be set up 
as administrator without having his confirmation that he's still interested and 
available.

   - Dennis

-Original Message-
From: Rob Weir [mailto:robw...@apache.org]
Sent: Friday, January 13, 2012 04:35
To: ooo-dev@incubator.apache.org
Subject: Re: Seeking Bugzilla Admin Volunteers

On Fri, Jan 13, 2012 at 4:48 AM, tjt...@apache.org   wrote:

On 1/12/2012 14:16, Rob Weir wrote:
[snip]


So if you want to be on the initial batch, please respond to this note
and let me know what your Bugzilla ID is. This is not necessarily the
same as your Apache ID.   And if you don't yet have a Bugzilla account
for the project, you can request one here:
https://issues.apache.org/ooo/

Thanks!

-Rob



Count me in (t...@apache.org) for both permissions and admin. I already have
some elevated permissions for Documentation project bugs.

I will try to make contact with David McKay, to see if he's still
interested. It would be nice to have an admin who actually knows what to do.


I'd consider him as already volunteered per his previous statements.
Do you know his Bugzilla ID?

-Rob


--
/tj/


I'm still interested and available, real-world job permitting. I'm in
the UK time-zone if that has any bearing on anything.

Dave.

Done.


Re: Seeking Bugzilla Admin Volunteers

2012-01-14 Thread Andrea Pescetti

On 12/01/2012 Rob Weir wrote:

I'll enter a JIRA issue asking that myself, and whichever other
committers want to be included, be added to a group that will have the
following additional Bugzilla permissions:
- editbugs
- editcomponents
- canconfirm
- editkeywords


I still have extended permissions (on bugs, not on users) that were 
preserved with the Bugzilla migration. They come handy from time to 
time, so please do not drop them (or just re-add me to the list). User 
pescetti AT apache.org


Thanks,
  Andrea.


Re: Seeking Bugzilla Admin Volunteers

2012-01-14 Thread Ariel Constenla-Haile
Hi *,

On Sat, Jan 14, 2012 at 11:52:03PM +0100, Andrea Pescetti wrote:
 On 12/01/2012 Rob Weir wrote:
 I'll enter a JIRA issue asking that myself, and whichever other
 committers want to be included, be added to a group that will have the
 following additional Bugzilla permissions:
 - editbugs
 - editcomponents
 - canconfirm
 - editkeywords
 
 I still have extended permissions (on bugs, not on users) that were
 preserved with the Bugzilla migration. They come handy from time to
 time, so please do not drop them (or just re-add me to the list).
 User pescetti AT apache.org

are current privileges going to dropped?
I didn't understand it this way (though I confess I do not read *all*
mail coming from this list - otherwise I wouldn't have time to spend on
doing what I like ;) ).

Just in case they're going to be dropped, please keep my current status
(canconfirm et. al.): arielch AT apache.org


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpYTargf9a6x.pgp
Description: PGP signature


Re: Seeking Bugzilla Admin Volunteers

2012-01-14 Thread Dave Fisher

On Jan 14, 2012, at 4:28 PM, Ariel Constenla-Haile wrote:

 Hi *,
 
 On Sat, Jan 14, 2012 at 11:52:03PM +0100, Andrea Pescetti wrote:
 On 12/01/2012 Rob Weir wrote:
 I'll enter a JIRA issue asking that myself, and whichever other
 committers want to be included, be added to a group that will have the
 following additional Bugzilla permissions:
 - editbugs
 - editcomponents
 - canconfirm
 - editkeywords
 
 I still have extended permissions (on bugs, not on users) that were
 preserved with the Bugzilla migration. They come handy from time to
 time, so please do not drop them (or just re-add me to the list).
 User pescetti AT apache.org
 
 are current privileges going to dropped?
 I didn't understand it this way (though I confess I do not read *all*
 mail coming from this list - otherwise I wouldn't have time to spend on
 doing what I like ;) ).
 
 Just in case they're going to be dropped, please keep my current status
 (canconfirm et. al.): arielch AT apache.org

IMO the default permissions in the OOO Bugzilla to be VERY constrained.

I fixed an issue a few weeks ago with the website and could not do anything!

Does anyone have a reference about the workflow in this bugzilla? It is 
definitely not what I'm used to in the normal Apache bugzilla. Let's consider 
making our special BZ much more open!

Regards,
Dave

Re: Seeking Bugzilla Admin Volunteers

2012-01-14 Thread Rob Weir
On Sat, Jan 14, 2012 at 7:28 PM, Ariel Constenla-Haile
arie...@apache.org wrote:
 Hi *,

 On Sat, Jan 14, 2012 at 11:52:03PM +0100, Andrea Pescetti wrote:
 On 12/01/2012 Rob Weir wrote:
 I'll enter a JIRA issue asking that myself, and whichever other
 committers want to be included, be added to a group that will have the
 following additional Bugzilla permissions:
 - editbugs
 - editcomponents
 - canconfirm
 - editkeywords

 I still have extended permissions (on bugs, not on users) that were
 preserved with the Bugzilla migration. They come handy from time to
 time, so please do not drop them (or just re-add me to the list).
 User pescetti AT apache.org

 are current privileges going to dropped?
 I didn't understand it this way (though I confess I do not read *all*
 mail coming from this list - otherwise I wouldn't have time to spend on
 doing what I like ;) ).


Did you read anyone say that current privileges are going to be
dropped?  I certainly did not say that.

-Rob

 Just in case they're going to be dropped, please keep my current status
 (canconfirm et. al.): arielch AT apache.org


 Regards
 --
 Ariel Constenla-Haile
 La Plata, Argentina


Re: Seeking Bugzilla Admin Volunteers

2012-01-13 Thread tj

On 1/12/2012 14:16, Rob Weir wrote:
[snip]


So if you want to be on the initial batch, please respond to this note
and let me know what your Bugzilla ID is. This is not necessarily the
same as your Apache ID.   And if you don't yet have a Bugzilla account
for the project, you can request one here:
https://issues.apache.org/ooo/

Thanks!

-Rob


Count me in (t...@apache.org) for both permissions and admin. I already 
have some elevated permissions for Documentation project bugs.


I will try to make contact with David McKay, to see if he's still 
interested. It would be nice to have an admin who actually knows what to do.


--
/tj/



Re: Seeking Bugzilla Admin Volunteers

2012-01-13 Thread Rob Weir
On Fri, Jan 13, 2012 at 4:48 AM, tj t...@apache.org wrote:
 On 1/12/2012 14:16, Rob Weir wrote:
 [snip]


 So if you want to be on the initial batch, please respond to this note
 and let me know what your Bugzilla ID is. This is not necessarily the
 same as your Apache ID.   And if you don't yet have a Bugzilla account
 for the project, you can request one here:
 https://issues.apache.org/ooo/

 Thanks!

 -Rob


 Count me in (t...@apache.org) for both permissions and admin. I already have
 some elevated permissions for Documentation project bugs.

 I will try to make contact with David McKay, to see if he's still
 interested. It would be nice to have an admin who actually knows what to do.


I'd consider him as already volunteered per his previous statements.
Do you know his Bugzilla ID?

-Rob

 --
 /tj/



RE: Seeking Bugzilla Admin Volunteers

2012-01-13 Thread Dennis E. Hamilton
For David McKay, see if thegur...@apache.org is registered.

On the other hand, I would not elevate his privileges or ask that he be set up 
as administrator without having his confirmation that he's still interested and 
available.  

 - Dennis

-Original Message-
From: Rob Weir [mailto:robw...@apache.org] 
Sent: Friday, January 13, 2012 04:35
To: ooo-dev@incubator.apache.org
Subject: Re: Seeking Bugzilla Admin Volunteers

On Fri, Jan 13, 2012 at 4:48 AM, tj t...@apache.org wrote:
 On 1/12/2012 14:16, Rob Weir wrote:
 [snip]


 So if you want to be on the initial batch, please respond to this note
 and let me know what your Bugzilla ID is. This is not necessarily the
 same as your Apache ID.   And if you don't yet have a Bugzilla account
 for the project, you can request one here:
 https://issues.apache.org/ooo/

 Thanks!

 -Rob


 Count me in (t...@apache.org) for both permissions and admin. I already have
 some elevated permissions for Documentation project bugs.

 I will try to make contact with David McKay, to see if he's still
 interested. It would be nice to have an admin who actually knows what to do.


I'd consider him as already volunteered per his previous statements.
Do you know his Bugzilla ID?

-Rob

 --
 /tj/




Re: Fwd: Seeking Bugzilla Admin Volunteers

2012-01-13 Thread David McKay

Hi TJ,

My real-world job changed on the 1st December 2011 (I moved company), 
and Bugzilla is no longer part of my day-to-day role, but I guess I 
still remember most of what I knew! If I can be of assistance I'd be 
pleased to help.


My bugzilla ID is thegur...@openoffice.org.

Regards, Dave.

On 13/01/12 10:19, tj wrote:

Hi, David,

Per below, Rob is going to push this. If you're still interested, it 
would be *very* nice to have an admin like you, who knows what to do 
and how to do it.  --/tj/


 Original Message 
Subject: Seeking Bugzilla Admin Volunteers
Date: Thu, 12 Jan 2012 14:16:31 -0500
From: Rob Weir robw...@apache.org
Reply-To: ooo-dev@incubator.apache.org
To: ooo-dev@incubator.apache.org

As far as I have been able to determine, no one in the project seems
to have the ability to do anything in our Bugzilla instance beyond the
basic operations that any member of the public is able to do.   We
need to get a handful of people to have some elevated permissions to
edit bugs, edit components, etc., so we can manage the quality process
for the upcoming 3.4 release.

I'll enter a JIRA issue asking that myself, and whichever other
committers want to be included, be added to a group that will have the
following additional Bugzilla permissions:

- editbugs
- editcomponents
- canconfirm
- editkeywords

Having these additional permissions will especially be critical for
those engaging in QA, I think.

I'm not sure if Infra will do it (security concerns, etc.), but it
would also be good to have one or two admin-level committers, with the
editusers permission, so they can enable the above permissions for
other users without going through Infra.

So if you want to be on the initial batch, please respond to this note
and let me know what your Bugzilla ID is. This is not necessarily the
same as your Apache ID.   And if you don't yet have a Bugzilla account
for the project, you can request one here:
https://issues.apache.org/ooo/

Thanks!

-Rob








Re: Seeking Bugzilla Admin Volunteers

2012-01-13 Thread David McKay

On 13/01/12 20:02, Dennis E. Hamilton wrote:

For David McKay, see if thegur...@apache.org is registered.

On the other hand, I would not elevate his privileges or ask that he be set up 
as administrator without having his confirmation that he's still interested and 
available.

  - Dennis

-Original Message-
From: Rob Weir [mailto:robw...@apache.org]
Sent: Friday, January 13, 2012 04:35
To: ooo-dev@incubator.apache.org
Subject: Re: Seeking Bugzilla Admin Volunteers

On Fri, Jan 13, 2012 at 4:48 AM, tjt...@apache.org  wrote:

On 1/12/2012 14:16, Rob Weir wrote:
[snip]


So if you want to be on the initial batch, please respond to this note
and let me know what your Bugzilla ID is. This is not necessarily the
same as your Apache ID.   And if you don't yet have a Bugzilla account
for the project, you can request one here:
https://issues.apache.org/ooo/

Thanks!

-Rob



Count me in (t...@apache.org) for both permissions and admin. I already have
some elevated permissions for Documentation project bugs.

I will try to make contact with David McKay, to see if he's still
interested. It would be nice to have an admin who actually knows what to do.


I'd consider him as already volunteered per his previous statements.
Do you know his Bugzilla ID?

-Rob


--
/tj/

I'm still interested and available, real-world job permitting. I'm in 
the UK time-zone if that has any bearing on anything.


Dave.






Seeking Bugzilla Admin Volunteers

2012-01-12 Thread Rob Weir
As far as I have been able to determine, no one in the project seems
to have the ability to do anything in our Bugzilla instance beyond the
basic operations that any member of the public is able to do.   We
need to get a handful of people to have some elevated permissions to
edit bugs, edit components, etc., so we can manage the quality process
for the upcoming 3.4 release.

I'll enter a JIRA issue asking that myself, and whichever other
committers want to be included, be added to a group that will have the
following additional Bugzilla permissions:

- editbugs
- editcomponents
- canconfirm
- editkeywords

Having these additional permissions will especially be critical for
those engaging in QA, I think.

I'm not sure if Infra will do it (security concerns, etc.), but it
would also be good to have one or two admin-level committers, with the
editusers permission, so they can enable the above permissions for
other users without going through Infra.

So if you want to be on the initial batch, please respond to this note
and let me know what your Bugzilla ID is. This is not necessarily the
same as your Apache ID.   And if you don't yet have a Bugzilla account
for the project, you can request one here:
https://issues.apache.org/ooo/

Thanks!

-Rob


Re: Seeking Bugzilla Admin Volunteers

2012-01-12 Thread Herbert Duerr

Hi Rob,


So if you want to be on the initial batch, please respond to this note
and let me know what your Bugzilla ID is.


Count me in. My bugzilla id is h...@apache.org.

Herbert