Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move deprecated and obsolete repositories from github.com/qooxdoo to github.com/qooxdoo-archive #9787

Open
cboulanger opened this issue Sep 10, 2019 · 11 comments

Comments

@cboulanger
Copy link
Contributor

commented Sep 10, 2019

If no objections are voiced, we will rename github.com/qooxdoo-contrib to github.com/qooxdoo-archive and transfer those of the following repositories which are no longer used:

  • rename qooxdoo-contrib to qooxdoo-archive
  • Inspector
  • Mobile-Frameworks-Comparison-Chart
  • Points (deleted, fork)
  • admin (deleted, empty skeleton)
  • cdnjs (deleted, fork)
  • generator-stats (deleted, just a logfile)
  • grunt-qx
  • maven-central-integration
  • qooxdoo-bz-archive
  • qooxdoo-preset-env
  • qooxdoo-wiki
  • qx-phantom
  • resources
  • sizzle (deleted, fork)
  • taskspeed (deleted, fork)
  • qx-webdriver
  • qxwebdriver-java
  • www

Please let me know if any repo in the list has to be kept within the qooxdoo organization namespace.

@derrell

This comment has been minimized.

Copy link
Member

commented Sep 10, 2019

qooxdoo-wiki is current and should not be archived. It contains our developer documentation, among other things.

@hkollmann

This comment has been minimized.

Copy link
Member

commented Sep 10, 2019

@derrell

This comment has been minimized.

Copy link
Member

commented Sep 10, 2019

It appears you're correct. That one has more recent changes than qooxdoo-wiki, which must have been the predecessor. Yes, it looks like qooxdoo-wiki can in fact be archived.

@cboulanger

This comment has been minimized.

Copy link
Contributor Author

commented Sep 10, 2019

I will also disable

since they are not used anymore.

@johnspackman

This comment has been minimized.

Copy link
Member

commented Sep 10, 2019

looks good to me; deleting www should be paired with removing tool/admin/www (submodule) from the core

@hkollmann

This comment has been minimized.

Copy link
Member

commented Sep 10, 2019

IMHO www is used in the build chain of qooxdoo

@cboulanger

This comment has been minimized.

Copy link
Contributor Author

commented Sep 10, 2019

What about the "Inspector"? Doesn't it still work with the old toolchain based on the generator?

@hkollmann

This comment has been minimized.

Copy link
Member

commented Sep 10, 2019

Just checked it. WWW can be moved - the resources are static on the website

@hkollmann

This comment has been minimized.

Copy link
Member

commented Sep 10, 2019

inspector: Is it worth to moddernize it? Has anyone worked with it?

@johnspackman

This comment has been minimized.

Copy link
Member

commented Sep 10, 2019

re inspector: AFAICR it looked interesting but was too intrusive to work. Its a long time ago, but I remember thinking that It could be useful if it could be outside looking in - eg if your qooxdoo app was inside an iframe, and the inspector was outside but using some kind of remote communication to look inside and inspect the objects. This would require a small server class inside the app for the inspector to talk to, and #9781 could be a good fit

@cboulanger

This comment has been minimized.

Copy link
Contributor Author

commented Sep 10, 2019

Ok, that would be a completely new project. I am going to archive and move it over. Then it can be picked up by anyone who wants to revive the project.

@cboulanger cboulanger added the GitHub label Sep 11, 2019

@cboulanger cboulanger added this to the release_6_0_0 milestone Sep 11, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.