On Tue, Jan 21, 2014 at 01:42:34PM -0700, Luke Macken wrote: > On Fri, Dec 20, 2013 at 03:11:17PM +0100, Pierre-Yves Chibon wrote: > > So, what I would like to ask is: > > * what do you think of the project? Worth pursuing or not? > > Love it. Totally worth pursuing :) Cool, thanks :) > > * Where should it live? > > I'm all for keeping it distro-agnostic, but having a Powered by OpenShift > button on there couldn't hurt :P That's a nice idea but makes me wonder two things: - Can I run cron job on OpenShift? - If so and if we go the OpenShift way, we would need to figure out how to set-up fedmsg as the cron job sends fedmsg notifications > > * Domain name suggestions? (release-monitoring.org, cnucnu.org, cnucnuweb.org, > > <insert here you own idea>?) > > release-monitoring.org is decent, anything with the name cnucnu in it > will be confusing, but part of me thinks it should contain the word > upstream. > > Do you envision any sort of API for this? We've wanted to have an 'Upstream > Summary' section in the fedora-packages app for a while now. > https://fedoraproject.org/wiki/Fedora_Packager#Package_details_.3E_overview > So having an API that we could hit to get the SCM type/url and latest version > would be nice :) There is a little API already but it doesn't contain the SCM information present in the mockup. What could be added is the 'Lastest version upstream', I'll need to add a new endpoint providing the project information for the project name of a specified distro https://github.com/fedora-infra/cnucnuweb/blob/master/cnucnuweb/api.py > It also feels like cnucnu is the Right Place to house DOAP metadata ;) http://blog.pingoured.fr/index.php?post/2013/12/10/RDFa-with-rdflib%2C-python-and-cnucnu-web ;-) Cheers, Pierre _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure