BitShares Forum
Main => Stakeholder Proposals => Topic started by: wmbutler on August 03, 2017, 04:59:48 pm
-
Thanks for your consideration:
http://www.bitshares.foundation/workers/2017-08-bill-butler
-
does this include:
* work on open source explorer gui ( @oxarbitrage )
* chrome push alerts
referral:
* overwork, better stats
* tailored landing pages for marketers
edit:
* where's can I check other projects/design portfolio
* why is there no mockup/first idea
-
does this include:
* work on open source explorer gui ( @oxarbitrage )
I don't think so:
https://bitsharestalk.org/index.php/topic,24097.msg309466.html#msg309466
Worker proposal '1.14.55' covers the open source explorer, not this thread's worker proposal.
-
This is an excellent worker proposal focusing on what bitshares currently need more - became the best and most used exchange in the world. in order to do it, a lot of work has to be done in the official bitshares UI( the dex). the core code is pretty much covered by now and there is a lot of stuff that can be done with what it is currently available. the core team can and will join efforts with the ui team to have new features, changes, etc.
in order to became the best exchange, trading need to be easy, clean, bug free, professional and familiar. the only way to do it is with hard long term work.
with @svk in the team i am confident all needed will be done, i listened to Bill yesterday in the hangout and it looks like a great addition to the team to organize the requests, documentation, be more on front against public and sigve more in the back as i know by own experience that developing and giving support at the same time is crazy, specially with live stuff.
in short , all the luck, i hope this can be voted in, my votes are insignificant but i voted for the proposal.
-
does this include:
* work on open source explorer gui ( @oxarbitrage )
Yes, this proposal outlines the steps we will take to remove bugs and improve usability with input and feedback from the bts community.
* chrome push alerts
That has not been specifically requested, but if push alerts are important to you, I'd suggest you create a github issue, open a discussion so we can move it into a milestone.
* overwork, better stats
I don't know what this means.
* tailored landing pages for marketers
This has not been posted as a desired issue on the UI, but the work performed for the UI could certainly include this if it were posted, discussed and prioritized.
* where's can I check other projects/design portfolio
I don't have a design portfolio. This isn't a UX proposal, it's a general maintenance for the UI proposal. I have 25 years of experience managing various teams. I will not be handing designs down from on high. Rather, I plan to propose designs that can be discussed and iterated on consistently and methodically.
* why is there no mockup/first idea
Because a mockup is putting the cart waaay before the horse in my opinion. A mockup provides a false sense of security. This worker proposal is not about drawing pretty pictures. It's about creating a stable, bug free framework upon which to build an intuitive user experience.
-
+5% very important worker, please vote.
we need to improve the reference wallet now.
@bitcrab
-
I have one concern:
will this worker proposal plan to do something to optimize the performance of the UI?
I have discussed with some developers, I was told that there are some issues in the UI which caused low performance, for example, someone told that he found when one summit one operation in the GUI, about 20 requests will be sent to API server, some other designs, such as how the charts update, may also lower the performance.
some even conclude that without redesign of the UI infrastructure it do not have a good furture. very limited clients with such UI can access an api server concurrently.
@alt even begin a project with meteor+mongodb+ddp protocol to build a service that can serve wallet to get high performance, mobile wallet - ICOWALLET will adopt this infrastructure.
I am not sure that I describe the issue exactly but I feel before we decide to upgrade the UI we need to consider this issue and decide whether and how to handle it.
-
I have one concern:
will this worker proposal plan to do something to optimize the performance of the UI?
I have discussed with some developers, I was told that there are some issues in the UI which caused low performance, for example, someone told that he found when one summit one operation in the GUI, about 20 requests will be sent to API server, some other designs, such as how the charts update, may also lower the performance.
some even conclude that without redesign of the UI infrastructure it do not have a good furture. very limited clients with such UI can access an api server concurrently.
@alt even begin a project with meteor+mongodb+ddp protocol to build a service that can serve wallet to get high performance, mobile wallet - ICOWALLET will adopt this infrastructure.
I am not sure that I describe the issue exactly but I feel before we decide to upgrade the UI we need to consider this issue and decide whether and how to handle it.
To get there, we need to improve the backend API of Bitshares which is what Alfredo is already working on. I cannot link to an actual github issue but i can remember some discussion about
improving API calls and making it easier to get all the data.
Also, we have the get_full_accounts API call which should provide you with almost everything you need.
Additionally, I personally want to work on an API/plugin to integrate one of my personal projects with, but I am still learning C++ ..
-
Our worker proposal is intentionally open ended so we have the flexibility to address the issues that are most pressing to the community. It appears that the part of the concern is that a community sanctioned wallet would essentially compete with the efforts of abit. It's our belief that incremental improvements to the existing wallet would be a faster path to adoption, but of course without community support it's unlikely it will ever happen.
Many people have put in hours of work without being fairly compensated. Our team agrees that this is not the path forward. We would welcome paying anyone who submitted PR's that were accepted into the reference wallet.
-
I have one concern:
We are losing market shares to the competition because of imminent problems in the reference Client.
A single GUI server may be not be scalable enough to support thousands of users right now but we have more urgent tasks to address in the current reference client where people are complaining daily about UX problems and bugs.
Working on these important issues is not blocking anyone from coming up with a completely new and better GUI but at least in the western hemisphere we only have the reference GUI right now.
And besides the actual work, new and existing shareholders do want to see actual progress on the reference wallet and have a team of developers constantly improving BitShares and the reference Client is what most users do see when they come try BitShares.
vote for adoption, vote for growth, vote for BitShares
-
@bitcrab I believe you are referring to this issue: https://github.com/bitshares/bitshares-ui/issues/202
It's on the first sprint to resolve.
-
We are losing market shares to the competition because of imminent problems in the reference Client.
A single GUI server may be not be scalable enough to support thousands of users right now but we have more urgent tasks to address in the current reference client where people are complaining daily about UX problems and bugs.
Working on these important issues is not blocking anyone from coming up with a completely new and better GUI but at least in the western hemisphere we only have the reference GUI right now.
And besides the actual work, new and existing shareholders do want to see actual progress on the reference wallet and have a team of developers constantly improving BitShares and the reference Client is what most users do see when they come try BitShares.
vote for adoption, vote for growth, vote for BitShares
+5%
-
@bitcrab I believe you are referring to this issue: https://github.com/bitshares/bitshares-ui/issues/202
It's on the first sprint to resolve.
thanks, my concern is not the compete between different wallets, but whether the community sanctioned development is on the right way, we need to try to avoid wasting resources.
I'll try to collect more info and then give my opinion soon.
-
@bitcrab I believe you are referring to this issue: https://github.com/bitshares/bitshares-ui/issues/202
It's on the first sprint to resolve.
thanks, my concern is not the compete between different wallets, but whether the community sanctioned development is on the right way, we need to try to avoid wasting resources.
I'll try to collect more info and then give my opinion soon.
can we get the two parties work together? pretty sure part of the money can be used to pay a 4th person
-
What if we formally modified the proposal to state that anyone in the community could claim an issue and work it for a bounty.
For example, we could attach a dollar value to each issue and members could submit a PR and be paid the bounty amount for each issue. This would open the process to anyone who had the necessary technical skills to resolve the issue? Would this strategy allow you, @bitcrab, to support the proposal?
EDIT:
In essence, this would turn the worker proposal into a UI development fund.
-
Who really cares if you outsource your worker or do all the job yourself, as long as the job gets done?
-
Do you mean something like https://tip4commit.com or https://peer4commit.com?
-
I can't find clear target for this worker.
what I concern about the wallet include:
1. efficient.
currently only 100 client support with a 32G mem VPS node.
will this wallet support at least 10K users in the future?
don't told me this is backend guy's work.
if so, you should find partner who can improve backend, and work together.
as share holder, we need a complete solution, not some lego toy.
2. user friendly.
this is very difficult to verify.
but what make user friendly very difficult because of most ui developer can't follow the wallet.
because the UI code mixed up with many blockchain code.
will you make the UI completely independency from the blockchain tec?
3. more function
I have no idea why we need a seperate exploere like cryptofresh.com
all we need can implement in the wallet.
can you expand more function in the wallet? what's the plan?
-
I can't find clear target for this worker.
what I concern about the wallet include:
1. efficient.
currently only 100 client support with a 32G mem VPS node.
will this wallet support at least 10K users in the future?
don't told me this is backend guy's work.
if so, you should find partner who can improve backend, and work together.
as share holder, we need a complete solution, not some lego toy.
2. user friendly.
this is very difficult to verify.
but what make user friendly very difficult because of most ui developer can't follow the wallet.
because the UI code mixed up with many blockchain code.
will you make the UI completely independency from the blockchain tec?
3. more function
I have no idea why we need a seperate exploere like cryptofresh.com
all we need can implement in the wallet.
can you expand more function in the wallet? what's the plan?
1.Thats a backend issue so to resolve that we have to depend on Alfredo Garcia and the others working on the backend. That's also the case for @bitcrab concerns about GUI performance and api calls:its a backend issue.
2.The code is bog standard react + flux, with most of the blockchain code already split into a separate library (bitsharesjs)
3. A block explorer needs data that's not available from the witness_node, so replacing cryptofresh.com would require a whole new backend layer.
The current explorer parts could certainly improved however.
-
1. efficient.
so the wallet can't support more clients without backend improve?
who will fix this? when?
2. code clean
here is some code from component chat.jsx,
it is just a simple chat component, why I need to understand accountstore, chainstore, fetchchainobjects?
it's not a clean user interface component. it's difficut for reuse these component.
import React from "react";
import { connect } from "alt-react";
import AccountStore from "stores/AccountStore";
import Translate from "react-translate-component";
import Icon from "../Icon/Icon";
import {ChainStore} from "bitsharesjs/es";
import {debounce} from "lodash";
import SettingsActions from "actions/SettingsActions";
import SettingsStore from "stores/SettingsStore";
import Peer from "peerjs";
import utils from "common/utils";
import counterpart from "counterpart";
import LoadingIndicator from "../LoadingIndicator";
import AccountActions from "actions/AccountActions";
import TransactionConfirmStore from "stores/TransactionConfirmStore";
import {FetchChainObjects} from "bitsharesjs/es";
import TimeAgo from "../Utility/TimeAgo";
3. more function.
you have said we can't get more functions with current backend, so let's move to new backend.
more early more good.
I can't find clear target for this worker.
what I concern about the wallet include:
1. efficient.
currently only 100 client support with a 32G mem VPS node.
will this wallet support at least 10K users in the future?
don't told me this is backend guy's work.
if so, you should find partner who can improve backend, and work together.
as share holder, we need a complete solution, not some lego toy.
2. user friendly.
this is very difficult to verify.
but what make user friendly very difficult because of most ui developer can't follow the wallet.
because the UI code mixed up with many blockchain code.
will you make the UI completely independency from the blockchain tec?
3. more function
I have no idea why we need a seperate exploere like cryptofresh.com
all we need can implement in the wallet.
can you expand more function in the wallet? what's the plan?
1.Thats a backend issue so to resolve that we have to depend on Alfredo Garcia and the others working on the backend. That's also the case for @bitcrab concerns about GUI performance and api calls:its a backend issue.
2.The code is bog standard react + flux, with most of the blockchain code already split into a separate library (bitsharesjs)
3. A block explorer needs data that's not available from the witness_node, so replacing cryptofresh.com would require a whole new backend layer.
The current explorer parts could certainly improved however.
-
What if we formally modified the proposal to state that anyone in the community could claim an issue and work it for a bounty.
For example, we could attach a dollar value to each issue and members could submit a PR and be paid the bounty amount for each issue. This would open the process to anyone who had the necessary technical skills to resolve the issue? Would this strategy allow you, @bitcrab, to support the proposal?
EDIT:
In essence, this would turn the worker proposal into a UI development fund.
This attitude is remarkable to me.
What about including someone like @zahomu (https://steemit.com/bitshares/@billbutler/translated-by-zhaomu-l), to ensure that development is equally beneficial to all, e.g. translating github issues and communicating chinese <==> english fundamentals when needed.
A complete solution would be to pair this worker proposal with a similar one to improve APIs performance.
@abit, would you accept a well paid worker to lead the development of a node plugin that records the most required data into a more efficient data structure? please?
-
A complete solution would be to pair this worker proposal with a similar one to improve APIs performance.
@abit, would you accept a well paid worker to lead the development of a node plugin that records the most required data into a more efficient data structure? please?
What about you @alt? Would you accept such a proposal? Or even better, can you introduce your team that is willing to do it for free? ;)
Since the UI is decoupled from backend API, we don't need to implement it at the same time. It still makes sense to improve UI before improving backend API performance. Should we create a BSIP for it?
-
I have introduce my architecture which already used by btsbots.com
just fetch all transactions from witness_node, process all data, generate new data, save it to mongodb.
mongodb is the new backend, it can be expand with a slave node easy.
nodejs get all data from mongodb, it's just a very common nodejs web project, no blockchain tec need for UI developer.
you can hire any reactjs developer to improve/custom your wallet.
you can get the source for btsbots.com: https://github.com/pch957/btsbots-demo-2016
icowallet is a Chinese team who develop a new wallet based the new architecture: https://www.icowallet.net/
they have their business plan, are funded with a ICO, and will open source their wallet in the future.
I will continue contribute to the new architecture, but not as a worker, as a volunteer.
-
I have introduce my architecture which already used by btsbots.com
just fetch all transactions from witness_node, process all data, generate new data, save it to mongodb.
mongodb is the new backend, it can be expand with a slave node easy.
nodejs get all data from mongodb, it's just a very common nodejs web project, no blockchain tec need for UI developer.
you can hire any reactjs developer to improve/custom your wallet.
you can get the source for btsbots.com: https://github.com/pch957/btsbots-demo-2016
icowallet is a Chinese team who develop a new wallet based the new architecture: https://www.icowallet.net/
they have their business plan, are funded with a ICO, and will open source their wallet in the future.
I will continue contribute to the new architecture, but not as a worker, as a volunteer.
who is gonna fork icowallets tech, test and implement it? who can audit? or do you expect this happens for free as well?
-
I have introduce my architecture which already used by btsbots.com
just fetch all transactions from witness_node, process all data, generate new data, save it to mongodb.
mongodb is the new backend, it can be expand with a slave node easy.
nodejs get all data from mongodb, it's just a very common nodejs web project, no blockchain tec need for UI developer.
you can hire any reactjs developer to improve/custom your wallet.
you can get the source for btsbots.com: https://github.com/pch957/btsbots-demo-2016
icowallet is a Chinese team who develop a new wallet based the new architecture: https://www.icowallet.net/
they have their business plan, are funded with a ICO, and will open source their wallet in the future.
I will continue contribute to the new architecture, but not as a worker, as a volunteer.
this is very interesting, i had in mind to store bitshares data in a mongodb, i saw a steem project making it but never knew it was already done for bitshares. this will allow all kind of user apps to be done without knowing anything about blockchain technology.
probably a topic to discuss in a different thread but i will be happy to fork, test, create some documentation and such.
-
I have introduce my architecture which already used by btsbots.com
just fetch all transactions from witness_node, process all data, generate new data, save it to mongodb.
mongodb is the new backend, it can be expand with a slave node easy.
nodejs get all data from mongodb, it's just a very common nodejs web project, no blockchain tec need for UI developer.
you can hire any reactjs developer to improve/custom your wallet.
you can get the source for btsbots.com: https://github.com/pch957/btsbots-demo-2016
icowallet is a Chinese team who develop a new wallet based the new architecture: https://www.icowallet.net/
they have their business plan, are funded with a ICO, and will open source their wallet in the future.
I appreciate all your contributions.
This is slowly but steadily going autonomous, more functional and bigger. Proving that building decentralized consensus can result more beneficial than working on controlled, more isolated environments seems to be the greatest challenge now.
I'm ok with forks too. In some cases faster consensus and more direct control may be needed, maybe just having more things in common between peers to make everything easier.
In any case, having a truly decentralized network as an upstream backup, a global community with synergistic competition and collaboration, I think most of us agree on its value.
I will continue contribute to the new architecture, but not as a worker, as a volunteer.
Wouldn't you accept the network to pay what you deserve for solving issues that the network needs to get solved? The network should try to keep you doing things that makes her more valuable.
Even if your business already benefits from your contributions, you are also benefiting the whole network, and that reward should 'buy time' from best and most committed developers to gain expertise, go deeper and stay longer to satisfy the demands from this highly scalable network.
How without an organized development team? a clean road map and coordination?
This means to me that at some point proxies should become an active part on development management . Proxies with the ability to identify and to agree on general priorities, measuring when to delay or trade off partial interests in favor of the whole system, should become something required by most users when they turn to have higher expectations from their shares.
We need to reduce voter apathy and active development is very positive to grow engagement.
I'm not talking about specific proxies. with actual rules this is my ideal expectation from such a powerful role.
This network is one of the most fruitful social peer to peer experiences I have seen, lets find out how to let her grow strong enough to remain free.
-
What if we formally modified the proposal to state that anyone in the community could claim an issue and work it for a bounty.
For example, we could attach a dollar value to each issue and members could submit a PR and be paid the bounty amount for each issue. This would open the process to anyone who had the necessary technical skills to resolve the issue? Would this strategy allow you, @bitcrab, to support the proposal?
EDIT:
In essence, this would turn the worker proposal into a UI development fund.
This idea is interesting.
A project manager analyse/classify the issues (as you're doing now), identify priorities, work with devs to identify what tasks need how much work/fund, or let the devs bid on the prices, after the work is done, review / merge to the code base (may need a team to do the reviews, may also need fund).
Periodically, report to the "management team" for performance review, but not only to an escrow who will release the fund no matter what's done.
-
I'm happy to hear that you agree. It was our original intent to allow anyone to submit PR's and award them monetarily for accepted PRs. My question is this:
If I modify the WP to support a bounty system, will you support it? If you agree, I will modify it.
-
today I have discussed with ICOWALLET team, they plan to
1.adpot alt's infrastructure
2.update bitsharesjs
to improve the performance, as they said, updating bitsharesjs can also imporve the performance greatly.
seems these 2 ways are currently what we can do to get the needed wallet performance, surely more highly configured API servers are also needed, good news is that there are also new contributors for this, wss://bitshares.wancloud.io/ws is provided by wancloud, a branch of WANXIANG Group. this is a good beginning.
maybe because of culture difference, developers from China seldom like to create worker proposal. but many times it is good to create a worker proposal for your work, not only for getting paid, but also to expose your work to public, to let all know what are you doing, this is helpful to keep the development community healthy.
I'll ask the ICOwallet team to explain their plan for updatting bitsharesjs, the goal, and also the estimatted workload.
maybe a worker will be created for this.
I feel it's also well for alt to create a worker for the new infrastructure development, however if he does not hate to do so.
I feel @wmbutler 's idea for linking issue with bounty is ok, if it can be managed well, let's try it?
-
today I have discussed with ICOWALLET team, they plan to
1.adpot alt's infrastructure
2.update bitsharesjs
to improve the performance, as they said, updating bitsharesjs can also imporve the performance greatly.
seems these 2 ways are currently what we can do to get the needed wallet performance, surely more highly configured API servers are also needed, good news is that there are also new contributors for this, wss://bitshares.wancloud.io/ws is provided by wancloud, a branch of WANXIANG Group. this is a good beginning.
maybe because of culture difference, developers from China seldom like to create worker proposal. but many times it is good to create a worker proposal for your work, not only for getting paid, but also to expose your work to public, to let all know what are you doing, this is helpful to keep the development community healthy.
I'll ask the ICOwallet team to explain their plan for updatting bitsharesjs, the goal, and also the estimatted workload.
maybe a worker will be created for this.
I feel it's also well for alt to create a worker for the new infrastructure development, however if he does not hate to do so.
I feel @wmbutler 's idea for linking issue with bounty is ok, if it can be managed well, let's try it?
Just .. thank you .. for taking all the time and write this down!!! +5%
My only minor concern is that bitsharesjs should imho still be compatible with regular witness node apis and have a proper fall back mechanism ..
-
I support the bounty program. Lets get this proposal approved!
-
I am the leader developer of ICOWallet team. From my point of view, the ChainStore part of bitsharesjs is poorly designed so we need to replace with our own. The points are:
1 The return value of APIs of the form getXXXX is a 'try and guess correct' thing (sync one), which should be replaced with ( same form of ) promise apis.
2. The tests are incomplete and the code is hard to argue and review.
3. For the cache thing, we need some carefully designed mechanism to reduce the network throughput . IMHO, if a fully api node can reduce the memory usage, then in theory , a smart phone is capable for a "reduced full api node" which is used only with concerned accounts. That is a big thing. But for now, we plan to do some small improvements: market data / account history with diff data on wire . BitsharesUI has some code for diff data on wire for market data, it should be in bitsharesjs. Also, we plan to use HTML5 storage like localstorage / indexedDB to save persistent data from blockchain. (For compatible with Nodejs, that is another story.)
And yes, I think there are two ways to improve the architecture which is more valuable now:
1. use and improve alt's backend, drop many components in bitsharesjs.
2. do something like the discussion in this post above to improve the bitsharejs lib to make it a better one.
with any direction done, we can then do a better UI but I think it will be much easier.
we don't plan to open-source the UI part for ICOWallet in the near future( but maybe 1 or 2 years later), but once we have improved the bitsharesjs lib , we will make it opensource. @bitcrab suggested us to apply a worker for this part, but I don't think we need so much work to apply a worker (I think the community will see a better lib in two months, however as we have some other works, it could be incomplete for a whole UI but it should be a good reference for community to work on). If anyone can do some "block to object generating" like in C++ part in javascript, that is a valuable worker proposal (the big thing mentioned above).
In short, we need a better API lib layer to talk to backend first, then it is valuable to do a better reference UI .
-
In short, we need a better API lib layer to talk to backend first, then it is valuable to do a better reference UI .
Appreciate your work.
Not sure what you mean with "better" reference UI but it is imminent that we fix urgent bugs and UI elements now, simply because people have difficulties to navigate and use the wallet. Just waiting now and hoping for someone to built a better API-lib do harm our reputation and hinders user adoption.
Now is the time to work on multiple parts, even if we will rework the reference client in the future.
For example Cryptonomex is running a marketing campaign out of their own pocket but it does not make sense to target new users if we don't address the most urgent problems in the wallet now. We simply do not have a choice.
Not voting for motivated workers is in the end more expensive then "wasting" $1mil per year to maintain our infrastructure and dev teams.
-
surely we cannot expect volunteers to do the needed development just for free, we need to pay for valuable work, especially when capitals are looking for blockchain relevant developers with high salary all around the world.
I think alt's project and ICOWALLET's plan do worth worker proposals, so if necessary, do not hesitate to apply one, it will help the community to be aware and trace what you do.
I finally decided to vote up this worker. I know it is not perfect, but we need it.
-
surely we cannot expect volunteers to do the needed development just for free, we need to pay for valuable work, especially when capitals are looking for blockchain relevant developers with high salary all around the world.
I think alt's project and ICOWALLET's plan do worth worker proposals, so if necessary, do not hesitate to apply one, it will help the community to be aware and trace what you do.
I finally decided to vote up this worker. I know it is not perfect, but we need it.
Thank you for your approval bitcrab. I am glad we are finally spending to fund development and would happily support alt and icowallet worker as well.
-
surely we cannot expect volunteers to do the needed development just for free, we need to pay for valuable work, especially when capitals are looking for blockchain relevant developers with high salary all around the world.
I think alt's project and ICOWALLET's plan do worth worker proposals, so if necessary, do not hesitate to apply one, it will help the community to be aware and trace what you do.
I finally decided to vote up this worker. I know it is not perfect, but we need it.
Thank you for this approval and I trust it will not disappoint your community and shareholders
-
The most important thing is to identify priority of the jobs and to arrange resources according to the priority. That said, value of low priority jobs is near zero. We don't need to get everything done, but need to get the most important things done asap. Hope you will not disappoint us.
-
What is the logic behind dates for milestones? https://github.com/bitshares/bitshares-ui/milestones
Now I see 1 Sep, 14 Sep, 1 Oct ... wouldn't it be better for both dev team and community to have predictable sprints, e.g. 14-day long?
-
Here came a new developer submitting PR's.
https://github.com/bitshares/bitshares-ui/pull/250
https://github.com/bitshares/bitshares-ui/pull/255
If we have more contributors like this, the worker fund may be not enough or be accumulating too slowly.
-
If we have more contributors like this, the worker fund may be not enough or be accumulating too slowly.
not a bad problem to have though
-
Good to have a weekly report? In the beginning we can summarize a bit more frequently, after the process became stable, do less.
-
At last, a sane account overview page. Good job!
+5%
-
seems like committee is meeting here, but i am curious, is there a regular meeting by committee to discuss and review proposals and future of bitshares?
Also why has this proposal not been approved for so long?