Discussion:
qooxdoo issues moving to github
(too old to reply)
Tobias Oetiker
2016-03-21 15:41:15 UTC
Permalink
Qooxdooers!

We are in the process of migrating qooxdoo resources to public
infrastructure ... My current focus is the issue tracker.

The initial idea was to move all existing issues from
bugzilla.qooxdoo.org to the qooxdoo repo on github. But it turnes
out that the github issues api is not well suited to seamlessly
migrate issues:

* Issue numbers get assigned automatically and can not be
imported

* People who are 'watching' the repo get notified for every issue
imported.

* As soon as there are watchers, github applies severe
ratelimiting to prevent notification storms.

With all that in mind, I am going to implement the following:

a) migrate (AND CLOSE) existing issues from bugzilla to
github.com/qooxdoo/qooxdoo-bugzilla (within the week)

b) enable the issues tab in
github.com/qooxdoo/qooxdoo (already done)

You can see what migrated issues will look like on

https://github.com/oetiker/issuetest2/issues?q=is%3Aissue

cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch ***@oetiker.ch +41 62 775 9902
Derrell Lipman
2016-03-21 15:53:20 UTC
Permalink
Essentially, this is making a backup of the bugzilla issues in the
qooxdoo-bugzilla repository's issue tracker, but moving forward to keeping
new issues in the qooxdoo repository's issue tracker. Am I interpreting
that correctly?

If so, I propose that the list of issues in qooxdoo-bugzilla be reviewed,
and, "relevant" issues moved into the qooxdoo issue tracker, so there's
only one place to look for the current issue list. (The meaning of
"relevant" should probably be discussed, however.)

Derrell
Post by Tobias Oetiker
Qooxdooers!
We are in the process of migrating qooxdoo resources to public
infrastructure ... My current focus is the issue tracker.
The initial idea was to move all existing issues from
bugzilla.qooxdoo.org to the qooxdoo repo on github. But it turnes
out that the github issues api is not well suited to seamlessly
* Issue numbers get assigned automatically and can not be
imported
* People who are 'watching' the repo get notified for every issue
imported.
* As soon as there are watchers, github applies severe
ratelimiting to prevent notification storms.
a) migrate (AND CLOSE) existing issues from bugzilla to
github.com/qooxdoo/qooxdoo-bugzilla (within the week)
b) enable the issues tab in
github.com/qooxdoo/qooxdoo (already done)
You can see what migrated issues will look like on
https://github.com/oetiker/issuetest2/issues?q=is%3Aissue
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Tobias Oetiker
2016-03-21 16:13:04 UTC
Permalink
Post by Derrell Lipman
Essentially, this is making a backup of the bugzilla issues in the
qooxdoo-bugzilla repository's issue tracker, but moving forward to keeping
new issues in the qooxdoo repository's issue tracker. Am I interpreting
that correctly?
yes
Post by Derrell Lipman
If so, I propose that the list of issues in qooxdoo-bugzilla be reviewed,
and, "relevant" issues moved into the qooxdoo issue tracker, so there's
only one place to look for the current issue list. (The meaning of
"relevant" should probably be discussed, however.)
this can certainly be done, but someone has todo it ...
AND everyone watching qooxdoo/qooxdoo will get notified for every
issue and every comment migrated.

my idea is that by having qooxdoo/qooxdoo-bugzilla, the people who
are interested in fixing qooxdoo bugs can simply watch that repo
too, and if someone re-opens an old bug there, they will get
notified ...

then the bug can be moved to the new repo and will thus get the
benefit of all the goodness of by being in the same repo as the
qooxdoo code.

cheers
tobi
Post by Derrell Lipman
Derrell
Post by Tobias Oetiker
Qooxdooers!
We are in the process of migrating qooxdoo resources to public
infrastructure ... My current focus is the issue tracker.
The initial idea was to move all existing issues from
bugzilla.qooxdoo.org to the qooxdoo repo on github. But it turnes
out that the github issues api is not well suited to seamlessly
* Issue numbers get assigned automatically and can not be
imported
* People who are 'watching' the repo get notified for every issue
imported.
* As soon as there are watchers, github applies severe
ratelimiting to prevent notification storms.
a) migrate (AND CLOSE) existing issues from bugzilla to
github.com/qooxdoo/qooxdoo-bugzilla (within the week)
b) enable the issues tab in
github.com/qooxdoo/qooxdoo (already done)
You can see what migrated issues will look like on
https://github.com/oetiker/issuetest2/issues?q=is%3Aissue
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch ***@oetiker.ch +41 62 775 9902
Derrell Lipman
2016-03-21 16:18:08 UTC
Permalink
Sounds reasonable. Thanks for the further explanation.

Derrell
Post by Derrell Lipman
Post by Derrell Lipman
Essentially, this is making a backup of the bugzilla issues in the
qooxdoo-bugzilla repository's issue tracker, but moving forward to
keeping
Post by Derrell Lipman
new issues in the qooxdoo repository's issue tracker. Am I interpreting
that correctly?
yes
Post by Derrell Lipman
If so, I propose that the list of issues in qooxdoo-bugzilla be reviewed,
and, "relevant" issues moved into the qooxdoo issue tracker, so there's
only one place to look for the current issue list. (The meaning of
"relevant" should probably be discussed, however.)
this can certainly be done, but someone has todo it ...
AND everyone watching qooxdoo/qooxdoo will get notified for every
issue and every comment migrated.
my idea is that by having qooxdoo/qooxdoo-bugzilla, the people who
are interested in fixing qooxdoo bugs can simply watch that repo
too, and if someone re-opens an old bug there, they will get
notified ...
then the bug can be moved to the new repo and will thus get the
benefit of all the goodness of by being in the same repo as the
qooxdoo code.
cheers
tobi
Post by Derrell Lipman
Derrell
Post by Tobias Oetiker
Qooxdooers!
We are in the process of migrating qooxdoo resources to public
infrastructure ... My current focus is the issue tracker.
The initial idea was to move all existing issues from
bugzilla.qooxdoo.org to the qooxdoo repo on github. But it turnes
out that the github issues api is not well suited to seamlessly
* Issue numbers get assigned automatically and can not be
imported
* People who are 'watching' the repo get notified for every issue
imported.
* As soon as there are watchers, github applies severe
ratelimiting to prevent notification storms.
a) migrate (AND CLOSE) existing issues from bugzilla to
github.com/qooxdoo/qooxdoo-bugzilla (within the week)
b) enable the issues tab in
github.com/qooxdoo/qooxdoo (already done)
You can see what migrated issues will look like on
https://github.com/oetiker/issuetest2/issues?q=is%3Aissue
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
------------------------------------------------------------------------------
Post by Derrell Lipman
Post by Tobias Oetiker
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
John Spackman
2016-03-22 08:22:30 UTC
Permalink
+1 Good idea :)

John
Post by Tobias Oetiker
Qooxdooers!
We are in the process of migrating qooxdoo resources to public
infrastructure ... My current focus is the issue tracker.
The initial idea was to move all existing issues from
bugzilla.qooxdoo.org to the qooxdoo repo on github. But it turnes
out that the github issues api is not well suited to seamlessly
* Issue numbers get assigned automatically and can not be
imported
* People who are 'watching' the repo get notified for every issue
imported.
* As soon as there are watchers, github applies severe
ratelimiting to prevent notification storms.
a) migrate (AND CLOSE) existing issues from bugzilla to
github.com/qooxdoo/qooxdoo-bugzilla (within the week)
b) enable the issues tab in
github.com/qooxdoo/qooxdoo (already done)
You can see what migrated issues will look like on
https://github.com/oetiker/issuetest2/issues?q=is%3Aissue
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Phyo Arkar
2016-03-26 03:53:34 UTC
Permalink
This is one of the best thing happened to qooxdoo. Lets make Qooxdoo kick
Angular ass!
Post by John Spackman
+1 Good idea :)
John
On 21/03/2016, 15:54, "qooxdoo Development <
Post by Tobias Oetiker
Qooxdooers!
We are in the process of migrating qooxdoo resources to public
infrastructure ... My current focus is the issue tracker.
The initial idea was to move all existing issues from
bugzilla.qooxdoo.org to the qooxdoo repo on github. But it turnes
out that the github issues api is not well suited to seamlessly
* Issue numbers get assigned automatically and can not be
imported
* People who are 'watching' the repo get notified for every issue
imported.
* As soon as there are watchers, github applies severe
ratelimiting to prevent notification storms.
a) migrate (AND CLOSE) existing issues from bugzilla to
github.com/qooxdoo/qooxdoo-bugzilla (within the week)
b) enable the issues tab in
github.com/qooxdoo/qooxdoo (already done)
You can see what migrated issues will look like on
https://github.com/oetiker/issuetest2/issues?q=is%3Aissue
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Peter Schneider
2016-03-29 08:30:56 UTC
Permalink
Hi there,

are there any plans on migrating the _bugzilla_accounts_ as well?
Or do I have to create (yet another) account?

/Peter
Post by Tobias Oetiker
Qooxdooers!
We are in the process of migrating qooxdoo resources to public
infrastructure ... My current focus is the issue tracker.
The initial idea was to move all existing issues from
bugzilla.qooxdoo.org to the qooxdoo repo on github. But it turnes
out that the github issues api is not well suited to seamlessly
* Issue numbers get assigned automatically and can not be
imported
* People who are 'watching' the repo get notified for every issue
imported.
* As soon as there are watchers, github applies severe
ratelimiting to prevent notification storms.
a) migrate (AND CLOSE) existing issues from bugzilla to
github.com/qooxdoo/qooxdoo-bugzilla (within the week)
b) enable the issues tab in
github.com/qooxdoo/qooxdoo (already done)
You can see what migrated issues will look like on
https://github.com/oetiker/issuetest2/issues?q=is%3Aissue
cheers
tobi
--
** Unsere Veranstaltungen bis 05-2016 - Termine vormerken!

T-Matik, Greven 10.05.2016
InnoMATIK 2016, 4. Innovationsforum Telematik 18.-19.05.2016
Post by Tobias Oetiker
Um Anmeldung wird gebeten: http://tis-innomatik.de/
** unsere NEUE Homepage ist online - schauen Sie mal rein:
http://tis-gmbh.de

** Kennen Sie schon unseren Blog?
telematics-magazine.com

** Interesse an unseren Unternehmensneuigkeiten?
http://tis-gmbh.de/logistikwissen/telematik-news/telematik-newsletter/
Tobias Oetiker
2016-03-29 09:17:45 UTC
Permalink
Hi Peter,
Post by Peter Schneider
Hi there,
are there any plans on migrating the _bugzilla_accounts_ as well?
Or do I have to create (yet another) account?
since everything is going to github, you can just use your github
account. note though the migrated issues will all be owned by a
custom issue migrator user I am going to create ...

so the idea really is to have the old issues just for lookup and
then create new ones if they are still valid

cheers
tobi
Post by Peter Schneider
/Peter
Post by Tobias Oetiker
Qooxdooers!
We are in the process of migrating qooxdoo resources to public
infrastructure ... My current focus is the issue tracker.
The initial idea was to move all existing issues from
bugzilla.qooxdoo.org to the qooxdoo repo on github. But it turnes
out that the github issues api is not well suited to seamlessly
* Issue numbers get assigned automatically and can not be
imported
* People who are 'watching' the repo get notified for every issue
imported.
* As soon as there are watchers, github applies severe
ratelimiting to prevent notification storms.
a) migrate (AND CLOSE) existing issues from bugzilla to
github.com/qooxdoo/qooxdoo-bugzilla (within the week)
b) enable the issues tab in
github.com/qooxdoo/qooxdoo (already done)
You can see what migrated issues will look like on
https://github.com/oetiker/issuetest2/issues?q=is%3Aissue
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch ***@oetiker.ch +41 62 775 9902
Loading...