Hi, Dong-hee: Thanks for your comments.
If that is helpful for coredev's review, I can set it up. However, since the porting to VxWorks has not been done, I am afraid that we are not allowed to connect the Buildbot to avoid breaking the existing CI. Is it possible just setting a Buildbot for reviewing use without connecting to CI? Thanks, Peixing -----Original Message----- From: Dong-hee Na <donghee.n...@gmail.com> Sent: Friday, August 7, 2020 4:01 PM To: Xin, Peixing <peixing....@windriver.com> Cc: Kyle Stanley <aeros...@gmail.com>; python-dev@python.org; Meng, Bin <bin.m...@windriver.com>; Duan, Kun <kun.d...@windriver.com> Subject: Re: [Python-Dev] Re: Pay for PR review and merging for VxWorks RTOS > Buildbot is also not a problem. The early issue from the core developer side, it would be helpful to review if the Buildbot is supported by Wind River for VxWorks. 2020년 8월 6일 (목) 오후 1:16, Xin, Peixing <peixing....@windriver.com>님이 작성: > > Hi, Stanley: > > > > Thanks for your comments. > > > > Almost all the patches are simple compatibility patch. But the subprocess > module is an exception. Like windows, VxWorks have no fork/exec API provided. > Instead, VxWorks uses rtpSpawn() to spawn a new process. So we have to > implement VxWorks’ own extension modules to support subprocess module. > However, this is not significant amount of codes, just around 500 lines of C > codes. Hopes any core dev could help to review and merge the simple > compatibility patches. If I can be granted the commit privileges, that will > be great. To ensure the quality, I will get the patches reviewed enough well > before merging. > > For long term support for VxWorks RTOS, I am an engineer from Wind River. > Wind River is willing to officially provide the support and I am willing to > be the maintainer. Buildbot is also not a problem. Once the patches have been > merging done, we will connect the buildbot for VxWorks. > > > > Thanks, > > Peixing > > > > From: Kyle Stanley <aeros...@gmail.com> > Sent: Thursday, August 6, 2020 9:27 AM > To: Xin, Peixing <peixing....@windriver.com> > Cc: python-dev@python.org; Meng, Bin <bin.m...@windriver.com> > Subject: Re: [Python-Dev] Pay for PR review and merging for VxWorks > RTOS > > > > What exactly does the PR involve? Is it a relatively simple compatibility > patch or something that adds significant amounts of platform-specific code? > The former can be reviewed (and potentially merged) by any core dev > knowledgeable in the areas being changed, but the latter requires long-term > support for the platform. > > > > In order to provide support for a new platform that we don't presently have > support for in CPython, it requires the following: > > > > 1) An existing core developer willing to provide long-term support for the > platform. Alternatively, someone else can be granted commit privileges, for > the purpose of maintaining that platform and fixing any issues that come up > in that CI that are specific to it. However, this is done on a case-by-case > basis, as it still requires a decent amount of trust with that individual. > > > > 2) A stable buildbot provided, to test against new changes made to CPython. > > > > The purpose of the above is to ensure that any substantial platform-specific > code added to CPython receives proper care; this is opposed to a large > addition of new code for a platform that has nobody to take care of it when > issues come up. Especially as a group of mostly volunteers (and those paid by > their employers to contribute), the latter wouldn't be sustainable. I > personally think it would be fantastic to have official support for real-time > OSs in CPython, but in this ecosystem, it requires being able to place trust > in someone that's willing and adequately proficient in the related areas to > provide long-term support for them. > > > > For more details, see PEP 11: > https://www.python.org/dev/peps/pep-0011/#supporting-platforms. > > > > > > On Wed, Aug 5, 2020 at 7:44 AM Xin, Peixing <peixing....@windriver.com> wrote: > > Hi, Python developers: > > > > Anyone interested in PR review and merging for VxWorks RTOS? We can give a > proper pay for that. Contact me if you have interest. > > > > Thanks, > > Peixing > > > > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org To unsubscribe send > an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/HA > TTYX3BWEIPVVUL7FMSNSCFYOBPS6OD/ Code of Conduct: > http://python.org/psf/codeofconduct/ > > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org To unsubscribe send > an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/TJ > M24KANKBKLQSFZIH42V4G4WLZ7MGO3/ Code of Conduct: > http://python.org/psf/codeofconduct/ -- Software Development Engineer at Kakao corp. Tel: +82 010-3353-9127 Email: donghee.n...@gmail.com | denn...@kakaocorp.com Linkedin: https://www.linkedin.com/in/dong-hee-na-2b713b49/ _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/OBMXWSVL7FGVLQGYYHHB4IONY54YVSO4/ Code of Conduct: http://python.org/psf/codeofconduct/
