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.

@xeroc I moved my witness and cli-wallet to a new machine with more disk space, but when I attempt to fire up the cli-wallet, I get this:

Logging RPC to file: logs/rpc/rpc.log
1806965ms th_a       main.cpp:117                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
1806966ms th_a       main.cpp:121                  main                 ] nathan_pub_key: BTS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
1806966ms th_a       main.cpp:122                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
1806966ms th_a       main.cpp:169                  main                 ] wdata.ws_server: ws://172.17.0.1:8090
1806968ms th_a       main.cpp:174                  main                 ] wdata.ws_user:  wdata.ws_password: 
Please use the set_password method to initialize a new wallet before continuing
1806971ms th_a       main.cpp:240                  main                 ] Listening for incoming HTTP RPC requests on 0.0.0.0:8092
1806972ms th_a       main.cpp:268                  main                 ] Entering Daemon Mode, ^C to exit


@xeroc possibly. I need to make sure that I understand the nature of the issues so I can actually help. I have a toolset for assisting with UX/UI but not as much when it comes to the technical underpinnings of BTS. I'll spend some time reviewing the graphene repo issues to attempt to wrap my head around it.

@Bhuz I understand your concern. I'd say being a witness is a long term play. I am expending real hours on a daily basis to improve the experience. In the past week, I easily invested 30 hours. I think the pay that I'm asking for is a token amount and is representative of my commitment to BTS. Oh, and thanks for the tip. Very good of you!

@fuzzy, to clarify, I did not fix those bugs (ok, I fixed a spelling error), but I did read through the 72 issues, classify them, organize them into sprints, talked daily with developers about process and kept them in the loop on progress and UX/UI'd potential solutions to problems. And, lastly gave 'em a slap on the shoulder for a job well done.

Hopefully I can get the proposal together. I left the private key to my server where I have the cli_wallet and home and I'm about to get on a very small boat to head down the Atlantic Coast. I'll send pics!

I really hope someone can make this happen. I've never been able to make the 0.9.x wallet work reliably on OS X.

All,

About a week and a half ago, the graphene-ui devs let me run an experiment with prioritizing issues and setting up milestones with weekly releases. I am happy to report that the team did an amazing job of knocking out 32 bugs and enhancements. One of my biggest concerns with Bitshares was the persistence of the same issues week after week. It is my goal to listen to requests on this board (and more importantly on the graphene-ui github site) https://github.com/cryptonomex/graphene-ui/issues.

I will make every effort to respond, clarify and prioritize features and bugs in an effort to make the bitshares2 wallet the best it can be. Releases will occur every Wednesday, with urgent fixes being released in between as required.

Here is the list of bugs that were fixed last week:
https://github.com/cryptonomex/graphene-ui/issues?q=milestone%3A2.0.151111+is%3Aclosed

Here is what the team is working on for the 11/18 release:
https://github.com/cryptonomex/graphene-ui/milestones/2.0.151118

I encourage you to discuss software issue on github. Get an account, it's free. Start an issue. Go slowly when explaining your issue. Do not bundle problems. If you have 3 distinct bugs or feature requests, create separate issues. Only submit the most pressing issues and really think through the urgency before posting. We are trying to triage those issues that hurt BTS perception. Once those are resolved we can move on to the all the other amazing features that are possible.

I will be submitting a Worker Proposal to serve as the Project Manager for the UI Team to help streamline this process and communicate needs / wants / priorities. I hope that you find value in what I am doing an you vote to accept my worker proposal. The text of the proposal is here and I will likely submit it to the blockchain for voting tomorrow.

Worker Proposal
https://docs.google.com/document/d/14d9bBAyUoB9wcBpFnYoGpE1MF0RnOwMKpF2Z8eh0QkI/edit?usp=sharing

Thanks for listening.

My bad. I've been using ZenHub as a plugin for github for so long that I thought the voting was a standard part of the github interface. Sorry for the confusion.

We do have a summary count of all the comments on a particular item so why don't we try having you guys leave feedback on the message and we can use the comment count to help guide the community interest level.

All,

I proposed that we try using Github's built in voting to help convey to the graphene-ui developers where the community feels the most work is needed. You need to register for a github account to vote.

Issues are tracked here: https://github.com/cryptonomex/graphene-ui/issues

As you read through the issues, vote by clicking the "plus 1" button in the upper right hand corner of the original post to reinforce your support of that issue. This will really help consolidate sentiment. You can also report issues there, but do a quick search first to ensure you aren't duplicating one already on the books.