Dear Ayan,
It is quite some time that the Aolserver and Naviserver communities
have joined their efforts and all new developments occur nowadays mostly on
Naviserver.
I believe you should extend your list of "desiderata" to this list:
https://lists.sourceforge.net/lists/listinfo/naviserver-devel.
As far for the future of Aolserver/Naviserver I see their evolution very
connected to the one of OpenACS.
I think that the union Aolserver/Naviserver - OpenACS historically was two
different things:
1. a feature reach platform for CMS and e-learning sites
2. an interesting and very productive/powerful platform to develop web
applications
But things have changed and keep changing:
1. social media are making legacy CMS and standard web sites less and less
important
2. web and mobile application are moving towards architectures with rich
clients (e.g. html5 based like SensaTouch, Oracle ADF, SAP SUP) and these
architectures are moving away from the legacy web application and
development model offered by Aolserver/Naviserver - OpenACS.
Hope it helps,
Maurizio
PS: About deleting Windows support in AOLserver I would like to rememeber
that perhaps the biggest user of Aolserver/OpenACS is still ]project-open[
and it might be interesting for you to look at these numbers:
http://sourceforge.net/projects/project-open/files/project-open/V4.0/
-----Original Message-----
From: Ayan George [mailto:a...@ayan.net]
Sent: 11 May 2014 19:38
To: aolserver-talk@lists.sourceforge.net
Subject: Re: [AOLSERVER] Roadmap Revisited (was Re: Is there anyone out
there?)
On 05/11/2014 01:35 PM, Ayan George wrote:
> * Completely commit to a traditional git workflow. Accept patches on
> the -talk submitted using list for review. Have subsystem maintainers
> apply patches. Dossy then pulls from each maintainer's tree to cut a
> release.
>
Eh -- this bullet point is mangled. I meant accept patches submitted to
-talk using git format-patch.
----------------------------------------------------------------------------
--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity • Requirements
for releasing software faster • Expert tips and advice for migrating
your SCM now http://p.sf.net/sfu/perforce
_______________________________________________
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
