If the team does not want to let mono go worse. Then I would suggest to add more test cases, and a peer reviews. But if mono team is just simply ignoring pull requests out of core business, and trying to make mono close for other developers. Then just let other volunteers know, we properly can start another more open mono project.
.Hzj_jie ________________________________ From: Edward Ned Harvey (mono)<mailto:edward.harvey.m...@clevertrove.com> Sent: 21/9/2014 21:21 To: Martin Thwaites<mailto:monofo...@my2cents.co.uk>; 何子杰Hzj_jie<mailto:hzj_...@hotmail.com> Cc: Miguel de Icaza<mailto:mig...@xamarin.com>; Steffen Kieß<mailto:steffen.ki...@ipvs.uni-stuttgart.de>; mono-devel-list@lists.ximian.com<mailto:mono-devel-list@lists.ximian.com> Subject: RE: [Mono-dev] System.Json string handling > From: Edward Ned Harvey (mono) > > even as Xamarin customers you can't get anyone to review your > patches. As a tiny little baby step in the right direction, I think Xamarin could at least promise to review pull requests submitted by customers paying for support. (This is a little bit shy of fully supporting mono, which would be even better.) Right now, even if you're willing to pay for it, there is no such thing as mono support. It's tough to get businesses developing applications on mono, staking the core of their business on mono development, with this kind of limitation. I know I made this commitment, starting my business, before I knew any better, and now that we're fully entrenched, people ask me in retrospect, did I make the right decision? And the answers I provide are a big resounding "Maybe?"
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
