Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

partner with Atmosphere.js #483

Closed
chadwhitacre opened this issue Jan 27, 2016 · 2 comments
Closed

partner with Atmosphere.js #483

chadwhitacre opened this issue Jan 27, 2016 · 2 comments

Comments

@chadwhitacre
Copy link
Contributor

Reticketed from #441 (comment).

Atmospherejs.com has a similar problem: https://atmospherejs.com/i/publishing

Why is Gratipay important? Well, consider the dreaded Dead Package Syndrome :-). Someone releases a cool and useful package as a fun creative effort. But months later, it no longer works with the latest version of Meteor... pull requests go unanswered... issues pile up. Creating a package is rewarding, but ongoing maintenance can be a lot of work (and often, not nearly as much fun :)

Happen to have more money than time right now? Fund the efforts important to you, and avoid having packages you rely on slowly die. Or, happen to have more time than money at the moment? Become a Gratipay recipient and get support for the community work you put in.
@awwx, Andrew Wilcox

@chadwhitacre
Copy link
Contributor Author

They are sending people to the old communities page for Meteor.

@mattbk Wanna reach out and see if they want to talk about a partnership a la Chocolatey (#441)?

@nobodxbodon
Copy link

Re-ticketed to #982 for further discussion and planning. After deciding on concrete implementation plan and dev work starts, this will be reopened for tracking purpose.

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

No branches or pull requests

2 participants