qooxdoo issues moving to github

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

qooxdoo issues moving to github

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
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 [hidden email] +41 62 775 9902


------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: qooxdoo issues moving to github

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?

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


On Mon, Mar 21, 2016 at 11:41 AM Tobias Oetiker <[hidden email]> wrote:
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 [hidden email] +41 62 775 9902


------------------------------------------------------------------------------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: qooxdoo issues moving to github

oetiker
Today Derrell Lipman wrote:

> 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

> 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

> Derrell
>
>
> On Mon, Mar 21, 2016 at 11:41 AM Tobias Oetiker <[hidden email]> wrote:
>
> > 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 [hidden email] +41 62 775 9902
> >
> >
> >
> > ------------------------------------------------------------------------------
> > 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
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> >
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch [hidden email] +41 62 775 9902


------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: qooxdoo issues moving to github

Derrell Lipman
Sounds reasonable. Thanks for the further explanation.

Derrell


On Mon, Mar 21, 2016 at 12:13 PM Tobias Oetiker <[hidden email]> wrote:
Today Derrell Lipman wrote:

> 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

> 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

> Derrell
>
>
> On Mon, Mar 21, 2016 at 11:41 AM Tobias Oetiker <[hidden email]> wrote:
>
> > 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 [hidden email] +41 62 775 9902
> >
> >
> >
> > ------------------------------------------------------------------------------
> > 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
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> >
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch [hidden email] +41 62 775 9902


------------------------------------------------------------------------------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: qooxdoo issues moving to github

John Spackman
In reply to this post by oetiker
+1 Good idea :)

John




On 21/03/2016, 15:54, "qooxdoo Development <[hidden email]> on behalf of Tobias Oetiker" <[hidden email] on behalf of [hidden email]> wrote:

>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 [hidden email] +41 62 775 9902
>
>
>------------------------------------------------------------------------------
>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
>[hidden email]
>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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: qooxdoo issues moving to github

Phyo Arkar
This is one of the best thing happened to qooxdoo. Lets make Qooxdoo kick Angular ass!

On Tue, Mar 22, 2016 at 4:24 PM John Spackman <[hidden email]> wrote:
+1 Good idea :)

John




On 21/03/2016, 15:54, "qooxdoo Development <[hidden email]> on behalf of Tobias Oetiker" <[hidden email] on behalf of [hidden email]> wrote:

>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 [hidden email] +41 62 775 9902
>
>
>------------------------------------------------------------------------------
>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
>[hidden email]
>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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: qooxdoo issues moving to github

Peter Schneider
In reply to this post by oetiker
Hi there,

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

/Peter

Am 3/21/2016 um 4:41 PM schrieb 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
> 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
>

--

** Unsere Veranstaltungen bis 05-2016 - Termine vormerken!

T-Matik, Greven 10.05.2016
InnoMATIK 2016, 4. Innovationsforum Telematik 18.-19.05.2016
 >> 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?
>> Newsletteranmeldung:
http://tis-gmbh.de/logistikwissen/telematik-news/telematik-newsletter/ 


------------------------------------------------------------------------------
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=278785471&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: qooxdoo issues moving to github

oetiker
Hi Peter,

Today Peter Schneider wrote:

> 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


>
> /Peter
>
> Am 3/21/2016 um 4:41 PM schrieb 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
> > 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 [hidden email] +41 62 775 9902


------------------------------------------------------------------------------
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=278785471&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Loading...