copyright licensing
What are the best practices revolving around forking and redistrubuting an apache 2.0 licensed repo?
<p>I forked a repo on github and made a few changes to some existing files, I wanted to know whats the &quot;suggested&quot; format/way i make changes to the copyright? The license says i need to add a notice to files i change, but i would like to know what exactly do i change (with examples would help).</p>
<p>Also do i need to add the same license header to new files i add to this project? and is there anything else i need to be aware of?</p>

<p>Presumably you are referring to this clause:</p>
<blockquote>
<p>You must cause any modified files to carry prominent notices stating that You changed the files;</p>
</blockquote>
<p>There is no magic legal incantation here. Just add a line in the header comment saying something like</p>
<blockquote>
<p>Modified from release 1.2.3 by Deadly (deadly@wibble.com).</p>
</blockquote>
<p>Having said that, if you are planning to submit a pull request to the original project then don't bother because you will just put the maintainer to the trouble of chopping out your header. You aren't trying to pass off your own work as something official from the project, which is what this is really about.</p>
