The Heliophysics community is moving towards routine release of software as open source, going beyond "software as software" efforts to include public availability of research-specific and task-specific code. In the context of this trend, recently-adopted NASA Heliophysics Division and Science Mission Directorate policies require all SMD-funded software to be released as open source. This session discusses approaches to "open source as default", whether by requirement or voluntarily. All participants developing task-oriented software, such as for a specific research study or operational need, are welcome; those contributing to missions are particularly invited. Suggested topics for discussion include but are not limited to: Managing open-source requirements on missions and projects which are technically exempt (e.g., started before a requirement was imposed); strategies for compliance with the spirit of open-source requirements Differing approaches for code with different purposes (e.g. data processing vs. data analysis vs. one-off studies) Approaches to treatment of existing and legacy code Management of institutional tech transfer issues Leveraging requirements or voluntary release to foster improved software development and maintenance practices within a mission Best practices for maximizing return on effort