(Disclaimer: Not a lawyer, but a number of my projects are licensed under MPL)
As I read it, the only time the MPL requires you to share source code is when you modify files belonging to the MPL-covered library. Even then, it only requires you to share the changes you made to the library - you don't have to share any of your proprietary or non-MPL code.
From TL;DRLegal: "You must make the source code for any of your changes available under MPL, but you can combine the MPL software with proprietary code, as long as you keep the MPL code in separate files."
So - did you install a MPL library using a package manager like npm or pip? You do not have to share your project's code.
Did you copy/paste a MPL library into a /vendor/mpl-library/ directory? You do not have to share your projects code.
Did you copy/paste functions from a MPL library directly into your source code? In this case, you may have to share the file you pasted into, but not any other files in your project.
Overall, I think the MPL strikes a great balance between the "do what you want" crowd and the "people should give back to projects that help them" crowd, which is why it's my go-to license for most libraries these days.
If I had to guess, the point is that OP enjoys learning about design systems and is trying to create a resource for other people to also learn from. Tons of knowledge already exists, but that doesn't stop people from trying to create or share new approaches to it anyway.
Nextdoor | San Francisco, CA; Toronto, ON, Canada | Full-time, Onsite | https://nextdoor.com/
Nextdoor is the world’s largest social network for the neighborhood, serving 247,000 neighborhoods across eleven countries. We recently closed a $170MM series F where Mary Meeker joined our board, and we officially launched in Canada. To support that, we're opening our first international engineering team in Toronto!
We're hiring many more roles than the above, including outside of product/engineering. Learn more about us and see if we can be the right place for you at https://about.nextdoor.com/careers/
What a flamebait title. Sure, don't hire someone just because they're a woman. Consider each candidate based on their merits. Etc, etc. But if you look at your hiring funnel and it's entirely men, something needs to change. Hard to consider the merit of women engineers if you don't have any women whose merit you can consider.
Thistle (thistle.co) | VP Engineering, Senior Software Engineer, Product Manager | San Francisco, CA | Fulltime, Onsite
Thistle is an early stage food-tech startup empowering our customers to eat better. We design high-quality plant-based food and serve it throughout California. We don’t want to be just another meal-kit company and have some key differentiators from our competitors: we put the nutritional wellness of our customers first, we make delicious meals that people actually enjoy eating, and unlike most food startups, we are both profitable and growing fast.
We are hiring experienced software engineers, product managers, and a VP of Engineering so we can scale to meet our customer demand and operational needs. Stack is Python, Django, Javascript, React, React Native. We value good engineering practices: we write maintainable code, review each others' work, use tests and static analysis tools to help catch mistakes, and have a CI pipeline to release often.
If you care about making peoples' lives better through good food or if you're interested in the challenges of delivering nutrition at scale, you'll love it at Thistle. Any questions, drop me a line: rodney 𝒶𝓉 thistle 𝒹ℴ𝓉 co
In many parts of the country, consumers don't have the luxury of choice between ISPs. Heck, I live in the Bay Area and my two options are between Comcast Xfinity and Comcast for Business. (I went for the latter because they have slightly stronger promises around my personal information.) I have to do business with Comcast because I need internet service, and I have no other reasonable source for it.
Thistle delivers delicious, organic and healthy meals as a subscription - "put your diet on autopilot". We're an early-stage, rapidly growing health & wellness startup in the Bay Area.
We're hiring software engineers (senior and junior; we're good about on-the-job training) for:
- Building our consumer website, with a focus on helping customers understand all the nutrition and health benefits in their meals.
- Kitchen/Ops infrastructure for designing, preparing and delivering thousands of meals in a day.
- Growth: Experiment with new user acquisition and engagement strategies.
I'm also a software engineer here - I actually joined Thistle after reaching out from an earlier HN Hiring thread. It works!
Our stack is Python/Django on the backend, some Javascript on the frontend, (forthcoming) app in React Native. Experience with those technologies is a plus but not required - if you're a fast learner we will be just as interested in what you like to eat for lunch.
Interview: phone screen, then visit HQ to try the food and discuss/pair program with our codebase. No brainteasers.
For the record, this is incorrect. The SEC filing does not indicate she is resigning as CEO. See other comments for explanations about what's actually going on.
As I read it, the only time the MPL requires you to share source code is when you modify files belonging to the MPL-covered library. Even then, it only requires you to share the changes you made to the library - you don't have to share any of your proprietary or non-MPL code.
From TL;DRLegal: "You must make the source code for any of your changes available under MPL, but you can combine the MPL software with proprietary code, as long as you keep the MPL code in separate files."
So - did you install a MPL library using a package manager like npm or pip? You do not have to share your project's code.
Did you copy/paste a MPL library into a /vendor/mpl-library/ directory? You do not have to share your projects code.
Did you copy/paste functions from a MPL library directly into your source code? In this case, you may have to share the file you pasted into, but not any other files in your project.
Overall, I think the MPL strikes a great balance between the "do what you want" crowd and the "people should give back to projects that help them" crowd, which is why it's my go-to license for most libraries these days.