Category talk:Peerproduction

From P2P Foundation
Jump to: navigation, search

--Poor Richard (talk) 20:34, 3 October 2012 (UTC) --- I like this presentation of the characteristics of peerproduction. The "beyond classes" etc. is a good list and the list of practices is very inclusive yet very concise. I suggest adding the term "composabilty" in the item on modularity, and something about subsidiarity in reference to hierarchy. Perhaps it could be clarified under what terms and conditions hierarchy and meritocracy may play roles. I wonder if it might also be useful to work in something about proportionality, checks and balances, and conflict resolution. --- --Poor Richard (talk) 20:34, 3 October 2012 (UTC)

I would suggest doing this in the 1-14 listing, by creating additional "see also" references in the appropriate places. Do you have texts to create an entry on composability? I do have one concern though, which is I have never seen any reference to composability or subsidiarity in any literature on the subject, and this list is meant to be empirical. So it's not about how anyone wishes peer production to be, but how it is actually functioning.

--MIchel Bauwens (talk) 19:10, 4 October 2012 (UTC)

--Poor Richard (talk) 11:51, 11 October 2012 (UTC): from the wiki: http://p2pfoundation.net/Subsidiarity There are no references to "composability" here other than my own, although it is roughly synonymous with modularity: "Composability is a system design principle that deals with the inter-relationships of components. A highly composable system provides recombinant components that can be selected and assembled in various combinations to satisfy specific user requirements. The essential features that make a component composable are that it be: a) self-contained (modular): it can be deployed independently - note that it may cooperate with other components, but dependent components are replaceable..." (Wikipedia)

In both cases my suggestion is that these terms, though perhaps not commonly used in the p2p vocabulary thus far, apply to existing p2p practice that is simply described in other terms. I suppose it remains to be seen whether the p2p community, perhaps those with systems analysis or engineering orientation like myself, find the terms useful.

This is how we might insert them within existing 1-14 list items:

  • Modularity: tasks, products and services are organized as modules, that fit with other modules in a puzzle that is continuously re-assembled; anybody can contribute to any module. (See also "composabilty", from software engineering terminology, [wikipedia dot org/wiki/Composability])
  • Negotiated Coordination: conflicts are resolved through an ongoing and mediated dialogue, not by fiat and top-down decisions ( ≠ centralized and hierarchical decision-making). (See also "subsidiarity", "the delegation of decision-making power over a particular area of operation by those working directly in that area." [1])
--Poor Richard (talk) 11:51, 11 October 2012 (UTC)

done!--MIchel Bauwens (talk) 15:28, 11 October 2012 (UTC)