This is an editable wiki page for collecting information with the intent towards develop a working Standard Operating Procedure SOP and Open Source Management Plan

This is not an official NCSA SOP or Management Plan.

Collection of ideas.

Links:

• University of Illinois/NCSA Open Source License: http://otm.illinois.edu/uiuc_openSource
  where Organization Name is:  The Board of Trustees of the University of Illinois. 
  • ERGO Code contribution process
    https://opensource.ncsa.illinois.edu/confluence/display/ERGO/Code+Contribution+Process+to+ERGO+Project
  • ERGO Project Contributor License Agreement
    140828 ERGO Contributor license Agreement- FINAL CLEAN.docx 
• Open Source web project: http://opensource.ncsa.illinois.edu/projects/
• Open Source Initiative: http://opensource.org/
  • Open Source Licenses: http://opensource.org/licenses
  • Open Source FAQ: http://opensource.org/faq
    • Which Open Source license should I choose to release my software under? http://opensource.org/faq#which-license 
      You can choose any license from the open source licenses listed starting here: opensource.org/licenses. Most people select one from the "popular" category, but you are free to choose any listed license.
      If this is your first time choosing an open source license, we recommend that you find someone who has experience with open source licensing and talk to them about your project — that will help you choose the most appropriate license. The person doesn't have to be a lawyer; it could be a developer who has experience releasing open source code. The section Choosing a License at the Civic Commons wiki may be useful, and you can learn more about open source licenses from Section 3.2 of the eBook Introduction to Free Software by Hernandez, Jimenez, Barahona, Pascual, and Robles.
• Office of Technology Management OTM: http://otm.illinois.edu/
  • OTM Disclosure forms: http://otm.illinois.edu/uiuc_invDisclosure
    • http://otm.illinois.edu/sites/all/files/files/softwaredisclosure.pdf
  • Intellectual Property: http://otm.illinois.edu/uiuc_principlesofip
• GItHub: https://github.com/ncsa
• XSEDE repository and software strategy paper: http://cb-repo.iu.xsede.org/xsederepo/XSEDE-Campus-Bridging-Cluster-software-strategy-2013.pdf
• ITIL - set of service and delivery processes for IT services http://www.itil-officialsite.com/

Standard Operating Procedure (SOP)

service description needed

• Develop Software
• Determine if software is suitable for Open Source Licensing

If,

• • You are sure that you have all the rights and the code
    was developed on Illinois time and resources 
  • You are sure that the code is yours and not a third parties
    or that any third party code included is open source 
  • You are sure that the funding says it is ok to release as open source
  • You have determined which open source license to release software under
  • You have determined that there are no existing patents or possible future patents that exist with the code

Then, it is ok to move forward with posting the code as open source
using the NCSA Open Source copyright info

If you have any questions related to these issues or
need to figure out which open source license to use, then
contact the OTM office with your questions.

• Incorporate appropriate copywrite info from http://otm.illinois.edu/uiuc_openSourceinto source
• Release software to NCSA Open Source Repository http://opensource.org/
• Cataloging and management of documentation for NCSA Open Source Software
• Communication of software release and ongoing updates to interested parties (web presence, elists, etc.)

Additional Thoughts

This section for trying to develop a comprehensive view - how does open source licensing fit in with all the other stuff that's going on?

There are multiple aspects of this initiative that relate to a larger organizational structure around software and even data.

Specifically for software there is licensing,  contributor agreements and hosting. But on a larger scale this is just an extension
of National Data Service because publications data and software are  often times linked together (directly related). It's easy to
ignore that there is a physical component to storage for all this but they are linked.