GENEALOGY-DNA-L ArchivesArchiver > GENEALOGY-DNA > 2011-11 > 1320489790
From: Jim Bartlett <>
Subject: Re: [DNA] Problems with some surname project admins
Date: Sat, 05 Nov 2011 06:43:10 -0400
References: <firstname.lastname@example.org> <4EAF2020.email@example.com><firstname.lastname@example.org><201111011407.pA1E7pHf011305@mail.rootsweb.com><201111050141.pA51ffjK031722@mail.rootsweb.com><8D202C82-550B-4AB6-B041-0FB4640850FB@gmail.com><00b601cc9b7f$335b11e0$9a1135a0$@com>
Start with an objective statement.
Such as: Create a brief set of Administrator guidelines to recruit participants, help people understand DNA as a genealogy tool, purchase tests, interpret results, and display matching results with some method of identifying the Patriarchal surname lines to which they belong.
Try it - an objective statement is hard to write, harder to get agreement, but essential as a common goal - otherwise everyone heads in their own direction.
I would not ask FTDNA to track metrics (each DNA project is different, and need not comply with standards); but FTDNA could be a little more willing to look into complaints of project participants.
Jim - Sent from my iPhone - FaceTime!
On Nov 5, 2011, at 1:53 AM, "Bob May" <> wrote:
> Lisa wrote :-
> " Would it make sense to establish a set of (really really) minimum admin
> requirements? I'm not sure, just wondering. A couple-few things which it
> would be easy for FTDNA to track? Things which might trigger an intervention
> What about a set of guidelines from those running good projects as a guide
> to someone just starting up a project or taking one over?
> This then could also fill the requirement that Lisa signals
|Re: [DNA] Problems with some surname project admins by Jim Bartlett <>|