-
Here is the newest version:
https://bitshares.org/roadmap.html
or
http://neura-sx.github.io/#progress/roadmap
* Overlap = potential overlap with other Graphene-based projects (i.e. BitShares ends up paying for generic Graphene features)
You can help to prioritize this list by casting your vote in this poll:
http://goo.gl/forms/UDBqvDnqyq
And here are the results:
https://docs.google.com/forms/d/1oHRfDeWw9GE-RYSr7NjI32OB-VcKKW5c3uZdLO_L3Bs/viewanalytics
-
You can look here for other possible future worker proposals
https://github.com/cryptonomex/graphene/issues/
-
Thank you jakub, I think we really need this.
In my opinion we need to tackle these one by one and get to a finished, stable product.
-
#sharebits "jakub" 100 MEGUSTA
-
Hey fav, here are the results of your tips...
- jakub (http://sharebits.io/Home/Dashboard?username=jakub): has been credited 100 MEGUSTA
Curious about BtsTip? Visit us at http://sharebits.io and start tipping BTS on https://bitsharestalk.org/ today!
Source: https://bitsharestalk.org/index.php/topic,20171.msg259525/topicseen.html#msg259525
Created by hybridd (https://bitsharestalk.org/index.php?action=profile;u=40140)
-
I think that is exactly what people who are investing in BitShares wants to know and you did a great job at pulling what has been scattered all over the place in multiple boards. +5%
I would add:
An affiliate dashboard for Lifetime Members.
When you do marketing you kind of want to know how your conversions is going.
(Average time of use, number of transactions, income, etc.)
-
#sharebits "jakub" 100 BEYONDBITCOIN
#sharebits "jakub" 1 GREATIDEA
#sharebits "jakub" 1 FISTBUMP
#sharebits "jakub" 1 HIGHFIVE
-
Hey Tuck Fheman, here are the results of your tips...
- jakub (http://sharebits.io/Home/Dashboard?username=jakub): has been credited 100 BEYONDBITCOIN
- jakub (http://sharebits.io/Home/Dashboard?username=jakub): has been credited 1 GREATIDEA
- jakub (http://sharebits.io/Home/Dashboard?username=jakub): has been credited 1 FISTBUMP
- jakub (http://sharebits.io/Home/Dashboard?username=jakub): has been credited 1 HIGHFIVE
Curious about BtsTip? Visit us at http://sharebits.io and start tipping BTS on https://bitsharestalk.org/ today!
Source: https://bitsharestalk.org/index.php/topic,20171.msg259529/topicseen.html#msg259529
Created by hybridd (https://bitsharestalk.org/index.php?action=profile;u=40140)
-
+5% This is a good effort and something that is needed.
-
#sharebits "jakub" 1 CHATEAUX
+5%
-
Hey 38PTSWarrior, here are the results of your tips...
- jakub (http://sharebits.io/Home/Dashboard?username=jakub): has been credited 1 CHATEAUX
Curious about BtsTip? Visit us at http://sharebits.io and start tipping BTS on https://bitsharestalk.org/ today!
Source: https://bitsharestalk.org/index.php/topic,20171.msg259535/topicseen.html#msg259535
Created by hybridd (https://bitsharestalk.org/index.php?action=profile;u=40140)
-
I think that is exactly what people who are investing in BitShares wants to know and you did a great job at pulling what has been scattered all over the place in multiple boards. +5%
I would add:
An affiliate dashboard for Lifetime Members.
When you do marketing you kind of want to know how your conversions is going.
(Average time of use, number of transactions, income, etc.)
+5% +5% +5%
-
I would add:
An affiliate dashboard for Lifetime Members.
Added.
I've also added as (11) my proposal to improve UX for the gateway/bridge page.
This is aimed at offering a flexible solution which could accommodate all kinds of different gateway providers.
Do it the way markets are organized in the GUI: there would be an initial page where all gateway providers are listed (e.g. Blocktrades, Transwiser, Metaexchange, OpenLedger etc) and when you click on any of them you navigate to a separate page which is fully dedicated to a particular service provider and organized according to the specific offer of the provider and fully managed by the provider.
In this approach the gateway/bridge functionality will be detached from the account page and made a separate item in the top menu bar:
Dashboard | Explore | Deposit/Withdraw | Trade | Transfer
-
Good job, this should be stickied +5%
-
+5% Yes!
And thank you! (old fashioned I know, "Hey, where's my UIA with that thank you?!) Soon. ;)
-
where can we make sure that this doesn't disappear and get somewhere we can keep ourselves "on the road map"
-
Since all we officially have as a roadmap is this (https://bitshares.org/roadmap/) I think we are hurting ourselves badly because:
(a) there is growing disorientation inside the community about where we are heading after 2.0 launch
(b) potential investors are deprived of a very important piece of information
CNX has not been able to compile such list, so let's do it ourselves.
Please help me to complete this list below - it 's my attempt to create some kind of roadmap for the next 4-6 month.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
(1) Migration tool for holders of a large number of private keys
Forum thread: ?
Worker Proposal: n/a
Potential overlap with other Graphene projects: N
Status: In progress
(2) Fix & standardize the API for trading bots
Forum thread: ?
Worker Proposal: n/a
Potential overlap with other Graphene projects: N
Status: In progress
(3) Refund Order Creation Fees
Forum thread: https://bitsharestalk.org/index.php/topic,20089.msg258214.html#msg258214
Worker Proposal: 1.14.7
Potential overlap with other Graphene projects: N
Status: In progress
(4) Prevent margin call from being triggered unless the price feed is less than call price
Forum thread: https://bitsharestalk.org/index.php/topic,19735.msg253383.html
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: N
Status: Not started yet
(5) Launch a Demo/Dev chain
Forum thread: https://bitsharestalk.org/index.php/topic,19735.msg253383.html
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: N
Status: Not started yet
(6) Collateralized Bond Market
Forum thread: https://bitsharestalk.org/index.php/topic,19419.0.html
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: N
Status: Not started yet (postponed)
We ditched the bond market we originally proposed after feedback from the community. The protocol level rules created a system that was combination bond/option and that made them difficult to price an unpredictable. The new bond market rules are more complex than the one originally proposed because it actually enforces margin calls on users. This extra complexity means we can toss the partial work that we already did on bond markets prior to June 8th and must start over.
I really really want a bond market. I am just trying to estimate the relative complexity of various tasks.
(7) Stealth Transfers
Forum thread: https://bitsharestalk.org/index.php/topic,20104.0.html
Detailed description: https://github.com/cryptonomex/graphene/issues/452
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: Y
Status: Not started yet
(8.1) Market fees adjustment
Forum thread: https://bitsharestalk.org/index.php/topic,19890.0.html
Detailed description: https://docs.google.com/document/d/12hWyasMJ5mL1fboAt9ZK8FEf0c7o_q-1bwm5ItsLNGo/edit#
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: N
Status: Not started yet
(8.2) Hosted wallet service
Forum thread: https://bitsharestalk.org/index.php/topic,19890.0.html
Detailed description: https://docs.google.com/document/d/12hWyasMJ5mL1fboAt9ZK8FEf0c7o_q-1bwm5ItsLNGo/edit#
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: Y
Status: Not started yet
(8.3) Improved market statistics
Forum thread: https://bitsharestalk.org/index.php/topic,19890.0.html
Detailed description: https://docs.google.com/document/d/12hWyasMJ5mL1fboAt9ZK8FEf0c7o_q-1bwm5ItsLNGo/edit#
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: N
Status: Not started yet
(8.4) Fiat Deposit / Withdraw / KYC management
Forum thread: https://bitsharestalk.org/index.php/topic,19890.0.html
Detailed description: https://docs.google.com/document/d/12hWyasMJ5mL1fboAt9ZK8FEf0c7o_q-1bwm5ItsLNGo/edit#
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: Y
Status: Not started yet
(9) Prediction markets
Forum thread: ?
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: ?
Status: Not started yet
(10) An affiliate dashboard for Lifetime Members
Forum thread: ?
Worker Proposal: Not created yet
Potential overlap with other Graphene projects: N
Status: Not started yet
(11) Improvement of deposit/withdraw UX
Forum thread: https://bitsharestalk.org/index.php/topic,20152.0.html
Worker Proposal: Not created yet
Detailed description: https://bitsharestalk.org/index.php/topic,20152.msg259362.html#msg259362
Potential overlap with other Graphene projects: N
Status: Not started yet
History tells me, those are most likely VERY good!
But I charge 45K for even pretending I read them...[ with no warranty I actually did, you know]
Enjoy! Great future waits, btw.!
If you do not trust me the moon stuff, here are some +5% +5% +5% +5% +5% +5% +5% +5%...so you can see it more easily....heard 'plus fives' help a lot with this.
-
Recurring & Scheduled Payments (https://bitshares.org/technology/recurring-and-scheduled-payments/) are also still missing.
-
Thanks for doing this.
I think this thread (with progress tracking) is one of the most important threads going forward.
-
Thank you for this effort ! +5%
-
GUI tools for committee members! If we want to govern the DAC, we need to have tools for doing it. Now it is very difficult to do with command line wallet.
-
A breathe of fresh air. +5%
-
Thank you for the positive feedback.
I've made a spreadsheet version of the roadmap as I think this way it's more manageable
https://docs.google.com/spreadsheets/d/1n3yqHGqHOMgE67AVmi9MfS2RRL8LX2x2oezFLi_Q9pw/edit?usp=sharing
(Please let me know if you'd like to have it in the form a forum post as well)
-
Great job! +5%
-
Thank you for the positive feedback.
I've made a spreadsheet version of the roadmap as I think this way it's more manageable
https://docs.google.com/spreadsheets/d/1n3yqHGqHOMgE67AVmi9MfS2RRL8LX2x2oezFLi_Q9pw/edit?usp=sharing
(Please let me know if you'd like to have it in the form a forum post as well)
Very cool ..
-
I guess know it's a matter of knowing which proposals should have more priority than others. Pool? It might not mean anything but I'm interested on seeing the general idea here on the forum.
And I would say the Instant Order (Bitstamp Style) also has potential for overlapping. And that's $30.000 Same thing for distributing fees as core asset for referral program? MUSE will have the referral program right? It will be used there.
-
And I would say the Instant Order (Bitstamp Style) also has potential for overlapping. And that's $30.000
I amended the list to indicate this potential overlapping.
-
And I would say the Instant Order (Bitstamp Style) also has potential for overlapping. And that's $30.000
I amended the list to indicate this potential overlapping.
Check edited post pls. marktet fees as core asset for referral program might overlap too?
Btw I'm doing a google form so ppl can vote on the priority for each one of these
Edit: I haven't, however included the "Improvement of the deposit/withdrawal UX" for the reason I consider that to go under the general GUI improvements that have been made. Or am I wrong? Doesnt this fall under that category? For that reason I dont think a worker proposal is needed. Unless of course CNX charges for that.
-
What mechanism can we use to prioritize this? Predicition market? ;-)
I know we can make a short survey for free on surveymonkey.com . This way, we can poll on prioritization.
-
Once the OP list is representative of all the potential projects currently before us can't we just make a poll here? Survey Monkey is cool, but everyone is already here, maybe I'm missing something. (besides the fact that the forum itself needs an upgrade)
Hey, should we add forum upgrade to the list as well? I mean, between DAWN, DPOSHUB, Freebie Servers, and multiple other community requests / lamentations, i'm thinking it really is time to plan, and execute on some kind of forum upgrade.
-
What mechanism can we use to prioritize this? Predicition market? ;-)
I know we can make a short survey for free on surveymonkey.com . This way, we can poll on prioritization.
I've already done it. Should I post it here or make a new thread? I'm afraid people won't see it here now
-
Is it possible to have several graphene based Blockchain paying a part of the amount needed to implement the same feature ?
For example, Muse and BitShares paying each one 50% of the amount needed to implement a feature they will both use ?
-
What mechanism can we use to prioritize this? Predicition market? ;-)
I know we can make a short survey for free on surveymonkey.com . This way, we can poll on prioritization.
I've already done it. Should I post it here or make a new thread? I'm afraid people won't see it here now
I think a separate thread would be better. And once we have prioritization sorted out I'll amend the roadmap to reflect the results of the poll.
-
I say do it here, make a post saying you've added it and @everyone who has participated in the thread thus far asking them to spread the word. Also, as @Riverhead suggested here: https://bitsharestalk.org/index.php/topic,20104.msg259604.html#msg259604 We need to facilitate counter proposals, and reach some mutual agreement.
Every consulting project, or worker proposal in our case, has defined terms. If you don't like CNX's offer then make a counter proposal that's agreeable to them and the community and try and get it voted in.
In business you don't get what you deserve you get what you negotiate.
-
What mechanism can we use to prioritize this? Predicition market? ;-)
I know we can make a short survey for free on surveymonkey.com . This way, we can poll on prioritization.
I've already done it. Should I post it here or make a new thread? I'm afraid people won't see it here now
I think a separate thread would be better. And once we have prioritization sorted out I'll amend the roadmap to reflect the results of the poll.
Or a separate one.. whatever works. ;)
-
Done
https://bitsharestalk.org/index.php/topic,20183
-
I did a quick search and see no mention of the URI scheme that was VERY useful in 1.0. :-\
I'm halfway talking out of my ass because I don't really know that much about a "URI scheme", but what I do know is that it allowed me to open the client using a link "bts:" and I could add all kinds of options to that string to submit payments and such. Others have mentioned that it is helpful when dealing with logins.
So, I'm throwing that out there. ;)
-
This might be a stupid question - but what is the status of these two?
- Transferable Named Accounts (https://bitshares.org/technology/transferable-named-accounts/)
- Dynamic Account Permissions (https://bitshares.org/technology/dynamic-account-permissions/)
Are they implemented on the blockchain level and are just awaiting to be exposed in the GUI?
(Or maybe Dynamic Account Permissions are already in the GUI but I just don't know how to use this feature)
-
What's the process to ratify something like this?
-
I know lots of people don't take it very seriously but a think an integrated chat box /troll box should be prioritised.
It can act as a free customer service instead of people having to scroll through pages and pages on this forum which takes them away from the actual exchange.
-
I know lots of people don't take it very seriously but a think an integrated chat box /troll box should be prioritised.
It can act as a free customer service instead of people having to scroll through pages and pages on this forum which takes them away from the actual exchange.
Troll-box task added.
-
please make a tab in the Gui showing the open orders of the specific wallet..we had that in bts 1 and we should definitely have it in bts2
-
please make a tab in the Gui showing the open orders of the specific wallet..we had that in bts 1 and we should definitely have it in bts2
Currently we have this:
https://bitshares.openledger.info/#/account/jakub/orders
Isn't this list supposed to show open orders?
-
Well I also think the chatbox is needed, a lot. People tell about wanting core users, well, those will hang out on the chatbox. But doesn't that make part of the UI development? I would place them under the same category?
-
please make a tab in the Gui showing the open orders of the specific wallet..we had that in bts 1 and we should definitely have it in bts2
Currently we have this:
https://bitshares.openledger.info/#/account/jakub/orders
Isn't this list supposed to show open orders?
It doesn't work, always empty
-
Well I also think the chatbox is needed, a lot. People tell about wanting core users, well, those will hang out on the chatbox.
I second that +5%
Users need easy access support without leaving the client.
-
Well I also think the chatbox is needed, a lot. People tell about wanting core users, well, those will hang out on the chatbox.
I second that +5%
Users need easy access support without leaving the client.
we can't add a 3rd party to the wallet. that's the deal here.
I think it can't get easier than to go to openledger.info and click on the chat button to get in touch
-
please make a tab in the Gui showing the open orders of the specific wallet..we had that in bts 1 and we should definitely have it in bts2
Yes, atm unless you don't memorize the market where you placed an order (i guess you can check account history) you don't know . You need to go there manually when you could just click on your open order and take you to that market. Also be able to cancel any orders from that tab
-
Well I also think the chatbox is needed, a lot. People tell about wanting core users, well, those will hang out on the chatbox.
I second that +5%
Users need easy access support without leaving the client.
we can't add a 3rd party to the wallet. that's the deal here.
I think it can't get easier than to go to openledger.info and click on the chat button to get in touch
Could the function be there so that each wallet provider can have it's own support?
-
Well I also think the chatbox is needed, a lot. People tell about wanting core users, well, those will hang out on the chatbox.
I second that +5%
Users need easy access support without leaving the client.
we can't add a 3rd party to the wallet. that's the deal here.
I think it can't get easier than to go to openledger.info and click on the chat button to get in touch
Why? Because it's not safe? Guess we need to wait for someone to provide that service?
Also isn't that chatbox for support only? Can I talk to you on that chatbox? I dont think so?
Plus, even if we could no one will keep a tab open just for that, it's not practical and it's not the same thing as having one right on the wallet.
-
Well I also think the chatbox is needed, a lot. People tell about wanting core users, well, those will hang out on the chatbox.
I second that +5%
Users need easy access support without leaving the client.
we can't add a 3rd party to the wallet. that's the deal here.
I think it can't get easier than to go to openledger.info and click on the chat button to get in touch
Could the function be there so that each wallet provider can have it's own support?
I think a configurable "support" or "chat" link on the main page would be ok, the wallet provider can link it to it's own page/box.
-
This might be a stupid question - but what is the status of these two?
- Transferable Named Accounts (https://bitshares.org/technology/transferable-named-accounts/)
- Dynamic Account Permissions (https://bitshares.org/technology/dynamic-account-permissions/)
Are they implemented on the blockchain level and are just awaiting to be exposed in the GUI?
(Or maybe Dynamic Account Permissions are already in the GUI but I just don't know how to use this feature)
Haven't tried these yet but dynamic account permissions are on the permissions tab in the wallet. You can add other accounts/keys and how much weight they have.
BTW, isn't Collateralized Bond Market a prerequisite for Margin Trading? Should we count these as a one thing?
-
Well I also think the chatbox is needed, a lot. People tell about wanting core users, well, those will hang out on the chatbox.
I second that +5%
Users need easy access support without leaving the client.
we can't add a 3rd party to the wallet. that's the deal here.
I think it can't get easier than to go to openledger.info and click on the chat button to get in touch
Could the function be there so that each wallet provider can have it's own support?
I think a configurable "support" or "chat" link on the main page would be ok, the wallet provider can link it to it's own page/box.
If we want a trollbox in graphene someone has to find a way to use the memokeys and probably make a sidechain for chat.
-
BTW, isn't Collateralized Bond Market a prerequisite for Margin Trading? Should we count these as a one thing?
You might be right, I've merged those two into one task.
-
please make a tab in the Gui showing the open orders of the specific wallet..we had that in bts 1 and we should definitely have it in bts2
Yes, atm unless you don't memorize the market where you placed an order (i guess you can check account history) you don't know . You need to go there manually when you could just click on your open order and take you to that market. Also be able to cancel any orders from that tab
Added to the roadmap.
-
Also added AdamBLevine's Tokenly Ecosystem integration (https://bitsharestalk.org/index.php/topic,19634.0.html) to the roadmap.
-
I think that is exactly what people who are investing in BitShares wants to know and you did a great job at pulling what has been scattered all over the place in multiple boards. +5%
I would add:
An affiliate dashboard for Lifetime Members.
When you do marketing you kind of want to know how your conversions is going.
(Average time of use, number of transactions, income, etc.)
Is there a forum thread (or a github request) I could link to for this task?
-
please make a tab in the Gui showing the open orders of the specific wallet..we had that in bts 1 and we should definitely have it in bts2
Yes, atm unless you don't memorize the market where you placed an order (i guess you can check account history) you don't know . You need to go there manually when you could just click on your open order and take you to that market. Also be able to cancel any orders from that tab
I don't know the difficulty of things but my guess would be that to have a tab showing all the open orders in that wallet shouldn't be that difficult..It is important though. With all the UIA and MPAs and multiple small orders in different markets it is impossible to keep everything on track. I many times go to one market then change my mind go to somewhere else etc etc..Having a tab canceling the open orders is a must. All exchanges in the world have a tab for open trades..
-
please make a tab in the Gui showing the open orders of the specific wallet..we had that in bts 1 and we should definitely have it in bts2
Yes, atm unless you don't memorize the market where you placed an order (i guess you can check account history) you don't know . You need to go there manually when you could just click on your open order and take you to that market. Also be able to cancel any orders from that tab
I don't know the difficulty of things but my guess would be that to have a tab showing all the open orders in that wallet shouldn't be that difficult..It is important though. With all the UIA and MPAs and multiple small orders in different markets it is impossible to keep everything on track. I many times go to one market then change my mind go to somewhere else etc etc..Having a tab canceling the open orders is a must. All exchanges in the world have a tab for open trades..
I fixed this yesterday, will be in tomorrow's release.
-
Awesome initiative Jakub! This is what a proper roadmap on github would look like (https://github.com/flarum/core/issues/74). You should ask the devs to give you access so you can format your roadmap to look something like that example.
-
Awesome initiative Jakub! This is what a proper roadmap on github would look like (https://github.com/flarum/core/issues/74). You should ask the devs to give you access so you can format your roadmap to look something like that example.
+5% This would be a huge help.
-
I think "AdamBLevine's Tokenly Ecosystem integration" should be re-categorised as 'Integration with 3rd party" and status is 'Pending a worker proposal'.
-
I think "AdamBLevine's Tokenly Ecosystem integration" should be re-categorised as 'Integration with 3rd party" and status is 'Pending a worker proposal'.
Fixed.
-
Awesome initiative Jakub! This is what a proper roadmap on github would look like (https://github.com/flarum/core/issues/74). You should ask the devs to give you access so you can format your roadmap to look something like that example.
+5% This would be a huge help.
Here are my attempts:
(1) Less details but nice subsections
https://github.com/neura-sx/BitShares/blob/master/BitShares%202.0%20Roadmap.md
(2) More details but unable to maintain subsections (tables in github are too primitive for that)
https://github.com/neura-sx/BitShares/blob/master/BitShares%202.0%20Roadmap%20Details.md
Let me know which format suits you best - and if github is the winner, I'll ask CNX for github access.
-
Brilliant jakub
-
Awesome initiative Jakub! This is what a proper roadmap on github would look like (https://github.com/flarum/core/issues/74). You should ask the devs to give you access so you can format your roadmap to look something like that example.
+5% This would be a huge help.
Here are my attempts:
(1) Less details but nice subsections
https://github.com/neura-sx/BitShares/blob/master/BitShares%202.0%20Roadmap.md
(2) More details but unable to maintain subsections (tables in github are too primitive for that)
https://github.com/neura-sx/BitShares/blob/master/BitShares%202.0%20Roadmap%20Details.md
Let me know which format suits you best - and if github is the winner, I'll ask CNX for github access.
Looks pretty nice, we needed that! +5%
-
I've come to the conclusion that we need something more robust than github can offer.
So I've created an XML file which is easily manageable:
https://github.com/neura-sx/neura-sx.github.io/blob/master/roadmap.xml
And thanks to a very nice invention called XSLT (http://www.w3schools.com/xsl/default.asp) it is able to render itself in the browser to this human-readable format:
http://neura-sx.github.io/roadmap.xml
-
I've come to the conclusion that we need something more robust than github can offer.
So I've created an XML file which is easily manageable:
https://github.com/neura-sx/neura-sx.github.io/blob/master/roadmap.xml
And thanks to a very nice invention called XSLT (http://www.w3schools.com/xsl/default.asp) it is able to render itself in the browser to this human-readable format:
http://neura-sx.github.io/roadmap.xml
+5%
It's easier to read. Good job.
Would it be possible to add an "estimated time completion" column?
-
https://bitshares.org/roadmap.xml
-
+5%
It's easier to read. Good job.
Would it be possible to add an "estimated time completion" column?
Done :)
But I'll need some help to get the data for this column.
EDIT: I've made the change in my code while cass took a copy of the previous version.
Tomorrow we'll merge these two into one.
http://neura-sx.github.io/roadmap.xml
https://bitshares.org/roadmap.xml
-
https://bitshares.org/roadmap.xml
That was quick :)
Thanks @cass
-
+5%
It's easier to read. Good job.
Would it be possible to add an "estimated time completion" column?
Done :)
But I'll need some help to get the data for this column.
EDIT: I've made the change in my code while cass took a copy of the previous version.
Tomorrow we'll merge these two into one.
http://neura-sx.github.io/roadmap.xml
https://bitshares.org/roadmap.xml
Thanks, I really believe in what the late Peter Drucker use to teach:
What gets tracked gets managed
Keep it up Jakub
-
https://bitshares.org/roadmap.xml
That was quick :)
Thanks @cass
happy to help .. i've pinged dan about giving you github access .. will keep you in the loop
and updated ... https://github.com/bitshares/bitshares.github.io/commit/c73db1f6d0875eaeba7f1440a2ae1e56d978f0f4
-
https://bitshares.org/roadmap.xml
@cass I like your color scheme, it's easier to read. +5%
-
This thing is becoming something more than a roadmap:
http://neura-sx.github.io/#roadmap
(please ignore the colors - I have no talent in this respect)
The powerful thing is that it's all based on XML data so it will be really easy to keep it up-to-date via github pull requests.
https://github.com/neura-sx/neura-sx.github.io/tree/master/xml
e.g. a roadmap item looks like this:
<item progress="0.0" funded="Y" overlap="N">
<name>Refund market order creation fees</name>
<description />
<status>Funded worker</status>
<time>Nov 2015</time>
<worker>1.14.7</worker>
<terms>2M BTS paid over 40 days at 50,000 BTS per day. Bunkerchain Labs
will sell the BTS to raise $4400 and refund any remaining BTS to the
blockchain.</terms>
<contractor>
<name>CNX</name>
<url>https://cryptonomex.com/</url>
<cost>4000</cost>
</contractor>
<escrow>
<name>Bunkerchain Labs</name>
<url>http://www.bunkerchainlabs.com/</url>
<cost>400</cost>
</escrow>
<links>
<link>
<label>forum</label>
<url>https://bitsharestalk.org/index.php/topic,20089.0.html</url>
</link>
<link>
<label>github</label>
<url>https://github.com/cryptonomex/graphene/issues/445</url>
</link>
</links>
</item>
-
This thing is becoming something more than a roadmap:
http://neura-sx.github.io/#roadmap
This is the first we can look at a visual bitshares roadmap. I am impressed!
Edit: @cass Is there a way to link it to bitshares.org?
-
https://bitshares.org/roadmap.xml
"This XML file does not appear to have any style information associated with it. The document tree is shown below."
???
-
https://bitshares.org/roadmap.xml
"This XML file does not appear to have any style information associated with it. The document tree is shown below."
???
Sorry for the confusion - I've been making several attempts to achieve a robust solution, i.e. to have one roadmap XML file that can be shared across many different websites.
My initial intention was to have the raw roadmap data in this file:
https://bitshares.org/roadmap.xml
and then be able to present this data in different contexts, e.g.:
https://bitshares.org/roadmap.html
http://neura-sx.github.io/#roadmap
Currently those two websites are not in sync but they will be as soon as @cass accepts my recent github pull requests.
-
https://bitshares.org/roadmap.html
-
https://bitshares.org/roadmap.html
The github and forum tags hurt my eyes. that lightblue and white combination is not very good.
One thing, could you specify on the Estimated Cost, if it's $USD or BTS? For example I believe you priced most in USD but on Open Source Graphene UI for BitShares the cost is 10M, I saw the github page and it mentioned BTS. People might get confused if they dont know the unit of the price (USD or BTS)
-
not ready yet .. yep will do ..
-
One thing, could you specify on the Estimated Cost, if it's $USD or BTS? For example I believe you priced most in USD but on Open Source Graphene UI for BitShares the cost is 10M, I saw the github page and it mentioned BTS. People might get confused if they dont know the unit of the price (USD or BTS)
A good catch. I've created a pull request that adds currency units.
-
roadmap colors updated...
-
Thanks Cass colors look a lot better. Is there a meaning to the colors?
-
Thanks Cass colors look a lot better. Is there a meaning to the colors?
Those three color variations aim to distinguish between these there phases:
(1) Task successfully completed
(2) Task already funded but not completed yet
(3) Task not funded yet
If you find the colors confusing we can easily eliminate them by applying the same color scheme for all tasks regardless of their status.
-
No, the colors are not confusing, perhaps you should have a color ledgend somewhere specifying what each color means. Just a thought.
-
yep agreed > (ledgend) i will add on top ..
i was thinking also to highlight the progress state at left of each entry ..
(maybe we can also iconfying some sections .. )
-
i'Ve also tried to get it a bit more responsive with hiding some of the columns with smaller view point width…
-
i'Ve also tried to get it a bit more responsive with hiding some of the columns with smaller view point width…
Since the color codes represent the status, you might also hide the status column if you need more space (just thinking out loud).
Maybe the "Estimated Time" column should read "Estimated Delivery", time could be taken as the time it would take to do the job and not necessarily when it will be delivered.
The "Name" column should read "Proposal Name" or just "Proposal"
I think that the darker rows might be too overpowering, how about something like this:
(http://i.imgur.com/97fkohih.jpg)
-
I think that the darker rows might be too overpowering.
I also think there is too much contrast between the bright and dark rows.
As we have it now, the dominating dark rows suggest items of greater importance whereas these are the tasks which have not even been funded yet.
But I'll leave it to @cass to decide.
-
The roadmap has been updated to reflect the announcements made during two Mumble hang-outs last Friday:
- upcoming hard-fork announced by BM
- upcoming Moonstone wallet release announced by @bitsapphire
https://bitshares.org/roadmap.html
Or the same data but presented with a different styling and context:
http://neura-sx.github.io/#progress/roadmap
-
The roadmap has been updated to reflect the announcements made during two Mumble hang-outs last Friday:
- upcoming hard-fork announced by BM
- upcoming Moonstone wallet release announced by @bitsapphire
https://bitshares.org/roadmap.html
Or presented in a different styling and context:
http://neura-sx.github.io/#roadmap
The specific planned date is 12/16 GMT at the moment.
-
The specific planned date is 12/16 GMT at the moment.
You mean planned date for what event?
-
The specific planned date is 12/16 GMT at the moment.
You mean planned date for what event?
Fix margin call trigger, Refund market order creation fees, (and referral fix)
https://github.com/bitshares/bitshares-2/commit/2b9876fd9809b8ea5bcb7fe9f3a2b73023023067
-
I think the "Last update" date should read 06 Dec 2015 or Dec 06 2015 otherwise in America people might think that the roadmap hasn't been updated since June 12, 2015. ???
-
I think the "Last update" date should read 06 Dec 2015 or Dec 06 2015 otherwise in America people might think that the roadmap hasn't been updated since June 12, 2015. ???
yea - or if u look other way around - otherwise many other countries would have same issue :D
-
I think that the darker rows might be too overpowering.
I also think there is too much contrast between the bright and dark rows.
As we have it now, the dominating dark rows suggest items of greater importance whereas these are the tasks which have not even been funded yet.
But I'll leave it to @cass to decide.
will take a look tomorrow ..
-
#sharebits "jakub" 1 ROSE
-
Hey ebit, here are the results of your tips...
- jakub (http://sharebits.io/Home/Dashboard?username=jakub): has been credited 1 ROSE
Curious about ShareBits? Visit us at http://sharebits.io and start tipping BTS on https://bitsharestalk.org/ today!
Source: https://bitsharestalk.org/index.php/topic,20171.msg264321/topicseen.html#msg264321
Created by hybridd (https://bitsharestalk.org/index.php?action=profile;u=40140)
-
(2) Fix & standardize the API for trading bots
Forum thread: ?
Worker Proposal: n/a
Potential overlap with other Graphene projects: N
Status: In progress
@jakub I noticed that a "cancel_order" API has been added to cli_wallet in the release v2.0.151209(https://github.com/bitshares/bitshares-2/releases/tag/v2.0.151209):
graphene::chain::signed_transaction cancel_order(graphene::db::object_id_type, bool)
And some other API's were added in the same release.
Do we still need any more API for trading bots?
-
In regards to this item:
Vested cashback balance and claim option
It has been done in the latest GUI (v2.0.151223), however in that release there are issues in some edge cases which has been fixed in latest code base.
https://github.com/bitshares/bitshares-2/releases/tag/v2.0.151223
https://github.com/cryptonomex/graphene-ui/issues/640
These items have been done:
* Refund market order creation fees (v2.0.151209)
* Fix margin call trigger (v2.0.151209)
-
In regards to this item:
Vested cashback balance and claim option
It has been done in the latest GUI (v2.0.151223), however in that release there are issues in some edge cases which has been fixed in latest code base.
https://github.com/bitshares/bitshares-2/releases/tag/v2.0.151223
https://github.com/cryptonomex/graphene-ui/issues/640
These items have been done:
* Refund market order creation fees (v2.0.151209)
* Fix margin call trigger (v2.0.151209)
Thanks @abit for your suggestions.
I've upgraded the roadmap:
- Status of several items changed to 'completed'.
- Synchronized the roadmap with BSIPs (https://github.com/bitshares/bsips).
- Added MAS and other newly created worker proposals.
- Also added BitShares Munich mobile wallet (https://bitsharestalk.org/index.php/topic,20762.0.html) as third party project.
The above changes will become visible once this pull request (https://github.com/bitshares/bitshares.github.io/pull/80) is accepted.
Anyone wanting to amend the roadmap, you can easily do it by updating this XML file (https://github.com/bitshares/bitshares.github.io/blob/master/roadmap.xml) and creating a pull request.
-
@jakub Any plans to update the Roadmap? There have been many hot topics and it is hard to judge which ones are the highest priorities, so I would kindly request @Bytemаsteг to tell us clearly, which ones he thinks that are the highest priorities.
There seems to be some chaos as to what should be done first and that doesn't help the witnesses to vote. If there is no schedule or at least some cooperation between workers, many projects might be downvoted just because people think its not high priority and that something else should be funded first.
-
@tarantulaz --> https://bitsharestalk.org/index.php/topic,21541.msg280507.html#msg280507