[MeeGo-dev] Information on contribution to upstream components
tomeu at tomeuvizoso.net
Mon Nov 29 01:17:48 PST 2010
I'm just a developer in a Meego-based project, but will share my point
of view just for what it may be worth.
On Sun, Nov 28, 2010 at 11:28, <aparna.nand at wipro.com> wrote:
> 1. There could be a great difference between latest version of the
> upstream components and the version running on MeeGo in which case the
> upstream version of the component may not even be compiling on the MeeGo
> env. So are we expected to put our patch and work on OS where the latest
> version can be compiled (like ubuntu, fedora etc).
My project uses mainly Clutter and Mx and I'm developing my new code
with their master branches from git, even if I know my code will
initially ship with Clutter 1.4.
This allows me to have the assurance that any bugs I find haven't been
already fixed in later releases and makes my interaction with the
upstream community more fluid because everybody is working with the
same version of the code.
It has the downside of finding regressions as I go because development
in master is progressing quickly, but by sharing my findings and
proposing patches my karma in the community increases. This has
already paid back greatly because the experts in the community can
spend some of their time answering my questions without the concern of
wasting their time. This expertise cannot be replaced by reading the
documentation available, regardless of its quality.
Debugging the master branch has also given me a good insight of the
internals of those libraries which is also being of great help in my
Please note that this approach works best when working with upstreams
with a good API stability policy and when Meego hasn't diverged too
much from upstream. But I guess this is the norm rather than the
Unfortunately, I don't know how to best explain this to a manager
without experience on FOSS, so many developers will be forced to go
with the apparently short route of just using whatever your product
will ship with, hindering the chances of contributing to upstream :(
> 2. Is it possible that MeeGo branches from a specific upstream version
> and we need to only work on the branched version? If yes is this information
> going to be available somewhere?
> 3. It will be good to have a page in wiki where list of MeeGo
> components, their git links, bugzilla links, roadmap/plan links, branch
> information is available.
This would be great.
> MeeGo-dev mailing list
> MeeGo-dev at meego.com
More information about the MeeGo-dev