Francois Marier: Growing the community around your new Free Software Project
Once your new Free Software project has had some traction and is gaining users, you will probably want to supplement its initial homepage with a few extra services. However, the most important aspects of managing a Free Software community have more to do with relating to human beings.
Social Interactions in Small ProjectsIn the early days of your project, support requests usually only come in through personal emails to the lead developer. In order to build your community, make sure new users feel welcome:
More Tools for Growing ProjectsAs your project grows and handling user-reported issues start becoming more of a burden, consider two things: documentation and distributed support.
The obvious place to start documentation-wise is to start collecting responses that you send to users who get in touch with you. This is the original meaning of a FAQ: answers to actual questions sent in by actual users. Fill your FAQ with irrelevant questions and users won't bother reading it and will email you instead.
In addition to providing good documentation, you should also think about creating a mailing list or a forum where users can post their questions (Google Groups provides a nice blend of the two technologies). There are two main advantages to this service:
Have a look at this excellent online book for more ideas.
Social Interactions in Small ProjectsIn the early days of your project, support requests usually only come in through personal emails to the lead developer. In order to build your community, make sure new users feel welcome:
- Be friendly and informal in your responses. Feel free to use the person's first name at the beginning of your emails.
- Be responsive to feedback and request for help. Most Free Software developers are quite busy so this is about letting user know that you'll get back to them or thanking them for their suggestions/feedback. Very few people take the time to contact authors to let them know about the problems they run into. It's important to be supportive of the ones who do.
- Be calm when responding to negative feedback. It helps to take a full day to cool off before sending a reply. Thank users for writing to you, but remind them that you are not getting paid to work on this project and that you are doing this for fun in your spare time. Some users seem to forget this.
More Tools for Growing ProjectsAs your project grows and handling user-reported issues start becoming more of a burden, consider two things: documentation and distributed support.
The obvious place to start documentation-wise is to start collecting responses that you send to users who get in touch with you. This is the original meaning of a FAQ: answers to actual questions sent in by actual users. Fill your FAQ with irrelevant questions and users won't bother reading it and will email you instead.
In addition to providing good documentation, you should also think about creating a mailing list or a forum where users can post their questions (Google Groups provides a nice blend of the two technologies). There are two main advantages to this service:
- the support load is distributed across other users of the software
- questions and answers are archived by search engines
Have a look at this excellent online book for more ideas.
So, fanatical readers of my blog (are there any?) may remember a long time back that I
I'm working on
Plus,
seeing why aptitude is actually running slowly might help when it
comes to finding ways to improve its performance.
So, this is where you come in. If you are using
After a bit of back and forth with
Async Map and Fold in JavaScript
My latest experiment is an implementation of
asynchronous/parallel "map" (and other array functions) in
JavaScript
and
I have a bit of money invested in stocks and funds, passively
managed by my bank. I ve made a bit with risky speculations, and
I ve lost about the same amount with the markets dive of the last
18 months. Net benefit: zero cash, a bit of experience. Time to
move on
I am not an interesting customer, so I was all the more
surprised to get a call from an employee of the bank the other day.
He identified himself as Crisis Manager or something similarly
ridiculous, mentioned at least 20 times that he was a regular
employee and wouldn t receive provisions, and he also kept assuring
me that he s doing himself what he s suggesting to me: leveraging
the cost-average effect.
I turned him down, probably a bit too briskily. Let s
investigate why.
Banks are good at devising ingenious tricks to fool people; it s
their business after all. One of those tricks is the so-called
cost-average effect. It s awesome, they say, because it is the
first product that adapts to the ever-changing market: when prices
are up, it buys smaller numbers of shares, and in low times, it
stocks up on them by buying larger quantities, automatically.
Fancy, no? It isn t, because the entire idea is to get your
signature on a contract that obliges you to pay a fixed sum each
month, with which shares are then bought. Obviously, when prices
are up, numbers you get for your money are low, and vice versa.
Observe how well the banks manage to turn that basic rule into a
selling point. They are good at that. In fact, that s probably all
they re good at. Obviously , inflation is also factored in, so the
monthly fixed sum actually increases by a projected 5% each year,
which they call inflation protection .
While this strategy investing fixed-sum installments rather
than lump sums certainly has its benefits, and can level out the
risk of throwing a large sum of money at the market, it is commonly
considered a suboptimal strategy, especially when employed over
longer spans of time. For more information, I refer you to the
frequently cited article
I was disappointed to read that ippimail


I've prepared a private autobuilder. As I've setup the incoming using scp, I don't need to gpg sign each package. But dupload complained saying that the package is not gpg signed. Lurking in dupload code, I found It's possible overriding the default preupload for my default host:
Have you ever thought what you send in email footer?
Given the large number of comments I got (26!), I feel obliged to post a summary of what was said.
First, the problem:
A new maintenance version of