DavorOcelic, HCOOP Inc. System Administrator and Board of Directors member.

1. System administrator position

One year ago

• we were still using our now-old server (fyodor.hcoop.net)
• we were a little more than half the current size (currently: 110 members)

• more of us were visiting #hcoop channel at the FreeNode IRC network (irc.gnu.org server, for example)

• more manual user-to-admin communication was required

Today, things are looking different. We have a new infrastructure to which the official migration has begun

• new 2 servers + old Abulafia
• a nice member base (kind greeting to everyone who joined!)

• an extraordinary members portal ([http://members.hcoop.net/] - all Domtool and Portal fame richly deserved by AdamChlipala), and the new wiki ([http://wiki.hcoop.net/])

As far as our current technology and my system administrator position at HCOOP are concerned, in 2007 I plan to:

• continue with the current, usual system administration tasks
• improve on the security infrastructure
• develop a global (authentication and other) infrastructure for all HCoop servers
• as always, help with any tasks that pop up

As mentioned, we are switching to the new infrastructure. The areas I take care of can be seen on the TaskDistribution page.

I would like to thank Justin Leitgeb, Ray Racine, Shaun Empie and Adam Megacz for valuable hardware donations that made the next round of HCoop expansion much easier in all aspects! See NewSystemHardware.

2. Board of Directors position

I should also give you a word on the nature of the Board of Directors position within HCoop, Inc. HCoop is democratic in its roots, thanks to the original principles set by Adam Chlipala. The power is held within the member base, and ultimately within the Board of Directors (see our HcoopBylaws page).

So the Board of Directors (BoD) position has a few specifics:

• the number of directors is very small (only three of all members, although with plans to increase that number to five)
• each directors is worth a whole 33.3%, and two-thirds of the board can take immediate action
• the number of directors will not grow linearly with the number of HCoop members
• the position requires combination of both management and technical abilities. Management will be gaining importance over technical ability as we continue to improve our hands-free systems infrastructure, and as we get to accept more and more members

I think it is important that you pay close attention to the Board being a "good balance of skills, geographic locations, and personalities" (quoting NathanKennedy).

3. Board of Directors position (2007)

I would like to thank everyone who voted for me on our third BoD HCOOP elections (see ["Election2007"]).

4. Board of Directors position (2006)

I would like to thank everyone who voted for me on our second BoD HCOOP elections (see ["Election2006"]).

5. Board of Directors position (2005)

I would like to thank everyone who voted for me on our first BoD HCOOP elections (see ["Election2005"]).

Close to what I initially predicted, our first year was marked mostly by advances in the system setup. On a parallel front, NathanKennedy was working on issues related to our legal status (see [http://hcoop.net/board/]).

Few members-related issues did pop up, but nothing that would require the Board to meet outside of the scheduled meetings.

6. Other

Pointers to various projects I'm involved with:

• [http://www.spinlocksolutions.com/ Spinlock Solutions], my company website

• [http://www.icdevgroup.org/ Interchange Development Group], powerful e-commerce solution and general-purpose platform