Re: [gentoo-dev] [23]/3 API files
On 16 June 2013 02:21, Robin H. Johnson robb...@gentoo.org wrote: Special pages and contents http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml Since I am the one generating this one, I don't think it makes sense to move it into a git repo as it is. The script is actually pretty simple. The text from chapter 1 is always the same (ie cat header maintainer-needed.xml) and then I generate the list of packages using the portageq --maintainer-email=maintainer-nee...@gentoo.org -n output. So, in theory other developers never have to touch it unless they want to change the text of chapter 1. This rarely happens (I never changed it since day 0). But if you want to put it on a git repo, I need to rewrite it a bit because it is not pretty as it is. -- Regards, Markos Chandras - Gentoo Linux Developer http://dev.gentoo.org/~hwoarang
Re: [gentoo-dev] [23]/3 API files
On 22.06.2013 11:20, Markos Chandras wrote: On 16 June 2013 02:21, Robin H. Johnson robb...@gentoo.org wrote: Special pages and contents http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml Since I am the one generating this one, I don't think it makes sense to move it into a git repo as it is. The script is actually pretty simple. The text from chapter 1 is always the same (ie cat header maintainer-needed.xml) and then I generate the list of packages using the portageq --maintainer-email=maintainer-nee...@gentoo.org -n output. So, in theory other developers never have to touch it unless they want to change the text of chapter 1. This rarely happens (I never changed it since day 0). But if you want to put it on a git repo, I need to rewrite it a bit because it is not pretty as it is. That sounds like a page to have on qa-reports.g.o. When you're happy with the script quality, let infra know and we'll add it there. -- Regards, Markos Chandras - Gentoo Linux Developer http://dev.gentoo.org/~hwoarang -- Alex Legler a...@gentoo.org Gentoo Security/Ruby/Infrastructure signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [23]/3 API files
On Sun, Jun 16, 2013 at 02:08:00PM +0200, Alex Legler wrote: - Do you know of more? http://www.gentoo.org/proj/en/metastructure/herds/herds.xml Another one: http://www.gentoo.org/proj/en/devrel/roll-call/userinfo.xml This one and herds are somewhat important, as we really need them to be nicely visible on the website. -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
Re: [gentoo-dev] [23]/3 API files
On 16.06.2013 03:21, Robin H. Johnson wrote: Special pages and contents -- herds.xml, repositories.xml, etc.: As these are intended for other applications to use, these should go to a new site, possibly api.gentoo.org, initially fed from a git repository. This site should get backed by SSL. Here's a partial list of the ones I know about: http://www.gentoo.org/proj/en/overlays/repositories.xml http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml http://www.gentoo.org/main/en/mirrors3.xml Both of these are broken I think: http://www.gentoo.org/proj/en/perl/outdated-cpan-packages.xml http://www.gentoo.org/proj/en/perl/outdated-cpan-packages-perl-experimental.xml - Do you know of more? http://www.gentoo.org/proj/en/metastructure/herds/herds.xml - How can we better encourage these to move to an API site? Not sure what you mean with that. - Some of these are meant for human consumption, others are meant for tool consumption, should be differentiate? Human consumption - qa-reports.g.o Image resources: These can be uploaded to the Wiki. How can we ensure later that the media files don't get deleted? Deletion is restricted to administrators, mediawiki also keeps old versions around in case someone reuploads a file. To prevent even that, we can restrict editing certain assets to developers. Other files and downloads: Until proper project file hosting is implemented, again a simple git-backed static site, possibly projects.gentoo.org. Please don't put lots of binary files in Git. How do we expose that site to developers then? Akin to the mirroring system on d.g.o? -- Alex Legler a...@gentoo.org Gentoo Security/Ruby/Infrastructure signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [23]/3 API files
On Sun, Jun 16, 2013 at 02:08:00PM +0200, Alex Legler wrote: On 16.06.2013 03:21, Robin H. Johnson wrote: Special pages and contents -- herds.xml, repositories.xml, etc.: As these are intended for other applications to use, these should go to a new site, possibly api.gentoo.org, initially fed from a git repository. This site should get backed by SSL. Here's a partial list of the ones I know about: http://www.gentoo.org/proj/en/overlays/repositories.xml http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml http://www.gentoo.org/main/en/mirrors3.xml Both of these are broken I think: http://www.gentoo.org/proj/en/perl/outdated-cpan-packages.xml http://www.gentoo.org/proj/en/perl/outdated-cpan-packages-perl-experimental.xml - Do you know of more? http://www.gentoo.org/proj/en/metastructure/herds/herds.xml - How can we better encourage these to move to an API site? Not sure what you mean with that. It needs to be really easy for any developer to throw up a new data source w/ scripts onto the API site. Even qa-reports is somewhat stalled, and doesn't have good visibility, because it's not that easy for any dev to add something new to it. Image resources: These can be uploaded to the Wiki. How can we ensure later that the media files don't get deleted? Deletion is restricted to administrators, mediawiki also keeps old versions around in case someone reuploads a file. To prevent even that, we can restrict editing certain assets to developers. See my other comment about git-mediawiki maybe, that would satisfy my needs, just having old versions of the images around as needed (not admin-deletable). Other files and downloads: Until proper project file hosting is implemented, again a simple git-backed static site, possibly projects.gentoo.org. Please don't put lots of binary files in Git. How do we expose that site to developers then? Akin to the mirroring system on d.g.o? I need to dust off the project hosting proposal, because there are a lot of files that need to move to it (like all the elections PR materials). -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
Re: [gentoo-dev] [23]/3 API files
On 16.06.2013 21:44, Robin H. Johnson wrote: […] - How can we better encourage these to move to an API site? Not sure what you mean with that. It needs to be really easy for any developer to throw up a new data source w/ scripts onto the API site. Even qa-reports is somewhat stalled, and doesn't have good visibility, because it's not that easy for any dev to add something new to it. Currently, it's files in CVS, soon to be files in a Git. That's at least the same reachability as before. I think solving this problem is a separate task. Image resources: These can be uploaded to the Wiki. How can we ensure later that the media files don't get deleted? Deletion is restricted to administrators, mediawiki also keeps old versions around in case someone reuploads a file. To prevent even that, we can restrict editing certain assets to developers. See my other comment about git-mediawiki maybe, that would satisfy my needs, just having old versions of the images around as needed (not admin-deletable). Um, got a link for that extension? I didn't clarify, the Wiki can be configured to keep a revision even if someone deletes a file. Other files and downloads: Until proper project file hosting is implemented, again a simple git-backed static site, possibly projects.gentoo.org. Please don't put lots of binary files in Git. How do we expose that site to developers then? Akin to the mirroring system on d.g.o? I need to dust off the project hosting proposal, because there are a lot of files that need to move to it (like all the elections PR materials). …or that. -- Alex Legler a...@gentoo.org Gentoo Security/Ruby/Infrastructure signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [23]/3 API files
On 16/06/13 03:44 PM, Robin H. Johnson wrote: Image resources: These can be uploaded to the Wiki. How can we ensure later that the media files don't get deleted? Deletion is restricted to administrators, mediawiki also keeps old versions around in case someone reuploads a file. To prevent even that, we can restrict editing certain assets to developers. See my other comment about git-mediawiki maybe, that would satisfy my needs, just having old versions of the images around as needed (not admin-deletable). With modern MediaWiki, it is impossible to permanently remove a page or file without the system administrator (I mean SSH access, not MW sysop) intentionally permitting it or deleting the file archive. https://www.mediawiki.org/wiki/Manual:Image_administration#Undeleting_files https://www.mediawiki.org/wiki/Extension:Oversight https://www.mediawiki.org/wiki/Manual:RevisionDelete signature.asc Description: OpenPGP digital signature
[gentoo-dev] [23]/3 API files
Special pages and contents -- herds.xml, repositories.xml, etc.: As these are intended for other applications to use, these should go to a new site, possibly api.gentoo.org, initially fed from a git repository. This site should get backed by SSL. Here's a partial list of the ones I know about: http://www.gentoo.org/proj/en/overlays/repositories.xml http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml http://www.gentoo.org/main/en/mirrors3.xml Both of these are broken I think: http://www.gentoo.org/proj/en/perl/outdated-cpan-packages.xml http://www.gentoo.org/proj/en/perl/outdated-cpan-packages-perl-experimental.xml - Do you know of more? - How can we better encourage these to move to an API site? - Some of these are meant for human consumption, others are meant for tool consumption, should be differentiate? Image resources: These can be uploaded to the Wiki. How can we ensure later that the media files don't get deleted? Other files and downloads: Until proper project file hosting is implemented, again a simple git-backed static site, possibly projects.gentoo.org. Please don't put lots of binary files in Git. -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
