Since the beginning of this year, Endocode has been part of a consortium of partners that develop intelligent software package management systems to enhance robustness and security in software ecosystems. The project “Fine-Grained Analysis of Software Ecosystems as Networks” is led by the TU Delft and has received funding from the European Unions H2020 research and innovation programme. Endocodes contribution in this project has its focus on licensing and compliance. License compliance requires analysis of own source code combined with an understanding of the complete dependency graph of the distributed packages.
Disclaim, disclaim Here at Endocode we love Microsoft Active Directory. Mostly because we don’t have to deal with it internally. But let’s be honest, we do understand that there are a couple of reasons to stick to this long-standing giant. Hence, this article is not another rant about Active Directory. It’s actually quite the opposite, because we are truly excited to tell the internet how it can be federated with Google easily.
Endocode believes that Free and Open Source software benefits all of us. Open Source licenses provide the legal backbone for our intentions to share the created code so that everybody can use, study, modify and improve it. Copyleft licenses, in particular the GPL, model this relationship in a reciprocal manner by requiring all modified and extended versions of the code to be free as well. Some of our Quartermaster code is released under the GPL-3. We also believe that our users share this vision and comply with the terms of the license by default, and that deviations from this norm are probably honest mistakes. By entering into the GPL cooperation commitment, Endocode aims at giving a fair chance to correct violations before licenses are terminated.
With the end of the year, Endocode is announcing some changes to reshape the company’s leadership. Lisa will take over the role of CEO and Sebastian will take over as CTO. While this might come as a surprise to some, for most of us, this is a natural evolution of our company. What we mean with being a meritocratic and inclusive company is that those who are eager to participate, thrive and lead will get the chance to do so.
Some time ago, when kicking off a new project to integrate yet another Jenkins based CI setup for one of our customers, they asked us for a rather unusual feature: a second Jenkins master the system can failover to in case of malfunction, that eventually would reduce risk of downtime. What we came up with, why we got there and how we implemented it is what we’re sharing here with you.