i know i've been a bit silent lately and i wanted to check in the let
you know what's going on.
i'm currently researching employment opportunities within and outside of
berkeley. if i decide to stay at berkeley, i will likely be moving
toward the embedded systems research here (www.tinyos.net) and moving
away from clusters/grid research. i'm also looking at opportunities at
other universities and government labs and a few large companies.
whatever my final decision, i want to make sure that ganglia is able to
continue. at every place i've interviewed thus far, i make sure to ask
about their policy regarding open source projects and have been assured
by each one that working on ganglia would not be a problem. i might not
have the time i used to have to put into it but i will make time (even
if it means giving up a little personal time).
i'd like to get feedback from you about the right process to help keep
ganglia moving forward even as my priorities might change (it's even
possible i might have MORE time for ganglia).
one of the things i feel i've failed to do adequately is to help define
a development "process" where i'm much more out of the loop (or out all
together?). i guess what i'm saying is that i'm open to any
ideas/feedback you have. i'm happy to grant admin rights to any of the
trusted developers out there who would like to take a more central role.
i know that the bugzilla database has been growing a bit lately and i
plan to get out the flyswatter and workup a new maintenance release
soon. i have also been working on rrdtool code and new PHP code for
building the next generation ganglia web console. development has been
slow lately but sure.
i'm looking forward to getting your feedback and making any changes we
need to adapt.
PGP fingerprint 'A7C2 3C2F 8445 AD3C 135E F40B 242A 5984 ACBC 91D3'
They that can give up essential liberty to obtain a little
temporary safety deserve neither liberty nor safety.
--Benjamin Franklin, Historical Review of Pennsylvania, 1759