[MeeGo-dev] Creating a Python project for MeeGo (was: pyside in repo.meego.com?)
Foster, Dawn M
dawn.m.foster at intel.com
Mon Sep 20 14:24:41 PDT 2010
On Sep 20, 2010, at 2:03 PM, Sivan Greenberg wrote:
> On Mon, Sep 20, 2010 at 5:59 PM, Matti Airas <matti.p.airas at nokia.com> wrote:
>> On 20.09.2010 17:41, ext Per Åstrand wrote:
>>> I've been checking the repositories for python support.
>>> AFAICT the compliance doc at
>>> requires an application to only use packages in the officail repos to
>>> be "meego compliant"
>>> IMHO it makes sense to also include python bindings for QT (pyside) to
>>> be able to write meego compliant applications in python. pyside
>>> project seems to be tracking QT and meego well
>>> Also kind of strange that bindings for gtk is in the repo, but not for
>> Hi Per,
>> We (as in the PySide team) are definitely planning on providing the PySide
>> packages on MeeGo in the near future. However, since we're just ramping up
>> our MeeGo activities (still waiting for the OBS accounts to be created,
>> etc), I have to say I've been rather ignorant about the details of the
>> contribution process.
>> In particular, I'm interested about the proper channels for contributing to
>> the existing Python distribution. What is the formal project the current
>> Python packages live in? Should we contribute there or should we make a
>> proposal to the TSG to create a proper MeeGo Python project which could act
>> as an umbrella for all Python-related activities in MeeGo?
> Matti, maybe we can ask Dawn to add this item for tomorrow's TSG
> meeting so it can be discussed and agreed upon already?
I don't think this is a TSG decision item. Only project-wide decisions or things
that need to be escalated should go all the way to the TSG for a decision. I'm
guessing that this is something that the architecture team along with the
SDK / application development team can address.
Links with contact info:
More information about the MeeGo-dev