Difference between revisions of "Edwin Mons Application 2010"

From XMPP WIKI
Jump to navigation Jump to search
(New page: My name is Edwin Mons ([xmpp:intosi@ik.nu intosi]) and I'm applying to retain my XSF membership. ==History== Until the end of July, I'm working as a server architect for iRex Technologies...)
 
Line 1: Line 1:
My name is Edwin Mons ([xmpp:intosi@ik.nu intosi]) and I'm applying to retain my XSF membership.
+
My name is Edwin Mons ([xmpp:intosi@ik.nu intosi], [mailto:intosi@ik.nu]) and I'm applying to retain my XSF membership.
  
 
==History==
 
==History==
Line 9: Line 9:
 
When the infrastructure team (iteam) was started last year, I quickly applied for that team.  I'm currently handling DNS and mail-related issues.
 
When the infrastructure team (iteam) was started last year, I quickly applied for that team.  I'm currently handling DNS and mail-related issues.
  
===Plans for the future===
+
==Plans for the future==
 
I'll probably be entertaining the people at FOSDEM next year at the XSF booth, if you're all willing to let me do it again.
 
I'll probably be entertaining the people at FOSDEM next year at the XSF booth, if you're all willing to let me do it again.
  

Revision as of 12:18, 19 July 2010

My name is Edwin Mons (intosi, [1]) and I'm applying to retain my XSF membership.

History

Until the end of July, I'm working as a server architect for iRex Technologies. I got interested in Jabber via Ralph very early on, but only decided to enter the (then) JSF in 2004, after a few people asked me why I was manning a Jabber Software Foundation booth at FOSDEM while I was no JSF member at all ;)

Jabber/XMPP Projects

In my job as server architect, I try to introduce Jabber/XMPP on every level it's technically feasible. Past projects include a data synchronization tool using pub/sub and content notifications via xmpp. Several of our new server applications use Jabber-RPC interfaces, and several new key components will use XMPP for event notifications. I also maintain the corporate Openfire server. In private projects, I try to use as much jabber-related techniques as well. Nothing too exiting, just plain notification of changes and/or database mutations, test driving XMPP server and client implementations.

When the infrastructure team (iteam) was started last year, I quickly applied for that team. I'm currently handling DNS and mail-related issues.

Plans for the future

I'll probably be entertaining the people at FOSDEM next year at the XSF booth, if you're all willing to let me do it again.

More activities in the infrastructure team of the XSF.

Apart from that, I'm advocating XMPP to everyone who dares to talk to me using proprietary protocols. But then again, who in the XSF isn't?

Why I'm reapplying

I really like the XSF, and I feel it's important to have such a body for XMPP. Leveraging business interest is still very important, although I feel we should at least partially focus on end-user features, as well. I also want to be active in the iteam, and I'll need to be an XSF member for that.