[gst-devel] GStreamer embedded mailing list proposal

[Zhao Liang-E3423C]

By my personal  opinion, I think discussing embedded device issues by a
separate maillist is convenient  and effective way to collect and
accelerate the gstreamer using on embedded device.
I believe there are many developers on gst community who are working on
embedded device, but many issues we meet are not same with desktop, for
example, memory usage, the embedded device alway has small memory, so
how to reduce resource usage is a painful issue for us. Another example
is DSP, many embedded devices use DSP as their decoder or sink, but we
could not find the whole solution for dsp on gstreamer. Gst performance
is also an issue for us, how to reduce gstreamer lib size and runtime
cost, how to reduce gstreamer dependency libs, they alway puzzle us.

So I think we need a place to discuss these issues.

Best Regards
Zhao Liang 

-----Original Message-----
From: gstreamer-devel-bounces at lists.sourceforge.net
[mailto:gstreamer-devel-bounces at lists.sourceforge.net] On Behalf Of
Julien Moutte
Sent: Tuesday, February 19, 2008 11:56 PM
To: gstreamer-devel at lists.sourceforge.net
Subject: [gst-devel] GStreamer embedded mailing list proposal


Dear GStreamers,

I have received requests and met a few people from the embedded world
and it is pleasing to know that they use and appreciate GStreamer.

I was surprised, though, to discover that most of them have been
refactoring big chunks of the frame work to suit their needs and they
are not sharing their ideas with our community. I was even more
surprised to see that they sometimes have issues and questions about
GStreamer but they don't dare, or consider it off-topic, to mail the
-devel list about them.

After some interesting discussion on IRC (yes we still do things first
on IRC before going to the list), I proposed to send that mail to raise
a discussion around that topic.

A potential idea would be to create a dedicated list around the embedded
community and their GStreamer discussions. The goal there would be to
focus on embedded concerns and have a good communication channel between
companies, individuals and organizations around GStreamer's future.

The risk here is that this could get the traffic on that list to a very
low level (if it is a subset of the current gst-devel traffic).  And
additionally it might be harder to get replies to questions if we expect
current hackers to pay attention to both lists. On the other hand,
embedded people might feel more involved and we could see some new faces
coming up on that list with interesting ideas, discussions.

So if you are working on an embedded project together with GStreamer and
you feel that having a dedicated communication channel would help you
collaborate on the project please bring your points to that thread.

Thanks for your attention.

Best regards,

Julien Moutte.

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel