LF Energy Summit 2024

When you publish an internal project as open source you want to make sure the project gives off a good impression. The code should be understandable and of acceptable quality and shouldn’t include passwords or confidential information. The project information should be clear and inviting to new contributors. Repeatedly reviewing the project to provide the team with feedback on these topics can be time-consuming for an OSPO. Automation can help speed up the process and reduce time. In this demo the Alliander OSPO team will show their internal OSPO automation that is used to provide teams with feedback on their project before publication. Currently it checks for secrets, copyright and license annotations, project dependencies and non-inclusive language. There are already some ideas for adding more tools for additional checks. The demo will also cover how to get started and what other tools might be considered. So come see this demo if you want to start using automation to check a project before publication or want to keep tabs on an existing open source project.