Let me tell you one thing. Definitely, and please, please don't modify the license that you apply to your software. For example:
The GPLv3, is copyrighted itself (emphasis is mine):
Copyright © 2007 Free Software Foundation, Inc. http://fsf.org/
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
You'll run into many problems by changing the legal code of a license.
In terms of making a note of your company (or even yourself) in the project, there are a few ways you can do this:
Edit the project's source code:
All you need to do is really put a few "commented" lines like so, likely at the top of the file:
// Haha! This source code file has been viciously made to make a reference to my
// company! This is lovely for [insert-company-name-here]
Alright, maybe not exactly like that... but you get the point.
Add a section in a "
It is common for many projects to include a
readme file, with details such as installation instructions, notes, known issues... It makes sense to put some details here. The
readme file normally receives tons of traffic: people view it from within your repository, and even if they have the source code on their computer.
Overactor has also raised a good point: Using a FLOSS license would mean that others would be able to modify the files of the project that you make available themselves, when it is in their personal hands.
One problem I see here is that redistributors are not obligated to keep this notice in there.
For a solution...
You could specify something to make sure that the license does not apply to these notices or separate files. As far as I can remember, this is allowed (I may be wrong), but I will find a source to back that up. Yar, I can't remember...
Forget all that -> It's non-sense.
Thanks to Bart Van Ingen Schenau, the Apache 2.0 license has a clause requiring a NOTICE file to be kept within the project. The relevant clause is 4d):
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
Therefore, you can acknowledge your employer in the NOTICE file, and it will pass on to its derivatives.