Very helpful info. We open-source a lot of small packages, and although I'm not sure we'll follow all of these principles for all of them (sorry, Phil!) it's great to have an easy place to go to see what would be the best we could do to support them. Our team really wants to get into open-sourcing.
I really like both the vision/mindset of the group and the checklist approach to doing things the right way. I have a couple packages that I need to think through to make sure they're up to these standards.
I hadn't planned on attending this talk, but got caught up with some great conversations in the same room (hint to prospective LSP16 attendees, this is a good thing!) so stuck around to hear Phil's talk. "PHP TownHall," of which Phil is the more loquacious half, is one of my favorite podcasts, so I had high expectations for this talk. Phil disappoints on a grand scale, because he approaches his talks with gravitas and jocular sobriety.
This talk emphasized not only code quality, but also documentation quality and PR (ie, Public Relations) quality. How one reacts to PRs (aka "pull requests') was also discussed. Phil spent much of his time talking about the important things that pajama-adorned developers rarely explore but should. Well done!
For my internal corporate work that will never be seen by the public eye, these concepts are still important. My clients are not anonymous legions, but are instead folks that I know and respect. Their happiness matters to me! The documentation I provide, the feedback I respond to, and the announcements I make are as important as the code I provide.
Serendipity led me to Phil's talk. I am glad that I attended.
Comments
Comments are closed.
Good info.
Some really excellent and useful information here for open source package involvement - waiting for the slides to go back over for some checklists...
What I'd love to see added - how does this also apply to private packages and usage?
Very helpful info. We open-source a lot of small packages, and although I'm not sure we'll follow all of these principles for all of them (sorry, Phil!) it's great to have an easy place to go to see what would be the best we could do to support them. Our team really wants to get into open-sourcing.
I really like both the vision/mindset of the group and the checklist approach to doing things the right way. I have a couple packages that I need to think through to make sure they're up to these standards.
I hadn't planned on attending this talk, but got caught up with some great conversations in the same room (hint to prospective LSP16 attendees, this is a good thing!) so stuck around to hear Phil's talk. "PHP TownHall," of which Phil is the more loquacious half, is one of my favorite podcasts, so I had high expectations for this talk. Phil disappoints on a grand scale, because he approaches his talks with gravitas and jocular sobriety.
This talk emphasized not only code quality, but also documentation quality and PR (ie, Public Relations) quality. How one reacts to PRs (aka "pull requests') was also discussed. Phil spent much of his time talking about the important things that pajama-adorned developers rarely explore but should. Well done!
For my internal corporate work that will never be seen by the public eye, these concepts are still important. My clients are not anonymous legions, but are instead folks that I know and respect. Their happiness matters to me! The documentation I provide, the feedback I respond to, and the announcements I make are as important as the code I provide.
Serendipity led me to Phil's talk. I am glad that I attended.