Re: State of micropython-lib?
Posted: Wed Feb 07, 2018 7:32 am
Hello everyone,
Thanks to those who raised their concerns over the recent forking of MicroPython and the library. I agree the current state is confusing and explanations are needed.
Without going into specifics, Paul (aka pfalcon) can oftentimes demonstrate inappropriate behaviour in discussions. For those who have been with the project for a while, and who participate actively on GitHub discussing PRs and issues, they will most likely have engaged with Paul at some point and understand the situation.
Paul's behaviour online reached a point towards the end of 2017 where, regretfully, I felt that he was doing more harm than good to the project. If you are interested you can read for example this post: https://mail.python.org/pipermail/pytho ... 50383.html
Not withstanding his contributions, and given his behaviour, I took the difficult decision to ask him to step down as maintainer of the project, and I eventually removed his push-rights to the main MicroPython repository.
I hope it is appreciated that we can discuss this sensitive issue in the open in a fair and reasonable way. That's the nature of true open source development: that not only the good but also the not-so-good events happen out in the open. Coming through such an event, MicroPython will be all the stronger for it.
To make it clear: https://micropython.org, https://forum.micropython.org, https://docs.micropython.org and https://store.micropython.org are all the official sites of The MicroPython Project and are run by the company George Robotics. The official source of the code is found at https://github.com/micropython/micropython which is the official master version. All PRs and issues should be directed to that repository
As for the libraries: https://github.com/micropython/micropython-lib will continue to be the location of the official libraries supported by the official master version of MicroPython. For PRs and issues associated with the libraries please use that repository.
As for libraries on PyPI: this will be sorted out shortly.
As for Paul's fork of MicroPython: if he insists to develop and promote his fork he should, as was already stated in this thread, rename it to something other than "MicroPython" in order to avoid confusion among users.
Let me also take this opportunity to again thank everyone who is involved with the project -- Paul included -- for their contributions big and small, whether it be participating on the forum, discussing things on GitHub, bringing MicroPython to a wider audience through outreach, or contributing code. I very much appreciate everything that is done and everyday I am amazed at how far MicroPython has come, and look forward to seeing it flourish as much as possible, in all manner of domains.
Damien.
Thanks to those who raised their concerns over the recent forking of MicroPython and the library. I agree the current state is confusing and explanations are needed.
Without going into specifics, Paul (aka pfalcon) can oftentimes demonstrate inappropriate behaviour in discussions. For those who have been with the project for a while, and who participate actively on GitHub discussing PRs and issues, they will most likely have engaged with Paul at some point and understand the situation.
Paul's behaviour online reached a point towards the end of 2017 where, regretfully, I felt that he was doing more harm than good to the project. If you are interested you can read for example this post: https://mail.python.org/pipermail/pytho ... 50383.html
Not withstanding his contributions, and given his behaviour, I took the difficult decision to ask him to step down as maintainer of the project, and I eventually removed his push-rights to the main MicroPython repository.
I hope it is appreciated that we can discuss this sensitive issue in the open in a fair and reasonable way. That's the nature of true open source development: that not only the good but also the not-so-good events happen out in the open. Coming through such an event, MicroPython will be all the stronger for it.
To make it clear: https://micropython.org, https://forum.micropython.org, https://docs.micropython.org and https://store.micropython.org are all the official sites of The MicroPython Project and are run by the company George Robotics. The official source of the code is found at https://github.com/micropython/micropython which is the official master version. All PRs and issues should be directed to that repository
As for the libraries: https://github.com/micropython/micropython-lib will continue to be the location of the official libraries supported by the official master version of MicroPython. For PRs and issues associated with the libraries please use that repository.
As for libraries on PyPI: this will be sorted out shortly.
As for Paul's fork of MicroPython: if he insists to develop and promote his fork he should, as was already stated in this thread, rename it to something other than "MicroPython" in order to avoid confusion among users.
Let me also take this opportunity to again thank everyone who is involved with the project -- Paul included -- for their contributions big and small, whether it be participating on the forum, discussing things on GitHub, bringing MicroPython to a wider audience through outreach, or contributing code. I very much appreciate everything that is done and everyday I am amazed at how far MicroPython has come, and look forward to seeing it flourish as much as possible, in all manner of domains.
Damien.