Live data from Hacker News

Show HN: Watermelon – open-source VSC ext. to document code and view Git blame

github.com

1–10 of 43 posts

Show HN: Watermelon – open-source VSC ext. to document code and view Git blame

#1
Hey there HN! We're a pair of devs looking to get feedback for our open-source project.

We're remote engineers who have contracted for many clients overseas. There's a problem that all codebases share: Onboarding devs to a new codebase is hard no matter what.

We're also open-source engineers and learned about the techniques used in OSS to tackle the problem. Please give us your feedback.

Homepage: https://watermelon.tools/

Repo: https://github.com/watermelontools/wm-extension

Install: https://marketplace.visualstudio.com/items?itemName=Watermel...

Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
github.com

Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame

#9
Hey, congrats on the open source approach! I do have a question on your strategy though. How do you get valuable feedback from users? What incentive does your users have in order to communicate with you back and forth trying to build a better product?

Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame

#10

Hey, congrats on the open source approach! I do have a question on your strategy though. How do you get valuable feedback from users? What incentive does your users have in order to communicate with you back and forth trying to build a better product?

Ty! Open source is a very important part of our philosophy.

1. We track which GitHub usernames and repos that use Watermelon, it's the only thing we track. This allows us to go to people and ask them for more detailed feedback. We also get feedback from stargazers and forkers. Because we're open source, people also leave GH issues.

2. The incentive is something very basic: They wanna see a better version of this out there in the world.

Post reply on HN