After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 657920 - Add Grilo documentation
Add Grilo documentation
Status: RESOLVED FIXED
Product: website
Classification: Infrastructure
Component: help.gnome.org
current
Other Linux
: Normal normal
: ---
Assigned To: GNOME Web maintainers
GNOME Web maintainers
Depends on:
Blocks:
 
 
Reported: 2011-09-01 12:06 UTC by Juan A. Suarez Romero
Modified: 2011-09-05 15:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
New pre-release of Grilo (481.28 KB, application/octet-stream)
2011-09-05 10:31 UTC, Juan A. Suarez Romero
Details

Description Juan A. Suarez Romero 2011-09-01 12:06:37 UTC
We have done several Grilo releases, a framework to get access to multimedia content, both on-line and off-line, that it is used by Totem and Media-Explorer.

But so far we never put the documentation online, so people wanting to inspect it must build it themselves.

Could you please add the documentation to library.gnome.org, so it is accessible from the web?

Grilo is available at http://ftp.gnome.org/pub/GNOME/sources/grilo/0.1/
Comment 1 Frederic Peters 2011-09-03 09:30:48 UTC
Could you pick a category for grilo in the right column of http://developer.gnome.org/references and provide a short summary (two lines is fine)?
Comment 2 Juan A. Suarez Romero 2011-09-05 06:41:24 UTC
I'd say it fits better in Multimedia category.

About Grilo,

"Grilo is a framework that provides access to different sources of multimedia content, using a pluggable system."

A bit longer description:

"Grilo is a framework focused on making media discovery and browsing easy for application developers.

More precisely, Grilo provides:

- A single, high-level API that abstracts the differences among various media content providers, allowing application developers to integrate content from various services and sources easily.
- A collection of plugins for accessing content from various media providers. Developers can share efforts and code by writing plugins for the framework that are application agnostic.
- A flexible API that allows plugin developers to write plugins of various kinds."
Comment 3 Frederic Peters 2011-09-05 07:28:35 UTC
What about grilo-libs? (developer.gnome.org will have two entries, as there are two documents in grilo sources)

(I don't know if it makes sense from a technical point of view, but from a documentation perspective I think it would be better to have a single document.)
Comment 4 Juan A. Suarez Romero 2011-09-05 07:42:15 UTC
Good question.

Grilo-libs was kept separated because, though included in the Grilo core, it is not an essential part of it, but a library of utilities that plugins (or developers) can choose to use.

I think you're right, I don't like very much neither to have two separated entries in developer.g.o

I'll take care of this, and I'll come with a solution.
Comment 5 Juan A. Suarez Romero 2011-09-05 10:31:38 UTC
Created attachment 195679 [details]
New pre-release of Grilo

I'm preparing the next Grilo release, 0.1.17.

I've merged grilo-libs documentation into main documentation, so now there is only one document.

Attached is the pre-release version.

Can you check if everything you need to close this bug is already fine in that version?

If so, then I'll make the real release.
Comment 6 Frederic Peters 2011-09-05 10:52:09 UTC
Looks ok, I'll wait for that version to be installed and push the required library-web change (I'll monitor ftp-release-list, no need to ping me).  Thanks for your quick reaction!
Comment 7 Juan A. Suarez Romero 2011-09-05 15:05:47 UTC
Done. 

I've made the release and pushed to download.gnome.org
Comment 8 Frederic Peters 2011-09-05 15:43:05 UTC
And it's now published, http://developer.gnome.org/grilo/unstable/