Blockchain technique for agile software development framework
An example operation may include one or more of transmitting a copy of the master ledger when a developer joins a network, receiving proposed changes to the master ledger, and updating the master ledger at the branch hash.
1. A method, comprising:
transmitting, via a blockchain in a network, a copy of a master ledger to a plurality of developers associated with a plurality of corresponding developer branches in the blockchain network;
receiving, by the blockchain, a proposed change to the master ledger from a developer of the plurality of developers;
identifying, by the blockchain, that the proposed change satisfies a smart contract setting forth requirements agreed on by the plurality of developers for submitting proposed changes to the master ledger; and
updating, by the blockchain, the master ledger at a branch hash based on the identifying; and
initiating, by the blockchain, a forced push of an origin hash to the plurality of corresponding developer branches to enforce synchronization across the plurality of corresponding developer branches.
2. The method of claim 1 , wherein the copy of the master ledger comprises:
a code and history of changes made to software associated with the master ledger.
3. The method of claim 1 , wherein the receiving the proposed changes comprises:
receiving a modified copy of the master ledger, where the modifications are performed within a firewall of the network for the developer.
4. The method of claim 1 , wherein the master ledger is a trusted history of a project.
5. The method of claim 1 , wherein the smart contract provides a historical trace of downloads and includes a signature when a child ledger commit is submitted for a vote.
6. A server comprising:
a memory storing one or more instructions; and
a processor that when executing the one or more instructions is configured to:
transmit a copy of a master ledger to a plurality of developers associated with a plurality of corresponding developer branches in the blockchain network;
receive a proposed change to the master ledger from a developer of the plurality of developers;
identify that the proposed change satisfies a smart contract setting forth requirements agreed on by the plurality of developers for submitting proposed changes to the master ledger; and
update the master ledger at a branch hash based on the identification; and
initiate a forced push of an origin hash to the plurality of corresponding developer branches to enforce synchronization across the plurality of corresponding developer branches.
7. The server of claim 6 , wherein the copy of the master ledger comprises:
a code and history of changes made to software associated with the master ledger.
8. The server system of claim 6 , wherein, when the processor is configured to receive the prosed change, the processor further configured to:
receive modified copy of the code, where the modifications to the modified copy are performed within a firewall of the network for the developer.
9. The server of claim 6 , wherein the master ledger is a trusted history of a project.
10. The server of claim 6 , wherein the smart contract provides a historical trace of downloads and includes a signature when a child ledger commit is submitted for a vote.
11. A non-transitory computer readable medium comprising one or more instructions that when executed by a processor configure the processor to perform:
transmitting a copy of a master ledger to a plurality of developers associated with a plurality of corresponding developer branches in the blockchain network;
receiving a proposed change to the master ledger from a developer of the plurality of developers;
identifying, by the blockchain, that the proposed change satisfies a smart contract setting forth requirements agreed on by the plurality of developers for submitting proposed changes to the master ledger; and
updating the master ledger at a branch hash based on the identifying; and
initiating a forced push of an origin hash to the plurality of corresponding developer branches to enforce synchronization across the plurality of corresponding developer branches.
12. The non-transitory computer readable medium of claim 11 , wherein the copy of the master ledger comprises:
a code and history of changes made to software associated with the master ledger.
13. The non-transitory computer readable medium of claim 11 , wherein the one or more instructions further configure the processor to perform:
receiving a modified copy of the master ledger, where the modifications are performed within a firewall of the network for the developer.
14. The non-transitory computer readable medium of claim 11 , wherein the master ledger includes information corresponding to a trusted history of a project.