[Mono-list] Mono Project website

[Martin Thwaites]

I'm assuming that this doesn't affect anything Xamarin might use...

It's quite interesting as I'm assuming that most areas of mono are
maintained by a Xamarin employee.  The question would be whether these
folks are allocated any time to look at community patches, or whether they
have to find time among the company's priorities, or whether they have to
do this in their own time.

I suppose this is the issue with Xamarin employees being the sole person
who can merge these fixes.  The issue though, Xamarin is hiring all the
people who can do it! (not that it's a bad thing, people gotta eat after
all).

I don't know the way forward, just making observations.


On 16 June 2014 18:29, Martin Thwaites <martin at my2cents.co.uk> wrote:

> I'm assuming that this doesn't affect anything Xamarin might use...
>
> It's quite interesting as I'm assuming that most areas of mono are
> maintained by a Xamarin employee.  The question would be whether these
> folks are allocated any time to look at community patches, or whether they
> have to find time among the company's priorities, or whether they have to
> do this in their own time.
>
> I suppose this is the issue with Xamarin employees being the sole person
> who can merge these fixes.  The issue though, Xamarin is hiring all the
> people who can do it! (not that it's a bad thing, people gotta eat after
> all).
>
> I don't know the way forward, just making observations.
>
> Martin
> On 16 Jun 2014 17:30, "Edward Ned Harvey (mono)" <
> edward.harvey.mono at clevertrove.com> wrote:
>
>> > From: bar.hofesh at safe-t.com [mailto:bar.hofesh at safe-t.com]
>> >
>> > We have the same issues as paying customers , in the end we just forked
>> and
>> > updated our own repo as we don't have time to wait forever until we get
>> > approved for the pull request
>>
>> In our case, there's a fatal security bug - not one that compromises
>> security, but one that makes the SslStream communications fail - so we had
>> to create our own fork, and we have to continue maintaining our fork,
>> building and distributing our customized version of mono to our customers.
>>  That was about 2 months ago.
>> _______________________________________________
>> Mono-list maillist  -  Mono-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-list
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-list/attachments/20140616/0462b827/attachment.html>