A proposal to make SpiritSwap front-end open public

Part of SpiritSwap DAO’s main ambition is to have as many people as possible contribute to the growth and expansion of SpiritSwap. For this to occur, there needs to be complete transparency of the exchanges repository files enabling contributing developers to access to SpiritSwaps front-end files.

In achieving this, the process and barriers of entry to contribute to SpiritSwap, for any would-be contributors, will be significantly reduced by opening repository files up to the public. To be clear, A DAO proposal will still be required (and need to be passed) for any PR submissions made to the DAO’s GitHub, before any pull requests are formally pushed. However, by making the front end public, will enable all community members and developers to check and comment on any PR’s made to the DAO’s GitHub, should a formal proposal be made for the DAO for a PR to be committed.

Further to this, even if a proposal is made and passed, to push a PR, in the event that a contributing developer or community member finds an issue with the pull request that puts the exchange at risk, the security shall outrank the DAO’s decision to push a PR from a contributor. This is to say, security parameters are in place and the code will be checked prior to any public PR submission being pushed.

Due to the SpiritSwap DAO’s foundation, maintaining IP rights over the front end, this proposal must be made, for the DAO to approve making the front-end repository files public before the proposed move can be made.

Benefits: Making the repository files public will allow for ease of access for community developers or other teams to contribute to SpiritSwaps code base

Risks: SpiritSwaps IP (that is the custom designs) will be accessible to the public, meaning it can be forked and used elsewhere.

PRs can be made by any members of the public which pose potential risks to the SpiritSwaps code base. This however will be mitigated by enabling the public access to review and comment on any code submissions, along with a review process by the multi-sig members (who possess developer skills), before any code is pushed live.

Actions:

Approve = Make SpiritSwaps Repos public Do nothing = Decline the proposal