You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub has a nice bar graph showing the Ruffle repo's commit history: https://github.com/ruffle-rs/ruffle/graphs/commit-activity
In my opinion, this bar graph more accurately reflects the project progress and activity than the AVM1 and AVM2 progress bars. It shows that things are consistently being accomplished every week as code is committed.
I'd like to see a version of this bar graph along the bottom of the "Compatibility" section of the Ruffle website. Hopefully it can be nicely styled, similarly to the progress bars (but the bars would be vertical, not horizontal).
The data can be requested straight from GitHub's API using this URL: https://api.github.com/repos/ruffle-rs/ruffle/stats/commit_activity
In that data, the "week" value is a Unix epoch giving the start date of the week, and "total" is the number of commits during that week.
The text was updated successfully, but these errors were encountered:
GitHub has a nice bar graph showing the Ruffle repo's commit history: https://github.com/ruffle-rs/ruffle/graphs/commit-activity

In my opinion, this bar graph more accurately reflects the project progress and activity than the AVM1 and AVM2 progress bars. It shows that things are consistently being accomplished every week as code is committed.
I'd like to see a version of this bar graph along the bottom of the "Compatibility" section of the Ruffle website. Hopefully it can be nicely styled, similarly to the progress bars (but the bars would be vertical, not horizontal).
The data can be requested straight from GitHub's API using this URL: https://api.github.com/repos/ruffle-rs/ruffle/stats/commit_activity
In that data, the "week" value is a Unix epoch giving the start date of the week, and "total" is the number of commits during that week.
The text was updated successfully, but these errors were encountered: