Quote from: Selsonblue on March 07, 2017, 03:53:30 PM

Quote from: techwriterjoe on March 07, 2017, 01:47:39 PM

I suggest running an agile type project management style. Perhaps make a larger roadmap, but only give dates for specific goals that can be completed within 2-3 weeks. Choose your sprint cycles 2 or 3 weeks. So only commit to any work for the 2-3 weeks and don't worry about dating the roadmap beyond that.

1. Scrum / agile has worked in geographically dispersed dev groups in the past (my experiences) - but there has to be 100% buy in and a good amount of daily communication. - Both of which are probably not going to happen at this late stage of development.

2. We all want to be informed and such. But it wouldnt be worth spending an hour or two to produce a roadmap when there is "not much left" to begin with.

If you want to suggest ways to assist with the project, research use cases, help prioritize the PR campaign or development ideas; you need to bring the discussion to slack and discuss! Clivemy and myself (boardwalk), jibble, coralreefer, bgjjj, and others are in there discussing the PR stuff almost daily. The more the merrier right?

Also, We have publicly available PR and development backlogs created -- Coralreefer (miner software dev.) has given a good amount of detail on what he sees as his next tasks for miner development. These boards are updated as developments take place. Use them as your first source for info.

PR tracking: https://trello.com/b/2efzgZZT/pr-tasks
Development Backlog: https://trello.com/b/fPdyn5Vp/development-backlog

EK is at the point were his time is better spent coding. Trying to write release notes / project updates before he figures the code out is a nearly impossible task. You cant switch to agile / scrum mid way through a development cycle and expect a better outcome. Patience is a virtue.

"EK is at the point were his time is better spent coding." completely agree.