Comments on: Alfresco packaging for Fedora

By: Open Core: The worst of both worlds - Lone Wolves - Web, game, and open source development

Fri, 09 Oct 2009 13:28:21 +0000

[...] SugarCRM is not just an exception here. Even open core projects that do have a more open development model, like Alfresco suffer from quality problems. [...]

By: quaid

quaid — Thu, 06 Aug 2009 20:57:34 +0000

September 2008:

http://www.redhat.com/archives/fedora-isv-sig-list/2008-September/msg00000.html

I got that from Jesse Keating in a thread that I think you had been on originally but may have bowed out of by then.

Until I get better advice or directions from Fedora releng, that’s the simple message I’m continuing to broadcast.

By: Andrew Overholt

Andrew Overholt — Tue, 04 Aug 2009 12:14:30 +0000

When did we recommend putting anything in JPackage?

By: quaid

quaid — Mon, 03 Aug 2009 14:40:51 +0000

I’m still not fully understanding the disconnect with Maven and Fedora, need to do more research here. Fortunately, it appears I know the packager, so I’ll work from there.

By: James

James — Mon, 03 Aug 2009 01:19:17 +0000

The first thing to solve for JBoss would be to get a recent version of Maven packaged[0]. Once you’ve got the build system, you then can start of the dependencies.

[0] http://fedoraproject.org/wiki/Java/JPPMavenReadme

By: quaid

quaid — Sun, 02 Aug 2009 23:50:35 +0000

Don’t think I haven’t thought of doing general calls for help around JBoss applications. But that is, as you imply, a pretty complex beast, and there is an entire team of smart cats at JBoss.org that know all the right people to help … far better than I do. If they come to Community Architecture asking for our help in duplicating what Fedora does so well, we’ll give it. In the meantime, getting the Alfresco needle progressed a bit might help sway some opinions about the feasibility of packaging Java apps for Fedora.

By: snerd

snerd — Sun, 02 Aug 2009 09:33:01 +0000

Shouldn’t we focus on getting cough-simple-cough stuff like jboss in fedora first?

By: quaid

quaid — Sat, 01 Aug 2009 16:46:06 +0000

Those are fair points, and we may discover it’s all a big mess, as Spot did with Chromium. My hope is that packaging on the community side will influence their packaging on the paid support side. I’m certain that the enterprises I’m talking to are interested in supported versions, but they don’t want crack-rock packaging or insecure, unmanageable jarballs. Since the place where we have a whisper of a chance to influence packaging is on the community version, that’s where we start. Heck, it worked for Fedora, which improved the quality of packages in RHEL et al.

By: Juanjo

Juanjo — Sat, 01 Aug 2009 09:06:11 +0000

I think Alfresco will be hard to package.

Warning: rant follows, keep reading on your own risk

I’ve deployed the OS version several times in CentOS 5.x and it’s PITA. Alfresco open source model of development sucks (IMHO), because the OS version usually has not the required level of quality to be in production.

I know it’s the Alfresco strategy to get people into paid support, but it’s very disappointing (the quality of the releases is bad, they don’t fix bugs -even severe- until next release, the configuration is a messy bunch of XML, the documentation is bad, …).

As you should have noticed I’m not a big Alfresco fan. In my company we’ve discarded Alfresco and we’re using Nuxeo for different projects.

I don’t want to discourage to any packager, I just wanted to say that it will be painful