Re: MNDF_Project

I just realized that all the facets of value networks may not apply to open
source.

On Tue, Jul 9, 2013 at 6:17 PM, Brent Shambaugh
<brent.shambaugh@gmail.com>wrote:

> Manu,
>
> Regrettably, I'm behind. I have been amazed that the percentage
> contribution for each package is given as well as the percentage
> contribution is built in for npm. After interacting a bit with the
> Sensorica project I have found that the Value Networks could be important
> in conjunction with this. That way you could deal with all of the
> complexities of reputation, role, accreditation, etc. But at the base level
> I would guess it would be some percentage.
>
> A friend of mine gave some thoughts about Debian in particular. Apparently
> he was a bit big on trying things out before donating. :
>
> "
> Debian packages state their dependencies. Ubuntu uses the Synaptic package
> manager to install its debian-style packages. Passing the -S flag to dpkg
> will tell you which file belongs to which package. In Linux, you can find
> what was typed to launch a process in the /proc virtual filesystem under
> /proc/$PID/cmdline for a given process ID $PID. If the first argument isn't
> a full path to a program, it should be a path relative to one of the full
> paths listed in the $PATH environment variable, and you can also get the
> environment out of the /proc filesystem. If it is a relative path, the
> "which" program can tell you the absolute path, but since you have access
> to the environment, you might as well just iterate through $PATH to find
> it. Putting it all together, it should be possible to go from the process
> ID of a process to the list of dependencies that the package that process
> came from rely upon, and you can even get that information hierarchically
> if you want it. It would be possible, then, I think, to go from a window on
> your screen to the process ID of the program that created that window. So
> in a rather rudimentary way, it should be possible write a program that
> lets you click on a window and lists the packages involved in putting that
> window on your screen. Then you could maybe have it go a step further and
> let the user specify an amount to donate and have it divide it up among the
> authors of those packages.
>
> Wouldn't that be cool? If Ubuntu some day supported paying the people who
> wrote the programs you use?
> Then again, I mostly use my web browser, so..."
>
> I also noticed that Dwolla was moving in the direction of gittip (or at
> least it seems). I'm definitely going to have to do more with this. I seem
> to be distracted by a former promise of writing up the broader picture.
> Almost done. Thanks for taking the lead in the past week or so.
>
> -Brent
>
>
> On Mon, Apr 22, 2013 at 10:49 PM, Manu Sporny <msporny@digitalbazaar.com>wrote:
>
>> On 04/22/2013 11:15 PM, Brent Shambaugh wrote:
>> > <2> http://bshambaugh.org/MNDF_Project.html
>>
>> Brent, what a cool concept! Here were my thoughts when reading your
>> proposal:
>>
>> Have you seen gittip? If not, definitely check it out:
>>
>> https://www.gittip.com/about/
>>
>> Did you know that the graphs that you show in your proposal can already
>> be constructed for over 20,000 node.js software packages? They could
>> probably also be constructed for over 30,000 Debian software packages.
>>
>> If you look at node.js packages on npmjs.org, you will notice that
>> almost every one of them is hosted publicly on github:
>>
>> https://npmjs.org/package/mocha
>>
>> Every node.js package contains a file called package.json, which lists
>> that project's dependencies:
>>
>> https://github.com/visionmedia/mocha/blob/master/package.json
>>
>> Almost every package listed in package.json is either on npmjs.org, or
>> on github. So, you could easily build a graph of which package depends
>> on what other package. Let's assume that you split a donation to a
>> project on a 50%-50% basis, where 50% goes to the project you're
>> contributing to, and 50% goes to all project dependencies. For the mocha
>> project, that would be:
>>
>> mocha: 50%
>> mocha dependencies
>>     commander: 5.5555%
>>     growl: 5.5555%
>>     jade: 5.5555%
>>     diff: 5.5555%
>>     debug: 5.5555%
>>     mkdirp: 5.5555%
>>     ms: 5.5555%
>>     should: 5.5555%
>>     coffee-script: 5.5555%
>>
>> Pretty cool stuff... and something where you could process the payments
>> in PaySwarm today. Receiving funds would be voluntary, all we'd have to
>> convince people to do is add something like this in their package.json
>> file:
>>
>>    "donations": "https://meritora.com/i/tjholowaychuk/accounts/mocha"
>>
>> Thoughts?
>>
>> -- manu
>>
>> --
>> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
>> Founder/CEO - Digital Bazaar, Inc.
>> blog: Meritora - Web payments commercial launch
>> http://blog.meritora.com/launch/
>>
>
>
>
> --
> Brent Shambaugh
>
> I've worked with polymers, I teach chemistry, I'm currently researching
> how to build distributed economies.
> Website: http:// <http://bshambaugh.org/experiments/connect_dots3.html>
> adistributedeconomy.blogspot.com
>