Open need as solution strategy

"Open need",  the conceptual/strategy is under-developed strategy and vision to guide FLOS development and break the monopoly in market for any software solution. Biggest realization of this project need is that FLOS softwares are the free and open solutions for mostly closed needs. The need or requirement of the software are closed, undisclosed by the proprietary developers but more importantly unexpressed by the people who need them, the users. When users have the ability to express their needs and when those needs in form of standards or use-cases are available to all as "Open need", the development of solutions will be well guided and will happen at multi points both proprietary and FLOSS community. This should reduce monopoly if not at-least guide the FLOSS development. To sum it, "Open source solution follows open need expression". The inspiration of this concept was realized while attending a software presentation inside the institute meant to help designers to identify similar looking trademarks. A huge gap about the software need between users/designers and the software developers and a need for bridge communication to express the need in form of use-cases from where the developers can take off was understood. This holds good for any software. The design methodology of designing along with the customers called Co-design needs to be applied to software development too. When this gets executed for FLOSS development there will be tremendous achievement for software freedom. Doodles related to this strategy are below:

Graphic designers explaining basics of graphic design to a developers

and Me acting as the bridge between NID and OSI, Open Source Intiative

Review feedback expressed in the "E-verification software for similar looking logos." 

Logo expression of NID becoming Open source development hub

Open need logo derivation from open source initiative logo

Open need expression in form of use-cases and available in commons.