<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:base="https://terceiro.xyz/">
  <id>https://terceiro.xyz/</id>
  <title>Antonio Terceiro - Posts tagged with "fisl"</title>
  <updated>2015-08-05T01:13:00Z</updated>
  <link rel="alternate" href="https://terceiro.xyz/" type="text/html"/>
  <link rel="self" href="https://terceiro.xyz/tag/fisl/feed.xml" type="application/atom+xml"/>
  <author>
    <name>Antonio Terceiro</name>
    <uri>https://terceiro.xyz</uri>
  </author>
  <entry>
    <id>tag:terceiro.xyz,2015-08-05:/2015/08/05/elixir-in-debian-minidebconf-at-fisl-and-debian-ci-updates/</id>
    <title type="html">Elixir in Debian, MiniDebconf at FISL, and Debian CI updates</title>
    <published>2015-08-05T01:13:00Z</published>
    <updated>2015-08-05T01:13:00Z</updated>
    <link rel="alternate" href="https://terceiro.xyz/2015/08/05/elixir-in-debian-minidebconf-at-fisl-and-debian-ci-updates/" type="text/html"/>
    <content type="html">&lt;p&gt;&lt;a href="/2015/07/02/upgrades-to-jessie-ruby-22-transition-and-chef-update/"&gt;In June I started keeping track&lt;/a&gt; of my Debian activities, and this is my July update.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Elixir in Debian&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="http://elixir-lang.org/"&gt;Elixir&lt;/a&gt; is a functional language built on top of the Erlang virtual machine. If features imutable data structures, interesting concurrency primitives, and everything else that Erlang does, but with a syntax inspired by Ruby what makes it much more aproachable in my opinion.&lt;/p&gt;

&lt;p&gt;Those interested in Elixir for Debian are encouraged to hang around in #debian-elixir on the OFTC IRC servers. There are still a lot of things to figure out, for example how packaging Elixir libraries and applications is going to work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;MiniDebconf at FISL, and beyond&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I helped organize a &lt;a href="https://wiki.debian.org/DebianEvents/br/2015/MiniDebconfFISL"&gt;MiniDebconf&lt;/a&gt; at this year’s FISL, in Porto Alegre on the 10th of July. The whole program was targetted at getting more people to participate in Debian, so there were talks about translation, packaging, and a few other more specific topics.&lt;/p&gt;

&lt;p&gt;I myself gave two talks: one about Debian basics, “What is Debian, and how it works”, and second one on “packaging the free software web”, which I will also give at &lt;a href="http://debconf15.debconf.org/"&gt;Debconf15&lt;/a&gt; later this month.&lt;/p&gt;

&lt;p&gt;The recordings are available (all talks in Portuguese) &lt;a href="http://meetings-archive.debian.net/pub/debian-meetings/2015/mini-debconf-fisl/"&gt;at the Debian video archive&lt;/a&gt; thanks to Holger Levsen.&lt;/p&gt;

&lt;p&gt;We are also organizing a &lt;a href="https://wiki.debian.org/DebianEvents/br/2015/MiniDebconfLatinoware"&gt;new MiniDebconf in October&lt;/a&gt; as part of the &lt;a href="http://latinoware.org/"&gt;Latinoware&lt;/a&gt; schedule.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ruby&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We are in the middle of a &lt;a href="https://release.debian.org/transitions/html/ruby2.2.html"&gt;transition&lt;/a&gt; to switch to Ruby 2.2 as default in Debian unstable, and we are almost there. The Ruby transition is now on hold while &lt;a href="https://release.debian.org/transitions/html/libstdc++6.html"&gt;GCC 5 one&lt;/a&gt; is going on, but will be picked up as soon as were are done with GCC 5.&lt;/p&gt;

&lt;p&gt;ruby-defaults has been uploaded to experimental for those that want to try having Ruby 2.2 as default before that change hits unstable. I myself have been using Ruby 2.2 as default for several weeks without any problem so far, including using vagrant on a daily basis and doing all my development on sid with it.&lt;/p&gt;

&lt;p&gt;I started taking notes about &lt;a href="https://wiki.debian.org/Teams/Ruby/InterpreterTransitions"&gt;Ruby interpreter transitions&lt;/a&gt; work to make sure that knowledge is registered.&lt;/p&gt;

&lt;p&gt;I have uploaded minor security updates of both &lt;a href="https://tracker.debian.org/news/701396"&gt;ruby2.1&lt;/a&gt; and &lt;a href="https://tracker.debian.org/news/701394"&gt;ruby2.2&lt;/a&gt; to unstable. They both reached testing earlier today.&lt;/p&gt;

&lt;p&gt;I have also &lt;a href="https://tracker.debian.org/news/697703"&gt;fixed&lt;/a&gt; another &lt;a href="https://bugs.debian.org/786763"&gt;bug&lt;/a&gt; in redmine, which I hope to get into stable as well as soon as possible.&lt;/p&gt;

&lt;p&gt;gem2deb has seen several improvements through versions &lt;a href="https://tracker.debian.org/news/698275"&gt;0.19&lt;/a&gt;, &lt;a href="https://tracker.debian.org/news/699499"&gt;0.20&lt;/a&gt;, &lt;a href="https://tracker.debian.org/news/699947"&gt;0.20.1&lt;/a&gt; and &lt;a href="https://tracker.debian.org/news/701578"&gt;0.20.2&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I have updated a few packages:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/694910"&gt;ruby-rubymail&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/698034"&gt;ruby-ferret&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/698259"&gt;ruby-omniauth&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/698258"&gt;ruby-hashie&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/699447"&gt;ruby-rack-accept&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/698268"&gt;chef-zero&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/698665"&gt;nailgun-agent&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/698716"&gt;ruby-serialport&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/698717"&gt;ruby-gnome2&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/699285"&gt;ruby-mysql2&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/699949"&gt;ruby-dataobjects-postgres&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/700007"&gt;ruby-standalone&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/700872"&gt;thin&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/701694"&gt;ruby-stringex&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://tracker.debian.org/news/701693"&gt;ruby-i18n&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Two NEW packages, &lt;a href="https://tracker.debian.org/news/698262"&gt;ruby-rack-contrib&lt;/a&gt; and &lt;a href="https://tracker.debian.org/news/701355"&gt;ruby-grape-logging&lt;/a&gt; ,were ACCEPTED into the Debian archive. Kudos to the ftp-master team who are doing an awesome job reviewing new packages really fast.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Debian Continuous Integration&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This month I have made good progress with the changes needed to make debci work as a distributed system with one master/scheduler node and as many worker nodes (running tests) as possible.&lt;/p&gt;

&lt;p&gt;While doing my tests, I have submitted a &lt;a href="https://lists.linuxcontainers.org/pipermail/lxc-devel/2015-July/012003.html"&gt;patch to lxc&lt;/a&gt; and updated &lt;a href="https://tracker.debian.org/news/699950"&gt;autodep8&lt;/a&gt; in unstable. At some point I plan to upload both autodep8 and autopkgtest to jessie-backports.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sponsoring&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I have sponsored a few packages:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tracker.debian.org/news/698263"&gt;ruby-rack-mount&lt;/a&gt;, &lt;a href="https://tracker.debian.org/news/698317"&gt;ruby-grape-entity&lt;/a&gt;, and &lt;a href="https://tracker.debian.org/news/698320"&gt;ruby-grape&lt;/a&gt; for Hleb Valoshka.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://tracker.debian.org/news/689030"&gt;redir&lt;/a&gt; and &lt;a href="https://tracker.debian.org/news/698913"&gt;tmate&lt;/a&gt; &lt;a href="https://tracker.debian.org/news/701152"&gt;twice&lt;/a&gt; for Lucas Kanashiro.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://lists.debian.org/debian-backports-changes/2015/08/msg00037.html"&gt;lxc to wheezy-backports&lt;/a&gt; for Christian Seiler.&lt;/li&gt;
&lt;/ul&gt;

</content>
  </entry>
  <entry>
    <id>tag:terceiro.xyz,2009-06-26:/2009/06/26/campanha-desligue-o-seu-access-point-no-fisl10/</id>
    <title type="html">Campanha: desligue o seu Access Point no FISL10!</title>
    <published>2009-06-26T10:21:00Z</published>
    <updated>2009-06-26T10:21:00Z</updated>
    <link rel="alternate" href="https://terceiro.xyz/2009/06/26/campanha-desligue-o-seu-access-point-no-fisl10/" type="text/html"/>
    <content type="html">&lt;p&gt;&lt;img src="/oldposts/images/network-wireless.png?1246022222" alt="Network-wireless"&gt;Você já deve ter percebido que a rede wireless do FISL funciona muito bem durante o começo da manhã e no final do dia, não é? Pois é, isso é porquê nesse horários os access points dos participantes não estão ligados! Eu não sou nenhum especialista em wireless, mas do pouco que eu entendo sobre rádio, eu sei que não dá pra transmitir tanta coisa na mesma frequência. O centro de eventos da PUCRS tem uma boa estrutura de wireless, mas com tanto AP ligado ela se torna inútil. Eles até tentam mudar o canal do wireless, mas sempre tem mais um tanto de access points em vários canais.&lt;/p&gt;

&lt;p&gt;Por isso, estou iniciando a campanha "Desligue o seu Access Point no FISL". Se você quer ter uma rede privada no seu stand, ao menos tire as antenas do AP pra que ele não atrapalhe a rede geral, ou melhor ainda, desligue o wireless do seu AP e use só as portas ethernet dele.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:terceiro.xyz,2009-06-23:/2009/06/23/chegando-para-o-fisl10/</id>
    <title type="html">Chegando para o fisl10</title>
    <published>2009-06-23T17:27:00Z</published>
    <updated>2009-06-23T17:27:00Z</updated>
    <link rel="alternate" href="https://terceiro.xyz/2009/06/23/chegando-para-o-fisl10/" type="text/html"/>
    <content type="html">&lt;p&gt;&lt;a href="http://fisl.softwarelivre.org/10/www/" title="FISL10"&gt;&lt;img src="http://fisl.softwarelivre.org/10/www/files/banners/fullbanner1.gif" alt=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Já estou em Porto Alegre. :-)&lt;/p&gt;

&lt;p&gt;O fisl10 promete: a &lt;a href="http://www.colivre.coop.br/" title="Colivre - Cooreativa de Tecnoologias Livres"&gt;Colivre&lt;/a&gt; está decendo em peso, vamos ter um estande na mostra de soluções para demonstrar nossos produtos e serviços. Vamos dar um enfoque especial ao &lt;a href="http://www.noosfero.org/" title="Projeto Noosfero, Redes Sociais com Software Livre"&gt;Noosfero&lt;/a&gt;, que hoje é a plataforma do &lt;a href="/" title="Software Livre Brasil"&gt;softwarelivre.org&lt;/a&gt; (entre outros sites). Estaremos também vendendo exemplares impressos do livro "&lt;a href="http://softwarelivre.org/livro"&gt;Software Livre, Cultura Hacker e Ecossistema da Colaboração&lt;/a&gt;".&lt;/p&gt;

&lt;p&gt;Vou dar duas palestras:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="http://fisl.softwarelivre.org/10/papers/pub/programacao/411"&gt;"Conheça o Noosfero - um software livre para redes sociais"&lt;/a&gt;,  junto com &lt;a href="http://softwarelivre.org/vicente"&gt;Vicente&lt;/a&gt;. Nesta palestra vamos apresentar o projeto, suas funcionalidades, casos de sucesso e como colaborar com o projeto.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="http://fisl.softwarelivre.org/10/papers/pub/programacao/446"&gt;"Qualidade de Código: mantendo seu projeto de software livre sob controle"&lt;/a&gt;. Nesta palestra eu vou falar sobre qualidade de projeto de software, no contexto em que eu venho trabalhando na minha pesquisa de doutorado. Além de discutir noções iniciais sobre alguns atributos de qualidade (tamanho, acoplamento, coesão e separação de interesses), vou demonstrar &lt;a href="http://github.com/terceiro/egypt"&gt;a ferramenta na qual eu venho trabalhando&lt;/a&gt; e discutir boas práticas de projeto (os &lt;a href="http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod"&gt;princípios SOLID&lt;/a&gt;, em especial), exemplificando com projetos de software livre com os quais eu estou familiarizado.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</content>
  </entry>
</feed>

