42 lines
2.3 KiB
HTML
42 lines
2.3 KiB
HTML
{% extends "base_conservancy.html" %}
|
||
|
||
{% block head %}
|
||
<style>
|
||
#subhed {
|
||
margin-top: -0.8em;
|
||
font-style: italic;
|
||
}
|
||
</style>
|
||
{% endblock %}
|
||
|
||
{% block content %}
|
||
<h1>ContractPatch</h1>
|
||
|
||
<div id="subhed">Everything is negotiable</div>
|
||
|
||
<div id="contractpatch-intro" class="section">
|
||
<h2>What is ContractPatch?</h2>
|
||
|
||
<p style="clear: both;">Many free and open source software developers sign employment agreements with their employers. These agreements can affect whether and how developers contribute to FOSS—whether it’s done as part of their employment, after hours, or both. ContractPatch is Conservancy’s initiative to give developers the words they need to make sure they can continue to do the work that’s important to them and our community. Whether those words are negotiation tactics for the hiring process, or language to suggest for a prospective employment agreement, ContractPatch helps developers defend their own interests.</p>
|
||
|
||
<p>In the coming months, we’ll write about legal and strategic points in contract negotiation strategies, pre-negotiation prep and practice, methods for negotiating, and general information on your legal rights around contracts. We’ll also look at specific contract provisions—especially those that impact tech workers the most, such as non-compete agreements and intellectual property assignment clauses. This will all go hand-in-hand with a Git repository with forkable sample language for key contract provisions, such as payment terms, benefits, non-competition and non-solicitation agreements, and intellectual property assignment clauses.</p>
|
||
</div>
|
||
|
||
<div id="contractpatch-follow" class="section">
|
||
<h2>Follow ContractPatch</h2>
|
||
|
||
<p><a href="https://lists.sfconservancy.org/mailman/listinfo/contractpatch">Subscribe to our discussion mailing list.</a> This is a great place to talk about issues in employment agreements, and suggest what ContractPatch might tackle next.</p>
|
||
|
||
<p><a href="https://twitter.com/ContractPatch">Follow ContractPatch on Twitter.</a></p>
|
||
</div>
|
||
|
||
<div id="contractpatch-blog" class="section">
|
||
<h2>Blog posts</h2>
|
||
|
||
{% for entry in blog_entries %}
|
||
{% include "blog/entry_partial.html" with entry=entry only %}
|
||
{% endfor %}
|
||
|
||
<p><span class="continued"><a href="/blog/?tag=ContractPatch">Read all ContractPatch blog posts…</a></span></p>
|
||
</div>
|
||
{% endblock %}
|