welcome: please sign in

The following 721 words could not be found in the dictionary of 7 words (including 7 LocalSpellingWords) and are highlighted below:
ability   able   about   access   accessible   accomplish   accomplished   accounting   accurate   achievable   achieving   acquire   active   actual   actually   Adam   address   admin   Administration   administrator   admins   adminstration   admit   afford   affordable   afloat   after   After   again   agent   aggressively   aging   ago   all   Allocate   allow   allowing   along   Already   already   also   an   and   another   any   anything   appears   are   around   arrangements   as   As   Aside   assist   assistance   at   At   atop   attempt   attempted   attention   attract   attracting   attrition   audit   August   authorize   authorized   Automated   automated   automatically   automating   available   away   back   bandwidth   bank   base   be   because   become   becoming   been   before   begin   behind   Being   being   benefit   better   beyond   bills   bit   Board   board   books   bring   budget   burden   burnout   busy   but   button   by   can   carried   case   cat   center   central   certificates   certs   changing   cheaper   Chlipala   clean   clicking   close   cloud   colo   com   comfortably   command   commonly   competent   completely   complicated   Config   consistently   Contents   continue   continued   convince   coop   Coop   cost   could   couple   Create   crossroads   csv   current   Currently   custom   daemon   daily   Darst   data   database   databases   date   Davor   Day   days   dead   decade   decided   decline   default   delays   deleuze   delivery   departing   design   did   disrepair   ditching   dns   docelic   documenting   does   doing   Dom   don   done   down   draft   dues   During   during   duties   each   easier   easy   effective   effectively   effort   elected   election   Election   else   empties   enhance   enough   ensure   enter   entered   entering   entirely   especially   essential   etc   even   events   every   everyone   excellent   except   expand   expanded   Expanding   expanding   expenses   expensive   explore   facing   failing   failure   failures   fall   fallen   familiar   far   few   file   filtering   finally   Finally   Financial   financial   financially   find   Finish   finish   firewall   first   Fix   flexibility   flirted   fly   focus   folder   folks   For   for   forced   form   formal   four   fresh   friend   fritz   from   From   fully   functioning   funds   future   fyodor   get   Get   gets   getting   give   given   giving   go   goal   goals   going   got   gotten   gracefully   granting   group   growing   half   handle   hardware   Hardware   has   have   haven   having   hcoop   Hcoop   help   helpful   herder   his   hit   hope   hopefully   hopes   hopper   hosting   however   https   ideal   ideally   identity   if   If   Implement   implications   import   Improve   improved   improvement   improvements   in   inactive   increased   increasing   information   infrastructure   Install   instead   intended   intent   interface   interrupting   into   involved   is   issues   it   It   itself   join   joined   joining   keep   keeping   knew   known   last   Lauren   least   leave   leaving   led   less   letsencrypt   levels   liberate   libvirt   life   like   limits   line   live   ll   long   longer   look   looks   losing   lost   love   lower   machine   made   mail   main   mainly   maintainable   maintainer   maintenance   make   Make   making   managed   management   manner   manual   many   Mc   me   measure   Member   member   members   membership   menial   might   migration   mind   mire   missing   modern   modernized   modestly   month   months   more   mostly   much   multiple   mused   mwolson   My   my   myself   near   need   needed   needing   needs   Nees   neglected   net   new   next   nextcloud   no   non   not   nothing   now   obsolete   occasional   occurred   Ocelic   Of   of   off   offer   offered   officer   on   One   one   ones   online   only   onto   operate   operating   option   or   order   Organize   other   others   ought   Our   our   out   outsiders   over   Over   own   Packages   paid   part   party   past   payment   payments   Paypal   people   per   perform   person   personal   phase   physical   place   Platform   pledges   plenty   point   polish   pool   portal   ports   position   potential   pre   President   pretty   prevent   previous   primary   priority   problems   procedures   process   procured   productive   projects   proprietary   provide   providers   public   Publish   Puppet   put   puts   quiet   quite   rack   raise   raising   re   read   ready   realize   realized   really   reasonable   reasonably   recently   records   recurring   redesign   redundant   registered   registrar   regrew   regular   relied   remove   Remove   replace   replacement   residual   resources   responsibilities   restored   result   resulted   retiring   returning   reversed   Richard   Right   right   role   runaway   running   scenes   secretary   see   seemed   seems   self   semi   server   service   services   serving   Setting   setup   several   shared   shell   shifting   should   sign   signed   similar   simply   since   single   sit   situation   six   slight   slow   slowly   small   so   software   solutions   some   someone   soon   sorely   spam   spare   speed   stability   stabilize   stabilized   stable   Start   start   starting   startssl   Statement   step   still   stock   storage   straightforward   Stripe   structure   succeeded   success   Successes   successfully   such   suck   suffered   supervision   support   survived   suspect   sysadmin   system   System   Table   take   task   tasks   team   technical   temporary   term   than   thanks   that   The   the   their   them   There   there   these   things   think   third   this   This   three   thrive   thus   time   times   to   tolerable   ton   too   took   tool   Tool   Transition   transitioned   transitioning   treasurer   treasurers   treasury   truly   Trusted   trusted   two   unable   uncommon   under   underutilized   unfortunately   unrealistic   untenable   until   up   update   upgrade   upon   us   usable   used   user   users   uses   ve   verification   very   virtual   virtualized   visits   vmail   volumes   volunteer   Volunteer   volunteering   volunteers   vps   want   was   way   We   we   web   website   well   Well   were   what   Wheezy   where   which   while   will   wishes   With   with   within   without   wordpress   work   worse   worthwhile   would   xanadu   year   years   yet   you   zero  

Clear message
Edit

ClintonEbadi / BoardStatements

1. 2018 Board Statement

draft

Well, it's 2018 already... for this term, if elected, I have a few straightforward goals, mostly carried over from 2016:

I was not as productive as I ought to have been for the last couple of years, which (along with I think times changing, with vps hosting even cheaper than the coop and giving you more resources) has led to us not doing too well. At our current membership levels, we are unable to afford our current hosting arrangements...

As a result, my primary focus will be on ditching our failing hardware setup and expensive, underutilized colo setup onto virtualized hardware. This does not close us off from returning to physical hardware in the future if we regrew to membership levels where we can truly afford it -- we really haven't been able to for years, having no budget for replacement hardware.

After that is accomplished (ideally within 60 days of the election), my intent would be to focus on transitioning away from board responsibilities. The last few years have been quite busy, and I've flirted with burnout, leaving the structure of the coop neglected. We've gotten off to a slow start, but I think the goal of making me redundant within a year, and able to leave the board entirely to others in two, is finally achievable.

Aside from that, I want to focus on non-board duties. We sorely need to make our infrastructure more accessible to new users and new admins. The migration to libvirt on fritz a few years ago got us half way there for admins, and this migration should allow us to get pretty close to all the way (e.g. ditching uncommon solutions like ConfigPackages for more commonly known ones like Puppet). There has already been some success in the last year with transitioning daily sysadmin duties away from me.

For new members, there are a ton of small polish projects I'd love to focus on, e.g. letsencrypt support, better default mail filtering (everyone gets a spam folder that empties itself by default), improved vmail support, new semi-managed services for less technical users (nextcloud, automated wordpress management, ...). Being able to offer more storage and having more available bandwidth, along with the ability to expand server resources on the fly thanks to virtual hosting, will I hope position us better to offer services that liberate people from proprietary cloud services.

2. 2016 Board Statement

If elected, my primary goals for this board term are to finish automating away treasurer duties, finally import the missing expenses from the bank into the portal (we still have records, but in csv), acquire new hardware and clean the server rack up, and begin work on shifting more responsibilities to others. I would like this to be my last term as an officer, and (if elected another time) sit on the board simply as a regular member for one more term before "retiring" from the board. It seems after all these years my life is finally busy enough that I can no longer give the coop the attention it needs and really need to focus on getting others involved and up to speed more than anything else so that it can thrive without me.

3. 2014 Board Statement

draft

3.1. 2012/2013 Successes

2012 was a pretty quiet year for the coop: services were reasonably stable (if out-of-date), we successfully transitioned to a new treasurer, and stability seemed restored. We even survived AdamChlipala departing from the board. Member attrition unfortunately continued, but behind the scenes much effort was put into making our infrastructure maintainable again.

During 2013, the previous year of work was realized and our infrastructure was finally modernized. We are down to only one obsolete machine (deleuze), and all member facing services are running on reasonably modern Debian. Our AutomatedSystemInstall and our custom software are ready for an upgrade to Debian Wheezy already. With a RAM upgrade for fritz, the member shell/daemon VM and web serving VM are operating comfortably. The shared services offered by the coop (especially MoinMoin!) are finally managed in an easy to update manner, and we've actually been keeping them up to date!

The new website design from LaurenMcNees seems to have succeeded in making us look less dead to outsiders, and we've been slowly increasing membership (about one member every month, after accounting for members departing... even with the treasurer going AWOL again and losing several potential members during the fall).

A few members are also becoming pretty active, with an HcoopVolunteerDay recently starting. We've got two folks instead of zero with access to the data center, and it looks like we've got at least one other system administrator.

3.2. 2013 failures

The treasury has fallen into disrepair: our treasurer suffered some life events that led to us effectively operating without one a treasurer for several months. It took me far too long to admit that someone else needed to take over, and as a result we lost several potential new members and still have residual problems (bills have not been entered since last August).

This did not help with achieving the goal of 150-200 members; instead we have only modestly increased membership over the past year, and a slight decline over two years ago (however, much of that decline occurred in 2012 and was reversed in 2013).

3.3. Platform for 2014

I don't mind being President, but I think someone else could be more effective in that role. The duties of the treasurer this year will be complicated by needing to enter previous bills, perform the first audit in far too long, and attempt to raise funds for new hardware. As such, I think the burden should fall upon me. Already being forced to perform treasurer duties has resulted in improvements to the portal.

My goals for this term:

4. 2012 Board Statement

This last year HCoop has been pretty inactive. We're really doing worse than we could; I'm effectively the primary sysadmin (and I suck at it!) and cat herder (I suck at that too). It appears that AdamChlipala is leaving the board so we're at a crossroads -- we've made it about a decade in one form or another; can we keep going?

This year, hopefully with fresh board members, we can actually accomplish some of the goals I've mused about over the last three years. The first step will be to get a new members server on atop fritz (modern Debian!) and get LaurenMcNees's excellent redesign of hcoop.net online. From there our first priority has to be attracting more members in the hopes that we find a few more self-starting volunteers to enhance our infrastructure.

5. 2010 Board Statement

5.1. Hardware

We have procured a new machine and, after some delays, are near to having it online as our primary file and database server. This will allow us to handle our (finally) growing membership gracefully.

My primary hardware goal for 2010 is to make our central services redundant. At the very least allowing mail delivery, databases, and read-only AFS volumes for all users to continue functioning in case of the failure of one machine.

5.2. System Administration

A year ago DavorOcelic was more or less our only admin, and I knew next to nothing about our setup and could perform only menial tasks under his supervision.

After a year I have become competent enough with the software HCoop uses to provide actual assistance to Davor, thus giving us two primary admins. RichardDarst has also joined the admin team and has been quite helpful with physical hardware visits and is now in our sysadmin group.

This puts us in a tolerable situation, but this is still less than ideal. Currently we are without a maintainer for DomTool or the portal as AdamChlipala (after many years of volunteering) has decided to step down from software maintenance.

Over the next year we will need to bring at least one more person onto the admin team and find a new maintainer for our custom software.

5.3. Financial

This year I was able to convince the board that $7/month dues were reasonable, and we've managed to bring HCoop to a reasonably stable financial position. We are within 20 members of being able to phase out of the dues system (intended as a temporary measure, but relied upon for far too long to keep us afloat).

My goal of expanding membership to ~300 was unrealistic last year, but now that services have stabilized and our sysadmin situation is better we have been slowly increasing membership month to month. Expanding to 200 members in 2010 would be reasonable without much effort; if we attempted to attract new members we might well hit 300 (and we have the infrastructure in place now to handle this many).

With even 200 members we will be in a position to replace our aging hardware and thus expand the available services to all members.

6. 2009 Board Election

6.1. Hardware

We should take stock of our current hardware, get hopper online soon, and see if it is worthwhile getting xanadu online for shell access.

6.2. Financial

Right now our financial situation is untenable; we have 134 members with base expenses of over $750 per month and are only able to operate because of members with multiple pledges. The active members of the coop should attempt to get a friend or two to join, and we should address any issues that would prevent someone familiar with UNIX from joining.

A goal of expanding membership to around 300 by next year seems reasonable given the hardware we own, and would put us in a position to explore things like having a part-time paid sysadmin and expanding a bit more aggressively six months to a year from now.

6.3. System Administration

The main volunteer system administrator pool should be expanded from three to four in order to replace mwolson and remove some task burden from docelic. If no one else wishes to volunteer, I should be able to assist, but it has been quite a while since I've done any system adminstration for anything other than my personal machine.

Setting up a firewall and user limits similar to what we used on fyodor is essential to expanding beyond our current membership; right now we have resources to spare and ports a plenty, but I suspect that with 300 or so members we'll be close enough to our hardware limits on at least mire that we'll need to prevent the occasional runaway process from interrupting service for other users.

ClintonEbadi/BoardStatements (last edited 2018-03-29 02:54:23 by ClintonEbadi)