Skip to main content

Open Software Market™

Pain Story

Software development costs a lot and still ends up with a bunch of bugs. Developers are frustrated because they can tell there's a problem: the development process is managed in a way that is very counterproductive.

There's a systemic problem in the way software is developed in most companies: the process is fundamentally flawed. Business relationships with software developers breakdown through issues with communication, roles, scope, timelines, and productivity.

Grand Vision

As a leader in business, what if you could get business problems and other real world problems solved without the current issues inherent to managing developers? As a developer, what if you could have everything you need to develop, without the usual pain associated with going through a corporation to do it?

Open Software Market

We propose OSM (Open Software Market), a system to facilitate people to:
  • Inspire: Think of great ideas? Share to find out which will fly
  • Influence: Aware of needs? Promote the ideas that you know have value
  • Create: Earn incentives to implement your choices from a variety of valuable ideas
OSM would let members of the general public bid to buy and sell shares of open intellectual property, possibly using digital currency. (OSM would start by supporting software development projects, and could possibly expand for other types of intellectual property.)

Differentiators

Other ideas including Open Source, consulting firms, freelance portals, and Agile, may be helpful, but don't give us the whole answer to the software development pain. OSM is different:
  • Open Software Shares: Creative workers would get a direct monetary incentive to publish their valuable work; and they wouldn't need to sell T-shirts or something to monetize it 
  • Blockchain Attribution: OSM would use advanced encryption technology to ensure incentives made it to the appropriately authenticated inventors

Comments

Popular posts from this blog

Shared Project Manifesto Version 2

Contents:IntroductionLaunchTradeRewardDevelopVoteHarvest 1. Introduction IP (Intellectual Property) is a great asset but it is hard to produce well. We hypothesize that a market to facilitate shared projects would make it easy to produce IP better.


The market contains projects. Each project has one admin and a number of traders and developers. One user can have any combination of roles at the same time. For example, a user may be an admin and also a trader, or a trader and also a developer. ProjectsUsersAdmin: Provides ideas in exchange for controlTraders: Provide incentives in exchange for growthDevelopers: Provide IP in exchange for incentives 2. Launch When somebody came up with an idea for an IP product, they could create a project for it on the market. That person would be the admin.
The market would record the time the admin launched the project. That lasting record could provide for the admin to claim credit for the project idea, on a first-come, first-served basis. This recogn…

Contact Codes Lite™

CCL (Contact Codes Lite™) would be a software product to help people exchange many kinds of contact information much more easily. CCL would do this by providing users with relatively simple contact codes. The users could distribute the codes to many people in many ways. Then, a person who received a contact code could use it to retrieve the original person's contact information through CCL.

For example, many people still exchange business cards. Retrieving various information from the cards can be time consuming and error prone, especially when there are many cards. Also, when somebody updates their information, the information from the card is no longer valid.

Other good examples for usage of contact codes include:
On a slide in a presentationIn email signaturesOn name tagsIn applications that provide limited space for profile informationWhenever you want to provide easy access to many different contact options without listing each
The main thing that would make CCL different from…

Fog Machine

Fog Machine™ (named because fog is like a cloud, on the ground) is a software product to provide cloud services to customers without a cloud service provider. The problem with the traditional cloud is that it requires a provider. Fog Machine™ would run cloud "nodes" in idle system resources on ordinary user's devices. This would be a peer to peer system in which each connected device would be a peer.

It would support standard cloud APIs (perhaps Cloud Foundry?) and it would be easy to port cloud apps to it off providers such as Google cloud, Azure, or AWS--or maybe it would be effortless for apps that were already portable through compliance with open standards.

We might use encryption for privacy, redundancy for reliability, and remuneration/incentive for resource consistency. The showstopper (critical assumption) is that the synergy would be sufficient to significantly surpass the overhead, and provide competitive performance for at least some types of cloud applicat…

Please Comment

Have you ever heard of a similar idea? What challenges might an idea run into? How might you like to be involved? Comment to add your voice to each idea.