0 Members and 1 Guest are viewing this topic.
- Full time worker proposal. 8 hours per day Monday to Friday. 40 hs per week.- 40 usd per hour. 320 usd per day. 1600 usd per week.- Duration. 6 months.
Quote from: xeroc on June 21, 2017, 09:46:06 amQuote from: oxarbitrage on June 18, 2017, 01:12:33 pm- Full time worker proposal. 8 hours per day Monday to Friday. 40 hs per week.- 40 usd per hour. 320 usd per day. 1600 usd per week.- Duration. 6 months.!!! I'll vote for that
Quote from: oxarbitrage on June 18, 2017, 01:12:33 pm- Full time worker proposal. 8 hours per day Monday to Friday. 40 hs per week.- 40 usd per hour. 320 usd per day. 1600 usd per week.- Duration. 6 months.!!!
My worker was not directly managed by me but actually by bitshares munich,. more specifically by Chris. Chris paid me part of the worker and now i should get the rest of it until the day it was stopped. I already pointed it to chris and he will send the rest to my account soon.
thanks for the updates. Keep up the good work Alfredo.
D Task: 0.025%, means bounty amount = 93,750 BTS
In my opinion the worker proposal system is fine the way it is... It is similar to the way many companies compensate their employees, via stock options. It provides incentive for the developers to do good work and promote the ecosystem.Startups provide stock based compensation because it works. It brings in the best talent, because it promotes greed. Also, it's not like this recent price pump didn't factor in the worker proposal system. The market knew that the dev's would get a dramatic bump in salary but bought anyway.
Quote from: ripplexiaoshan on December 18, 2016, 06:20:24 pmA normal flow of bounty is: Shareholders feedback the demand firstly, then the committee is responsible for summarizing these demands and organizing voting to create bounty, then waiting for people to submit their work, then shareholders decide whether the work is qualified for bounty or not.刚想到一个 bounty 金额由投票决定的思路:首先,根据 bounty 任务的难度和工作量进行分级,给定不同的赏金系数。任务等级分类参考(从高到低):QuoteSS级:也是最高级,在不同地方用法不同,但通常在关乎生死存亡阶段使用。属于只许成功不许失败的任务。S级:此类任务通常不被使用,这类任务一般是关乎上级或者公司的直接利益的任务。A级:使用较为频繁,通常是于珍贵物品或上级人物直接或间接挂钩。B级:使用最为频繁的一类任务。也是最常见的一类任务。C级:较为简单的任务。也是除了SS级最少发的任务。D级:作为最简单的任务,这类人物属于刚加入的新手。也被叫做休闲任务。以当前的“预算项目(worker)”投票情况来说,#1 worker 获得 375,721,810 BTS支持。我们可以以此为基础来确定每一个任务的 bounty 赏金系数。例如:SS 级任务:1%,意味着 bounty 金额为:375w BTSS 级任务:0.5%,意味着 bounty 金额为:187.5w BTSA 级任务:0.25%,意味着 bounty 金额为:93.75w BTSB 级任务:0.1%,意味着 bounty 金额为:37.5w BTSC 级任务:0.05%,意味着 bounty 金额为:18.75w BTSD 级任务:0.025%,意味着 bounty 金额为:9.375w BTS其次,有两种方案来投票确定每一个任务的 bounty 赏金额度:方案一:股东投票决定奖金额度创建一个预算项目(worker),根据任务等级描述 bounty 系数,系数乘以支持该任务的总票数等于完成任务后可领取的 BTS 数量。方案二:基础悬赏金额 + 额外奖励由理事会根据任务难度议定 bounty 基础金额(在比特股这家公司里面,理事会成员的责任感更强,要么是大股东,要么看好公司前景,理事会来商定 bounty 的基础金额是有说服力的)。额外的奖赏额度则由全体股东投票,同样采用方案一的方式,但 bounty 系数要降低到大约 1/10,系数乘以支持该任务的票数等于额外奖赏。在任务进行中,领取任务者随时公布动态,股东根据情况予以投票支持(类似打赏),额外的奖赏代表股东对该任务完成度的认可度!在上面的两个方案中,BTS 股东支持这个项目就投票,投票就代表愿意稀释(从储备资金池支取 BTS),每一票(每一股 BTS)都代表要花钱,每一票都代表股东的意愿。至于手里总共有 100w 票但只想出 30w 票权重的投票支持,那就自己单独把 300w 票现转到自己的小账号里去投票支持对应的 bounty 项目。以上想法,仅供交流讨论!I've just had a great idea that could determine the amount of bounty for each task by the VOTE of BTS holders:First of all, according to the classification of bounty task difficulty and workload, given different reward coefficient. Task level from high to low like this:QuoteSS: Highest tasks, is of vital importance must not fail.S: Super tasks, related to the vital interests of the company.A: Major tasks.B: Frequent tasks.C: Relatively simple tasks.D: The simplest tasks, leisure tasks.In the current project proposal vote situation, #1 worker got 375,721,810 BTS support, we can use this result as a base to determine the bounty coefficient for each task.For EXAMPLE:SS Task: 1%, means bounty amount = 3,750,000 BTSS Task: 0.5%, means bounty amount = 1,875,000 BTSA Task: 0.25%, means bounty amount = 937,500 BTSB Task: 0.1%, means bounty amount = 375,000 BTSC Task: 0.05%, means bounty amount = 187,500 BTSD Task: 0.025%, means bounty amount = 93,750 BTSThen, voting to determine the amount of bounty for each task in two ways:Plan A: only BTS holders vote to determine the amountCreat a project proposal(worker), describe the task level and the bounty coefficient,[total number of votes]*[bounty coefficient]=[the amount of BTS for bounty].Plan B: Basic task reward + Extra bonusCommittee discuss to determine the basic reward according to the difficulty of the task( in the Company, BitShares DAC, committee members are more responsible, because they are either major shareholders, or is extremely optimistic about the prospects of BitShares, they discuss the amount of the decision is convincing).Extra bonus can refer to Plan A to creat a project proposal(worker), but need to reduce the coefficient to about 1/10, [basic task reward]+[total number of votes]*[bounty coefficient]=[the amount of BTS for bounty].In the task, at any time to publish the dynamic, BTS holders to vote according to the circumstances, extra bonus on behalf of shareholders to the task completion degree of recognition.In Plan A and B, BTS holders who support the bounty task, vote it. Vote for it means they they are willing to accept dilution ( agree to withdraw BTS from reserve pool), 1 BTS 1 vote, each BTS vote represents the wishes of shareholders. If I have 1,000,000 BTS in my account A, but I only want to vote it 300,000 BTS, I can transfer 300,000 BTS to account B then vote it.Above is my idea for exchange discussion.
A normal flow of bounty is: Shareholders feedback the demand firstly, then the committee is responsible for summarizing these demands and organizing voting to create bounty, then waiting for people to submit their work, then shareholders decide whether the work is qualified for bounty or not.
SS级:也是最高级,在不同地方用法不同,但通常在关乎生死存亡阶段使用。属于只许成功不许失败的任务。S级:此类任务通常不被使用,这类任务一般是关乎上级或者公司的直接利益的任务。A级:使用较为频繁,通常是于珍贵物品或上级人物直接或间接挂钩。B级:使用最为频繁的一类任务。也是最常见的一类任务。C级:较为简单的任务。也是除了SS级最少发的任务。D级:作为最简单的任务,这类人物属于刚加入的新手。也被叫做休闲任务。
SS: Highest tasks, is of vital importance must not fail.S: Super tasks, related to the vital interests of the company.A: Major tasks.B: Frequent tasks.C: Relatively simple tasks.D: The simplest tasks, leisure tasks.
i agree that future worker proposals by me or actually by anyone should be in usd. i never had the intention to speculate here, the fact is i found at with all this by pure luck. i have no problem on closing current proposal now and go with a new one if needed. in the other hand the extra compensation will be used to bring more value to the community by working more, much more happy. it is hard to quantify this additional value in money but you can be sure i will be always grateful with this community and be forever loyal.this is a new milestone in my life and my professional career that will definitely want to develop here, not only for the payment of the current worker, i made a commitment with myself pretty much since i started, i want to be here.will i make the same work for less money ? a reasonable hourly rate ? probably. but living with a rope in the neck every month is hard and stressfull, the worker money at current bts prices will remove big pressure i have over my shoulders while at the same time finish my new office and buy new equipment. this will bring value, i am not going to be needing to make extra businesses for extra money, fully dedicated to bitshares with everything i have.will i enjoy my new computer equipment to lets say watch a movie ? of course i will, but the important is that i will use it for work in bitshares, will improve productivity.i don't want to spend more of your time on why i will like to leave the worker proposal as it is, it is obvious that i need/want the money but the decision is yours and whatever you decide i will agree with it.
Quote from: Chris4210 on May 13, 2017, 09:11:47 am@fav, Please see the initial proposal. The worker is quoted in BTS, not in USD.quoting again for visibility.QuoteThis Proposed 6-month Worker will cost Bitshares 1,630,835 BTS (~4800 USD)*BitShares Munich will pay the other half, ~4800 USDusing the logic "quoted in BTS" - I'm still missing a second 1100000 BTS transaction from @Chris4210 since they agreed on paying the other half.
@fav, Please see the initial proposal. The worker is quoted in BTS, not in USD.
This Proposed 6-month Worker will cost Bitshares 1,630,835 BTS (~4800 USD)*BitShares Munich will pay the other half, ~4800 USD
If BitShares Munich had not been involved, and the contract was between Alfredo himself and BitShares 2.0 shareholders, then the terms would be simple."Complete work to the subjective satisfaction of the BitShares shareholders and you will receive x bts per month."Then after a huge price rise, shareholders may find it prudent to renegotiate the employment contracts it holds with employees. Should this worker proposal, employing Alfredo, be voted out?The Shareholders could then wait patiently for a new proposal with payment in bitUSD to be submitted by Alfredo.Depending on his demands for compensation I am sure the shareholders will be pleased to re-hire a talented BitShares literate core dev.
I think they made the dill with Alfredo in USD and accepted the risk of BTS fluctuations. Otherwise worker would be payed to Alfredo's account. They probably made new arrangement with Alfredo since BTS has appreciated. Alfredo probably accepted that generous offer. Who wouldn't? As far as Bitshares concern the dill is clear. Same is related for all payments from Bitshares blockchain. Regarding management of Bitshares company, it is bad dill. That is why we spend so many discussions regarding witness and workers pay denominated in bitUSD.Next time pay closer attention to those discussions and act accordingly.
@xeroc is paid with bitUSD.https://bitsharestalk.org/index.php/topic,23770.0.htmlhttp://cryptofresh.com/u/multisig-worker-2017-01BTW Just noticed that escrow account has set its own proxy which perhaps shouldn't be: that BTS doesn't belong to them.Quote Every thing that is not paid out after the end of the worker will be settled and returned to the reserve fund
Every thing that is not paid out after the end of the worker will be settled and returned to the reserve fund
hello guys, Alfredo here
Quote from: Chris4210 on May 13, 2017, 09:11:47 amAlfredo fully deserves his payout, since he worked many hours for the BitShares community as core dev and is highly motivated to continue. Good job!@fav note that $20/hr is far below market rate for a skilled developer, plus Alfredo was taking a risk AND showing his commitment by accepting payment in BTS.
Alfredo fully deserves his payout, since he worked many hours for the BitShares community as core dev and is highly motivated to continue.
Quote from: Chris4210 on January 11, 2017, 08:33:22 pmDear BitShares Stakeholder,We would like to introduce a new worker proposal that pays for a new BitShares core dev.Please vote for Worker 1.14.49: Alfredo Garcia, Bitshares Core Dev This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for. Worker DetailsTotal Cost of hiring Alfredo: 3,261,671 BTS (~9600 USD at $20/hr)This Proposed 6-month Worker will cost Bitshares 1,630,835 BTS (~4800 USD)*BitShares Munich will pay the other half, ~4800 USDWorker Lifetime: 6 months, (Jan 23 - Jul 23, 2017)Working Hours: 20h per weekWorker focus on the 190 Github Issues, and new BitShares features from BitShares Roadmap@fav, Please see the initial proposal. The worker is quoted in BTS, not in USD.I agree with you if the worker would have been quoted in USD, then the leftover BTS would have been burned or repaid to the pool. That is not the case with this worker.Alfredo fully deserves his payout, since he worked many hours for the BitShares community as core dev and is highly motivated to continue. If the future BitShares workers should be nominated in BTS or in BitUSD like Xeroc´s worker is up to all of us to decide.
Dear BitShares Stakeholder,We would like to introduce a new worker proposal that pays for a new BitShares core dev.Please vote for Worker 1.14.49: Alfredo Garcia, Bitshares Core Dev This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for. Worker DetailsTotal Cost of hiring Alfredo: 3,261,671 BTS (~9600 USD at $20/hr)This Proposed 6-month Worker will cost Bitshares 1,630,835 BTS (~4800 USD)*BitShares Munich will pay the other half, ~4800 USDWorker Lifetime: 6 months, (Jan 23 - Jul 23, 2017)Working Hours: 20h per weekWorker focus on the 190 Github Issues, and new BitShares features from BitShares Roadmap
Dear BitShares Community,today I got some awesome news for you all. After a few talks with Alfredo, Xeroc and others we came to the conclusion that Alfredo has become a very valuable member of our community and his past few months of hard work have paid off. Alfredo is now an active member of our BitShares community and has contributed a lot to the BitShares code base, its security and its future.I am happy to transfer Alfredo the first part of his BTS worker salaries for the time frame: January 23th, 2017 to May 13th, 2017.In total: 1,180,210 BTSOutstanding: -450,625 BTSIn total: 1,630,835 BTShttp://cryptofresh.com/tx/86f46f20f741d67191626cb361692d9fbdd34fa1Next payout day: July 26th, 2017Thank you all for your support for Alfredo´s worker and I am looking forward to more of his great work.Best regards,Christoph
I have great faith in Ken and support this worker, especially for this price. I think BitShares should encourage as much new developer activity as it can.
Quote from: Chris4210 on January 11, 2017, 08:33:22 pmAlfredo is under the supervision of, and reports daily to @kenCode at BitShares Munich. As you guys know, I am kind of a hardass. I will fire as fast as I hire, I have zero patience for slackers, so rest assured that the rest of my team will also be security auditing his work just like the other products that we have audited recently. Github issues, mem leaks, wiresharking, the works. Getting a Core Dev for 6 months, for only ~$5K is a sweetheart deal. Please vote for Alfredo, and as always my updates will be posted on his progress every week.
Alfredo is under the supervision of, and reports daily to @kenCode at BitShares Munich.
Quote from: santaclause102 on January 12, 2017, 03:38:26 pmThis is really great!! Thanks a lot for the initiative! I will update my proxy to whoever votes for this if necessary. Feedback / questions: 1) Is there public information about Alfredo Garcia available besides his name? LInkedin, github etc?2) I can not finally judge this as I am not a developer but did you think about a third party code reviewer such as Cryptonomex or Bunkerchainlabs? Or does Bitshares Munich hire one anyway? If so it would be nice if the results of these reviews and who did the review would be public as well. In the end such a review is effective if the reviewer has a reputation (to loose). 1) No. Have faith in me and my team, I hope my track record speaks for itself at this point. I only work with the brightest minds in the world. 2) We have auditors on staff, and I always encourage the public to audit our code as well on my github repos. I totally agree with you about reviews too and welcome them here.
This is really great!! Thanks a lot for the initiative! I will update my proxy to whoever votes for this if necessary. Feedback / questions: 1) Is there public information about Alfredo Garcia available besides his name? LInkedin, github etc?2) I can not finally judge this as I am not a developer but did you think about a third party code reviewer such as Cryptonomex or Bunkerchainlabs? Or does Bitshares Munich hire one anyway? If so it would be nice if the results of these reviews and who did the review would be public as well. In the end such a review is effective if the reviewer has a reputation (to loose).
Quote from: Geneko on January 12, 2017, 06:25:28 pmBeside subsidized request, kencode has offered us his reputation. In my opinion and with all respect to others, it is worth more.It's funny, because KenCode had quite a poor reputation here a couple years ago. He was accused of scamming Floridans with a fraudulent gun school. There was an entire website with details about it. He was also accused of running a solar panel scam in 2007, where he never shipped the panels to buyers. More details can be found through a simple web search.It's remarkable how that has changed. Thanks for sticking around, @kenCode!
Beside subsidized request, kencode has offered us his reputation. In my opinion and with all respect to others, it is worth more.
Quote from: bitcrab on January 12, 2017, 08:53:55 amQuote from: BunkerChain Labs on January 12, 2017, 01:12:40 amQuote from: Chris4210 on January 11, 2017, 08:33:22 pmThis Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for. What exactly does this mean? There is room for a lot of clarifiaction:Issues in github? There are plenty to go for a while, which ones are planned for with what milestones?What new features specifically has the community been asking for?Without a clear plan for work inefficiency creeps. Looking forward to the reply.exactly, please give the detail of the new features in the develop plan, there should be a process for the community to agree on adding new features.I will post a roadmap for this worker. We want to start with the long issue list on Github first, and then move into building new features. Which features we should build will be discussed in the forum, and on the mumble. Here is the latest feature list for the BitShares Blockchain. I collected most different ideas from chat, mumble and old forum posts/roadmaps.The goal is to keep the list updated, and vote in the forum/mumble about the next feature.https://docs.google.com/spreadsheets/d/1kgTYNEeqYP8xrEKBs2L0uc52xjQCPURuigI2CIplEtE/edit?usp=sharing@ken can give a direct roadmap which of the 190 open github issues we are planning to fix first.
Quote from: BunkerChain Labs on January 12, 2017, 01:12:40 amQuote from: Chris4210 on January 11, 2017, 08:33:22 pmThis Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for. What exactly does this mean? There is room for a lot of clarifiaction:Issues in github? There are plenty to go for a while, which ones are planned for with what milestones?What new features specifically has the community been asking for?Without a clear plan for work inefficiency creeps. Looking forward to the reply.exactly, please give the detail of the new features in the develop plan, there should be a process for the community to agree on adding new features.
Quote from: Chris4210 on January 11, 2017, 08:33:22 pmThis Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for. What exactly does this mean? There is room for a lot of clarifiaction:Issues in github? There are plenty to go for a while, which ones are planned for with what milestones?What new features specifically has the community been asking for?Without a clear plan for work inefficiency creeps. Looking forward to the reply.
This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for.
Quote from: btswildpig on January 12, 2017, 04:40:28 pmi feel more comfortable to pay someone who is willing to take financial risk with bitshares to perform work on bitshares rather seeing it as a work place. kencodeI totaly agree.As I understand proposition, it would be undefined overlap between existing workers, Soledgers, Svks and future Alfredo Garcias.How they will divide jobs and responsibilities. BTW what are jobs and responsibilities of current workers? Is there any clear road map for them. Can we track and measure theirs accomplishments?Only one thing to tell about that, the accomplishment that isn't measured, it isn't improving. I like the way @kenCode manages his projects, specially reports about his work. It should be "minimum standard behavior" for all Bitshares Workers. Finally it is good thing for workers to compete between each other or find common ground and collaborate.Either way community is on gain.Beside subsidized request, kencode has offered us his reputation. In my opinion and with all respect to others, it is worth more.
i feel more comfortable to pay someone who is willing to take financial risk with bitshares to perform work on bitshares rather seeing it as a work place. kencode
What new features specifically has the community been asking for?
Without a clear plan for work inefficiency creeps.
Note from Chris4210:We are calculating with a stable BTS price of 0.0033 BTS/USD, including a small security buffer for BTS price, voting volatility, etc. The Worker funds will be paid to our BitShares Munich (bitshares-munich-devs) account, and we will manage the regular monthly payouts to Alfredo.