Quote from: clayop on November 21, 2015, 01:33:38 AM
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?

Hey rgcrypto, here are the results of your tips...

• wmbutler: has been credited 1 HIGHFIVE

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 Tuck Fheman, here are the results of your tips...

• wmbutler: has been credited 1 GREATIDEA
• wmbutler: has been credited 1 FISTBUMP

#btstip "wmbutler" 1 GREATIDEA
#btstip "wmbutler" 1 FISTBUMP

The proposal seems to be not accepted. @wmbutler Could you make another proposal with addressing above questions and longer voting period?

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:

Quote
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!

Quote from: mike623317 on November 20, 2015, 09:34:46 PM
I appreciate the project management you're providing.
Here are some thoughts on what i like about our competitors products ..

Video Section


GitHubs screen layout is very nice and easy to interpret. I really like their sidebar menus and use of symbols instead of text.


Graphics to depict wallet distribution and asset distribution is also cool along with the current exchange rates


Use of charts - color coded to show whats appreciating/depreciating


OK, a nice to have buy buying directly from the chart :)

Video tutorials, yes!

I appreciate the project management you're providing.
Here are some thoughts on what i like about our competitors products ..

Video Section


GitHubs screen layout is very nice and easy to interpret. I really like their sidebar menus and use of symbols instead of text.


Graphics to depict wallet distribution and asset distribution is also cool along with the current exchange rates


Use of charts - color coded to show whats appreciating/depreciating


OK, a nice to have buy buying directly from the chart :)

@wmbutler , I appreciate your work and I'm willing to give it a go.
Just waiting for your response to cube's questions.

Quote from: bytemaster on November 20, 2015, 05:50:56 PM
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.

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.

Quote from: roadscape on November 20, 2015, 05:35:00 PM
Great work so far, helping out the UI team and providing organization.. definitely worth $500/mo.

Quote from: cube on November 20, 2015, 05:28:05 PM
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.

Great work so far, helping out the UI team and providing organization.. definitely worth $500/mo.

Quote from: cube on November 20, 2015, 05:28:05 PM
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

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)?