Re: [Quickfix-developers] Unresolved stability issue in rev 2300

[<or...@qu...>]

Hi Brian,

Thank you for your comment, and I would first like to point out you are
100% correct that the level of participation from myself lately has been
unacceptable.  I don't want to go into to much detail about why I
haven't been able to commit the time, but would like to propose an
action plan that will put QuickFIX in a better situation as either a
going concern or a forked project.  I'm not going to put forward an
argument for or against a fork as a fork is beyond my control, so I will
only propose what I can control.

First though I would like to point out that I make exactly $0 from
QuickFIX.  I do not work for Connamara.  They have been a valuable
partner, but ultimately management of the project lies with me and it is
my fault not theirs that the project has remained inactive.

So what do I propose?  Here is a mini plan that I would like to see
enacted going forward.

1) Wrap up the release ready to go in source control.  There are many
fixes that are just sort of sitting in the repository that haven't made
it into a formal release.  So let's get that out there first.

2) Complete move to github.  Frankly svn and SourceForge are a huge pain
working with patches submitted to the bug tracker.  It will be wayyyyyy
easier to accept patches if we are working through git.  The added
advantage is that it will become trivial to for QuickFIX once on github.

3) Close out open bugs in the bug tracker.

4) Recruit an additional admin or 2 to help with the project.  I'm sure
Connamara would be willing to help with this, another community member
that uses QuickFIX daily would be a welcome addition.

5) Move to a regular release cycle.  The release cycle currently is at
my whim.  As you can tell that's not a very motivating deadline to hit. 
I'm thinking of moving to something like regular 6 month release cycles.

6) remove .NET support from standard QuickFIX.  We killed the JNI api a
while ago as QuickFIX/J matured, and now QuickFIX/n is mature enough as
well.  I spent probably 50% of project time maintaining these two APIs
and that is demoralizing.  Chopping the project down to just bare C++
and letting the satellite projects do their thing should improve
productivity.

So that's all I have for now.  Comments?

> -------- Original Message --------
> Subject: Re: [Quickfix-developers] Unresolved stability issue in rev
> 2300
> From: Brian Erst <azz...@ya...>
> Date: Mon, June 17, 2013 10:14 am
> To: Lolrim <pohrebnyak@i.ua>,
> "qui...@li..."
> <qui...@li...>
> 
> 
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html<hr>As much as I hate to say it (as QF has been very good), the only time you get traction on fixes/releases is when someone threatens to fork the project. 
> 
> 
> This project lay pretty fallow from 2006-2009, stuck on 1.12.4 (which didn't even support FIX 5.0, released in 2006) until, in March of 2009, developers got so frustrated that a fork was discussed pretty seriously. Suddenly, there was renewed interest by Oren/Connamara, but QuickFix 1.13.0 still took an entire year (Feb 26, 2010) to be released. A couple of quick bug fix releases over the next few months and then... nothing again for three years.
> 
> Connamara is a busy consulting firm and has long since moved on from any sort of active management/development of QuickFIX. Oren hasn't even participated in the forum since January of 2011. I don't blame them - they have lots of paying customers for their projects and are quite busy. Their bread and butter comes from .Net development - look at the change log of QuickFIX/n (https://github.com/connamara/quickfixn/commits/master) and see the frequent, active development of that system (four pages of commits this year alone).
> 
> 
> Management of traditional QuickFIX should be moved to a more active developer community with thanks to Oren and Connamara for getting it to where it is.
> 
> - Brian Erst
> 
> 
> 
> ________________________________
>  From: Lolrim <pohrebnyak@i.ua>
> To: qui...@li... 
> Sent: Sunday, June 16, 2013 2:24 PM
> Subject: [Quickfix-developers] Unresolved stability issue in rev 2300
>  
> 
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> Hi, team.
> 
> There is an unresolved stability issue caused by rev [2300] which contained
> my code changes.
> 
> I’ve uploaded a patch more than a year ago:
> https://sourceforge.net/p/quickfix/patches/23/ but unfortunately it is not
> reviewed yet. Could some of you take a look, please? There are a lot of
> complaints about stability on forum and I would like to resolve the issue.
> 
> Best regards,
> Viktor Pogrebnyak
> 
> 
> 
> 
> --
> View this message in context: http://quickfix.13857.n7.nabble.com/Unresolved-stability-issue-in-rev-2300-tp6495.html
> Sent from the QuickFIX - Dev mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers<hr>------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev<hr>_______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers