4 ms·
The OP explicitly said that he worked on it during personal non work time, and further more has evidence (git logs) to prove it. Whether his former employer has
by tankenmate 13y ago
The OP explicitly said that he worked on it during personal non work time, and further more has evidence (git logs) to prove it. Whether his former employer has any evidence (either way) apart from the existence of the project on github obviously hasn't been stated.
- Xylakant 13y agoSorry, but git logs prove nothing. Git allows rebase and modification of commits. Even a full log of when pushes to github happened prove nothing - I can work during the day and just commit later.
- nsxwolf 13y agoSo neither party can prove anything either way. This is precisely why we should never presume guilt.
- Xylakant 13y agoThe crowd here seems to presume guilt on the side of the employer.
- phaemon 13y agoIt's a little unclear what you mean by "modify", so just to be clear here: you can't alter an existing commit. You can certainly fake any timestamp you want to start with, or you can create a new set of commits with a different timestamp (which is what rebase does), but you can't change an existing commit - the hash would be wrong.
- Xylakant 13y ago>but you can't change an existing commit - the hash would be wrong. True - however as long as nobody ever saw that commit, nobody will know. So the only way a git log could ever constitute a proof would be that you immediately push to a tamper-proof audit system right after your commit.
- briantakita 13y agoIsn't the onus of proof on the company in this case? How can the company prove that he worked on the open source project on their time?
- kibibu 13y agoGit logs are pretty flimsy sort of evidence though. You can work all day and commit at midnight.
- __david__ 13y agoOr just "git commit --date='2014-04-14T20:00'"