There're lot of sites nowadays offering project development stats, starting with Github itself:
3rd-party sites are however found and then forgotten, so I'd like to collect them here for future reference.
Development Stats
Development Stats
Awesome MicroPython list
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Re: Development Stats
Apparently it's possible to get badges from issuestats and use them in the README.md, like the travis "build passing" badge.
http://www.issuestats.com/github/microp ... style=flat
http://www.issuestats.com/github/microp ... style=flat
http://www.issuestats.com/github/microp ... style=flat
http://www.issuestats.com/github/microp ... style=flat
Re: Development Stats
Yes, that's how I found it. Numbers don't look that bad to show off, but I wonder if that would put pressure to close long-standing issues rather then let them hang as reminders
.
![Wink ;-)](./images/smilies/icon_e_wink.gif)
Awesome MicroPython list
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Re: Development Stats
Right. It's easy to artificially enhance the numbers with false issues. And the last thing we want is undue pressure to fix things fast. upy requires crafting, which takes time.