| 1 |
On Tue, Nov 27, 2018 at 12:49 PM Rich Freeman <rich0@g.o> wrote: |
| 2 |
> |
| 3 |
> On Tue, Nov 27, 2018 at 11:59 AM Matt Turner <mattst88@g.o> wrote: |
| 4 |
> > |
| 5 |
> > On Tue, Nov 27, 2018 at 7:41 AM Rich Freeman <rich0@g.o> wrote: |
| 6 |
> > > It makes sense to ensure that the solution actually solves the problem |
| 7 |
> > > before we simply implement it. |
| 8 |
> > > |
| 9 |
> > > If we really need such a file it would probably also make more sense |
| 10 |
> > > to have it auto-generated from git commit headers |
| 11 |
> > |
| 12 |
> > And how do you want to determine whether William's contributions are |
| 13 |
> > copyright Sony or now? Do you want to look up his timezone and check |
| 14 |
> > whether they were made during work hours? |
| 15 |
> |
| 16 |
> No, you look at the Copyright-owner header or whatever we want to call |
| 17 |
> it, and use that. Companies that care about labeling what they own |
| 18 |
> can take the time to properly document this. |
| 19 |
|
| 20 |
I would prefer not to see copyright noise to git commit messages. |
| 21 |
|
| 22 |
If a manually maintained file will suffice, please don't |
| 23 |
over-complicate matters. |
Archives