Fwd: GTK and OSX: a call to sanity

[Alberto Ruiz <aruiz gnome org>]

Forgot to "Reply All" :-)

---------- Forwarded message ----------
From: Alberto Ruiz <aruiz gnome org>
Date: 2011/9/8
Subject: Re: GTK and OSX: a call to sanity
To: John Ralls <jralls ceridwen us>

2011/9/8 John Ralls <jralls ceridwen us>

The rest of Gtk-OSX isn't Gtk. It's a build system using jhbuild with its own modulesets, a python script for making application bundles, and a few other bits and pieces, including gtk-quartz-engine, a Cocoa HIT theme engine which I haven't touched since Richard Hult left it to me except to ensure that the github and git.gnome.org repos are the same. I don't even know if it works with Gtk3.

It doesn't work with Gtk3.

Do you have any patches for jhbuild or is it just the moduleset? If it is just a module set feel free to maintain it in jhbuild/modulesets/other. I maintain a wayland moduleset there.

 

What's the cost of keeping those bits on Sourceforge vs. Gnome.org? ISTM it will cost me a lot of time and effort to move them into gnome.org with no real benefit to anyone except Emmanuele who can't seem to get an SF account. (Emmanuele, if you really want to sort that out, email me directly and I'll see what I can do to help.)

That is not true at all. There are several benefits for a lot of people, specially you. The main one is that everybody would be working in the same "place", we are very few people and we need to pool resources.

The other benefit is, most people file bugs against bugzilla.gnome.org when they find a problem in Gtk+ (on whatever platform).

When I started my Windows efforts, I did exactly what you did. Under the assumption that nobody cared about Windows, I ended up creating my own mailing list, and trying to do things on my own. That's the worst way to generate traction. If you want help, and if you want people to care, keep them in the loop.

The problem here is that in one hand, most core Gtk+ developers are used to a certain workflow, a certain set of tools... if you want their help, you're going to have to make their lifes easier (and believe me, they want to help you, despite the tone of certain emails). On the other hand, and this is the important bit, fragmentation of the project resources is a huge problem. It is already bad with all the different bindings (pygtk, gtkmm, etc...). Something as fundamental as Windows and Mac OS X support should be visible within the same place (the gtk.org website, gnome's bugzilla, gnome's git repos).

This is not about core Gtk+ developers not wanting to create an SF account, most of them probably have one already. This is about pooling resources and learning to work together.

 

Regards,
John Ralls

[1] https://bugzilla.gnome.org/show_bug.cgi?id=571582

_______________________________________________
gtk-devel-list mailing list
gtk-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list

--
Un saludo,
Alberto Ruiz

-- 
Un saludo,
Alberto Ruiz