On Thu, May 19, 2016 at 7:47 AM, Auke Schrijnen <[email protected]> wrote:
> Hi all!
>
> We are sad to see the development of Synapse slowly stop. We use Synapse in 
> our integration platform since 2012 which has proved it’s use and still 
> perfectly does the job. Over the years we had to apply some patches, 
> especially to make the servlet integration work with the various mediators 
> and transport methods.
>
> When trying to contribute to the Synapse project we ran into a wall. Our lack 
> of understanding of the Apache rules and uses and all the hurdles to overcome 
> made that we didn’t contribute that much. It’s really hard compared to 
> contributing to projects which are using tools like GitHub or Gerrit.
>
> I’m wondering if the user base of Apache Synapse has shrunk to 1 (just us). 
> Back in 2012 the development seemed stable and WSO2 was involved in the 
> project. Did they move away from Apache Synapse?

They forked Synapse and continued development on their fork. It looks
like they are now submitting some of these changes back to Apache
Synapse; at least that's what I got from looking at some of the
recently submitted patches.

Part of the problem of the Apache Synapse problem has always been that
the project is too dependent on contributors of a single organization.
It would be great to see you contribute actively to the project in
order to get more diversity.

> Or are there more organizations using Synapse?
>
> What can be done to revive the project and keep it alive? Andreas created a 
> 1.7.2 release for Axis2, what would it take to create a 2.2.0 release for 
> Synapse?

Update the release process to make it conform to the current
requirements for Apache releases.

>
> Auke
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to