i would say it should be the engineer who was owning the initial issue, and then reviewed/ merged the PR to own the code. it should be them on gitblame anyways as a co-author once a gitstart PR is merged
i would think gitstart as an extension to engineers themselves instead of working in silo
afaik gitstart pays above market in the local economies, but there’s always room to improve of course. however it’s hard to pay everyone the market rate of american companies.
the developers are typically folks who wouldn’t be able to get a remote job otherwise due to universities not being globally recognized or english is not super fluent. many developers grow a lot during their time at gitstart and eventually move on to getting jobs at places like Google, Amazon too. they support any developer to grow (there’s a team dedicated to figure out growth paths for each developer on the platform)
Imo the typical “women in tech” issues only really applies to US (and maybe some other typical western countries). It’s really different elsewhere, case in point in Afghanistan.
Hope that the small things we’re doing at GitStart can break down the barriers of language, merit, class, culture, and political situation and let anyone who wants to learn coding can learn, and those who want to make money from it can!
Thanks! Huge fan of Pragmatic Engineer's blog post. There are plenty of paid mentorship programs listed, which is totally different from what we are looking for as we're trying to build a mentorship program that's free for our developers (and ofc we will pay the mentors). But paid mentorship with exclusivity is not reaaally what we're looking for as they're structured very differently.
The free ones seems cool, gonna check them out and probably reach out to folks there.
We're launching a mentorship program for our developers at GitStart with mentors from outside our community.
If you have experience building such programs, know excellent mentoring platforms, or would like to be a mentor yourself, I’d love to hear from you at: [email protected] or reply below
thanks for sharing thanks.dev! This looks really cool. This is something I've been looking for.
It seems more like for a one time donation, right? Imo it would work better in a subscription model / base on real production time usage rather than just dependency tree. But this is a great start for sure.
It could be a new badge for companies, like how buildings get those sustainability badges, but for companies who pay for OSS!
This is one of the biggest problems in OSS imo. I don't think codeberg built this with the sponsorship as the first thing in mind, which means I only see codeberg's own org and own projects asking for funding / maintenance help.
To truly fix open source we need a platform that makes maintaining (and potentially merging similar projects) a breeze. And make sponsorship simple, and make it work. Otherwise new projects will keep popping up on new platforms, and go stale instantly once the maintainer runs out of the passion fuel.
Please ask for Github Sponsors! However, I do see how broken the financial ecosystem is for open source folks. There are some things that I think open source needs:
- discoverability of open source projects that need funding
- the actual runtime usage of different open source projects
- priority to fix open source bugs with bounty
i've been wanting to know more about my hormones and how it affects me for years! and my goal for 2019 is to understand more about female hormones and find solutions to make our lives easier.
are you also having similar questions/ problems? please check out my website & subscribe to the mailing list and stay tuned xx
i would think gitstart as an extension to engineers themselves instead of working in silo
disclaimer: i used to work at gitstart