This is the beauty of open source. Apache 1.3 is still widely used, and many products are still based on it. If the Apache Foundation no longer wants to maintain it, others are free to pick it up and carry on. I wouldn't be surprised if this happened sooner rather than later.
So after a project dies it forks off into a slew a Legacy systems all needed independent modifications and changes. That is the Ugly side of Open Source to me. A more beauty side is if the tools that did need to work on 1.3 once apache stopped 1.3 support went and modified their apps to work on newer web browsers.
Forking code to keep your project going is not the way, it is just a bad idea.
Open Source (Score:4, Interesting)
This is the beauty of open source. Apache 1.3 is still widely used, and many products are still based on it. If the Apache Foundation no longer wants to maintain it, others are free to pick it up and carry on. I wouldn't be surprised if this happened sooner rather than later.
Re: (Score:3, Interesting)
So after a project dies it forks off into a slew a Legacy systems all needed independent modifications and changes. That is the Ugly side of Open Source to me. A more beauty side is if the tools that did need to work on 1.3 once apache stopped 1.3 support went and modified their apps to work on newer web browsers.
Forking code to keep your project going is not the way, it is just a bad idea.
Re: (Score:2)
Why ugly? It's better than the project dying, period.
And one of those forks may become the new official version.
Re:Open Source (Score:0)
The new official version exists. It's called Apache 2.2 (or 2.0, if you fancy old stuff).