Update eligibility criteria

our-eligibility-criteria.md

@@ -1,28 +1,31 @@
 # Our Eligibility Criteria 
 
-Since the goal of the Open Source Collective is to support a Free and Open Source ecosystem, your project license is critically important. The list of [Open Source Initiative Approved License List](https://opensource.org/licenses) can serve as a gauge for valid open license criteria to the collective. Other valid licensing guidelines include the following: 
+We accept any open source project, in any language, anywhere in the world. We can also accept projects that are strongly associated with open source projects and communities like meetups and conferences, as well as advocacy groups, research, and awareness initiatives.
 
+If applying as an open source project your project license is critically important. We review licenses on a case-by-case basis when needed but licenses approved by the following bodies will significantly increase the likelihood your project will be approved:  
+
+* [Open Source Initiative Approved Licenses](https://opensource.org/licenses);
 * [Free Software Foundation License List](https://www.gnu.org/licenses/license-list.html); 
 * [Debian Free Software Guidelines](https://wiki.debian.org/DFSGLicenses); 
 * [Fedora Software License List](https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing);
 * [Open Source Hardware Association Statement of Principles](https://www.oshwa.org/definition/).
 
-We can accept any open source project, in any language, anywhere in the world. We can also accept open source related meetup groups and conferences, as well as advocacy, research, and awareness initiatives.
-
-If you are an open source project with at least 100 stars on GitHub and at least two contributors, you will likely be immediately approved.
-
-If you don’t fit 100 GitHub stars requirement, we will consider your application on a case by case basis, using the following criteria:
+We do not accept projects that do not have a recent history of activity or an established base of dependent packages, applications or services. If your project is a fork of an existing repository there should be a material degree of activity and usage _away_ from the forked project. 
 
-Projects who don’t have their code repo on GitHub should show equivalent traction to the 100 stars requirement, whether through GitLab stars, evidence that the project is a dependency of other open source projects, or similar social validation.
+We do not accept projects that are hosted under a personal profile. Please make sure your project is hosted under an profile that is not strongly associatated with an individual (i.e. an organisation account).
 
-User groups should have at least 50 members and be able to demonstrate a genuine history of community activity (forum, events, publications, etc).
+If you are an open source project with an [SPDX compliant license](https://spdx.org/licenses/), a recent history of activity or a current base of dependents, at least two maintainers, and your project is not associated with an individual user's profile, you will be immediately approved.
 
-Your project must be directly related to open source, not proprietary technology or any other topics.
+If you don’t fit the above requirements, we will consider your application on a case by case basis, using the following criteria:
 
-If there’s a codebase at the heart of your project, it should be under an open source license. (See above.)
+## Open source projects
+If there’s a codebase at the heart of your project, it should meet the crieria above. 
 
-Meetups or small event groups should have organized at least 2 events previously, and be able to show a history of activity online and offline. As further evidence, you agree to send photo/video documentation of your first event after joining Open Source Collective.
+## User groups 
+Should have at least 50 members and be able to demonstrate a genuine history of community activity (forum, events, publications, etc).
 
-Conferences and larger events may require specific risk assessment by our board. No expenses will be paid in advance of sufficient funds being available in the Collective budget (e.g. hiring a venue).
+## Meetups or small event groups 
+You should have organized at least 2 events previously, and be able to show a history of activity online and offline. As further evidence, you agree to send photo/video documentation of your first event after joining Open Source Collective.
 
-You understand that all agreements between your Collective and third parties, such as venues, contractors, speakers, etc, require explicit written permission and involvement of the OSC administrators. As fiscal sponsor, such agreements are legally between the third party and Open Source Collective.
+## Conferences and larger events 
+We may require specific risk assessment by our board. No expenses will be paid in advance of sufficient funds being available in the Collective budget (e.g. hiring a venue).All agreements between your Collective and third parties, such as venues, contractors, speakers, etc, require explicit written permission and involvement of the OSC administrators. As fiscal sponsor, such agreements are legally between the third party and Open Source Collective.