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 Slingshot to a new Meteor organization: slingshot #125

Open
timbrandin opened this issue Aug 2, 2015 · 2 comments
Open

Move Slingshot to a new Meteor organization: slingshot #125

timbrandin opened this issue Aug 2, 2015 · 2 comments

Comments

@timbrandin
Copy link

Embrace the community and have all awesome slingshot packages under one roof!

  • edgee:slingshot -> slingshot:core
  • NEW PACKAGE!? -> slingshot:s3
  • NEW PACKAGE!? -> slingshot:google-cloud
  • NEW FUTURE PACKAGE!? -> slingshot:dropbox
  • NEW FUTURE PACKAGE!? -> slingshot:box
  • NEW FUTURE PACKAGE!? -> slingshot:sharepoint
  • NEW FUTURE PACKAGE!? -> slingshot:drupal
  • ryanswrt:autoform-slingshot -> slingshot:autoform

And from the different service provider packages we could give better detailed instructions for each service, like s3 differs somewhat from google-cloud I imagine.

The repos could still link to the original author, or you could create a new github organisation like CollectionFS.

Btw, you should check out the new version of ryanswrt:autoform-slingshot – It has some large improvements!

@gsuess
Copy link
Contributor

gsuess commented Aug 2, 2015

I already made a branch for splitting the package into its services: #105

Making a meteor account for slingshot, makes a lot of sense. Will see about making it happen.

@timbrandin
Copy link
Author

Awesome! Great!!

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

No branches or pull requests

2 participants