Skip to content
This repository has been archived by the owner on Jun 8, 2023. It is now read-only.

Review hubot-scripts organization and npm for scripts that have been extracted #1641

Closed
20 of 28 tasks
technicalpickles opened this issue Jun 6, 2015 · 12 comments
Closed
20 of 28 tasks

Comments

@technicalpickles
Copy link
Contributor

technicalpickles commented Jun 6, 2015

As part of deprecating this repo, we'll want to find scripts that have been extracted, and prompt users to use those. When we get closer to turning this off, we can make it more forceful.

Some places to look:

Example snippet for deprecation: https://github.com/github/hubot-scripts/blob/master/src/scripts/pagerduty.coffee#L61 (This is handled in hubot as of 2.19.0)

Running list of things to deprecate:

Known things without extractions:

  • bing.coffee
  • bang-bang.coffee
  • python_library.coffee
  • cowsay.coffee
  • brewerydb.coffee (there's a npm package, but the GitHub repository was deleted, and README makes it look like it was something else)
  • github-pulls.coffee
  • graphite.coffee

cc @github/open-source-hubot-maintainers

@technicalpickles
Copy link
Contributor Author

When new issues are opened, we should check to see if it's on a script that's been extracted. That'd give us a nice reactive list, without having to go through everything up front.

@notpeter
Copy link

notpeter commented Jun 8, 2015

I'm also maintaining the original Karma script (karma.coffee, not plusplus.coffee).
https://github.com/notpeter/hubot-karma-classic

@cycomachead
Copy link
Contributor

I'm willing to move my package over to wherever it needs to be. I'm also probably going to work on my own hubot over the summer and will probably find reasons to fix scripts -- what should the process be for doing that? It seems like most scripts have an author, but not necessarily a maintainer, assuming I give credit to the original work, is there any harm in creating a new package, and the creating new PR's with deprecation warnings?

@cycomachead
Copy link
Contributor

Some additional scripts to deprecate:

meme_captain.coffee → cycomachead/hubot-meme
xkcd.coffee → https://www.npmjs.com/package/hubot-xkcd

@ChrisMissal
Copy link
Contributor

@technicalpickles
Copy link
Contributor Author

#1697 adds a mapping of deprecated scripts in that package to external packages. Then hubotio/hubot#970 builds on this to display notices to users that they are using the deprecated thing with some actions to take. Unfortunately, the action for most people is going to be to try to find a replacement or maintain it themself, but the notice points to this issue for coordination.

@khera
Copy link

khera commented May 11, 2016

I was just directed here after an npm update and restart of my hubot. One of the scripts the warning message says has no replacement is "s3-brain.coffee", yet I see it linked above in the checklist. Is it supposed to detect these already, or is that still not an implemented feature?

edit: looks like the replacements.json file lists "s3-brain" instead of "s3-brain.cofee" as the key.

@jvarness
Copy link

@technicalpickles for brewerydb.coffee, I made a hubot package that uses untappd instead of brewerydb that can suggest random beers for you: https://github.com/jvarness/hubot-barkeep

This isn't a 100% like-for-like replacement, but it might be similar.

@jdoose
Copy link

jdoose commented Jul 29, 2016

@markspolakovs
Copy link

@mmwtsn
Copy link

mmwtsn commented Jan 10, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests