I remember seeing a mail from Brian that he is working on codeina. Brian, do we
have a integration plan?

I have added a spec-file to SFE for codina called SFEcodeina.spec.  Overall it
seems to work well, but it does not correctly link to the proper Solaris
plugins on the Fluendo website.  I filed a bug with the Fluendo trak, it is bug
#132.  You can refer to the bug here:

  https://core.fluendo.com/gstreamer/trac/ticket/132

I am hoping to work with the Fluendo team to fix this.  I suspect the problem
may  be on the Fluendo server side, and they may need to do some work to make
it work with Solaris.

Also, note that codeina has some new dependencies (gnome-python, pyopenssl, and
pyyaml) which will need to get integrated for this to work.  Since pyopenssl
relates to encryption, this will take a bit of time to ingrate due to export
control paperwork, etc.

Is there any status on this and what we are going to do about it?

This should be considered as a usability blocker for next release.
Regards,

If the problem is on the Fluendo server side, I am not sure making this issue a 
"blocker" makes any sense.  Fluendo is a 3rd party that makes a fair portion of 
their money via consulting.  If this is a high priority, then I would recommend
hiring Fluendo to spend a few days or a week making it Solaris ready.

In the meantime, I plan on continuing to work with Fluendo to fix the problems.
 However, they do not seem to have a lot of time to dedicate to helping me for
free, so far.  You probably notice that they have not had time to update my bug
report, even though I filed it a month ago.  

So, things have been slow going.

Working with the codeina project team, we have now got this working.  I think 
there were some changes they needed to make on the server side to make it 
understand that https://shop.fluendo.com/codeina/?arch=intel&os=solaris and
https://shop.fluendo.com/codeina/?arch=sparc&os=solaris actually should point
to the Solaris plugins.

But this is now done, and you should be able to build SFEcodeina and its 
dependencies from spec-files-extra.  Seems to work reasonably.  

However, before we integrate into OpenSolaris, we probably first need to decide 
if Sun wants to endorse Fluendo in this way.  I am not sure what we need to do
to 
make such a decision.  But I am guessing we probably need to get some approval 
from business and legal leadership.  Who is driving the need to integrate this?

Also, note that codeina sucks in a few new dependencies, including pyOpenSSL, 
pyyaml, and notify-python.  I believe we already have plans to integrate
notify-python, but the other two will need to be added also to support codeina.
Note that adding PyOpenSSL will likely be a bit of work since it will require 
doing Export Control forms.  Just so you know this will likely take some time
to integrate once we decide we want to do it.

*** Bug 1022 has been marked as a duplicate of this bug. ***

The codeina code is not ready for integration with OpenSolaris 08.11.

Although codeina now seems to work okay if you launch it directly from the 
command line, it doesn't autolaunch when you try to play a file in a 
GStreamer-based program that can't be played but a plugin is available at the 
Fluendo webstore.  In other words, it doesn't work when you set the 
environment variable: GST_INSTALL_PLUGINS_HELPER=/usr/bin/codeina  

You can refer here:

  https://core.fluendo.com/gstreamer/trac/ticket/132

We really need to get this issue resolved before we can integrate Codeina.  I
am working with the people at Fluendo at resolving this issue.

The legal work for pyopenssl is done, as IPS is using it now.  It still needs
to be ARCed and integrated into whatever consolidation will take it, but you
should be clear to start that process.

When you say legal work is done.  Do you mean OSR and/or Export Control?

I believe once this integrates we will also have to update Export Control forms
for all python modules which make use of it, but currently have the pyopenssl
features disabled.  So probably some additional work.

Are there any plans for the IPS team to ARC and/or integrate pyopenssl, or
should the desktop team do this when we integrate codeina or elisa or something
else that needs it?

Hi,

Gezz, I think this has got to be one of *the* most important REF for the next
release in regards to Ubuntu-kind of usability.

Not much time for community testing and feedback..
What's our status?

Best Regards,
Edward.

We are currently working to integrate Elisa and codeina into the next release. 
There is a fair bit of work involved due to the dependency on pyopenssl, but
our hope is to get this into the next release.  We're working towards that end.

This is an important enhancement but we won't hold the November release to
address it so clearing this as a blocker.

Note that we've pretty much done all the work to integrate codeina.  ARC review
is in process.  However, this is being hung up in marketing.  We need marketing
approval to integrate a product that endorses a 3rd party like Fluendo, and
marketing seems slow to make a decision here.

Fantastic news Brian!

Is there any way that we can track the marketing approval process from outside
of Sun...maybe communicating milestones as they are reached?

Brian: who are you looking for marketing approval from?

Chris Baker is the marketing person who is working for BobG's staff on
multimedia related issues, and who I have been taking direction from on issues
relating to media.

I don't believe there is any process for providing status updates on codeina's
marketing review.  It is very uncommon for a free software module to endorse a
specific company like Fluendo.  In fact, I am unaware of any other module that
has ever been integrated into Solaris by the desktop team that has this sort of
issue.  So there isn't really a formal process with milestones to report.

Got marketing approval.  Now integrated into build 107.