News for hackers. Stuff that matters.
Re:It's time to let go, Apache Software Foundation by zoogeny on Monday September 25, 2023 @11:50AM (#37645854)
I've felt for a long time (maybe even a decade) that Apache is the place OSS goes to retire/die. It is heartbreaking in some ways, they became the stewards for a lot of interesting projects [1]. And the venerable web server was so important to the early web. I am still running Apache vhosts on a few personal websites.

It is also a totally unfair characterization. I mean, they still house relevant projects including Kafka, Lucene, Zookeeper, Spark, Arrow and many others.

But it does feel Apache lives in a kind of stasis, a relic of the "old" web, like geocities sites or MySpace. If a project ends up in Apache it feels to me like it has gone out to pasture.

1. https://projects.apache.org/projects.html

Re:It's time to let go, Apache Software Foundation by brand on Monday September 25, 2023 @12:02PM (#37646070)
It seems that “younger generation” programmers underestimate the value of governance in OSS. The recent Terraform kerluffle couldn’t have happened if Terraform was in the ASF, etc.
Re:It's time to let go, Apache Software Foundation by debacle on Monday September 25, 2023 @12:31PM (#37646552)
Terraform wouldn't be in the ASF unless it was dead, is the point.
Re:It's time to let go, Apache Software Foundation by KptMarchewa on Monday September 25, 2023 @12:37PM (#37646636)
There is giant amount of actively worked upon, very heavily used software projects in Apache: Airflow, Spark, Flink, Kafka, Lucene and a lot of foundations on which those are written or use: Parquet, Arrow, Iceberg.
Re:It's time to let go, Apache Software Foundation by jacoblambda on Monday September 25, 2023 @01:12PM (#37647266)
But are they web scale? (/s if that isn't clear)
Re:It's time to let go, Apache Software Foundation by addicted on Monday September 25, 2023 @01:12PM (#37647270)
Maybe the real problem is that the ASF has been adopting too many abandoned projects that have been “donated” by much bigger entities (e.g. Google donating Wave).

This is the right thing to do from a helping the world perspective, but it’s clearly hurt ASF’s reputation.

They should simply start saying no to some of these dead/dying projects. Or at the very least brand them differently.

Re:It's time to let go, Apache Software Foundation by rbowen on Monday September 25, 2023 @01:41PM (#37647718)
It's important to note that the ASF did say no to Wave. It never made it out of the Incubator, because it was unable to build an active user community.
Re:It's time to let go, Apache Software Foundation by mindcrime on Monday September 25, 2023 @02:47PM (#37648684)
And in addition, simply by virtue of going through the Incubator at all, these projects ensure that the source code is available under a well known, well understood, popular, ALv2 license - and the code, email archives, and other artifacts that were created are preserved by the ASF even when the project is sent to the Attic. This is still a net good for the world in general, IMO.

And while it's not exactly common there have been forks of Attic'd projects outside of the ASF that went on to be useful to people.

Re:It's time to let go, Apache Software Foundation by zoogeny on Monday September 25, 2023 @12:28PM (#37646491)
There is a quote: "When you stop growing you start dying" (William S. Burroughs). I am not sure I believe that the kind of governance that Apache is providing is helping to grow the projects under its supervision.

Your comparison to Terraform is also interesting. Apache Kafka, for example, has been absorbed by Amazon (MSK). Apache Spark is Amazon EMR. Just looking through Amazon's paid service offering I find several Apache projects rebranded and for sale. A cynical take could be that Apache is an org that helps companies like Amazon profit off of the work of open source developers.

Re:It's time to let go, Apache Software Foundation by JohnFen on Monday September 25, 2023 @12:38PM (#37646649)
But with software, sometimes there comes a time when it really should stop growing. When any further "enhancements" make the software worse.

It's something I've seen countless times in my life. A piece of software achieves something pretty close to perfection for its task, but the self-imposed "need" to continue development on it ruins it.

Re:It's time to let go, Apache Software Foundation by rzzzt on Monday September 25, 2023 @01:05PM (#37647147)
Does it read mail and/or contain a subset of Common Lisp?
Re:It's time to let go, Apache Software Foundation by worthless-trash on Tuesday September 26, 2023 @12:26AM (#37654356)
All software will eventually grow to send email. And lets be honest, if its not written in lisp, are you really trying ?
Re:It's time to let go, Apache Software Foundation by systems_glitch on Monday September 25, 2023 @01:12PM (#37647271)
Absolutely. Some things go into bugfix-only mode because their code has reached perfection for the 99% use case.
Re:It's time to let go, Apache Software Foundation by broeng on Monday September 25, 2023 @02:01PM (#37648011)
And then we fear it's a dead project, and move on in search for something else with active contributors.
Re:It's time to let go, Apache Software Foundation by JohnFen on Monday September 25, 2023 @02:03PM (#37648034)
Certainly not everyone. Personally, I pay little attention to that sort of thing at all. I don't care if it's a "dead" project or not -- as long as the software is meeting my needs, that's the only thing that matters. If/when it stops doing that, then I'll look for alternatives.
Re:It's time to let go, Apache Software Foundation by systems_glitch on Tuesday September 26, 2023 @01:34PM (#37662854)
Same here. I run Slackware on all of my engineering and development workstations. It does what I want, nothing gets hosed when running updates, and I don't feel like my main job is sysadmin.

But I keep getting told I need a "Slackware intervention" :P

Re:It's time to let go, Apache Software Foundation by AlbertCory on Monday September 25, 2023 @02:37PM (#37648538)
Hot take: Python 3.

Totally unnecessary.

Re:It's time to let go, Apache Software Foundation by Master_Odin on Monday September 25, 2023 @03:32PM (#37649321)
The move to python 3 helped shake loose a number of text processing bugs with library I work on, that was never caught in python 2 with its loose goosy text type handling.
Re:It's time to let go, Apache Software Foundation by JohnFen on Monday September 25, 2023 @04:38PM (#37650297)
But as an end user, it's made using applications based on (or even tangentially using, as I learned first-hand a couple of months ago) Python highly problematic due to extreme version incompatibility.

I now try my best to avoid anything that involves Python.

Re:It's time to let go, Apache Software Foundation by janoc on Monday September 25, 2023 @05:19PM (#37650806)
Sorry but that's nonsense. Python 3 has been released in 2008 - 15 years ago. And the last Python 2 version has been EOLed 1.1.2020, three years ago, after a decade of deprecation!

With your argument about compatibility no programming language would ever be able to evolve or deprecate/remove some features. Look at how many things changed e.g. between recent C++, Rust or C# major releases. Python had only one major revision in 15 years in comparison!

If you are using software that still requires Python 2 that's very much a problem of that application and not Python. Complain to the vendor responsible, not about Python. They had ample time to update their code.

End users had no business touching Python 2 for at least a decade now. And upward compatibility between the point releases of Python is (and has been) generally pretty good.

Re:It's time to let go, Apache Software Foundation by AlbertCory on Monday September 25, 2023 @05:46PM (#37651154)
all arguably true, but it has no bearing on whether 3 was necessary in the first place.

> With your argument about compatibility no programming language would ever be able to evolve

"evolve" and "change" are not ends in themselves. If it was usable as it was, then there was no need to evolve or change in an incompatible way.

15 years ago: also irrelevant. World War One was unnecessary, and that was 109 years ago. Whatever issues existed are sorted out by now, but that doesn't mean it had to happen.

Re:It's time to let go, Apache Software Foundation by janoc on Monday September 25, 2023 @06:02PM (#37651340)
There have been some very good reasons why Python 3 made those changes.

That you find them unnecessary because the original code was "usable as is" for you is irrelevant.

The reasons why these changes have been done (for a developer they have been fairly minor) has been hashed and rehashed for the past 15 years, Guido van Rossum wrote on it extensively too.

Most has been performance-related (Python 3 is significantly faster than 2) and probably the biggest user-visible change is the clean up of string handling with everything being Unicode now.

Frankly, anyone complaining about this stuff today is just beating the old dead horse for the sake of having something to complain about. The same like some people constantly bringing up the Linux systemd discussions after more than a decade, even though they are completely irrelevant today.

Re:It's time to let go, Apache Software Foundation by AlbertCory on Monday September 25, 2023 @08:19PM (#37652635)
the age of an unnecessary change is irrelevant. Here's your sequence:

1. It's not true

2. It's true, but it's not important

3. It's true, and it's important, but we're tired of talking about it.

Re:It's time to let go, Apache Software Foundation by JohnFen on Monday September 25, 2023 @05:49PM (#37651195)
> Sorry but that's nonsense.

I'm not lying. This problem cost me a full weekend earlier this year. I may have misremembered the exact version numbers, though. Perhaps it wasn't between 2 and 3. Is there a Python 4?

The problem is that you can't have one Python interpreter that covers all versions of Python, and Python is very unforgiving about using the wrong interpreter version.

In any case, it was a serious problem that cost me a lot of time and really soured me on Python as an end user. I've not encountered a similar issue with any other language before, so this appears to be uniquely a Python thing.

But I don't know. I'm happy enough to just avoid Python-based anything whenever possible now.

Re:It's time to let go, Apache Software Foundation by janoc on Monday September 25, 2023 @06:11PM (#37651421)
There is no Python 4 - and may not ever be.

If you have downloaded Python 2, you must have done it intentionally, it isn't even available from the Python.org website download anymore - and had not been for a long time.

>The problem is that you can't have one Python interpreter that covers all versions of Python, and Python is very unforgiving about using the wrong interpreter version.

Because it doesn't make sense. The language evolves. Nobody is going to stop working on it only because it could break some old code somewhere. The changes from 2 to 3 happened *15 years ago*.

There is no reason to try to compile/run old Python 2 code today - and if you still do need it for some reason, then you need to download the Python 2 version (which are still available, if you need them but one has to look for them). But then you better know what you are doing.

If some old code requires Python 2, any somewhat experienced Python developer will spot that right away (e.g. the use of print statement in Python 2 vs. print() function in Python 3 is a dead giveaway).

>In any case, it was a serious problem that cost me a lot of time and really soured me on Python as an end user. I've not encountered a similar issue with any other language before, so this appears to be uniquely a Python thing.

I don't doubt it has costed you a lot of time but this was a problem entirely of your own doing by not doing your homework.

You would have exactly the same problems if you tried to compile old K&R C code or C++ code from 20 years ago using modern compilers. Or tried to feed modern C# code to a compiler from 10 years ago. Or, God forbid, tried to run some modern Javascript code using old browser - or that old HTML with Flash and what not in a modern browser ...

Python is actually much more lenient in this regard because a major language change has happened only once, 15 years ago, with Python 2 being deprecated for well over a decade. The point releases are all upward compatible with no issues.

Re:It's time to let go, Apache Software Foundation by jen20 on Monday September 25, 2023 @10:13PM (#37653468)
I’m with you on Python 2 to 3 being a fine idea and an improvement but…

> You would have exactly the same problems if you tried to compile old K&R C code or C++ code from 20 years ago using modern compilers. Or tried to feed modern C# code to a compiler from 10 years ago.

If you feed 10 year old C# to a modern compiler it will compile it fine. I’d imagine most C and C++ of even 20-year vintage will still compile. The issue is of forward compatibility, not backwards.

Re:It's time to let go, Apache Software Foundation by pjmlp on Tuesday September 26, 2023 @05:13AM (#37656514)
No it won't, as it might be using the breaking for change introduced in C# 5, or .NET Framework features not made available on .NET Core.

Likewise C and C++ have had enough breaking changes since 2010.

Re:It's time to let go, Apache Software Foundation by neonsunset on Tuesday September 26, 2023 @09:43AM (#37659200)
It depends. Some projects can be retargeted to netstandard2.0/net6(8).0 without any changes at all, some require minor update of dependencies and some other - do face breaking changes in library code because APIs did get deprecated.

With that said, neither IL nor C# itself had any changes breaking forward compatibility (aside from a very early change to foreach recently discussed here).

Re:It's time to let go, Apache Software Foundation by pjmlp on Tuesday September 26, 2023 @11:13AM (#37660559)
C# isn't used in isolation without standard library.

Also, "it depends" isn't the same as "If you feed 10 year old C# to a modern compiler it will compile it fine."

Re:It's time to let go, Apache Software Foundation by augustk on Monday September 25, 2023 @12:59PM (#37647033)
Why do you think software needs to grow?
Re:It's time to let go, Apache Software Foundation by kuchenbecker on Monday September 25, 2023 @01:12PM (#37647274)
It needs at least a stable set of users, but maintaining a set of users is essentially managing the set of people onboarding and the set of people migrating off.

If you're shrinking then a competitor is providing better options, or your problem space has shifted.

Re:It's time to let go, Apache Software Foundation by dale_glass on Monday September 25, 2023 @06:15PM (#37651458)
Software as big as Open Office may not need to technically grow, but still needs a lot of work to stay current.

Various dependencies, like XML parsers, JPEG decoders, HTTP libraries, etc, change over time, drop deprecated APIs and need the main application to adapt. It'll also bump into the tech changing around it -- UTF8, year 2038, 64 bit CPUs, etc.

For a project this size it takes work just to stand still and keep it comfortably buildable on a modern Linux distro.

Re:It's time to let go, Apache Software Foundation by znpy on Monday September 25, 2023 @01:31PM (#37647561)
> "When you stop growing you start dying"

death is part of life though, and the only thing that grows without and end is cancer (quite literally).

I don't see why project can't just be considered "done": yeah you update dependencies and make it work with new/current formats, but essentially it's done. The use case is now clearly defined, implemented and tested.

Re:It's time to let go, Apache Software Foundation by rbowen on Monday September 25, 2023 @01:40PM (#37647699)
I'm fascinated at your characterization of both Kafka and Spark as being absorbed by Amazon.

AWS offers hosted versions of each. They are not, as you say "rebranded and for sale", but rather are hosted services, running whatever upstream releases.

But to say that the project as been absorbed by AWS (in either case) is simply false. Spark is developed by a community of numerous companies, of which Databricks is usually most prominent. Kafka is likewise a community of several organizations, of which Confluent tends to be the most influential.

Yes, Apache is (and always has been) business-friendly. The license enables companies to profit on those projects. But, for the most part, companies that benefit from those project also contribute back to them, as a way to ensure sustainability. That's how it is supposed to work.

Re:It's time to let go, Apache Software Foundation by toast0 on Monday September 25, 2023 @01:46PM (#37647788)
> A cynical take could be that Apache is an org that helps companies like Amazon profit off of the work of open source developers.

Apache httpd certainly helped tons of companies profit, so helping companies profit doesn't seem off-brand.

Re:It's time to let go, Apache Software Foundation by softwaredoug on Monday September 25, 2023 @12:56PM (#37646968)
Agreed... We are seeing dozens of database companies turn their OSS into basically proprietary shared code licenses. And we seem to still pretend its "open source"

Collaboration, across companies, not ownership by one company is the root of open source. To do that you need some kind of governance model. Essentially "ownership" by one company is conducive to quick progress on specific problems, but not collaboration.

Re:It's time to let go, Apache Software Foundation by AceJohnny2 on Monday September 25, 2023 @01:29PM (#37647532)
To put it another way: many startups today have adopted the "Open Core" business model, and it's really more about marketing than actual open-source.

"Open Core" means they open-source the core of their product portfolio, core which some enterprising people may use to develop applications on, but for others will really need the buy into the rest of the portfolio to get the best use out of.

Re:It's time to let go, Apache Software Foundation by AceJohnny2 on Monday September 25, 2023 @01:30PM (#37647541)
I can't really fault companies for using this model. Development is expensive, and business models around open-source are hard. I mean, just look at what Red Hat ends up doing to fend off copycats. Getting people to try your product and also rely on it is a tricky proposition.
Re:It's time to let go, Apache Software Foundation by softwaredoug on Monday September 25, 2023 @03:20PM (#37649146)
I don't fault them either. In fact I'm a big fan of many of those companies.

I think the fault is with the consumers. Many companies consume but do not participate in open source. All the incentives are there for companies to become vendors rather than participants (stewards?) of an open source project.

Re:It's time to let go, Apache Software Foundation by soenkeliebau on Monday September 25, 2023 @03:58PM (#37649712)
I think we are heading towards a bit of a shift in this regard. With the CRA in Europe and similar legislation in the States it will become more important to have "enterprise" services surrounding open source software. This is for example support, but also vulnerability assessment and similar things.

I may be mistaken here, but I think we will see pure functionality become less important to enterprise customers, which might (maybe not, but one can hope) proper open source business models more viable again.

Re:It's time to let go, Apache Software Foundation by falalalala on Monday September 25, 2023 @06:52PM (#37651852)
What does Debian do?
Re:It's time to let go, Apache Software Foundation by AceJohnny2 on Monday September 25, 2023 @06:53PM (#37651867)
Debian is not a commercial entity. It's a volunteer organization.

In fact there's been quite a bit of vitriol about Canonical profiting from all the hard work from Debian volunteers and not shared as much of that value back to Debian as was felt was deserved.

Re:It's time to let go, Apache Software Foundation by worthless-trash on Tuesday September 26, 2023 @12:24AM (#37654344)
I've always wondered about that, I feel like ubuntu sometimes doesn't contribute fixes upstream. When I hear 'it works on ubuntu but not on distro X', it makes me wonder why ubuntu devs didnt post the fixes upstream.

* I do realise that different release timings can fudge with the timing, but when fedora is building upstream versions and I hear it, its a bit.. disheartening.

Re:It's time to let go, Apache Software Foundation by pxc on Tuesday September 26, 2023 @03:43PM (#37664845)
> When I hear 'it works on ubuntu but not on distro X', it makes me wonder why ubuntu devs didnt post the fixes upstream.

I think this usually doesn't really have to do with Canonical at all, but with third party developers only testing against and building for Ubuntu.

Re:It's time to let go, Apache Software Foundation by worthless-trash on Tuesday September 26, 2023 @11:45PM (#37669784)
Possibly, the examples I chased down are usually patches to the gnome userspace stack.
Re:It's time to let go, Apache Software Foundation by pclmulqdq on Monday September 25, 2023 @01:22PM (#37647424)
The flipside is that companies don't seem all that interested in this sort of collaboration, though, nor should they be. It doesn't really make sense for a company that believes its edge is its technology to both give up the secret sauce and accept the dillution of that edge that comes from taking code from outside contributors. The modern version of "open source" is a natural evolution of the concept when this is how companies think.
Re:It's time to let go, Apache Software Foundation by znpy on Monday September 25, 2023 @01:27PM (#37647504)
> We are seeing dozens of database companies turn their OSS into basically proprietary shared code licenses. And we seem to still pretend its "open source"

"open source" here is working as intended. the thing is, "open source" is misunderstood by many (most?) individuals.

"open source" was explicitly created by Eric Raymond and others in the late 90ies because the Free Software movement was seen as too extremistic by companies still deeply rooted into the proprietary model.

"open source" is a nice way out, in order to be able to look cool, while not actually playing it cool.

I said it in many posts and i'll say it again: if you're require to give up copyright on your contributions and the license isn't free-software... then it's just a matter of time before a company turns your code into proprietary intellectual property.

people that do not agree are simply delusional (or okay with that).

Re:It's time to let go, Apache Software Foundation by ptx on Monday September 25, 2023 @01:47PM (#37647790)
Well, sort of. Open source was just a different name to describe free software, with the purpose of emphasizing the collaboration benefits this gives the business rather than the freedom it gives users. But this "business source" stuff is a different thing which is not open source at all.
Re:It's time to let go, Apache Software Foundation by mixmastamyk on Monday September 25, 2023 @02:06PM (#37648091)
Not just different names but different licenses.
Re:It's time to let go, Apache Software Foundation by ptx on Monday September 25, 2023 @02:37PM (#37648543)
No, not really. The first three criteria of the Open Source Definition [0] are essentially freedoms 1–3 of the Free Software Definition [1] and freedom 0 more or less maps to criteria 5 and 6.

The mainstream FOSS licenses (GPL, BSD, Apache2, etc.) are all included both in the official list of open source licenses [2] and the official list of free software licenses [3], so these licenses are both open source licenses and free software licenses. These lists might have some minor differences, but they share a substantial subset and the definitions broadly speaking define the same thing.

[0] https://opensource.org/osd/

[1] https://www.gnu.org/philosophy/free-sw.html

[2] https://opensource.org/licenses/

[3] https://www.gnu.org/licenses/license-list.en.html

Re:It's time to let go, Apache Software Foundation by toyg on Monday September 25, 2023 @04:06PM (#37649832)
You can't interpret things like these out of context.

OSS as a term was created at a time when free software, as defined by GNU, was effectively becoming the de-facto standard for collaborative efforts on the internet. Yes, MIT and BSD were around (barely, in the BSD case), but the rising star was Linux and Linux (and the software built on it - GTK, gimp, etc) was GPL.

The industry needed a way to get on the action without touching the "communist" GPL, and that's why ESR's definition of "Open Source" was endorsed. Obviously they coopted all the existing bits they were ok with (i.e. all the ones that did not impose any extra burden on companies), that's why the definitions overlap substantially; but they are not the same thing. If they were, there would not have been any need to create a new definition for it.

Re:It's time to let go, Apache Software Foundation by znpy on Monday September 25, 2023 @05:41PM (#37651094)
> The industry needed a way to get on the action without touching the "communist" GPL, and that's why ESR's definition of "Open Source" was endorsed.

which against, doesn't really makes sense.

Stallman has repeated over and over that the Free Software movement is not about communism (despite what communist people like to say).

Most likely, the industry needed a way to get people to submit improvements and patches (essentially doing Development, QA and support) for free without having to give a way the right to sell proprietary services.

Re:It's time to let go, Apache Software Foundation by ptx on Monday September 25, 2023 @06:44PM (#37651762)
Out of context? I provided plenty of context if you care to follow the links I posted.

The distinction between copyleft and non-copyleft licenses, e.g. GPL and BSD, is different from the distinction between open source and free software, which is mainly ideological. The GPL is a copyleft license but also an open source license, as you can see on the OSI website.

For maximum context, here is a quote from the board meeting minutes [0] where the OSI approved the Free Software Foundation's copyleft GPL license as an open source license in accordance with the Open Source Definition: "The Open Source Initiative is pleased to announce that, based on broad review and acceptance by both the Board and the community, it has confirmed that GPLv3 and LGPLv3 both conform to the Open Source Definition."

[0] https://opensource.org/meeting-minutes/minutes20070905/

Re:It's time to let go, Apache Software Foundation by toyg on Tuesday September 26, 2023 @03:18AM (#37655621)
Yes, because OSS was meant to be a superset of projects including Free Software, so that stuff that did not fit the Free Software definition could still be considered ideologically acceptable. Do I really have to draw a diagram...?
Re:It's time to let go, Apache Software Foundation by ptx on Tuesday September 26, 2023 @07:35AM (#37657770)
Such as what stuff? Draw a diagram if you need to, but a few examples of these nefarious non-free licenses promoted by the OSI would be sufficient.
Re:It's time to let go, Apache Software Foundation by toyg on Tuesday September 26, 2023 @09:18AM (#37658867)
Crap like Sun's CDDL and MPL were endorsed by OSI although they were developed explicitly in opposition to the GPL. Yeah, they might be nominally "free", but their aim was fairly nefarious at the time. OSI endorses all sorts of licenses that are free in name only.
Re:It's time to let go, Apache Software Foundation by ptx on Tuesday September 26, 2023 @09:47AM (#37659242)
OK, so you're saying that Open Source is "not the same thing" as Free Software and there was a "need to create a new definition for it" to include "stuff that did not fit the Free Software definition". You give the CDDL and the MPL as examples of such stuff.

But if you take a look at the Free Software Foundation's list [0] of Free Software licenses, you will see that it lists both the CDDL and the MPL as Free Software according to the Free Software Definition.

So why should a new definition have been needed to allow these licenses when they are already allowed by the old definition? Maybe you could supply some of that context you were talking about?

[0] https://www.gnu.org/licenses/license-list.en.html

Re:It's time to let go, Apache Software Foundation by toyg on Tuesday September 26, 2023 @10:14AM (#37659658)
CDDL and MPL were defined as "free" only after a lengthy debate, and remain incompatible with the GPL - which, at the time, was widely considered the gold standard of free licenses. Without OSI as an ideological cover, they would have been ostracized even harder than they were.

> So why should a new definition have been needed to allow these licenses when they are already allowed by the old definition?

Maybe you should ask the founders of OSI? If their work was fundamentally pointless, why did they do it? Because it wasn't pointless, it was seen as necessary to be able to say "we are Good Guys, but not like them dirty GPL hippies".

Re:It's time to let go, Apache Software Foundation by znpy on Monday September 25, 2023 @03:17PM (#37649095)
In this contexts license is everything, I can’t understand why people won’t get this in their head.
Re:It's time to let go, Apache Software Foundation by znpy on Monday September 25, 2023 @03:15PM (#37649070)
What you’re saying doesn’t make sense at all.

If that was true that would have been just some marketing campaign.

There would have been no need to divert the attention from the free software foundation.

Re:It's time to let go, Apache Software Foundation by ptx on Monday September 25, 2023 @03:58PM (#37649704)
Yes, basically a marketing campaign. Wikipedia [0] says (in part): "Netscape's act prompted Raymond and others to look into how to bring free software principles and benefits to the commercial-software industry. They concluded that FSF's social activism was not appealing to companies like Netscape, and looked for a way to rebrand the free software movement to emphasize the business potential of the sharing of source code."

In other words, we had a thing that would benefit everyone in many ways, but some people didn't like the marketing message of "users deserve these rights!" so a complementary marketing message of "cheaper and higher-quality software through collaboration!" was needed to reach that group.

[0] https://en.wikipedia.org/wiki/History_of_free_and_open-sourc...

Re:It's time to let go, Apache Software Foundation by morelisp on Monday September 25, 2023 @01:27PM (#37647499)
More like the ASF lost any claim to inherently support good governance with OOo.
Re:It's time to let go, Apache Software Foundation by mixmastamyk on Monday September 25, 2023 @02:08PM (#37648109)
Can’t good-governance your way out of a stinker project.
Re:It's time to let go, Apache Software Foundation by pgeorgi on Monday September 25, 2023 @02:55PM (#37648788)
Of course that's possible, Apache even has a process for that: https://attic.apache.org/
Re:It's time to let go, Apache Software Foundation by pjmlp on Monday September 25, 2023 @02:39PM (#37648581)
Governance alone doesn't help, if there isn't a way to pay the bills.

It was cool to be a UNIX/FOSS zealot during the late 90's while still getting monetary support.

Writing M$ on the email signature and such.

Eventually I had to find a way to pay my bills.

Re:It's time to let go, Apache Software Foundation by raxxorraxor on Tuesday September 26, 2023 @05:47AM (#37656843)
In the current market you reliably can do both. Nobody in software can deny the importance of open source software, if only for learning or training. Without FOSS, there would only be stagnation.

You can even develop commercial software and still support FOSS. This isn't some think the kids of the 90s do. Most new open source projects are created by younger developers.

Re:It's time to let go, Apache Software Foundation by pjmlp on Tuesday September 26, 2023 @07:00AM (#37657456)
Try to make a living from open source desktop software, or open source games.

Younger developers are re-discovering public domain and shareware, while rebranding them as open core.

Re:It's time to let go, Apache Software Foundation by pxc on Tuesday September 26, 2023 @03:50PM (#37664930)
> Try to make a living from [...] open source games.

To me, many of the elements of political interest with free software in general don't really come into play with games (although some incidental issues, like privacy concerns, certainly do come into play in practice). Part of what makes software freedom urgent where it matters most is a very material dependency on software— it matters most when we depend on that software to make our livings, or to access medical care, or to access education. The stakes are lower for games, and I imagine that many people who care deeply about free software are still comfortable buying and running proprietary games. I know I am.

I don't think there's a serious problem with making/selling proprietary games, either, even if you're generally committed to free software.

Re:It's time to let go, Apache Software Foundation by londons_explore on Monday September 25, 2023 @02:54PM (#37648774)
> value of governance in OSS

You are assuming that a strict and stable governance model is good for OSS.

But often it is the least stable projects with lots of hostile forks and huge mailing list arguments which turn out to be the most successful projects.

Strict and stable governance model is perhaps dull and turns away contributors who feel they will never get to the top of such a stable project with long timelines and complex procedures for everything.

Re:It's time to let go, Apache Software Foundation by softwaredoug on Monday September 25, 2023 @03:03PM (#37648910)
"Strict and stable" isn't quite the important feature, its being community-managed. Chaotic projects with lots of forks, and disorganized governance may be a sign that there is a strong community. If the chaos goes on forever, then you're going to probably lose people to the drama (or the forks themselves will eventually stabilize). If the chaos is short, spasmatic, and leads to a better outcome, then it was overall a good thing in the project's governance.
Re:It's time to let go, Apache Software Foundation by londons_explore on Monday September 25, 2023 @03:05PM (#37648951)
It's the difference between:

> "Ask bob on discord and he'll give you commit access to the repo"

and:

> "First you need to fill out the CLA and send 3 pull requests before you can then apply for committer access at the bi-monthly steering group committee. Present your case in an email to them at least 28 days beforehand, and make sure an existing committer seconds it"

Re:It's time to let go, Apache Software Foundation by TylerE on Monday September 25, 2023 @03:44PM (#37649499)
There are things people argue over, and things no one cares about.
Re:It's time to let go, Apache Software Foundation by hodgesrm on Monday September 25, 2023 @11:11PM (#37653854)
Can you give a couple examples of such projects?
Re:It's time to let go, Apache Software Foundation by j-a-a-p on Monday September 25, 2023 @03:38PM (#37649421)
"Open Source" is such a strong brand nowadays, it suffices to claim to be open source. Even after so many projects flipped their license.
Re:It's time to let go, Apache Software Foundation by giamma on Monday September 25, 2023 @12:03PM (#37646091)
I think this is a wrong perceptions. Projects come and go, based on adoption, community interest, technology evolution, trends...

There are still a lot of projects at Apache.

Check their last annual report [1], especially the sponsors and the statistics sections.

[1] https://apache.org/foundation/docs/FY2023AnnualReport.pdf

Re:It's time to let go, Apache Software Foundation by mistrial9 on Monday September 25, 2023 @12:12PM (#37646224)
those Fortune 500 funders are slightly balanced by "pineapple fund" !
Re:It's time to let go, Apache Software Foundation by ianburrell on Monday September 25, 2023 @12:28PM (#37646493)
Apache has lots of active projects. But they are mostly data analysis. At work, we use Airflow to run Spark jobs which uses Hadoop and Hive.

Apache also has a lot of dead projects that never got picked up by users. Apache should have a marker for zombie projects so people don't start using them.

Re:It's time to let go, Apache Software Foundation by giamma on Monday September 25, 2023 @12:44PM (#37646740)
Well, the same would hold for github or any other open source container.

When I find something interesting on github, before deciding to use it, I check the number of committers and the commit history/frequency.

Anyone can do the same for Apache projects.

Re:It's time to let go, Apache Software Foundation by renegade-otter on Monday September 25, 2023 @01:11PM (#37647250)
GitHub is an unfiltered firehose. The job of something like ASF is to curate. It used to be that an "Apache project" meant the same as "solid, popular, vouched for, safe to use".
Re:It's time to let go, Apache Software Foundation by rbowen on Monday September 25, 2023 @01:46PM (#37647782)
The ASF does have a marker for retired projects. See https://attic.apache.org/

Software projects have a natural lifecycle, and since we've been around for almost 30 years, there's going to be a number of projects in that state.

However, the ASF doesn't force projects into the attic while they still have a community around them. OpenOffice is an edge case - there's still a project community, primarily around templates and other end-user-centric activities. They're just not doing much with the actual software any more.

Granted, there's room to disagree as to whether 1) the ASF should force projects into the attic and 2) whether OO actually has an active community. But the Foundation's position is that this is the decision of the project, not one to be forced top-down by the Board.

Re:It's time to let go, Apache Software Foundation by pavon on Monday September 25, 2023 @01:47PM (#37647802)
They do have the Apache Attic for that purpose, but they typically defer to the project maintainers to make the decision to retire a project, unless there are no longer any maintainers.
Re:It's time to let go, Apache Software Foundation by wiremine on Monday September 25, 2023 @12:58PM (#37647024)
Go to die, or go to provide incremental improvements? Maybe a bit of both? Either said, it's a good question.

Some projects are going to die, and I don't think that's the fault of the organization behind it. I'd love to see a more detailed analysis of all the current projects at Apache, and their growth/decline, and a breakdown of _why_ they're growing or declining. Maybe Apache is the problem, maybe it isn't.

Re:It's time to let go, Apache Software Foundation by talent_deprived on Monday September 25, 2023 @01:14PM (#37647301)
> Apache is the place OSS goes to retire/die

Fortunately many of us in the world disagree with the dystopian warped view.

Re:It's time to let go, Apache Software Foundation by phkahler on Monday September 25, 2023 @01:29PM (#37647537)
>> > Apache is the place OSS goes to retire/die >> Fortunately many of us in the world disagree with the dystopian warped view.

They would still be doing everyone a favor if they shut down OpenOffice completely and hand the trademark over to The Document Foundation. The name is better than LibreOffice, and the fact that a grossly outdated version of OpenOffice is what people will be finding is detrimental to the project. Most the developers and the code have moved on, but the name and a bunch of old code lives on with ASF for no good reason. Seriously there is NO reason for it except the completely selfish (and harmful to others) excuse that ASF can claim to be the stewards of OpenOffice. In my dystopian imaginary world they are even paid to maintain this situation to prevent more widespread adoption of LibreOffice.

Re:It's time to let go, Apache Software Foundation by taylorbuley on Monday September 25, 2023 @01:28PM (#37647514)
Thankfully, yes. But I still see an unmaintained project as a broken window, of sorts, that mars an otherwise nice open-source edifice.
Re:It's time to let go, Apache Software Foundation by AndyMcConachie on Monday September 25, 2023 @01:20PM (#37647399)
I was recently searching around for a good enterprise search engine and wanted something OSS. I found Apache Lucene and so far I really like it. It's got documentation, a clear release schedule, and I know lots of other people use it. I was happy to hear that it's Apache because it probably means it won't die because one maintainer goes away. Maybe it's silly, but if I find a project is Apache it gives me a good feeling.

Of course some of their projects die. That's OSS. But that's not something you can solve for. Even paid software goes away after awhile.

Re:It's time to let go, Apache Software Foundation by geertj on Monday September 25, 2023 @01:29PM (#37647538)
> I've felt for a long time (maybe even a decade) that Apache is the place OSS goes to retire/die.

It's a bit too strong as others have pointed out that there are very active projects under the Apache umbrella. But I do feel that there's a core of truth in this. Specifically, Apache does appear to provide a "way out" for large enterprise customers that want to dump non-strategic (to them) code somewhere and not necessarily invest in it. Seems something that could be solvable on the ASF side by having additional criteria before accepting projects, and maybe require a certain level of activity for continued membership.

Re:It's time to let go, Apache Software Foundation by no_wizard on Monday September 25, 2023 @01:53PM (#37647892)
Unless it’s one of their many durable Java projects, or the web server that bares its name. I think some things were (are?) bad fits for the ASF and languished as a result.

If you do a lot of development in the JVM ecosystem though you’ll find there’s a lot of ASF projects that are actively used and maintained

Re:It's time to let go, Apache Software Foundation by indymike on Monday September 25, 2023 @02:04PM (#37648062)
> If a project ends up in Apache it feels to me like it has gone out to pasture.

There are many Apache Foundation projects that are active and important or complete and important.

Unfortunately OpenOffice is not any of the above, and it was that way almost from the beginning. The original OO community largely went with LibreOffice. They did not like the interference of Oracle and later IBM in their project's governance. So, Apache got the trademarks from Oracle and a community of people who were largely not maintainers. This put Apache, almost from day one, in position to be competing with the community of one of their own projects.

Re:It's time to let go, Apache Software Foundation by pjmlp on Monday September 25, 2023 @02:36PM (#37648527)
At least in what concerns Java projects, Apache foundation was always quite relevant.
Re:It's time to let go, Apache Software Foundation by EFreethought on Monday September 25, 2023 @05:28PM (#37650927)
A lot of the relevant Java projects either started there or got brought in pretty early.
Re:It's time to let go, Apache Software Foundation by MPSimmons on Monday September 25, 2023 @03:50PM (#37649598)
Apache is kind of the CNCF of the 2000s, I think.
Re:It's time to let go, Apache Software Foundation by mekster on Monday September 25, 2023 @08:31PM (#37652739)
Or plane graveyard.
Re:It's time to let go, Apache Software Foundation by cameldrv on Monday September 25, 2023 @04:42PM (#37650330)
A big part of the problem is that the Apache foundation has become sort of a dumping ground for OSS projects where the corporate sponsor doesn’t want to be responsible anymore. They pull the full time developers and donate the project. In this context it’s not surprising that these projects “die”, because they’ve lost most or all of their contributors.
Re:It's time to let go, Apache Software Foundation by JoshuaRogers on Monday September 25, 2023 @05:09PM (#37650671)
At work I've lovingly but sadly referred to Apache as the "Crazy Cat Lady of Software." From the outside it looks like they're willing to take on any project that someone wants to give away regardless of whether they have the capacity to provide maintenance / governance of it themselves.

While I do love the preservation aspect of it, seeing that a project is maintained by Apache rings the same "Sure, but is the project already dead" bells in my head that I hear when I see a project from Google. In both cases, the name brings the concern that a project might be on its way out.

Re:It's time to let go, Apache Software Foundation by jsight on Monday September 25, 2023 @05:39PM (#37651071)
I feel like that is often true for organizations like this. Eclipse Foundation isn't much better.

Sometimes it is the place projects go when their original author wants to kill them but doesn't want to say they are doing that.