[maemo-developers] Community widgets for Fremantle

[From: Cornelius Hald]

On Tue, 2009-09-29 at 15:11 +0300, Claudio Saavedra wrote:
> > Input from Nokia would be very welcome (and in my new role I will be asking 
> > for some).  However, I am sure that there is no way that any more widgets are 
> > going to be added to Hildon before Fremantle ships.
> 
> To be realistic, I don't think you'll have your library ready by the
> time Fremantle ships either, so I don't see that as a real problem.

I don't think that either, but a first version with 2-4 widgets could be
ready within a month or two. Of course depending of participation :)

> I have to be honest and say that I don't like this whole discussion too
> much. We are talking all the time about hypotetical things that need to
> be done, and what will be done when these hypotetical things get
> hypotetically merged, and so on. Too much hypothesis, too little facts.

I know you want the code in Hildon. And we all know that this would be
nice. So basically we all want this. But as long as we don't know that
there will be another Hildon release and when this Hildon release will
be, I see now point in even trying to commit to Hildon. Yes, the code
should be there, but of what use is this code if it's never shipped?

Also you didn't reply to my questions regarding my check button
implementation yet. It would be interesting (at least for me) to get a
feeling what kind of contribution would be accepted.

> If I was in your place, I'd start by going the right way and assuming
> that everyone has the best intentions for hildon: just clone the hildon
> tree, put the widgets in place, work on your clone, get something that
> can be shown, file a bug. If for whatever reason these don't get merged
> or you see things going too slowly or too much bureaucracy, nothing is
> stopping you from diverting then.

Our time is also limited, so I really don't want to waste it on my
personal hildon tree if it's not even clear what will eventually be
accepted and when this will be shipped. I'm not talking about a detailed
schedule here, but a rough number. How many updates have there been for
Gtk and Hildon for Diablo?

Also it's a completely different thing if I'm developing a widget under
the assumption that I can make changes to the complete Hildon tree. Or
if I develop under the assumption that Hildon is as it is and I have to
work with that.

So if I'm developing under the assumption that I can change Hildon, I
cannot use this code anymore once it is decided that there will be no
further Hildon updates.


Anyways, it's not even clear, that we will come up with a lot of code.
It's not clear that people will use our code. So why not just start
coding now in a garage project and later if we really have something see
whether or not we can get it into hildon? As a start I really would like
to have a low entry barrier.

I think we cannot just ignore that the Hildon project plays a special
roll in the Nxxx universe. Maybe it's freed from it's chains one day -
then we can take action. The sooner the better of course.

Cheers!
Conny