<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kodo Kojo on Medium]]></title>
        <description><![CDATA[Stories by Kodo Kojo on Medium]]></description>
        <link>https://medium.com/@kodokojo?source=rss-15cac062e657------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*hDyFXdsn3WN0G8DL.png</url>
            <title>Stories by Kodo Kojo on Medium</title>
            <link>https://medium.com/@kodokojo?source=rss-15cac062e657------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:50:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kodokojo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[About Kodo Kojo SaaS plateform]]></title>
            <link>https://medium.com/@kodokojo/about-kodo-kojo-saas-plateform-7b0b24f29358?source=rss-15cac062e657------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b0b24f29358</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Kodo Kojo]]></dc:creator>
            <pubDate>Mon, 06 Feb 2017 10:28:38 GMT</pubDate>
            <atom:updated>2017-02-06T13:14:25.417Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi,</p><p>As we already discussed in a previous post, our SaaS platform was a successful experiment. So successful that it was challenging to welcome all of you. After some thoughts about the best way to provide Kodo Kojo for every one, we decided not to develop our SaaS offer for now. As a result, we had to discontinue the SaaS sandbox on <a href="http://my.kodokojo.io/">my.kodokojo.io</a>. If you have data you want to retrieve, please contact us on help[at]<a href="http://kodokojo.io/">kodokojo.io</a>.</p><p>We have moved in a new direction: we will increase our efforts to improve Kodo Kojo and to provide tools that make it easier to deploy on your own platform. It is not a small task and we will not address every use case at once, but it seems to us that it is the right path to provide a suitable tool for users.</p><p>As always, we are very open to all discussions about it.<br>If you prefer face-to-face meetings, you have two possibilities:</p><ul><li><a href="https://www.meetup.com/fr-FR/Paris-Hackergarten/">The Hackergarten Paris</a> meetup where we are always at (as mentor or contributors).</li><li>The next stop of our community tour at the <a href="http://www.lyonjug.org/evenements/kodokojo">LyonJUG, on 15 February</a>.</li></ul><p>Thanks for your support and see you soon.</p><p>—</p><p>The Kodo Kojo Team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b0b24f29358" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kodo Kojo at the BreizhJUG]]></title>
            <link>https://medium.com/@kodokojo/kodo-kojo-at-the-breizhjug-dfe22894ee15?source=rss-15cac062e657------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfe22894ee15</guid>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[breizhjug]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Kodo Kojo]]></dc:creator>
            <pubDate>Fri, 09 Dec 2016 11:35:25 GMT</pubDate>
            <atom:updated>2016-12-09T11:35:25.900Z</atom:updated>
            <content:encoded><![CDATA[<p>On December 1rst, we were at the <a href="http://www.breizhjug.org/#/home">BreizhJUG</a> to talk about Docker in our development workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rAYH-47krpMxkL0gJomFgA.jpeg" /><figcaption><a href="https://medium.com/u/a451b090daf7">Antoine Le Taxin</a> and <a href="https://medium.com/u/3ad6be16e7bc">Jean-Pascal Thiery</a> on stage.</figcaption></figure><p>During the train journey we finished working on our talk and practiced the art of coding without Wi-Fi, thanks to Docker containers that can run all our tools locally as this tweet proves it! (ok… you can’t see much)</p><h3>Jean-Pascal Thiery on Twitter</h3><p>Continuer à coder avec son Redis et Rabbitmq dans le train grâce à Docker. Nous vous expliquerons comment ce soir au @breizhjug !</p><p>Welcomed by the <a href="http://www.istic.univ-rennes1.fr/">ISTIC</a> of Rennes, we took place in a large lecture theatre. We had the chance to be the firsts to test the video capture system for the <a href="http://www.breizhcamp.org/">next BreizhCamp</a>.</p><h3>Nicolas De loof on Twitter</h3><p>The @breizhcamp technical staff preparing session recording</p><p>Jean-Pascal got a very efficient lapel microphone and Antoine tried to speak loud enough for you to hear what he says when watching the video. Thanks to the BreizhJUG for sharing! Talking here reminded us that it was after a BreizhCamp that the idea of what is called Kodo Kojo now took root.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSHxH2O1Az0I%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSHxH2O1Az0I&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FSHxH2O1Az0I%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e5d88b2fbec22e1873361f851d09b028/href">https://medium.com/media/e5d88b2fbec22e1873361f851d09b028/href</a></iframe><p>The audience was attentive, the organizers were very friendly, it all went very well. Kodo Kojo yielded interest and questions, that’s great!</p><p>We could not leave without eating some “galettes”, Breton specialities. So we finished the evening in a “crêperie” which is like a second headquarter for some of the meetup organizers.</p><p>This was a great meetup and we were very kindly welcomed, thanks for all <a href="https://twitter.com/breizhjug">@breizJUG!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfe22894ee15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feed-back, two weeks after]]></title>
            <link>https://medium.com/@kodokojo/feed-back-two-weeks-after-1ae8e0654622?source=rss-15cac062e657------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ae8e0654622</guid>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[kodo-kojo]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Kodo Kojo]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 18:03:12 GMT</pubDate>
            <atom:updated>2016-11-19T10:20:52.450Z</atom:updated>
            <content:encoded><![CDATA[<p>(French version below | version française plus bas)</p><p><strong>Hi and thank you all!</strong></p><p>Thanks to the many of you who tested our SaaS platform once we opened it last November 7th. We can’t wait to know what you thought about it.</p><p>But we didn’t anticipate such a keen interest and, as XebiCon attendees already know, we have been ‘victims’ of our own success. The projected size of our SaaS infrastructure has been filled in a two day period. Many of you had not been able to create their factory or had encountered problems (some parts of the stack staying in “starting” state for example). If you are in this case, <a href="/service/mailto:help@kodokojo.io">please let us know</a>. We reacted very quickly by adding more space… But it has not been enough!</p><p>So we have been thinking of a longer term strategy that ensures that you can test Kodo Kojo in good conditions. It has been very clear that we could not let our infrastructure grow indefinitely and incur the costs on our own. On the other hand, we really wanted everyone to be able to test without having to commit. Ultimately, we are not losing sight of our priority: improving and developing our Open Source solution. <strong>For that, we definitely need you!</strong></p><p>Here is what we have decided to do:</p><ul><li>We have closed, for now, the possibility of creating new accounts from the platform (you will still be able to add new members to your project).</li><li>We have created a <a href="https://my.kodokojo.io/">waiting list you can sign on to</a> (sorry for those who have already registered for the newsletter, you will have to do it again on this specific form), so you will be contacted as soon as free space is available.</li><li>You will have the opportunity to use Kodo Kojo for free for a duration of 15 days (if you already have an account, the period will start when you receive a personal communication).</li><li>During that time, you will have the <a href="/service/mailto:contact@kodokojo.io">possibility to contact us</a> if you wish to go further than a simple test and continue using Kodo Kojo after this period.</li><li>If you wish to go further with Kodo Kojo, it will remain free of charge until 31 December 2016, without any subsequent commitment or need for any bank details.</li><li>Otherwise, your account will be suspended but all your data will be securely stored in order to reopen it easily if needed (unless you request it explicitly).</li><li>In any case, we will get in touch with each of you personally in order to collect your precious feed-back. This data is vital for us as it will enable us to improve Kodo Kojo.</li><li>Last but not least, we are about to start working on the launch of the platform to a wider audience in the best possible conditions. This will incur a cost (yet to be defined) which will enable us to continue offering the service.</li></ul><p>Any ideas, remarks, special requests? Contact us at <a href="/service/mailto:contact@kodokojo.io">contact@kodokojo.io</a>. We are, above all, creators and maintainers of an Open Source project and we are committed to direct and transparent communication, so don’t hesitate!</p><p>We continue our community tour at the <a href="http://www.breizhjug.org/"><strong>BreizhJUG</strong>, <strong>December 1st</strong></a>, come and meet us if you are in the area :)</p><p>Cheers and see you soon for more!<br> — <br> The Kodo Kojo Team</p><p><strong>Bonjour et surtout merci !</strong></p><p>Merci d’avoir été aussi nombreux à tester notre plateforme SaaS dès son ouverture le 7 novembre dernier. Nous espérons que ce premier aperçu vous a plu et nous trépignons d’impatience de savoir ce que vous en avez pensé.</p><p>Cependant nous n’avions pas prévu un tel engouement et, comme ceux qui sont venus à la XebiCon le savent déjà, nous avons été victimes de notre succès. L’espace prévu pour notre infrastructure SaaS a tout simplement été rempli en deux jours. Nombre d’entre vous n’ont pas pu créer leur usine ou ont rencontré des problèmes (certaines briques restant à l’état “starting” par exemple). Si vous êtes dans ce cas, <a href="/service/mailto:help@kodokojo.io">faites le nous savoir</a>. Nous avons réagi très vite en ajoutant de la place … Mais cela n’a pas suffi !</p><p>Nous avons donc réfléchi à une stratégie à plus long terme, pour vous permettre de tester Kodo Kojo dans de bonnes conditions. Il a très vite été clair que nous ne pouvions pas faire grossir notre infrastructure à l’infini et en assumer seuls les coûts. D’un autre côté, nous voulons absolument permettre à chacun de tester sans pour autant devoir s’engager de quelque manière que ce soit. Enfin, nous ne perdons pas de vue notre priorité : améliorer et faire évoluer notre solution Open Source. Pour cela, <strong>nous avons besoin de vous !</strong></p><p>Voici donc ce que nous avons décidé de faire :</p><ul><li>Fermer, pour le moment, la possibilité de créer automatiquement un nouveau compte depuis la plateforme (mais vous pourrez toujours ajouter de nouveaux membres à votre projet).</li><li>Vous permettre de <a href="https://my.kodokojo.io/">vous inscrire sur une liste d’attente</a> (désolé pour ceux qui sont déjà inscrits à la newsletter, mais il va falloir vous inscrire à nouveau) pour être contacté dès qu’une place est disponible.</li><li>Vous pourrez utiliser Kodo Kojo gratuitement pendant 15 jours (si vous avez déjà un compte, la période débutera à partir de la date d’envoi d’une communication individuelle).</li><li>Pendant cette durée, vous aurez la <a href="/service/mailto:contact@kodokojo.io">possibilité de nous contacter</a> si vous souhaitez aller plus loin que le simple test et continuer à utiliser Kodo Kojo au-delà de cette période.</li><li>Si vous en avez émis le souhait, l’utilisation de Kodo Kojo restera gratuite jusqu’au 31 décembre 2016, sans engagement et sans compte bancaire.</li><li>Sinon, votre compte sera suspendu, mais toutes les données seront conservées afin de permettre une réouverture facile le cas échéant, sans aucune perte (sauf demande contraire explicite).</li><li>Dans tous les cas, nous vous contacterons individuellement pour recueillir vos précieux retours d’expérience. Ces informations sont vitales pour nous et nous permettrons d’améliorer Kodo Kojo.</li><li>Et enfin, nous commençons dès aujourd’hui à travailler sur l’ouverture prochaine de notre plateforme à tous et dans de bonnes conditions, moyennant un coût qui nous permette de continuer à proposer ce service.</li></ul><p>Vous avez des idées, des remarques, une demande particulière ? Contactez-nous sur <a href="/service/mailto:contact@kodokojo.io">contact@kodokojo.io</a>, nous sommes avant tout créateurs et mainteneurs d’un projet Open Source et nous privilégions toujours l’échange direct et transparent, alors n’hésitez pas !</p><p>Nous continuons notre tournée de la communauté part le <a href="http://www.breizhjug.org/"><strong>BreizhJUG le 1er décembre</strong></a>, si vous êtes dans le coin, venez nous rencontrer :)</p><p>À très bientôt pour la suite !<br> — <br>L’équipe Kodo Kojo</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ae8e0654622" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kodo Kojo is opening its SaaS platform!]]></title>
            <link>https://medium.com/@kodokojo/kodo-kojo-is-opening-its-saas-platform-3f02f3112bf?source=rss-15cac062e657------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f02f3112bf</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[kodo-kojo]]></category>
            <dc:creator><![CDATA[Kodo Kojo]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 10:21:19 GMT</pubDate>
            <atom:updated>2016-11-18T10:21:19.325Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Hi all,</strong></p><p>Today is a very special day for us and — more significantly — for you.<br> You haven’t heard from us since we announced the Kodo Kojo became open source. There is a very good reason for that: we were really busy on <strong>three major releases</strong>.</p><p>First of all, Kodo Kojo is now mature enough to be <strong>released in version 1.0.0</strong>. That is a first move in order for the project to gain exposure to the real world.</p><p>Secondly, we are very proud and excited to announce that <strong>Kodo Kojo is opening its SaaS platform!</strong> We explained what Kodo Kojo can achieve (a three-click software factory), we did numerous demos and we demonstrated how fast it is to have your factory up and running. Now we want you to experience it!</p><p><a href="https://my.kodokojo.io/"><strong>Try it now</strong></a>. Open your account on kodokojo.io. Your sources will be safe and secured: Factories are isolated and unreachable by non authorised users; Contents are stored on a GlusterFS cluster and duplicated through 3 Amazon Availability Zones.</p><p>Finally, we have released <strong>a brand new landing page</strong>. It respects our style guide and centralizes important information, explaining how you can contribute and how you can get in touch with us. To start with Kodo Kojo, there is now <strong>one unique entry point: </strong><a href="https://kodokojo.io/"><strong>kodokojo.io</strong></a>.</p><p>For the next steps, as it’s important for us to give you visibility and to get your feedback, we published an overview of the <a href="https://trello.com/b/3xNdZBXq/kodo-kojo-public-roadmap">Kodo Kojo forecast roadmap</a> on Trello. <a href="https://trello.com/b/3xNdZBXq/kodo-kojo-public-roadmap">We are eagerly waiting for your votes on it</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f02f3112bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We are OpenSource]]></title>
            <link>https://medium.com/@kodokojo/we-are-opensource-ce47eb6a7f2a?source=rss-15cac062e657------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce47eb6a7f2a</guid>
            <category><![CDATA[kodo-kojo]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Kodo Kojo]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 10:18:06 GMT</pubDate>
            <atom:updated>2016-11-18T10:18:06.350Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Hi Kodo Kojo fans!</strong></p><p>Today, we are overjoyed as Kodo Kojo has reached a major milestone in its short (but promising) history: <strong>Today, the project becomes truly OpenSource!</strong> Here are the sources:<br><a href="https://github.com/kodokojo"><strong>https://github.com/kodokojo</strong></a><br><a href="https://gitter.im/kodokojo/kodokojo"><strong>https://gitter.im/kodokojo/kodokojo</strong></a></p><p>The team worked hard to unlock this achievement, so we are proud to present our code to the community and share our experience with you. We can’t wait to see you using Kodo Kojo and we are also eager to receive our first Pull Requests, and discover in which direction you will take this initiative. We do not pretend to be perfect, and we are willing to listen to every kind of feedback in order to make Kodo Kojo a better project. We are really impatient to hear from you.</p><p>Hope you will like what you will discover!</p><p>The first round of applause goes to the main commiters, <a href="https://twitter.com/jpthiery">@jpthiery</a> and <a href="https://twitter.com/ModuloM">@ModuloM</a>. The second one goes to everyone who stepped early into our ship, <a href="https://twitter.com/KristofKerminon">@KristofKerninon</a>, <a href="https://twitter.com/freemaria55">@freemaria55</a>, <a href="https://twitter.com/XebiaFr">@XebiaFr</a>, <a href="https://twitter.com/innothiga">@innothiga</a> and <a href="https://twitter.com/YesWeScale">@YesWeScale</a>!</p><p>Stay tuned, we have a lot more to come!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce47eb6a7f2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The return]]></title>
            <link>https://medium.com/@kodokojo/the-return-8465ad6a8cec?source=rss-15cac062e657------2</link>
            <guid isPermaLink="false">https://medium.com/p/8465ad6a8cec</guid>
            <category><![CDATA[xebia]]></category>
            <category><![CDATA[kodo-kojo]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Kodo Kojo]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 10:09:42 GMT</pubDate>
            <atom:updated>2016-11-18T10:09:42.650Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everybody,</p><p>Long time no see… But hopefully we have some fresh news to share with you!</p><p><strong>Project snapshot overview</strong></p><p>We have reached a very important milestone in Kodo Kojo’s development:</p><p>Our backend and frontend communicate together from account creation to software factory creation! We are now able to pop a complete project stack with Gitlab, Jenkins and Nexus registry. The Statuses are routed from Marathon to the UI through WebSocket during creation and, when ready, users can access each brick with a generated https link with valid SSL certification.</p><p>We have decided to open our sources to the consultants of our major and generous investor company:<a href="http://www.xebia.fr/"> Xebia IT Architects France</a>. We have merged some PRs and welcomed new contributors. We can’t wait to open it to all of you so you can try, use, PR and open issues on what we have achieved so far.</p><p>We are actively working on documentation to do it as soon as possible. Stay tuned!</p><p><strong>Focus</strong></p><p>From our point of view, UX and design are one of the cornerstones of an awesome tool. We had the great privilege to welcome a very talented Art Director, Kristof, in the team last week. We try hard to make the UI clean, simple, beautiful and easily extensible. He has already created some design tests and we are very interested to have your feedbacks on it. So here is a sneak peek (remember that it is at a very early stage and could change):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*bVXjUHr60CPPkXcU.png" /></figure><p><strong>What’s next?</strong></p><p>Our next big goal is to be able to build Kodo Kojo with Kodo Kojo. It’s enough work to keep us busy until our next mailing. We will consolidate the UI look and feel and start to implement it.</p><p>One last thing: we are very proud to announce that we will talk at the <a href="http://paris-container-day.xebia.fr/"><strong>Paris Container Day</strong></a>!</p><p>Don’t forget our twitter account <a href="https://twitter.com/kodokojo">@kodokojo</a> and our email <a href="/service/mailto:contact@kodokojo.io">contact@kodokojo.io</a>, we will love to hear from you if you have any question or feedback.</p><p>We will come back soon for our next fresh &amp; news mailing.<br>Since then, code carefully and have fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8465ad6a8cec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[News are coming !]]></title>
            <link>https://medium.com/@kodokojo/news-are-coming-58ef25c1c8df?source=rss-15cac062e657------2</link>
            <guid isPermaLink="false">https://medium.com/p/58ef25c1c8df</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[kodo-kojo]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Kodo Kojo]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 10:01:29 GMT</pubDate>
            <atom:updated>2016-11-18T10:02:35.210Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi there,</p><p>Welcome to <a href="https://:kodokojo.io">Kodo Kojo</a> and thank you for your interest!</p><p>We are now waiting for our code to reach the right level of quality.</p><p>At the moment we have a good part of the core features working:</p><ul><li>We scaffold an entire <a href="http://mesos.apache.org/">Mesos</a> / <a href="https://mesosphere.github.io/marathon/">Marathon</a> infrastructure on AWS with <a href="https://www.ansible.com/">Ansible</a>.</li><li>We can create and manage users on a <a href="https://about.gitlab.com/">Gitlab</a> and a <a href="https://jenkins.io/">Jenkins</a> (in containers).</li><li>We auto generate SSH keys so users can connect to the Gitlab through SSH.</li><li>The UI is under active construction. We have chosen a <a href="https://facebook.github.io/react/">React</a> / <a href="http://redux.js.org/">Redux</a> stack and will work on the UX very soon.</li><li>… Some cool features we will talk about next time</li></ul><p>We also have a twitter account — <a href="https://twitter.com/kodokojo">@kodokojo </a>— don’t be shy, follow us ;) We’re excited to have you on board and look forward to giving you fresh news about us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58ef25c1c8df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>