robmensching

5 ms·

31.
by robmensching 1y ago
Yep, and now you have about half a million lines of code* to maintain as well. Have fun with it!* * Last count the WiX Toolset had 589,719 loc but 444,936 if you skip comments and whitespace. * This is the point, maintaining successful (and
32.
by robmensching 1y ago
You can pay annually. GitHub Sponsors allows that.
33.
by robmensching 1y ago
Yes! Exactly. You're not alone with this sentiment. :)
34.
by robmensching 1y ago
There are models out there like this. Look around the term "Fair Source" and I think you'll find them.
35.
by robmensching 1y ago
This right here is the bottom line. The OSMF's goal is to keep the software FOSS and the maintainers involved.
36.
by robmensching 1y ago
It sounds like you maintain a successful Open Source project. :)
37.
by robmensching 1y ago
> I guess they're banking on their users preferring to get the binaries straight from the source instead of through an unaffiliated third party. Yep. It turns out a lot of companies are willing to pay for maintenance but they aren&#
38.
by robmensching 1y ago
Note that the package.lock file is not the place to look for your OSMF dependencies. That file will list your project's dependencies and all of their dependencies and so on and so on. You want to look at the list of packages in your pa
39.
by robmensching 1y ago
> I'll give the benefit of the doubt and assume this is just a difficult concept to succinctly explain in a short paragraph. It is challenging to describe the concept succinctly, especially as there are lots of varied expectations p
40.
by robmensching 1y ago
> Its only appeal was that it was free. That was definitely its appeal to people who didn't want to pay anything for setup installation tools. But that definitely wasn't our only appeal or even our primary appeal. The WiX Tools
41.
by robmensching 1y ago
I mentioned this in another response: > Our primary goal with the WiX Toolset was to provide access to the full power of the Windows Installer. Given the adoption by extremely large software projects, I think we've done pretty well
42.
by robmensching 1y ago
> IIRC it was a project under the Office organization originally. I worked in Office in 1999 when I created WiX but it definitely was not an "Office project". It wasn't until I left Office for project in Windows Server tha
43.
by robmensching 1y ago
My experience is that FOSS is being destroyed by entitled consumers. Note: I'm not saying you're an entitled consumer, but I interviewed many maintainers of successful Open Source projects. The number one issue for all of them was
44.
by robmensching 1y ago
Creating a private distribution point and private issue tracker definitely would be an option, and it would make enforcement much easier. But I believe it would also make us more distant from the community. I really wanted to create a syste
45.
by robmensching 1y ago
If the OSMF takes off, I could definitely see something like this taking off.
46.
by robmensching 1y ago
I disagree. The EULA is an extremely elegant solution to activate an organization's legal team to help their procurement team sponsor Open Source projects.
47.
by robmensching 1y ago
Yeah, the build system integration was always one of the core benefits provided by the WiX Toolset. I know you're not working with MSI any longer, but in recent versions of WiX Toolset we _finally_ nailed down how to include files in t
48.
by robmensching 1y ago
Honestly, thus far it's been a relative breeze. I expected the need to work out "bugs" as the idea is new. My hope is that after we address the bulk of the issues that actual consumers have raised about the OSMF, it'll b
49.
by robmensching 1y ago
Heh, funny. My goal was to funnel questions and comments into a single location: the Discussion forum.
50.
by robmensching 1y ago
Oh, snap! That's bad. It's fixed (thanks to a random contributor :)
51.
by robmensching 1y ago
No. Not really. There are 406 forks, and ~10 were created in the last 5 months. The other people on this thread are more correct.
52.
by robmensching 1y ago
Yes! There are many Open Source projects my company depends on (like Astro, Vue, and Vite for our web sites) that I would love to pay a Maintenance Fee to encourage the maintainers to keep on keeping on. For all Open Source projects that we
53.
by robmensching 1y ago
100%. We're still learning here. I also don't expect every project to choose the same policy on how they tackle issues/PRs when requiring an Open Source Maintenance Fee.
54.
by robmensching 1y ago
The window was definitely smaller than I would consider ideal. But the OSMF only applied to WiX v6 (released in April) and later. So, all the older versions would not be impacted. Also, the timing was never raised as an issue by anyone in t
55.
by robmensching 1y ago
Absolutely true, but that isn't what happened (at least, not yet). Most companies found the fee reasonable and worth it to have us maintain the project and not have to fork it.
56.
by robmensching 1y ago
No. A maintainer is someone who maintains the project. Fixing a bug is a great contribution and makes you a contributor to the project. But you need stick around the project for a while, fixing issues that keep the project running and doing
57.
by robmensching 1y ago
We're still working through the best way to talk about issues and PRs. This is an area where I expect maintainers to differ in how they apply the OSMF (every maintainer I've spoken to is 100% behind requiring payment for binaries)
58.
by robmensching 1y ago
> It looks a bit similar to the RedHat model Yes, very good recognition. The Open Source Maintenance Fee follows several of the paths RedHat paved long ago. > This may give CTOs an easy way to expense such support I'm finding it
59.
by robmensching 1y ago
> As an open source project no one is forcing you to maintain it. Absolutely true. For maintainers willing to abandon their project because they tire of maintaining it, this is a totally viable alternative. Just ignore everything you don
60.
by robmensching 1y ago
> This can make it harder to recruit further contributors as there is a two-clays system of contributors. We'll see. I haven't seen any reduction in contributions (not that the project gets lots of contributions because we&#x27

More ›