Beginning March 2nd, 2020 the Mailing Lists functionality on RootsWeb will be discontinued. Users will no longer be able to send outgoing emails or accept incoming emails. Additionally, administration tools will no longer be available to list administrators and mailing lists will be put into an archival state.
Administrators may save the emails in their list prior to March 2nd. After that, mailing list archives will remain available and searchable on RootsWeb
I don't think it has to be an either/or situation. The best county sites
I've seen have BOTH types of info... transcribed data *and* a variety of
other helpful information.
Transcribing and uploading *every record* for our counties is a great goal!
Ideally, we'll all accomplish that one day. But even with an army of
volunteers working on it 24/7, this will take years! In the meantime, we
can direct people to the resources that are not yet online. Let them know
what is available, and where to find it, so they can access the records
themselves.
True, there are some folks who are unable to conduct research from anywhere
other than their home computers. But there are many people who *can* go to
libraries, Family History Centers, or even travel to the county to walk the
cemeteries and snoop around the courthouse. There are even a few nutty
folks out there who actually *like* doing that stuff! :) Until the day
comes when we have every single record online, what's wrong with providing
guidance to the many researchers who can benefit from the information?
This dosen't mean *instead of* uploading data, but *in addition* to data.
And the opposite of "data" doesn't have to mean "links" to other sites.
There's a lot we can put on our own county pages that can be extremely
helpful, such as: A list of books or published family histories - many of
which can be borrowed through interlibrary loan at any local library. An
inventory of records at the courthouse - many of which can be viewed on
microfilm at any local Family History Center. Information about county
newspapers and where to find historical issues. Tips for conducting on-site
research, for those lucky enough to be able to do so. Combined with the
transcribed records we're all working so hard on, this kind of info will
make our sites all the more helpful.
Jeanne
> This is an interesting subject. I am not trying to be argumentative with
> anyone, just running thoughts through my own my mind, and putting some of
> them out here for y'all. I guess I 'assumed' that the project, both at the
> US and state level, was all about making genealogy DATA available 'free'
for
> all researchers. Why have a site with only links? Google can uncover
waaaaay
> more current links than any one site. All one would have to do is Google
> most any subject and or name(s) and find more than you could ever find on
a
> single link site. Not just genealogy sites..."any subject" link site.
True,
> in many of our counties due to fires and other disasters, there just isn't
> much available to transcribe; even if we 'could' recruit volunteers. I can
> sympathize with this one too, I haven't been overwhelmed with volunteers
> either. *g* Though I'm extremely thankful for the few who have. I do think
> it very handy to researchers to have all the links or phone numbers and
> addresses to the local information posted in one location, like our county
> sites. We are supposed to keep the county sites updated at regular
> intervals...what does this mean 'if' we are only placing links there? Add
> more addresses or links? Just make sure the same ole ones are still
current?
> I think it good to offer the contact information for materials for sale
from
> gen. societies and other places who offer books and other items for sale,
> but many are like me and cannot afford to order all these materials, which
> may or may not have information of interest to my research. If all we are
> offering is telling folks to go to their libraries (local, state,
national)
> and archives, and NARA, and telling them where to go buy some books, and
> this type thing, and generalized ideas on how to research, why have
> individual county sites? we could have ONE site for the whole state with
all
> this contact information? Those who will do lookups for each county. And
a
> link to Google.com. *grins* Just wonderin'.
>
> Sharon
>
>
> ==== GAGEN Mailing List ====
> USGenWeb's motto is - Volunteers dedicated to free, on-line information.
>
I can only take on one new county at a time as I have it... it's taken a few
years to acquire 12 and of those, 2 I took on to "babysit" without revising
the existing site. But included in my 12 is the county I live in--and to be
honest, sometimes it's easier to find information for the counties I DON'T
live in.
In putting pointers to resources online, I attempt to tell researchers from
Japan, Germany and New Mexico how they COULD access that information from a
distance. After all, most of these people are probably NOT researching from
right within the county--right? I've also tried to get a volunteer network
for the things that cannot be accessed from a distance (although I'm not all
that successful in recruiting!). And when I say "accessed from a distance"
I don't necessarily mean via internet. I mean via telephone, fax and snail
mail.
12 sites might seem like a full time job, but 10 of my sites are identical
in format and I have 4 in the same state--so half of the information is the
same (like the state level holdings for vital statistics). I have a "shell"
to work with and as I take on each site, I transfer the old site's
information into the new and then seek out what is needed to fill in the
rest of my "shell"... and add whatever additional I can find. It takes me
about 40-60 hours to get a site reworked. Yes, I took on alot of them
during a period of unemployment... Maintaining the site is a few hours per
week for all of them (I don't have a great deal of e-mail traffic--maybe 25
e-mails per week for all combined). I don't do transcription for any of
them, although I have taken on transcribing some censuses. I leave
transcriptions to the volunteers in the USGW Archives and I try to keep up
with what's been put there to ensure I have links to that information from
the county site. Not just a link to the archive site, but in my marriages
section I have a link to the marriage license transcriptions in the
archives, etc.
Glad to see that I'm not completely "off"...!!!
--Heather Jones DeGeorge
----- Original Message -----
From: "lrober" <lrober(a)plantationcable.net>
To: <GAGEN-L(a)rootsweb.com>
Sent: Monday, February 16, 2004 3:13 PM
Subject: Re: [GAGEN] "Good" sites & goals of the project?
> You are right Heather, it is a combination of all these things that make
our
> sites beneficial to researchers. But if a researcher is in Japan, or
> Germany, or New Mexico it does little good to tell them the location of
> census, wills, or marriage records. They cannot visit the archives or
> counties. And as you say, a handful of trainscriptions will not be of
much
> help. My goal has been and will continue to be to put all county records
on
> line for each of my counties and to help researchers that ask for help.
>
> I admire your ability to coordinate 12 counties. It must be a full time
> job.
>
> Liz Robertson
> Co-Coordinator Haralson County GA
> Coordinator, Monroe County GA
>
> ----- Original Message -----
> From: "Heather J. DeGeorge" <h.degeorge(a)verizon.net>
> To: <GAGEN-L(a)rootsweb.com>
> Sent: Monday, February 16, 2004 2:23 PM
> Subject: Re: [GAGEN] "Good" sites & goals of the project?
>
>
> > Commenting on Liz's remark that nobody can do a "good" job with more
than
> 3
> > counties because you are only providing links...
> >
> > If links to online repositories and information on finding source
> documents
> > (like instructions on ordering B/M/D certs from the state including
years
> > available, fees, wait times, etc.) are not accomplishing goals of the
> > project, then what exactly IS a "good" site? One that is comprised
> > primarily of transcriptions?
> >
> > My understanding is that the goal of the project is to be an aid to
> > genealogical researchers who live in-county or on the other end of the
> > earth. Unless you are able to provide transcriptions to most or all of
> the
> > documentation available in a county, I'm not sure how you are providing
a
> > "better" site by providing a handful of transcriptions and no direction
on
> > finding the documentation for yourself. My sites are FULL of pointers
to
> > source repositories--not just hyperlinks (since many are not online) but
> > INFORMATION on where to go and how to obtain/use the sources. I am
> > constantly receiving feedback on how comprehensive my sites are... all
12
> of
> > them. These people want to find their ancestors and they are glad to go
> > searching instead of having a fraction of all the source information
> > transcribed--a handful that does not bear reference to their family.
> >
> > Perhaps I misunderstood the goals of the project...?
> >
> > And I don't think the original "A vs. B" was stated clearly enough that
we
> > knew the status quo was an option. To be honest, I have to LOOK at the
> > bylaws--I don't recall all of them otherwise... so when you ask us to
give
> a
> > preference, I don't assume there IS an existing section without hunting
> > through the bylaws to look for it. That's something I would do--but I
> don't
> > think everyone would assume "there must already be something there".
This
> > was really a question of semantics and I think it's been clarified that
we
> > have the "status quo" option!!!
> >
> > --Heather Jones DeGeorge
> > White Co.
> >
> >
> > ----- Original Message -----
> > From: "lrober" <lrober(a)plantationcable.net>
> > To: <GAGEN-L(a)rootsweb.com>
> > Sent: Sunday, February 15, 2004 2:26 PM
> > Subject: Re: [GAGEN] Membership to GAGen
> >
> >
> > > I personally am not that anxious to include HISTORICAL data other than
a
> > > brief introduction to the county. Histories of these counties have
> > already
> > > been written and most of it is on line two or three or more times. I
> > think
> > > our main purpose should be to transcribe data, upload to county pages,
> and
> > > assist researchers with genealogical data about PEOPLE.
> > >
> > > If I have to choose between A and B, I choose B simply because it
closes
> a
> > > big loop hole in the guidelines regarding the number of counties one
> > person
> > > may have. No way can one person do a good job with more than three
> > counties
> > > except provide graphics and links. They are not abiding by the
> guidelines
> > > and not accomplishing the goals of the project. If there is one vote
> per
> > > person, regardless of number of counties controlled, the purpose of
> having
> > 5
> > > or more counties is voided.
> > >
> > > Liz R.
> > >
> > >
> > > ----- Original Message -----
> > > From: "Jan Cortez" <cristian(a)netonecom.net>
> > > To: <GAGEN-L(a)rootsweb.com>
> > > Sent: Saturday, February 14, 2004 6:43 PM
> > > Subject: [GAGEN] Membership to GAGen
> > >
> > >
> > > > Am forwarding on the Membership sub-committee report worked on by
> > Virginia
> > > > and myself and looking for comment.
> > > >
> > > > Please let us know whether you prefer Plan A or B, in regard to
> council
> > > > make-up and any other comments you might have. Comments will be
> > submitted
> > > > to the committee, but, will remain anonymous.
> > > >
> > > > Thanks for any input you might give us.
> > > >
> > > > Jan
> > > >
> > > > 1. Membership.
> > > > Membership in GAGenWeb is granted to those persons who hold the
> > following
> > > > positions within GAGenWeb: State Coordinator (SC); Asst. State
> > > > Coordinator(s) (ASC); Regional Coordinators
> > > > (RC); County Coordinators (CC); Co-county Coordinators (CCC);
> Assistant
> > > > County Coordinators (ACC) and GAGenWeb Special Projects Coordinators
> > > (SPC).
> > > > [Co-county Coordinators = share equally responsibilities for
creating
> > and
> > > > uploading county pages.
> > > > Assistant County Coordinators=assist CC but not required to know
HTML.
> > > > Special Projects = Native American, African-American, Military. New
> > > Special
> > > > Projects must be approved by the CCs.
> > > > ]
> > > >
> > > > 2. GAGenWeb Council.
> > > > PLAN A.
> > > > Members of the GAGenWeb Council will be those who hold the following
> > > > positions: State Coordinator (Chairperson, with voting privileges);
> > Asst.
> > > > State Coordinator(s); Regional
> > > > Coordinators; GAGenWeb State Special Projects Coordinators (one
person
> > per
> > > > Special Project).
> > > > These are positions appointed by the SC and perform duties as
> assigned.
> > > > REMOVED FROM THIS SECTION
> > > > The GAGenWeb Council will be responsible for amending these
guidelines
> > (NO
> > > > only by the vote of the CC); settling issues brought before it by
the
> SC
> > > > (see Mediation Process); the approval of state special projects (no
by
> > all
> > > > CCs); and assisting
> > > > researchers and others who email the Council directly (This doesn't
> need
> > > to
> > > > be stated here... itwould come under assisting the SC..)
> > > >
> > > > PLAN B.
> > > > Members of the GAGenWeb Council will be those who hold the following
> > > > positions: State Coordinator (Chairperson, with voting privileges);
> > Asst.
> > > > State Coordinator(s); Regional
> > > > Coordinators; County Coordinator Representative (one from each
> > > > Region); GAGenWeb State Special Projects Coordinators (one person
per
> > > > Special Project).
> > > > The Regional Coordinator and County Coordinator Representative
elected
> > by
> > > > the CCs within the region. Special Projects Coordinator elected by
> their
> > > > Project. Asst. State Coordinator appointed by the SC.
> > > >
> > > > 3. Member Voting Privileges.
> > > > Voting rights: One vote per county or special project; no one has
more
> > > than
> > > > one vote regardless of how many positions they fill. A designated
> voting
> > > > member must be selected i.e. only one name will be on the "voter
> list".
> > > > Members must have assumed their duties three (3) months before the
> > > > state-wide election is held.
> > > > Voting privileges of GAGenWeb members for national USGenWeb
elections
> > > shall
> > > > be governed
> > > > by USGenWeb bylaws and rules.
> > > > Voter list with e-mails will be posted on the State Wide pages so
that
> > all
> > > > members may review it. RCs are responsible for quarterly roll
> > > > calls/communication to assure CCs and their e-mails are correct.
> > > > 12. Appointment of a County/Special Projects Coordinator.
> > > > A county coordinator is selected by the RC, with the SC's
> > > > approval. The Special Coordinator is selected by the SC with Council
> > > > Approval.
> > > > DELETE THIS ALTOGETHER.... Doesn't need to be in the Guidelines.
> > > > RC or SC may take any of the following into consideration:
> > > > a) the opinion of the outgoing CC or SPC.
> > > > b) the candidate's past performance in GAGenWeb.
> > > > c) the candidate's past performance in other xxGenWeb Projects.
> > > > d) the opinion of the SC or RC.
> > > > e) the opinion of the GAGenWeb Council.
> > > > ===============================
> > > > A new coordinator's responsibilities
> > > > in setting up their county page will include (in order of
importance):
> > > > a) obtain the ftp account information from the RC.
> > > > b) ask the RC if the old design has been donated to the new
> > > > coordinator's use.
> > > > c) edit the coordinator's name, email address, and copyright
> information
> > > > on each HTML page on the site, within seven days of ****obtaining
the
> > > > password*** (added).
> > > > d) informing the RC of any problems in the county changeover.
> > > > e) make any necessary page redesigns within 30 days. If the site is
> very
> > > > large, the CC should seek the RC's approval in taking more time. A
CC
> > may,
> > > > of course, make
> > > > changes s/he deems necessary and/or beneficial to the site at any
> time.
> > > > At no time will a CC maintain more than three counties within the
> > GAGenWeb
> > > > Project.
> > > > DELETE The following...as there is no CC (other than the RCs who
have
> > more
> > > > than 3)
> > > > Those CCs holding more than three counties upon the approval of
these
> > > > guidelines shall be
> > > > exempt from this rule, until such time as they maintain not more
than
> > > three
> > > > counties.
> > > >
> > > >
> > > >
> > > >
> > > > ==== GAGEN Mailing List ====
> > > > What's new on your site this month?
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > ==== GAGEN Mailing List ====
> > > Genealogy research usually begins with our great-grandparents to
> preserve
> > > the privacy of 'living persons'. If you encounter a person
searching
> > > their birth parents, the need to go to the area on the web that deals
> > > with just this type of research. Please refer them to:
> > > http://www.adoption.org
> > >
> >
> >
> >
> > ==== GAGEN Mailing List ====
> > Confused about Copyrights??? Review USGenWeb's policy on copyrights at:
> > http://www.usgenweb.org/volunteers/copyright.html
> >
> >
> >
>
>
>
>
> ==== GAGEN Mailing List ====
> Genealogy research usually begins with our great-grandparents to preserve
> the privacy of 'living persons'. If you encounter a person searching
> their birth parents, the need to go to the area on the web that deals
> with just this type of research. Please refer them to:
> http://www.adoption.org
>
>
===============================================
Report 9 of Georgia Council Discussion Summary.
February 1 - February 15, 2004.
===============================================
REMINDER: There is one month left of the six-month trial period for the
appointed County Coordinator Representative on the Georgia Council email list.
If the list monitoring is to continue, decisions need to be made soon to enable
the replacement CC or alternate list monitoring method to take effect by March
15th.
- - - - -
Continuing county adoption discussion
- - - - -
Continuing discussion on Election Committee email list
- - - - -
January Roll-call discussion
- - - - -
<End of summary for February 1-15, 2004>
The minutes of the GRC are at:
http://www.rootsweb.com/~gacolqu2/Guidelines/
The GAGenWeb Guidelines are at:
http://www.rootsweb.com/~gagenweb/guidelines.htm
For what it is worth.
I support Plan B.
Thanks.
Donald Allen
Haralson County Co-Coordinator
-----Original Message-----
From: Gloria Holback [mailto:gholback@comcast.net]
Sent: Sunday, February 15, 2004 7:55 AM
To: GAGEN-L(a)rootsweb.com
Subject: Re: [GAGEN] Membership to GAGen
neither...leave as it is Gloria
----- Original Message -----
From: "Jan Cortez" <cristian(a)netonecom.net>
To: <GAGEN-L(a)rootsweb.com>
Sent: Saturday, February 14, 2004 6:43 PM
Subject: [GAGEN] Membership to GAGen
> Am forwarding on the Membership sub-committee report worked on by Virginia
> and myself and looking for comment.
>
> Please let us know whether you prefer Plan A or B, in regard to council
> make-up and any other comments you might have. Comments will be submitted
> to the committee, but, will remain anonymous.
>
> Thanks for any input you might give us.
>
> Jan
>
> 1. Membership.
> Membership in GAGenWeb is granted to those persons who hold the following
> positions within GAGenWeb: State Coordinator (SC); Asst. State
> Coordinator(s) (ASC); Regional Coordinators
> (RC); County Coordinators (CC); Co-county Coordinators (CCC); Assistant
> County Coordinators (ACC) and GAGenWeb Special Projects Coordinators
(SPC).
> [Co-county Coordinators = share equally responsibilities for creating and
> uploading county pages.
> Assistant County Coordinators=assist CC but not required to know HTML.
> Special Projects = Native American, African-American, Military. New
Special
> Projects must be approved by the CCs.
> ]
>
> 2. GAGenWeb Council.
> PLAN A.
> Members of the GAGenWeb Council will be those who hold the following
> positions: State Coordinator (Chairperson, with voting privileges); Asst.
> State Coordinator(s); Regional
> Coordinators; GAGenWeb State Special Projects Coordinators (one person per
> Special Project).
> These are positions appointed by the SC and perform duties as assigned.
> REMOVED FROM THIS SECTION
> The GAGenWeb Council will be responsible for amending these guidelines (NO
> only by the vote of the CC); settling issues brought before it by the SC
> (see Mediation Process); the approval of state special projects (no by all
> CCs); and assisting
> researchers and others who email the Council directly (This doesn't need
to
> be stated here... itwould come under assisting the SC..)
>
> PLAN B.
> Members of the GAGenWeb Council will be those who hold the following
> positions: State Coordinator (Chairperson, with voting privileges); Asst.
> State Coordinator(s); Regional
> Coordinators; County Coordinator Representative (one from each
> Region); GAGenWeb State Special Projects Coordinators (one person per
> Special Project).
> The Regional Coordinator and County Coordinator Representative elected by
> the CCs within the region. Special Projects Coordinator elected by their
> Project. Asst. State Coordinator appointed by the SC.
>
> 3. Member Voting Privileges.
> Voting rights: One vote per county or special project; no one has more
than
> one vote regardless of how many positions they fill. A designated voting
> member must be selected i.e. only one name will be on the "voter list".
> Members must have assumed their duties three (3) months before the
> state-wide election is held.
> Voting privileges of GAGenWeb members for national USGenWeb elections
shall
> be governed
> by USGenWeb bylaws and rules.
> Voter list with e-mails will be posted on the State Wide pages so that all
> members may review it. RCs are responsible for quarterly roll
> calls/communication to assure CCs and their e-mails are correct.
> 12. Appointment of a County/Special Projects Coordinator.
> A county coordinator is selected by the RC, with the SC's
> approval. The Special Coordinator is selected by the SC with Council
> Approval.
> DELETE THIS ALTOGETHER.... Doesn't need to be in the Guidelines.
> RC or SC may take any of the following into consideration:
> a) the opinion of the outgoing CC or SPC.
> b) the candidate's past performance in GAGenWeb.
> c) the candidate's past performance in other xxGenWeb Projects.
> d) the opinion of the SC or RC.
> e) the opinion of the GAGenWeb Council.
> ===============================
> A new coordinator's responsibilities
> in setting up their county page will include (in order of importance):
> a) obtain the ftp account information from the RC.
> b) ask the RC if the old design has been donated to the new
> coordinator's use.
> c) edit the coordinator's name, email address, and copyright information
> on each HTML page on the site, within seven days of ****obtaining the
> password*** (added).
> d) informing the RC of any problems in the county changeover.
> e) make any necessary page redesigns within 30 days. If the site is very
> large, the CC should seek the RC's approval in taking more time. A CC may,
> of course, make
> changes s/he deems necessary and/or beneficial to the site at any time.
> At no time will a CC maintain more than three counties within the GAGenWeb
> Project.
> DELETE The following...as there is no CC (other than the RCs who have more
> than 3)
> Those CCs holding more than three counties upon the approval of these
> guidelines shall be
> exempt from this rule, until such time as they maintain not more than
three
> counties.
>
>
>
>
> ==== GAGEN Mailing List ====
> What's new on your site this month?
>
==== GAGEN Mailing List ====
USGenWeb's motto is - Volunteers dedicated to free, on-line information.
I personally am not that anxious to include HISTORICAL data other than a
brief introduction to the county. Histories of these counties have already
been written and most of it is on line two or three or more times. I think
our main purpose should be to transcribe data, upload to county pages, and
assist researchers with genealogical data about PEOPLE.
If I have to choose between A and B, I choose B simply because it closes a
big loop hole in the guidelines regarding the number of counties one person
may have. No way can one person do a good job with more than three counties
except provide graphics and links. They are not abiding by the guidelines
and not accomplishing the goals of the project. If there is one vote per
person, regardless of number of counties controlled, the purpose of having 5
or more counties is voided.
Liz R.
----- Original Message -----
From: "Jan Cortez" <cristian(a)netonecom.net>
To: <GAGEN-L(a)rootsweb.com>
Sent: Saturday, February 14, 2004 6:43 PM
Subject: [GAGEN] Membership to GAGen
> Am forwarding on the Membership sub-committee report worked on by Virginia
> and myself and looking for comment.
>
> Please let us know whether you prefer Plan A or B, in regard to council
> make-up and any other comments you might have. Comments will be submitted
> to the committee, but, will remain anonymous.
>
> Thanks for any input you might give us.
>
> Jan
>
> 1. Membership.
> Membership in GAGenWeb is granted to those persons who hold the following
> positions within GAGenWeb: State Coordinator (SC); Asst. State
> Coordinator(s) (ASC); Regional Coordinators
> (RC); County Coordinators (CC); Co-county Coordinators (CCC); Assistant
> County Coordinators (ACC) and GAGenWeb Special Projects Coordinators
(SPC).
> [Co-county Coordinators = share equally responsibilities for creating and
> uploading county pages.
> Assistant County Coordinators=assist CC but not required to know HTML.
> Special Projects = Native American, African-American, Military. New
Special
> Projects must be approved by the CCs.
> ]
>
> 2. GAGenWeb Council.
> PLAN A.
> Members of the GAGenWeb Council will be those who hold the following
> positions: State Coordinator (Chairperson, with voting privileges); Asst.
> State Coordinator(s); Regional
> Coordinators; GAGenWeb State Special Projects Coordinators (one person per
> Special Project).
> These are positions appointed by the SC and perform duties as assigned.
> REMOVED FROM THIS SECTION
> The GAGenWeb Council will be responsible for amending these guidelines (NO
> only by the vote of the CC); settling issues brought before it by the SC
> (see Mediation Process); the approval of state special projects (no by all
> CCs); and assisting
> researchers and others who email the Council directly (This doesn't need
to
> be stated here... itwould come under assisting the SC..)
>
> PLAN B.
> Members of the GAGenWeb Council will be those who hold the following
> positions: State Coordinator (Chairperson, with voting privileges); Asst.
> State Coordinator(s); Regional
> Coordinators; County Coordinator Representative (one from each
> Region); GAGenWeb State Special Projects Coordinators (one person per
> Special Project).
> The Regional Coordinator and County Coordinator Representative elected by
> the CCs within the region. Special Projects Coordinator elected by their
> Project. Asst. State Coordinator appointed by the SC.
>
> 3. Member Voting Privileges.
> Voting rights: One vote per county or special project; no one has more
than
> one vote regardless of how many positions they fill. A designated voting
> member must be selected i.e. only one name will be on the "voter list".
> Members must have assumed their duties three (3) months before the
> state-wide election is held.
> Voting privileges of GAGenWeb members for national USGenWeb elections
shall
> be governed
> by USGenWeb bylaws and rules.
> Voter list with e-mails will be posted on the State Wide pages so that all
> members may review it. RCs are responsible for quarterly roll
> calls/communication to assure CCs and their e-mails are correct.
> 12. Appointment of a County/Special Projects Coordinator.
> A county coordinator is selected by the RC, with the SC's
> approval. The Special Coordinator is selected by the SC with Council
> Approval.
> DELETE THIS ALTOGETHER.... Doesn't need to be in the Guidelines.
> RC or SC may take any of the following into consideration:
> a) the opinion of the outgoing CC or SPC.
> b) the candidate's past performance in GAGenWeb.
> c) the candidate's past performance in other xxGenWeb Projects.
> d) the opinion of the SC or RC.
> e) the opinion of the GAGenWeb Council.
> ===============================
> A new coordinator's responsibilities
> in setting up their county page will include (in order of importance):
> a) obtain the ftp account information from the RC.
> b) ask the RC if the old design has been donated to the new
> coordinator's use.
> c) edit the coordinator's name, email address, and copyright information
> on each HTML page on the site, within seven days of ****obtaining the
> password*** (added).
> d) informing the RC of any problems in the county changeover.
> e) make any necessary page redesigns within 30 days. If the site is very
> large, the CC should seek the RC's approval in taking more time. A CC may,
> of course, make
> changes s/he deems necessary and/or beneficial to the site at any time.
> At no time will a CC maintain more than three counties within the GAGenWeb
> Project.
> DELETE The following...as there is no CC (other than the RCs who have more
> than 3)
> Those CCs holding more than three counties upon the approval of these
> guidelines shall be
> exempt from this rule, until such time as they maintain not more than
three
> counties.
>
>
>
>
> ==== GAGEN Mailing List ====
> What's new on your site this month?
>
>
...if the council agrees to let the ccs vote?????
Down with the council! CCs rule
Michael Saffold wrote:
>
> During this comment phase of the process, any and all suggestions are
> welcome, including maintaining the status quo. After the comment phase has
> ended, the committee will submit its final report to the council. If the
> council agrees to let the CCs vote, the choice would be between the GRC's
> recommendation or the current guidelines.
>
> Vivian Price Saffold
> Meriwether County
>
> At 10:48 AM 2/15/2004 -0500, you wrote:
> >Bias comes in when there is no mention that the original guidelines are also
> >an option...and only two a and b are placed before the CCs as
> >choices...sorry if you misunderstood what I was saying. Gloria
> >----- Original Message -----
> >From: "Jan Cortez" <cristian(a)netonecom.net>
> >To: <GAGEN-L(a)rootsweb.com>
> >Sent: Sunday, February 15, 2004 10:15 AM
> >Subject: Re: [GAGEN] Biased when the original is not included.....
> >
> >
> > > Biased? I believe that the CC's have been left the current option.
> >Should
> > > both plans be voted down by the CC's, then what we currently have *is* the
> > > option. So where would that be biased?
> > >
> > > What I do think is biased, is the current guidelines that don't give the
> > > CC's an option of even voting upon *anything* until such time as it shall
> >be
> > > approved by the council. Very sad to say, I find that biased.
> > >
> > > Jan
> > >
> > >
> > > ----- Original Message -----
> > > From: "Gloria Holback" <gholback(a)comcast.net>
> > >
> > >
> > > > By omitting the bylaws/guidelines which are already in place is very
> > > biased
> > > > and does not leave the CCs an option. Seems as if it is being said
> >either
> > > > one of the other of these two plans....and that is not allowing the CCs
> > > the
> > > > option of leaving this portion of the guidelines/bylaws as they are. So
> > > that
> > > > is why I say neither of the two that Jan and Virginia have submitted.
> > > > Gloria
> > >
> > >
> > >
> > > ==== GAGEN Mailing List ====
> > > Have you added something signifigant to your website? Advertise it on
> >this
> > > list!
> > >
> >
> >
> >==== GAGEN Mailing List ====
> >This list is for volunteers of the GAGenWeb Project. If you wish to
> >address only the GAGenWeb Board, send your email to:
> > <GAGENWEB-L(a)rootsweb.com>
>
> 3570 Hildon Circle
> Chamblee, GA 30341
>
> ==== GAGEN Mailing List ====
> Have you added something signifigant to your website? Advertise it on this
> list!
--
Thomas (Tom) Hammack, Jr.
Gulfport, Mississippi
W4WLF
Bias comes in when there is no mention that the original guidelines are also
an option...and only two a and b are placed before the CCs as
choices...sorry if you misunderstood what I was saying. Gloria
----- Original Message -----
From: "Jan Cortez" <cristian(a)netonecom.net>
To: <GAGEN-L(a)rootsweb.com>
Sent: Sunday, February 15, 2004 10:15 AM
Subject: Re: [GAGEN] Biased when the original is not included.....
> Biased? I believe that the CC's have been left the current option.
Should
> both plans be voted down by the CC's, then what we currently have *is* the
> option. So where would that be biased?
>
> What I do think is biased, is the current guidelines that don't give the
> CC's an option of even voting upon *anything* until such time as it shall
be
> approved by the council. Very sad to say, I find that biased.
>
> Jan
>
>
> ----- Original Message -----
> From: "Gloria Holback" <gholback(a)comcast.net>
>
>
> > By omitting the bylaws/guidelines which are already in place is very
> biased
> > and does not leave the CCs an option. Seems as if it is being said
either
> > one of the other of these two plans....and that is not allowing the CCs
> the
> > option of leaving this portion of the guidelines/bylaws as they are. So
> that
> > is why I say neither of the two that Jan and Virginia have submitted.
> > Gloria
>
>
>
> ==== GAGEN Mailing List ====
> Have you added something signifigant to your website? Advertise it on
this
> list!
>
Biased? I believe that the CC's have been left the current option. Should
both plans be voted down by the CC's, then what we currently have *is* the
option. So where would that be biased?
What I do think is biased, is the current guidelines that don't give the
CC's an option of even voting upon *anything* until such time as it shall be
approved by the council. Very sad to say, I find that biased.
Jan
----- Original Message -----
From: "Gloria Holback" <gholback(a)comcast.net>
> By omitting the bylaws/guidelines which are already in place is very
biased
> and does not leave the CCs an option. Seems as if it is being said either
> one of the other of these two plans....and that is not allowing the CCs
the
> option of leaving this portion of the guidelines/bylaws as they are. So
that
> is why I say neither of the two that Jan and Virginia have submitted.
> Gloria
By omitting the bylaws/guidelines which are already in place is very biased
and does not leave the CCs an option. Seems as if it is being said either
one of the other of these two plans....and that is not allowing the CCs the
option of leaving this portion of the guidelines/bylaws as they are. So that
is why I say neither of the two that Jan and Virginia have submitted.
Gloria
Will Tom's suggestion be added as an option?
Also, will option C or D be "keep the current guidelines"?
As the membership has previously voted on those guidelines,
should those not also be included as an option?
Brenda Pierce
> [Original Message]
> From: Thomas Hammack, Jr. <thammack(a)datasync.com>
> To: <GAGEN-L(a)rootsweb.com>
> Date: 2/14/04 7:46:27 PM
> Subject: Re: [GAGEN] Membership to GAGen
>
> How about Plan C ... doing away with the whole darned thing!!
>
> Jan Cortez wrote:
> >
> > Am forwarding on the Membership sub-committee report worked on by
Virginia
> > and myself and looking for comment.
> >
> > Please let us know whether you prefer Plan A or B, in regard to council
> > make-up and any other comments you might have. Comments will be
submitted
> > to the committee, but, will remain anonymous.
> >
> > Thanks for any input you might give us.
> >
> > Jan
> >
> > 1. Membership.
> > Membership in GAGenWeb is granted to those persons who hold the
following
> > positions within GAGenWeb: State Coordinator (SC); Asst. State
> > Coordinator(s) (ASC); Regional Coordinators
> > (RC); County Coordinators (CC); Co-county Coordinators (CCC); Assistant
> > County Coordinators (ACC) and GAGenWeb Special Projects Coordinators
(SPC).
> > [Co-county Coordinators = share equally responsibilities for creating
and
> > uploading county pages.
> > Assistant County Coordinators=assist CC but not required to know HTML.
> > Special Projects = Native American, African-American, Military. New
Special
> > Projects must be approved by the CCs.
> > ]
> >
> > 2. GAGenWeb Council.
> > PLAN A.
> > Members of the GAGenWeb Council will be those who hold the following
> > positions: State Coordinator (Chairperson, with voting privileges);
Asst.
> > State Coordinator(s); Regional
> > Coordinators; GAGenWeb State Special Projects Coordinators (one person
per
> > Special Project).
> > These are positions appointed by the SC and perform duties as assigned.
> > REMOVED FROM THIS SECTION
> > The GAGenWeb Council will be responsible for amending these guidelines
(NO
> > only by the vote of the CC); settling issues brought before it by the SC
> > (see Mediation Process); the approval of state special projects (no by
all
> > CCs); and assisting
> > researchers and others who email the Council directly (This doesn't
need to
> > be stated here... itwould come under assisting the SC..)
> >
> > PLAN B.
> > Members of the GAGenWeb Council will be those who hold the following
> > positions: State Coordinator (Chairperson, with voting privileges);
Asst.
> > State Coordinator(s); Regional
> > Coordinators; County Coordinator Representative (one from each
> > Region); GAGenWeb State Special Projects Coordinators (one person per
> > Special Project).
> > The Regional Coordinator and County Coordinator Representative elected
by
> > the CCs within the region. Special Projects Coordinator elected by their
> > Project. Asst. State Coordinator appointed by the SC.
> >
> > 3. Member Voting Privileges.
> > Voting rights: One vote per county or special project; no one has more
than
> > one vote regardless of how many positions they fill. A designated voting
> > member must be selected i.e. only one name will be on the "voter list".
> > Members must have assumed their duties three (3) months before the
> > state-wide election is held.
> > Voting privileges of GAGenWeb members for national USGenWeb elections
shall
> > be governed
> > by USGenWeb bylaws and rules.
> > Voter list with e-mails will be posted on the State Wide pages so that
all
> > members may review it. RCs are responsible for quarterly roll
> > calls/communication to assure CCs and their e-mails are correct.
> > 12. Appointment of a County/Special Projects Coordinator.
> > A county coordinator is selected by the RC, with the SC's
> > approval. The Special Coordinator is selected by the SC with Council
> > Approval.
> > DELETE THIS ALTOGETHER.... Doesn't need to be in the Guidelines.
> > RC or SC may take any of the following into consideration:
> > a) the opinion of the outgoing CC or SPC.
> > b) the candidate's past performance in GAGenWeb.
> > c) the candidate's past performance in other xxGenWeb Projects.
> > d) the opinion of the SC or RC.
> > e) the opinion of the GAGenWeb Council.
> > ===============================
> > A new coordinator's responsibilities
> > in setting up their county page will include (in order of importance):
> > a) obtain the ftp account information from the RC.
> > b) ask the RC if the old design has been donated to the new
> > coordinator's use.
> > c) edit the coordinator's name, email address, and copyright information
> > on each HTML page on the site, within seven days of ****obtaining the
> > password*** (added).
> > d) informing the RC of any problems in the county changeover.
> > e) make any necessary page redesigns within 30 days. If the site is very
> > large, the CC should seek the RC's approval in taking more time. A CC
may,
> > of course, make
> > changes s/he deems necessary and/or beneficial to the site at any time.
> > At no time will a CC maintain more than three counties within the
GAGenWeb
> > Project.
> > DELETE The following...as there is no CC (other than the RCs who have
more
> > than 3)
> > Those CCs holding more than three counties upon the approval of these
> > guidelines shall be
> > exempt from this rule, until such time as they maintain not more than
three
> > counties.
> >
> > ==== GAGEN Mailing List ====
> > What's new on your site this month?
>
> --
> Thomas (Tom) Hammack, Jr.
> Gulfport, Mississippi
> W4WLF
>
>
> ==== GAGEN Mailing List ====
> This list is for volunteers of the GAGenWeb Project. If you wish to
address only the GAGenWeb Board, send your email to:
> <GAGENWEB-L(a)rootsweb.com>
Am forwarding on the Membership sub-committee report worked on by Virginia
and myself and looking for comment.
Please let us know whether you prefer Plan A or B, in regard to council
make-up and any other comments you might have. Comments will be submitted
to the committee, but, will remain anonymous.
Thanks for any input you might give us.
Jan
1. Membership.
Membership in GAGenWeb is granted to those persons who hold the following
positions within GAGenWeb: State Coordinator (SC); Asst. State
Coordinator(s) (ASC); Regional Coordinators
(RC); County Coordinators (CC); Co-county Coordinators (CCC); Assistant
County Coordinators (ACC) and GAGenWeb Special Projects Coordinators (SPC).
[Co-county Coordinators = share equally responsibilities for creating and
uploading county pages.
Assistant County Coordinators=assist CC but not required to know HTML.
Special Projects = Native American, African-American, Military. New Special
Projects must be approved by the CCs.
]
2. GAGenWeb Council.
PLAN A.
Members of the GAGenWeb Council will be those who hold the following
positions: State Coordinator (Chairperson, with voting privileges); Asst.
State Coordinator(s); Regional
Coordinators; GAGenWeb State Special Projects Coordinators (one person per
Special Project).
These are positions appointed by the SC and perform duties as assigned.
REMOVED FROM THIS SECTION
The GAGenWeb Council will be responsible for amending these guidelines (NO
only by the vote of the CC); settling issues brought before it by the SC
(see Mediation Process); the approval of state special projects (no by all
CCs); and assisting
researchers and others who email the Council directly (This doesn't need to
be stated here... itwould come under assisting the SC..)
PLAN B.
Members of the GAGenWeb Council will be those who hold the following
positions: State Coordinator (Chairperson, with voting privileges); Asst.
State Coordinator(s); Regional
Coordinators; County Coordinator Representative (one from each
Region); GAGenWeb State Special Projects Coordinators (one person per
Special Project).
The Regional Coordinator and County Coordinator Representative elected by
the CCs within the region. Special Projects Coordinator elected by their
Project. Asst. State Coordinator appointed by the SC.
3. Member Voting Privileges.
Voting rights: One vote per county or special project; no one has more than
one vote regardless of how many positions they fill. A designated voting
member must be selected i.e. only one name will be on the "voter list".
Members must have assumed their duties three (3) months before the
state-wide election is held.
Voting privileges of GAGenWeb members for national USGenWeb elections shall
be governed
by USGenWeb bylaws and rules.
Voter list with e-mails will be posted on the State Wide pages so that all
members may review it. RCs are responsible for quarterly roll
calls/communication to assure CCs and their e-mails are correct.
12. Appointment of a County/Special Projects Coordinator.
A county coordinator is selected by the RC, with the SC's
approval. The Special Coordinator is selected by the SC with Council
Approval.
DELETE THIS ALTOGETHER.... Doesn't need to be in the Guidelines.
RC or SC may take any of the following into consideration:
a) the opinion of the outgoing CC or SPC.
b) the candidate's past performance in GAGenWeb.
c) the candidate's past performance in other xxGenWeb Projects.
d) the opinion of the SC or RC.
e) the opinion of the GAGenWeb Council.
===============================
A new coordinator's responsibilities
in setting up their county page will include (in order of importance):
a) obtain the ftp account information from the RC.
b) ask the RC if the old design has been donated to the new
coordinator's use.
c) edit the coordinator's name, email address, and copyright information
on each HTML page on the site, within seven days of ****obtaining the
password*** (added).
d) informing the RC of any problems in the county changeover.
e) make any necessary page redesigns within 30 days. If the site is very
large, the CC should seek the RC's approval in taking more time. A CC may,
of course, make
changes s/he deems necessary and/or beneficial to the site at any time.
At no time will a CC maintain more than three counties within the GAGenWeb
Project.
DELETE The following...as there is no CC (other than the RCs who have more
than 3)
Those CCs holding more than three counties upon the approval of these
guidelines shall be
exempt from this rule, until such time as they maintain not more than three
counties.
How about Plan C ... doing away with the whole darned thing!!
Jan Cortez wrote:
>
> Am forwarding on the Membership sub-committee report worked on by Virginia
> and myself and looking for comment.
>
> Please let us know whether you prefer Plan A or B, in regard to council
> make-up and any other comments you might have. Comments will be submitted
> to the committee, but, will remain anonymous.
>
> Thanks for any input you might give us.
>
> Jan
>
> 1. Membership.
> Membership in GAGenWeb is granted to those persons who hold the following
> positions within GAGenWeb: State Coordinator (SC); Asst. State
> Coordinator(s) (ASC); Regional Coordinators
> (RC); County Coordinators (CC); Co-county Coordinators (CCC); Assistant
> County Coordinators (ACC) and GAGenWeb Special Projects Coordinators (SPC).
> [Co-county Coordinators = share equally responsibilities for creating and
> uploading county pages.
> Assistant County Coordinators=assist CC but not required to know HTML.
> Special Projects = Native American, African-American, Military. New Special
> Projects must be approved by the CCs.
> ]
>
> 2. GAGenWeb Council.
> PLAN A.
> Members of the GAGenWeb Council will be those who hold the following
> positions: State Coordinator (Chairperson, with voting privileges); Asst.
> State Coordinator(s); Regional
> Coordinators; GAGenWeb State Special Projects Coordinators (one person per
> Special Project).
> These are positions appointed by the SC and perform duties as assigned.
> REMOVED FROM THIS SECTION
> The GAGenWeb Council will be responsible for amending these guidelines (NO
> only by the vote of the CC); settling issues brought before it by the SC
> (see Mediation Process); the approval of state special projects (no by all
> CCs); and assisting
> researchers and others who email the Council directly (This doesn't need to
> be stated here... itwould come under assisting the SC..)
>
> PLAN B.
> Members of the GAGenWeb Council will be those who hold the following
> positions: State Coordinator (Chairperson, with voting privileges); Asst.
> State Coordinator(s); Regional
> Coordinators; County Coordinator Representative (one from each
> Region); GAGenWeb State Special Projects Coordinators (one person per
> Special Project).
> The Regional Coordinator and County Coordinator Representative elected by
> the CCs within the region. Special Projects Coordinator elected by their
> Project. Asst. State Coordinator appointed by the SC.
>
> 3. Member Voting Privileges.
> Voting rights: One vote per county or special project; no one has more than
> one vote regardless of how many positions they fill. A designated voting
> member must be selected i.e. only one name will be on the "voter list".
> Members must have assumed their duties three (3) months before the
> state-wide election is held.
> Voting privileges of GAGenWeb members for national USGenWeb elections shall
> be governed
> by USGenWeb bylaws and rules.
> Voter list with e-mails will be posted on the State Wide pages so that all
> members may review it. RCs are responsible for quarterly roll
> calls/communication to assure CCs and their e-mails are correct.
> 12. Appointment of a County/Special Projects Coordinator.
> A county coordinator is selected by the RC, with the SC's
> approval. The Special Coordinator is selected by the SC with Council
> Approval.
> DELETE THIS ALTOGETHER.... Doesn't need to be in the Guidelines.
> RC or SC may take any of the following into consideration:
> a) the opinion of the outgoing CC or SPC.
> b) the candidate's past performance in GAGenWeb.
> c) the candidate's past performance in other xxGenWeb Projects.
> d) the opinion of the SC or RC.
> e) the opinion of the GAGenWeb Council.
> ===============================
> A new coordinator's responsibilities
> in setting up their county page will include (in order of importance):
> a) obtain the ftp account information from the RC.
> b) ask the RC if the old design has been donated to the new
> coordinator's use.
> c) edit the coordinator's name, email address, and copyright information
> on each HTML page on the site, within seven days of ****obtaining the
> password*** (added).
> d) informing the RC of any problems in the county changeover.
> e) make any necessary page redesigns within 30 days. If the site is very
> large, the CC should seek the RC's approval in taking more time. A CC may,
> of course, make
> changes s/he deems necessary and/or beneficial to the site at any time.
> At no time will a CC maintain more than three counties within the GAGenWeb
> Project.
> DELETE The following...as there is no CC (other than the RCs who have more
> than 3)
> Those CCs holding more than three counties upon the approval of these
> guidelines shall be
> exempt from this rule, until such time as they maintain not more than three
> counties.
>
> ==== GAGEN Mailing List ====
> What's new on your site this month?
--
Thomas (Tom) Hammack, Jr.
Gulfport, Mississippi
W4WLF
> GALILEO has just published an addition to their web site entitled
> "Vanishing Georgia". This is a collection of approximately 18,000
> photographs of Georgia places and people, searchable by County, subject,
> etc.
The URL for the Digital Library of Georgia is: http://dlg.galileo.usg.edu/. You
can click on Online Collections & Current Projects to get a complete list of the
collections, including Vanishing Georgia. It also includes a link to Georgia
Historic Books (which contains full-text, fully searchable books related to
Georgia's history and culture).
Check it out!
Jacki
------------------------------------------------------------------
This email message was sent using web-based email services provided by Chesapeake.Net
Internet Services.
http://www.chesapeake.net/
Blank
GALILEO has just published an addition to their web site entitled
"Vanishing Georgia". This is a collection of approximately 18,000
photographs of Georgia places and people, searchable by County, subject,
etc.
I'm sure most of you have links to GALILEO but just in case the home page
is: http://www.galileo.usg.edu/cgi-bin/homepage.cgi
You may enter the "public databases" without a password but must secure a
password for others. Click the "Arts and Humanities" tab at the top: Click
#8, Georgia Department of Archives and History; Click "Search the Vanishing
Georgia Collection". Click "Search the Vanishing Georgia collection"
(again); Click 'continue" to leave state web site. Then you will be on
search page for the Vanishing Collection". Enter the county name you wish
to search in the search box and select "county" or whatever subject you wish
to search. (If you find an easier way to get there from here please let me
know).
Just thought I would share this with y'all.
Liz Robertson
Hi everyone,
I just wanted to bring you up to date on what is going on with The
USGenWeb Project Advisory Board.
A newsletter has been distributed to around 2000 project members via
email. If you haven't received one and would like to see it, please let
me know.
At some point in the near future, the newsletter will be archived here
http://www.rootsweb.com/~usgwpub/
If you would like to opt out of future issues of the newsletter please
let NC Isaiah Harrison know via this address USGenWebNews(a)cox.net.
If you received the newsletter and have ideas for future issues, please
let me know or send an email to USGenWebNews(a)cox.net.
Please remember that The USGenWeb Project's Bylaws Revision Committee is
still working on recommended changes to the bylaws. They can be viewed
here
http://home.mchsi.com/~sagitta56/
And any comments can be sent to members of the committee.
There is currently a Site Review Committee discussing the need for site
reviews within The USGenWeb Project.
http://archiver.rootsweb.com/th/read/BOARD/2004-02/1075737551
If you have any ideas or suggestions concerning this please write to me
or one of your other AB reps and let us know what you think!
Thanks!
Linda Blum-Barton
SEMA CC Rep
Hi everyone,
I just wanted to bring you up to date on what is going on with The
USGenWeb Project Advisory Board.
A newsletter has been distributed to around 2000 project members via
email. If you haven't received one and would like to see it, please let
me know.
At some point in the near future, the newsletter will be archived here
http://www.rootsweb.com/~usgwpub/
If you would like to opt out of future issues of the newsletter please
let NC Isaiah Harrison know via this address USGenWebNews(a)cox.net.
If you received the newsletter and have ideas for future issues, please
let me know or send an email to USGenWebNews(a)cox.net.
Please remember that The USGenWeb Project's Bylaws Revision Committee is
still working on recommended changes to the bylaws. They can be viewed
here
http://home.mchsi.com/~sagitta56/
And any comments can be sent to members of the committee.
There is currently a Site Review Committee discussing the need for site
reviews within The USGenWeb Project.
http://archiver.rootsweb.com/th/read/BOARD/2004-02/1075737551
If you have any ideas or suggestions concerning this please write to me
or one of your other AB reps and let us know what you think!
Thanks!
Linda Blum-Barton
SEMA CC Rep
Well I adjusted my connection time to 120 seconds, and it took exactly 2 minutes for the software to log on.
I am still experiencing problems viewing Rootsweb pages. I couldn't find my site by my direct link, but if I went through all the links from Rootsweb home page to the Glynn Site, it showed up.
I tried getting the help tab at Rootsweb, can't find the server there either. It must be a combination of my ISP and Rootsweb.
Thanks for everyone's help. I am going to email Rootsweb, whenever I can finally get the help page up, at let them know my problems.
Amy Hedrick
Glynn Co. CC
Amy,
Last night the RootsWeb HelpDesk had some note about entry pages or
something not working. It wasn't there when I checked this morn, and can't
recall exactly what it said now ;-( Maybe you could write to them using
the form at the helpdesk site for technical problems. I have done this
several times and they respond very promptly and are very kind. Maybe they
could walk you thru a solution.
Hope you get it resolved soon. It is SOOOO frustrating to be in the mood and
have your mouth set right and eveything rearing to go, to work on your site;
and then can't access!
Good Luck,
Sharon
>I tried downloading this software, and it won't connect either. Neither
will Front Page. It has to be my ISP. I know they are going to tell me that
nothing is wrong. Amy<