For some time now, we have been implementing a new routine in our SCOP: every two months, the whole team meets up for a whole day dedicated to contributing to the Free tools we use, we develop&#8230; or not!



This new initiative comes in addition to what was already allocated to some of our cooperators to maintain some of the projects that allow our structure (like so many others) to prosper. The problem of the sustainability and maintenance of Free Software &#8211; Although they are the foundation of the information society &#8211; is a complex and publicly useful subject to which few effective answers have yet been found.



By dedicating time to our developers to work on these projects, our cooperative is trying to improve the situation and to contribute in return to the public interest infrastructures created and maintained for free by developers from all over the world. It&rsquo;s also a good opportunity for our teams to learn new skills, to discover new technologies and to face advanced problems.



Despite the calm of August, we have again taken up this challenge: a few days ago, about twenty cooperators gathered to fix security issues, resolve bugs, review patches proposed by the community and add new features on various free projects that we like.



The day started with the constitution of the working groups:&nbsp;



The API Platform working group was busy releasing API Platform 2.4.6 and preparing the imminent release of API Platform 2.5 beta ;



The team working on React Admin focused on finalizing a brand new version of the integration with API Platform (done in collaboration with Marmelab) which will greatly improve its ease of use and customization;



The team working on Symfony focused on fixing bugs affecting the tool.



Discover our contributions:



The team finalized the addition of a major new feature that will arrive in API Platform 2.5: the support of generated API formats (such as Hydra) in the auto-generated OpenAPI documentation, and the possibility to generate JSON Schema corresponding to a resource;



Using this new infrastructure, Jacques Lefebvre added a command to export a JSON Schema from a ressource;



Quentin Barloy solved a bug affecting API Platform when a data provider returns a generator, he also improved the documentation concerning this feature. Moreover he added unit tests covering the brand new JSON Schema generator;



Kévin Van Der Stracten did his first bug fix on API Platform, with the help of Antoine Bluchet;



Grégory Copin adapted the NextJS application generator provided with API Platform to use the new version of the popular JavaScript framework;



Mathieu Dewet, in collaboration with Robin Chalas, fixed the implementation of the refreshUser method of the LdapProvider, and fixed some other issues in Symfony ;



Vincent Chalamon drastically improved the security and usability of the access control mechanism provided with API Platform;



Grégoire Hébert added a new feature to API Platform allowing to choose which OpenAPI versions to activate;



Jean-François Thuillier and Morgan Auchedé finalized the new version of API Platform Admin and started writing documentation.



The outcome of this working day: 13 PRs have been merged, 2 issues are open and other topics are under consideration.&nbsp;



At Les-Tilleuls.coop, we encourage and support our cooperators, even the beginners or the most shy, to contribute to the software they use. The Free Software community is based on knowledge sharing, collaboration and exchange. Every contribution, no matter how small, is beneficial and has a lasting effect on the ecosystem. Some reticence may arise, linked to the fear of not feeling legitimate to contribute, but we must keep in mind that we are lucky to have access to a large community of contributors acting for the continuous improvement and reliability of the software we use. Supporting them like this is the best way to thank them for all the time they have already undertaken in this process.

A day at Les-Tilleuls.coop: collective contribution to Free Software

What do we do at a General Meeting?

Hello everyone! I&rsquo;m <meta charset="utf-8"><a rel="noopener" href="https://twitter.com/Pandora_angora" target="_blank">Caroline</a>, back-end developer freshly arrived at Les-Tilleuls.coop! Today was my first general assembly (GA) and the first of the year 2019. Here is my feedback on this special day.



<h3>What do we do at a General Meeting?</h3>



Les-Tilleuls.coop being a SCOP (go here to learn more), we make decisions together in a democratic way. Each employee can make proposals or give his or her opinion on different areas. Once a month, all the cooperators meet at the office in Lille to make various decisions related to legal news, the budget or recruitment. Each cooperator has one vote representing one vote, it is not a dictatorship here.



The office is busier than usual. We are from a dozen people to about thirty in some minutes. We take a breakfast together, we discuss then we make a Tetris with the armchairs so that everyone can return in the meeting room.



<figure class="wp-block-image"><img src="https://les-tilleuls-wordpress.preprod-tilleuls.ovh/wp-content/uploads/2021/08/286.jpg" alt="AG" title="AG"/></figure>



Tetris with chairs.



 



The agenda is established a few days before and sent to each cooperator who can contribute directly. If someone has a proposal for a tool, an idea, you shouldn&rsquo;t hesitate to add it and to present it to everyone during the GM. We discuss the different points, give our opinion and then we vote by a show of hands (for, against, abstention).  



Olivier (our CFO) started this first GM of the year with the balance sheet of the turnover of 2018. It was an opportunity to talk about customer relations, the strong and weak points, to get advice on processes to improve.



An important aspect in the life of our cooperative concerns recruitment. We discuss candidates&rsquo; profiles by email or on Slack, we vote on hiring them together at the GM. During a GM, we can also suggest a candidate and then vote to decide if we dig the lead or not, and what offer we can make. We also review current hires and the marketing strategy for future hires (we&rsquo;re hiring, come on! &lt;3 ).



Then, we present the different prospects, the current demands of the client, what his needs are and we plan which cooperator will be available and the most suitable for each mission. We then vote on all the other proposals concerning the life of the scop, such as the budget for an event or the implementation of a new reform.



It is 12:30, we end the GM with the presentation of the different workshops planned for the afternoon. We take the opportunity to work together on internal projects, on Open Source contributions or to train for conferences. 



At the end of the day, a report of the GM is sent to all and we fix a date for the next monthly GM. We celebrate the end of the GM with a good meal in a nice brewery. A convivial moment to share with the cooperators of the different offices 🙂



<figure class="wp-block-image"><img src="https://les-tilleuls-wordpress.preprod-tilleuls.ovh/wp-content/uploads/2021/08/287.jpg" alt="TEAM 3B" title="TEAM 3B"/></figure>



We eat a very balanced diet to survive the cold. weather.



<h3>Workshops</h3>



Several groups were formed in the afternoon to work on different internal projects, Open Source projects, preparations for training or upcoming meetups. This afternoon I followed a video-conference training on <meta charset="utf-8"><a rel="noopener" href="https://blackfire.io/" target="_blank">Blackfire</a> given by Christophe Dujarric.



<blockquote class="twitter-tweet" data-lang="fr">Cet après-midi, c’est formation <a href="https://twitter.com/blackfireio?ref_src=twsrc%5Etfw">@blackfireio</a> avec <a href="https://twitter.com/Chris_Dujarric?ref_src=twsrc%5Etfw">@Chris_Dujarric</a> en attendant le meetup <a href="https://twitter.com/afup_hdf?ref_src=twsrc%5Etfw">@afup_hdf</a> de demain <a href="https://twitter.com/hashtag/Masterclass?src=hash&amp;ref_src=twsrc%5Etfw">#Masterclass</a> <a href="https://t.co/N32J6bTQHp">pic.twitter.com/N32J6bTQHp</a>— Les-Tilleuls.coop (@coopTilleuls) <a href="https://twitter.com/coopTilleuls/status/1087362605465985027?ref_src=twsrc%5Etfw">21 janvier 2019</a></blockquote>
<script async="" src="//platform.twitter.com/widgets.js" charset="utf-8"></script>



I then finished my day on the writing workshop for the blog. Another busy day at the cooperative. See you soon!