[Mono-dev] System.Json string handling

[Miguel de Icaza]

Hello,

The best way is to become an active contributor.   Look at bugs in Bugzilla
or missing features and provide pull requests.   If we like your code, your
style, and you can follow the direction of the team, you can graduate to be
a maintainer.

But this is not a short process, it takes a while.

Miguel

On Sun, Sep 21, 2014 at 6:58 AM, Chris Rogus <cricel472 at gmail.com> wrote:

> So, lurker though I have been to date, I would like to one day be able to
> help.  Miguel/whoever, what is the road to prove myself to be able to help
> with this backlog and support this excellent and worthwhile project?
> On Sep 21, 2014 5:18 AM, "Martin Thwaites" <monoforum at my2cents.co.uk>
> wrote:
>
>> I would have to both agree and disagree with Edward on that...
>>
>> Yes you need things to be updated and made to work so you get people
>> wanting to use the platform.  However, without making sure that the patches
>> meet standards and are considering all the options, you risk the opposite
>> the code gets worse, there are knock on affects.
>>
>> I'm as frustrated with the current process as most as I've been waiting
>> for the MVC5 stuff to be fixed and merged for a while.  What I would say is
>> though, I'd prefer for MVC4 to continue working as is, than some MVC5 stuff
>> work and MVC4 become unstable.
>>
>> You have to appreciate the position Miguel and the mono team are in.
>> They have a commercial product to maintain, that without that, they
>> wouldn't be able to eat (or put on what I've been told are awesome parties).
>>
>> At the end of the day, having mono is better than not.  Also, it's better
>> maintained than some other open source projects.
>>
>> That said, I think that there isn't enough time, currently, dedicated to
>> code that isn't useful to Xamarin.  They have taken stewardship of a
>> platform that goes beyond mobile platforms, and are controlling the
>> elements that are not part of their core business, however, they are acting
>> as a bottleneck for those.
>>
>> In short, there is a lot room for improvement, but where we are is by no
>> means a bad position.
>>
>> Just my two (or possibly four) cents.
>>
>> Martin
>>
>> On 21 September 2014 02:29, 何子杰Hzj_jie <hzj_jie at hotmail.com> wrote:
>>
>>>  And how to define practices and skills? If you guys do not have time
>>> to review the changes from contributors out of mono group, then how to find
>>> out new people to join the group? And, I continually see an incorrect
>>> design pattern in mono source code, which may cause unexpected behavior in
>>> multithreading environment. This kind of issue may not be able to get
>>> totally fixed, until someone else pointed out the design pattern is not
>>> correct.
>>>
>>> .Hzj_jie
>>>  ------------------------------
>>> From: Edward Ned Harvey (mono) <edward.harvey.mono at clevertrove.com>
>>> Sent: ‎21/‎9/‎2014 3:13
>>> To: Miguel de Icaza <miguel at xamarin.com>; 何子杰Hzj_jie
>>> <hzj_jie at hotmail.com>
>>> Cc: Steffen Kieß <Steffen.Kiess at ipvs.uni-stuttgart.de>;
>>> mono-devel-list at lists.ximian.com
>>> Subject: RE: [Mono-dev] System.Json string handling
>>>
>>>  > From: mono-devel-list-bounces at lists.ximian.com [mailto:
>>> mono-devel-list-
>>> > bounces at lists.ximian.com] On Behalf Of Edward Ned Harvey (mono)
>>> >
>>> > Tru dat.  However,
>>>
>>> I guess I'm actually trying to say two separate things:
>>>
>>> * When broken stuff doesn't get fixed, it's a disincentive for usage
>>> adoption.
>>> and
>>> * When pull requests get ignored, it is a disincentive to contributors
>>> trying to contribute anymore (fixing things).
>>>
>>> This is an unfortunate positive feedback loop, which can hopefully be
>>> broken some day.  I know based on my experience here so far, I'm not going
>>> to bother trying to fix anything anymore.  My time would have been better
>>> spent, finding an alternative to mono SslStream instead of trying to
>>> contribute the fix to make mono SslStream operational.
>>>
>>> _______________________________________________
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>>
>>>
>>
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140922/9f46c31a/attachment.html>