[Jclouds Wiki] Trivial Update of "1.6.1 Incubating Release Issues" by IgnasiBarrera

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jclouds Wiki" for change notification.

The "1.6.1 Incubating Release Issues" page has been changed by IgnasiBarrera:
https://wiki.apache.org/jclouds/1.6.1%20Incubating%20Release%20Issues?action=diff&rev1=4&rev2=5

  == jclouds-chef issues ==
   * Obsolete resources/NOTICE.txt and resources/LICENSE.txt, should be removed
   * Test resource JSON files - do we need them to end up in NOTICE, if they can't be changed to ASF headers?
-   * ''[nacx] Those json files do not have the license headers, because they are in the src/test/resources package and are only intended to be used as test expectation data. This was already discussed  [[here|http://markmail.org/message/pg2hxols62sfas3z]] and the conclusion was that the licensing creativity clause justified this. Should we change something then?''
+   * ''[nacx] Those json files do not have the license headers, because they are in the src/test/resources package and are only intended to be used as test expectation data. This was already discussed  [[http://markmail.org/message/pg2hxols62sfas3z|here]] and the conclusion was that the licensing creativity clause justified this. Should we change something then?''
    * ''[nacx] It is not the file itself what is copyrighted. Those files contain the json representation (the body of a  Chef REST API response) of a cookbook. So the cookbook itself has a license, and if you download the cookbook from the Opscode Community site, then you have to respect it; but those json files are just the body of a REST response, which includes the metadata of the cookbook (and its licensing information too); but it is just the Api response in json format; nothing we are re-distributing or similar.''
  
  == jclouds-karaf issues ==