The global ICT industry nowadays cannot be imagined without the Open Source Software (OSS). When discussing open source two meanings are possible: 1) software that is free of cost and 2) software that one can do whatever one wants (e.g. read the source). During the development of the eWALL system a special attention was put on the software, both used and developed. The choice was made from the start to make the final outcome open source and for this reason every input building block had to satisfy the software license and quality requirements. The benefits of open source such as transparency, usage of open standards, avoidance of vendor lock-in, possibly larger developer base and community were all considered when deciding for going open source.
In the eWALL project, the consortium partners have similar beliefs that sharing concepts, ideas and source-code in public can be the beginning of synergies and collaboration to address challenges more efficiently and does not necessarily mean that others will reach the same level of maturity that is being reached over a period of years from the consortium partners. Besides, the new digital era is about “survival of the fittest” and whoever wants to make the big step, should be among the “fittest”.
eWALL has therefore taken the strategic decision to release its solution as open source and agreed on a joint exploitation plan that will be flexible and open for collaborations within partner organizations and individuals.
eWALL software is released under Apache License 2.0 for the Cloud domain and GPL for the home environment. eWALL aims to reduce the digital divide and at the same time achieve greater market penetration. Since it is envisaged that the eWALL system should involve in the future, include some additional functionalities but also to tweak existing ones according to the specific user needs we believe going with open source will also attract new developers, researchers, institutions and possibly also companies. Apart from updating and adding new functionalities a possible improvement in code base and additional testing and continuous quick bug fixing was also on the top of the list when deciding on the future of our system.