Contributing - Balanced Employee IP Agreement (GitHub)
The Balanced Employee IP Agreement (BEIPA) is an open-source template designed to address intellectual property ownership between employers and employees. It provides a framework for managing IP created during employment, aiming for a fair and balanced approach that can be adapted for various jurisdictions.
Contributing
Hi there! We're thrilled that you'd like to contribute to the Balanced Employee IP Agreement (BEIPA). Your help is essential. Our README describes the project, its purpose, and caveats, and is necessary reading for contributors.
Contributions to this project are released to the public domain under CC0-1.0.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Help wanted
Browse open issues to see current requests. We also generally want to hear about:
Legal issues with BEIPA (e.g., how it works in different jurisdictions)
Typos
Clearer wording
Companies using BEIPA
Translations
Other employee IP agreements that have been open sourced
Open an issue to tell us about any of the above. You may also open a pull request to propose specific changes, but it's always OK to start with an issue.
Substantive questions about and suggestions for BEIPA are welcome. We'll try to acknowledge them promptly, but may take a long time to respond on the substance, if we can. GitHub uses a version of the agreement, so our communication about it and direction for its development must be carefully considered. Also, remember that such communication is not legal advice and comes without warranty.
Versioning
BEIPA applies MAJOR.MINOR.PATCH semantic versioning to its domain as follows:
MAJOR version when objectives of agreement change. A company using BEIPA would have to fully evaluate a new major version to determine fit.
MINOR version when agreement changes do not change objectives of agreement but are substantial enough to merit legal scrutiny from any user.
PATCH version for corrections which any user would likely want to accept with minimal additional review.
Any change to the agreement text mandates a new version. Before merging any change to the agreement to main, a maintainer will:
Have changes reviewed by GitHub Legal.
Update version number in the agreement title/heading and commit to branch to be merged.
Merge branch with new version.
Tag and push: git tag vx.x.x; git push --tags
Create docx, odt, and pdf copies of the agreement:
pandoc -f commonmark+smart Balanced_Employee_IP_Agreement.md -o Balanced_Employee_IP_Agreement.docx pandoc -f commonmark+smart Balanced_Employee_IP_Agreement.md -o Balanced_Employee_IP_Agreement.odt pandoc --pdf-engine=xelatex -f commonmark+smart Balanced_Employee_IP_Agreement.md -o Balanced_Employee_IP_Agreement.pdf
Make a release from the tag created above, adding the docx, odt, and pdf copies as binary attachments.
https://github.com/github/balanced-employee-ip-agreement/releases/latest will show the release just made.
This process may become more involved if and when required by translations, support for additional jurisdictions, or desire to have old versions available in source tree, rather than only in history. At this time it is not necessary to design these procedures before they are needed.
Resources
5.0 out of 5 on Google
Read reviewsAs seen in
Frequently asked questions
A template isn't binding on its own - like any contract, it becomes binding once it's properly completed and signed. Templates in our curated library are professionally drafted for US or UK law; review any template before you sign it.
Yes. Chat with GitLaw to edit any section, or make changes directly in the editor.
Yes, read about team plans here.
Describe what you need in the chat and GitLaw will draft it for you.
Templates in our curated library are professionally drafted for US or UK law. The wider library comes from the GitLaw community and public sources - a solid starting point, but check any template fits your situation before you rely on it.
Mostly US and UK law. Some templates use general commercial terms that work across jurisdictions, and many note which law they're written for.
It depends on the situation. Templates work well for routine business agreements. For anything involving significant money, complex IP, employment, or areas you're unsure about, it's worth getting professional advice before you sign. GitLaw provides templates and tools, not legal advice.
Open any template in GitLaw and describe the change you want in the chat — 'make clause 4 mutual' or 'add a 30-day notice period', for example. GitLaw drafts the revised language and shows it as a suggested edit. You accept, reject, or keep editing from there.
Yes. Upload a Word, PDF, or Markdown file and GitLaw will open it in the editor. You can review, edit, or chat with GitLaw about it the same way you would with any template from the library.
Trusted by 5,000+ businesses
From template to signed, in one place
Every template opens in an editor with an AI agent alongside it.
Open
Pick a template and open it. Nothing to download, and no credit card to start.
Free to open
Edit with AI
Describe your situation in chat and the agent adapts the wording, clause by clause.
Tracked changes you can review
Send and sign
Share it for negotiation, then collect signatures without leaving GitLaw.
eSign included
Built for your legal work,
with practicing lawyers
Trained on 5,500+ clauses and specialist areas of law. Built with a standards committee of independent lawyers.
As seen in
Ready to get started?
No sales calls, no credit card. Just chat with GitLaw.
GitLaw provides templates and tools, not legal advice. Templates are a starting point, not a substitute for advice on your situation - for anything significant, speak to a qualified lawyer.