Mojca Miklavec

> Here is my user feedback on the web app Amazing, thank you very much for the very detailed feedback. > running OSX 10.8.5 that is old by now, I...

I would say that thes explanations and testimonials would be really beneficial, but they belongs to the main page, not necessarily to the "here's statistics" page, but just to answer...

@dmitriz: would you be willing to take another look at http://macports.silentfox.tech/ (the URL might change soon) and open a new ticket or tickets with whatever you still feel would be...

I suggested something different, but your proposal is better. Potentially call it `os_arch_id` to make it more explicit that it's not just about OS version (even though I'm not 100%...

Should the newly set up builders usually be automatically picked up? (I don't see anything for the new builders being picked up yet.)

How did you do the first run populating the builders? In principle you could get the info from API like https://build.macports.org/json/builders?as_text=1 (which would change and become more intuitive with buildbot...

> While trying to implement this I felt that the `display_name` field might remove the need of the `os_arch_id`. I mean, `display_name` would be same for `10.8_x86_64` and `10.8_x86_64_legacy`, then...

The new builders for 10.6-10.8 have already been added, however: * @ryandesign has disabled the workers (until a bunch of binary archives are cleaned up, and maybe other issues) *...

I believe that the main of this ticket has been resolved, but a few other fronts remain open that might warrant opening a new ticket. Like: 1. automatically detecting a...

Not sure if this qualifies as a bug or as a feature ... I added a `bug` label for now.