nondiremanuel on Nostr: How I contributed in a Free Open Source Software (FOSS) in #Bitcoin as a ...
How I contributed in a Free Open Source Software (FOSS) in #Bitcoin as a non-developer (and got a Bitcoin job as a side effect):
I've recently made a user feedback collection for bitcoindevkit (npub13dk…gnvc) and I would like to share what the main purpose and results were and how it can be useful for other similar projects.
I've started being involved in BDK in April 2023 thanks to the bitcoin_product (npub1lmn…sc9n).
I wanted to understand if non-dev product people could have an impact in the Bitcoin open source ecosystem and I started contributing mostly with some basic triage and project management activity.
Even in "backend" highly-technical libraries as BDK, there is always something a non-dev can do to help, but I wanted to focus on what could give the most value given my working experience and expertise as a Product Manager in IT.
What I noticed was that in the prioritization and roadmap definition process, the (wonderful) BDK team was making a great effort in trying to understand what needed to go first and be included in the next release, but I felt that we were missing some relevant information.
As a product person, I’m used to make decision based on qualitative and quantitative data about customers or potential ones and so I proposed to apply the same reasoning to BDK.
Thanks to the BDK Foundation, I was able to get a Project Grant to dedicate myself to a proper user research process with the aim of filling such information gap, getting users' feedback and helping with the activities prioritization and roadmap definition process.
This project was very useful to understand what BDK users’ perspective was and which were the most valuable adjustments and features that we needed to implement.
The outcome of such activity was a report with some data analysis and summary of the feedback I got, which I shared and presented to the team so that we could define and assess the next steps and possible correction actions.
I feel that this was already important for the prioritization of the last activities of version 1.0 of BDK, which is now finally through the beta process and very close to be released, but I’m sure that it will be valuable in the future as a reference point as well.
Here you can find the report I presented to the team in case you are interested in having a look:
https://www.canva.com/design/DAGK7SXPYIw/k9SWMvbVOCLUte27CIXsZA/
I'm very grateful to notmandatory (npub1ke4…8jfm) for the great help in onboarding to BDK and much more.
If anyone is interested to hear more, on Thursday at 4 p.m. UTC we are going to talk about it with the Bitcoin Product Community (link: https://meet.jit.si/bitcoinproductcommunity).
I've recently made a user feedback collection for bitcoindevkit (npub13dk…gnvc) and I would like to share what the main purpose and results were and how it can be useful for other similar projects.
I've started being involved in BDK in April 2023 thanks to the bitcoin_product (npub1lmn…sc9n).
I wanted to understand if non-dev product people could have an impact in the Bitcoin open source ecosystem and I started contributing mostly with some basic triage and project management activity.
Even in "backend" highly-technical libraries as BDK, there is always something a non-dev can do to help, but I wanted to focus on what could give the most value given my working experience and expertise as a Product Manager in IT.
What I noticed was that in the prioritization and roadmap definition process, the (wonderful) BDK team was making a great effort in trying to understand what needed to go first and be included in the next release, but I felt that we were missing some relevant information.
As a product person, I’m used to make decision based on qualitative and quantitative data about customers or potential ones and so I proposed to apply the same reasoning to BDK.
Thanks to the BDK Foundation, I was able to get a Project Grant to dedicate myself to a proper user research process with the aim of filling such information gap, getting users' feedback and helping with the activities prioritization and roadmap definition process.
This project was very useful to understand what BDK users’ perspective was and which were the most valuable adjustments and features that we needed to implement.
The outcome of such activity was a report with some data analysis and summary of the feedback I got, which I shared and presented to the team so that we could define and assess the next steps and possible correction actions.
I feel that this was already important for the prioritization of the last activities of version 1.0 of BDK, which is now finally through the beta process and very close to be released, but I’m sure that it will be valuable in the future as a reference point as well.
Here you can find the report I presented to the team in case you are interested in having a look:
https://www.canva.com/design/DAGK7SXPYIw/k9SWMvbVOCLUte27CIXsZA/
I'm very grateful to notmandatory (npub1ke4…8jfm) for the great help in onboarding to BDK and much more.
If anyone is interested to hear more, on Thursday at 4 p.m. UTC we are going to talk about it with the Bitcoin Product Community (link: https://meet.jit.si/bitcoinproductcommunity).