19,206 reputation
622
bio website monkeyman.be
location Belgium
age 29
visits member for 4 years
seen Apr 23 at 18:55

I am a freelance developer, mostly web-based stuff. I don't like to re-invent the wheel, so I try to re-use existing components and focus on the problem-specific part. WordPress fits nicely into this picture, especially if you understand the inner structure.

You can contact me at [firstname.lastname] [at] monkeyman.be.

In addition to the standard Creative Commons license of this site, I give permission to use all my contributions under the GPL license (version 2). Feel free to re-use it in plugins, themes, or in the Codex.


Aug
11
awarded  Yearling
Jul
2
awarded  Curious
Jan
4
awarded  Nice Answer
Aug
11
awarded  Yearling
Dec
10
awarded  Good Question
Aug
11
awarded  Yearling
May
30
awarded  Nice Question
Oct
7
comment The functions tag seems to be misused
I think there are (some) questions that can benefit from a functions.php tag: Between functions.php, widgets and plugins, which is loaded first?, How often is functions.php loaded?, ... functions when talking about WordPress-specific functions might be better if called wp-functions. Currently I suggest breaking the synonym from functions.php to functions, and start using wp-functions. Those with courage can clean up the old functions tags.
Sep
3
awarded  discussion
Aug
12
awarded  Yearling
Jul
25
answered Is there a way to do a search on my favorite questions ?
Jul
7
awarded  Revival
Jun
13
comment License my own answers under the GPL too?
@tnorthcutt: If you dual-license your content, you give the user the option to choose one of the two licenses for your work. If they choose to use it under the GPL license, the CC BY-SA clauses don't apply, and vice-versa. So there is no conflict.
Jun
9
answered Should there be more control over links in user profiles ?
Jun
6
comment Commercial, non-GPL code: flag & support
@Chip: Though question! Good posts might be The Wikipedia of Long Tail Programming Questions and A new WordPress Stack Exchange. For the scope of this site: we as a community should define it. If we don't want answers on pro themes, that's fine. If we don't want questions about WordPress.com, that's fine. Just make sure the line is clear.
Jun
6
comment License my own answers under the GPL too?
@Chip: I don't think it is a problem that the site states all your content is CC-by-SA. It is not an exclusive license, you are free to license it again under other conditions. You just can't take anything away from the CC-by-SA freedoms.
Jun
6
comment License my own answers under the GPL too?
@EAMann: I could do this for all substantial code snippets (smaller ones will probably be just citations), but I explicitly want to allow all non-code contributions to be included in the Codex. I want to use the "fire" from this community to improve the Codex. So then I would need to add this line to all my posts?
Jun
6
comment License my own answers under the GPL too?
@Rarst: That was also my ultimate goal, but I think we can show clear community support via these individual actions. I think the Drupal SE will also be interested in this. The trick is how to deal with historical contributions: you can't re-license them without the users agreement.
Jun
6
comment License my own answers under the GPL too?
@Chip: I don't know what is the right way, but I updated the question with the notice that I currently use. Specifying "my contributions" is probably enough to make the distinction between the content from me and from other users.
Jun
6
revised License my own answers under the GPL too?
Added first attempt