fsnotify contains code from https://github.com/golang/exp
Previously there was plans to incorporate fsnotify into the standard library and use it for tools such as the go command and godoc. #1
The LICENSE and CLA requirement in CONTRIBUTING are based on this.
However, I haven't been enforcing the CLA requirement on recent pull requests. A tool like CLAHub would help but its future is unknown. More importantly, I don't think fsnotify belongs in the standard library any longer. Using an internal/ package would allow the go command to use fsnotify (or an alternative) without exposing an API that must be locked down.
So I think it's time to make fsnotify its own project:
- The license is currently the same three clause BSD as Go with mention of Google. This could be changed to a simplified BSD license (2 clause).
- The license should continue to have the copyright to fsnotify authors.
- The header comments on .go files could be updated to fsnotify authors or simply removed.
- There should still a mention somewhere that fsnotify is derived from code that is
Copyright (c) 2012 The Go Authors. All rights reserved.
- The CLA requirement could be dropped.
/cc @rsc
fsnotify contains code from https://github.com/golang/exp
Previously there was plans to incorporate fsnotify into the standard library and use it for tools such as the go command and godoc. #1
The LICENSE and CLA requirement in CONTRIBUTING are based on this.
However, I haven't been enforcing the CLA requirement on recent pull requests. A tool like CLAHub would help but its future is unknown. More importantly, I don't think fsnotify belongs in the standard library any longer. Using an
internal/package would allow thegocommand to use fsnotify (or an alternative) without exposing an API that must be locked down.So I think it's time to make fsnotify its own project:
Copyright (c) 2012 The Go Authors. All rights reserved./cc @rsc