[PySide] PySide website down

Srini Kommoori vasure at gmail.com
Fri Sep 28 15:46:46 CEST 2012


pyside.org redirect to wiki page is online. I have updated wiki with a
docs link.

Hugo, Is it possible to host static documentation pages on github
pyside account? I will send a pull request.

thanks,
-Srini

On Fri, Sep 28, 2012 at 5:43 AM, Srini Kommoori <vasure at gmail.com> wrote:
> 1. I contacted local Digia folks(Tuukka Ahoniemi) and they sent our
> domain and vpc requests to concerned folks. Hope we will hear
> something back from them today.
>
> On the technical side of things, I just checked search also on the
> docs, there is no dependency on a server as they are all static pages
> and javascript is doing the search.
> http://srinikom.github.com/pyside-docs/
>
> So we could host docs on github without depending on anyone. All we
> need is domain whois info access Or someone willing to modify domain
> settings for us.
>
> 2. I can easily create a blogger site+blog with the same theme and we
> all can collaborate and publish updates.
>
> 3. I volunteer to take up the hosting tasks going forward completely.
> It would be good to know how is the project structured? Who posts
> binaries? I think on the coding and checkin side, our git repository
> is taken care right now - do we need any help on that?
>
> Matti, Am I missing any hosting tasks?
>
> thanks,
> -Srini
>
> On Fri, Sep 28, 2012 at 5:22 AM, Matti Airas <mairas at iki.fi> wrote:
>> Hi Stephan,
>>
>> On 28 September 2012 15:07, Stephan Deibel <sdeibel at wingware.com> wrote:
>>
>>> Matti Airas wrote:
>>
>>
>>>
>>> I'm almost 100% certain that the PSF hosting some resources for PySide
>>> won't come with a requirement about licensing or process for PySide.  Or at
>>> least that's my impression from having been on the PSF board some years ago,
>>> and from everything I've observed since. It certainly is true that a
>>> contributor agreement is needed for anything in Python itself and the Python
>>> standard library, but PySide would not go into the Python standard library.
>>
>>
>> I was discussing the issue with some PSF board members back in August 2011,
>> and that was the message then.
>>
>>>
>>> That said, is the problem with Qt Project or a temporary one caused by the
>>> transfer from Nokia to Digia?
>>
>>
>> It's probably really neither. I think the problem was more due to the
>> overworked Nokia Qt organization having to deliver to an unpublished closed
>> project, while at the same time having to cater for the open Qt Project. The
>> open project probably couldn't be sufficiently prioritized - it wasn't an
>> issue with Qt Project itself, IMHO. Ever an optimist, I actually think Digia
>> has more interest in Qt Project in general and in PySide too.
>>
>> I got a while ago in contact with Lars Knoll (Qt lead maintainer), and he
>> wanted to resolve the issue ASAP. Also talked to Tuukka Turunen (Digia Qt
>> Commercial Director), and he wanted to resolve the issue without delay, too.
>> So, let's hope for the best.
>>
>>> I don't care too much either way but maybe in the long term being part of
>>> the Qt Project will be less hassle (if really part of it, and not easily
>>> orphaned again as seems to have happened now).
>>
>>
>> Me too, with the same condition. :-)
>>
>> Cheers,
>>
>> ma.



More information about the PySide mailing list