Last modified by Patrick Masson on 2023/02/17 01:51

Show last authors
1 {{info}}
2 In addition to the below 2018 report, additional annual reports are attached.
3 [[2019 Annual Report>>attach:ClearlyDefined Fiscal Sponsor Report 2019.odt]]
4 {{/info}}
5
6 ----
7
8 == ClearlyDefined Fiscal Sponsorship Annual Reports ==
9
10 Due Date of Report: The due date for the report is January 1st.
11
12 If you have questions on reporting requirements, please check with OSI staff at osi@opensource.org.
13
14 Type of submission (please check one):
15
16 ✓ This report completes the requirements for the current year of participation in the fiscal sponsorship program. We will be continuing in the program.
17
18 Group name: ClearlyDefined
19
20 Address: 855 El Camino Real, Ste 13A, #270
21 Palo Alto, CA 94301
22
23 United States
24
25 Telephone: (415) 857-5398
26
27 Email: clearlydefined@googlegroups.com
28
29 Website: clearlydefined.io
30
31 Contact person and role in group: Carol Smith, Program Manager; Board Director and Project Sponsor, OSI
32
33 Dates report covers from: 1/11/18 to 12/20/18
34
35 Submit cover sheet, 3-5 page report, and financial information to: [[osi@opensource.org>>path:mailto:osi@opensource.org]] Feel free to contact our office at (415) 857-5398 or email us at osi@opensource.org with any questions regarding this report or its submission.
36
37 Yearly Report Questions and Required Information: Please send us a short report about the fiscal sponsorship project’s progress. We hope that this will be an informal 2-3 page narrative report plus a financial accounting.
38
39 \\
40
41 ==== **Impact and Assessment** ====
42
43 1. Please restate the goal and objectives as stated in your original proposal and describe progress made.
44
45 Our mission is to help FOSS projects be more successful through clearly defined project data. Ambiguities around license metadata and vulnerabilities mean that FOSS cannot be consumed with confidence. This impacts adoption and success of FOSS and drives duplication in the compliance and security maintenance work for consumers. With ClearlyDefined, we propose crowdsourcing the curation of licensing, security, accessibility, and other data for FOSS projects. This project will harvest data embedded in FOSS and available in the broader community, and subsequently: curate the data in an open and collaborative process, contribute clearly defined data back to the FOSS projects, and make the data freely and easily accessible. The project will initially focus on licensing data that facilitates understanding and complying with the legal obligations related to using FOSS. This includes license (declared and discovered), copyright holders, and source location (including revision/commit).
46
47 We reached feature complete for the initial functionality in 2018 and now are making improvements and focusing on adoption and integration next year. We intend to scope the security work early in 2019.
48
49 \\
50
51 1. What was most effective? Response should include both qualitative and quantitative impacts where possible.
52
53 Finding the right metaphors to describe the project has helped quite a bit. Many of our initial conversations with potential users didn’t accurately place this project in context. Our conversations have been much more frank and fruitful and we have multiple potential users who may be able to move forward with integration soon.
54
55 Keeping the project specifically scoped to license data has also been helpful for our development work. It has helped us prioritize the development work we are executing with contractors as well as framing our goals and scope for the project with our users.
56
57 Finally, our projects’ alignment with OSI’s mission has benefitted us significantly. Our users understand the importance of clear license data about FOSS projects and see the OSI as an appropriate vendor- and organization-neutral body to support this data project.
58
59 \\
60
61 1. Please identify specific groups and communities that benefited from your program, including, if possible, the total number of people included in these groups or communities.
62
63 We currently have multiple organizations (Amazon, Google, Microsoft) helping to run the infrastructure, which has benefitted them and the project itself. We’ve begun to see projects upstream adopting practices that will make themselves more clearly defined in future versions, which we hope will grow significantly in 2019.
64
65 You can find a list of all our current partners here: https:~/~/clearlydefined.io/about
66
67 Our users are currently corporations which are benefiting from using the data in production settings as part of their compliance workflows.
68
69 \\
70
71 1. Please identify the benefits provided to the program groups or communities.
72
73 The data is freely available to anyone to use, we hope as adoption grows and more communities are relying on the ClearlyDefined data there will be more certainly around the license of projects and that will drive adoption of those projects.
74
75 The data quality is also demonstrably on par with data provided by vendors for a fee. Providing this data for free where it was previously offered for a fee will continue to benefit users over time.
76
77
78 ==== **Challenges** ====
79
80 1. Please list any changes of project plans in light of changing issues or significant challenges, whether expected or unexpected, and how dealt with them.

81
82 The project structure has not changed significantly, but the details of implementation and execution have become more defined over time. We understand now more precisely how to communicate to potential users what the project is.
83
84 The user interface and website portion of the project has also ended up being larger in scope than we initially anticipated. We have adjusted to this and all the necessary features that users and curators need in order to make use of or change the data have been implemented. We have identified more potential improvements and plan to continue work on them in 2019.
85
86
87 ==== **Evaluation and Lessons Learned** ====
88
89 1. Description of your evaluation process; please indicate who was involved and when it happened.
90
91 We evaluated our progress on 2018 as well as did our planning for 2019. This was done on December 18, 2018.
92
93 We provided feedback to OSI on our experience as a fiscal sponsoree along with the submission of this document.
94
95 1. What have you learned? Please describe any lessons or insights from the past year that you intend to apply in the future.
96
97 Much of the learnings over the last year have been around the implementation details of how the software will work and function. We’ve learned much more about how users will consume this data when it’s available. We’ve also heard from many users that they are interested in the ClearlySecure project getting off the ground, and we will prioritize scoping that work in 2019.
98
99 1. How did the funding you received during the year make a difference in your work?
100
101 The funding we’ve received has entirely been allocated to contract development work on the software and website for ClearlyDefined. This has meant we’ve been able to add features and functionality as well as make significant improvements in the software we could not have otherwise made. Our volunteer resources are very limited, and so the funding has enabled to build the project according to our specifications more quickly than if we had relied only on volunteer time.
102
103 Overall, this funding has been the crux of all the development we’ve done. It’s also meant that the development is primarily done by neutral parties who aren’t associated with a particular organization or company.
104
105
106 ==== **Funding and Finances** ====
107
108 1. Total funds received by your organization from The OSI during the reporting period.

109 11. $175,000
110 1. Itemize how these funds were spent.

111
112 |\\|\\|\\
113 |
114 \\(((
115 == Statement of Activity Comparison ==
116 )))|\\|\\
117 |November 2018|\\|\\
118 |\\|\\|\\
119 |Revenue|Nov 2018|Jan – Nov, 2018 (YTD)
120 | Contributions, Sponsorship, and Membership Revenue|\\|\\
121 | Contributions - Temporarily Restricted|\\|\\
122 | Contributions - Clearly Defined|$0|$175,000
123 | Total Contributions - Temporarily Restricted|$0|$175,000
124 | Total Contributions, Sponsorship, and Membership Revenue|$0|$175,000
125 |Total Revenue|$0|$175,000
126 |\\|\\|\\
127 |Expenditures|\\|\\
128 | Other Expenses|\\|\\
129 | Bank & Credit Card Fees|\\|\\
130 | Bank & Wire Transfer Fees|$152|$653
131 | Total Bank & Credit Card Fees|$152|$653
132 | Total Other Expenses|$152|$653
133 |\\|\\|\\
134 | Program Service Expense|\\|\\
135 | Clearly Defined Expense|\\|\\
136 | Administrative fee expense-OSI|\\|$17,500
137 | Development-ClearlyDefined|$20,000|$90,260
138 | Total Clearly Defined Expense|$20,000|$107,760
139 | Total Program Service Expense|$20,000|$107,760
140 |Total Expenditures|$20,152|$108,413
141 |\\|\\|\\
142 |Net Income|-$20,152|$66,587
143 |\\|\\|\\
144
145 1. Please attach the following items:
146 11. Attach a budget for your current fiscal year.
147 111. $20,000 - January contract development work
148 111. $20,000 - February contract development work
149 11. Attach a list of pending and planned funding requests for the year.

150 11. Please attach a list of the organization’s Board of Directors/Coordinating Committee/Or Other Decision Making Body. This list must include full names, title if any (i.e. board president, board chair, board treasurer, etc.), home address and telephone number, e-mail address and amount of any compensation paid by the organization to each member of the committee if applicable.

151 111. Carol Smith, contact information on file with OSI
152 11. A list of all staff and/or core volunteers. (There is no need to replicate the list of Board of Directors/Coordinating Committee/Or Other Decision Making Body in this list).
153 111. Jeff McAffer
154 111. Dan Butvinik
155 111. Alessandro Russo

Submit feedback regarding this wiki to webmaster@opensource.org

This wiki is licensed under a Creative Commons 2.0 license
XWiki 14.10.13 - Documentation