[Libreoffice-qa] Bugzilla Migration Plan

classic Classic list List threaded Threaded
17 messages Options
Robinson Tryon Robinson Tryon
Reply | Threaded
Open this post in threaded view
|

[Libreoffice-qa] Bugzilla Migration Plan

Hi All,

We've been talking recently about migrating our bugtracker to our own
server. There are a number of benefits to such a migration, but we've
often glossed-over some of the details of how to effect such a move.

Florian R. and I stuck our heads together and came up with some good
ideas on how to make this happen. Here's our current draft:

1) Ping our users:

- Ask our FDO users for permission to include their accounts/data in
the new install (this could be as simple as a mass-email asking for
them to reply back to us, or a small Bugzilla plugin where users can
check a box "Please copy my account to LibreBugzilla...")


2) Prep

- Clone the LibreOffice project into a separate bugzilla instance
(still run by FDO)

- Use bugs.libreoffice.org as the url for this new instance of bugzilla

- Add a default license/ToS for all users/new bugs (I suggest CC-BY-SA
3.0 for consistency)

- Document and prepare to transition all LibreOffice infrastructure
that interfaces with FDO (e.g. Gerrit, Ask, MediaWiki, IZBot, etc..)

- Design a redirect system so that LO bug urls on FDO redirect to the
new bugs.libreoffice.org (either with mod_redirect, a custom patch to
Bugzilla, or etc..)

- Change all non-migrated account emails to
"fdo-user_<username-at-fdo>+[hidden email].


3) Migration Day

- Lock-down the LibreOffice project in FDO so that no new changes can
be made to LO bugs

- Copy-over the bugzilla database to the new instance, and make it live


4) Continue to migrate accounts

- For the next few months, respond to user-inquiries about migrating
their user accounts from FDO to the new Bugzilla instance. If we left
passwords, etc.. in place, this could be as simple as telling the user
to log-in with the new username/email address, and have them change
the username back to its original value.


5) Complete the transfer

- After a few months, the FDO admins can delete user
credentials/log-in information for any accounts that have not opted-in
to the new system

- The server instance may be handed over to the TDF sysadmins at any time



Thoughts?

Thanks,
-- R
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Jochen Schiffers Jochen Schiffers
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

Hi Robinson,

my thoughts are

1) wow - great idea and good plan/implementation

Then
2) What benefits?
3) Never change a running system

Regards

Jochen


Am 12.08.2013 19:54, schrieb Robinson Tryon:

> Hi All,
>
> We've been talking recently about migrating our bugtracker to our own
> server. There are a number of benefits to such a migration, but we've
> often glossed-over some of the details of how to effect such a move.
>
> Florian R. and I stuck our heads together and came up with some good
> ideas on how to make this happen. Here's our current draft:
>
> 1) Ping our users:
>
> - Ask our FDO users for permission to include their accounts/data in
> the new install (this could be as simple as a mass-email asking for
> them to reply back to us, or a small Bugzilla plugin where users can
> check a box "Please copy my account to LibreBugzilla...")
>
>
> 2) Prep
>
> - Clone the LibreOffice project into a separate bugzilla instance
> (still run by FDO)
>
> - Use bugs.libreoffice.org as the url for this new instance of bugzilla
>
> - Add a default license/ToS for all users/new bugs (I suggest CC-BY-SA
> 3.0 for consistency)
>
> - Document and prepare to transition all LibreOffice infrastructure
> that interfaces with FDO (e.g. Gerrit, Ask, MediaWiki, IZBot, etc..)
>
> - Design a redirect system so that LO bug urls on FDO redirect to the
> new bugs.libreoffice.org (either with mod_redirect, a custom patch to
> Bugzilla, or etc..)
>
> - Change all non-migrated account emails to
> "fdo-user_<username-at-fdo>+[hidden email].
>
>
> 3) Migration Day
>
> - Lock-down the LibreOffice project in FDO so that no new changes can
> be made to LO bugs
>
> - Copy-over the bugzilla database to the new instance, and make it live
>
>
> 4) Continue to migrate accounts
>
> - For the next few months, respond to user-inquiries about migrating
> their user accounts from FDO to the new Bugzilla instance. If we left
> passwords, etc.. in place, this could be as simple as telling the user
> to log-in with the new username/email address, and have them change
> the username back to its original value.
>
>
> 5) Complete the transfer
>
> - After a few months, the FDO admins can delete user
> credentials/log-in information for any accounts that have not opted-in
> to the new system
>
> - The server instance may be handed over to the TDF sysadmins at any time
>
>
>
> Thoughts?
>
> Thanks,
> -- R
> _______________________________________________
> List Name: Libreoffice-qa mailing list
> Mail address: [hidden email]
> Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
> Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
> List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
>
>
>
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
bfoman bfoman
Reply | Threaded
Open this post in threaded view
|

Re: [Libreoffice-qa] Bugzilla Migration Plan

In reply to this post by Robinson Tryon
Robinson Tryon wrote
1) Ping our users:
- Ask our FDO users for permission to include their accounts/data in
the new install (this could be as simple as a mass-email asking for
them to reply back to us, or a small Bugzilla plugin where users can
check a box "Please copy my account to LibreBugzilla...")
Hi!
I think this should be all or nothing operation - LibreOffice bugs moved to new instance along with every account that touched the bug. Personally I would like to have my account auto-moved, just like big mail systems do it. Explanation before, during and after, good FAQ about the rationale and change password link in welcome message would be welcomed. Not mentioning all personal searches, settings, tags intact.
Robinson Tryon wrote
3) Migration Day
- Lock-down the LibreOffice project in FDO so that no new changes can
be made to LO bugs
- Copy-over the bugzilla database to the new instance, and make it live
Do not forget about data directory - see https://wiki.mozilla.org/Bugzilla:Move_Installation.
Best regards.

Robinson Tryon Robinson Tryon
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by Jochen Schiffers
On Mon, Aug 12, 2013 at 2:39 PM, Jochen <[hidden email]> wrote:
> Hi Robinson,
>
> my thoughts are
>
> 1) wow - great idea and good plan/implementation
>

Thanks! We hope that people like it :-)

> Then
> 2) What benefits?

There are a number of reasons for us to migrate to our own bugtracker.
Off the top of my head:

- Be able to update field labels
- Have the bug tracker under a libreoffice.org url
- Easily have more than one product listed (e.g. Website bugs, Android
Impress Remote bugs, Marketing bugs, etc..)
- Change email defaults
- Have our bugzilla code stored in git
- Activate voting
- Bulk-update bugs without spamming the devs each time

(I'm sure that Florian or Joel can chime in here with more... :-)

> 3) Never change a running system
>

I'd prefer not to change the system, but IMHO we're currently butting
our heads against a slew of issues that are attributable to our
inability to customize and hack on our bugtracker. I think that
limitations in the bugtracker are starting to negatively affect other
aspects of the project. Don't get me wrong -- I don't think that us
having our own bugtracker is going to magically fix all of our
problems, but I think it's an important step in the advancement of our
project.

I'm hoping that we'll be able to effect the migration with very
minimal changes to the underlying code and data. Tiny atomic changes
are the best strategy to make the transition as painless as possible.
I'm really looking forward to working with the FDO admins to find ways
for us to simplify, simplify, and simplify even more the transition.
If we do it right, I think we can be done quickly and off to the pub
for a celebratory pint :-)

speaking of...Cheers,
--R
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Robinson Tryon Robinson Tryon
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by bfoman
On Mon, Aug 12, 2013 at 3:58 PM, bfoman <[hidden email]> wrote:

> Robinson Tryon wrote
>> 1) Ping our users:
>> - Ask our FDO users for permission to include their accounts/data in
>> the new install (this could be as simple as a mass-email asking for
>> them to reply back to us, or a small Bugzilla plugin where users can
>> check a box "Please copy my account to LibreBugzilla...")
>
> Hi!
> I think this should be all or nothing operation - LibreOffice bugs moved to
> new instance along with every account that touched the bug.

Thats our general plan right now. One of the particulars that would
need to be ironed-out is to figure out how to deal with old/abandoned
user accounts. We'd like to migrate the data but leave the account
innactive/disabled if the user has no intention of returning.

> Personally I
> would like to have my account auto-moved, just like big mail systems do it.
> Explanation before, during and after, good FAQ about the rationale and
> change password link in welcome message would be welcomed. Not mentioning
> all personal searches, settings, tags intact.

That's one possible approach to the move, and something that we'll
definitely discuss with the leaders at FDO and TDF. As mentioned
previously, one approach would include a super-quick way for existing
users to indicate their support of the migration via an email reply or
a checkbox in their Bugzilla user account; either way, the process
will be pretty painless.

> Robinson Tryon wrote
>> 3) Migration Day
>> - Lock-down the LibreOffice project in FDO so that no new changes can
>> be made to LO bugs
>> - Copy-over the bugzilla database to the new instance, and make it live
>
> Do not forget about data directory - see
> https://wiki.mozilla.org/Bugzilla:Move_Installation.

Excellent -- that'll be a helpful resource when we copy over the data.

--R
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Florian Reisinger Florian Reisinger
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by Robinson Tryon
Hi Jochen, Rob,

Am 12.08.2013 um 23:33 schrieb Robinson Tryon <[hidden email]>:

> On Mon, Aug 12, 2013 at 2:39 PM, Jochen <[hidden email]> wrote:
>> Hi Robinson,
>>
>> my thoughts are
>>
>> 1) wow - great idea and good plan/implementation
>
> Thanks! We hope that people like it :-)
>
>> Then
>> 2) What benefits?
>
> There are a number of reasons for us to migrate to our own bugtracker.
> Off the top of my head:

I will add something to the list, some quite personal.

>
> - Be able to update field labels
> - Have the bug tracker under a libreoffice.org url
> - Easily have more than one product listed (e.g. Website bugs, Android
> Impress Remote bugs, Marketing bugs, etc..)
> - Change email defaults
-No default assingie (If no one is assigned, then no one is assigned - so easy to understand)
-Implementation of "take" for QA contact, which should not be too difficult...
-No whiteboard status for QA any more (only keywords, which do not need to be tested.
- More then one version field (we might discuss that) One for earliest tested version, where the bug exists and one for the latest tested version. IMHO we could do some nice (and thus helpful queries)
- (sample scenario) I am going to file a bug against the impress Remote (Android). Which OS should I take? I will take Linux, because it is the closed to Android....
-We can install addons and themes (okay, last is minor, but we could have a green bugzilla)
We could have OpenID or other methods


> - Have our bugzilla code stored in git

-Bugzilla updates via cvs...

> - Activate voting
> - Bulk-update bugs without spamming the devs each time
>
> [...]
>
> speaking of...Cheers,
> --R

Liebe Grüße, / Yours,
Florian Reisinger

> _______________________________________________
> List Name: Libreoffice-qa mailing list
> Mail address: [hidden email]
> Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
> Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
> List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Florian Reisinger Florian Reisinger
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by bfoman
Hi bfoman,

Liebe Grüße, / Yours,
Florian Reisinger

Am 12.08.2013 um 21:58 schrieb bfoman <[hidden email]>:

Robinson Tryon wrote
[...]
Hi!
I think this should be all or nothing operation - LibreOffice bugs moved to
new instance along with every account that touched the bug. Personally I
would like to have my account auto-moved, just like big mail systems do it.
Explanation before, during and after, good FAQ about the rationale and
change password link in welcome message would be welcomed. Not mentioning
all personal searches, settings, tags intact.

You meant "Directly to a new instance"? I fear we are not allowed to do this, because of privacy issues...

[...]
Best regards.


_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Petr Mladek Petr Mladek
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

Florian Reisinger píše v Út 13. 08. 2013 v 07:57 +0200:

> Hi bfoman,
>
> Liebe Grüße, / Yours,
> Florian Reisinger
>
> Am 12.08.2013 um 21:58 schrieb bfoman <[hidden email]>:
>
>
> > Robinson Tryon wrote
> > [...]
> > Hi!
> > I think this should be all or nothing operation - LibreOffice bugs
> > moved to
> > new instance along with every account that touched the bug.
> > Personally I
> > would like to have my account auto-moved, just like big mail systems
> > do it.
> > Explanation before, during and after, good FAQ about the rationale
> > and
> > change password link in welcome message would be welcomed. Not
> > mentioning
> > all personal searches, settings, tags intact.
> >

> You meant "Directly to a new instance"? I fear we are not allowed to
> do this, because of privacy issues...

I think that we should discuss this with some layers. I hope that the
board of directors or ESC could find one.

It would be great to avoid the "ask for permission" step if possible. It
would be a lot of work. Note that the overloaded FDO bugzilla admins
would need to extract the user infos selectively again and again. Also I
am afraid that we will not get many approvals because people simply
won't mind.


Also I am not sure about the point:

- Add a default license/ToS for all users/new bugs (I suggest CC-BY-SA
3.0 for consistency)

On one hand it would be interesting to get test documents under certain
license. On the other hand, people must not be scared to attach them.
Also we should not overengineer it ;-)


Finally, I support the idea of our own bugzilla. It might solve many of
the mentioned problems. On the other hand, I am still a bit unsure about
the needed work. Do we already have a volunteer who could maintain
it? ;-)


Best Regards,
Petr


_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Pedro Pedro
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by Jochen Schiffers
Hi Jochen, all

I think this is a GREAT idea!

Jochen wrote
2) What benefits?
IMO the main advantage would be to remove another one or two layers of obstacles for the user

1) Instead of having to select the project from a long list where LibreOffice is somewhere in the middle (https://bugs.freedesktop.org/enter_bug.cgi) you would start here https://bugs.freedesktop.org/enter_bug.cgi?product=LibreOffice&bug_status=UNCONFIRMED

2) If OpenID can be implemented (unfortunately I think it's an unsolvable problem with OpenID https://bugzilla.mozilla.org/show_bug.cgi?id=294608) or BrowserID or any other ID thing that removes the need for yet another registration it would be fantastic

Jochen wrote
3) Never change a running system
Agreed. Unless that system does not /no longer suit your needs or is user unfriendly thus defeating it's purpose :)

Just my 2 cents...
bfoman bfoman
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by Florian Reisinger
Florian Reisinger wrote
You meant "Directly to a new instance"? I fear we are not allowed to do this, because of privacy issues...
Hi!
So lets check bugs.freedesktop.org, www.libreoffice.org/bugzilla, www.libreoffice.org/get-help/bug/, or whatever is the other link to the same Bugzilla instance Privacy Policy. Wait, I don't recollect to read anything more than the following:
PRIVACY NOTICE: Bugzilla is an open bug tracking system. Activity on most bugs, including email addresses, will be visible to the public. We recommend using a secondary account or free web email service (such as Gmail, Yahoo, Hotmail, or similar) to avoid receiving spam at your primary email address.
This Bugzilla is already available at www.libreoffice.org/bugzilla so I think it is just technical operation. No lawyers involved as there is no privacy policy whatsoever (well, this could make some concerned, not mentioning EU cookie law hunters).
I cannot imagine a per user "ask for ack" migration of more than 8000 accounts of people ever reported in LibreOffice product. Bugzilla bugs are connected to UserIDs. You pretty much can't delete an account without a risk of getting referential integrity problems in your database . On the other hand having orphaned bugs with artificial UserIDs and then reassigning bugs back to reporters by hand or scripting sounds like horror story. Also having bugs anonymized doesn't have much sense.
Best regards.
BTW: You can read OpenOffice Bugzilla to Apache migration announcement here - http://mail-archives.apache.org/mod_mbox/incubator-ooo-users/201109.mbox/%3CSNT126-DS17794D26E0ACE2103DEE6CDB1A0%40phx.gbl%3E.
bfoman bfoman
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by Florian Reisinger
Hi!
Some comments:

-No default assingie (If no one is assigned, then no one is assigned - so easy to understand)

This is mandatory field in Bugzilla. Anyway, default assignee allows to watch new bugs filed in components - whether by mailinglist or by watching special account (like component@libreoffice.bugs).

-Implementation of "take" for QA contact, which should not be too difficult...

This is already available in Bugzilla 4.4.

-No whiteboard status for QA any more (only keywords, which do not need to be tested.

Yep, can be disabled by usestatuswhiteboard.

- More then one version field (we might discuss that) One for earliest tested version, where the bug exists and one for the latest tested version. IMHO we could do some nice (and thus helpful queries)

Only one version field is possible by default. This could be enabled by other means - flags or custom fields.

> - Have our bugzilla code stored in git
-Bugzilla updates via cvs...

CVS is rather rusty...

Well, there are https://wiki.documentfoundation.org/QA-ImprovingBugzilla and https://wiki.documentfoundation.org/How_to_Improve_Bugzilla articles already. I think they should be updated before migration. Some test installation could be installed to allow pick up the best settings, extensions, customizations. And when all is prepared - do it.
Best regards.
Florian Reisinger Florian Reisinger
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by bfoman
Hi,

Am 13.08.2013 17:52, schrieb bfoman:

> Florian Reisinger wrote
>> You meant "Directly to a new instance"? I fear we are not allowed to do
>> this, because of privacy issues...
> Hi!
> So lets check bugs.freedesktop.org, www.libreoffice.org/bugzilla,
> www.libreoffice.org/get-help/bug/, or whatever is the other link to the same
> Bugzilla instance Privacy Policy. Wait, I don't recollect to read anything
> more than the following:
> /PRIVACY NOTICE: Bugzilla is an open bug tracking system. Activity on most
> bugs, including email addresses, will be visible to the public. We recommend
> using a secondary account or free web email service (such as Gmail, Yahoo,
> Hotmail, or similar) to avoid receiving spam at your primary email address.
> /
> This Bugzilla is already available at www.libreoffice.org/bugzilla so I
> think it is just technical operation. No lawyers involved as there is no
> privacy policy whatsoever (well, this could make some concerned, not
> mentioning EU cookie law hunters).

The fact is: data is @freedesktop. In the and data is @libreoffice. IMHO
the problem is the German law, which forbids us to continue using the
data (I really hope it is a law worldwide....) I really do hope at some
point that I am wrong, that would easify everything, but I do not
believe it....

> I cannot imagine a per user "ask for ack" migration of more than 8000
> accounts of people ever reported in LibreOffice product. Bugzilla bugs are
> connected to UserIDs. You pretty much can't delete an account without a risk
> of getting referential integrity problems in your database . On the other
> hand having orphaned bugs with artificial UserIDs and then reassigning bugs
> back to reporters by hand or scripting sounds like horror story. Also having
> bugs anonymized doesn't have much sense.
> Best regards.
> BTW: You can read OpenOffice Bugzilla to Apache migration announcement here
> -
> http://mail-archives.apache.org/mod_mbox/incubator-ooo-users/201109.mbox/%3CSNT126-DS17794D26E0ACE2103DEE6CDB1A0%40phx.gbl%3E.

Thanks for this link....

>
>
>
>
> --
> View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-Bugzilla-Migration-Plan-tp4069765p4069871.html
> Sent from the QA mailing list archive at Nabble.com.
> _______________________________________________
> List Name: Libreoffice-qa mailing list
> Mail address: [hidden email]
> Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
> Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
> List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


--
Liebe Grüße, / Yours,
Florian Reisinger

_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Robinson Tryon Robinson Tryon
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by Petr Mladek
On Tue, Aug 13, 2013 at 5:05 AM, Petr Mladek <[hidden email]> wrote:
>
> It would be great to avoid the "ask for permission" step if possible. It
> would be a lot of work.

It would be a lot of work; yes, we should ask a lawyer :-)

> Note that the overloaded FDO bugzilla admins
> would need to extract the user infos selectively again and again.

There are a couple of ways to speed up the please-re-enable-my-account
process. That being said, I think if we ask people a month or so
before the transfer, I'm hopeful that we can get 90%+ of the
currently-active bugzilla accounts, so the workload might not be that
huge...

> Also I
> am afraid that we will not get many approvals because people simply
> won't mind.

yep, yep

> Also I am not sure about the point:
>
> - Add a default license/ToS for all users/new bugs (I suggest CC-BY-SA
> 3.0 for consistency)
>

Right now it sounds like we're unsure if we transfer data/comments
from FDO because there's no license on that data, and no ToS (that I
can see) anywhere on the FDO/Bugzilla site. If we had such a
license/ToS on there right now, the whole discussion about 'can we
transfer data?' would be moot.

Even if we didn't have this hurdle in front of us right now, I'd still
think it would be a good idea to clarify our usage terms for the
bugtracker data. Given that we *actually* need to address this problem
before a migration can proceed, I think we'd be foolish not to prevent
this problem from occurring in the future :-)

> On one hand it would be interesting to get test documents under certain
> license. On the other hand, people must not be scared to attach them.
> Also we should not overengineer it ;-)

True, true. A particular CC license might not work for all use cases,
especially with test documents attached to bugs. My primary focus here
would be to ease any future data transitions in the future; we'd
probably want to do some brainstorming and/or ping some other FOSS
projects for advice on this topic.

> Finally, I support the idea of our own bugzilla. It might solve many of
> the mentioned problems. On the other hand, I am still a bit unsure about
> the needed work. Do we already have a volunteer who could maintain
> it? ;-)

I'm going to defer to Joel regarding the workload for day-to-day
administration of projects in Bugzilla, but I think that the QA Team
usually has that aspect of the bug tracker under control.

Regarding the backend sysadmin aspects, I don't think that there'd be
much required beyond security upgrades.


Cheers,
--R
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Robinson Tryon Robinson Tryon
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by bfoman
On Tue, Aug 13, 2013 at 12:17 PM, bfoman <[hidden email]> wrote:
>
> -Implementation of "take" for QA contact, which should not be too
> difficult...
>
> This is already available in Bugzilla 4.4.

FDO runs 4.2.3, but we can run whatever version of Bugzilla we like :-)

> - More then one version field (we might discuss that) One for earliest
> tested version, where the bug exists and one for the latest tested version.
> IMHO we could do some nice (and thus helpful queries)
>
> Only one version field is possible by default. This could be enabled by
> other means - flags or custom fields.

yes, we'd probably put in a custom field.

(Of course, all of these changes would come after the migration is
complete and running well,  and after we've checked all of the code
into version control so that we stay sane :-)

>
>> - Have our bugzilla code stored in git
> -Bugzilla updates via cvs...
>
> CVS is rather rusty...

I think that primary Bugzilla sources live in Bazaar, with CVS access
available for legacy purposes. Because we already have a bunch of our
infrastructure stuff in git (e.g. the BSA), and most people are
familiar with that VCS, my proposed plan is that we store our patched
of Bugzilla in git. To upgrade to a newer version of Bugzilla, we can
just extract a tarball, toss it in an 'upstream' branch, and work from
there.

> Well, there are https://wiki.documentfoundation.org/QA-ImprovingBugzilla and
> https://wiki.documentfoundation.org/How_to_Improve_Bugzilla articles
> already. I think they should be updated before migration. Some test
> installation could be installed to allow pick up the best settings,
> extensions, customizations. And when all is prepared - do it.

Test install of Bugzilla 4.2.3 (to match what's running on FDO) is here:
http://testing.eagleeyet.net/bugs/

This includes a couple of patches we were testing out:
- Tweaked version field label
- A very special enhancement request from Joel :-)


Cheers,
--R
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
bfoman bfoman
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

Robinson Tryon wrote
I think that primary Bugzilla sources live in Bazaar [...] of Bugzilla in git.
Hi!
Bazaar development is discontinued, so probably Bugzilla will be available at github quite soon.
Robinson Tryon wrote
Test install of Bugzilla 4.2.3 (to match what's running on FDO) is here:
http://testing.eagleeyet.net/bugs/
Great, so now you can test a bunch of useful extensions enabled on bugzilla.mozilla.org:
http://bzr.mozilla.org/bmo/4.0/files/head:/extensions/
I really like My product dashboard or /page.cgi?id=triage_reports.html search page (http://bzr.mozilla.org/bmo/4.0/annotate/head:/extensions/BMO/template/en/default/pages/triage_reports.html.tmpl).

About the legalese - full Mozilla's Bugzilla (sanitized by this script http://bzr.mozilla.org/bmo/4.0/annotate/head:/contrib/sanitizeme.pl) is available to download from http://people.mozilla.com/~mhoye/bugzilla/. Before that it was available per request, such as in bug https://bugzilla.mozilla.org/show_bug.cgi?id=801255.
Best regards.
bfoman bfoman
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

bfoman wrote
Great, so now you can test a bunch of useful extensions enabled on bugzilla.mozilla.org:
http://bzr.mozilla.org/bmo/4.0/files/head:/extensions/
I really like My product dashboard or /page.cgi?id=triage_reports.html search page
I am sorry - correct links:
http://bzr.mozilla.org/bmo/4.2/files
http://bzr.mozilla.org/bmo/4.2/annotate/head:/extensions/BMO/template/en/default/pages/triage_reports.html.tmpl
Rob Snelders-3 Rob Snelders-3
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Migration Plan

In reply to this post by Robinson Tryon
Hi,

On 12-08-13 19:54, Robinson Tryon wrote:
> Hi All,
>
> We've been talking recently about migrating our bugtracker to our own
> server. There are a number of benefits to such a migration, but we've
> often glossed-over some of the details of how to effect such a move.

Great. I think it really helps to have our own Bugzilla.

--
Greetings,
Rob Snelders
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: [hidden email]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/