This is a brilliant idea. This is also in compatible with how collaborative version management systems like Git work. The process does not require anything to be erased. Every little change is done in a new version that can later be merged with the main version to be used in production.
As you say, the main advantage of using a blockchain is the lack of a centralized locus of control. Another is redundancy. Everyone retains access to the entire intact code repository forever. A third advantage is the ability to easily monetize open source coding as the additions to the code base can be upvoted.
On Steem, there was an app called Utopian.io. It was created for the purpose of rewarding open source development. The catch was that it was merely for rewarding contributions on GitHub. One could make posts about one's contribitions containing proof of actually contributing. The project died.
The app you are proposing would be different in the sense that the code would be written directly on Hive. I think such a project would be much more viable.
I argue Utopian.io is totally different than what @taskmaster4450le is proposing... Utopian couldn't be a Git alternative, (I'm using Git name here because Github and its alternatives are based on Git,) and couldn't record the data by itself.
The thing Hive needs is a way to (I think this part will be easy,) as well as built-in decentralized storage for files that aren't code. (Some of these files can go up to hundreds of GB in space.) There also should be a way to prevent abuse as someone could upload terabytes of spam to intentionally clutter the system.
If those two parts werent there, it could as well be a Web2 platform, and there are already many alternatives to Github on Web2.
I wouldnt think it would mirror Utopian. I agree totally different concept.
This part would be rather easy. The app would pull from two databases: the code is on Hive and the documentation is on a centralized server somewhere.
Posted Using LeoFinance Beta
Wouldn't that defeat the point?
The documentation could be on chain as well, if user so chooses. It is currently cheap to do so. But if space on chain becomes scarce, then the user could opt for another form of storage. IPFS is another decentralized storage type.
Of course, it is different. Utopian.io uses GitHub as the code repository. What @taskmaster is proposing is storing the code on chain, if I'm not mistaken.
It's already possible to try and clutter Hive with garbage. But it costs money to do so. One must have Hive Power to gain sufficient resource credits.
That's fair~
Yes. I dont know the need for rewarding the contributions per se. I guess that could be worked into the project. My reasoning here is simply the ability for open source developers to operate without fear of having their work shut down. Since Hive is a decentralized database, the data is all there.
My sense is that a frontend only needs to be build to assimilate the data as needed and to provide the features that the other Gits provide.
Glad you think it is feasible.
Posted Using LeoFinance Beta
I think it's totally feasible and the value proposition makes sense. Rewarding would not need to be built in unless as post rewards if one wants to post about one's contributions. It would be easy to verify the contributions were by the same account as the poster.
Yeah. If using as a simple database, simply have all post reject rewards.
Posted Using LeoFinance Beta
I was thinking more along the lines of storing the code as just text, not as contents in comments. To monetize one's contributions, a separate post could be made containing references to the work done.