Re: OOo Bugzilla data import available for review
On 08/25/2011 05:16 PM, TJ Frazier wrote: On 8/25/2011 18:54, Mark Thomas wrote: snip 3. All usernames and passwords remain unchanged with one exception: users with system administration rights have been removed from the admin group. Access to this group will be limited to members of the ASF infrastructure team (new volunteers always welcome). Enjoy. Mark [1] https://issues.apache.org/ooo/ [2] https://issues.apache.org/jira/browse/INFRA-3884 RBircher has reported on the JIRA ticket that logins do not work at all (confirming Andy's and my experience). Thanks to his helpful mention on this thread, we know that BZ email is disabled. This may be related to the problem, since BZ-test is recognizing user names with the full @oo.o suffix, but not passwords (or at least, login fails with bad-password message). I can't log in with either my old/existing OOo id or e-mail or anything else (???) -- MzK Music expresses that which cannot be said and on which it is impossible to be silent. -- Victor Hugo
RE: OOo Bugzilla data import available for review
Did you try your old (OOo) e-mail address and the password password? Or did you have administrative privileges before? - Dennis -Original Message- From: Kay Schenk [mailto:kay.sch...@gmail.com] Sent: Sunday, August 28, 2011 08:47 To: ooo-dev@incubator.apache.org Subject: Re: OOo Bugzilla data import available for review On 08/25/2011 05:16 PM, TJ Frazier wrote: On 8/25/2011 18:54, Mark Thomas wrote: snip 3. All usernames and passwords remain unchanged with one exception: users with system administration rights have been removed from the admin group. Access to this group will be limited to members of the ASF infrastructure team (new volunteers always welcome). Enjoy. Mark [1] https://issues.apache.org/ooo/ [2] https://issues.apache.org/jira/browse/INFRA-3884 RBircher has reported on the JIRA ticket that logins do not work at all (confirming Andy's and my experience). Thanks to his helpful mention on this thread, we know that BZ email is disabled. This may be related to the problem, since BZ-test is recognizing user names with the full @oo.o suffix, but not passwords (or at least, login fails with bad-password message). I can't log in with either my old/existing OOo id or e-mail or anything else (???) -- MzK Music expresses that which cannot be said and on which it is impossible to be silent. -- Victor Hugo
Re: OOo Bugzilla data import available for review
On 08/28/2011 09:09 AM, Dennis E. Hamilton wrote: Did you try your old (OOo) e-mail address and the password password? oh my! THAT actually worked. ha! I had never ever used my openoffice.org e-mail for any login to OO.o before. OK, then. Curious as to why my normal OO.o userid wouldn't take. :/ Or did you have administrative privileges before? - Dennis -Original Message- From: Kay Schenk [mailto:kay.sch...@gmail.com] Sent: Sunday, August 28, 2011 08:47 To: ooo-dev@incubator.apache.org Subject: Re: OOo Bugzilla data import available for review On 08/25/2011 05:16 PM, TJ Frazier wrote: On 8/25/2011 18:54, Mark Thomas wrote: snip 3. All usernames and passwords remain unchanged with one exception: users with system administration rights have been removed from the admin group. Access to this group will be limited to members of the ASF infrastructure team (new volunteers always welcome). Enjoy. Mark [1] https://issues.apache.org/ooo/ [2] https://issues.apache.org/jira/browse/INFRA-3884 RBircher has reported on the JIRA ticket that logins do not work at all (confirming Andy's and my experience). Thanks to his helpful mention on this thread, we know that BZ email is disabled. This may be related to the problem, since BZ-test is recognizing user names with the full @oo.o suffix, but not passwords (or at least, login fails with bad-password message). I can't log in with either my old/existing OOo id or e-mail or anything else (???) -- MzK Music expresses that which cannot be said and on which it is impossible to be silent. -- Victor Hugo
Re: OOo Bugzilla data import available for review
On 08/26/2011 12:54 AM, Mark Thomas wrote: The OOo Bugzilla data export provided to the ASF infrastructure team has been imported into a test instance[1] for your review. Excellent, thanks! Please review the import and report any *show stopper* issues to the infrastructure team via the Jira ticket created for this import. [2] I'm not sure whether this is a showstopper issue for the new import as it obviously wasn't too important for the maintainers of old OOo-IZ, but many issues got spam-attachments https://issues.apache.org/ooo/show_bug.cgi?id=113088 I see that JIRA does a more sensible thing for such kinds of attachments, by replying The attachment is not viewable in your browser due to security restrictions enabled by your Apache ooo Bugzilla administrator. but I think if it was possible to identify it would be even better if it was possible to remove the spam-attachments before they get imported into JIRA. An efficient to identify many spam-attachments in the JIRA import is to look for attachments by Unknown, which works because many of the abusers of the old system got banned and their userid got deleted. An even better best way would be to directly scan for spam. Herbert
Re: OOo Bugzilla data import available for review
Am 08/26/2011 08:04 AM, schrieb Herbert Duerr: On 08/26/2011 12:54 AM, Mark Thomas wrote: The OOo Bugzilla data export provided to the ASF infrastructure team has been imported into a test instance[1] for your review. Excellent, thanks! Yes, thanks a lot for creating the test inatance. :-) Please review the import and report any *show stopper* issues to the infrastructure team via the Jira ticket created for this import. [2] I'm not sure whether this is a showstopper issue for the new import as it obviously wasn't too important for the maintainers of old OOo-IZ, but many issues got spam-attachments https://issues.apache.org/ooo/show_bug.cgi?id=113088 I see that JIRA does a more sensible thing for such kinds of attachments, by replying The attachment is not viewable in your browser due to security restrictions enabled by your Apache ooo Bugzilla administrator. but I think if it was possible to identify it would be even better if it was possible to remove the spam-attachments before they get imported into JIRA. An efficient to identify many spam-attachments in the JIRA import is to look for attachments by Unknown, which works because many of the abusers of the old system got banned and their userid got deleted. An even better best way would be to directly scan for spam. +1 I think the spam trash should be tried to deleted before importing into a real system. Otherwise someone has to go over the issues (maybe one-by-one, I don't know) and delete it manually which doesn't sound very attractive. Marcus
Re: OOo Bugzilla data import available for review
Hi, Marcus, On 8/26/2011 04:30, Marcus (OOo) wrote: Am 08/26/2011 08:04 AM, schrieb Herbert Duerr: On 08/26/2011 12:54 AM, Mark Thomas wrote: The OOo Bugzilla data export provided to the ASF infrastructure team has been imported into a test instance[1] for your review. Excellent, thanks! Yes, thanks a lot for creating the test inatance. :-) Please review the import and report any *show stopper* issues to the infrastructure team via the Jira ticket created for this import. [2] I'm not sure whether this is a showstopper issue for the new import as it obviously wasn't too important for the maintainers of old OOo-IZ, but many issues got spam-attachments https://issues.apache.org/ooo/show_bug.cgi?id=113088 I see that JIRA does a more sensible thing for such kinds of attachments, by replying The attachment is not viewable in your browser due to security restrictions enabled by your Apache ooo Bugzilla administrator. but I think if it was possible to identify it would be even better if it was possible to remove the spam-attachments before they get imported into JIRA. An efficient to identify many spam-attachments in the JIRA import is to look for attachments by Unknown, which works because many of the abusers of the old system got banned and their userid got deleted. An even better best way would be to directly scan for spam. +1 I think the spam trash should be tried to deleted before importing into a real system. Otherwise someone has to go over the issues (maybe one-by-one, I don't know) and delete it manually which doesn't sound very attractive. Marcus If you know any way to delete spam en masse that would work better before (rather than after) an import, please suggest it. According to the Bz manual, Bz can be configured to run CGI scripts. Perhaps finding Unknown attachments and deleting them can be automated. Otherwise, it looks like searching for spam itself, and for contributions from identified spammers, could take a while, but I will do it. -- /tj/
Re: OOo Bugzilla data import available for review
Am 08/26/2011 12:06 PM, schrieb TJ Frazier: Hi, Marcus, On 8/26/2011 04:30, Marcus (OOo) wrote: Am 08/26/2011 08:04 AM, schrieb Herbert Duerr: On 08/26/2011 12:54 AM, Mark Thomas wrote: The OOo Bugzilla data export provided to the ASF infrastructure team has been imported into a test instance[1] for your review. Excellent, thanks! Yes, thanks a lot for creating the test inatance. :-) Please review the import and report any *show stopper* issues to the infrastructure team via the Jira ticket created for this import. [2] I'm not sure whether this is a showstopper issue for the new import as it obviously wasn't too important for the maintainers of old OOo-IZ, but many issues got spam-attachments https://issues.apache.org/ooo/show_bug.cgi?id=113088 I see that JIRA does a more sensible thing for such kinds of attachments, by replying The attachment is not viewable in your browser due to security restrictions enabled by your Apache ooo Bugzilla administrator. but I think if it was possible to identify it would be even better if it was possible to remove the spam-attachments before they get imported into JIRA. An efficient to identify many spam-attachments in the JIRA import is to look for attachments by Unknown, which works because many of the abusers of the old system got banned and their userid got deleted. An even better best way would be to directly scan for spam. +1 I think the spam trash should be tried to deleted before importing into a real system. Otherwise someone has to go over the issues (maybe one-by-one, I don't know) and delete it manually which doesn't sound very attractive. Marcus If you know any way to delete spam en masse that would work better before (rather than after) an import, please suggest it. No, sorry. According to the Bz manual, Bz can be configured to run CGI scripts. Perhaps finding Unknown attachments and deleting them can be automated. Otherwise, it looks like searching for spam itself, and for contributions from identified spammers, could take a while, but I will do it. Marcus
Re: OOo Bugzilla data import available for review
Thanks for doing this for us. Mark Thomas wrote: 3. All usernames and passwords remain unchanged with one exception: users with system administration rights have been removed from the admin group. Access to this group will be limited to members of the ASF infrastructure team (new volunteers always welcome). I can not get it to recognize user name or email address. Any suggestions? Andy
Re: OOo Bugzilla data import available for review
Am 26.08.11 01:24, schrieb Andy Brown: Thanks for doing this for us. Mark Thomas wrote: 3. All usernames and passwords remain unchanged with one exception: users with system administration rights have been removed from the admin group. Access to this group will be limited to members of the ASF infrastructure team (new volunteers always welcome). I can not get it to recognize user name or email address. Any suggestions? e-mailer is desabled, so Bugzilla can't send a mail ;-) Andy -- My private Homepage: http://www.raphaelbircher.ch/
Re: OOo Bugzilla data import available for review
On 8/25/2011 19:24, Andy Brown wrote: Thanks for doing this for us. Mark Thomas wrote: 3. All usernames and passwords remain unchanged with one exception: users with system administration rights have been removed from the admin group. Access to this group will be limited to members of the ASF infrastructure team (new volunteers always welcome). I can not get it to recognize user name or email address. Any suggestions? Andy It recognizes my user name @oo.o, but not the password. It has sent me a reset message, but I haven't received it (yet). -- /tj/
Re: OOo Bugzilla data import available for review
TJ Frazier wrote: On 8/25/2011 19:24, Andy Brown wrote: Thanks for doing this for us. Mark Thomas wrote: 3. All usernames and passwords remain unchanged with one exception: users with system administration rights have been removed from the admin group. Access to this group will be limited to members of the ASF infrastructure team (new volunteers always welcome). I can not get it to recognize user name or email address. Any suggestions? Andy It recognizes my user name @oo.o, but not the password. It has sent me a reset message, but I haven't received it (yet). Retried, same results. Also did a quick test to make sure the forwarding was still working, it is. Andy
Re: OOo Bugzilla data import available for review
On 8/25/2011 18:54, Mark Thomas wrote: snip 3. All usernames and passwords remain unchanged with one exception: users with system administration rights have been removed from the admin group. Access to this group will be limited to members of the ASF infrastructure team (new volunteers always welcome). Enjoy. Mark [1] https://issues.apache.org/ooo/ [2] https://issues.apache.org/jira/browse/INFRA-3884 RBircher has reported on the JIRA ticket that logins do not work at all (confirming Andy's and my experience). Thanks to his helpful mention on this thread, we know that BZ email is disabled. This may be related to the problem, since BZ-test is recognizing user names with the full @oo.o suffix, but not passwords (or at least, login fails with bad-password message). -- /tj/
Re: OOo Bugzilla data import available for review
Thanks Mark and everybody else involved! I do prefer this approach than the stepped transition that was planned previously. Here we know what we got and people don't have to spend time finishing the migration in the background. It does look sane: attachments are still there, which is the main thing I am interested in. Just for curiosity, I checked an issue referred from the LO first week development summary, Bug 100686: the patch is there in our bugzilla, so we can pick up relatively easily in some of those changes without diverging too much :). cheers, Pedro. --- On Thu, 8/25/11, Mark Thomas ma...@apache.org wrote: ... All, The OOo Bugzilla data export provided to the ASF infrastructure team has been imported into a test instance[1] for your review. Please review the import and report any *show stopper* issues to the infrastructure team via the Jira ticket created for this import. [2] Assuming no show stopper issues, the data will be re-imported no sooner that Monday 29 August 2011. Please note the following: 1. None of the OOo UI customisations were provided with the export so the UI is the same as the main ASF bugzilla instance apart from the name which has been changed to Apache ooo Bugzilla 2. The previous OOo Bugzilla instance was running on Bugzilla 3.2.10. This reached end-of-live over 6 months ago. It is not acceptable to run production services on unsupported software. As part of the migration, the bugzilla instance was upgraded to 4.0.0. 3. All usernames and passwords remain unchanged with one exception: users with system administration rights have been removed from the admin group. Access to this group will be limited to members of the ASF infrastructure team (new volunteers always welcome). Enjoy. Mark [1] https://issues.apache.org/ooo/ [2] https://issues.apache.org/jira/browse/INFRA-3884
