Justin Karneges | 5 Mar 08:38 2009

Re: Jingle A/V

On Wednesday 04 February 2009 22:46:22 Justin Karneges wrote:
> To use it, you need a separate checkout of PsiMedia.  Then, add
> PSIMEDIA_DIR=/path/to/psimedia in Psi's conf.pri file.  GStreamer
> dependencies are hard-coded.  Edit psimedia/gstprovider/gstconf.pri to
> change them.  With the main window focused, press ctrl+shift+N to configure
> your devices.  To use STUN, set the PSI_STUNADDR environment variable to
> the IP address of a STUN server.

I've changed how this works.  Psi now contains a copy of the PsiMedia 
front-end library (just a few files, in src/psimedia), and is configured to 
use the backend as a plugin rather than static.  A/V call support is now 
compiled in by default.  No need to edit conf.pri.

For A/V calls to actually work, you need to build the psimedia plugin:
  svn checkout https://delta.affinix.com/svn/trunk/psimedia
  cd psimedia
  qconf
  ./configure
  make

(there should be no more need to edit gstconf.pri, as there's now a configure 
script to set up gstreamer.)

This will produce the "libgstprovider.so" plugin.  Set the PSI_MEDIA_PLUGIN 
environment variable to the full path of this file.

Warning: for now, Psi will allow access to the A/V call stuff regardless of 
whether or not you have the plugin.  Using any of it without the plugin will 
cause you to crash, so be careful.  My eventual goal is to have the UI 
dynamically adjust based on the availability of multimedia support.
(Continue reading)

Aleksey Palazhchenko | 5 Mar 22:27 2009
Picon

Re: input fields are broken with qt-4.5

Hi Justin,

Any progress regarding this issue?

I can say that this patch doesn't affect Windows and Mac OS X, and
fixes problem under GNU/Linux. I did check the code of QCA::init
doesn't see any problems.

Do you see any trouble there?
Kevin Smith | 5 Mar 22:44 2009
Picon

Psi - under new^h^h^hold management

Hi all,
  After a few days, I've given up doing a long and explanatory post.
After four and a half great years of Psi, I know that I don't have the
energy for running the project that I had back in 2004 when Justin
handed over to me. Fortunately, Justin is recharged, active again, and
available to continue his calling as project leader, so I'm handing
project leadership back to him. I won't be going anywhere, so please
feel free to contact me about Psi things, and maybe I'll even have a
chance to write some code again, I'll certainly still be around the
XMPP world doing some new and interesting things :)

Thanks to everyone for their support over the last 4 1/2 years in
allowing me such a rewarding role.

I hand you now to the new project leader of Psi ... Justin Karneges.
Good luck to Justin :)

Best,
/K
Justin Karneges | 6 Mar 01:49 2009

Re: input fields are broken with qt-4.5

On Thursday 05 March 2009 13:27:46 Aleksey Palazhchenko wrote:
> Hi Justin,
>
> Any progress regarding this issue?
>
> I can say that this patch doesn't affect Windows and Mac OS X, and
> fixes problem under GNU/Linux. I did check the code of QCA::init
> doesn't see any problems.
>
> Do you see any trouble there?

I haven't quite figured it out yet, but something in the QCA initialization, 
maybe text codec usage or something, happens before QApplication and that 
breaks things.  I hope to resolve this soon (among other Qt 4.5 issues).

-Justin
Justin Karneges | 6 Mar 02:07 2009

Re: Psi - under new^h^h^hold management

On Thursday 05 March 2009 13:44:57 Kevin Smith wrote:
> Thanks to everyone for their support over the last 4 1/2 years in
> allowing me such a rewarding role.

Thank you Kevin, and good luck with everything. :)

To everyone: I'll write up a plan soon.

Have fun,
-Justin
Frederik Schwarzer | 6 Mar 19:26 2009
Picon

Re: Psi - under new^h^h^hold management

On Thursday 05 March 2009 22:44:57 Kevin Smith wrote:

Hi,

> After four and a half great years of Psi, I know that I don't have the
> energy for running the project that I had back in 2004 when Justin
> handed over to me.

There was some critisism about how community-friendly Psi is, a little bit of 
which from my direction. I know that it is sometimes hard to not take such 
critisism personally if you lead a project but I hope you didn't. :)

Thank you for doing an exhausting and sometimes unthankful job for over four 
years. :)

Regards
Justin Karneges | 9 Mar 10:40 2009

The way forward

Hi folks,

It's clear that Psi is in need of some direct attention.  Over the past 
months, contributed patches and user concerns have not been handled very 
well, and in many ways this was simple mismanagement.  I believe this is 
easily correctable.

Compounding the problem is that we thought Kevin and Remko would fully return 
to Psi development after their book-writing.  Were it possible to know that 
they would not actually resume at full capacity (and I'm not implying that 
they even knew this themselves), we could have come up with a resolution 
sooner.  Instead, we suddenly find ourselves needing to reallocate 
responsibility, so please bear with us.

For those that have seen the Swift IM project announcement, I feel I should 
emphasize that the project's existence does not mean Psi is somehow 
deprecated.  Kevin already made this clear in a blog post, but I thought I'd 
say it again here for good measure.  In fact, the projects will likely 
compete, because they have very similar goals.

The plan:
  - Make sure 0.12.1 packages are properly accessible.
  - Qt 4.5 compatibility for 0.13.
  - 0.13 RC at the end of the month.
  - Organize all pending patches and requests.  Improve the task process.
  - Investigate translation process (the handling seemed fishy in 0.12).

I expect to begin working on this plan by the end of the week.

Have fun,
(Continue reading)

Norman Rasmussen | 9 Mar 10:59 2009
Picon

Re: The way forward

On Mon, Mar 9, 2009 at 11:40 AM, Justin Karneges <justin-psi2-A4HSxAr4s6pBDgjK7y7TUQ@public.gmane.org> wrote:
 - Organize all pending patches and requests.  Improve the task process.

Specifically addressing pending patches, what's the easiest way to make them available?  I've been watching the github repo's and they seem pretty active.  Some sort of community review of commits that do not appear in mainline might help - assuming there's a global identifier for 'identical' patches that appear in multiple branches.

--
- Norman Rasmussen
- Email: norman-jsiQGjUZkXfbNDpEy91xOQ@public.gmane.org
- Home page: http://norman.rasmussen.co.za/
<div>
<div class="gmail_quote">On Mon, Mar 9, 2009 at 11:40 AM, Justin Karneges <span dir="ltr">&lt;<a href="mailto:justin-psi2@...">justin-psi2@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
&nbsp;- Organize all pending patches and requests. &nbsp;Improve the task process.</blockquote>
<div><br></div>
<div>Specifically addressing pending patches, what's the easiest way to make them available? &nbsp;I've been watching the github repo's and they seem pretty active. &nbsp;Some sort of community review of commits that do not appear in mainline might help - assuming there's a global identifier for 'identical' patches that appear in multiple branches.</div>
</div>
<br>-- <br>- Norman Rasmussen<br> - Email: <a href="mailto:norman <at> rasmussen.co.za">norman@...</a><br> - Home page: <a href="http://norman.rasmussen.co.za/">http://norman.rasmussen.co.za/</a><br>
</div>
Frederik Schwarzer | 9 Mar 13:20 2009
Picon

Re: The way forward

On Monday 09 March 2009 10:40:55 Justin Karneges wrote:

Hi,

>   - Investigate translation process (the handling seemed fishy in 0.12).

As you pobably know[0], I started some little scripts to handle 
translations[1].
The status of these scripts is that they worked nicely here on a daily basis.
After my last re-installation I didn't set the l10n environment up due to the 
felt lack of interest. However, if it is decided to give it a try, I set it up 
again and prepare deployment more seriously. :)
If you decide to take another path, I maybe could offer some help as well.

Regards

[0] http://lists.affinix.com/pipermail/psi-devel-affinix.com/2008-
September/008309.html
[1] http://github.com/icwiener/psi-l10n-scripts/tree/master
Remko Tronçon | 9 Mar 13:46 2009
Picon

Re: The way forward

> In fact, the projects will likely compete, because they have very similar goals.

Well, it's certainly not the intention that Swift becomes a competing
client for Psi, because of the completely *different* goals. With
Swift, we're going after the users that Psi cannot reach (unless it
changes philosophies drastically, and as such loses the userbase it
currently has).

cheers,
Remko

Gmane