Viewing a response to: @develcuy/re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181001t004050638z
We have greatly improved organizational development practices since the several prior forks, including real adherence to Agile development, but we havenโt improved enough. The post mortem of HF20 will make us sick and cry. Our Standards will increase. I want the witnessโ Gatekeeping Standards even higher. There is a silver lining in struggles or failure โ it can be the beginning of new strengths.
author | ned |
---|---|
permlink | re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181001t004731785z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-01 00:47:30 |
last_update | 2018-10-01 00:47:30 |
depth | 7 |
children | 13 |
last_payout | 2018-10-08 00:47:30 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 400 |
author_reputation | 94,449,026,656,258 |
root_title | "HF20 Update: Restoring Continuity" |
beneficiaries | [] |
max_accepted_payout | 0.000 HBD |
percent_hbd | 10,000 |
post_id | 72,382,052 |
net_rshares | 0 |
Its not easy to focus on the business challenges and the software development at the same time especially in such a community where there are lots of people whose lively hood is from STEEM. So personally I would say, understanding is a good starting point and this can be the beginning of a new era. By adapting a model similar to Wikipedia and true to FOSS principles, IMHO this project can set standards in the blockchain software development. > including real adherence to Agile development Agile, yes -- but need "Test Driven Agile Development". This is the **ONLY** shortfall and everything else will fall in place auto-magically. Few points: - Lets make sure that every commit is tested on the TESTNET (blackbox) - if possible write white box testing can be introduced - start using CI - CD Your biggest strength is an incredible community & wishing STEEM all the best!
author | bobinson |
---|---|
permlink | re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181001t045356458z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-01 04:53:30 |
last_update | 2018-10-01 04:53:30 |
depth | 8 |
children | 11 |
last_payout | 2018-10-08 04:53:30 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 1.172 HBD |
curator_payout_value | 0.387 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 883 |
author_reputation | 55,343,141,313,811 |
root_title | "HF20 Update: Restoring Continuity" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,390,815 |
net_rshares | 786,556,754,142 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
ned | 0 | 737,575,853,608 | 1% | ||
murh | 0 | 4,443,335,977 | 100% | ||
gniewomir-sotel | 0 | 3,337,915,531 | 100% | ||
airhawk-project | 0 | 37,101,626,982 | 100% | ||
kayceefresh | 0 | 3,036,383,046 | 100% | ||
otto11 | 0 | 516,700,436 | 100% | ||
cryptohook | 0 | 0 | 100% | ||
danish1 | 0 | 544,938,562 | 100% |
@bobison, If you want to set standards, then start by following the lead of existing mature FOSS projects. For example Drupal (the biggest dev-focused FOSS project worldwide). It is 17 years old, [Drupal adopted TDD 10 years ago](buytaert.net/embracing-test-driven-development) and had its own moments of radical changes, but [Drupal has tradition of communicating change pretty well! (starting from its founder & project lead)](https://dri.es/why-the-big-architectural-changes-in-drupal-8)! In short, there is no need to reinvent the wheel @ned, if you really want to keep steem for the long run, make it formal, and if you know that you can't hold the technical weight of the project, then hire a competent CTO ;)
author | develcuy |
---|---|
permlink | re-bobinson-re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181002t042253727z |
category | steem |
json_metadata | {"tags":["steem"],"users":["bobison","ned"],"links":["buytaert.net/embracing-test-driven-development","https://dri.es/why-the-big-architectural-changes-in-drupal-8"],"app":"steemit/0.1"} |
created | 2018-10-02 04:23:00 |
last_update | 2018-10-02 04:23:00 |
depth | 9 |
children | 7 |
last_payout | 2018-10-09 04:23:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.117 HBD |
curator_payout_value | 0.037 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 715 |
author_reputation | 4,853,554,441,622 |
root_title | "HF20 Update: Restoring Continuity" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 0 |
post_id | 72,455,511 |
net_rshares | 80,303,133,766 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
develcuy | 0 | 68,545,192,325 | 100% | ||
bobinson | 0 | 11,757,941,441 | 100% |
Agree @develcuy Drupal is not alone. gcc, Bash, emacs etc are even older than drupal and are still holding up. I would prefer to go Python's route though (as opposed to even Linux's). Why I said Python instead of Drupal is because of the recent CVEs against Drupal which was lurking there for so many years. But in general, we are saying the same thing :-)
author | bobinson |
---|---|
permlink | re-develcuy-re-bobinson-re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181002t073655423z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1","users":["develcuy"]} |
created | 2018-10-02 07:36:57 |
last_update | 2018-10-02 07:37:36 |
depth | 10 |
children | 6 |
last_payout | 2018-10-09 07:36:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 363 |
author_reputation | 55,343,141,313,811 |
root_title | "HF20 Update: Restoring Continuity" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,463,574 |
net_rshares | 0 |
Valuable input. Thank you.
author | ned |
---|---|
permlink | re-bobinson-re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181001t054605578z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-01 05:46:06 |
last_update | 2018-10-01 05:46:06 |
depth | 9 |
children | 2 |
last_payout | 2018-10-08 05:46:06 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 26 |
author_reputation | 94,449,026,656,258 |
root_title | "HF20 Update: Restoring Continuity" |
beneficiaries | [] |
max_accepted_payout | 0.000 HBD |
percent_hbd | 10,000 |
post_id | 72,392,685 |
net_rshares | 10,054,941,349 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
bobinson | 0 | 10,054,941,349 | 100% |
To add to it, I wrote the following else where: One is a suggestion and 2 is about usability aspect and a possible opportunity of STEEM #1. ## Suggestions Why don't everyone - community, witnesses and STEEM Inc take this opportunity to create a truly decentralized, community driven project by introducing a QA process which will be independent of the blockchain development ? The Goals can be formulated from the witness testaments regarding HF20 written by the developers. A DAO can be created and this can do the following but not limited to it: - help the developers to run the TESTNET - ensure that the code has enough test coverage - maintain the CI-CD pipeline - generate transactions mimicing the MAIN-NET - publish test reports on a periodic basis - help to bring in bug bounties - create a code of conduct - Attempt to join various blockchain consortiums - work with Academicians in reasearch A starting point can be using something like https://gitlab.com/SBCDAO/ #2.  On this, the requirement is this "have volunteer assignments for various surveys and volunteer + their specific task on a immutable fashion". Hyperledger based private chain was the first preference because the geo-graphical region I am in has a blockchain academy run by the government and it is a partner of hyperledger + stellar. The technical volunteers wanted an open system like wikipedia and Openstreetmap so that its possible for anyone and everyone to audit the data. We managed to convince the stake holders for a public chain and due to obvious reasons STEEM blockchain was the first choice. Right now damage assessment for the homes are over and a damage assessment for the infrastructure is about to begin. The proof of volunteer assignment and task assignment is already on private STEEM chain. Now, the question is, unlike a private deployment which is controlled and tested, the public chain behaves ways like what happened this week. So, is it possible to for anyone to ensure that in the next 2 - 3 months time there will not unexpected behaviors happening ? I am well aware that you or any of the witnesses will not be able answer this question. But if the STEEM Inc has any means to contact, this could be something that can be taken up. The next opportunity could be Ushahidi rescue request platform who is interested in on a blockchain -- this also open. Since there is no way I can communicate to anyone in STEEM Inc, just sharing it here so that someone takes it up if it makes sense. timcliff September 30, 2018 10:39 PM @bobinson it is just as possible for a consensus upgrade on Hyperledger to experience the same issues we went through here on Steem
author | bobinson |
---|---|
permlink | re-ned-re-bobinson-re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181001t055554423z |
category | steem |
json_metadata | {"tags":["steem"],"users":["bobinson"],"image":["https://cdn.steemitimages.com/DQmQSeXsJJXGNxmSMcMruaS6uAeKe1Q9Jn7U7UbFPweAWJt/12345.png"],"links":["https://gitlab.com/SBCDAO/"],"app":"steemit/0.1"} |
created | 2018-10-01 05:55:33 |
last_update | 2018-10-01 05:55:33 |
depth | 10 |
children | 0 |
last_payout | 2018-10-08 05:55:33 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.053 HBD |
curator_payout_value | 0.017 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 2,790 |
author_reputation | 55,343,141,313,811 |
root_title | "HF20 Update: Restoring Continuity" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,393,056 |
net_rshares | 36,364,901,805 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
airhawk-project | 0 | 36,364,901,805 | 100% |
@ned : followup work & status https://hackmd.io/s/ByT1BuG5m
author | bobinson |
---|---|
permlink | re-ned-re-bobinson-re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181003t194652869z |
category | steem |
json_metadata | {"tags":["steem"],"users":["ned"],"links":["https://hackmd.io/s/ByT1BuG5m"],"app":"steemit/0.1"} |
created | 2018-10-03 19:46:54 |
last_update | 2018-10-03 19:46:54 |
depth | 10 |
children | 0 |
last_payout | 2018-10-10 19:46:54 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 59 |
author_reputation | 55,343,141,313,811 |
root_title | "HF20 Update: Restoring Continuity" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,567,165 |
net_rshares | 0 |
That is good will from you @ned! However, having a formal process requires more than just good will. I've been involved on a CMMI level 3 certification about 6 years ago, it was way too boring back then, but it brought the ability to scale. Not an easy process btw, we had to make hard decisions and to deal with key people leaving the company, but things stabilized over time. So, you had the guts to let HF20 go, how about letting your company to formalize with working industry standards?
author | develcuy |
---|---|
permlink | re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181001t010158242z |
category | steem |
json_metadata | {"tags":["steem"],"users":["ned"],"app":"steemit/0.1"} |
created | 2018-10-01 01:02:03 |
last_update | 2018-10-01 01:04:42 |
depth | 8 |
children | 0 |
last_payout | 2018-10-08 01:02:03 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.095 HBD |
curator_payout_value | 0.031 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 491 |
author_reputation | 4,853,554,441,622 |
root_title | "HF20 Update: Restoring Continuity" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 0 |
post_id | 72,382,559 |
net_rshares | 63,535,193,044 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
develcuy | 0 | 63,535,193,044 | 100% |