Post #31396

e81a4b0c081090804aa7dce1ecc436f1ebd31bf3d3ea06fa1b84a3a930b9b734
f14cc86a78084a14e5293ee7b828771c956709098abd4f1ce2af6ccd1c1f9ecd
e2c61429397da55a5ee7749088023feb12e0e8e261dfeba32ee7c0794f9a12f8
Signature verified

The signature from the blockchain entry has been verified against an identity on this server.

{"entry_date":1611160904,"post_data":{"edit_count":0,"last_edit_date":0,"last_edit_user_id":0,"message_sha512":"b0e044ff2951e8b14be3b1e44344955858b3a15b252500130b518c504dca3f56d3b30c5d1f0b13c3fd4ae3a137ef56cf285212434c162bb8e2d9eb0ea1cbffb7","node_id":52,"post_date":1611160904,"thread_id":5637,"user_id":29},"post_link":"https:\/\/forum.factomprotocol.org\/threads\/batched-amendment-strategy-and-resource-director-proposal.5637\/post-31396"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
Batched Amendment - Strategy and Resource Director Proposal
[QUOTE="Niels Klomp, post: 31395, member: 8"]
roadmaps are a living document. It gets changed over time, especially in agile times like these. Obviously not every week or month, but priorities shift if something takes of for instance or doesn't seem to work. That is part of the game. On of the biggest mistakes though is trying to communicate a really elaborate roadmap with many things in there. They you are setting yourself up for (perceived) failure, because the chances of underdelivering are very big.
[/QUOTE]

We do have more issues to track than many projects. I think tracking them and making progress of the critical items will not hurt us.

Historically we have been slammed by stability issues which killed momentum on goals that otherwise would have been our top priorities. Stability as an issue has largely gone away, with just elections during upgrades as our current known risk, cross our fingers.

Nothing in the roadmap currently should impact stability so I'm less concerned with the number of items in the current list.
This is the raw content, without BBCode parsing.
Top