Meta tags:

Headings (most frequently used words):

license, and, process, for, has, appropriate, standing, steward, the, to, approval, review, search, form, purpose, of, how, submit, request, submission, types, supporting, data, decision, user, login, promote, protect, open, source, software, communities, retirement, legacy, licensees,

Text of the page (most frequently used words):
the (73), #license (50), and (31), open (22), for (21), source (18), #review (17), osi (16), licenses (15), that (13), software (12), approval (12), process (10), appropriate (9), approved (8), this (7), community (7), definition (7), discussion (7), will (7), ensure (7), org (6), which (6), any (6), freedom (6), has (6), request (6), have (6), board (6), decision (6), submission (6), proliferation (6), category (6), opensource (5), steward (5), through (5), new (5), list (5), questions (4), about (4), made (4), openid (4), you (4), must (4), submitted (4), existing (4), after (4), date (4), rationale (4), standing (4), public (4), type (4), standards (4), website (3), should (3), form (3), osd (3), initiative (3), login (3), provide (3), determines (3), but (3), days (3), version (3), previously (3), guidelines (3), below (3), only (3), legacy (3), been (3), identify (3), successor (3), legal (3), with (3), submit (3), requirement (3), please (2), contact (2), content (2), author (2), under (2), not (2), international (2), our (2), all (2), use (2), change (2), education (2), communities (2), password (2), log (2), using (2), mailing (2), submitter (2), asked (2), committee (2), chair (2), decisions (2), copy (2), report (2), require (2), reasons (2), duplicative (2), one (2), conforms (2), may (2), general (2), day (2), available (2), https (2), recommend (2), describe (2), history (2), already (2), used (2), retirement (2), supporting (2), data (2), name (2), formal (2), conform (2), help (2), articles (2), faq (2), code (2), conduct (2), affiliate (2), become (2), membership (2), logo (2), trademark (2), web (2), jul (2), hosting, generously, provided, see, regarding, contents, terms, service, digitalocean, licensed, reproduced, site, copyright, directed, creative, commons, attribution, sign, newsletter, grants, rights, study, share, modified, unmodified, essential, enabling, development, compliant, distributed, many, people, preventing, abuse, ideals, ethos, inherent, movement, champions, society, collaboration, infrastructure, stewarding, global, non, profit, practice, worked, raise, awareness, adoption, build, bridges, between, over, years, promote, protect, create, account, cancel, username, what, user, javascript, enabled, takes, place, participate, replying, claims, recommendations, updated, withhold, would, reworking, appears, willing, able, revise, constructively, reject, cannot, practically, remedied, adequately, guarantee, there, sufficient, consensus, emerging, from, rejected, substantive, problematic, nonsubstantive, example, poorly, drafted, significantly, more, approve, taking, into, consideration, guarantees, condition, requiring, changes, resubmitted, defer, another, cycle, conformance, remains, active, later, than, next, meeting, select, four, possible, normally, means, initially, revised, was, considered, follows, set, forth, while, try, best, adhere, strictly, circumstances, extend, further, adopted, aim, follow, when, reviewing, provides, nature, usage, retroactive, historic, extensively, licensees, specify, exactly, being, retired, retire, can, note, results, analysis, compare, contrast, most, similar, distinguish, clearly, state, completely, single, entity, types, email, include, link, earlier, discussions, listed, plaintext, subject, field, proper, tracking, aren, subscribe, identified, read, your, complies, how, thorough, transparent, timely, within, discourage, vanity, purpose, goal, labeled, norms, expectations, reason, described, happy, consult, entities, advance, them, navigate, improve, their, requires, going, join, sponsors, blog, books, case, business, bibliography, getting, resources, policy, communications, archives, disclaimer, forums, reports, licensing, lists, criteria, affiliates, member, osr, frequently, compliance, licence, authority, recognition, associations, volunteers, staff, conflict, interest, bylaws, elections, incorporation, organization, operations, minutes, search, home, skip, main, wayback, machine, http, archive, 20221130040445, timestamps, capture, fail, success, 2023, 2022, 2021, dec, nov, oct, 2007, 2026, 472, captures,

Text of the page (random words):
the license review process open source initiative 472 captures 07 jul 2007 14 jul 2026 oct nov dec 30 2021 2022 2023 success fail about this capture timestamps the wayback machine http web archive org web 20221130040445 https opensource org approval skip to main content home contact login search form open source initiative about board minutes organization operations articles of incorporation board elections bylaws conflict of interest volunteers staff associations history international authority recognition trademark logo trademark guidelines logo guidelines licenses open source definition licenses by category licenses by name license review process licence proliferation lp report to the board open standards the open standards requirement open standards requirement compliance open standards requirement rationale osr frequently asked questions membership become an osi member membership faq affiliates become an affiliate affiliate criteria mailing lists licensing code of conduct general code of conduct discussion list reports disclaimer for osi public forums policy on public communications and archives resources getting help bibliography open source case for business faq open source education articles books blog sponsors join the license review process the goal of the osi license review process is to ensure that licenses and software labeled as open source conform to existing community norms and expectations for that reason all licenses must go through a public review process described below the osi board is happy to consult with entities in advance to help them navigate the process and improve their license but formal approval requires going through license review purpose of the process ensure approved licenses conform to the open source definition and provide software freedom identify appropriate license proliferation category discourage vanity and duplicative licenses ensure a thorough transparent and timely review e g within 60 days how to submit a request read the open source definition and ensure that your license complies with it identify the type of submission retirement legacy approval or approval ensure you have appropriate standing to submit the type of submission that you have identified subscribe to license review if you aren t already submit a formal request to license review the request email must include the submission type and license name in subject field to ensure proper tracking a plaintext copy of the license the supporting data listed below as appropriate for the type of submission a link to earlier public discussions if any submission types and supporting data for approval has appropriate standing license steward approval of completely new licenses or licenses previously used by only a single entity rationale clearly state rationale for a new license distinguish compare to and contrast with the most similar osi approved license s legal review describe any legal review the license has been through and provide results of any legal analysis if available proliferation category recommend which license proliferation category is appropriate for retirement has appropriate standing license steward a request to retire the license this request can only be made by the license steward note that successor licenses must be approved through the new license approval process version specify exactly which version is being retired successor identify successor license s if any for legacy approval has appropriate standing license steward and licensees retroactive approval of historic legacy licenses that have already been extensively used by an existing community but have not previously been approved rationale describe the nature and history of the existing usage proliferation category recommend which license proliferation category is appropriate decision process the osi has adopted the guidelines below which we aim to follow when reviewing licenses to ensure that a license will be approved only if it conforms to the open source definition and provides software freedom decision date for a license normally means a 60 days after a license is initially submitted to the license review list for review and b 30 days after submission of a revised version of a license that was previously submitted for review a license is considered to be submitted for review if it follows the process set forth at https opensource org approval while we will try our best to adhere strictly to this 60 30 day decision date definition circumstances may require us to extend the decision date further no later than the next available board meeting after the decision date the osi will select one of four possible decisions defer for another 30 day discussion cycle if community discussion of conformance of the license to the osd remains active approve if after taking into consideration community discussion the osi determines that the license conforms to the open source definition and guarantees software freedom a license may be approved on the condition that a change be made but in general a license requiring changes will have to be resubmitted reject if a the osi determines that the license cannot practically be remedied to adequately guarantee software freedom or b there is sufficient consensus emerging from community discussion that the license should be rejected for substantive reasons or c the license is problematic for nonsubstantive reasons for example it is poorly drafted or significantly duplicative of one or more existing osi approved licenses withhold approval if a the osi determines that approval would require reworking the license and b the license submitter appears willing and able to revise the license constructively community discussion of submitted licenses takes place on the license review mailing list the submitter should participate in this discussion by replying to any questions asked or claims made about the license the license committee chair will provide recommendations for decisions to the osi board and copy the license review list the license committee chair will report the decision to the list if a license is approved the osi website will be updated as appropriate you must have javascript enabled to use this form user login log in using openid what is openid username password log in using openid cancel openid login create new account request new password to promote and protect open source software and communities for over 20 years the open source initiative osi has worked to raise awareness and adoption of open source software and build bridges between open source communities of practice as a global non profit the osi champions software freedom in society through education collaboration and infrastructure stewarding the open source definition osd and preventing abuse of the ideals and ethos inherent to the open source movement open source software is made by many people and distributed under an osd compliant license which grants all the rights to use study change and share the software in modified and unmodified form software freedom is essential to enabling community development of open source software sign up for our newsletter the content on this website of which opensource org is the author is licensed under a creative commons attribution 4 0 international license opensource org is not the author of any of the licenses reproduced on this site questions about the copyright in a license should be directed to the license steward hosting for opensource org is generously provided by digitalocean please see terms of service for questions regarding the osi website and contents please contact us