4 ms·
The intent is good and I hope we find a good way to implement this. I do see pitfalls though: I would separate ownership (i.e., one cannot patent the code deve
by ptero 9y ago
The intent is good and I hope we find a good way to implement this.
I do see pitfalls though: I would separate ownership (i.e., one cannot patent the code developed with public money -- IMO a good idea) and visibility (showing the code on request -- IMO a very dangerous one).
My big concern is formalizing things that should be left informal. For example, in applied research, we usually build a number of throwaway prototypes before the real system. Those quick prototypes and proofs of concept are often ugly in many ways. If I have to expose those to the world I have to smooth sharp edges (HR -- "we cannot get this outside"), which means instead of building 10 throwaways I can only build 2-3.
- jack9 9y ago> in applied research, we usually build a number of throwaway prototypes before the real system. Those quick prototypes and proofs of concept are often ugly in many ways. So basically you just do normal development? In the commercial world, one of those prototypes usually becomes the production code.
- kilotaras 9y ago> one cannot patent the code developed with public money Code can't be patented in EU anyway.