July 8, 2015 Board Meeting Minutes

Quorum

Quorum reached and meeting called to order at 11:08 ET / 16:08 UTC.

Attendees

Board Members

  • Deb Bryant
  • Richard Fontana
  • Leslie Hawthorn
  • Patrick Masson
  • Simon Phipps
  • Allison Randal
  • Bruno Souza
  • Paul Tagliamonte
  • Tony Wasserman

Guests

  • None

Expected, but Not Present

  • None

Sent Regrets

  • Mike Milinkovich
  • Tony Wasserman
  • Stefano Zacchiroli

Officer Reports

  • Motion to approve minutes (Patrick)
  • Treasurer's report (Mike), see Appendix A

Board Topics

  • Review service quotes (in email)

Communications Topics

  • Meeting to begin web site refresh with Nick Vidal
  • Sync meeting with potential new communications volunteer

Legal Topics

  • Tools for license review
  • Discussions around the development of a tool for managing and reviewing the license review process. Paul has begun to develop some ideas/funtionality.
  • NASA License update
  • Highlights the OSI's role and value in providing services related to improving submitted license language/terms

Membership Topics

Application for Affiliate Membership from:

Infrastructure Topics

Incubator/Project Topics

Review of Timeline

Next Board Meeting

The next OSI board meeting is scheduled for Aug. 12, 2015

Meeting adjourned at: 11:55 AM EDT

Motions

Motion (Allison): Approve and post the meeting minutes of Jun. 10, 2015
Second (Leslie):
Discussion:
Vote: 5 Yes; 0 No; 0 Abstain 1

Motion (Simon): Approve the application of LPI as an Affiliate
Second (Patrick): Discussion: Review of affilaite agreement and requirements.
Vote: Yes, 6; No, 0; Abstain 0

Motion (Leslie): Approve the application of Mifos as an Affiliate.
Second (Simon)
Discussion: Review of affilaite agreement and requirements.
Vote: Yes 6; No, 0; Abstain 0

Motion (Patrick): Approve the application of the University of Southern Queensland as an Educational Affiliate.
Second (Leslie):
Discussion: Review of agreement and requirements.
Vote: Yes, 6; No, 0; Abstain 0

Motion (Patrick): Approve the application of The Xerte Project as an Affiliate.
Second (Allison)
Discussion: Review of agreement and requirements.
Vote: Yes, 0; No, 0; Abstain, 0

Appendix A - Treasurer's Report

Treasurer's Report For the Month Ending June 30, 2015

Total Assets at Beginniing of Period: $87012.96

Income or Sources of Funds:

  • Contributions: $ 5
  • Memberships: $560 (14 x $40)
  • Open Hatch: Received $278.45 Paid $278.45
  • Interest: $1.57

Total Income or Sources of Funds: $566.57

Expenses or Uses of Funds for Operations:

  • Payroll $ 9035.93
  • Professional $ 1197.72
  • Bank Fees $ 53.18
  • Software $ 2760.70 (Roland Mas)
  • Supplies $ 21.60
  • Conferences/Conv $ 303.85
  • Working Groups, Project
  • Meetings $ 7524.59
  • Website Hosting $
  • Paypal $ 19.38

Total Expenses or Uses of Funds for Operations: $20916.95

Payroll Liabilities increase ie cash out 6074.69-6290.90 $ 216.21

Total Assets at End of Period $66,878.79

Major Contributions 2015:

  • Corporate Sponsorship $2500 invoiced 1/29/15 received 3/3/15
  • Corporate Sponsorship $ 25000 unsolicited received 3/6/15
  • Corporate Sponsorship $ 20000 invoiced1/20/15 received 4/6/15
  • Corporate Sponsorship $25000 invoiced 6/16/15
  • Corporate Sponsorship $ 5000 Invoiced 6/3/15 Received in 7/2/15
  • Corporate Sponsorship $ 20000 invoiced 1/26/15 paid 5/15/15
  • Corporate Sponsorship $ 1000 invoiced 4/10/15 paid 4/10/15

Appendix B - Team Reports

Communications Team

Membership Team

Infrastructure Team

Legal Team

Incubator/Projects Team

Appendix C - Applicant(s) QualificationsEdit

Linux Professional Institute (https://www.lpi.org/)
Completed documentation on Affiliates Wiki Page

  1. Currently recognized as a (or application submitted for) non-profit / not-for-profit (or equivalent) by the national government were organized.
    Letters Patent Incorporating approved on August 16, 1999
  2. Mission statement describing purpose and goals.
    ✅ Available at: https://www.lpi.org/about-lpi/
  3. Documentation formalizing organization, e.g. by-laws.
    By-laws and operations are publicly available (Ref: https://drive.google.com/file/d/0ByeK44WJrHIvN2lGWVZYaGI2SjA/edit)
  4. Publicly available release of a product(s) or service(s).
    ✅ LPI has one professional development certificate program, Linux Essentials, as well as three professional Linux certification programs: LPIC-­‐1, LPIC-­‐2, and LPIC-­‐3.     
  5. Use of an OSI approved open source license (software development projects only).
    Not Applicable
  6. Documented approach for participation by the public.
    ✅ LPI community is active in the development of certification exams through their Exam Development discussion list. The community assists in certification development process by providing feedback on industry needs through the Job Task Analysis survey and community SMEs help develop exam objectives and aid in item development. For       more information about our process, visit: https://www.lpi.org/certification/certification-development-process/
    Those interested in volunteering with the LPI to help with exam development can find information at: www.lpi.org/community/volunteer/
  7. An active community:
    1. Methods for current and interested individuals/organizations to join and participate in your community
      ✅ LPI has an active social community (www.lpi.org/social) and their community is active in the development of the certification exams through our Exam Development       discussion list as outlined above.    
    2. Active participation from multiple contributors, i.e. individuals and organizations other than founders (contributions may be other than programming/technology)
  8. References from other open source projects, ideally a current OSI Affiliate Member.
    ✅ Linux Foundation (via their Linux.com website) lists LPI as one of the top 5 Linux Certification programs http://www.linux.com/learn/linux-­‐certifications
    Dru Lavigne of FreeBSD holds some LPI exams labs on our behalf at events when LPI is unable to attend inperson.      

Mifos (http://mifos.org/)
Completed documentation on Affiliates Wiki Page

  1. Currently recognized as a (or application submitted for) non-profit / not-for-profit (or equivalent) by the national government were organized.
     ✅ 501(c)3 Designation Letter, received on July 23, 2013 (Ref: https://drive.google.com/file/d/0ByeK44WJrHIvVjRZVFZoclVYX0k/edit)
  2. Mission statement describing purpose and goals.
    Mission statement is documented (Ref: http://mifos.org/about-us/)
  3. Documentation formalizing organization, e.g. by-laws.
    By-laws and operations are publicly available (Ref: https://drive.google.com/file/d/0ByeK44WJrHIvN2lGWVZYaGI2SjA/edit)
  4. Publicly available release of a product(s) or service(s).
    Downloads of Mifos X are available (Ref: http://mifos.org/take-action/get-mifos/#download​, http://sourceforge.net/projects/mifos/files/Mifos%20X/​ and https://github.com/openMF/mifosx)
  5. Use of an OSI approved open source license (software development projects only).
    ✅ Mifos X is distributed with the MPL (Ref: http://mifos.org/about-us/financial-legal/, https://github.com/openMF/mifosx/blob/develop/LICENSE.md)
  6. Documented approach for participation by the public.
    ✅ Public information regarding how to participate can be found at http://mifos.org/take-action/​. Mifos has a Developer Network at https://mifosforge.jira.com/wiki/display/MDZ
  7. An active community:
    1. Methods for current and interested individuals/organizations to join and participate in your community
      ✅ Public information regarding how to participate can be found at http://mifos.org/take-action/volunteer/).
    2. Active participation from multiple contributors, i.e. individuals and organizations other than founders (contributions may be other than programming/technology)
      ✅ Mifos reports approx 100 Pull Request per release/quarter as can be seen at https://github.com/openMF/mifosx/pulls?utf8=%E2%9C%93&q=created%3A2014-10-0
      1..2015-03-31+
      ​.
  8. References from other open source projects, ideally a current OSI Affiliate Member.
    ✅ Identified OpenMRS--Patrick contacted to confirm.

University of Southern Queensland (http://www.usq.edu.au)
Completed documentation on Affiliates Wiki Page

  1. Institution is currently recognized and in good standing by an appropriate accreditation body.
    ✅ USQ has been accredited by the Tertiary Education Quality Standards (TESQA): PRV12081 and the Commonwealth Register of Institutions and Courses for Overseas Students (CRICOS): QLD 00244B, NSW 02225M (Ref:http://wiki.opensource.org/bin/download/Communities/Affiliate_Status/USQCoverLetter.pdf).
  2. Evidence of institutional/departmental authority to affiliate with external organizations.
    ✅ The membership is at the University level, not through a department/division. Cover letter signed by University President, Jan Thomas (Ref:http://wiki.opensource.org/bin/download/Communities/Affiliate_Status/USQCoverLetter.pdf).
  3. Mission statement describing purpose and goals of institution/department.
    ✅ “To enable broad participation in higher education and to make significant contributions to research and community development”(Ref: USQ Strategic Plan 2013-2015, Pg 16)
  4. Documentation by the institution recognizing organization (academic and administrative departments only), e.g. organizational chart.
    ✅ The membership is at the University level, not through a department/division. Cover letter signed by University President, Jan Thomas (Ref:http://wiki.opensource.org/bin/download/Communities/Affiliate_Status/USQCoverLetter.pdf).
  5. Publicly available release of a product(s) or service(s) in line with the goals, values and mission of the OSI.
    ✅ USQ has developed and released ReDBox; (http://www.qcif.edu.au/services/redbox) as open source via QCIF (who provide maintenance and updates). ReDBox (Research Data Box) helps the research community describe and share information about research data collections. Created a culture of open use and reuse of educational resources, with an emphasis on working in communities and contributing rather than creating. Has participated in the Moodle Development CoOP. Has developed the “Collaboratorium” a University wide, open forum to discuss Openness, related ideas and emerging issues. Active involvement in the OERu community through which USQ helps develop productive use of the learning and teaching platform, MediaWiki, contribute open course materials, and volunteer on a range of working groups. (Ref:http://wiki.opensource.org/bin/download/Communities/Affiliate_Status/USQCoverLetter.pdf).
  6. Examples of software used and/or supported within the institution/department with an OSI approved open source license.
    ✅ USQ is an active participant in the use of Moodle, Mahara, ePrints and Wordpress as examples of software utilised within the institution with an OSI approved open source licence.
  7. An active community:
    1. Methods for current and interested individuals/organizations to join and participate in your community
      ✅ Many considering this membership is at the University level.
    2. Active participation from multiple contributors, i.e. individuals and organizations other than founders (contributions may be other than programming/technology)
      ✅ Many considering this membership is at the University level.
  8. References from other open source projects, ideally a current OSI Affiliate Member.
    ✅ Ian Dolphin, Apereo Foundation; Patrick Masson, OSI.

The Xerte Project (http://www.xerte.org.uk)
Completed documentation on Affiliates Wiki Page

  1. Currently recognized as a (or application submitted for) non-profit / not-for-profit (or equivalent) by the national government were organized.
    ✅ The project is sponsored by the University of Nottingham (Ref: https://www.nottingham.ac.uk/xerte/index.aspx)
  2. Mission statement describing purpose and goals.
    ✅ Mission statement is documented (Ref: https://github.com/thexerteproject/xerteonlinetoolkits/wiki)
  3. Documentation formalizing organization, e.g. by-laws.
    ✅ By-laws and operations are publicly available (Ref: https://github.com/thexerteproject/xerteonlinetoolkits/wiki/6.-Decision-Making-Process)
  4. Publicly available release of a product(s) or service(s).
    ✅ Downloads are available (Ref: http://www.xerte.org.uk/index.php?option=com_jdownloads&Itemid=510&view=viewcategories&lang=en)
  5. Use of an OSI approved open source license (software development projects only).
    ✅ Xerte is distribute with the Apache License (Ref: https://github.com/thexerteproject/xerteonlinetoolkits/blob/develop/LICENSE)
  6. Documented approach for participation by the public.
    ✅ Public information regarding events and so on is announced via the Xerte list or the xerte-dev list (Ref: http://lists.nottingham.ac.uk/mailman/listinfo/xerte and herehttp://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev).
  7. An active community:
    1. Methods for current and interested individuals/organizations to join and participate in your community
    2. Active participation from multiple contributors, i.e. individuals and organizations other than founders (contributions may be other than programming/technology)
      ✅ Evidence of our well established and very active community of users and developers can be found in the xerte list archives herehttp://lists.nottingham.ac.uk/pipermail/xerte/, the xerte-dev archives here http://lists.nottingham.ac.uk/pipermail/xerte-dev/, the forums herehttp://xerte.org.uk/index.php?option=com_kunena&view=category&Itemid=760&lang=en&layout=list and elsewhere on the web herehttps://www.google.co.uk/#safe=off&q=xerte.
  8. References from other open source projects, ideally a current OSI Affiliate Member.
    ✅ Ian Dolphin, Ex. Dir. of OSI Affiliate Apereo Foundation has provided a reference for Xerte.