Dear all,
As you may know, over the last few weeks I have been working on a small project called (for the moment) cnucnu web. You can already see it in place at: http://209.132.184.188/cnucnu/
The idea is to provide a web-interface to the release monitoring script that is being run for the moment via the wiki: http://fedoraproject.org/wiki/Upstream_release_monitoring
So this web-application replaces the wiki page, allows mapping of projects into linux distributions and anyone with an OpenID account can contribute to it. On the back, there is a cron job that runs, check for new version of the project with the information provided and send a message on fedmsg for every new version found.
The idea is to host the project on the Fedora infrastructure but, I would prefer not have it under the fedoraproject.org name as I see it as a broader project than just for Fedora: Debian, Ubuntu, Arch, Slack, Suse, we all can benefit from this.
I also would like to have it broadcast messages on the debian version of fedmsg (I'm already in contact with Olsad for this).
So, what I would like to ask is: * what do you think of the project? Worth pursuing or not? * Where should it live? * Domain name suggestions? (release-monitoring.org, cnucnu.org, cnucnuweb.org, <insert here you own idea>?)
So if we agree to get it up and running, I foresee few steps: * Check with legal if there are any limitations (ie: can we put non-FOSS projects in there?) * Get the domain name * Update the UI: we already have a design but I think it could be made nicer (especially the front page) -- Any volunteers? * Deploy it and see w/ Debian how to have it send messages onto their bus * Set the DNS to point to the website
I will start the first step now already.
Thoughts?
Pierre
On Fri, Dec 20, 2013 at 10:11 PM, Pierre-Yves Chibon pingou@pingoured.fr wrote:
Dear all,
As you may know, over the last few weeks I have been working on a small project called (for the moment) cnucnu web. You can already see it in place at: http://209.132.184.188/cnucnu/
[cut]
So, what I would like to ask is:
- what do you think of the project? Worth pursuing or not?
Really really nice and helpful for tracking. Thanks.
- Where should it live?
- Domain name suggestions? (release-monitoring.org, cnucnu.org, cnucnuweb.org,
<insert here you own idea>?)
releases-monitoring.org maybe the best among these three. I think some guys may already know ROSA's ABI tracker and use it for comparing ABI/API differences. http://upstream-tracker.org. It's free and open for all users without OS limitation. And users can know its usage from the name quickly.
So if we agree to get it up and running, I foresee few steps:
- Check with legal if there are any limitations (ie: can we put non-FOSS projects
in there?)
This depends on which operating system does the user choose.
--
Yours sincerely, Christopher Meng
Noob here.
On Sat, Dec 21, 2013 at 11:36:54AM +0800, Christopher Meng wrote:
On Fri, Dec 20, 2013 at 10:11 PM, Pierre-Yves Chibon pingou@pingoured.fr wrote:
- Domain name suggestions? (release-monitoring.org, cnucnu.org, cnucnuweb.org,
<insert here you own idea>?)
releases-monitoring.org maybe the best among these three. I think some guys may already know ROSA's ABI tracker and use it for comparing ABI/API differences. http://upstream-tracker.org. It's free and open for all users without OS limitation. And users can know its usage from the name quickly.
Any other vote for the domain name? :)
Pierre
HI
On Mon, Jan 20, 2014 at 9:38 AM, Pierre-Yves Chibon wrote:
On Sat, Dec 21, 2013 at 11:36:54AM +0800, Christopher Meng wrote:
On Fri, Dec 20, 2013 at 10:11 PM, Pierre-Yves Chibon pingou@pingoured.fr wrote:
- Domain name suggestions? (release-monitoring.org, cnucnu.org,
cnucnuweb.org,
<insert here you own idea>?)
releases-monitoring.org maybe the best among these three. I think some guys may already know ROSA's ABI tracker and use it for comparing ABI/API differences. http://upstream-tracker.org. It's free and open for all users without OS limitation. And users can know its usage from the name quickly.
Any other vote for the domain name? :)
FWIW, I am for release-monitoring.org as well
Rahul
On Mon, Jan 20, 2014 at 02:16:25PM -0500, Rahul Sundaram wrote:
On Mon, Jan 20, 2014 at 9:38 AM, Pierre-Yves Chibon wrote:
On Sat, Dec 21, 2013 at 11:36:54AM +0800, Christopher Meng wrote:
On Fri, Dec 20, 2013 at 10:11 PM, Pierre-Yves Chibon pingou@pingoured.fr wrote:
- Domain name suggestions? (release-monitoring.org, cnucnu.org,
cnucnuweb.org,
<insert here you own idea>?)
releases-monitoring.org maybe the best among these three. I think some guys may already know ROSA's ABI tracker and use it for comparing ABI/API differences. http://upstream-tracker.org. It's free and open for all users without OS limitation. And users can know its usage from the name quickly.
Any other vote for the domain name? :)
FWIW, I am for release-monitoring.org as well
That domain name seems in tune with the purpose, +1.
On Mon, Jan 20, 2014 at 04:41:11PM -0500, Paul W. Frields wrote:
On Mon, Jan 20, 2014 at 02:16:25PM -0500, Rahul Sundaram wrote:
On Mon, Jan 20, 2014 at 9:38 AM, Pierre-Yves Chibon wrote:
On Sat, Dec 21, 2013 at 11:36:54AM +0800, Christopher Meng wrote:
On Fri, Dec 20, 2013 at 10:11 PM, Pierre-Yves Chibon pingou@pingoured.fr wrote:
- Domain name suggestions? (release-monitoring.org, cnucnu.org,
cnucnuweb.org,
<insert here you own idea>?)
releases-monitoring.org maybe the best among these three. I think some guys may already know ROSA's ABI tracker and use it for comparing ABI/API differences. http://upstream-tracker.org. It's free and open for all users without OS limitation. And users can know its usage from the name quickly.
Any other vote for the domain name? :)
FWIW, I am for release-monitoring.org as well
That domain name seems in tune with the purpose, +1.
Ok, so as soon as I have an response from legal I will see if we can get it :)
Thanks to all! Pierre
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?
Even if it is only used by Fedora it is good to get away from the wiki page. I always planned to add some more features that require a more information per package, e.g. getting automatic changelog details for new packages.
So if we agree to get it up and running, I foresee few steps:
- Check with legal if there are any limitations (ie: can we put non-FOSS projects
in there?)
It is not only non-FOSS software but also about software with patents that might be problematic.
Regards Till
On Sat, Dec 21, 2013 at 09:50:16AM +0100, Till Maas 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?
Even if it is only used by Fedora it is good to get away from the wiki page. I always planned to add some more features that require a more information per package, e.g. getting automatic changelog details for new packages.
I guess you're thinking of upstream's changelog from an eventual `CHANGELOG` file in the upstream sources?
I've been thinking of cnucnu as the back-end library while cnucnu-web is just the interface, so if you like to add more feature, I'm all for it :)
So if we agree to get it up and running, I foresee few steps:
- Check with legal if there are any limitations (ie: can we put non-FOSS projects
in there?)
It is not only non-FOSS software but also about software with patents that might be problematic.
I have asked spot about this.
Pierre
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 :)
- 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
- 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 :)
It also feels like cnucnu is the Right Place to house DOAP metadata ;)
luke
On Jan 22, 2014 4:42 AM, "Luke Macken" lmacken@redhat.com wrote:
- 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.
Or upstream-monitoring.org?
Similar to upstream-tracker.org and nice as well.
On Wed, Jan 22, 2014 at 09:06:57AM +0800, Christopher Meng wrote:
On Jan 22, 2014 4:42 AM, "Luke Macken" lmacken@redhat.com wrote:
- 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.
Or upstream-monitoring.org?
Similar to upstream-tracker.org and nice as well.
This also popped-up when we discussed it on #fedora-devel a while ago but the outcome (iirc) was that `upstream` might be too `downstream` (clear right? :)), in other word, `upstream` might refer too much to the Fedora or Linux environment, I do not know if other Linux distribution also use this word. release-monitoring is likely less confusing for people outside our environment (I'm thinking of perl or python developer that runs Mac, not sure they know they are upstream).
Thoughts? Pierre
On Jan 21, 2014 2:42 PM, "Luke Macken" lmacken@redhat.com 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 :)
- 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
+11
-AdamM
- 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 :)
It also feels like cnucnu is the Right Place to house DOAP metadata ;)
luke _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
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-pytho... ;-)
Cheers, Pierre
On Wed, Jan 22, 2014 at 09:30:59AM +0100, Pierre-Yves Chibon wrote:
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:
- 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?
Yep! https://www.openshift.com/blogs/getting-started-with-cron-jobs-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
I think that should work just fine, but Ralph would know for sure. You'll probably need to point it at a config for your endpoints, since /etc/fedmsg.d won't exist.
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-pytho... ;-)
Excellent!
luke
On Wed, Jan 22, 2014 at 09:51:00AM -0700, Luke Macken wrote:
On Wed, Jan 22, 2014 at 09:30:59AM +0100, Pierre-Yves Chibon wrote:
- 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
I think that should work just fine, but Ralph would know for sure. You'll probably need to point it at a config for your endpoints, since /etc/fedmsg.d won't exist.
We'd need a static IP that we allow in with iptables. That's the only tricky part I can think of. (We can put the config in $(pwd)/fedmsg.d/ to point it at our inbound relay)
infrastructure@lists.fedoraproject.org
-
Adam Miller -
Christopher Meng -
Luke Macken -
Paul W. Frields -
Pierre-Yves Chibon -
Rahul Sundaram -
Ralph Bean -
Till Maas