[Aplaws-devel] [aplaws - Developing on APLAWS+] RE: Raising the profile of APLAWS

[Aplaws D. L. <apl...@li...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=7407611
By: pboy

Terry,

for shure, on the "marketing" side of APLAWS there is a lot of room for improvement
-:)

Since some time I have administrative privileges on sourceforge and I will update
as much information as possible during the next weeks. Until now I was busy
with the URL resource: beast.

As soon as we have the next release ready, running in a standard JEE container,
we should do some "marketing" work, not only sourceforge, but freshmeat, cmsmatrix
and others. APLAWS / Byline had been present there for years, but sind the release
of 1.0.4 and the need to change a funded project to "user led" had made some
problems and delays. But looking over the commit log for the past months I think
the project is going well now.

Because of the "marketing needs" I'm very glad about your project of an "embedded"
database and the "examples" project (which make it easier to provide a demo
version). We should really try to discuss it and make plan for implementation.

|  Any thoughts on the future of APLAWS compared to others 
|  such as Alfresco etc. 

APLAWS / CCM has a lot of outstanding features (semantic approach, categorizing
system, among others, more technical ones) which set it apart from the crowd
of Open Source projects like Typo3 or Mambo/Joomla, etc.

Regarding Alfresco one idea was, to reimplement APLAWS's key conepts on top
of Alfresco to make use of their implementation of the Java Content Repository
framework. But Alfresco is not "really" an Open Source program but commercially
driven. And currently it is far away from a full fledged CMS.

So, if we decide to replace APLAWS persistence by JCR, we should use a really
free implementation like Apache's jackrabbit.

As a summary: In my perspective, the many outstanding features of APLAWS are
currently hidden and hampered by a bloated code base, performance and a lot
of minor usability issues, which sum up to a severe problem (steep learning
curve) for new users. For (to) a long time developers (Red Hat?) refused or
plumg forgot to clean up the code. Implementation of new features was the  main
and single goal. Discussions about that issue are 5 years old! "Never touch
a running system" was the motto. That strategie led to a situation, where new
Java functions were not used and some features of APLAWS are 2 or 3 times implemented
in a different way, because nobody understood the (bloated) code or it was to
time consuming to study it.

So, for the foreseeable future / the next months we should:

-  extensivly clean up the code which will result in performance gain and easier
maintenance and implementation of new functionality.

-  should polish up the user interface to make using APLAWS more pleasant.


Having done that we have a good chance to regain a terrain we may have lost
over the past year.


By the way, did you receive my mail (yesterday) via user.sourceforge?



Peter

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=368401