The output of lsusb:

Bus 001 Device 006: ID 147a:e03d Formosa Industrial Computing, Inc.

Hooked them all together, installed avahi-daemon on the Pi so I can ssh into it easily from any lan (ssh raspberrypi.local, although I should change its name to something more unique). Tested arecord locally first. It took me a while to figure out how to use arecord, it’s old stuff that I’m not very used to. You need to specify the hardware device. If you get this sort of error:

arecord: main:682: audio open error: No such file or directory

probably you haven’t specified that you want to record from the card that actually has an input device

pi@raspberrypi ~ $ arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: Audio [2 Channel USB Audio], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

I hooked my phone’s audio player to the mic input of the USB card so that there would be constantly audio coming in the Pi, then started recording

pi@raspberrypi ~ $ arecord -D hw:1,0 -f s16_le -c 2 > test.wav

I have specified the hardware device I want to use, the format and the number of channels. Playing back that file worked.

pi@raspberrypi ~ $ aplay -D hw:1,0 test.wav

Next step was to capture live audio from the line input of the USB card, transcode that to OGG Vorbis and ship the bits to the remote Icecast server I setup last week. I quickly gave up on ezstream and started using ices2, the Icecast client: it seems easier to manage as it takes care of the encoding. This is the input module I used for the Pi:

<input>
<module>alsa</module>
<param name=”rate”>16000</param>
<param name=”channels”>2</param>
<param name=”device”>hw:1,0</param>
<!– Read metadata (from stdin by default, or –>
<!– filename defined below (if the latter, only on SIGUSR1) –>
<param name=”metadata”>1</param>
<param name=”metadatafilename”>liveaudio</param>
</input>

The USB soundcard I’m using sends 16000hz samples. I chose not to resample that, only to downmix stereo to mono to save bandwidth.

<–  stereo->mono downmixing, enabled by setting this to 1 –>
<downmix>1</downmix>

And all seems to work: the Pi sends a clear signal up to the streaming server and it’s been doing that for a while. Big success so far. Next step for me will be to write a script that grabs data from the OpenStack Summit schedule for one room and adds that information as metadata for the streaming: this way the listeners will have an idea of who is speaking or what the session is about.

Update: the stream was having a wide latency, around 20 seconds so I decided to play a little bit with the sampling rates. The latency went down to around 1 second using  <param name=”rate”>48000</param> in the input module and  <samplerate>48000</samplerate> in the encode module, with no resampling. Unfortunately the USB card dies every now and then when not connected through a powered USB hub. Too bad, because the USB hub looks ugly.

Stef for ][ stefano maffulli, 2013. | Permalink | 10 comments
Post tags: communication, community, openstack, participation, raspberrypi, streaming

the question this government needs to answer is why it was so necessary that Aaron Swartz be labeled a “felon.”

This morning I was listening to a show in Italy a volunteer that talks to prisoners incarcerated into the horrible Italian jails. She mentioned a conversation with a man sentenced to six years for selling counterfeited CDs and DVDs on the streets. His words: “Six years! That’s too long”. We’re accepting that selling a song with no rights to do so is a crime worst than hitting a singer with a baseball bat. Our politicians should be ashamed.

.

Stef for ][ stefano maffulli, 2013. | Permalink | No comment
Post tags: aaron, community, copyright, suicide

I presented one session at the conference, lead two sessions on the Design Summit track and facilitated the meeting of the APEC group. Especially on the last day I missed the integration of the summit’s agenda from sched.org into my personal calendar applications (phone and desktop) because I ended up overbooking myself a couple of times. Thankfully Monty Taylor covered for me.

The ‘Community Dashboard‘ that I presented with zAgile was received with enthusiastic comments: the crowd cheered ‘ship it’ when I asked them what they thought of the demo. I’ve talked with Sanjiva and Andrew after the presentation, we should have an early beta out there by the end of the year.

More needs to be done in order to improve the community resources: IRC channels are not owned by the Foundation, some services depend by one person only (the main website and etherpad service, just to make an example). The forums need some love and probably we should have a Q&A system in place. During the sessions Atul Jha from India showed an askbot-powered system that he volunteered to run. In the next weeks I’ll help him go live with it. We discussed also the migration of the General mailing list out of Launchpad: unfortunately I have no news since my last update. The planet needs a better look, if nothing else. And the OpenStack blog needs a better content policy: some people in the room raised some concerns over the abuse of corporate posts on it.

During the discussion on how to track OpenStack’s adoption I was suggested to focus on users’ survey instead of proposing to add some ‘telephone home’ capability to OpenStack’s code (like Mozilla Foundation does with Firefox). I think this is a good idea and I’ll make sure this will become a project of the Foundation in the next months, once we’ll be fully staffed (we’re hiring).

Monty lead the session I proposed about an Integrated Identity System among all OpenStack tools. We went through the improvements we’re working on regarding the CLA workflow and its integration into Gerrit and the Foundation’s membership database. Todd Morey was in the session and we had more ideas on how to make things progress a bit faster (we agreed that hanging out on IRC is a prerequisite for make things happen faster). The future of Launchpad as the main ID system for OpenStack will be decided after Ubuntu Developer Summit: Thierry will spend time with Canonical’s folks there to understand if it will still be able to serve our purposes in the future.

My list of things to do has increased, as it’s expected after the Summit. Thanks everybody for joining.

Stef for ][ stefano maffulli, 2012. | Permalink | 6 comments
Post tags: community, openstack, recap, san diego, summit, todo

I have high hopes for the projects I will present at the Grizzly Summit: Achieving Visibility and Insight Across OpenStack Projects with Dashboards, Traceability, and Faceted Search, Integrated identity system for OpenStack  and Tracking OpenStack adoption.

Stef for ][ stefano maffulli, 2012. | Permalink | No comment
Post tags: change, community, jobs, openstack

There are many people comparing different open source projects, I keep seeing blog posts trying to extrapolate complex concepts from too simple facts. For example, it’s hard to evaluate if an open source project is growing just by looking at the total number of commits per week: when number of commits slow down it may mean that the codebase has reached maturity, not necessarily it’s a sign of diminishing interest. Other simple facts visible on github like the number of followers, forks or ‘watchers’ may not mean much if the developers of that project don’t use the ‘social’ features offered by github.

To measure the “growth” of a project I usually look at a whole bunch of numbers and trends (more importantly) like the total number of committers over time, total new committers over time and also things that are not code-related traffic on mailing lists/forums, websites, google searches, activity on bug trackers as indicators of growth of a community. The total number of commits is more meaningful when taken as one element of ‘livelihood’ of a project (is it still maintained?) but it needs to be integrated with other elements to avoid making mistakes.

All the people interested in measuring open source communities should join the Metrics Working Group at The Open Source Way and push the conversation forward.

Stef for ][ stefano maffulli, 2012. | Permalink | No comment
Post tags: cls, community, metrics, opensourceway, openstack, oscon

I’d be much happier if I saw communities cheering for the alternatives. For example, I wish Canonical added a xmpp/jingle service to its One product (and I’d love to pay for it). I wish the community knew that Google allows federation in its Google Talk service: you can reach your friends that use Google.com from your own jingle server. These are the things that we need, more than yet another proprietary protocol and software to take away our options.

Stef for ][ stefano maffulli, 2012. | Permalink | No comment
Post tags: community, free software, skype

I’d like to discuss the needs of the international community and get a new system in place in the next few weeks. The basic needs are:

• A directory of OpenStack user groups (OSUG) that can host content in different languages: new visitors should be able to find easily an OpenStack User Group for their local area/language. If such group/language is not available, there should be an easy pointer to instructions, tools and policies to create one
• A system for the community  managers to contact the members (all members or just the coordinators/leaders?) of the international communities to coordinate activities.

Requirements

• Register users using SSO: as a user I would like to be able to associate my profile from Launchpad, Linkedin or Google to the site
• Support content in multiple languages (switch list and automatic recognition via browser agent configuration)
• Support roles: managers of the groups can add resources to the directory, members can sign up as members, anonymous can read all content
• Show activity from all groups in my own language on the portal home page
• Directory of OSUGroups, with geographic representation (be able to view the groups on a map and display also the full list of groups on a page)
• Manage content (pages) of generic interest (to host content like how to start a group, general, policies, trademark stuff, generic icons, etc)

Per each user group:

• allow users to add events, each group will expose its ical feed
• show to list additional resources for the group: mailing lists, forums, wiki pages, home page, url of blogs,
• import RSS feed from blogs to aggregate content on groups page
• display photostreams from flickr and such on the home page

Open questions

• is this all we need?
• do we want to host and provide web apps for any of the local groups (mlists, blog, forums, etc)? And if yes, should these be part of the such portal?
• can we reuse code from Ubuntu Loco portal? The code is tightly integrated in Launchpad, local teams need to be created as Launchpad Teams, it uses Launchpad as OpenID provider (bugs included). But it’s already there, it’s fairly simple and it’s a django app
• What other tools can we use for this and do you volunteer to manage such tool?

I’m interested in your opinions: join the OpenStack International Community Team on Launchpad  to discuss this further.

Stef for ][ stefano maffulli, 2012. | Permalink | One comment
Post tags: community, growth, international, openstack, user groups

Following up on the discussion held at the Design Summit, Thierry suggested to split the Mailing-list in order to improve the communication among developers and users. The proposal requires a significant change in the current workflow for developers and adds a new burden on the infrastructure team.  A reason to be proud of this community is that the infrastructure team didn’t say ‘no’ like many IT shops would. They highlighted what they needed in order to do a good job satisfying the request. A volunteer jumped up to help (thank you Duncan) and off we go to do something without wasting time debating. This community is effective and gets things done.

Stef for ][ stefano maffulli, 2012. | Permalink | No comment
Post tags: community, openstack

The infrastructure is amazing! The networking is astonishingly good. I learned that the Ubuntu team bypasses the usually lame the Internet connections provided by the hotels and puts down their own. Ubuntu’s wifi was gratis, easy to join and always on! By comparison, the access provided by the hotel was mostly down and costed $10 per day.

The participation is insane! Not only Canonical employees participate to the summit but also volunteers from around the world. In Orlando there were around 700 people all interested in making Ubuntu the greatest operating system in the world.

OpenStack is everywhere! Three plenary sessions were dedicated to OpenStack and many sessions of the summit had to do with it. Canonical is putting lots of energy into making OpenStack its cloud. Mark Shuttleworth in one of these sessions made it also clear that he wants to provide resources for OpenStack to maintain compatibility Amazon’s API.

Rackspace distributed the coolest t-shirts at the event: we ran out of three full boxes in a few minutes.

The pace of the summit was not as mad as I imagined after looking at the schedule. Even if there are many parallel tracks from 9am to 6pm for five full days, I ended up with plenty of time free to meet people and talk with them. Sharing the same hotel with a big swimming pool and very nice weather probably helped the conversations. I enjoyed also the free buses available to go out in large groups.

All in all, it was great to be there since OpenStack Developer Summit is modelled after UDS.

Stef for ][ stefano maffulli, 2011. | Permalink | No comment
Post tags: community, meeting, summit, ubuntu, uds

I’ve been hearing this story of the universal operating system many times in the past 20 years and nobody has managed to come up with one. I’ve seen the failure of LiMo, Maemo and Meego later (not Tizen), WebOS and more in direct competition with iOS and Android on the mobile/embedded space. Mark may succeed where others have failed.

Stef for ][ stefano maffulli, 2011. | Permalink | One comment
Post tags: community, developers, ubuntu, uds