Hi all. I'm the developer for PackageKit and gnome-software. The community has already written an AppData file for Fedora, would you be interested to including it upstream? This will allow us to "feature" Inkscape on the front page in the future.
See http://people.freedesktop.org/~hughsient/appdata/ for more details about AppStream and AppData.
The file is here: https://raw.github.com/hughsie/fedora-appstream/master/appdata-extra/inkscap... but checking and perhaps needs some more filling in.
Thanks!
RIchard.
Hey Richard,
We do have a packaging directory for such things, but I'm unsure if you need the file in the root of the project's main repository. Or if you even need it in the same repository at all.
I'm also confused by the license tag. Is this the license for the appdata or the project code or the release?
Is there a donate url tag yet similar to the debian meta data? Any videos url can be included? And this is for packageKit and thus not just for fedora right? It'd be useful for any FDO that reads the meta data?
Speaking of which, we're not including the debian dir in trunk, which would indicate we're not putting packaging materials into trunk. I'll deffer on that to Bryce or others. Also upstream email to be chosen.
Thanks for writing us an appdata :-) much appreciated.
Martin,
On Fri, 2013-09-06 at 09:10 +0100, Richard Hughes wrote:
Hi all. I'm the developer for PackageKit and gnome-software. The community has already written an AppData file for Fedora, would you be interested to including it upstream? This will allow us to "feature" Inkscape on the front page in the future.
See http://people.freedesktop.org/~hughsient/appdata/ for more details about AppStream and AppData.
The file is here: https://raw.github.com/hughsie/fedora-appstream/master/appdata-extra/inkscap... but checking and perhaps needs some more filling in.
Thanks!
On 6 September 2013 12:27, Martin Owens <doctormo@...400...> wrote:
We do have a packaging directory for such things, but I'm unsure if you need the file in the root of the project's main repository. Or if you even need it in the same repository at all.
I don't need it anywhere special in the repo (or even in the same repo) it just has to be installed in /usr/share/appdata/ when the other files get installed.
I'm also confused by the license tag. Is this the license for the appdata or the project code or the release?
Just the AppData. CC0 ensures we can use it anywhere.
Is there a donate url tag yet similar to the debian meta data? Any videos url can be included? And this is for packageKit and thus not just for fedora right? It'd be useful for any FDO that reads the meta data?
It's useful to the desktop software center, so for now that gnome-software and potentially ubuntu software center. SuSE, Fedora and Ubuntu all ship AppStream metadata now. A donate URL is a good idea, as is videos, but for the first version I want to keep only the agreed on data here.
Also upstream email to be chosen.
When we extend the spec to include things like donate_url and videos, this is the email I'll use to contact the upstream projects. Most projects just chose the mailing list email as the contact data, which is fine as long as you can post without joining the mailing list.
Thanks!
Richard.
Thanks for reaching out Richard!
Maybe we should consider a more marketable description?
On Fri, Sep 6, 2013 at 9:39 PM, Richard Hughes <hughsient@...400...> wrote:
On 6 September 2013 12:27, Martin Owens <doctormo@...400...> wrote:
We do have a packaging directory for such things, but I'm unsure if you need the file in the root of the project's main repository. Or if you even need it in the same repository at all.
I don't need it anywhere special in the repo (or even in the same repo) it just has to be installed in /usr/share/appdata/ when the other files get installed.
I'm also confused by the license tag. Is this the license for the appdata or the project code or the release?
Just the AppData. CC0 ensures we can use it anywhere.
Is there a donate url tag yet similar to the debian meta data? Any videos url can be included? And this is for packageKit and thus not just for fedora right? It'd be useful for any FDO that reads the meta data?
It's useful to the desktop software center, so for now that gnome-software and potentially ubuntu software center. SuSE, Fedora and Ubuntu all ship AppStream metadata now. A donate URL is a good idea, as is videos, but for the first version I want to keep only the agreed on data here.
Also upstream email to be chosen.
When we extend the spec to include things like donate_url and videos, this is the email I'll use to contact the upstream projects. Most projects just chose the mailing list email as the contact data, which is fine as long as you can post without joining the mailing list.
Thanks!
Richard.
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 9 September 2013 01:22, Andy Fitzsimon <andrew@...420...> wrote:
Maybe we should consider a more marketable description?
It's completely up to you as a project. Just try to bear these points in mind: http://people.freedesktop.org/~hughsient/appdata/#description-format
Richard.
I just tried to merge it in, but I'm having trouble with the build system. I think it needs to go through the clean process to do translations and then go to the right directory as specified, but it's all voodoo and not making much sense.
Bryce or someone, are you guys around to do a quick automake update?
Martin,
On Mon, 2013-09-09 at 15:37 +0100, Richard Hughes wrote:
On 9 September 2013 01:22, Andy Fitzsimon <andrew@...420...> wrote:
Maybe we should consider a more marketable description?
It's completely up to you as a project. Just try to bear these points in mind: http://people.freedesktop.org/~hughsient/appdata/#description-format
Richard.
On Fri, Sep 06, 2013 at 07:27:33AM -0400, Martin Owens wrote:
Hey Richard,
We do have a packaging directory for such things, but I'm unsure if you need the file in the root of the project's main repository. Or if you even need it in the same repository at all.
I'm also confused by the license tag. Is this the license for the appdata or the project code or the release?
Is there a donate url tag yet similar to the debian meta data? Any videos url can be included? And this is for packageKit and thus not just for fedora right? It'd be useful for any FDO that reads the meta data?
Speaking of which, we're not including the debian dir in trunk, which would indicate we're not putting packaging materials into trunk. I'll deffer on that to Bryce or others. Also upstream email to be chosen.
AIUI, it's best practices to not include the debian dir in the upstream trunk, because it makes it easier for debian to maintain the dir in their own repositories if they need to add patches or whatnot.
Bryce
Thanks for writing us an appdata :-) much appreciated.
Martin,
On Fri, 2013-09-06 at 09:10 +0100, Richard Hughes wrote:
Hi all. I'm the developer for PackageKit and gnome-software. The community has already written an AppData file for Fedora, would you be interested to including it upstream? This will allow us to "feature" Inkscape on the front page in the future.
See http://people.freedesktop.org/~hughsient/appdata/ for more details about AppStream and AppData.
The file is here: https://raw.github.com/hughsie/fedora-appstream/master/appdata-extra/inkscap... but checking and perhaps needs some more filling in.
Thanks!
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Fri, 2013-09-20 at 10:22 -0700, Bryce Harrington wrote:
AIUI, it's best practices to not include the debian dir in the upstream trunk, because it makes it easier for debian to maintain the dir in their own repositories if they need to add patches or whatnot.
The argument is that this meta data IS NOT packaging materials and is instead a way for upstreams to specify certain things in a standard way for FDO deployments.
The debian comparison I made was a little hasty.
Martin,
participants (4)
-
Andy Fitzsimon -
Bryce Harrington -
Martin Owens -
Richard Hughes