Currently, I'm doing a large assignment on KeePass as an open source innovation. I handed in my draft and received feedback. The feedback was mostly about the inter-operability of KeePass with other websites, systems and services which was very important as it showed the linkages of the platform (KeePass). As a consequence, the usability of the program gets enhanced, according to the teacher. I'm finding it difficult to come up with an extensive answer. The project is mostly about value appropriation. So, how does KeePass appropriate value as an open source innovation (role of developers, contributors and end-users. KeePass as a platform etc.).
Also, do you think that KeePass is dealing with a ''same-side effect'' in which an increasing number of users on one side makes it more (or less) valuable to users on the same side. So, developers of Keepass and other developers. Or do you think that they are dealing with a ''cross-side effect'' in which an increasing number of users on one side makes it more (or less) valuable to users on the other side. So, developers from KeePass and end-users of KeePass.
I was wondering whether I could derive any usefull information from anyone regarding this matter. Looking forward to hear from you.
Last edit: Skandar Sediqi 2019-03-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
KeePass is a single purpose app with virtually no integration with other apps. For linkages it relies on 3rd party "plug-ins" to add features / integration that others find useful. KeePass could be closed source and derive the same advantages from plug-ins.
KeePass gains from user suggestions in much the same way any software does, some things are added / enhanced, some are not. Because KeePass is developed privately there is no external development that you find in collaborative projects, which may have advantages from a security perspective and disadvantages from a feature / development perspective - depending on your point of view.
Side effects are hard to guage unless you find a way to record and measure changes and their effects. As this hasn't been done...
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear all,
Currently, I'm doing a large assignment on KeePass as an open source innovation. I handed in my draft and received feedback. The feedback was mostly about the inter-operability of KeePass with other websites, systems and services which was very important as it showed the linkages of the platform (KeePass). As a consequence, the usability of the program gets enhanced, according to the teacher. I'm finding it difficult to come up with an extensive answer. The project is mostly about value appropriation. So, how does KeePass appropriate value as an open source innovation (role of developers, contributors and end-users. KeePass as a platform etc.).
Also, do you think that KeePass is dealing with a ''same-side effect'' in which an increasing number of users on one side makes it more (or less) valuable to users on the same side. So, developers of Keepass and other developers. Or do you think that they are dealing with a ''cross-side effect'' in which an increasing number of users on one side makes it more (or less) valuable to users on the other side. So, developers from KeePass and end-users of KeePass.
I was wondering whether I could derive any usefull information from anyone regarding this matter. Looking forward to hear from you.
Last edit: Skandar Sediqi 2019-03-18
KeePass is a single purpose app with virtually no integration with other apps. For linkages it relies on 3rd party "plug-ins" to add features / integration that others find useful. KeePass could be closed source and derive the same advantages from plug-ins.
KeePass gains from user suggestions in much the same way any software does, some things are added / enhanced, some are not. Because KeePass is developed privately there is no external development that you find in collaborative projects, which may have advantages from a security perspective and disadvantages from a feature / development perspective - depending on your point of view.
Side effects are hard to guage unless you find a way to record and measure changes and their effects. As this hasn't been done...
cheers, Paul