It’s no secret that Travis CI loves open source. Travis CI is the home of open source testing and is available to use for any open source software project out there. It helps ensure that best practices are followed, and helps improve overall software quality.
I have been involved with the foundation since it’s early days when I attended the first London meetup. When I started the hubot-symphony project, I had an account on the public Symphony POD and that was it. Like many open source projects, I started with a selfish purpose, to facilitate moving existing chat bot tools used in my day job onto the Symphony platform as part of evaluating Symphony. Building software to interface with an API without access to the system itself was certainly a challenge for a modern software engineer and I am glad to say the route I took is consigned to history thanks to the Open Developer Platform (ODP) provided by the Foundation. I want to discuss my initial development approach and how that has evolved as the Foundation has matured.
At the Symphony Software Foundation we care a lot about IP Compliance of the software we host, which is why we:
Governments, corporations and cybersecurity experts are still reeling after getting a taste of the most widespread ransomware attack to date. Only a few weekends ago, over 200,000 computers in 99 countries were hit by the unprecedented “Wanna” ransomware attack, also known as: WannaCry, WCry, WanaCrypt and WanaCrypt0r.
