Slashdot Mirror
Eazel Shutting Down, Nautilus Will Continue
1010011010 pointed out this follow-up email from Darin Adler about the future of various projects maintained by former Eazel employees, including Nautilus, gnome-vfs, and various libraries, as well as bugtracking and other necessities.
Shutting down is never a happy event, but it's gratifying to see email from Andy Hertzfeld (also on the gnome-hackers list) in which he says: "I just want to reaffirm my personal commitment to the continuing development of Nautilus, the GNOME platform and free software in general. I plan to keep working hard to make free software easier to use and I'm still optimistic that our work can make a big difference to millions of users."
rexlam indicates this story from cnet on the shutdown as well. Best of luck to everyone at Eazel.
I like this new net order:
1) Get an idea
2) Fake a business plan
3) Get VC funding
4) Use the money on development, not marketing
5) Release the code as open source
6) Go under
7) Leave the world a better place on the VC dime.
Kevin Fox
--
Kevin Fox
Their biggest mistake was jumping the gun in calling themselves a business. If they wanted to succeed, it would've been better to develop it as a side project until it was almost usable, and then to announce the formation of such a company when all the pieces were in place.
I used up all my sick days, so I'm calling in dead.
The original clause is:
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
This product includes software developed by the University of California, Berkeley and its contributors.
The rational behind not using licenses that include this clause is quite sound, you can see some arguments for omiting that clause at http://www.gnu.org/philosophy/bsd.html (don't worry, it doesn't say the BSD license sucks and everyone should use GPL). You could imagine how such a clause could cause problems if, perhaps, you had a product that included 40-50 of programs with those kinds of licenses -- the required statements could outnumber actual ad-space.
I used up all my sick days, so I'm calling in dead.
Anybody remember the hype that "Java was dead?" Well, here we go again...
My predictions:
Dvorak will declare Gnome dead, saying KDE has won.
Having been overcome by the excitement, Fred Moody will have a fatal seizure while trying to write a similar story.
ZDNet will run future KDE vs. Gnome reviews, and give KDE the thumbs up based on Gnome's "no longer maintained" file manager.
In the meantime, both the Gnome and KDE camps will continue building great desktop environments. Nautilus will lose its services, get cleaned up, stabilize and offer dramatic performance improvements such that it is everyday usable.
Well that's all of my rant, best be getting back to that highly lucrative Java programming now.
--
To all of the Eazel folks who were affected, my sympathies and a hearty thanks to those (especially Eli Goldberg) who were always there to answer my questions and provide troubleshooting suggestions. I'm happy to hear that most of the major project leaders are going to continue working on Nautilus and look forward to what the future may bring. Maybe in another time and climate, things would have worked out differently. As the story submission says, it _has_ been a fun ride. ---tomg
On the face of it, OSS projects should be able to survive the transition of management from the project initiator to another group of interested developers, but it's not that simple. OSS projects are more than the source code. There is a great deal of infastructure required in order to manage decentralized development efforts. Thanks to SourceForge for providing a great deal of that infastructure. The other componant needed in an OSS project is a leader, weather that is one person or a group of people. This leader is the visionary and driving force behind the project and unless projects can find new leaders for developers to gravitate around, the project will unboubtedly slide into mediocrity and disrepair.
Much luck to the projects left stranded by the demise of Easel. It appears that the project leaders are taking steps to find the ptojects new homes, with varying degrees of success.
--CTH
--
--Got Lists? | Top 95 Star Wars Line
...big businesses, the government, charitable organizations and philanthropists. After all, is not art sponsored by the government and other organizations? Maybe Eazel should have applied for a grant, one never knows.
Maybe we should actively pressure our representatives to sponsor free software because it's for the greater public good. Just one man's opinion. I hope the McArthur Foundation and others are listening.
Claric
--
There's no problem that cannot be solved with a suitable amount of high explosives
If a company were to donate their source code to a non-profit organization that acted as kind of a clearing house for open source projects, is it possible that some or part of the development costs could be written off once the result was donated to the non-profit?
While Eazel might not be the best example of the power this could have, as it has already provided the code open sourced and likely doesn't have much tax liability at all... Imagine a closed source project that never sees the light of day and ends up in a bit warehouse somewhere. I am the investors in many of these failed tech companies wouldn't think twice about assigning the IP rights to get something back after everything blew up.
Free software is a wonderful thing, and it is definitely possible to make money off of it. Companies like Red Hat and IBM are demonstrating this. I encourage that. If you have a business that can survive while developing and releasing free software, that is excellent.
On the other hand, if you have no business plan, free software won't help you. HINT: "make a file manager and give it away" is not a complete business plan. Even if it becomes popular, if you lose money for every copy you give away, even if you lose less money per copy if you give away more copies, you still won't be a viable business.
I have no sympathy for anyone involved. Neither the idiot venture capitalists who sponsored a project with no clue how it would make money, nor the developers, who obviously confused coding sense with business sense.
I've been in business, and you can't always do what you want. Sometimes, you have to put a lot of effort into making a profit, or else you just won't survive. Where are your ideals then? I wish the best of luck to the hackers involved, and I have a lot of hope for Nautilus. But next time you get involved in a business venture, make sure that sound financial advice is one of the first things you get!
Being Liberal should be a Crime!