Dear Arjun, Just quickly (I'm online for a very short time) I'm listing some of the potential next steps (in no particular order), I hope that Umesh will also comment on it:
(1) It would probably be time for a thorough code review. It's a bit tricky to do code reviews on your personal repository. What we could do (I would be grateful if someone from the infrastructure team could help a bit) is create a new empty temporary repository inside the MacPorts organisation (but without subscribing everyone with commit access), maybe with an initial commit, and then let you make a pull request to that one, while we would do code review until the code is in "perfect shape". (2) You made a simple PR last time to fix portindex2json for a more reasonable output of categories. Would you be willing for a tiny bit more difficult task and try to improve the output for maintainers as well? We would want a list of all maintainers with two optional keys for each (email & github handle) plus a boolean value to tell whether the port is under openmaintainer policy. (3) The author of portindex2json asked if we could generate the json file on our infrastructure. Maybe you could explore how our buildbot infrastructure works and create a PR or two to allow automatically generating json output along with PortIndex on our buildbot. Others might be able to help with more information if I'm offline. (I left a tiny bit of info last time.) (4) Umesh might point you to his past attempt to create such an application. You could review how it was done and try to start working on accepting installation statistics. (5) Think about how to keep the build logs up to date. Mojca