[PySide] PySide website down

[Matti Airas]

Hi,

Unfortunately the WHOIS information is not correct. The domain was moved
from Nokia Meego (where I worked) to Qt Project around March or April, but
for some reason the Qt admins decided to put my information as the owner. I
no longer work at Nokia and have no access there.

Hugo and Luciano gave me a heads-up about the virtual server being down.
There's probably nothing that can be done about that, but the plan was
anyway that Qt Project admins would create a redirect from pyside.org to
the PySide wiki front page, and provide hosting for the static pages. I've
tried emailing Qt about the issue as well, but got no reply so far. Next,
some good ole' phone calls...

If the consensus is that being part of Qt Project is actually harmful for
PySide (due to issues like the current one), we could of course try to
discuss with Qt Project about getting the ownership of the domain ourselves
(dunno who should be the right owner?). Or, a bit more than year ago, when
trying to figure out the eventual home for PySide, I was also discussing
with PSF, and they would've been willing, but Qt proposed the current
setup, and at the time I thought it would be a great idea. PSF probably
would be still willing, but if I recall correctly, that'd require a
copyright assignment to PSF from all contributors, and I still have painful
memories about the Qt contributor license agreement hassle... :-/

Cheers,

ma.

On 27 September 2012 22:43, Srini Kommoori <vasure at gmail.com> wrote:

> Hi Guys,
>
> Can we get hold of Matti Airas for domain transfer?
> http://www.networksolutions.com/whois-search/pyside.org
>
> I have talked to few folks at Digia to get the site transferred. I
> will send them the information so that they can track down the
> machine/vpc.
>
> Matti, If you are still on the mailing list, please guide us through.
>
> thanks,
> -Srini
>
> On Thu, Sep 27, 2012 at 1:28 AM, Roman Lacko <backup.rlacko at gmail.com>
> wrote:
> > Hi,
> >
> > 2012/9/26 Jason McCampbell <jmccampbell at enthought.com>:
> >> On Tue, Sep 25, 2012 at 3:40 PM, Anderson Lizardo
> >> <anderson.lizardo at openbossa.org> wrote:
> >>>
> >>> For those looking for the latest release (1.1.2) and pyside-tools,
> >>> fortunately PySide can be found in many distros/OSes, so the source is
> >>> "mirrored" in many places. E.g:
> >>>
> >>> https://distfiles.macports.org/py-shiboken/shiboken-1.1.2.tar.bz2
> >>> (SHA1: 2ffe9d47a3f536840ed9d7eff766a53040bb2a2e)
> >>>
> >>> https://distfiles.macports.org/py-pyside/pyside-qt4.8+1.1.2.tar.bz2
> >>> (SHA1: c0119775f2500e48efebdd50b7be7543e71b2c24)
> >>>
> >>>
> https://distfiles.macports.org/py-pyside-tools/pyside-tools-0.2.14.tar.bz2
> >>> (SHA1: f654553bc9bfb35dbc5673da26830969393f9fe8)
> >>
> >>
> >> This is very helpful, thanks.  I am also trying to update my local
> source
> >> tree from the current development trunk.  Is it correct to pull from
> >> https://codereview.qt-project.org/p/pyside/*?  If so, is there a
> current
> >> version of the build scripts repo or has that been replaced by the
> >> pyside-setup code?  I was able to pull from pyside and shiboken but not
> the
> >> builds scripts.
> >
> > Yes you should allways pull PySide sources from
> > https://codereview.qt-project.org/p/pyside/*
> >
> > The pyside-setup build scripts is available only on github here
> > https://github.com/PySide/pyside-setup
> >
> > R.
> >
> >>
> >> Thanks,
> >> Jason
> >>
> >> _______________________________________________
> >> PySide mailing list
> >> PySide at qt-project.org
> >> http://lists.qt-project.org/mailman/listinfo/pyside
> >>
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/56b5c569/attachment.html>