[Ironpython-users] Attracting new developers

[Jeff Hardy]

On Thu, Nov 5, 2015 at 12:55 AM, Kuno Meyer <kuno.meyer at gmx.ch> wrote:

> First, I would start processing pending pull requests and react to bug
> reports on Github (merge / give feedback). A project that has virtually
> lost all active core developers and that nobody feels responsible to create
> roadmaps and to drive releases is not very likely to attract new developers.
>
> Then, and maybe I've missed that, there should be an official statement
> about the healthiness of the 3.0 branch (compared to the 2.7 branch) and
> about where checkins should go.
>
> And finally, it would be very helpful if some "official" test suite
> results would be accessible somewhere, so that any developer can easily see
> which of the red tests are actually due to his changes.
>
> Just my 2 cents. I am using IronPython on a daily basis, but the current
> situation makes it hard to recommend it to anybody else.
>

Agree with all of this. I'll try to be better about checking on PRs within
a couple of days instead of letting them linger.

I have a half-written blog post on IronPython status to remind people that
it's not dead. :) Posting the test suite results is a good idea, and the
teamcity server used to have them, but the test suite also needs a lot of
work to pass cleanly.

Still, I know it's frustrating to only have radio silence form the core
devs, but I can only say "sorry, to busy with real life" so many times
before it starts to lose all meaning. It's been a very busy year for me;
next year should be better, hopefully.

- Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20151105/a1003fdd/attachment.html>