Are there plans for progress? If the app was open it would be possible to start integrating it more with the rest of the maemo environment. Presence information in Address Book, etc...
There are no exact schedule. The original plan was to open it when version 0.2.0 was released, but the plan was changed a bit. Of course, if there is really larger interest to develop the application further, the plans could be done. I think opening just for for sake of opening is not necessary.
However, there were plans to add support for presence information (Galago etc). The problem is that Jaiku has not published how the actual presence information (availability "traffic lights") is updated. I have asked about the topic directly from Jyri but received no answer. I interpreted the silence so that they are not willing to support third party developers otherwise than publishing the very limited API documentation.
But there are plenty of possibilities to move on, and I have already a long list of new features targeted to version 0.3.0.
I'd at least contribute a patch to use proper icons intead of the ugly stock ones being used currently. Having it closed-source kinda puts me in the "I don't care" mode.
Okey. It is nice to know that there is interest to participate. I have appreciated the help of active users who have contributed by reporting bugs and making feature requests. Maybe a larger group would have a change to make this bigger, better and more beatiful.
I am planning to refactor the architecture a bit (as I did also before the 0.2.0 release), so it is not wise to put efforts into this version. I am seriously considering opening the next version (0.3.0) now.
No strong opinions, as long as it's a mainstream GPL compatible Free Software license. Apache 2.0 is only compatible with GPL 3 (not 2), but I guess that's not a real problem.
Incompatibleness with gpl is quite small nuance, since both licences share the ideologicy regarding to patents. Of course apache licence permits one to release derived works without publishing the source code, which can be a good thing or a bad thing.
Compatibility with GPL is important when you think about mixing and merging code from different projects. It would be good if there is a single license that everybody is compatible with to allow code to move freely. From my point of view, the GPL has the best chance to become this single "lingua franca" license, and it's of course a good license.
That's true at least what comes to mixing and merging. I am not keen on gpl, but lgpl could be okay. However, I think apache licence is a good compromise.
Yep, I am not saying you should use theGPL, just that it is a good idea to choose a license that is compatible with the GPL. Apache 2.0 is incompatible with GPL 2, which is a bug that GPL 3 fixed. I guess it is OK to only worry about compatibility with GPL 3 now.
17 comments so far
No, no progress in that area... :)
1 year, 10 months ago by hhedberg
Are there plans for progress? If the app was open it would be possible to start integrating it more with the rest of the maemo environment. Presence information in Address Book, etc...
1 year, 9 months ago by bergie
There are no exact schedule. The original plan was to open it when version 0.2.0 was released, but the plan was changed a bit. Of course, if there is really larger interest to develop the application further, the plans could be done. I think opening just for for sake of opening is not necessary.
However, there were plans to add support for presence information (Galago etc). The problem is that Jaiku has not published how the actual presence information (availability "traffic lights") is updated. I have asked about the topic directly from Jyri but received no answer. I interpreted the silence so that they are not willing to support third party developers otherwise than publishing the very limited API documentation.
But there are plenty of possibilities to move on, and I have already a long list of new features targeted to version 0.3.0.
1 year, 9 months ago by hhedberg
I'd at least contribute a patch to use proper icons intead of the ugly stock ones being used currently. Having it closed-source kinda puts me in the "I don't care" mode.
1 year, 9 months ago by michaldominik
I have already forgotten what I wanted to fix. Already stopped caring :-/
1 year, 9 months ago by tko
Okey. It is nice to know that there is interest to participate. I have appreciated the help of active users who have contributed by reporting bugs and making feature requests. Maybe a larger group would have a change to make this bigger, better and more beatiful.
I am planning to refactor the architecture a bit (as I did also before the 0.2.0 release), so it is not wise to put efforts into this version. I am seriously considering opening the next version (0.3.0) now.
1 year, 9 months ago by hhedberg
Mauku goes open source. See http://mauku.henrikhedberg.com/news#20070928213000
1 year, 9 months ago by hhedberg
Great news!
1 year, 9 months ago by perwille
Cool.
1 year, 9 months ago by michaldominik
What license?
1 year, 9 months ago by mvo
Apache licence, v2 is the strongest candidate. Why? Any opinions on the licencing issues?
1 year, 9 months ago by hhedberg
No strong opinions, as long as it's a mainstream GPL compatible Free Software license. Apache 2.0 is only compatible with GPL 3 (not 2), but I guess that's not a real problem.
1 year, 9 months ago by mvo
Incompatibleness with gpl is quite small nuance, since both licences share the ideologicy regarding to patents. Of course apache licence permits one to release derived works without publishing the source code, which can be a good thing or a bad thing.
1 year, 9 months ago by hhedberg
Compatibility with GPL is important when you think about mixing and merging code from different projects. It would be good if there is a single license that everybody is compatible with to allow code to move freely. From my point of view, the GPL has the best chance to become this single "lingua franca" license, and it's of course a good license.
1 year, 9 months ago by mvo
That's true at least what comes to mixing and merging. I am not keen on gpl, but lgpl could be okay. However, I think apache licence is a good compromise.
1 year, 9 months ago by hhedberg
Yep, I am not saying you should use theGPL, just that it is a good idea to choose a license that is compatible with the GPL. Apache 2.0 is incompatible with GPL 2, which is a bug that GPL 3 fixed. I guess it is OK to only worry about compatibility with GPL 3 now.
1 year, 9 months ago by mvo
OK, guys. The source is out now! Let's see what is the benefit for the Mauku user community. :)
1 year, 7 months ago by hhedberg