Skip to content
This repository has been archived by the owner on May 9, 2021. It is now read-only.

5. Lessons Learned

Lynn Bendixsen edited this page Nov 12, 2019 · 3 revisions

This page is for best practices (AKA lessons that have been learned the hard way).

Advice for Product Owners


Don't use 12:00 (noon or AM) as a closing time for proposals. It confuses people if they don't read carefully. Update: We've made the create an opportunity form to lock proposal deadline times at 16:00 Pacific Time.


After you've evaluated proposals, before you formally announce an assignment, ask the person you chose to confirm that they in fact want the assignment!


If a Milestone date is not going to be met, be very clear in your communications—with both the developer involved and the community, via the GitHub issue—about what is going to be done about it (i.e. extend the milestone, or reassign).


The faster you respond and provide feedback, the more likely the developer will be collaborative and iterate more with you.