[Ironpython-users] Community Meeting

[Slide]

See comments inline

On Mon, Jul 11, 2016 at 1:45 AM Markus Schaber <m.schaber at codesys.com>
wrote:

> Hi,
>
>
>
> Just my personal thoughts on some of the topics:
>
>
>
> - IronRuby - What do we want to do here?
>
>
>
> To be honest, IronRuby is not my personal area of interest.
>
>
>


> I’m in favour of splitting IronRuby, IronPython and the DLR into three
> different projects. Maybe we could bring some of them under the hood of the
> .NET Foundation or some other non-profit organization.
>
>
>
> While we can raise awareness for IronRuby, and try to initiate some
> community there, I think we don’t have the manpower and expertise to bring
> the project back to life on our own, as we’re already struggling with
> IronPython.
>
>
>

I wasn't meaning that we would or should support IronRuby. I agree with
what you say about splitting things out. My meaning was do we want to do
the splitting, or only worry about IronPython and the DLR and if someone
comes along wanting IronRuby, they can split it from "main" into its own
repo?


> - Issue disposition - there are currently about 961 issues, with most
> having been ported from CodePlex.
>
>
>
> We could hold some “bug squashing party” where we try to close
> non-reproducible bugs, link duplicates, and try to create regression tests
> for the remaining ones.
>
>
>

Agreed.


> - Release schedule - I would like to do more rolling releases, getting
> features and fixes out faster, but still maintaining stability
>
>
>
> +1. I suggest regular, time-driven releases, and maybe hotfixes for urgent
> bugs on demand.
>
>
>

Agreed


> - Continuous Integration - I was, for some time a contributor on the
> Jenkins project, I am approaching CloudBees to see what might be available
> for open source projects
>
>
>
> +1. This will also help with the “maintaining stability” point.
>
>
>
> We should run as much of the standard Python tests as possible, as well as
> our own IronPython specific tests.
>
>
>
> If it won’t work out with CloudBees very well, this might be something
> where the .NET Foundation could help, or maybe I could ask whether we could
> provide some infrastructure in our company.
>
>
>

I think we currently have _something_ on TeamCity, but I need to research
mode.


> - IronPython 3 - Roadmap to IronPython 3, which would be Python 3
> compatible.
>
>
>
> We should aim directly for IronPython 3.5 or 3.6 (or even 3.7, depending
> on the time frame?) – It makes no sense to target an older release.
>
>
>

I agree, by Python 3 compatible, I was meaning the 3.x series.


> Targeting an unreleased upstream version has the advantage that we could
> submit some upstream patches for the python part of the standard library –
> AFAIR, the cPython core devs are rather open to that kind of patches if
> they don’t bring to much hassle for cPython.
>
>
>

Yes, this would be very nice, pushing stdlib changes upstream would be
awesome.


> I’d also vote on using a different assembly name and namespace (e. G.
> “IronPython3”) – some users might need to support both IronPython 2 and 3
> in parallel (at least during some transition period), and using different
> assembly names and namespaces might drastically simplify this.
>
>
>

This is definitely something we can discuss.


> We should start with the parser, and work through the layers from there.
>
>
>
>
>
> Best regards
>
> Markus Schaber
>
> *CODESYS®* a trademark of 3S-Smart Software Solutions GmbH
>
> *Inspiring Automation Solutions *
> ------------------------------
>
> 3S-Smart Software Solutions GmbH
> Dipl.-Inf. Markus Schaber | Product Development Core Technology
> Memminger Str. 151 | 87439 Kempten | Germany
> Tel. +49-831-54031-979 | Fax +49-831-54031-50
>
> E-Mail: m.schaber at codesys.com | Web: codesys.com <http://www.codesys.com>
> | CODESYS store: store.codesys.com
> CODESYS forum: forum.codesys.com
>
> *Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner* | *Trade
> register: Kempten HRB 6186* | *Tax ID No.: DE 167014915*
> * ------------------------------ *
>
>
>
> *This e-mail may contain confidential and/or privileged information. If
> you are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorised copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.*
>
> *From:* Ironpython-users [mailto:ironpython-users-bounces+m.schaber=
> codesys.com at python.org] *On Behalf Of *Slide
> *Sent:* Monday, July 11, 2016 7:02 AM
> *To:* ironpython-users at python.org
> *Subject:* [Ironpython-users] Community Meeting
>
>
>
> Hello IronPythonistas!
>
>
>
> Jeff Hardy has handed over the mangement of IronPython to myself and
> Benedikt Eggers. We are hoping to recruit some new people to contribute to
> IronPython and get some releases out. We would like to have a community
> meeting to discuss future direction for IronPython. We're planning on
> holding the meeting on Gitter, you can find the room here:
> https://gitter.im/IronLanguages/main.
>
>
>
> I would like to cover the following agenda topics, but would definitely
> like to hear from community members what they would like to discuss as
> well.
>
>
>
> - IronRuby - What do we want to do here?
>
> - Issue disposition - there are currently about 961 issues, with most
> having been ported from CodePlex.
>
> - Release schedule - I would like to do more rolling releases, getting
> features and fixes out faster, but still maintaining stability
>
> - Continuous Integration - I was, for some time a contributor on the
> Jenkins project, I am approaching CloudBees to see what might be available
> for open source projects
>
> - IronPython 3 - Roadmap to IronPython 3, which would be Python 3
> compatible.
>
>
>
> Please reply back if you are interested in attending the meeting and
> specify your timezone. I'd like to make the meeting as easy to attend as
> possible for the most amount of people. We won't be able to get everyone,
> but I would like to get as many as possible. I would like to hold the
> meeting this Thursday.
>
>
>
> Thanks!
>
>
>
> Alex Earl
>
> (slide)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20160711/e9cc53a9/attachment.html>