Super useful.. thank you! I've got the daily funding logic in place now

Excellent! You have the best way of visualizing worker proposals in the whole world as of now, literally.
If you want to improve the display, here are some other hints:
1) Worker objects never expire. Also some workers are not valid yet. You probably should filter out your worker list to only show active and valid ones.
2) However, it is important that upcoming proposals get visibility. Perhaps a separate table of "pending proposals" ranked in order of votes for proposals which have not started yet.

Quote from: maqifrnswa on October 27, 2015, 03:00:26 pm

Quote from: roadscape on October 27, 2015, 01:53:08 pm

Quote from: cass on October 27, 2015, 10:59:33 am

Quote from: mindphlux on October 27, 2015, 10:56:34 am

There's no gui support yet.

ok then we should work in this to get it into asap IMO .. this will drive more people into!

Very basic worker proposals list/schedule can be found at the bottom of this page: http://cryptofresh.com/

that's great, could there be a payline put in there? (so people know what is being funded and at what level?)

That's the "Daily pay" column right? I'm still trying to decipher the API.. your "Debian/Ubuntu-based PPA" proposal is 3966 BTS per day correct?

First off: that's a great site, thanks for doing it

Regarding payline: It's a little more complicated.
There is a daily worker budget of 500,000. Every maintenance period, worker votes are tallied and workers are ranked in order of votes for minus against. The system then pays each worker in order of rank until the daily budget is exhausted.

To find the current worker pay, it's the "worker_budget_per_day" global property:
unlocked >>> get_global_properties
{SNIP}
    "witness_pay_per_block": 150000,
    "worker_budget_per_day": "50000000000",
    "max_predicate_opcode": 1,
{SNIP}

Now you can
look at the current proposals in order of most to least votes (as of this moment) and their daily pay:
1) 1.14.4 (10,000 BTS/day)
2) 1.14.1 (0.1 BTS/day)
3) 1.14.0 (400,000 BTS/day)
4) 1.14.6 (3,966 BTS/day)

So that means that each of the proposals should get funded since the total (413,966.1) is < 500,000
Now imagine there were 2 more 100k proposals with less votes than (4). The new order is:
1) 1.14.4 (10,000 BTS/day)
2) 1.14.1 (0.1 BTS/day)
3) 1.14.0 (400,000 BTS/day)
4) 1.14.6 (3,966 BTS/day)
5) (100,000 BTS/day)
6) (100,000 BTS/day)

That means that 1-4 get funded, 5 gets 86033.9, and 6 gets 0.

So, on your website you can list all proposals pending in order of votes, but indicate on their that 1-4 are funded, 5 is partial, and 6+ is not funded (like you do with active witnesses).

Worker created!
OP updated with info.
Thanks, if you have questions please post here

update_worker_votes maqifrnswa {"vote_for":["1.14.6"]} true

xeroc, I'll let you know when it's production ready. It's now fully functional, but still in testing

I don't get why people take the BTC price of BTS .. that makes no sense to me .. would anyone be so kind and enlighten me... please?

removes systemic noise, crypto currencies all tend to rise and fall together, to some degree. It's like saying a stock beat the S&P500 by 10%. That shows it is a strong company, even if the stock dropped.

Also, be careful not to equate rising BTS value with profit, they may not be correlated. A company can be profitable and still lose share value. BTS post 2.0 has been profitable (income exceeds expenses) even though share value declined.

---

To VOTE:
update_worker_votes ACCOUNTNAME {"vote_for":["1.14.6"]} true

As of now, no linux binaries of bitshares are available. This will fix that!

This worker will provide repositories for Debian based distributions for BitShares. Debian and Ubuntu are ready on both amd64 and i386. The worker will also implement Mint and extend to ARM processors (Raspberry Pi).

Preview and Installation Instructions:
http://162.243.185.205/
http://162.243.185.205/repos

Raspberry Pi Preview:
https://people.debian.org/~showard/raspbian/


They will be "official" since they are funded by the blockchain with voter approval.

What it does: Pulls from git every hour and checks for a new tag. If a new tag is present, new packages are built. Packages are gpg signed, md5sums are included in release files and signed. The Debian apt tool verifies md5sums and gpg key after download and before installation. Ubuntu packages are hosted and built on Canonical's Launchpad Service (ppa:bitshares/bitshares). Debian packages are built and hosted on the worker's VPS.

Qualifications: maqifrnswa is a Debian developer, has maintained a bitshares PPA for 1.5 years, was a delegate and a witness. maqifrnswa is the founder of the debian bitcoin team and is the maintainer of bitcoin in Debian and Ubuntu.

Internals/Security/Trust: The static pages will be SSL secured reduce chance of prevent man-in-the-middle attack. apt-get transport will follow standard distribution practices (over http). The package list, md5sums, and package info are GPG signed and will be verified automatically by apt's internal mechanisms. Sources are available for inspection via the "apt-get source" command and via the online repository.

Witness: maqifrnswa is currently running a witness. If this proposal is approved, maqifrnswa will serve as witness if needed by the network. If witness numbers should be reduced, maqifrnswa volunteers to be voted out.

Timeline: Prototype site already up and running for testing. Production-level site announced and running for Ubuntu and Debian by December. Mint and Raspbian/ARM by 2016 or early 2016. Future work to investigate: Automatically generate rpm from .deb packages and Ubuntu Snappy packages (container based Ubuntu packages).

Worker proposal costs:
$15/day (~3966 BTS)
New worker proposal every 3 months to adjust for price.
Breakdown:

• Servers: $80 monthly for front-end and back-end servers.
• Domain name: $15 one time
• SSL cert: free (startssl, just to prevent man-in-the-middle attack on the info page)
• Development time: $50/hour based on jobs at freelancer.com
• 10 hours: server set-up development of build scripts (done)
• 1 hour/week maintenance (new versions/bug fixing)
• New distributions and architectures are not included yet. They will add as development time based on actual time spent in future months

Daily expenses over 90 days:
[80*3+15+(10+1*12)*50]/90 = $15.05/day
Rounded down to $15/day

create_worker maqifrnswa "2015-10-28T00:00:00" "2016-01-31T00:00:00" 396600000 "Debian/Ubuntu-based PPA" "https://bitsharestalk.org/index.php/topic,19485.msg250031.html" {"type" : "vesting", "pay_vesting_period_days" : 0} true
get_object 1.14.6
[{
    "id": "1.14.6",
    "worker_account": "1.2.6004",
    "work_begin_date": "2015-10-28T00:00:00",
    "work_end_date": "2016-01-31T00:00:00",
    "daily_pay": 396600000,
    "worker": [
      1,{
        "balance": "1.13.279"
      }
    ],
    "vote_for": "2:80",
    "vote_against": "2:81",
    "total_votes_for": 0,
    "total_votes_against": 0,
    "name": "Debian/Ubuntu-based PPA",
    "url": "https://bitsharestalk.org/index.php/topic,19485.msg250031.html"
  }
]

good list, I too like xeroc.

Has anyone publicly declared an interest in  being on the committee?

@cryptosig: you can only ONCE claim your balances .. once they are claimed they are located in the account you claimed them to ..
since you claimed them already in the cli, all you need to do is import your account keys into the GUI wallet .. either by manually importing the owner and active key .. or by importing the 0.9.3c export

cryptosig, you said you did the owner key, but also you need the active key. Import that one as well if you haven't already

Me: DO NYC3 with my own hardware for failover