Commit 941c1496 authored by Davyd Madeley's avatar Davyd Madeley

Add a DOAP file for the release notes

parent aa0949c2
<Project xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:gnome="http://api.gnome.org/doap-extensions#"
xmlns="http://usefulinc.com/ns/doap#">
<!--
This is a DOAP template file. It contains Pulse's best guesses at
some basic content. You should verify the information in this file
and modify anything that isn't right. Add the corrected file to your
source code repository to help tools better understand your project.
-->
<name xml:lang="en">release-notes</name>
<shortdesc xml:lang="en">Release Notes for GNOME Releases</shortdesc>
<homepage rdf:resource="http://library.gnome.org/misc/release-notes/" />
<mailing-list rdf:resource="http://mail.gnome.org/mailman/listinfo/roadmap-list" />
<download-page rdf:resource="http://download.gnome.org/sources/release-notes/" />
<bug-database rdf:resource="http://bugzilla.gnome.org/browse.cgi?product=release-notes" />
<!-- DOAP category: This is used to categorize repositories in cgit.
Pulse has taken its best guess at the correct category. You may
want to replace the rdf:resource attribute with one of the following:
http://api.gnome.org/doap-extensions#admin
http://api.gnome.org/doap-extensions#bindings
http://api.gnome.org/doap-extensions#deprecated
http://api.gnome.org/doap-extensions#desktop
http://api.gnome.org/doap-extensions#development
http://api.gnome.org/doap-extensions#infrastructure
http://api.gnome.org/doap-extensions#platform
http://api.gnome.org/doap-extensions#productivity
NOTE: There is an "Other" categorization on cgit, but we do not have a
DOAP category for it. If your module does not belong to one of these
groups, then do not include a category property in your DOAP file.
-->
<category rdf:resource="http://api.gnome.org/doap-extensions#infrastructure" />
</Project>
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment