<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Odoo/addons/web_unsplash/__manifest__.py, branch 14.0</title>
<subtitle>The current checkout of upstream Odoo</subtitle>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/'/>
<entry>
<title>[IMP] * : manifest module categories cleanup</title>
<updated>2019-09-25T14:03:45+00:00</updated>
<author>
<name>Victor Feyens</name>
<email>vfe@odoo.com</email>
</author>
<published>2019-08-20T16:26:19+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=07631a51858830cf9dd7f06e9c3ac2576efa559b'/>
<id>07631a51858830cf9dd7f06e9c3ac2576efa559b</id>
<content type='text'>
closes odoo/odoo#35754

Signed-off-by: Damien Bouvy (dbo) &lt;dbo@odoo.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
closes odoo/odoo#35754

Signed-off-by: Damien Bouvy (dbo) &lt;dbo@odoo.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] web_unsplash: don't expose client_id in network</title>
<updated>2018-11-23T14:51:07+00:00</updated>
<author>
<name>Romain Derie</name>
<email>rde@odoo.com</email>
</author>
<published>2018-11-19T14:36:31+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=8b1a05d9e09dca317ca38422d75f459a7e1784aa'/>
<id>8b1a05d9e09dca317ca38422d75f459a7e1784aa</id>
<content type='text'>
Unsplash CEO asked us to stop exposing our key client side (even if it was
only in the browser network and previously allowed by their API team leader).

After multiple exchange, it has been negociated that:
1. Our non saas user won't be able to apply for a production key and should
   prefix they Unsplash application name by 'Odoo:'. Their key will remain in
   test mode.
   Indeed, Unsplash won't be able to review every Odoo application and ensure
   it respects the API terms and it is a real application.
2. Our saas user will query Unsplash with a dedicated enterprise key
3. The documentation should explain it all

Task-1911345</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Unsplash CEO asked us to stop exposing our key client side (even if it was
only in the browser network and previously allowed by their API team leader).

After multiple exchange, it has been negociated that:
1. Our non saas user won't be able to apply for a production key and should
   prefix they Unsplash application name by 'Odoo:'. Their key will remain in
   test mode.
   Indeed, Unsplash won't be able to review every Odoo application and ensure
   it respects the API terms and it is a real application.
2. Our saas user will query Unsplash with a dedicated enterprise key
3. The documentation should explain it all

Task-1911345</pre>
</div>
</content>
</entry>
<entry>
<title>[ADD] web_unsplash: Find free high-resolution images from Unsplash</title>
<updated>2018-08-13T18:38:38+00:00</updated>
<author>
<name>Romain Derie</name>
<email>rde@odoo.com</email>
</author>
<published>2018-08-13T17:27:47+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=732702d5e2a007797e589dc42b29f31a9e27c54f'/>
<id>732702d5e2a007797e589dc42b29f31a9e27c54f</id>
<content type='text'>
Move module from enterprise to community

Work of @dep-odoo and @rdeodoo
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Move module from enterprise to community

Work of @dep-odoo and @rdeodoo
</pre>
</div>
</content>
</entry>
</feed>
