News for hackers. Stuff that matters.
Re:Apache NetBeans Proposal by dr_faustus on Tuesday September 13, 2016 @09:11AM (#12487840)
Is it me or has Apache increasingly become the place open source projects of big companies go to die? OpenOffice, Geronimo, Harmony, Wave, etc.pp.

I really think that Apache should stop incubating projects which were essentially discarded by their corporate owners. Successful OSS projects are either community projects from day one (HTTPd etc) or require (at least initially) strong interest and involvement of the company that donates the code. How can you expect a community to magically develop around an abandoned project?

Re:Apache NetBeans Proposal by TylerJewell on Tuesday September 13, 2016 @10:14AM (#12488391)
I am the project lead for Eclipse Che - developer workspace server and cloud IDE. The core of this project came out of Codenvy. Three years ago we were searching for the right governance model and community to open source Che from Codenvy.

We originally started with Apache. We went that way because we did not have relationships with Eclipse Foundation, the Orion project - a perceived competitor at the time - was already there, and concerns over IBM having an outsized dominance / influence over the community.

When we reached out to the Apache foundation to discuss the ways we could get our software into their foundation, building mentors, and also cross-project collaboration - we really struggled. We were unable to get the necessary endorsements. Apache was really bare bones governance. Because we couldn't get the right mentors, the proposal never made it out of an early proposal phase.

Serendipity at the time had me accidentally meat the Orion project lead at the Eclipse Foundation. Conversations ensued, and a path for how Che could come to be a reality with the support of other vendors that wanted to get involved was laid out. And that lead to our ultimate path into Eclipse and promotion there.

So this is an interesting back story about how one project ended up in Eclipse vs. Apache.

Interestingly, Eclipse is opinionated about the projects they promote. They are topically focused and work for project cross-pollination along with driving marketing initatives and IP policies around driving adoption of their core underlying projects. So that is a bit of a departure from the Apache approach where each product is more autonomous in terms of its underlying promotion responsibilities.

This plays a little bit to @dr_faustus comment on Apache being a place where many large projects are going - they can do that because the community already exists and they need the most structured infrastructure / process.

Re:Apache NetBeans Proposal by gtirloni on Tuesday September 13, 2016 @10:51AM (#12488757)
I'm curious to understand where to draw the line between the need for governance/bureaucracy versus just releasing code on GitHub and being a good participant (reviewing PRs, running a mailing list, etc).

Maybe whenever there are a dozen or so companies trying to create a business model so they don't fight each other too much? Has that ever worked with the high profile Apache projects that people remember here (OpenOffice, CouchDB, etC)?

Re:Apache NetBeans Proposal by TylerJewell on Tuesday September 13, 2016 @11:01AM (#12488854)
There is a really interesting distinction between Apache and Eclipse around IP policy. It's taken me a good year of releasing with Eclipse to understand many of the nuances.

The biggest distinction is that Eclipse has an IP Policy where all of the code and assets has to have provenance of the code - either code submitted under a CLA, but if there are links to third party libraries, they are each independently reviewed by an on staff legal team. There are more details beyond this, but that level of human provenance review for every Eclipse project for it to be released, enables certain companies to more readily and easily adopt projects with not only an EPL license, but released as an Eclipse project with signed binaries on their hosted servers.

There are differences around mentoring, release process, hosting rules, infrastructure. But at the end of the day, it's about structure, rigorous rules, mentorship, and community.

Re:Apache NetBeans Proposal by jimjag on Tuesday September 13, 2016 @02:07PM (#12490780)
Apache's IP provenance is also considerably robust and respected.
Re:Apache NetBeans Proposal by specialist on Tuesday September 13, 2016 @03:03PM (#12491250)
Thank you for sharing.

"...we were searching for the right governance model..."

I am very interested in comparisons of governance models. Case studies, war stories, analysis, whatever.

I joined a team working on OSS specifically to learn more about governance. The stewards of kuali.org were a consortia. It was a train wreck. Least common denominator consensus based decision making, layers of hierarchy, no accountability, paralysis and inaction, abundance of NIH / reinvention, etc.

Tellingly, kuali is now kaput.

Sadly, I didn't learn anything actionable about governance.

Re:Apache NetBeans Proposal by TylerJewell on Tuesday September 13, 2016 @08:27PM (#12493391)
It would be a nice white paper to compare the development, release, IP, infrastructure and branding processes of the Linux Foundation vs. Apache vs. Eclipse.

I pick these three as they are foundations that have been long lasting and have proven an ability to retain member companies and a diverse set of projects.

The comparison would take a lot of effort to do but be worthwhile. You need to compare details as minute as around how web sites are hosted, how products are named, trademarking + copyright issues, provenance and IP policies around releases, mentorship, maintenance --- even things as formal as how issues are created, pull requests established, and how projects are organized among the committers.

The foundations can derive policy and rules at any level - and there is a significant variance depending upon the underlying charter of what the foundation is trying to promote. So the best place to start is the bylaws of each foundation, which are open source themselves, to understand the underlying motivation. Nearly all choices are made from the underlying principles.

Interestingly, the Eclipse Foundation is one of the larger revenue organizations from member contributions, but they do not have that many projects - maybe 300 or so. The IP provenance requirements are so stringent that many smaller projects turn away because they do not desire such a level of review. So the Eclipse Foundation is about to introduce a dual IP mode where projects can self-certify their IP provenance. The entire process around releases will be different can instead of taking weeks to make a release, could be done nearly instantaneously, allowing many projects that have a small group or open source license to become a project of the foundation, if that was a desire.

Re:Apache NetBeans Proposal by rectang on Tuesday September 13, 2016 @09:22PM (#12493611)
Apache doesn't have "member companies" -- it is governed by individuals.

Apache is also a 501(c)(3) charity for the public good -- as opposed to a 501(c)(6) business league like Eclipse and the the Linux Foundation.

One of these things is not like the others.

Re:Apache NetBeans Proposal by geodel on Tuesday September 13, 2016 @09:47AM (#12488157)
It is not you. If you look closely at Apache projects. They are mostly Java type projects in various state of completion. Some are either failed at corporates and hence dumped there (struts, cordova and so on) or too experimental and hence good place get wider audience. If successful the main sponsor will add proprietary features/components and sell product and/or support(e.g Hadoop ecosystem components).

Some exceptions to this are Apache Http server, tomcat, svn etc.

Re:Apache NetBeans Proposal by _wmd on Tuesday September 13, 2016 @10:39AM (#12488623)
There are plenty of live and popular Apache projects that get plenty of press time: Zookeeper, Hadooop, CouchDB, Cassandra, Storm, Cloudstack, SpamAssassin, Lucene(! -- the guts of ElasticSearch), Spark, .. hell, the list is fairly endless.

Yes they adopt a lot of code (OpenOffice!) and weird abstract crapware, but this is not quite the norm. If you measure the success of the average Apache project, I'm certain it is vastly higher than any comparable organization, although I'm not sure who you could compare Apache to.. GNU?

Re:Apache NetBeans Proposal by geodel on Tuesday September 13, 2016 @12:17PM (#12489671)
Not much to disagree here. The success of Apache Http and Tomcat server will itself lift average success rate by quite a bit. Others if successful are mainly a vendor driven version of software.
Re:Apache NetBeans Proposal by DashRattlesnake on Tuesday September 13, 2016 @05:07PM (#12492242)
> struts

Wasn't Struts a once-popular non-failure whose time has passed; rather than a corporate failure that was "dumped"?

Re:Apache NetBeans Proposal by smrtinsert on Tuesday September 13, 2016 @10:04AM (#12488303)
I look at the project list and I think the great majority are not dead and abandoned. They are not the hottest list of tech but they are stable and used.
Re:Apache NetBeans Proposal by andrewbinstock on Tuesday September 13, 2016 @08:56PM (#12493520)
That's in part because the dead ones and the dump-ware are migrated by Apache to the "attic."
Re:Apache NetBeans Proposal by rectang on Tuesday September 13, 2016 @09:51AM (#12488185)
Apache is biased towards giving communities a chance.

Costs are low -- for about 200 projects, the ASF runs on a budget of around 1.4 million USD per year. It doesn't take that much to give a community a home -- the community itself is primarily responsible for making things happen.

Re:Apache NetBeans Proposal by jsight on Tuesday September 13, 2016 @09:43AM (#12488113)
People used to say that the surest sign of death for a project was to get a domain at Apache.org. This goes back at least ten years.
Re:Apache NetBeans Proposal by moondowner on Tuesday September 13, 2016 @09:44AM (#12488125)
It's still the same... "OpenOffice, after years of neglect, could shut down" http://arstechnica.com/information-technology/2016/09/openof...
Re:Apache NetBeans Proposal by agentgt on Tuesday September 13, 2016 @12:14PM (#12489630)
I sort of agree and see that trend but on the other hand some projects are flourishing on Apache.

My biggest gripe with the Apache community sphere is it is pain to contribute (I mentioned it here as well: https://news.ycombinator.com/item?id=11121563) and there is often interesting politics that develop on the mailinglist between developers. It seems when you start talking but "organizational" + "community" things some interesting behaviors happen (like who is the head honcho and who should we kick out).

On the other hand Apache does offer some continuity (in the event something happens to a lead developer) I suppose.

Re:Apache NetBeans Proposal by sspiff on Tuesday September 13, 2016 @09:34AM (#12488028)
I was thinking the same thing. Many big open source projects are "entrusted" to Apache after their funding/support is cut off.

Why is Apache taking these up / wasting time on them? So far all of them have died shortly after, with no significant improvements landing once Apache has taken over.

Re:Apache NetBeans Proposal by vorg on Tuesday September 13, 2016 @10:53AM (#12488774)
> Many big open source projects are "entrusted" to Apache after their funding/support is cut off

Although "entrusted" to Apache, they're still controlled by the same people who change their titles from XXXX Project Manager at BigCorp to Apache PMS Chair for XXXX. These people are often the reason the project funding is cut off, and they'd rather keep control of a shrinking ecosystem than give up some control so the project can be saved, where they'd have a smaller share of a larger ecosystem.

Re:Apache NetBeans Proposal by toopok4k3 on Tuesday September 13, 2016 @10:13AM (#12488385)
Because the software still works and can be used by someone. Sure they might not be maintained and bug fixes wont happen. If the software does something that has no free alternative, the Apache one can still be used by someone for something to fill a need somewhere.

Yeah I know this is an absurd concept (to some) that someone might use older than a few year old tech.

Being an Apache project means(to me at least) that the product is ready to use and someone has used it before with at least some success. I trust a random open source product much less than anything Apache.

Re:Apache NetBeans Proposal by ricksplat on Tuesday September 13, 2016 @10:11AM (#12488369)
> Why is Apache taking these up / wasting time on them?

Presumably they get some funding in return. It makes $$$ sense for those entrusting if they have an established user base they no longer want to support.

Re:Apache NetBeans Proposal by jimjag on Tuesday September 13, 2016 @02:09PM (#12490794)
The discussions and rationale for accepting any and all projects is done on-list, on the public Incubator threads. There are no "side deals" or "arrangements" other that was is opening and publicly discussed. In any case, any sort of quid-pro-quo about funding is NOT part of the equation.
Re:Apache NetBeans Proposal by ricksplat on Tuesday September 20, 2016 @09:13AM (#12539234)
I didn't mean there were "side deals" I just presumed that funding for Apache came from somewhere and this is surely somewhat from the organisations that donate technology. To say it's NOT part of the equation is naive at best, disingenuous at worst. Money is ALWAYS part of the equation.
Re:Apache NetBeans Proposal by ricksplat on Tuesday September 20, 2016 @09:14AM (#12539239)
Re:Apache NetBeans Proposal by coolspot on Tuesday September 13, 2016 @01:20PM (#12490336)
Also a lot of projects succeed under Apache. NetBeans is great piece of software and it is not even remotely close to die.
Re:Apache NetBeans Proposal by jimjag on Tuesday September 13, 2016 @02:43PM (#12491097)
"Is it me or has Apache increasingly become the place open source projects of big companies go to die? OpenOffice, Geronimo, Harmony, Wave, etc.pp."

It's just you :)

Seriously though, that is a mistaken impression, bolstered by people who have a vested interest in that impression. Instead, Apache is a place where large open source projects of big companies go to build an independent and healthy community around the project. Sometimes it doesn't work out, for numerous reasons, but most of the time the change is one of the best things to happen to the project.

Re:Apache NetBeans Proposal by orionblastar on Tuesday September 13, 2016 @10:29PM (#12493866)
Actually I think this is the way that FOSS projects are designed. If one group can't maintain it, another can take it over.

Netbeans was fine for a while and then better tools came out. I used Frontpage and Visual Interdev in the mid to late 1990s, discovered Netbeans later on. I remember downloading Netbeans with the Java SDK.

Re:Apache NetBeans Proposal by mgr86 on Tuesday September 13, 2016 @10:30AM (#12488543)
maybe, in fact, reading some of these comments it feels like they have quite the collection there at Apache.

But I personally find myself using Apache Lucene by way of Apahce Solr quite frequently. If we were a bigger organization I'd likely look at Zookeeper and Kafka as well. Alas the library market can be a small and depressing market.

Re:Apache NetBeans Proposal by mavelikara on Tuesday September 13, 2016 @12:59PM (#12490132)
Wasn't Geronimo and Harmony formed at Apache (and not donated by a commercial entity)?
Re:Apache NetBeans Proposal by tn13 on Tuesday September 13, 2016 @02:08PM (#12490787)
Isn't Apache a community itself ? Should not it be left to the community to decide if they want to support that given project. Apache itself can abandon the project if there are not contributors.
Re:Apache NetBeans Proposal by hota_mazi on Tuesday September 13, 2016 @01:11PM (#12490244)
You can add Groovy to that list.
Re:Apache NetBeans Proposal by rectang on Tuesday September 13, 2016 @01:39PM (#12490520)
Since Groovy has come to Apache it has thrived, though.

https://twitter.com/aalmiray/status/775614209442840576

Re:Apache NetBeans Proposal by hota_mazi on Tuesday September 13, 2016 @02:43PM (#12491100)
The Groovy download numbers have been infamously inflated [1]

Besides, most Groovy downloads come from Gradle. Hardly anyone starts a new project with Groovy, it's become a niche language used exclusively to write build files.

[1] https://news.ycombinator.com/item?id=8107241

Re:Apache NetBeans Proposal by vorg on Tuesday September 13, 2016 @05:51PM (#12492562)
Nowadays if you check bintray for Groovy downloads, virtually all of them come from Germany, which is where the server hosting the groovy-lang.org site is located.

Gradle 3.0, which came out last month, has replaced Groovy with Kotlin as its prefered choice for writing build scripts and plugins, so expect Groovy's use for build scripts to decrease.

I think Groovy will live long for scripting on the JVM, in the same way Bash is used for Linux. All the extra cruft Groovy bundles (e.g. MOP, static typing) will become irrelevant over time.

Re:Apache NetBeans Proposal by oldmanjay on Tuesday September 13, 2016 @03:55PM (#12491654)
"People only use groovy to get shit done" is not an argument in favor of groovy dying.
Re:Apache NetBeans Proposal by johnhenry on Tuesday September 13, 2016 @11:18PM (#12494033)
Arguably, it's not where open-source projects go to die, but rather, where we send projects that should die, but we're just not ready to let them go.