Doap file

This explanation is lifted from Wikipedia. It was created and initially developed by Edd Dumbill to convey semantic information associated with open source software projects.

It is currently used in the Mozilla Foundation's project page and in several other software repositories, notably the Python Package Index. Defaults to "doap. Set this to the empty string to disable XML output. For example, if your project is called gnome-foo , create a gnome-foo. GNOME Shell takes advantage of the capabilities of modern graphics hardware and introduces innovative user interface concepts to provide a visually attractive and easy to use experience.

Tarball releases are provided largely for distributions to build packages. If your project does not belong in one of these categories, leave the category element out, and your repository will appear under the "Other" heading in cgit. We use this e. I'm doing my first code contribution to GNOME, when I "git push", I get "fatal: the remote end hung up unexpectedly" To push patches direct to a code repository you must have commit access and a Git account.

This repository has been archived by the owner. It is now read-only. Star 1. What to do with the DOAP file? Labels Linux Rebranding Refactoring. Milestone 0.

Copy link. Parts of its properties are reused in this specification, where DOAP was lacking namely for the logo, screenshot and documentation properties. AppStream was also considered, but it lacks the extensibility and existing tooling of RDF, while being limited to being a description for software installers instead of a generic software description.

Permission is hereby granted, free of charge, to any person obtaining a copy of this specification the "Specification" , to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification.

Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. In no event and under no legal theory, whether in tort including negligence , contract, or otherwise, unless required by applicable law such as deliberate and grossly negligent acts or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses , even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself. Discussion on other xmpp.

Abstract This specification defines how XMPP projects can provide a machine-readable description of their abilities, and how external entities can interact with it.