-
All,
I've posted my worker proposal. Please vote if you support my efforts to help manage expectations as they relate to graphene-ui progress. I'm proposing $500 per month for 3 months to begin. It's #7 (1.14.8):
http://cryptofresh.com/workers
Here is an update of the items that were fixed and added to the Web Wallet this week:
https://github.com/cryptonomex/graphene-ui/issues?q=is%3Aissue+milestone%3A2.0.151118+is%3Aclosed
Here are the items slated for completion by 11/25:
https://github.com/cryptonomex/graphene-ui/milestones/2.0.151125
Official Version Announcement:
https://github.com/bitshares/bitshares-2/releases/tag/v2.0.151119
-
I think this is a good idea, and having one person dedicated on managing releases/bug triage is important and helpful. Especially as a connection between the community, bug reports, and devs.
1) graphene-ui is a CNX project that is licensed to bitshares. Bitshares will be paying you to manage graphene. Is CNX ok with a non-employee managing their releases?
2) Will you have commit access/tag access to the offical repos?
3) The role appears to be mostly community organizing, bug triage, illustration of goals (all very important for a successful project). In the end these are just "suggestions" (although probably very good ones) of priorities. Are you the one that will say "we won't release until X Y Z are fixed?" or is it more helping articulate highest priorities from the input from the community?
-
I like to hear from the dev team members ( Daniel Larimer, Sigve Kvalsvik, James Calfee, Valentine Zavgorodnev, Fabian Schuh, cass) on their view of this Project Manager role - specifically:
1) Is such a role missing in CNX currently,
2) why is this role needed, and
3) assuming (1) and (2), how has wmbutler contributed to the co-oridination and project management of graphene-ui development so far?
I like to ask wmbutler :
What are the deliverables that you will be providing to the community in the process of performing the tasks defined in https://docs.google.com/document/d/14d9bBAyUoB9wcBpFnYoGpE1MF0RnOwMKpF2Z8eh0QkI/edit (quoting here):
1) Read and respond to all github issues posted by users. Request clarification where needed.
2) Maintain weekly Milestones with an achievable number of issues in each Milestone
3) Prioritize issues by urgency (a) bugs (b) required features (c) nice to have features
4) Remove duplicates and reference tracked items
5) Provide UX/UI visuals?
How are the milestones going to be defined and reported?
Will there be a Microsoft Project Management type of Gantt chart to schedule and track milesstones and reported issues?
Will there be a report that says how many issues resolved, how many pending, and how many delayed and/or cannot be resolved (and the reasons why)?
-
Great work so far, helping out the UI team and providing organization.. definitely worth $500/mo.
What are the deliverables that you will be providing to the community in the process of performing the tasks defined in https://docs.google.com/document/d/14d9bBAyUoB9wcBpFnYoGpE1MF0RnOwMKpF2Z8eh0QkI/edit (quoting here):
1) Read and respond to all github issues posted by users. Request clarification where needed.
2) Maintain weekly Milestones with an achievable number of issues in each Milestone
3) Prioritize issues by urgency (a) bugs (b) required features (c) nice to have features
4) Remove duplicates and reference tracked items
5) Provide UX/UI visuals?
How are the milestones going to be defined and reported?
https://github.com/cryptonomex/graphene-ui/issues?q=milestone%3A2.0.151111+is%3Aclosed
https://github.com/cryptonomex/graphene-ui/milestones/2.0.151125
https://github.com/cryptonomex/graphene-ui/milestones
He's been rounding up issues into manageable chunks, prioritizing, and managing expectations.. GitHub appears to be the tool of choice for tracking & reporting
-
Great work so far, helping out the UI team and providing organization.. definitely worth $500/mo.
What are the deliverables that you will be providing to the community in the process of performing the tasks defined in https://docs.google.com/document/d/14d9bBAyUoB9wcBpFnYoGpE1MF0RnOwMKpF2Z8eh0QkI/edit (quoting here):
1) Read and respond to all github issues posted by users. Request clarification where needed.
2) Maintain weekly Milestones with an achievable number of issues in each Milestone
3) Prioritize issues by urgency (a) bugs (b) required features (c) nice to have features
4) Remove duplicates and reference tracked items
5) Provide UX/UI visuals?
How are the milestones going to be defined and reported?
https://github.com/cryptonomex/graphene-ui/issues?q=milestone%3A2.0.151111+is%3Aclosed
https://github.com/cryptonomex/graphene-ui/milestones/2.0.151125
https://github.com/cryptonomex/graphene-ui/milestones
He's been rounding up issues into manageable chunks, prioritizing, and managing expectations.. GitHub appears to be the tool of choice for tracking & reporting
Thanks for providing the link. What I see is a bunch of jumbled up issues (enhancements requests, enhancement planned, bugs reported) grouped into a so-called 'milestones'. The 'milestones' are meaningless version coding and they have no description what-soever. Neither do they have a clearly defined estimated start and end dates (with estimated task duration) and who are the people assigned to the development tasks. IMHO, having such a grouping does not help in providing visibility, accountability nor manageability.
-
I would view his role as coordinating the bug reports and feature requests from the BitShares community and those volunteering or working on independent worker proposals. Our team has been shorthanded when it comes to sifting through and prioritizing the millions of issues so his efforts are appreciated.
At the end of the day BitShares is a Open Source community project that has been granted free use of our code. We will work on issues that the community sees as most pressing and also fit with our internal goals.
I view his role as one of organization / clarification rather than final decision making.
I support his efforts, the team has responded positively to his contributions thus far.
-
I would view his role as coordinating the bug reports and feature requests from the BitShares community and those volunteering or working on independent worker proposals. Our team has been shorthanded when it comes to sifting through and prioritizing the millions of issues so his efforts are appreciated.
At the end of the day BitShares is a Open Source community project that has been granted free use of our code. We will work on issues that the community sees as most pressing and also fit with our internal goals.
I view his role as one of organization / clarification rather than final decision making.
I support his efforts, the team has responded positively to his contributions thus far.
Thanks for your clarification and review of wmbutler's contribution.
I would like to suggest to the OP to change the role from 'Project Manager' to 'Project Co-ordinator' in order to avoid any potential misunderstandings.
-
@wmbutler , I appreciate your work and I'm willing to give it a go.
Just waiting for your response to cube's questions.
-
I appreciate the project management you're providing.
Here are some thoughts on what i like about our competitors products ..
Video Section
(http://i.imgur.com/MCdYJn0.jpg)
GitHubs screen layout is very nice and easy to interpret. I really like their sidebar menus and use of symbols instead of text.
(http://i.imgur.com/ZvpFcBQ.jpg)
Graphics to depict wallet distribution and asset distribution is also cool along with the current exchange rates
(http://i.imgur.com/iFOOirJ.jpg)
Use of charts - color coded to show whats appreciating/depreciating
(http://i.imgur.com/TDryUBQ.jpg)
OK, a nice to have buy buying directly from the chart :)
(http://i.imgur.com/SaI7idF.jpg)
-
I appreciate the project management you're providing.
Here are some thoughts on what i like about our competitors products ..
Video Section
(http://i.imgur.com/MCdYJn0.jpg)
GitHubs screen layout is very nice and easy to interpret. I really like their sidebar menus and use of symbols instead of text.
(http://i.imgur.com/ZvpFcBQ.jpg)
Graphics to depict wallet distribution and asset distribution is also cool along with the current exchange rates
(http://i.imgur.com/iFOOirJ.jpg)
Use of charts - color coded to show whats appreciating/depreciating
(http://i.imgur.com/TDryUBQ.jpg)
OK, a nice to have buy buying directly from the chart :)
(http://i.imgur.com/SaI7idF.jpg)
Video tutorials, yes!
-
This thread is awesome! Fantastic efforts by all here. I really think cube's questions are important and deserve a solid response.
Although I think it would be great to have the level of detail and definition cube mentioned (definition of milestones, their duration, reasons for issue resolution / disposition), it is clear from BM's comments wmbutler is demonstrating real value and helping the team to work more effectively. IMO that is very important.
I view this thread as helping dev management and moving it in the right direction. I also agree with cube's perspective and see that as a more detailed level of management the dev team should be working towards.
This is exactly what I was referring to when I said (https://bitsharestalk.org/index.php/topic,20123.msg258776.html#msg258776):
However, the empirical evidence of our progress since 10/13 has not inspired confidence. I concur with the others that say we must stay focused on completing the exchange functionality to support traders and ease of use. Define clear objectives and stick with them. Jakub is really doing a great job for you, don't hinder his efforts but rather strengthen them by demonstrating to this community you are making measurable progress towards identified goals / milestones. You need a good project manager, someone that knows how to use Microsoft Project and keep a team focused and on task. Project is good to measure progress. I've seen it used very effectively and it actually helped the team's morale, b/c it allowed everyone to see everybody else's progress and stumbling blocks.
My apologies to the OP for failing to mention his contributions. And thank you @bytemaster for recognizing the significance of these contributions. If you continue to improve like this we're sure to see the vision realized sooner rather than later!
-
The proposal seems to be not accepted. @wmbutler Could you make another proposal with addressing above questions and longer voting period?
-
#btstip "wmbutler" 1 GREATIDEA
#btstip "wmbutler" 1 FISTBUMP
-
Hey Tuck Fheman, here are the results of your tips...
- wmbutler (http://btstip.io/Home/Dashboard?username=wmbutler): has been credited 1 GREATIDEA
- wmbutler (http://btstip.io/Home/Dashboard?username=wmbutler): has been credited 1 FISTBUMP
Curious about BtsTip? Visit us at http://btstip.io and start tipping BTS on https://bitsharestalk.org/ today!
Source: https://bitsharestalk.org/index.php/topic,20144.msg259282/topicseen.html#msg259282
Created by hybridd (https://bitsharestalk.org/index.php?action=profile;u=40140)
-
The UI is getting better and better. I just saw now that we can star our favorite market!
Thank you for what you do. It's those little things that make life easier and wallet fun to use.
#btstip "wmbutler" 1 HIGHFIVE
Because you rock!
-
Hey rgcrypto, here are the results of your tips...
- wmbutler (http://btstip.io/Home/Dashboard?username=wmbutler): has been credited 1 HIGHFIVE
Curious about BtsTip? Visit us at http://btstip.io and start tipping BTS on https://bitsharestalk.org/ today!
Source: https://bitsharestalk.org/index.php/topic,20144.msg259286/topicseen.html#msg259286
Created by hybridd (https://bitsharestalk.org/index.php?action=profile;u=40140)
-
The proposal seems to be not accepted. @wmbutler Could you make another proposal with addressing above questions and longer voting period?
Voting period? I don't see a voting period in gui. Could somebody point me to summary of how the voting works? What are requirements of proposal to be accepted?
-
I think this is a very important role....great work wmbutler!
I appreciate this may be quite a challenge, but if you could increase the information available to include;
Priority - how urgent the resolution is considered to be
Developers - who is working on it
Completion estimate - the amount of time resolution likely to take
Status - active (being worked on,) standby (waiting for attention,) postponed (was active, now waiting for attention,) ready for testing, tested - fail, tested - passed, ready for release
Worker contract - who is providing the effort
There is probably more useful information we can come up with.....the objective would be to produce a fluid, web of categorised work items that can inform the community, current workers, potential workers and can adapt in an organised way.
No doubt each development worker will have their own change management processes.....but if we can merge all of it into a cohesive plan, the combined efforts will be more efficient and adaptive.
Great stuff so far though!!
-
The proposal seems to be not accepted. @wmbutler Could you make another proposal with addressing above questions and longer voting period?
Voting period? I don't see a voting period in gui. Could somebody point me to summary of how the voting works? What are requirements of proposal to be accepted?
That's the problem - there is still no guide on the most important thing in DPOS i.e. voting.
Other subjects are more or less covered but AFAIK voting has not be touched yet (@xeroc , please correct me if I'm wrong)
http://docs.bitshares.eu/bitshares/index.html
Sometimes I am a bit confused myself and regarding wmbutler's proposal I was not aware of any deadline so I missed my chance to support it.
-
I like to hear from the dev team members ( Daniel Larimer, Sigve Kvalsvik, James Calfee, Valentine Zavgorodnev, Fabian Schuh, cass) on their view of this Project Manager role - specifically:
1) Is such a role missing in CNX currently,
2) why is this role needed, and
3) assuming (1) and (2), how has wmbutler contributed to the co-oridination and project management of graphene-ui development so far?
I like to ask wmbutler :
What are the deliverables that you will be providing to the community in the process of performing the tasks defined in https://docs.google.com/document/d/14d9bBAyUoB9wcBpFnYoGpE1MF0RnOwMKpF2Z8eh0QkI/edit (quoting here):
1) Read and respond to all github issues posted by users. Request clarification where needed.
2) Maintain weekly Milestones with an achievable number of issues in each Milestone
3) Prioritize issues by urgency (a) bugs (b) required features (c) nice to have features
4) Remove duplicates and reference tracked items
5) Provide UX/UI visuals?
How are the milestones going to be defined and reported?
Will there be a Microsoft Project Management type of Gantt chart to schedule and track milesstones and reported issues?
Will there be a report that says how many issues resolved, how many pending, and how many delayed and/or cannot be resolved (and the reasons why)?
I fully support this, wmbutler has been a breath of fresh air since he started getting involved, providing excellent advise on UX and making some great mockups that help focus the development and discussion around it. He's also introduced weekly milestones and done some great work on organising the github issues.
The role of project manager is one that's been acutely missing from the Graphene development (both GUI and toolkit), it's been very ad-hoc so far so I'm very happy he's stepped up to get things organized. Having weekly milestones with clear priorities is great for us developers. Having a project manager also makes it much easier for new people to come in, as he has a clear view of what's being worked on, what's complicated and what's easy, and can direct new contributors to where their skills will be best utilised.
So to sum it up: He's great to have around for us in the development team, and definitely deserves being voted in.
-
All,
I'll try to address all questions in this post. First of all, I'm not big on titles. So, let's just say I'm trying to provide some order and clarity. I do not make the final call or set concrete deadlines. I'm simply trying to provide a general framework that should make priorities clear to the community. My worker proposal only covers the graphene-ui repo. I probably put 1-3 hours per day into it and am asking to be paid around $17 per day. If you like the work that I've done so far, it's a pretty fair deal.
@maqifrnswa
1) graphene-ui is a CNX project that is licensed to bitshares. Bitshares will be paying you to manage graphene. Is CNX ok with a non-employee managing their releases?
They seem to be fine with it so far. It was their suggestion that I carve out a worker proposal.
2) Will you have commit access/tag access to the offical repos?
I do have commit access to the graphene-ui repo
3) The role appears to be mostly community organizing, bug triage, illustration of goals (all very important for a successful project). In the end these are just "suggestions" (although probably very good ones) of priorities. Are you the one that will say "we won't release until X Y Z are fixed?" or is it more helping articulate highest priorities from the input from the community?
I will articulate the status of items in the github issues thread. I will also provide a summary announcement like the top of this thread every Wednesday or Thursday ( timed with the Wednesday release dates)
@cube
1) Is such a role missing in CNX currently
Yes
2) why is this role needed, and
Because bugs and needed UX/UI items were stacking up and were not getting resolved.
3) assuming (1) and (2), how has wmbutler contributed to the co-oridination and project management of graphene-ui development so far?
I have established weekly milestones and have provided UX mockups. Since I started working with the graphene-ui team, we have completed 2 Milestones and have squashed 24 bugs and have released 16 enhancements.
1) Read and respond to all github issues posted by users. Request clarification where needed.
2) Maintain weekly Milestones with an achievable number of issues in each Milestone
3) Prioritize issues by urgency (a) bugs (b) required features (c) nice to have features
4) Remove duplicates and reference tracked items
5) Provide UX/UI visuals?
I'm not sure I understand the question. Those are the deliverables.
How are the milestones going to be defined and reported?
Github
Closed Milestones (2.0.151111 and 2.0.151125)
https://github.com/cryptonomex/graphene-ui/milestones?state=closed
Open Milestones
https://github.com/cryptonomex/graphene-ui/milestones?state=open
Will there be a Microsoft Project Management type of Gantt chart to schedule and track milestones and reported issues?
No just github
Will there be a report that says how many issues resolved, how many pending, and how many delayed and/or cannot be resolved (and the reasons why)?
Yes, github
Thanks for providing the link. What I see is a bunch of jumbled up issues (enhancements requests, enhancement planned, bugs reported) grouped into a so-called 'milestones'. The 'milestones' are meaningless version coding and they have no description what-soever. Neither do they have a clearly defined estimated start and end dates (with estimated task duration) and who are the people assigned to the development tasks. IMHO, having such a grouping does not help in providing visibility, accountability nor manageability.
Watch the Milestones carefully. It allows for visibility, accountability and manageability, maybe just not in the way you are used to seeing it. It's not jumbled up. It's discrete tasks tagged and assigned to the proper team member with a due date and visibility into the progress. It's a great tool once you get the hang of it.
I would like to suggest to the OP to change the role from 'Project Manager' to 'Project Co-ordinator' in order to avoid any potential misunderstandings.
Make no difference to me what I'm called.
@jakub
Hopefully this message will suffice
@mike623317
Noted. We will break things down into bitesized pieces. Rome wasn't built in a day. I would suggest that you register for a github account and begin to interact there for UI requests. It's a more direct line to the devs and a much more purpose built tool that this discussion board.
@Thom
You hit the nail on the head. Things felt really sluggish after the release. That is why I offered my services. I truly believe we can make the UI awesome and will do everything in my power to help.
@clayop
How does one set the voting period. I did not see that in the syntax.
@Ben Mason
Thanks. We use a zenhub plugin for github wich adds a kanban board and includes priority and estimates. Github allows devs to claim the item already. We also have a test column although not a very formal testing process (yet). You can download zenhub and see the pipelines.
@svk
Thanks for the kind words. BTW, @svk created the markets list and favs based upon my UX. So, hopefully more of that is to follow.
-
#sharebits "wmbutler" 100 BEYONDBITCOIN
#sharebits "wmbutler" 1 FISTBUMP
#sharebits "wmbutler" 1 HIGHFIVE
#sharebits "wmbutler" 1 GREATIDEA
#sharebits "wmbutler" 100 TIPSHARES
-
Hey Tuck Fheman, here are the results of your tips...
- wmbutler (http://sharebits.io/Home/Dashboard?username=wmbutler): has been credited 100 BEYONDBITCOIN
- wmbutler (http://sharebits.io/Home/Dashboard?username=wmbutler): has been credited 1 FISTBUMP
- wmbutler (http://sharebits.io/Home/Dashboard?username=wmbutler): has been credited 1 HIGHFIVE
- wmbutler (http://sharebits.io/Home/Dashboard?username=wmbutler): has been credited 1 GREATIDEA
- wmbutler (http://sharebits.io/Home/Dashboard?username=wmbutler): has been credited 100 TIPSHARES
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,20144.msg259559/topicseen.html#msg259559
Created by hybridd (https://bitsharestalk.org/index.php?action=profile;u=40140)
-
All,
I resubmitted my worker proposal to begin 11/24. Hopefully this gives enough time for votes:
http://cryptofresh.com/workers
It's Bitshares UI Project Coordinator (1.14.9)
Vote from the cli:
update_worker_votes your-account {"vote_for":["1.14.9"]} true
-
Could we add a help link to the GUI that directs users to the forum helpdesk (https://bitsharestalk.org/index.php?action=helpdesk;sa=main).
Staff support could be rated by quality of experience and paid in BROWNIES (https://bitshares.openledger.info/?r=by24seven#/market/BROWNIE.PTS_BTS).
eg
* 10 BROWNIES
** 20 BROWNIES
*** 30 BROWNIES
**** 40 BROWNIES
***** 100 BROWNIES +5%
Users get 24 hour ticketed help and staff have an incentive to help.
-
You might want to take a look at the roadmap post made by Jakub.
https://bitsharestalk.org/index.php/topic,20171.0.html
Maybe that will also help in your proposed role. I also think you are asking for too little each month. :)
-
You have my vote (as a proxy).
-
we need this role
-
@TravelsAsia I looked at it and directed users to github. A lot of those comments were a month old and many issues have been fixed.
All,
I need a few more votes within the next 16 hours to complete the worker proposal:
update_worker_votes your-account {"vote_for":["1.14.9"]} true
-
I need a few more votes within the next 16 hours to complete the worker proposal:
update_worker_votes your-account {"vote_for":["1.14.9"]} true
Pinged @xeroc and @mindphlux
-
fixed
-
I need a few more votes within the next 16 hours to complete the worker proposal:
update_worker_votes your-account {"vote_for":["1.14.9"]} true
Pinged @xeroc and @mindphlux
and @bytemaster
-
Exellent! @wmbutler +5%
-
Any updates, @wmbutler ?
Looks like we've missed the last two milestones 15.12.09 & 15.12.16.
-
Any updates, @wmbutler ?
Looks like we've missed the last two milestones 15.12.09 & 15.12.16.
There will be a release today. The main reason things have gotten pushed back is that I've been busy moving into a new apartment.
-
@wmbutler , I do realize it's a holiday season but I think it's a bit unfair to be paid $17 per day and remain without a single update for the last 3 weeks.
Maybe you are contributing but not updating. Just let us know.
@svk , have you had any contact with wmbutler lately?
-
wmbutler was on holiday for 10 days or so .. he has started to work on the gui again
-
Like xeroc said he was on holiday, we have heard from him in the dev slack chat.
-
Any news? Last activity is on 12 days ago. Before that day, it's Dec. 10.
https://github.com/wmbutler?tab=activity
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#636
[member=6036]wmbutler[/member]
How about a hover tooltip to reveal the memo as a quick fix.
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#633
[member=6036]wmbutler[/member]
@svk31 do you have enough info to squash this bug? Can you reproduce?
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#630
[member=6036]wmbutler[/member]
Voting needs a UX overhaul as well. I'll work on this.
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#622
[member=6036]wmbutler[/member]
I agree with [member=12639]valzav[/member] I'd keep them and go lighter as a compromise. Personally I like them as is. But I UX'd it :)
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#621
[member=6036]wmbutler[/member]
Not sure I understand. The star indicates that it's a favorite.
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#613
[member=6036]wmbutler[/member]
Let's keep the toggles on the right side.
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#612
[member=6036]wmbutler[/member]
Quick fix.
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#602
[member=6036]wmbutler[/member]
I'm not convinced this is an issue. @svk31 ?
12 days ago
wmbutler closed issue cryptonomex/graphene-ui#529
[member=6036]wmbutler[/member]
Market Volumes in the Same Unit
12 days ago
wmbutler closed issue cryptonomex/graphene-ui#303
[member=6036]wmbutler[/member]
fetch extended history
12 days ago
wmbutler closed issue cryptonomex/graphene-ui#301
[member=6036]wmbutler[/member]
add option of one letter trx labels to Operation.jsx
12 days ago
wmbutler closed issue cryptonomex/graphene-ui#610
[member=6036]wmbutler[/member]
Firefox browser unsupported
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#610
[member=6036]wmbutler[/member]
Closing but we know this needs to be a priority after base features and bugs are in place.
12 days ago
wmbutler closed issue cryptonomex/graphene-ui#456
[member=6036]wmbutler[/member]
When claiming from many small balanceid, the transaction times out
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#456
[member=6036]wmbutler[/member]
Closing due to no feedback for many months.
12 days ago
wmbutler closed issue cryptonomex/graphene-ui#233
[member=6036]wmbutler[/member]
Collateral dialog precision and editing issues
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#233
[member=6036]wmbutler[/member]
Closing since no response from [member=29285]theoreticalbts[/member]
12 days ago
wmbutler closed issue cryptonomex/graphene-ui#226
[member=6036]wmbutler[/member]
Show open orders in the account overview and in the account orders sections
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#226
[member=6036]wmbutler[/member]
Closing this since we have a good open orders area.
12 days ago
wmbutler closed issue cryptonomex/graphene-ui#530
[member=6036]wmbutler[/member]
Support for high latency connections
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#530
[member=6036]wmbutler[/member]
This is a limitation of sockets and probably not worth the effort.
12 days ago
wmbutler commented on issue cryptonomex/graphene-ui#577
[member=6036]wmbutler[/member]
@cassiopaia placing this in 0106
12 days ago
wmbutler closed issue cryptonomex/graphene-ui#375
[member=6036]wmbutler[/member]
The cross-hair line on the price history chart jumps unexpectedly
on Dec 10, 2015
wmbutler commented on issue cryptonomex/graphene-ui#600
[member=6036]wmbutler[/member]
Not sure I'll be able to UX this in time for 1216. @svk31 take a shot at it if it's super high priority, otherwise I can get it completed before 1223
on Dec 10, 2015
wmbutler opened issue cryptonomex/graphene-ui#601
[member=6036]wmbutler[/member]
Switch the default chart interval to 1 day
on Dec 10, 2015
wmbutler commented on issue cryptonomex/graphene-ui#590
[member=6036]wmbutler[/member]
I would drop the: 'as collateral' for just 'collateral' 'in open orders' for just 'open orders'
on Dec 10, 2015
wmbutler commented on issue cryptonomex/graphene-ui#543
[member=6036]wmbutler[/member]
@jcalfee is this one in your realm? Moving to 1216.
on Dec 10, 2015
wmbutler commented on issue cryptonomex/graphene-ui#255
[member=6036]wmbutler[/member]
[member=12639]valzav[/member] status?
on Dec 10, 2015
wmbutler closed issue cryptonomex/graphene-ui#282
[member=6036]wmbutler[/member]
in Safari wallet backup download button opens new empty window, nothing downloaded
on Dec 10, 2015
wmbutler commented on issue cryptonomex/graphene-ui#282
[member=6036]wmbutler[/member]
Closed for now. Can revisit when we focus on Safari compatibility.
-
Still no updates and the milestones have stood still...
Is it possible to vote out a worker?
-
Still no updates and the milestones have stood still...
Is it possible to vote out a worker?
Sure. Just vote against it.
-
wmbutler was on holiday for 10 days or so .. he has started to work on the gui again
@xeroc are you in contact with him? 2 weeks have passed
-
He has been busy finishing up the move to a new apartment
I hope to see more action back from Monday
-
He has been busy finishing up the move to a new apartment
I hope to see more action back from Monday
We will feel better if we can get a notification IN ADVANCE when a paid contributor temporarily unable to work as normal, for example had a plan of holidays etc.
-
He has been busy finishing up the move to a new apartment
I hope to see more action back from Monday
We will feel better if we can get a notification IN ADVANCE when a paid contributor temporarily unable to work as normal, for example had a plan of holidays etc.
Maybe it was an emergency vacation where his destination decided to completely ban the usage of the Internet for a simple update.
-
Any update?
-
Any update?
https://github.com/wmbutler
Last contribution Dec 9.
The worker is still up tho.