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

Please migrate plugins from old to new repo #15661

Closed
qgib opened this issue Sep 25, 2012 · 11 comments
Closed

Please migrate plugins from old to new repo #15661

qgib opened this issue Sep 25, 2012 · 11 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins

Comments

@qgib
Copy link
Contributor

qgib commented Sep 25, 2012

Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 6408
Affected QGIS version: master
Redmine category:python_plugins


Plugins from old repos are now de facto unavailable for new users. Please move them to the new repo. Only deprecated, non functional plugins should be left out.

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2012

Author Name: Jürgen Fischer (@jef-n)


Shouldn't that be filed in the trackers of the missing plugins?

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2012

Author Name: Paolo Cavallini (@pcav)


Maybe yes, but:

  • not all missing plugins have a bugtracker
  • I believe this is a general issue, that can be solved with a mass importation rather than one by one.

Of course, this is open to discussion.

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2012

Author Name: Jürgen Fischer (@jef-n)


Paolo Cavallini wrote:

Maybe yes, but:

  • not all missing plugins have a bugtracker
  • I believe this is a general issue, that can be solved with a mass importation rather than one by one.

Of course, this is open to discussion.

But it's not a qgis issue...

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2012

Author Name: Bernd Vogelgesang (Bernd Vogelgesang)


But it's not a qgis issue...

well, but "qgis" changed its policy, and now functionalities are lost.
it may be discussed in length and breadth whos fault that is, but at least its a "bug" in the documentation, cause users are highly irritated and nearly no information was published what happened and how this process is going to be coordinated.
This will only result in thousands of hours of lost time with frustrating searches, when people find a tutorial for their problem, but they have no clue where to get the plugin and when they found it, how to install it from outside the plugin installer.

My top 2 plugins for the start:
openlayers:
A lot people have no access to imagery and benefit a lot from this.
table manager:
Though a lot functionalities already went into core, you still can't reorder or rename columns in a shapefile dbf within qgis without extra steps in the field calculator.

Thanx for your great work!

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2012

Author Name: Paolo Cavallini (@pcav)


Table Manager has been migrated

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2012

Author Name: Jürgen Fischer (@jef-n)


Bernd Vogelgesang wrote:

But it's not a qgis issue...

well, but "qgis" changed its policy, and now functionalities are lost.
it may be discussed in length and breadth whos fault that is, but at least its a "bug" in the documentation, cause users are highly irritated and nearly no information was published what happened and how this process is going to be coordinated.

The question isn't who's fault it is - the question is who can do something about it. If it's not a qgis issue, it doesn't belong here. I think the plugin authors need to act and they probably don't care much about a ticket here.

We can't do much in qgis about it, except to reinstate the old repository list or hijack all plugins - both probably not what we want.

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2012

Author Name: Paolo Cavallini (@pcav)


I think there is a general agreement on moving the plugins from old to new repo - it's a simple backend replacement after all, no interference with real life of plugins.

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2012

Author Name: Jürgen Fischer (@jef-n)


Paolo Cavallini wrote:

I think there is a general agreement on moving the plugins from old to new repo - it's a simple backend replacement after all, no interference with real life of plugins.

huh? if that's so, why isn't it done already?

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2012

Author Name: Paolo Cavallini (@pcav)


Usual reason - lack of time?

@qgib
Copy link
Contributor Author

qgib commented Dec 30, 2012

Author Name: Giovanni Manghi (@gioman)


  • priority_id was changed from High to Normal

@qgib
Copy link
Contributor Author

qgib commented Jun 23, 2014

Author Name: Paolo Cavallini (@pcav)


  • resolution was changed from to fixed/implemented
  • status_id was changed from Open to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins labels May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins
Projects
None yet
Development

No branches or pull requests

1 participant