From goffi at goffi.org Sat Mar 1 00:00:01 2014 From: goffi at goffi.org (Goffi) Date: Sat, 01 Mar 2014 00:00:01 +0100 Subject: [dev] =?utf-8?q?=5Bfr=5D_quelques_reflexions_=C3=A0_propos_de_la_?= =?utf-8?b?c8OpY3U=?= In-Reply-To: <1393625469-sup-2885@kpad> References: <40efbaae51fb18b437cea669b91f36d4@mail.goffi.org> <1393625469-sup-2885@kpad> Message-ID: <40f2342a5f06be82714cbda546fe1283@mail.goffi.org> Hum intéressant, faut voir si c'est compatible avec la nature asynchrone de SàT, et si ça ne demande pas trop de boulot pour l'adapter à Twisted... À étuder... Merci du tuyau :) Le 2014-02-28 23:14, Matthieu Rakotojaona a écrit : > Salut tout le monde, > >> - une implementation de Jingle serait probablement une bonne idée >> aussi >> pour le chiffrement (sans oublier la copie de fichier) > > Pour ce point, Gajim [0] est tout-python et a implémenté Jingle [1], > ca > pourrait aider. En plus, ils sont GPLv3 et utilisent eux aussi hg. > Que > demande le peuple ? :) > > [0] https://gajim.org/ > [1] https://trac.gajim.org/wiki/JingleFileTransfer From mcy at lm7.fr Mon Mar 3 22:59:23 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Mon, 3 Mar 2014 16:59:23 -0500 Subject: [dev] [en] [patch] Jp: GObject 2 --> GI Message-ID: <20140303165923.41274fe5c34c3f23d2d00853@lm7.fr> Hi there, As discussed on sat@, I'm sending a patch to allow Jp to work with the ?new? GObject interface from GI. Thank you Link Mauve for providing the solution. Could you please test that in the dev branch and commit the patch if everything is fine? Thanks, Matteo -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: jp_gobject-gi.patch Type: text/x-diff Taille: 897 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 836 octets Desc: non disponible URL: From mcy at lm7.fr Tue Mar 4 00:00:39 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Mon, 3 Mar 2014 18:00:39 -0500 Subject: [dev] [fr] Nouveau README4PACKAGERS Message-ID: <20140303180039.47c6e490e7cded8ef292ae89@lm7.fr> C'est encore moi, Ci-joint un README4PACKAGERS retravaillé à plusieurs niveau : reformulations, corrections d'anglais, ajout de la dépendance directe de Primitivus sur D-Bus, mise en page, etc. Je n'ai pas envoyé de patch car le fichier était au format DOS donc ça n'aurait pas été lisible de toute façon. J'ai pris quelques libertés, j'espère que ça vous conviendra, sinon prenez ce que vous voulez et jetez le reste :-) Matteo -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: README4PACKAGERS Type: application/octet-stream Taille: 3984 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 836 octets Desc: non disponible URL: From goffi at goffi.org Mon Mar 17 11:53:15 2014 From: goffi at goffi.org (Goffi) Date: Mon, 17 Mar 2014 11:53:15 +0100 Subject: [dev] [FR] quelques infos Message-ID: <5384681.WLS1EAU2Bt@necton3> Salut, quelques infos sur ce qu'on fait en ce moment: Souliane a bossé sur des améliorations du blog (affichage d'une bannière, améliorations diverses), et sur la radio collective (entre autres support MP3); il a aussi ajouté la suppression de compte, en particulier pour la démo sur libervia.org. Pour m'a part j'ai surtout bossé sur des choses extérieures: on essaye de faire revenir pyjamas dans Debian - ce qui nous sera nécessaire pour que Libervia y arrive à son tour - , administration des serveurs, quelques améliorations pour l'installation. J'ai commencé à implémenter les marque- pages aussi. Nous sommes en train d'étudier l'implémentation d'OTR. ++ Goffi From goffi at goffi.org Tue Mar 18 12:23:02 2014 From: goffi at goffi.org (Goffi) Date: Tue, 18 Mar 2014 12:23:02 +0100 Subject: [dev] [en] pyjamas is back in Debian \o/ Message-ID: <9320036.j2ROahxQ7l@necton3> G'day, Pyjamas, the python to javascript compiler/framework which is used to build Libervia, is back in Debian, thanks to Luke Kenneth Casson Leighton and Philip Hands help. It's an important step to bring Libervia in Debian too, so you can expect to see Libervia packaged in a few weeks/months. great news :) Cheers Goffi From goffi at goffi.org Mon Mar 24 13:23:42 2014 From: goffi at goffi.org (Goffi) Date: Mon, 24 Mar 2014 13:23:42 +0100 Subject: [dev] [en] recommendations + text commands Message-ID: <4340031.Us5ptnkBzr@necton3> G'day, I have added a new "recommendations" field for plugins in PLUGIN_INFO: if a plugin is in recommendations instead of dependencies, it will be treated as a dependecy (loaded if needed), but if it can't be found no exception will be raised (i.e. it's not a mandatory plugin). A use case is text commands: before, text-commands plugin was implementing everything, including commands like "join" which is linked to XEP-0045, so XEP-0045 was a dependency of text-commands. Now, text-commands has no more dependency, and it's a recommendation of plugin XEP-0045: if it's available, XEP-0045 will add its own commands, else there just a warning in the logs telling that commands are not available. 2 new methods are in text-commands: - registerTextCommands which look in an instance for every method name "cmd_.*", and add them as text command (the docstring is used for /help). - addWhoIsCb, which can be used by plugin to add information to /whois command. Software version add client name/version and OS used with this method. cheers Goffi From goffi at goffi.org Tue Mar 25 12:08:24 2014 From: goffi at goffi.org (Goffi) Date: Tue, 25 Mar 2014 12:08:24 +0100 Subject: [dev] [en] SSL certificate: which one ? Message-ID: <6860981.EM0NRrjl39@necton3> G'day, as Souliane as implemented https support in Libervia, we now need a certificate for libervia.org serveur/Libervia instance. I'd like your advices for the following options: - self-signed certificate: PROS: * free * easy and quick to do CONS: * can't do authentification * warning in browsers * not accepted in xmpp.net security test - CAcert (https://www.cacert.org/): PROS: * free * based on community, not commercial, more on less in the spirit of SàT * accepted in xmpp.net security test CONS: * warning in browsers * recently removed from Debian and Ubuntu, its seems that there are some security concerns according to the bugs comments (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718434) - StartSSL (https://startssl.com/): PROS: * free for Class 1 * no warning in browsers CONS: * Non commercial use (SàT is not commercial, but as we are planing to create a cooperative and to have salaries, we must check the terms of use) * only one domain and one subdomain * free certificate is 1 year only (but it can be renewed) OK, so what's you opinion ? Do you have any other option ? It's possible to have a self-signed certificate first, and change later. Cheers Goffi From goffi at goffi.org Tue Mar 25 12:30:09 2014 From: goffi at goffi.org (Goffi) Date: Tue, 25 Mar 2014 12:30:09 +0100 Subject: [dev] [en] SSL certificate: which one ? In-Reply-To: <6860981.EM0NRrjl39@necton3> References: <6860981.EM0NRrjl39@necton3> Message-ID: <1608780.cPSFOVjpdq@necton3> I forget to say, StartSSL certificates are also accepted in xmpp.net security tests. In my opinion, we should use a Class I startSSL certitficate for the moment, and think more deeply about it when we will have an official association/cooperative status. The big advantage in comparaison of CAcert is that there are no browser warning. Here are the policies of startcom: https://startssl.com/policy.pdf, it's pretty long (50 pages) so please double check that it's OK... Le mardi 25 mars 2014, 12:08:24 Goffi a écrit : > G'day, > > as Souliane as implemented https support in Libervia, we now need a > certificate for libervia.org serveur/Libervia instance. I'd like your > advices for the following options: > > - self-signed certificate: > PROS: > * free > * easy and quick to do > CONS: > * can't do authentification > * warning in browsers > * not accepted in xmpp.net security test > > - CAcert (https://www.cacert.org/): > PROS: > * free > * based on community, not commercial, more on less in the spirit of > SàT > * accepted in xmpp.net security test > CONS: > * warning in browsers > * recently removed from Debian and Ubuntu, its seems that there are > some security concerns according to the bugs comments > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718434) > > - StartSSL (https://startssl.com/): > PROS: > * free for Class 1 > * no warning in browsers > CONS: > * Non commercial use (SàT is not commercial, but as we are planing > to create a cooperative and to have salaries, we must check the terms of > use) * only one domain and one subdomain > * free certificate is 1 year only (but it can be renewed) > > > > OK, so what's you opinion ? Do you have any other option ? It's possible to > have a self-signed certificate first, and change later. > > Cheers > Goffi > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev From goffi at goffi.org Tue Mar 25 13:13:20 2014 From: goffi at goffi.org (Goffi) Date: Tue, 25 Mar 2014 13:13:20 +0100 Subject: [dev] [en] SSL certificate: which one ? In-Reply-To: <1608780.cPSFOVjpdq@necton3> References: <6860981.EM0NRrjl39@necton3> <1608780.cPSFOVjpdq@necton3> Message-ID: <5266269.6Cd9bgYWEe@necton3> Some intersting talks (in french): - https://linuxfr.org/aide#aide-autrecertificatssl - https://linuxfr.org/users/dinomasque/journaux/auto-hebergement-et-securisation-des-acces-via-https - https://linuxfr.org/news/%C3%A9volutions-sur-linuxfr--3#comment-928531 CAcert is clairly more in the spirit of SàT, but it's not included in browsers and will not be anytime soon. So let me know what you think... Le mardi 25 mars 2014, 12:30:09 Goffi a écrit : > I forget to say, StartSSL certificates are also accepted in xmpp.net > security tests. > > In my opinion, we should use a Class I startSSL certitficate for the moment, > and think more deeply about it when we will have an official > association/cooperative status. > > The big advantage in comparaison of CAcert is that there are no browser > warning. > > Here are the policies of startcom: https://startssl.com/policy.pdf, it's > pretty long (50 pages) so please double check that it's OK... > > Le mardi 25 mars 2014, 12:08:24 Goffi a écrit : > > G'day, > > > > as Souliane as implemented https support in Libervia, we now need a > > certificate for libervia.org serveur/Libervia instance. I'd like your > > advices for the following options: > > > > - self-signed certificate: > > PROS: > > * free > > * easy and quick to do > > > > CONS: > > * can't do authentification > > * warning in browsers > > * not accepted in xmpp.net security test > > > > - CAcert (https://www.cacert.org/): > > PROS: > > * free > > * based on community, not commercial, more on less in the spirit of > > > > SàT > > > > * accepted in xmpp.net security test > > > > CONS: > > * warning in browsers > > * recently removed from Debian and Ubuntu, its seems that there are > > > > some security concerns according to the bugs comments > > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718434) > > > > - StartSSL (https://startssl.com/): > > PROS: > > * free for Class 1 > > * no warning in browsers > > > > CONS: > > * Non commercial use (SàT is not commercial, but as we are planing > > > > to create a cooperative and to have salaries, we must check the terms of > > use) * only one domain and one subdomain > > > > * free certificate is 1 year only (but it can be renewed) > > > > OK, so what's you opinion ? Do you have any other option ? It's possible > > to > > have a self-signed certificate first, and change later. > > > > Cheers > > Goffi > > > > _______________________________________________ > > dev mailing list > > dev at goffi.org > > http://lists.goffi.org/listinfo/dev > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev From goffi at goffi.org Tue Mar 25 13:28:47 2014 From: goffi at goffi.org (Goffi) Date: Tue, 25 Mar 2014 13:28:47 +0100 Subject: [dev] [en] SSL certificate: which one ? In-Reply-To: <5266269.6Cd9bgYWEe@necton3> References: <6860981.EM0NRrjl39@necton3> <1608780.cPSFOVjpdq@necton3> <5266269.6Cd9bgYWEe@necton3> Message-ID: <1649640.F4fGYzzIzb@necton3> Le mardi 25 mars 2014, 13:13:20 Goffi a écrit : > - https://linuxfr.org/aide#aide-autrecertificatssl > > - > https://linuxfr.org/users/dinomasque/journaux/auto-hebergement-et-securisat > ion-des-acces-via-https > > - https://linuxfr.org/news/%C3%A9volutions-sur-linuxfr--3#comment-928531 I have started a page (in french) on the wiki for security related questions: http://wiki.goffi.org/wiki/S%C3%A9curit%C3%A9 From souliane at mailoo.org Tue Mar 25 13:42:53 2014 From: souliane at mailoo.org (Adrien) Date: Tue, 25 Mar 2014 13:42:53 +0100 Subject: [dev] [en] SSL certificate: which one ? In-Reply-To: <5266269.6Cd9bgYWEe@necton3> References: <6860981.EM0NRrjl39@necton3> <1608780.cPSFOVjpdq@necton3> <5266269.6Cd9bgYWEe@necton3> Message-ID: <533179CD.4040905@mailoo.org> I would go for CACert. The warning is the browser is not a big deal IMHO. On 03/25/2014 01:13 PM, Goffi wrote: > Some intersting talks (in french): > > > - https://linuxfr.org/aide#aide-autrecertificatssl > > - https://linuxfr.org/users/dinomasque/journaux/auto-hebergement-et-securisation-des-acces-via-https > > - https://linuxfr.org/news/%C3%A9volutions-sur-linuxfr--3#comment-928531 > > CAcert is clairly more in the spirit of SàT, but it's not included in browsers > and will not be anytime soon. So let me know what you think... > > > Le mardi 25 mars 2014, 12:30:09 Goffi a écrit : >> I forget to say, StartSSL certificates are also accepted in xmpp.net >> security tests. >> >> In my opinion, we should use a Class I startSSL certitficate for the moment, >> and think more deeply about it when we will have an official >> association/cooperative status. >> >> The big advantage in comparaison of CAcert is that there are no browser >> warning. >> >> Here are the policies of startcom: https://startssl.com/policy.pdf, it's >> pretty long (50 pages) so please double check that it's OK... >> >> Le mardi 25 mars 2014, 12:08:24 Goffi a écrit : >>> G'day, >>> >>> as Souliane as implemented https support in Libervia, we now need a >>> certificate for libervia.org serveur/Libervia instance. I'd like your >>> advices for the following options: >>> >>> - self-signed certificate: >>> PROS: >>> * free >>> * easy and quick to do >>> >>> CONS: >>> * can't do authentification >>> * warning in browsers >>> * not accepted in xmpp.net security test >>> >>> - CAcert (https://www.cacert.org/): >>> PROS: >>> * free >>> * based on community, not commercial, more on less in the spirit of >>> >>> SàT >>> >>> * accepted in xmpp.net security test >>> >>> CONS: >>> * warning in browsers >>> * recently removed from Debian and Ubuntu, its seems that there are >>> >>> some security concerns according to the bugs comments >>> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718434) >>> >>> - StartSSL (https://startssl.com/): >>> PROS: >>> * free for Class 1 >>> * no warning in browsers >>> >>> CONS: >>> * Non commercial use (SàT is not commercial, but as we are planing >>> >>> to create a cooperative and to have salaries, we must check the terms of >>> use) * only one domain and one subdomain >>> >>> * free certificate is 1 year only (but it can be renewed) >>> >>> OK, so what's you opinion ? Do you have any other option ? It's possible >>> to >>> have a self-signed certificate first, and change later. >>> >>> Cheers >>> Goffi >>> >>> _______________________________________________ >>> dev mailing list >>> dev at goffi.org >>> http://lists.goffi.org/listinfo/dev >> >> _______________________________________________ >> dev mailing list >> dev at goffi.org >> http://lists.goffi.org/listinfo/dev > > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev > From goffi at goffi.org Tue Mar 25 18:37:15 2014 From: goffi at goffi.org (Goffi) Date: Tue, 25 Mar 2014 18:37:15 +0100 Subject: [dev] [en] SSL certificate: which one ? In-Reply-To: <533179CD.4040905@mailoo.org> References: <6860981.EM0NRrjl39@necton3> <5266269.6Cd9bgYWEe@necton3> <533179CD.4040905@mailoo.org> Message-ID: <8134027.Rs3MiHcqi8@necton3> OK, I have emitted a class I certificate (6 months validity) from CAcert. libervia.org is updated with https support, and prosody now use the CAcert certificate. I have also updated lua-sec. We now have two A on xmpp.net security test (was F before): - https://xmpp.net/result.php?domain=libervia.org&type=client - https://xmpp.net/result.php?domain=libervia.org&type=server I guess we'll need to document how CAcert works, why we choosed it, how to install root certificates, why there is a warning, etc. Le mardi 25 mars 2014, 13:42:53 Adrien a écrit : > I would go for CACert. The warning is the browser is not a big deal IMHO. > > On 03/25/2014 01:13 PM, Goffi wrote: > > Some intersting talks (in french): > > > > > > - https://linuxfr.org/aide#aide-autrecertificatssl > > > > - > > https://linuxfr.org/users/dinomasque/journaux/auto-hebergement-et-securis > > ation-des-acces-via-https > > > > - https://linuxfr.org/news/%C3%A9volutions-sur-linuxfr--3#comment-928531 > > > > CAcert is clairly more in the spirit of SàT, but it's not included in > > browsers and will not be anytime soon. So let me know what you think... > > > > Le mardi 25 mars 2014, 12:30:09 Goffi a écrit : > >> I forget to say, StartSSL certificates are also accepted in xmpp.net > >> security tests. > >> > >> In my opinion, we should use a Class I startSSL certitficate for the > >> moment, and think more deeply about it when we will have an official > >> association/cooperative status. > >> > >> The big advantage in comparaison of CAcert is that there are no browser > >> warning. > >> > >> Here are the policies of startcom: https://startssl.com/policy.pdf, it's > >> pretty long (50 pages) so please double check that it's OK... > >> > >> Le mardi 25 mars 2014, 12:08:24 Goffi a écrit : > >>> G'day, > >>> > >>> as Souliane as implemented https support in Libervia, we now need a > >>> certificate for libervia.org serveur/Libervia instance. I'd like your > >>> advices for the following options: > >>> > >>> - self-signed certificate: > >>> PROS: > >>> * free > >>> * easy and quick to do > >>> > >>> CONS: > >>> * can't do authentification > >>> * warning in browsers > >>> * not accepted in xmpp.net security test > >>> > >>> - CAcert (https://www.cacert.org/): > >>> PROS: > >>> * free > >>> * based on community, not commercial, more on less in the spirit of > >>> > >>> SàT > >>> > >>> * accepted in xmpp.net security test > >>> > >>> CONS: > >>> * warning in browsers > >>> * recently removed from Debian and Ubuntu, its seems that there are > >>> > >>> some security concerns according to the bugs comments > >>> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718434) > >>> > >>> - StartSSL (https://startssl.com/): > >>> PROS: > >>> * free for Class 1 > >>> * no warning in browsers > >>> > >>> CONS: > >>> * Non commercial use (SàT is not commercial, but as we are planing > >>> > >>> to create a cooperative and to have salaries, we must check the terms of > >>> use) * only one domain and one subdomain > >>> > >>> * free certificate is 1 year only (but it can be renewed) > >>> > >>> OK, so what's you opinion ? Do you have any other option ? It's possible > >>> to > >>> have a self-signed certificate first, and change later. > >>> > >>> Cheers > >>> Goffi > >>> > >>> _______________________________________________ > >>> dev mailing list > >>> dev at goffi.org > >>> http://lists.goffi.org/listinfo/dev > >> > >> _______________________________________________ > >> dev mailing list > >> dev at goffi.org > >> http://lists.goffi.org/listinfo/dev > > > > _______________________________________________ > > dev mailing list > > dev at goffi.org > > http://lists.goffi.org/listinfo/dev > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev From mcy at lm7.fr Wed Mar 26 12:23:33 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Wed, 26 Mar 2014 11:23:33 +0000 Subject: [dev] =?utf-8?q?=5Ben=5D_SSL_certificate=3A_which_one_=3F?= In-Reply-To: <533179CD.4040905@mailoo.org> References: <6860981.EM0NRrjl39@necton3> <1608780.cPSFOVjpdq@necton3> <5266269.6Cd9bgYWEe@necton3> <533179CD.4040905@mailoo.org> Message-ID: <13d27ff1dae14b45cc441656453ebd30@lm7.fr> Le 2014-03-25 12:42, Adrien a écrit : > I would go for CACert. The warning is the browser is not a big deal > IMHO. I think CACert is a good choice. The importance of the browser warning is relative to the target audience. For now I think mostly geeks are interested in SaT so asking to install a new certificate is not a problem. You can still change for a StartSSL certificate later if needed. Cheers, Matteo From goffi at goffi.org Wed Mar 26 16:41:24 2014 From: goffi at goffi.org (Goffi) Date: Wed, 26 Mar 2014 16:41:24 +0100 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?changement_du_pr=C3=A9fixe?= =?utf-8?q?_/_subject_prefix_change?= Message-ID: <2341634.JMnFfC54cS@necton3> Salut, suite à une demande pour faciliter le filtrage, le préfixe de la liste a été change en [SàT dev]. Merci de mettre à jour vos filtres... ++ Goffi -- G'day, as requested to make filtering more easy, the list prefix has been changed to [SàT dev]. Please update your filters Cheers Goffi From goffi at goffi.org Wed Mar 26 16:42:44 2014 From: goffi at goffi.org (Goffi) Date: Wed, 26 Mar 2014 16:42:44 +0100 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Bdev=5D_changement_du_pr?= =?utf-8?q?=C3=A9fixe_/_subject_prefix_change?= In-Reply-To: <2341634.JMnFfC54cS@necton3> References: <2341634.JMnFfC54cS@necton3> Message-ID: <2314894.jAkfKMJvi4@necton3> Just adding [dev] to this emal, so everybody can see it :) Le mercredi 26 mars 2014, 16:41:24 Goffi a écrit : > Salut, > > suite à une demande pour faciliter le filtrage, le préfixe de la liste a été > change en [SàT dev]. Merci de mettre à jour vos filtres... > > ++ > Goffi > > -- > > G'day, > > as requested to make filtering more easy, the list prefix has been changed > to [SàT dev]. Please update your filters > > Cheers > Goffi > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev From goffi at goffi.org Fri Mar 28 18:36:00 2014 From: goffi at goffi.org (Goffi) Date: Fri, 28 Mar 2014 18:36 +0100 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [en] important updates Message-ID: <3466074.uTHL3bQvJZ@necton3> G'day, I have done a huge refactoring in the backend, mainly about discovery but also with entities cache (see commits). The discovery change are explained enough in the commits, but some precisions about entities cache; before there was a mess between bare jid and resources, so I have changed that: - entity cache now always use the full jid, if you need to access bare_jid information, you have to use userhostJID yourself - when a resource is accessed, the bare jid cache is updated with 2 keys: "LAST_RESOURCE" which contain the last used resource, and "resources" which containt a set of all the resources which were active during the session. I have also done a lot of cleaning. These changes should bring some bugs, the time to fixe the usage everywhere, but they should quickly fix a lot of them... Cheers Goffi From goffi at goffi.org Sun Mar 30 13:44:03 2014 From: goffi at goffi.org (Goffi) Date: Sun, 30 Mar 2014 13:44:03 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [en] Naming conventions Message-ID: <5812368.fAQ3R7jeaW@necton3> G'day, please note some updates in SàT's naming conventions: http://wiki.goffi.org/wiki/Coding_style/en#General Cheers Goffi