Contributions are one thing, but there should be a windows build system implemented and running - even continuous integration running for each commit. I'm pretty sure there's a Jenkins set up for the linux/mac builds but non for Windows? Why?
On 16 October 2014 15:45, Edward Ned Harvey (mono) < edward.harvey.m...@clevertrove.com> wrote: > > From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list- > > boun...@lists.ximian.com] On Behalf Of Bryan Crotaz > > > > Basically if we could persuade Xamarin to get mono building on Windows > and > > VS users able to debug Mono, suddenly there would be a lot more > > developers able to contribute without having to learn a whole new stack > > first. > > As discussed previously on this list in other threads, the barrier to > contribution to the mono code base is not a lack of developers - there are > plenty of people willing and able to work with XS or MD on mac and linux. > The problem is bottleneck of Xam employees to review and test code > submissions. There is already a huge backlog of pull requests; they just > don't have enough human resource to handle it. The community isn't pouring > forth with experienced volunteer maintainers to step into that role > either. And it takes quite an investment to get all the build & test VM's > up to run a full fledged test environment anyway, which is necessary to > pass before pull requests can be accepted. > > Hopefully this can improve someday. For now, community contribution is > sparse. > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list