209 похожих чатов

The biggest problem with Jared is that people don’t want

to work with him - his behaviour drives talent away from the community. Given that he (supposedly) works on DigiByte Core that is definitely a problem for DigiByte, since we badly need people working on it.

For the last couple of years, pretty much all significant progress to improve DigiByte has been been made on things that Jared has had no involvement with. Those involved have realised that the best way to get things done in this community is to ignore Jared, and avoid having to work with him, if you possibly can. Unfortunately, when it comes to DigiByte Core that is currently almost impossible.

The idea of forking DigiByte Core is pretty pointless in my opinion. This is not a code problem. This is a people problem - actually a person problem. The best solution that I can see is to create a new core repository which Jared has no admin rights over, and move development there. Perhaps if developers can be reassured that their work won’t be thrown out or their access revoked by an unstable founder, they might be encouraged to get more involved. Some in the community might initially balk at the idea, but if it got things moving and real progress was demonstrated people would soon loose their misgivings.

The challenge of course is finding the support to make such an apparently drastic step. Nobody wants to haven to do it, which is likely why we continue to go around in circles, hoping the situation will improve. And every few months we are back for another round of arguing and infighting.

It’s clear to me that it may be the only move left if we want DigiByte to move forwards. I would support this move. But how many other’s would?

1 ответов

4 просмотра

Copying the repository would result in a fork, in the case that it were contested with 2 separate code evolutions. Then the miners would vote with hash power.

Похожие вопросы

Обсуждают сегодня

Карта сайта