Re: Correct .doap file syntax for the name tag
On Wed, Aug 21, 2013 at 12:15:32AM +0200, Andrea Veri wrote: 2. many other scripts are relying on name matching the exact repository-name. Which ones? No script that I am aware of uses this to figure out the repository name. It uses https://git.gnome.org/repositories.doap, and that contains the real repository name. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the name tag
Thanks a lot David for working on this, the patch has been tested and was included into the relevant script. cheers, Andrea 2013/8/22 David King amigad...@amigadave.com On 2013-08-20 21:23, Shaun McCance sha...@gnome.org wrote: On Wed, 2013-08-21 at 00:15 +0200, Andrea Veri wrote: I noticed that many repositories are not using the name tag correctly into the respective .doap files. The name tag should possibly match the repository name (i.e gnome-shell.git -- gnome-shell, gnome-user-docs.git -- gnome-user-docs) for two main reasons: That's not how the rest of the world uses the name property. If you want the location of the repository, that's what the location property of the Repository class is for. Or use a custom property in our DOAP extension namespace. I just made a change to add the repository information to the Cheese DOAP file: https://git.gnome.org/browse/**cheese/commit/?id=** ba6f9e564cc828d197bf89a7d71e7e**a697fb3132https://git.gnome.org/browse/cheese/commit/?id=ba6f9e564cc828d197bf89a7d71e7ea697fb3132 It is a few more lines than using the name property, but has the benefit that other public clones of the repository have the upstream git location included. Looking at the mirror script, it seems that using the DOAP name property for the repository name can be avoided entirely. I filed a bug about this, with a patch: https://bugzilla.gnome.org/**show_bug.cgi?id=706562https://bugzilla.gnome.org/show_bug.cgi?id=706562 -- http://amigadave.com/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the name tag
On Wed, Aug 21, 2013 at 10:48:11AM +0200, Olav Vitters wrote: On Wed, Aug 21, 2013 at 12:15:32AM +0200, Andrea Veri wrote: 2. many other scripts are relying on name matching the exact repository-name. Which ones? No script that I am aware of uses this to figure out the repository name. It uses https://git.gnome.org/repositories.doap, and that contains the real repository name. Now that David's patch [1] has been applied, is the requirement of having the name tag match the repository name still valid? Particularly if I add GitRepository to my modules's DOAP? Cheers, Debarshi [1] https://bugzilla.gnome.org/show_bug.cgi?id=706562 -- Life is like bein' on a mule team. Unless you're the lead mule, all the scenery looks about the same. pgpEo11N6l69l.pgp Description: PGP signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the name tag
No, sorry for not pointing that out on my previous email, you can use a name tag of your choice but it would be simply awesome to have all the GitRepositories tags in place. cheers, 2013/8/22 Debarshi Ray rishi...@lostca.se On Wed, Aug 21, 2013 at 10:48:11AM +0200, Olav Vitters wrote: On Wed, Aug 21, 2013 at 12:15:32AM +0200, Andrea Veri wrote: 2. many other scripts are relying on name matching the exact repository-name. Which ones? No script that I am aware of uses this to figure out the repository name. It uses https://git.gnome.org/repositories.doap, and that contains the real repository name. Now that David's patch [1] has been applied, is the requirement of having the name tag match the repository name still valid? Particularly if I add GitRepository to my modules's DOAP? Cheers, Debarshi [1] https://bugzilla.gnome.org/show_bug.cgi?id=706562 -- Life is like bein' on a mule team. Unless you're the lead mule, all the scenery looks about the same. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the name tag
On Thu, Aug 22, 2013 at 12:28:43PM +0200, Andrea Veri wrote: No, sorry for not pointing that out on my previous email, you can use a name tag of your choice but it would be simply awesome to have all the GitRepositories tags in place. GitRepositories is really not needed. A script adds that, there is no need to add such information IMO. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the name tag
On 2013-08-22 12:49, Olav Vitters o...@vitters.nl wrote: On Thu, Aug 22, 2013 at 12:28:43PM +0200, Andrea Veri wrote: No, sorry for not pointing that out on my previous email, you can use a name tag of your choice but it would be simply awesome to have all the GitRepositories tags in place. GitRepositories is really not needed. A script adds that, there is no need to add such information IMO. The build-repo-list script adds the GitRepository property to the DOAP file at https://git.gnome.org/repositories.doap but does not add the same information to the DOAP file in each repository. I think that the DOAP files in each repository should be the canonical source of project metadata, so that moving the injected data from repositories.doap to individual modules should be a goal. This has the (slight) benefit that public clones of the repository will then contain the upstream location of the source. However, it is a minor thing, and the current mirror script works without it. None of the current sysadmin scripts use the GitRepository property, other than injecting it into repositories.doap. -- http://amigadave.com/ signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the name tag
On Thu, Aug 22, 2013 at 12:11:11PM +0100, David King wrote: However, it is a minor thing, and the current mirror script works without it. None of the current sysadmin scripts use the GitRepository property, other than injecting it into repositories.doap. You missed handle-ldap-modules. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the name tag
On Thu, Aug 22, 2013 at 1:28 PM, Andrea Veri a...@gnome.org wrote: No, sorry for not pointing that out on my previous email, you can use a name tag of your choice but it would be simply awesome to have all the GitRepositories tags in place. Would be nice if you revert your relevant commits to repositories now :) -- Regards, Zeeshan Ali (Khattak) FSF member#5124 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.9.90 release
Hi, the first beta release of the GNOME 3.9 development cycle is here! With the 3.9.90 release, most of our feature work for 3.10 is wrapping up and we're heading into the the Freeze [1]: - UI Freeze: No UI changes should be made without prior consulting the release team and notification to gnome-doc-l...@gnome.org - Feature Freeze: new functionality is implemented now, for exceptions please again consult the release team - API/ABI Freeze for 3.9: Developer APIs should be frozen at this point; - String Change Announcement Period: All string changes should be announced to both gnome-i...@gnome.org and gnome-doc-l...@gnome.org. More details about changes and news for this beta are available here: core: http://download.gnome.org/core/3.9/3.9.90/NEWS apps: http://download.gnome.org/apps/3.9/3.9.90/NEWS The GNOME 3.9.90 release itself is available here: core sources: http://download.gnome.org/core/3.9/3.9.90/ apps sources: http://download.gnome.org/apps/3.9/3.9.90/ JHBuild modulesets to compile GNOME 3.9.90 by hand are available here http://download.gnome.org/teams/releng/3.9.90/ Check the Smoketesting documentation [2] for instructions about how to compile and test GNOME with these modulesets. WARNING! WARNING! WARNING! -- This release is a snapshot of development code. Although it is buildable and usable, it is primarily intended for testing and hacking purposes. GNOME uses odd minor version numbers to indicate development status. For more information about 3.10, the full schedule, the official module lists and the proposed module lists, please see our colourful 3.10 page: http://www.gnome.org/start/unstable For a quick overview of the GNOME schedule, please see: http://live.gnome.org/Schedule [1] https://live.gnome.org/ReleasePlanning/Freezes [2] https://live.gnome.org/Smoketesting -- Matthias Clasen GNOME Release Team ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
