Gajim-devel February 2009

gajim-devel@gajim.org

5 participants
9 discussions

GSOC
by Yann Leboulanger 20 Mar '09

20 Mar '09

Hi all, GSOC will arrive in the next monthes, so we can start thinking about project we could propose. So what new features would you like to see in Gajim ? We can discuss that on Wednesday at the end of the meeting. -- Yann

3 5

Re: [Gajim-devel] GSOC
by Yann Leboulanger 01 Mar '09

01 Mar '09

Jonathan Schleifer wrote: > I think adding FT should be pretty easy, whereas I think video might be > a lot of work due to the codecs etc. codecs are handled by gstreamer, not sure we do a lot about that. I CC to liori who may have ideas about that. > So, maybe, we could as well participate in the GSoC and not only XMPP? > There's no requirement for us to be only part of the XMPP projects, we > could be a project as well in the GSoC. Gajim is not an organisation. And I don't have to time to manage all that process. PS: I replied to the list, even if you message was only to me. -- Yann

3 8

Weekly Bug Party #2
by Yann Leboulanger 25 Feb '09

25 Feb '09

I did a small summary of WBP #2 in wiki [1] Next Wednesday I won't be available, but I added some possible points to discuss. Don't hesitate to discuss them! Thanks for those who were here and helped to find solutions and ideas. [1] http://trac.gajim.org/wiki/WeeklyBugParty -- Yann

2 1

Leaving the team
by Stephan Erb 20 Feb '09

20 Feb '09

Hello all, with this mail I and this commit [1] I officially resign from the position of a developer. Within the last months I barely had the time and the motivation to keep contributing to Gajim. I don't see an upcoming shift in that and I want to move on to new tasks. Thanks for the great time. I learned a lot and lot of fun. I will stay around in the community, might even contribute a patch on a rainy summer day :-) Anyway, I am very pleased to see new momentum in the community: New ideas, new patch writers, a new release, regular ticket work. You're doing a great job! Thanks. Kind regards, steve-e [1] http://trac.gajim.org/changeset/11124

3 2

Build system for Gajim
by Mateusz Biliński 15 Feb '09

15 Feb '09

Hi. There's a discussion scheduled for one of next WBPs about build system that works on all OSes (including Mac OSX). I've just stumbled across the post on Google Open Source Blog that is related to this issue [1]. I'm not stating here that this is the solution - it just might come in handy as another option to keep in mind. [1] http://google-opensource.blogspot.com/2009/02/software-construction-toolkit… -- Mateusz Biliński

3 2

Re: [Gajim-devel] [commit-gajim] r11102 - branches/osx_newbuildsys/src/osx/growl/growl_c
by Yavor Doganov 14 Feb '09

14 Feb '09

js(a)gajim.org wrote: > > Author: js > Date: 2009-02-14 15:51:31 +0100 (Sat, 14 Feb 2009) > New Revision: 11102 > > Modified: > branches/osx_newbuildsys/src/osx/growl/growl_c/_growl.c > Log: > DON'T append the GPL to a BSD licensed file! This is clearly a license > violation! Also, don't claim false copyright! No. If a GPL'ed package incorporates files under GPL-compatible licenses (with or without modifications), it is perfectly OK to prepend the GPL license and copyright notice. What's NOT OK is to remove the original copyright notice, since this usually is a violation of the original non-copyleft license (most of them require the notice to be preserved). No violation here at all. See http://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html.

2 2

Weekly Bug party?
by Mateusz Biliński 11 Feb '09

11 Feb '09

Hi. What would you say about Weekly Bug Party? I'm not talking here about bugs solving, but deciding what to do with filed tickets. The idea is to meet for one hour (or so), each week and decide what to do with newly created tickets. This could involve: - setting the real priority of ticket - assigning tickets to devs (epsecially those that were set to high priority) - assign tickets to versions (milestones) - closing invalid tickets - transferring ticket to be handled (decided what to do with it) next week on another WBP [Weekly Bug Party] - evolving: commenting (getting additional info from users), setting more appropriate component, fixing/adding tags This is probably something that Asterix (and some other people from time to time) does all the time. The idea is to face all those tickets in Trac and prioritize them. I think collaboration is a good way here, as there is lots of opened tickets. When we work out all those old tickets WBP will be all about tickets filed during last week (or those transferred to be handled that week). Of course everyone would be still encouraged to perform all of the above mentioned actions outside WBP time window :) Preparation here would involve: * creating new report on Trac [1] that shows all unassigned tickets sorted by date (I guess newest tickets go first as these correspond to current version and are more urgent to solve; by each WBP we could go deeper into forgotten lands) * decide when WBP should take place (I guess some late evening hours would be acceptable) - of course this could be changeable. What do you think about it? :> This is inspired by Scons WBP [2] [1] http://trac.edgewall.org/wiki/TracReports [2] http://www.scons.org/wiki/BugParty -- Regards, Mateusz Biliński

2 4

Re: [Gajim-devel] GSOC
by Yann Leboulanger 08 Feb '09

08 Feb '09

Jonathan Schleifer wrote: > Am 08.02.2009 um 16:30 schrieb Yann Leboulanger: > >> Esessions: already in release, and I don't see any bug. > > It's a very basic implementation, not yet complete. But it's going to go > away anyway due to XTLS, I guess. what is not complete? >> Jingle: Liori will work on that after his exams, in some weeks. > > That's only Jingle Audio, I guess? Then we could have Jingle Video and > Jingle File Transfers as a project. Yep that are projects I thought about. But I don't know if it's hard and long enough for a GSOC project (3 months full time job).As we'll already have jingle for voice, is adding FT or video hard? I cannot answer. >> Plugin system: I'll talk about that with Vardo. Maybe on wednesday. > > Ok. > >> But that doesn't mean someone else cannot work on a new feature. I >> cannot do everything in this project: discuss and fix tickets, implement >> new features. I need help. So anything that can bring help (GSOC for >> example) is very welcome. > > I don't think only introducing new features is a good idea. We could > have a SoC project which is to fix bugs, do API changes, rewrite some of > the code that needs a rewrite. We could have a project that is to > separate the GUI code from the XMPP code (it's sometimes mixed in > common/) etc. There can be project that help Gajim, but don't introduce > new features before the others are stable. I don't think such a project would be accepted by XSF members. Plugin system last year was hardly discussed, and not easily accepted. Not that what you said is useless, of course! But it doesn't promote XMPP directly, showing new feature that can be done thanks to XMPP. -- Yann

1 0

Licence incompatibility -- GPL and OpenSSL
by Yavor Doganov 02 Feb '09

02 Feb '09

[I submitted this as a Trac ticket, but got "Submission rejected due to potential spam" or similar.] I believe Gajim is currently not distributable, as even an optional dependency on python-openssl requires the license of Gajim to have the (in)famous OpenSSL exception. Although PyOpenSSL is under LGPL, it is merely a wrapper and the interpreted program (Gajim) is effectively linked with the library (libssl) through the python extension (PyOpenSSL). http://www.gnu.org/licenses/license-list.html#OpenSSL http://www.gnome.org/~markmc/openssl-and-the-gpl.html http://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL http://www.gnu.org/licenses/gpl-faq.html#InterpreterIncompat (The questions from the GPL FAQ are not about this specific problem, but the explanations give answers to that as well.) Probably an easier alternative to relicensing would be to use python-gnutls, the GnuTLS bindings.

3 9

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Gajim-devel February 2009