Topic: [DVC]DevCoin - Official Thread - Moderated - page 273. (Read 1059181 times)

LOL Good point. Well I will help so long as I can

lol, everything in devcoin, devtome, cryptocurrencies etc is under constant development.


Is the current version working and being used?

Yes.

Is it still under development?

Also yes.

How long will it stay under development?

Hopefully forever.

What will happen if development stops?

It's dead and abandoned.

Ahh I didn't know it was still under development. In that case, I will continue working on the bounties the way they are (on the prototype site) and will help out where I can to further the development of bounties in the future.  I loved some of the proposal further up the forum here today. It would be nice to be automate a little more with the way they are given out. Like the bounty admin being able to fill out a form on the website and click a button to close a bounty and assign the share amount for the bounty to a user. The website should update the receiver files.

But that for now is beyond my understanding of the coin and how it works at this time! As I learn more, I will be able to help more! Also any input on the prototype site is welcome from anyone It is just a play site for me, but can be used by anyone (without warranty of course! )

Chad

Yes, I was talking about how bounties and reviews should work in the future. It's an ongoing development. ;-)

I am not sure that is how the bounties work here since they have to be added to the blockchain etc. The bounty admin and other admins are the ones that accept a bounty proposal and then decide who gets the bounty and how etc as they add them to the receiver files. If this is going to change or what not I am all for it, I just just writing a front end to help the admins at this time. It will have the ability for people who have a devtome account to propose and vote on proposed bounties, but that is about as dynamic as it is going to be for the first rev. (this is just for the project I am working on)

Chad

PS. I could be wrong on how bounties work too!

You are more then welcome to for someone else to start one, the one I am working on I figure there wasn't a bounty for (out of love of the community I guess )  

ps. Prolly more just to see if I could do it

pps. Wow, I didn't see the proposal till I wrote this one! That is nice! I can incorporate some into it, but iti s mostly just a prototype site so nothing is open source so to speak (PHP and not ready for prime time) Love that proposal! Ok, back to work...

Looking good!  Should we assign a bounty to this to help kick things off?  e.g. 12 shares or so, depending on the difficulty

Forgive me for posting this plan here, but I don't have access to Devtome. I have been working on it over the last few hours and think it is relevant to the discussion. Let me know what you think

Devcoin Bounty Engine

Introduction

Devcoin’s model of paying out shares of coins for creative, technical and administrative work has a few barriers in its way if it wishes to extend beyond a few people that make up the current community. As of today, the process for suggesting what will be paid out consists of a member of the bitcointalk community writing on the forum with an idea for a proposed bounty. Other members may then discuss the idea and an Admin will finally validate the idea into a bounty by posting it on the Devtome bounty page. This process is cumbersome, needlessly complicated and does not allow for  a democratically popular vote. If we wish to move Devcoin forward, we need to have people trust that bounties are not being created out self interest but instead to expand public domain and open source material.

I propose creating a website that functions as platform for people to propose bounties and vote for which they want to see move forward.

Bounty Engine

From here forward, I shall refer to the this website as a bounty engine seeing as how it functions an engine of creation.

Model

This idea for a bounty engine is modeled after bountysource.com, a website that helps complete open-source projects by allowing people to propose bounties.

Summary

The Devcoin bounty engine will allow for bounties to be proposed by active users. These proposed bounties will then be voted on by the members of the community. If they pass they are allowed to be funded by members of the community directly as well as shares of Devcoin blocks. If a person is able to complete the project proposed in the bounty the community will then decide whether the project meets the specification original proposed. If so, the bounty is awarded.

Proposing a Bounty

Any active member can propose a bounty (see below in bounty funding for the definition of active member.) A bounty proposal must be no longer than 150 words and written with clear objectives. Once a bounty proposal is created the week long vetting process begins. Under the bounty proposal description is a “pro column” and a “con column”.  Members of the community can place comments in either the pro or the con column with their opinions. These comments get voted up or down, so that the most popular comment for and against the creation of this bounty are at the top of the respective columns. At the end of the week the most valuable comments for and against the proposed bounty should be visible at the top of the columns.


Voting

Any active member can vote. Voting is open for a week. For a bounty to pass, it needs a total of half the points equal to the number of active users at the time the voting starts. For example, if there are 100 active users at the time voting begins, you will need 50 points by the end of the week. A “yes vote” is equal to +5 points and a “no vote” is equal to -4 points. Therefore, at least 10% of active users need to participate to get a vote passed. If, for example, there were 100 active users and everyone were to vote, 50 yes and 50 no, the vote would just barely pass will 50 points. Once voting is complete and a proposal has passed it becomes a bounty.

Bounty Funding

Bounties are funded in two ways, community funding and share funding.

Community Funding

Signing up to be an active member requires paying at least 1000 Devcoins for 30 days in advance of it begin spent. In other words, to become an active member you must pay at least 1000 Devcoins every 30 days (or 12000 a year) with that money being spent on bounties throughout the next 30 day period. You can always pay more if you want to fund more projects, but 1000 Devcoins a month is the minimum.

When you put your initial 1000 Devcoins in an active user account you must choose at least one bounty to which you wish to contribute.

Every second 0.00037500 Devcoin is subtracted from your 1000 Devcoins and go into you bounty(s) of your choice. I’ll call this drip system funding. You can choose up to 6 projects you wish to fund simultaneously.

If you choose 1 it is for each bounty: 0.00037500
If you choose 2 it is for each bounty: 0.00018750
If you choose 3 it is for each bounty: 0.00012500
If you choose 4 it is for each bounty: 0.00009375
If you choose 5 it is for each bounty: 0.00007500
If you choose 6 it is for each bounty: 0.00006250

Over a 30 day period this is 972 Devcoins, with 28 Devcoins remaining for transaction fees.

The idea behind drip system funding is that the price of the bounty is incrementally increasing and allows for a more dynamic feel and encourage people to fund bounties as well as complete them.

If dripping is stopped for more than a week, meaning no one giving the bounty any money, the bounty is closed and the coins are spread to all open bounties. (I don’t for see this happening very often since it doesn’t take much to keep a bounty active. It would help bounties from remaining open for years without any activity.)

Share Funding

Beyond community fund, coins can also come from shares paid out by the Devcoin blockchain. A certain amount of funding can be extended to the Devcoin bounty engine much like it is to Devtome and split among open bounties. How this might be funded would take some more careful consideration.

Claiming a bounty

If you feel like you have fulfilled the requirements of the bounties you can submit your bounty claim. Once a bounty claim is submitted, admins verify that the bounty had been completed. (This could eventually also be done by voting or some other democratic method) The bounty is left open for a week after it has been completed to let other people submit bounty claims for second and third place. If for any reason the first bounty claim did not satisfy the bounty specifications, the bounty will be award to the runner up. The payout scheme for bounty claims submitted before the one week deadline are as follows:

1st and only legitimate claim: 100% of bounty
1st legitimate claim with runner up: 75% bounty, runner up: 25%
1st legitimate claim with runner up and third place: 70% bounty, runner up: 20%,  third place 10%

Projects that can be funded with this model

The Devcoin bounty engine would not just be limited to open source code, but allow for all sorts of creative projects to be funded. We can imagine a future where a lot of small scale public projects are funded through this format.

Why Devcoin?

It’s value is low enough that it can work mathematically.
It already has an existing bounty system in place that can be utilized to make this bounty engine work.

Conclusion

The preceding plan is just one way that this can all come together. Though many have put together ideas for ways bounties can be created, I hope that by being more specific I can move this discussion to the next stage.

jdlrexy DVC: 13EXhfCtJ3n3R2k2iNLoRVDCxqfjv9LN2Z

Atleast every developer should have a score, a rating system that shows if they messed up in the past.
That's how a fair free market works. Every form of transparency is welcomed, aslong as it doesn't violate privacy.

That is a great idea to add to the bounties as well! I may look into doing something like that once I am done with the "official bounty" thing. I will have to look into more of how things work on the back end to do something like that, but it is a really good idea. There are going to be things that people want to have done that won't get picked up by the official group, and they should be able to fund it themselves.

Chad

Very interesting to hear about that.

I agree that we need something that brings demand and supply together, so that things that are wanted are created, and things that are unneeded are shunned.
(ofcourse it's not that easy, because how do you know what is needed? Sometimes a solution is only visible in hindsight, for example you do a lot of research & development that could be considered wasted in hindsight, but was nonetheless necessary. Sometimes it's not a targeted process.)

People who visit devtome (or other devcoin "departments") should have an easy possibility to express what they want and need.
Also they should have a possibility to easily check if someone else has already started a project that fits their own specifications.
Something like kickstarter, but instead every registered user can give his one vote/share of the total 180 mill.
Also there should be a possibility to donate your own devcoins (not from the 90%)

There must also be a possibility to take pledged money back if a proposed project/development does for some reason die or selfdestruct.

So many thoughts...

Nice, I am by no means capable of pulling something like that off on my own, but it is interesting!  I am going to keep moving forward with my vision of the bounty tracker for DevCoin as I see it, but I could see possibly integrating it with the exchange you mentioned as well. I will follow any developments you may have in that area! Great write-up too by the way!

That's an interesting site, didn't know anything about it. My longer-term business plan involved something like that (http://devtome.com/doku.php?id=development_exchange) but actually directed at the opposite non-core devcoin bounties and work, although I agree a more structured way to organise bounties would be helpful.

Another couple of things I've come across that were also interesting re. Devcoin angle:
http://ejohn.org/blog/gittip-at-khan-academy/
payswarm (cached - seems to have been subsumed in past week by web-payments.org which looks more about bigger picture Open Transactions perspective, although not sure how 'open').

Well, I have started coding, though it isn't going to be as intricate as the "bountysource.com" site. I am mostly putting it together so the bounty admins have a place to track it  and everyone can propose and vote on proposed bounties. Since the admin have to approve a bounty and they have to do things on the back end once a bounty is completed.  I am sure it is going to go through a bunch of iterations, but still I don't foresee it being anything like Bountysource.com since it doesn't quite work that way with devcoin bounties.  I may have a first rev up today, not sure yet   Will be at http://madrabbitproductions.com/devcoin/

That's great. Do you mean that you have a plan in the works that you are writing or actually already putting together the site?

done Thanx

Looks nice. Maybe you can add thousands separators to make bigger numbers better readable, for example here:

DVC / BTC   1,149,425.28735632
Est. DVC Per Share   205,479

I have no clue Any ideas on other things we can put up there?  I was going to set it up so that when logged in it will allow you to see a graph of your shares from round 22 on. Other then that right now I am working on a bounty organizer page. I just didn't want to take away from your page, just figured since I had made this one as well we could share ideas or what not.

Ha, this desktop is running Fedora 17, with Gnome 3, albeit in the tuned down mode that makes it try to look more like Gnome 2.

When I visit that page it tells me right at the top of the page

"We cannot detect a running copy of GNOME on this system, so some parts of the interface may be disabled. See our troubleshooting entry for more information."

In theory I can run some other windowing manager such as KDE, which I might actually find I like better since I have never liked Gnome 3.

But in practice I have been trying to get all my machines as raw out of the box standard as possible, so as to minimise the amount of setup needed each time I set up a new box and so the live boot disks work just like the ones that have the O/S installed to hard disk.

It is quite annoying that they insist on coming out of the box broken by design.

I would almost be tempted to figure I should move to Ubuntu since that seems to be the new standard "everyone" is using, but I hear that now comes totally infested with spyware by design so that is right out.

So far none of the extensions packages mentioned seem to exist for Fedora, maybe they just bundle them differently into differently named packages I am not sure yet. I need to get my country house re-wired and get out there, then I will have space and electricity to screw around with trying to find a usable setup to switch all my machines over to.

What is going on with the checksums thing that is going to break all existing assets, server-IDs, nyms, accounts and so on? I do not think setting Grandma up for having to do a big migration of all her nyms and accounts and so on is a good idea, if that stuff has to go in it should probably go right into Grandma's client from the start else we are just setting her up for a huge amount of work she will end up having to do to upgrade to the next version at some point, work that probably isn't really the kind of stuff we should expect Grandmas to do...

-MarkM-

I have something in the works for this at the moment. Just thought I would let you know