[bisq-network/growth] Proposed existing payment method editing process and estimated timelines (#207)

[pazza]

### Proposed existing payment method editing process and estimated timelines

Part of the [Payment Method Maintainer](https://github.com/bisq-network/roles/issues/38) role is to oversee changes to existing payment methods.

The proposal is closely linked with the #206 

I have documented my proposal below for discussion / comments.

The below proposal has just been created from my current understanding of the role and is therefore, a work in progress, I welcome any feedback.



***



**0-30 days**
---
1. User requests changes to existing payment method on Bisq channel; GitHub, Twitter, Reddit, Telegram, KeyBase, Bisq Community etc  

2. User directed to create issue on [Bisq-Network>Growth>Issues](https://github.com/bisq-network/growth/issues)  using a new template to be created, or in some instances Payment Method Maintainer will create it on their behalf.

3. Issue of changes to existing payment method to be discussed by all interested stakeholders with regards to if payment method changes better meet the ‘[requirements of a payment method](https://github.com/bisq-network/bisq/issues/4757#issuecomment-727711700)'

4. Payment Method Maintainer recommends one of the following:
        
        a. Proposed payment method changes not to be implemented.
        b. Proposed payment method changes to be implemented.


**31-60 days**
---
5.	If Payment Method Maintainer recommends against the proposed changes to the existing payment method then user can submit proposal to the DAO for a vote.  

6.	If Payment Method Maintainer recommends the proposed payment method to be implemented they will @bisq-network/mediators and @bisq-network/arbitrators informing them of the intention to implement the proposed changes to the payment method along with the proposed changes of requirements; limits, aging, signing requirement, required fields, etc.
        
        a.	If no objections payment method will be prioritized for addition.

7.	If @bisq-network/mediators or @bisq-network/arbitrators have concerns these can be discussed. 
        
        a.	If rough consensus reached, payment method changes will be prioritized for addition.
        b.	If rough consensus not reached, Payment Method Maintainer, will put the issue to DAO vote.  



**61-90 days**
---

8.	If Payment Method Maintainer recommends against a payment method to be changes, or if the DAO vote against changes to a payment method, this will be documented on the payment methods roadmap.

9.	If Payment Method Maintainer recommends a payment method to be changes, or if the DAO vote for changing a payment method, the payment method changes will be prioritized for addition and added to the roadmap. The Payment Method Maintainer will then:

        a.	Package the required information to make it easy for @bisq-network/bisq-devs to make changes
        b.	Update Bisq Wiki to ensure payment method information reflects changes.


**91-150 days from payment method being added**
---
10.	Once payment method changes have been included added Payment Method Maintainer will, if required, liaise with @bisq-network/growth to promote the payment method on various channels; website, wiki, twitter, reddit, telegram, Bisq community etc.
  
11.	Once the payment method changes are live Payment Method Maintainer will assist with any snagging required during its first 6 months.

12.	Payment Method Maintainer will then report on status, KPIs, metrics of any payment methods changes. 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/growth/issues/207
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201117/07fcc81d/attachment.html>