Gdistribute: Difference between revisions

From Sharewiki.org
(creation of page)
 
mNo edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
gdistribute is a (proposed) tool to facilitate the distribution of goods and parts without the need for money or exchange.
'''gdistribute''' is a (proposed) tool to facilitate the distribution of goods and parts without the need for money or exchange.


Unlike freecycle, or similar initiatives, this is not primarily about "recycling". Although recycling might be a secondary benefit, and may even be an important and large component of the process, the primary goal is to develop a sophisticated and ''industrial-strength gift economy''.
Unlike freecycle, or similar initiatives, this is not primarily about "recycling". Although recycling might be a secondary benefit, and may even be an important and large component of the process, the primary goal is to develop a sophisticated and ''industrial-strength gift economy''.
This does not encompass barter, credit, labour tokens, a "reputation-based" economy, alternative currencies, or any sort of paradigm which is based in exchange.  
This does not encompass barter, credit, labour tokens, a "reputation-based" economy, alternative currencies, or any sort of paradigm which is based in exchange.  


=Transactions=
=Trust-based decisions=


Transactions should not be based on "first come, first serve", but on an appraisal of each local and remote circumstances, availability of resources, etc..
Decisions should not be based on "first come, first serve", but on ''trust'', and on an appraisal of local and remote circumstances, availability of resources, etc..
It may be useful to use the same membership criteria as for [[Sharespace#Membership_criteria|ShareSpaces]].


=Part numbers=
=Part numbers=
Line 15: Line 16:
Thus, the application should really accommodate ''both''.
Thus, the application should really accommodate ''both''.


=Complementary tools & applications=
=Complementary software applications=


Obviously this would need a complementary app devoted to arranging ''transport''. Or maybe that could be integrated in.
Obviously this would need a complementary app devoted to arranging ''transport''. Or maybe that could be integrated in.
Line 41: Line 42:
=External links=
=External links=


* http://gnusha.org/skdb/ - the SKDB project, specifications for open-source hardware
* [http://gnusha.org/skdb/ SKDB project] - specifications for open-source hardware
*
* [http://groups.google.com/group/openmanufacturing/browse_thread/thread/dc97a78f349a7bb8/2ac070bb49fdc2dd a related discussion on Open manufacturing list]
 
 
[[Category:Projects]][[Category:Software]]

Latest revision as of 15:40, 5 September 2011

gdistribute is a (proposed) tool to facilitate the distribution of goods and parts without the need for money or exchange.

Unlike freecycle, or similar initiatives, this is not primarily about "recycling". Although recycling might be a secondary benefit, and may even be an important and large component of the process, the primary goal is to develop a sophisticated and industrial-strength gift economy. This does not encompass barter, credit, labour tokens, a "reputation-based" economy, alternative currencies, or any sort of paradigm which is based in exchange.

Trust-based decisions

Decisions should not be based on "first come, first serve", but on trust, and on an appraisal of local and remote circumstances, availability of resources, etc.. It may be useful to use the same membership criteria as for ShareSpaces.

Part numbers

The software should facilitate both parts with codes and those without. In many cases, the use of a specific part number to unambiguously identify an item can be extremely useful - or even indispensable. On the other hand, trying to attribute a number to everything is unrealistic, far too time-consuming, and probably completely unnecessary. Thus, the application should really accommodate both.

Complementary software applications

Obviously this would need a complementary app devoted to arranging transport. Or maybe that could be integrated in.

Development stages

A possible course of development stages would be:

  • alpha:
    • proof of concept, probably a very crude implementation
    • probably no part numbers at this stage
    • centralised data store
  • beta:
    • distributed rather than centralised datastore, peer-to-peer (or at least the option there of)
    • reliable identification of individuals and groups, e.g. through use of public cryptography (GnuPG IDs, signing, etc.)
    • introduction of part-numbers to unambiguously identify items
  • stable:
    • encryption
    • code refactoring
    • etc.

Compatibility

It may be worth exploring the integration of the tool into skdb application (or vice versa) - or at least ensuring that they are compatible.

External links