8000 ANNOUNCEMENT: Clearing the backlog · Issue #2602 · micropython/micropython · GitHub
[go: up one dir, main page]
Skip to content

ANNOUNCEMENT: Clearing the backlog #2602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
dpgeorge opened this issue Nov 6, 2016 · 2 comments
Closed

ANNOUNCEMENT: Clearing the backlog #2602

dpgeorge opened this issue Nov 6, 2016 · 2 comments

Comments

@dpgeorge
Copy link
Member
dpgeorge commented Nov 6, 2016

Hello all.

MicroPython has grown into a piece of software that is used by many people in many different systems for many different purposes. There are also lots of people who have contributed to the project in various ways, not only through code. This is fantastic and is what open source is all about.

But, with such a large scope, the maintenance of the code and managing of the community and their contributions has reached a point where it takes more time than is available. There are currently 2 core developers/maintainers of this project (@pfalcon and myself, @dpgeorge) and we have become overwhelmed by the volume of work. The number of issues and pull-requests grows faster than we can deal with them.

To get back on top of things we have decided that for the next few months (at least until start of 2017) we will focus primarily on:

  1. reducing technical debt and making things more efficient to maintain;
  2. addressing existing issues and PRs to clear the backlog;
  3. finalising the machine API and improving documentation;
  4. working through the ESP8266 Kickstarter stretch goals.

As such, any new issues or PRs opened after this one may take a while to be reviewed and responded to until we have dealt with the backlog. We will try to process new bugs and security issues for the Python core and active ports, so please do file bug reports if you have found something.

This issue is not meant to discourage submission of new bugs or patches but rather gives an update on the current state of the project and plans for moving forward. As usual, contributions for items in #1331 are always welcome.

Thanks for your understanding!
@prusnak
Copy link
Contributor
prusnak commented Nov 8, 2016

Is there a way how other people can help you with the project and its backlog so you don't feel overwhelmed?
AC34

This was referenced Nov 11, 2016
Closed
Closed
@peterhinch peterhinch mentioned this issue Nov 27, 2016
Closed
@dpgeorge dpgeorge mentioned this issue Jan 16, 2017
Closed
@SpotlightKid SpotlightKid mentioned this issue Mar 17, 2017
Closed
@dpgeorge
Copy link
Member Author
dpgeorge commented Jun 9, 2020

There's still a backlog, but I don't think it's helping to keep this issue open, so closing.

@dpgeorge dpgeorge closed this as completed Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@prusnak @pfalcon @dpgeorge
0