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 repo3) 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)@cube1) Is such a role missing in CNX currently
Yes2) 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?
GithubClosed Milestones (2.0.151111 and 2.0.151125)
https://github.com/cryptonomex/graphene-ui/milestones?state=closedOpen Milestones
https://github.com/cryptonomex/graphene-ui/milestones?state=openWill there be a Microsoft Project Management type of Gantt chart to schedule and track milestones and reported issues?
No just githubWill 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, githubThanks 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 MasonThanks. 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.
Topic: Graphene-ui update and Worker Proposal for UI Project Manager (Read 14036 times)
