You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2019. It is now read-only.
thank you so much for the fine tutorial and example code.
Unfortunately I'm a more than a little concerned with the license text: "The examples provided by Facebook are for non-commercial testing and evaluation purposes only. Facebook reserves all rights not expressly granted.". (a8c9f89)
This means that using or substantially reproducing your examples and code in production will leave users in breach of copyright! Personally I strongly believe that the best license for tutorial example code is a dual CC0/public domain (where applicable) and a liberal license like BSD/MIT/APL, possibly LGPL (but for example code, I think "no strings attached" is more constructive).
I find it hard to believe that the intent is for people to have to work around reusing the knowledge presented in the repository when working with react?
Is there any chance the license could be changed? Then I wouldn't have to be afraid to recommend the article to people that work on production systems...
The text was updated successfully, but these errors were encountered:
Hi,
thank you so much for the fine tutorial and example code.
Unfortunately I'm a more than a little concerned with the license text: "The examples provided by Facebook are for non-commercial testing and evaluation purposes only. Facebook reserves all rights not expressly granted.". (a8c9f89)
This means that using or substantially reproducing your examples and code in production will leave users in breach of copyright! Personally I strongly believe that the best license for tutorial example code is a dual CC0/public domain (where applicable) and a liberal license like BSD/MIT/APL, possibly LGPL (but for example code, I think "no strings attached" is more constructive).
I find it hard to believe that the intent is for people to have to work around reusing the knowledge presented in the repository when working with react?
Is there any chance the license could be changed? Then I wouldn't have to be afraid to recommend the article to people that work on production systems...
The text was updated successfully, but these errors were encountered: