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

plusplus / karma #14

Closed
ajacksified opened this issue Oct 25, 2013 · 3 comments
Closed

plusplus / karma #14

ajacksified opened this issue Oct 25, 2013 · 3 comments

Comments

@ajacksified
Copy link
Member

Github: https://github.com/ajacksified/hubot-plusplus

NPM: https://npmjs.org/package/hubot-plusplus

❤️

@patcon
Copy link
Member

patcon commented Oct 25, 2013

cc: @davereid

@technicalpickles
Copy link
Contributor

Forked and added the hubot-plusplus team! If you need any feedback or run into hubot issues, you can mention @hubot-scripts/hubot-maintainers

I only added @ajacksified but let me know if anyone else should be added.

@patcon
Copy link
Member

patcon commented Oct 28, 2013

@technicalpickles Nice! Isn't there an discoverability issue with primary repos being given special search result status over forks? Is it not better to transfer the repo wholesale to the hubot-scripts org, rather than forking?

EDIT: ie https://github.com/search?q=hubot-codinglove&ref=cmdform

With chef cookbooks at least, it's a huge problem when a fork becomes the maintained repo, because people keep submitting PR's to the original after doing a search and if the active fork maintainer isn't putting extra effort into scouring for that stray code, they get lost and the effort fragments (because the dead primary repo appears to be more active with pull requests, issues, etc)

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

No branches or pull requests

3 participants