[Worker Proposal] Blockchain maintenance developer

[dannotestein]

@dannotestein what do you think about this idea: https://bitsharestalk.org/index.php?topic=19625.0

If you become a developer employed by community, would you stream your work? It would be additional promotion and knowledge sharing For sure I would watch it!

I'm heading to my parents today, but I'll take a look at the livestreaming in more depth when I get back tonight and see if it's something I can work with. One thing that I should make clear is that this worker isn't just really "me" (I'd be a mix of a manager who distributes and monitors work and a coder), so the livestreaming choice would be up to each individual (I'm certainly not comfortable to try to mandate anything like that).

[pc]

I've sent the official proposal to the blockchain. It can be found in the wallet under "Voting" in the Workers tab as "Blockchain maintenance developer".

For CLI users: 1.14.30

[noisy]

@dannotestein what do you think about this idea: https://bitsharestalk.org/index.php?topic=19625.0

If you become a developer employed by community, would you stream your work? It would be additional promotion and knowledge sharing For sure I would watch it!

[dannotestein]

I feel the current auti-dilution emotion in China community mainly come from:

1. BTS's price keeps in low level for long time.
2. no exciting news that convince shareholders/users that BTS have a good future.

even so, I don't agree to reject all the worker proposals, from my own opinion, I still would like to support the worker proposals with high priority demand, efficient work and fair price, on the other hand, I will keep neutral to or even reject the worker proposals with low priority demand, inefficient work or overrated price.

a little more constrictive financial policy is suitable to such a tough time?

In this case, I think the solution is simple. Vote for us, and see how we perform in 2-4 week time frame. If you don't like the results, remove your vote. One of the nice things about the worker system from the coin holder's point of view is it's very easy to "fire" a worker, without having to worry about any of the headaches that it causes for a normal business.

This "trial" approach might not work for large tasks, but it makes plenty of sense for a worker that is making small independent changes to the code base.

[bitcrab]

I feel the current auti-dilution emotion in China community mainly come from:

1. BTS's price keeps in low level for long time.
2. no exciting news that convince shareholders/users that BTS have a good future.

even so, I don't agree to reject all the worker proposals, from my own opinion, I still would like to support the worker proposals with high priority demand, efficient work and fair price, on the other hand, I will keep neutral to or even reject the worker proposals with low priority demand, inefficient work or overrated price.

a little more constrictive financial policy is suitable to such a tough time?

[dannotestein]

I've sent the official proposal to the blockchain. It can be found in the wallet under "Voting" in the Workers tab as "Blockchain maintenance developer". As a side note, as I just found this out: you need to press either Approve or Reject, and THEN you must press Publish Changes button at top of screen. I've suggested a change to this interface since it deeply confused me.

This https://github.com/cryptonomex/graphene-ui/issues/718? I've added some comments there.

Basically you're asking for $200 per day with weekends/holidays included. What's your hourly rate? Will you make daily/weekly work reports? The biggest obstacle here is how to validate/value your work.

As indicated previously, we would make monthly reports. Daily reports would just be insane, IMO. If someone wants to monitor more closely, they can always look to github commits, but I don't expect daily commits to github for many tasks (e.g. I expect the bandwidth consumption issue to take more than a day to solve). Also, a side point, since you mentioned weekends, for the past few years Eric and I both work partial days on weekends too (usually 2-7pm). It' a nice time to work, as there are fewer outside interruptions.

Imo you're a bit too optimistic about the worker.. Take it seriously. Politics matters. If bytemaster voted for your worker with no reason, will make a big trouble with Chinese community. If bytemaster doesn't vote, your worker is hard to be approved. Better do something first and apply for the worker later. Just my 2 cents.

I'm expecting BM to vote in favor of the proposal, but certainly not for "no reason". He's well aware of what we can do since we've worked with him since before BitShares even existed. And these rates are far below what we charged him (and the company he worked for prior to bitshares project) for past work, so he knows what a bargain it is.

Truthfully, I don't even to expect to clear any real direct profit from this worker, given the anticipated expenses in man hours and salary rates. The biggest benefit to BlockTrades will be gaining familiarity with new parts of the code base and having a better blockchain to build our businesses on.

[abit]

I've sent the official proposal to the blockchain. It can be found in the wallet under "Voting" in the Workers tab as "Blockchain maintenance developer". As a side note, as I just found this out: you need to press either Approve or Reject, and THEN you must press Publish Changes button at top of screen. I've suggested a change to this interface since it deeply confused me.

This https://github.com/cryptonomex/graphene-ui/issues/718? I've added some comments there.

Basically you're asking for $200 per day with weekends/holidays included. What's your hourly rate? Will you make daily/weekly work reports? The biggest obstacle here is how to validate/value your work.

Imo you're a bit too optimistic about the worker.. Take it seriously. Politics matters. If bytemaster voted for your worker with no reason, will make a big trouble with Chinese community. If bytermaster doesn't vote, your worker is hard to be approved. Better do something first and apply for the worker later. Just my 2 cents.

[dannotestein]

I've sent the official proposal to the blockchain. It can be found in the wallet under "Voting" in the Workers tab as "Blockchain maintenance developer". As a side note, as I just found this out: you need to press either Approve or Reject, and THEN you must press Publish Changes button at top of screen. I've suggested a change to this interface since it deeply confused me.

[bitacer]

This looks like a Keynesian model that is implemented nicely and fairly. Like building highways for everybody's benefit. Money comes from the reserves, its not like those sneaky IOU cryptos or UIAs penetrate into the system, imo those are the dilution.

[bitacer]

This is nice, DAC is working ! 

[jakub]

I would support this proposal.

[dannotestein]

Theo and I were discussing what kinds of issues we think should be tackled by this worker proposal based on the current github issues, and we came up with these general categories:

- minor bugfixes
- performance issues (websocket spaming is a high priority one, as this can seriously affect mobile web browsers)
- more unit tests (many are pending as issues in github now). Both of the last two network halts could have been potentially averted by more unit tests.
- Code cleanup (poor coding techniques, inconsistent coding methods, naming conventions, etc)
- BlockChain-level documentation
- cli_wallet maintenance (there's several issues related to the current API caching used by the cli wallet)
- minor features

[abit]

We'll put together a list of some of the problems we would address near term, but one of the ones that stood out for me was the high data spamming across the websocket that was stressing mobile web browsers.

Great.

[donkeypong]

I would support this proposal.

[dannotestein]

I'm fine with the worker pay being denominated in BTS rather than a usd/euro equivalent. If we see a significant appreciation in the value of BTS, we can increase the amount of work we do (and I think BTS is near its low side now). It's relatively easy for BlockTrades to convert pay to different forms as required by different contractors.

We'll put together a list of some of the problems we would address near term, but one of the ones that stood out for me was the high data spamming across the websocket that was stressing mobile web browsers.