Hello! Olivier Dion <[email protected]> skribis:
> I don't think we need Cuirass for this. We only need to poll a git > source of Guile for changes. Then we can list all commits sinces last > poll and generate metrics for each of them (we could put some heuristics > to avoid generating metrics when only documentation changes are made). > > From there, we can generate Guix profiles and run some scripts in them > to gather the needed metrics. Finally, put all of that in a DB and > share it to a web-server. Yes, sounds like a plan. The data collection, database maintenance, and visualization part quickly goes more complex than one would think, so it might make sense for this to go to an existing tool. [...] >> I would suggest asking Guix Foundation > > Is there an official channel for this? You can email [email protected] (public mailing list). >> for a dedicated machine to do that. It doesn’t need to be powerful or >> anything; it just needs to be stable and kept around long enough (a >> few years at least). There are even laptops that were donated to Guix >> Foundation that would be good enough for the job. > > It does not need to be very powerful indeed. The important factors here > are the heat and the battery. If the laptop is heating too much, the > results will be skewed due to hardware trottling. Same goes if the > battery is too low. Right. > Also, who is going to maintain that hardware? That’s always the tricky part. The other option is to rent a small VPS, but that gives less control on the setup. Perhaps it’s good enough though? Ludo’.
