The Slack-IRC gateway is a trick to lock-in customers

Well, here is another reason to resist using Slack:

[…]when you use /me on the IRC gateway while in private chat with someone, Slack just drops the message on the floor and doesn’t deliver it!

The company brags about their IRC gateway to lure in more groups and teams, but Slack and IRC are two totally different beasts: there will always be an increasing amount of pieces that get lost in translation.

The Slack-IRC gateway is just a trick to lock more users into the walled garden. Resist!

Source: rjbs’s rubric: The Slack IRC gateway drops your messages.

How To Use Vagrant And Git To Develop A WordPress Theme

 

Sometimes I like to sit down and play with technology. My colleague Mike Shroder mentioned VVV a few weeks ago and I had to try it. Check out this tutorial I wrote on how to create a new WordPress site, use Vagrant and git to develop a new theme locally, then push the modifications to a live site running on DreamHost (but it could run anywhere else, really).

Source: How To Use Vagrant And Git To Develop A WordPress Theme

Why the OpenStack community voting process fails and how to fix it

Open source communities offer a lot of democratic participation. The idea that you contribute to a project and have a say in its governance is a powerful one.  When it doesn’t work, those same projects turn their backs on active contributors and discourage newcomers. The most recent OpenStack elections for Individual members to the Board of Directors is a strong example of how community voting fails and how to fix it.

This time I watched the elections from the distance, as much of an outsider as I have ever been. Now that the results are in, I’m very disappointed to see confirmed four Individual board members — half of the total — whose inaction during 2016 should have not granted them reconfirmation.

It’s also extremely sad to see more than a few very active individuals have not been elected.  Of the eight elected, only one works for a smaller company and only one is mostly an OpenStack user (seven are primarily OpenStack vendors). The Individual members of the OpenStack Foundation were added to the bylaws to keep large corporate interests in check, and clearly this doesn’t seem to be working.

The OpenStack community has a huge problem here: good behavior and personal investments to improve the project don’t get rewarded. On the contrary, affiliation with large companies, spammy promotion, and geographic proximity seem to be more effective at granting a seat on the board. This has discouraged participation already, as some backchannel conversations have confirmed. You have to ask yourself, why would someone like Edgar Magana do what he has done for the short time he’s been on the board, when almost-inactive members get the votes?

A couple of immediate actions can be taken to improve the situation. First, acknowledge that an issue exists at the Board level, where too few small organizations and users are represented. Then, stop tolerating abuse of community resources like planet.openstack.org and use of the OpenStack logo. Actions should have followed OpenStack Foundation’s COO Mark Collier reminder to be nice during the campaign. Mark wrote:

With respect to local user groups and web channels, I think they should remain neutral ground that are open to all local community members.

But then the OpenStack logo (that’s another problem, known and unsolved for many years) was used to promote a single candidate as ‘our APAC‘ candidate. Who’s we exactly? OpenStack AU with the logo of the OpenStack Foundation? From my cursory glance at the candidates, there were others in APAC region, but I bet those candidates didn’t have direct access to the OpenStack AU Twitter feed.

OpenStack Australia suggesting to vote for Kavit as 'our APAC candidate'

And the shared Planet OpenStack (which is syndicated to Reddit and other places) was inundated for a week by the same advertising. My attempt to limit the damage to the community and send a signal was blocked.

One more thing: make the pages of the candidates more meaningful. They’re too wordy now, start with the generic bio and offer no link to hard facts. How many of the 3,000 voters actually read their pages (I bet they don’t, and we can easily find out with Google Analytics)? Members pages should show facts, not generic intention to make the world a better place. I always had the vision to collect data from analytics tools and show those in the individual member pages. Stackalytics already offers a pretty comprehensive view of what each person does, not just code-relate but emails, translations, work on bugs, and I bet more can be added from OpenStack Groups portal.

Communities need constant supervision and nurturing, they can’t be left unattended because as quickly as they have formed, they fall apart or at the very least lose critical focus. OpenStack is under tremendous pressure and now more than ever needs dedicated contributors to keep the project at the center of attention.

Wix fights against the GNU GPL creating another license

First Wix took code licensed under the GNU GPL, used it to enhance their code and shipped the combined work under a license not compatible with the GNU GPL, violating the rights of copyright holder Automattic.

Now, they’ve taken code distributed under the MIT license, very permissive, and relicensed under a new license they created ad-hoc. They call the new license “The Enhanced MIT License”, which is exactly like the MIT License, with one exception:

Any distribution of this source code or any modification thereof in source code format, must be done under the Enhanced MIT license and not under any other licenses, such as GPL.

The license file is basically a political manifesto against the copyleft licenses (like the GNU GPL), where they use the derogatory adjective ‘viral’ to describe the persistent nature of the four freedoms granted by the license.

Does this EMIT license conform to the definition of open source? Maybe… but my smell test says this is a messy license.  In the “Official wording” section (the part in legalese) I read:

the licensee is prohibited to change the license of the Software to any “viral” copyleft-type license

But in the FAQ above they say:

if you add/change the source code, the license must be kept as Enhanced MIT license.

which is not the same thing. Has this been reviewed by an attorney? Until it has, I wouldn’t touch this code with a 10-foot pole.

Source: Wix abandons WordPress GPL editor fork in favour of original MIT library – blocks relicensing | React, etc. Tech Stack

Medium is “pivoting”

I’m glad to read Ev Williams finally admitting that:

the broken system is ad-driven media on the internet. It simply doesn’t serve people. In fact, it’s not designed to.

He’s a smart person, I’m sure the next iteration of Medium will be interesting, no matter what the outcome will be.

Source: Renewing Medium’s focus

Prototyping applications with Airtable

Gotta say: using spreadsheet as poor-man’s database makes me feel poor every time. Google Sheets is so convenient that everybody starts a new sheet to hold some information in a table. The problem is, sheets are so convenient that some sheets keep on starting again, and again. Soon the company has 20 sheets holding bad information. It’s the tragedy of the corporate wikis all over again.

Instead I’m one of the few who used to love Microsoft Access: I know, it’s bad as a database but to rapidly prototyping small applications it was awesome. As a poor-mans database, Access was at least credit-worthy compared to spreadsheets.

Unfortunately Google doesn’t have something similar to MS Access so when I discovered Airtable, I got really happy. I’ve prototyped a small application to keep track of conferences and call for papers. Finally I don’t have to keep entering the same data every year in a new sheet and I can keep tables in fairly normalized form. Nice stuff. I wish Google Apps buys it … and the cynical in me says: “so we can have dozens of similar databases instead of hundreds of similar spreadsheets (the same tragedy, at a smaller scale).”

“Do not feed the troll” is still the best advice

Feels like an innocent request from Techdirt:

Do you have examples of communities or individuals coming up with unique, creative or innovative ways to respond to hateful, abusive or trollish speech?

but I still think silence is the best response. Block and report the trolls to the authorities because engaging in any ways with them will only make things worse.

The old advice “Don’t feed the troll!” is still the best advice.

Why you should not use Slack for volunteer communities

Last night I was asked again to join a Slack channel during a community event and I lost it. I lost the patience for this constant push into a walled garden. I can accept that only at work. I don’t want my email to be given away to a company so they can brag about their growth rate… and for what in exchange? More work for me to signup, pay attention to terms of service, unsubscribe, remove notifications…

No! No! and NO! Community managers, don’t use Slack and please note:

  • It’s tacky to ask volunteers to surrender their email address to a third party who will use to send “occasionally” unrequested “news and announcements”. No, thank you.
  • It’s annoying to force your volunteers to signup for yet another service. Click click click click email click-verify tutorial etc. No, thank you.
  • It’s wrong to archive your volunteers conversations and credentials in a big fat place where the next criminal will grab them. Because you know it will eventually happen, right? No, thank you.

Slack works so well in work environment because it keeps history, it’s very good on mobile, its notifications can be fine tuned… it’s pervasive, and very effective… at work! But the last thing I want as a volunteer is to spend time to fine tune notifications for each and every group I join.

Also, you can’t expect volunteers to keep up with the history of a channel (hey, hello, hi, wazzup, thank you, great, awesome, gif, gif gif… ), so that Slack feature is not useful.  As a community manager, you should know that there is always one that abuses of the @here @channel @all shortcuts to ask moronic “support” questions in the most populated #general channel. There you have your daily “@all it doesn’t work!” even if there is a channel called #support.

Buzz off, and RTFM! I said it!

There are better ways, not intrusive, easy to start and quit when the meeting is done. Etherpads have chat: do the volunteer work, take notes, share links on the chat. If etherpad is too complicated, I’d accept Google Docs.

Do you just need a temporary channel to chat? Just create one on the fly with freenode web chat, mibbit or any other IRC on web. Hit it and quit it: chances are, the archives of your meeting are not going to be read by anybody anyway. Let your community focus on the asynchronous systems: email works well, forums, comments on your website etc.

You should not give away your community members : they’re not yours to give, in the first place!

VCs who miss the point of open source shouldn’t fund it | InfoWorld

People who believe that Apache is a competitor, OSI approves licenses that permit monopolization, Red Hat is a business that’s succeeded through artificial scarcity, and open source communities with diverse agendas are “broken” are not the people you want in your new open source business.

Well said. Via Simon Phipps on http://www.infoworld.com/article/3032120/open-source-tools/vcs-who-miss-the-point-of-open-source-shouldnt-fund-it.html