Contributing to Meteor Packages

Transcript

1. Contributing to Atmosphere Packages Meteor Boston / August 27th, 2015 TWTR: @bengreene
2. Y U NO MERGE???
8. Popular? On GitHub? Documented well? Recent releases?
9. Active development? Has tests?
10. Responds to issues?
11. Accepts pull requests?
13. “The Illustrated Guide to a Ph.D.” by Matt Might http://matt.might.net/articles/phd-school-in-pictures/
16. “accounts-entry is a meteor package that relies on Iron Router and provides an alternative interface to accounts-ui, with whole pages for sign up and sign in.”
19. /enroll-­‐account
21. Fork it!
30. [ do the work ]
33. 1. Keep it simple 2. Try to match style 3. Respond quickly! 4. Make veiled threats 5. resubmit Ben’s guide to getting a pull request merged:
34. 2. git submodule add PRO: easy to add CON: a pain to share, remove 3. meteor publish --create PRO: your forked package works like all the other ones you use CON: trivial amount of additional work 1. cp -r /path/to/package my_app/packages/ PRO: easy to add CON: source control nightmare
36. My 1 request…
37. Don’t steal.
38. This has been Ben Greene