Development Stats

C programming, build, interpreter/VM.
Target audience: MicroPython Developers.
Post Reply
pfalcon
Posts: 1155
Joined: Fri Feb 28, 2014 2:05 pm

Development Stats

Post by pfalcon » Fri Jan 16, 2015 4:31 pm

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.
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/

Damien
Site Admin
Posts: 647
Joined: Mon Dec 09, 2013 5:02 pm

Re: Development Stats

Post by Damien » Sun Jan 18, 2015 11:17 am

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

pfalcon
Posts: 1155
Joined: Fri Feb 28, 2014 2:05 pm

Re: Development Stats

Post by pfalcon » Sun Jan 18, 2015 12:50 pm

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 ;-).
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/

Damien
Site Admin
Posts: 647
Joined: Mon Dec 09, 2013 5:02 pm

Re: Development Stats

Post by Damien » Sun Jan 18, 2015 6:23 pm

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.

Post Reply