I like.
I also like the suggestion to clearly define the roles of each of the
titles.
If a person doesn't know precisely what is expected of him, that sometimes
will doom him or her to failure. Instead, if we clearly lay out what is
needed for a particular spot in that grid, it makes it much easier for
someone to look at the requirements and say "I can" or "I can't".
I also think that task delegation is important as well, but I'm nowhere near
smart enough to solve that one alone. Maybe dialog about that? Does the SF
bug tracking mechanism allow delegation from the admin level to specific
team members?
I can also offer end-user support. As I would be digging into documentation
(probably more deeply than I've ever done before! LOL), I think that I'd be
a good candidate to provide the support buffer between developers and users
(and could certainly use help in that area as well)
I guess it's time to dust off my LaTex chops.
---
Jerald M. Sheets jr.
On Thu, Jul 1, 2010 at 12:48 PM, TJ Yang <user-61afc885aa73@xymon.invalid> wrote:
Before a new admin is chosen, I think it would be a good idea to create a
list of the tasks and responsibilities that the volunteer(s) would be
taking
on. It doesn't have to be a complete list, but just something that
covers
the major points. If you want to be an active developer (and I hope that
you do, as you know the code better than anyone and can help others get
up
to speed), it would be nice to know what the admin(s) should be helping
you
with.
How about this ?
http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Developer_Guide#Xymon_volunteers_resource_allocation
If no objection, I will put in more effort complete the table.
tj
Tom
--
T.J. Yang