December 9, 2015 Board Meeting Minutes

Quorum

Quorum reached and meeting called to order at 11:15

Attendees

Board Members

  • Allison
  • Deb
  • Leslie
  • Patrick
  • Richard
  • Tony
  • Zack

Guests

  • None

Expected, but Not Present

  • Paul

Sent Regrets

  • Mike
  • Simon

Officer Reports

Board Topics

  • Determine dates for the next F2F
    • According to the board@ thread, best option seems to be April Weds 20 (Dinner), Thus  21(Social), &  Fri 22 (Bail), 2016 in Boston

Membership Topics

  • Review new Affiliate Member Applicants (Appendix C)
  • ACTION: Patrick and Richard to develop communication to Kuali Foundation to clarify relationship with KualiCo.

Communications Topics

Legal Topics

Infrastructure Topics

Incubator/Project Topics

Review of Timeline

  • Planning Timeline
  • ACTION: confirm with Helios ability to host.

Next Board Meeting

The next OSI board meeting is scheduled for January 13, 2016

Meeting adjourned at: 12:45.


Motions

Motion (Patrick): Approve and post the meeting minutes of Face to Face, Nov. 10-11 .
Second (Allison).
Discussion: None
Vote: 5 Yes; 0 No; 2 Abstain.

Motion (Patrick): Approve and post the meeting minutes of Oct. 14
Second (Allison).
Discussion: None
Vote: 7 Yes; 0 No;  0 Abstain.

Motion (Deb): Approve IU assoc affilate.
Second (Patrick).
Discussion: Interested in academic activity related to open source. Application comes from administration
Vote: 7 Yes; 0 No;  0 Abstain.

Motion (Allison): Approve Kaiyuanshe as a non-profit Affiliate.
Second (Zack).
Discussion: Information required translation and interpretation, but confimed with Kaiyuanshe. Questions raised about sponsorship an support. Initially connected through Debian and their work with Kaiyuanshe, as well as a reference from Microsoft. An Affiliate in China would also help with various issues around OSI brand / identity. We do have an English speaking contact.
Vote: 7 Yes; 0 No; 0 Abstain.


Appendix A – Treasurer’s Report

Treasurer’s Report For the Month Ending November 30, 2015

The IRS has sent a letter confirming the collection case is closed with no penalty due.

Total Assets at Beginning of Period: $54218.38Income or Sources of Funds:

  • Contributions: $ 5101.12
  • Memberships: $ 560.00 (14 x $40)
  • Open Hatch: Received $254.60 paid $0.0 (October and November paid 12/10/15)
  • Snowdrift $ -7200.00
  • Commissions $
  • Interest: $ .98

Total Income or Sources of Funds: $ -1283.30Expenses or Uses of Funds for Operations:

  • Payroll $ 8,970.84
  • Professional $ 613.00
  • Bank Fees $ 55.57
  • Software $
  • Postage, Shipping $
  • Conferences/Conv $ 251.91
  • Working Groups, Project
  • Meetings $ 1941.17
  • Website Hosting
  • Paypal $ 21.98

Total Expenses or Uses of Funds for Operations: $ 11854.47

Payroll Liabilities $2629.62-2631.92 $ 0.0

Total Assets at End of Period $ 41,080.61

Major Contributions 2015:

  • Previous Annual Sponsor: $ 2500 invoiced 1/29/15 received 3/3/15
  • Previous Annual Sponsor: $ 25000 unsolicited received 3/6/15
  • Previous Annual Sponsor: $ 20000 invoiced10/29/14 received 1/20/15
  • Previous Annual Sponsor: $ 20000 invoiced1/20/15 received 4/6/15
  • Previous Annual Sponsor:  $25000 invoiced 6/16/15 received 7/24/15
  • Previous Annual Sponsor: $ 5000 Invoiced 6/3/15 Received in 8/28/15
  • Previous Annual Sponsor: $ last invoiced 6/6/2014 received 7/1/14
  • Previous Annual Sponsor: $ 4000 Invoiced 9/7/15
  • Previous Annual Sponsor: $ 20000 invoiced 1/26/15 paid 5/15/15
  • Previous Annual Sponsor: $ 1000 invoiced 4/10/15 paid 4/10/15
  • New Annual Sponsor: $ 5000 Invoiced 9/28/15 paid 10/4/15
  • New Annual Sponsor: $ 5000 invoiced 10/15/15 paid 11/30/15

Appendix B – Team Reports

Communications Team

Membership Team

Infrastructure Team

Legal Team

Incubator/Projects Team

Appendix C – Review of new Affiliate Members

Indiana University

View Affiliate Agreement

  1. Institution is currently recognized and in good standing by an appropriate accreditation body.
    ✓ Indiana University is accredited by The Higher Learning Commission (http://www.ncahlc.org) and is a member of the North Central Association (http://registrar.indiana.edu/disclosures/accreditation.shtml)
  2. Evidence of institutional/departmental authority to affiliate with external organizations.
    ✓ Agreement signed by Donald S. Lukes, University Treasurer and provided via Brad Wheeler, Vice President for IT and CIO.
  3. Mission statement describing purpose and goals of institution/department.
    ✓ Indiana University’s mission is to provide broad access to undergraduate and graduate education for students throughout Indiana, the United States, and the world, as well as outstanding academic and cultural programs and student services. Indiana University seeks to create dynamic partnerships with the state and local communities in economic, social, and cultural development and to offer leadership in creative solutions for 21st-century problems. Indiana University strives to achieve full diversity, and to maintain friendly, collegial, and humane environments, with a strong commitment to academic freedom (http://www.iu.edu/about/mission.shtml).
  4. Documentation by the institution recognizing organization (academic and administrative departments only), e.g. organizational chart.
    ✓ See organizational chart (http://www.iu.edu/about/org-chart.shtml).
  5. Publicly available release of a product(s) or service(s) in line with the goals, values and mission of the OSI.
    ✓ IU produces a variety of open content and services, from academic materials and courses to technologies and software. (http://open.iu.edu/)
  6. Examples of software used and/or supported within the institution/department with an OSI approved open source license.
    ✓ “IU is a leader in open source software with the Open Systems Lab, Sakai, Kuali, and OSP projects” (http://open.iu.edu/)
  7. An active community:
    1. Methods for current and interested individuals/organizations to join and participate in your community
      ✓ Participation is undertaken through the projects in which IU supports and contribute. IU also has opportunuties for faculty/staff/students to release their original work under an
      open source license (http://iurtc.iu.edu/process/software-licensing/index.shtml)
    2. Active participation from multiple contributors, i.e. individuals and organizations other than founders (contributions may be other than programming/technology)
      ✓ IU participates in many ways across multiple open source projects, as a founding institution of the Sakai Project (https://kb.iu.edu/d/anej, Kuali (http://www.kuali.org/membership/members), and as contributors and users to the same (http://www.indiana.edu/~ocmhptst/021304/text/FAQ.shtml) and many more (https://pti.iu.edu/research/oss.php).
  8. References from other open source projects, ideally a current OSI Affiliate Member.
    ✓ Board members Deb Bryant and Patrick Masson have worked with Indiana University VP & CIO, Brad Wheeler on multiple open source projects and communities.

Kaiyuanshe

View: Affiliate Agreement, Qualifications, Letter of Reference:

  1. Currently recognized as a (or application submitted for) non-profit / not-for-profit (or equivalent) by the national government were organized.
    ✓Kaiyuanshe is established under the support and guidance of the Department of the Shanghai Software Industry Association and the Professional Committee of open-source software, in accordance with the principles of “cohabitation, work, contribute”. – http://www.kaiyuanshe.cn/joinus.php
  2. Mission statement describing purpose and goals.
    ✓Help China to become actively involved in the open source community and contributors to open source software globally. Create an open source ecosystem for healthy and sustainable development, together with local communities, businesses, universities, and government. – http://www.kaiyuanshe.cn/about.html 
  3. Documentation formalizing organization, e.g. by-laws. http://www.kaiyuanshe.cn/joinus.php 
  4. Publicly available release of a product(s) or service(s).
    ✓Publicly available reference documentation on open source licenses: http://www.kaiyuanshe.cn/index.php?option=com_content&view=category&id=8✓Publicly available posts on open source participation and governance: http://www.kaiyuanshe.cn/index.php?option=com_content&view=category&id=15✓Local language license selection tool: http://www.kaiyuanshe.cn/license-tool.html✓Besides, we also deliver China Open Source Ecosystem report. You can download it from here (Chinese version), Download: http://www.kaiyuanshe.cn/portal/file-download-69-left.html , online: http://kaiyuanshe.github.io/2015R1/#/
  5. Use of an OSI approved open source license (software development projects only).
    ✓Kaiyuanshezhixing (OSS Star) project which will help software developers apply for open source licenses to their projects and give special recogintion to those who use one of the several available OSI-approved licenses.
    ✓The link to the OSS start project: http://www.kaiyuanshe.cn/star-home.html
    ✓Source code is on github: https://github.com/msopentechcn/kaiyuanzhixing✓Besides, we also have an Open Hackathon Platform which can provide cloud development environment for Online Hackathons, website: http://hacking.kaiyuanshe.cn/landing✓Source code on github: https://github.com/msopentechcn/open-hackathon✓Both the two projects are developed by Microsoft Open Tech team which are core member of Kaiyuanshe, they have contribute those two projects to Kaiyuanshe.
  6. Documented approach for participation by the public.
    ✓Kaiyuanshe’s working groups and related mailing lists provide a path for participation. – http://www.kaiyuanshe.cn/working-group.html
  7. An active community:
    1. Methods for current and interested individuals/organizations to join and participate in your community
      ✓New members apply to join the open source community by submitting an application on the website. Applications are voted on and approved by a majority of the open source community council members. New members sign the membership Code. – http://www.kaiyuanshe.cn/joinus.php
    2. Active participation from multiple contributors, i.e. individuals and organizations other than founders (contributions may be other than programming/technology)
      ✓Kaiyuanshe’s working groups show active participation by many individuals and organizations. – http://www.kaiyuanshe.cn/working-group.html
  8. References from other open source projects, ideally a current OSI Affiliate Member.
    ✓See reference letterfrom Mozilla.

Kuali Foundation

View: Agreement Letter, Bylaws, Tax StatusQualifications:

  1. Currently recognized as a (or application submitted for) non-profit / not-for-profit (or equivalent) by the national government were organized.
    ✓ See IRS U.S. tax documentation (http://osi.xwiki.com/bin/download/Communities/Affiliate_Status/KualiFoundationIRSExemptionLetter2015.pdf)
  2. Mission statement describing purpose and goals (https://www.kuali.org/about/governance/bylaws).
    ✓ The mission of Kuali is to enable the community to advance the mission of higher education and specifically:
    1. To deliver software and associated systems, tools, designs, services, and components (hereafter “software”) that collectively work together to support the needs of educational institutions and other similar non-profit entities;
    2. To support collaboration and community building that support software and the mission;
    3. To solicit grants and other funding to permit the development and refinement of software and community building
    4. To promote economic efficiencies for IT in software system settings through cooperation, leverage of shared investments and innovation;
    5. To engage in the development, adoption and propagation of open standards for IT, data and information, through cooperation with similar efforts;
    6. To engage in such activities permitted under the Indiana Nonprofit Corporation Act, incidental or beneficial to the foregoing purposes; and
    7. To serve as an effective voice for open and community source software that supports education and other similar non-profit activities.
  3. Documentation formalizing organization, e.g. by-laws.
    ✓ https://www.kuali.org/about/governance/bylaws
  4. Publicly available release of a product(s) or service(s).
    ✓ Multiple applications available at: https://www.kuali.org/download
  5. Use of an OSI approved open source license (software development projects only).
    ✓ Kuali software is licensed under the GNU Affero General Public License version 3 (AGPLv3), an approved Open Source Initiative license. (http://www.kuali.org/about/license)
  6. Documented approach for participation by the public.
    ✓ Membership (http://www.kuali.org/membership)✓ Partners (http://www.kuali.org/partner)
  7. An active community:
    ✓ Kuali User Groups (https://kis.kuali.org/collabs/)✓ JIRA (https://jira.kuali.org/secure/BrowseProjects.jspa#all)✓ Confluence (https://wiki.kuali.org/dashboard.action)
  8. References from other open source projects, ideally a current OSI Affiliate Member.