Hacker News new | past | comments | ask | show | jobs | submit | armini's comments login

Absolutely, There’s hope in initiatives like https://osspledge.com/ & https://thanks.dev

Also https://polar.sh/, which lets users of the project "vote with their wallets" on which issues should be prioritized. You can see it in action in Starlette's GitHub issues, e.g. https://github.com/encode/starlette/issues/649

I can't tell you how many developers feel this way, there is no reason for this to be the norm. Be sure to seek professional help but if you'd like someone to talk to someone who can relate feel free to book a time https://calendly.com/thanks_dev/30min


Is this a calendly link to you?


It says he used the money from redundancy to continue with his work. Pfizer would have a hard time winning that case because the discovery was made past their employment. Having field knowledge doesn't make it a crime. Coding is different because it's easier to copy paste functions & classes, it also doesn't help that everything has timestamps. Your best bet is to rewrite everything.


Maybe it's semantics, but I understand it was discovered while at Pfizer and further developed post-redundancy. IANAL but it definitely feels like a grey area?


It's not a grey area at all. The article literally says that he purchased the IP rights from Pfizer, and as part of the deal they got a small stake in his new company.


Hi HN Community,

Microsoft recently announced they have generated 2Billion in ARR from Github Copilot. As part of corporate social responsibility, do you think Microsoft should give back to the open source community given that Copilot is technically trained by OSS maintainers??


Yes it’s a start & it helps optimize queries by suggesting alternatives


If you like using psql, you might want to try out https://pxlapp.com/home


It's great that this is getting coverage but I'd love to see more solid tangible actions. I think simple & solid commitment frameworks like https://osspledge.com/ will do more in terms of helping to recognise & reward the eco-system.


Thanks for sharing this, happy to answer any questions.


The team at frontend masters are doing that well https://frontendmasters.com/blog/how-were-supporting-open-so...


Thats still contributing to the maintainers of projects, not to the people writing pull requests etc.


I personally like Sentry's approach more, their program focused on supporting the breadth and depth of their dependency tree rather than just the critical components https://blog.sentry.io/we-just-gave-500-000-dollars-to-open-... Disclaimer: I work for thanks.dev


I got a DM from a maintainer asking to elaborate so here's my personal opinion "The Geomys model feels a lot like the Tidelift model but it doesn't really create an eco-system that's more inclusive & exciting to be a part of. We want to create a community where more maintainers are excited by contributing to open source instead of them saying ohh this is too hard lets pass it onto someone else with the resource. The other issue is that how do you determine if something is critical & if something isn't, it's really subjective."


Did I misread something? I don't think Geomys is in the business of deciding what is or isn't critical.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: