-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@leo816 to assume Support Team Lead role #230
Comments
The duties you have added are completely logical and necessary. |
I'm glad to see that this role will be in good hands. It's probably not urgent now, but at some point we should start planning for multi-language support. It should factor into recruitment and internship proposals. |
This proposal has now been up for nearly a week (and has been discussed for much longer than that). There have been only 👍's in response, and there have been no other contributors stepping forward as interested in the role. I will therefore close this as approved once the following tasks are complete:
|
Closing as approved. |
I would like to formally apply for this role,
My current roles include:
I have been involved with bisq for over 2 years now. I started making bisq's first ever tutorial video (https://www.youtube.com/watch?v=-o9CKiivyIc&t=1s) and then having a series of critical roles inside the support team that have made me very aware of how each one works.
I am very passionate about this project and think I have gained enough knowledge through these years that make me an adequate candidate.
I have added two more duties on the https://bisq.wiki/Support_Team_Lead that I think are inherent to the role, and that I happen to have done to some extent already:
Review Team's Compensation requests as per Process.
Manage new internship proposals and evaluate their performance once the period is over.
Review and supervise the "on duty" schedule.
I'd like to hear if anyone, specially the @bisq-network/support have any suggestions or comments about which direction should the role develop into going forward.
The text was updated successfully, but these errors were encountered: