> As a rule of thumb, the more open source you use, the more time you need to put all the content together. The initial development of this UI in a software pro

> As a rule of thumb, the more open source you use, the more time you need to put all the content together. The initial development of this UI in a software product takes between 5 to 10 developer days based on two backlog refinement meetings I’ve been part of. I would estimate the maintenance of the content to take one developer day per year. For a thing that shows the licenses you need 5-10 days? Weird estimation. Add a item to a popover menu called "Licenses", make it open a window with textview in it or a listview of expanders for each component, done. Maybe two hours at worst > You need to make the source code available either with the product or separately, which means you need to manage a repository where people can inspect and download the open-source code, depending on the open-source license sometimes even your own code. It would be best to create a workflow allowing people to request the open-source software, create and maintain a software repository where the relevant source code is available, and assign somebody responsible for this. [...] The development of the corresponding UI takes some 2 to 3 developer days. The GPL does not require you to host it as a git repo, so a simple "Download"-Button should be ok, so it would only require adding a button to the website and uploading the file to a server, maybe adding a direct link to this file somewhere in your application. This shouldn't take more than 30 minutes