Committee instructions are posted on the website at http://home.mchsi.com/~sagitta56/ > From: "Phyllis Rippee" <wchs@getgoin.net> > In accordance with Parliamentary Authority, the revised bylaws must be voted > on as a whole unit, since they will be replacing existing bylaws. > > The original charge to the Revision Committee was to "tweak" the existing > bylaws, not to rewrite them. The committee has chosen to rewrite them. > > Since it was an NC who appointed the BRC and continued by the current NC, > the report (i.e. the set of bylaws) when finalized will be presented to the > NC (whoever that is) for one of three actions: Filing away with "Thanks"; > Sending to the voters during the next regular election; Returning same to > committee and asking them to do more work on them. > > Regardless, I find these oppressive; over-stepping the bounds of "good > bylaws" suggested by parliamentary authority; taking away most freedom of > choice from the CCs, SCs or AB members. > > Does that leave any doubt as to how I'll be voting when the time comes? > > Phyllis Rippee > SW/SC CC Representative

All of this discussion brings to mind an old adage ... "Beware the Ides of March", or, in this case the Ides of ANY month. The whole project is moving dangerously close to self-destruction from within. The more restrictive 'rules' get, the greater the possibility of alienating current willing volunteers. The project has been and should always be about genealogy and not politics. Alabama won't join the political parade. Richard White ALGenWeb SC At 07:24 PM 3/10/2004 -0700, Susan Bellomo wrote: >This revision will not be well received by the CCs in New Mexico with one >possible exception. > >Helping people research their genealogy will be lost in a tidal wave of >bureaucracy. No thanks! > >Susan > >Susan Stockbridge Bellomo >http://www.rootsweb.com/~nmgenweb/ >State Coordinator, NMGenWeb >County Coordinator, Chaves, Grant and Otero Counties > >----- Original Message ----- >From: "Phyllis Rippee" <wchs@getgoin.net> >To: <STATE-COORD-L@rootsweb.com> >Sent: Wednesday, March 10, 2004 1:18 PM >Subject: [STATE-COORD] Bylaws > > >> In accordance with Parliamentary Authority, the revised bylaws must be >voted >> on as a whole unit, since they will be replacing existing bylaws. >> >> The original charge to the Revision Committee was to "tweak" the existing >> bylaws, not to rewrite them. The committee has chosen to rewrite them. >> >> Since it was an NC who appointed the BRC and continued by the current NC, >> the report (i.e. the set of bylaws) when finalized will be presented to >the >> NC (whoever that is) for one of three actions: Filing away with "Thanks"; >> Sending to the voters during the next regular election; Returning same to >> committee and asking them to do more work on them. >> >> Regardless, I find these oppressive; over-stepping the bounds of "good >> bylaws" suggested by parliamentary authority; taking away most freedom of >> choice from the CCs, SCs or AB members. >> >> Does that leave any doubt as to how I'll be voting when the time comes? >> >> Phyllis Rippee >> SW/SC CC Representative

This revision will not be well received by the CCs in New Mexico with one possible exception. Helping people research their genealogy will be lost in a tidal wave of bureaucracy. No thanks! Susan Susan Stockbridge Bellomo http://www.rootsweb.com/~nmgenweb/ State Coordinator, NMGenWeb County Coordinator, Chaves, Grant and Otero Counties ----- Original Message ----- From: "Phyllis Rippee" <wchs@getgoin.net> To: <STATE-COORD-L@rootsweb.com> Sent: Wednesday, March 10, 2004 1:18 PM Subject: [STATE-COORD] Bylaws > In accordance with Parliamentary Authority, the revised bylaws must be voted > on as a whole unit, since they will be replacing existing bylaws. > > The original charge to the Revision Committee was to "tweak" the existing > bylaws, not to rewrite them. The committee has chosen to rewrite them. > > Since it was an NC who appointed the BRC and continued by the current NC, > the report (i.e. the set of bylaws) when finalized will be presented to the > NC (whoever that is) for one of three actions: Filing away with "Thanks"; > Sending to the voters during the next regular election; Returning same to > committee and asking them to do more work on them. > > Regardless, I find these oppressive; over-stepping the bounds of "good > bylaws" suggested by parliamentary authority; taking away most freedom of > choice from the CCs, SCs or AB members. > > Does that leave any doubt as to how I'll be voting when the time comes? > > Phyllis Rippee > SW/SC CC Representative >

> Regardless, I find these oppressive; over-stepping the bounds of "good > bylaws" suggested by parliamentary authority; taking away most freedom of > choice from the CCs, SCs or AB members. > > Does that leave any doubt as to how I'll be voting when the time comes? > > Phyllis Rippee > SW/SC CC Representative > I agree with Phyllis on this one and will be voting against them unless some major revisions and deletions are made before they are presented for vote. Connie

Speaking of which, will the vote be for the bylaws as a whole, or Section by Section? I find it impossible to believe they will pass if the vote is for the whole. Even Article by Article would be difficult - Article XI being the example here. David W. Morgan wrote: > This looks like a lot of micromanagement to me. Let's vote this turkey > down and move on to something more productive. > > David > > David W. Morgan damorgan@nyx.net Honolulu Hawaii > SC - TXGenWeb http://www.rootsweb.com/~txgenweb/ > ** http://freepages.genealogy.rootsweb.com/~dmorgan/ Susan -- Coordinator Rhode Island USGenWeb ~ http://www.rootsweb.com/~rigenweb/

In accordance with Parliamentary Authority, the revised bylaws must be voted on as a whole unit, since they will be replacing existing bylaws. The original charge to the Revision Committee was to "tweak" the existing bylaws, not to rewrite them. The committee has chosen to rewrite them. Since it was an NC who appointed the BRC and continued by the current NC, the report (i.e. the set of bylaws) when finalized will be presented to the NC (whoever that is) for one of three actions: Filing away with "Thanks"; Sending to the voters during the next regular election; Returning same to committee and asking them to do more work on them. Regardless, I find these oppressive; over-stepping the bounds of "good bylaws" suggested by parliamentary authority; taking away most freedom of choice from the CCs, SCs or AB members. Does that leave any doubt as to how I'll be voting when the time comes? Phyllis Rippee SW/SC CC Representative

ARTICLE XI. STATE PROJECTS Section 1. The state web site shall include direct links to the state's local and state-level special project sites, The USGenWeb Project national site, The USGenWeb Archives (Digital Library) and other USGenWeb Special Projects' national home pages, and The USGenWeb Archives (Digital Library) and other USGenWeb Special Projects' table of contents pages for the individual state. In addition, each state web site shall provide information for current and prospective local coordinators, including but not limited to any state bylaws, guidelines and/or standards, official national and state logos, and The USGenWeb Project Guidelines/Standards and Copyright Information pages. Section 2. Each state shall have a State Coordinator (SC) elected by majority of state members voting. A State Coordinator may not serve more than 36 consecutive months unless re-elected. Each state shall hold an election for State Coordinator every 36 months, or sooner if specified by adopted state bylaws/rules.The State Coordinator, as primary administrative officer of the state project shall appoint one or more Assistant State Coordinator(s) (ASC) as necessary to assist in administration of the state project. Assistant State Coordinators who are "appointees" are not eligible to be a candidate or vote for a candidate for the national office of State Coordinator Representative. Section 3. State projects are required to comply with all USGenWeb Project bylaws, rules, and policies. State projects are encouraged to adopt additional bylaws, rules or policies, as appropriate for their state, provided they do not conflict with national bylaws, rules or policies. Section 4. State Coordinators must remain subscribed to the State Coordinator's mailing list. State Coordinator duties include, but are not limited to, oversight and maintenance of the state web site, administering the state mailing list for Local Coordinators, maintaining an up-to-date roster of names and email addresses of the state's Local Coordinators and state-level Special Project Coordinators and providing this list to the Election Committee promptly when requested, supervision of the development and implementation of state procedures for the periodic review of component websites of the state project, and promptly forwarding messages pertaining to USGenWeb Project business to the state mailing list for Local Coordinators when requested to do so by the Advisory Board Chair or the Chair of an appointed committee. Section 5. The state project has authority and responsibility to remove links to websites which fail to comply with national or state adopted bylaws, rules and policies. Notice must be given and ample time to comply must be allowed as circumstances warrant. Local Coordinator(s) may request an extension of time to comply subject to approval by the state authority. Section 6. If a State Coordinator is unable to perform his/her duties, the Assistant State Coordinator, or other support team, shall serve until an election can take place within 60 days. A majority shall elect. Section 7. State Coordinators and Assistant State Coordinators are subject to removal for valid cause; by vote of the Advisory Board, or by majority vote of the Local Coordinators within the state subsequent to a recall petition submitted to and approved by the Advisory Board. by vote of the Advisory Board? THat's it? No petition from the CCs? This looks like a lot of micromanagement to me. Let's vote this turkey down and move on to something more productive. David David W. Morgan damorgan@nyx.net Honolulu Hawaii SC - TXGenWeb http://www.rootsweb.com/~txgenweb/ ** http://freepages.genealogy.rootsweb.com/~dmorgan/

Here is the administrative contact to report any problems to. You also can contact the server which is burgoyne.com that they have rented space on, but the site is user submitted. Registrant: Find A Grave (FINDAGRAVE-DOM) PO Box 522107 Salt Lake City, UT 84152-2107 US Domain Name: FINDAGRAVE.COM Administrative Contact, Technical Contact: Tipton, Jim (JT3468) jim@FINDAGRAVE.COM Find-A-Grave PO Box 522107 Salt Lake City, UT 84152-2107 US 801/671.4677 fax: 801/581.8045 Record expires on 20-Jun-2008. Record created on 21-Jun-1997. Database last updated on 8-Mar-2004 13:53:48 EST. Domain servers in listed order: NS1.BURGOYNE.COM 209.197.0.2 NS3.BURGOYNE.COM 209.197.0.6 ----- Original Message ----- From: "Lesley Shockey" <LShockey@citynet.net> To: <STATE-COORD-L@rootsweb.com> Sent: Saturday, March 06, 2004 9:51 AM Subject: [STATE-COORD] Fwd: Copyright > Hello group, > > One of my CCs is having a problem with an outfit called FindAGrave. It > appears that they are stealing information from the USGenWeb Project pages > to build their site. > > Has anyone found a successful way to prevent these thefts? > > The CCs message is below with county name Xed out. > > Les Shockey > SC WVGenWeb > > >Les, > > Do you know what the policy of Rootsweb is as to their statement that > > anything submitted to Rootsweb is copyrighted and the property of the > > submitter? Do they do anything about someone who is stealing material > > from one of the GenWeb sites and reposting it to another site as their > > own? I am having this problem with a couple named Larry and Kim > > Weaver. They are stealing the cemetery list I have posted on the XXXXXX > > Co. site and re-posting them to another Internet database as their own > > work. Any attempt to contact them about this has been ignored. It's been > > going on for over a year, but only came to my attention several months > > ago. I have demanded they remove the names they stole from the XXXXXX > > site from this other web site known as FindAGrave. It's been several > > months now and they have done nothing. > >Will Rootsweb stand behind me and help me keep this couple from stealing > >my hard work which I have donated freely to the Project? What can I do to > >stop them from continuing to take my cemetery list and how do I make them > >remove what has already been stolen? > >I also believe they are stealing data from several other sites and I've > >have written to the webmasters there too. Do you or Val have any > >suggestions or advice for me? > > Les Shockey email address = lshockey@citynet.net > or wvgenweb@citynet.net > RootsWeb Listowner for the SHOCKEY family discussion group. > SHOCKEY-L@rootsweb.com > Visit the Jackson County, WVGenWeb Page, part of USGenWeb Project at: > http://www.rootsweb.com/~wvjackso/JACK.HTM > Visit the (West Virginia) WVGenWeb: > http://www.rootsweb.com/~wvgenweb/ > >

Lesley - Also report it to FindAGrave - see their policy at: http://findagrave.com/disclaimer.html Since their are Ancestory.com pop-ups - are you sure this isn't yet another one of their sites under a different name? R/S MAK --- Lesley Shockey <LShockey@citynet.net> wrote: > Hello group, > > One of my CCs is having a problem with an outfit called FindAGrave. It appears that they are stealing information from the USGenWeb Project pages to build their site. ===== MAKTranscriber - http://www.rootsweb.com/~wiwood http://www.rootsweb.com/~wiportag http://www.rootsweb.com/~wimonroe __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com

Is the problem with Find-a-Grave, or with the couple who is copying the info and sending it to them? A communication with the Find-a-Grave folks might put and end to this. Larry Flesher Lesley Shockey wrote: > Hello group, > > One of my CCs is having a problem with an outfit called FindAGrave. > It appears that they are stealing information from the USGenWeb > Project pages to build their site. > > Has anyone found a successful way to prevent these thefts? > > The CCs message is below with county name Xed out. > > Les Shockey > SC WVGenWeb > >> Les, >> Do you know what the policy of Rootsweb is as to their statement >> that anything submitted to Rootsweb is copyrighted and the property >> of the submitter? Do they do anything about someone who is stealing >> material from one of the GenWeb sites and reposting it to another >> site as their own? I am having this problem with a couple named >> Larry and Kim Weaver. They are stealing the cemetery list I have >> posted on the XXXXXX Co. site and re-posting them to another Internet >> database as their own work. Any attempt to contact them about this >> has been ignored. It's been going on for over a year, but only came >> to my attention several months ago. I have demanded they remove the >> names they stole from the XXXXXX site from this other web site known >> as FindAGrave. It's been several months now and they have done nothing. >> Will Rootsweb stand behind me and help me keep this couple from >> stealing my hard work which I have donated freely to the Project? >> What can I do to stop them from continuing to take my cemetery list >> and how do I make them remove what has already been stolen? >> I also believe they are stealing data from several other sites and >> I've have written to the webmasters there too. Do you or Val have any >> suggestions or advice for me? > > > Les Shockey email address = lshockey@citynet.net > or wvgenweb@citynet.net > RootsWeb Listowner for the SHOCKEY family discussion group. > SHOCKEY-L@rootsweb.com > Visit the Jackson County, WVGenWeb Page, part of USGenWeb Project at: > http://www.rootsweb.com/~wvjackso/JACK.HTM > Visit the (West Virginia) WVGenWeb: > http://www.rootsweb.com/~wvgenweb/ > > > >

At 09:51 AM 3/6/2004 -0500, you wrote: >Hello group, > >One of my CCs is having a problem with an outfit called FindAGrave. It >appears that they are stealing information from the USGenWeb Project pages >to build their site. > >Has anyone found a successful way to prevent these thefts? > >The CCs message is below with county name Xed out. > >Les Shockey >SC WVGenWeb You didn't include the county name, so I couldn't compare that site. I did visit FindAGrave and compared their Jones county, IA information to the information I have on my Jones county site. There is much that is the same, but much more that is different. They do not have all the information that I do--they have some information that I don't. Some people who contributed information to their pages are they same people who contributed to my pages, others are different. All entries include the name of the contributor. The site appears to be legitimate. Here is their disclaimer: >Any information you submit to Find A Grave is subject to editorial review. >All content you submit must not conflict with the copyright laws of any >country, state or other legal entity. No copyright is claimed on >non-original or licensed material. > >Find A Grave, Inc. attempts to provide accurate information to the public. >We have thousands of sources for the data on our site and we list >information for millions of names. As with any project of this scope, >there will be inevitable inaccuracies. We are not responsible for any >actions taken or emotions invoked as a result of the information found >within our website. Of course, someone could take information from my pages and contribute it there, but I didn't see anything to indicate that had happened. -Isaiah

Hi Susan, Thanks. I will pass this advice on to the CC. Les At 08:47 AM 03/06/2004 -0700, you wrote: >I teach Internet Technology and must convince my students that they abide by >the law when learning to build and create their Web sites. This is >information we discuss in class. > >Copyright is implied even if it isn't specifically posted, whenever work is >published. This was established in the Berne copyright convention, and Les Shockey email address = lshockey@citynet.net or wvgenweb@citynet.net RootsWeb Listowner for the SHOCKEY family discussion group. SHOCKEY-L@rootsweb.com Visit the Jackson County, WVGenWeb Page, part of USGenWeb Project at: http://www.rootsweb.com/~wvjackso/JACK.HTM Visit the (West Virginia) WVGenWeb: http://www.rootsweb.com/~wvgenweb/

Hello group, One of my CCs is having a problem with an outfit called FindAGrave. It appears that they are stealing information from the USGenWeb Project pages to build their site. Has anyone found a successful way to prevent these thefts? The CCs message is below with county name Xed out. Les Shockey SC WVGenWeb >Les, > Do you know what the policy of Rootsweb is as to their statement that > anything submitted to Rootsweb is copyrighted and the property of the > submitter? Do they do anything about someone who is stealing material > from one of the GenWeb sites and reposting it to another site as their > own? I am having this problem with a couple named Larry and Kim > Weaver. They are stealing the cemetery list I have posted on the XXXXXX > Co. site and re-posting them to another Internet database as their own > work. Any attempt to contact them about this has been ignored. It's been > going on for over a year, but only came to my attention several months > ago. I have demanded they remove the names they stole from the XXXXXX > site from this other web site known as FindAGrave. It's been several > months now and they have done nothing. >Will Rootsweb stand behind me and help me keep this couple from stealing >my hard work which I have donated freely to the Project? What can I do to >stop them from continuing to take my cemetery list and how do I make them >remove what has already been stolen? >I also believe they are stealing data from several other sites and I've >have written to the webmasters there too. Do you or Val have any >suggestions or advice for me? Les Shockey email address = lshockey@citynet.net or wvgenweb@citynet.net RootsWeb Listowner for the SHOCKEY family discussion group. SHOCKEY-L@rootsweb.com Visit the Jackson County, WVGenWeb Page, part of USGenWeb Project at: http://www.rootsweb.com/~wvjackso/JACK.HTM Visit the (West Virginia) WVGenWeb: http://www.rootsweb.com/~wvgenweb/

I teach Internet Technology and must convince my students that they abide by the law when learning to build and create their Web sites. This is information we discuss in class. Copyright is implied even if it isn't specifically posted, whenever work is published. This was established in the Berne copyright convention, and original works created after 1989 is copyrighted whether a notice is posted or not. It applies to web sites. Facts and ideas cannot be copyrighted, but the way they are presented is. If FindAGrave is copying your work exactly and posting it, they are in violation of copyright law. If they are retyping the data and presenting it in a different format, there probably are no grounds for contention. Recent laws and decisions: 1991--the U.S. Supreme Court ruled that no one can copyright a compilation of facts, such as the information contained in a telephone directory's white pages (Feist vs. Rural Telephone) 1993--the Clinton Administration formed its Working Group on Intellectual Property Rights as part of the Information Infrastructure Task Force to resolve intellectual property disputes and digital distribution of text, images, and video and audio recordinmgs. A revision to copyright law was proposed in 1994, but it has met with considerable opposition because it is seen as limiting communication among scientists and educators. 1998--the On-Line Copyright Infringement Liability Limitation Act was signed into law to reinforce intellectual property rights on the Web. The law protexts an ISP from liability for copyright infringements on the ISP's Web servers as long as the ISP has no prior knowledge of the infringement. Once the ISP is informed of a copyright violation, the ISP must disable the online access to the information that has been questioned. Go after the ISP. Find out where FindAGrave is hosted and inform the ISP that they are violating copyright and the above law. There is no reason that they can't link to the site where the copyright owner has posted the information. That way, the CC receives the credit for his or her hard work and it brings more traffic to the site. Susan Susan Stockbridge Bellomo http://www.rootsweb.com/~nmgenweb/ State Coordinator, NMGenWeb County Coordinator, Chaves, Grant and Otero Counties ----- Original Message ----- From: "Lesley Shockey" <LShockey@citynet.net> To: <STATE-COORD-L@rootsweb.com> Sent: Saturday, March 06, 2004 7:51 AM Subject: [STATE-COORD] Fwd: Copyright > Hello group, > > One of my CCs is having a problem with an outfit called FindAGrave. It > appears that they are stealing information from the USGenWeb Project pages > to build their site. > > Has anyone found a successful way to prevent these thefts? > > The CCs message is below with county name Xed out. > > Les Shockey > SC WVGenWeb > > >Les, > > Do you know what the policy of Rootsweb is as to their statement that > > anything submitted to Rootsweb is copyrighted and the property of the > > submitter? Do they do anything about someone who is stealing material > > from one of the GenWeb sites and reposting it to another site as their > > own? I am having this problem with a couple named Larry and Kim > > Weaver. They are stealing the cemetery list I have posted on the XXXXXX > > Co. site and re-posting them to another Internet database as their own > > work. Any attempt to contact them about this has been ignored. It's been > > going on for over a year, but only came to my attention several months > > ago. I have demanded they remove the names they stole from the XXXXXX > > site from this other web site known as FindAGrave. It's been several > > months now and they have done nothing. > >Will Rootsweb stand behind me and help me keep this couple from stealing > >my hard work which I have donated freely to the Project? What can I do to > >stop them from continuing to take my cemetery list and how do I make them > >remove what has already been stolen? > >I also believe they are stealing data from several other sites and I've > >have written to the webmasters there too. Do you or Val have any > >suggestions or advice for me? > > Les Shockey email address = lshockey@citynet.net > or wvgenweb@citynet.net > RootsWeb Listowner for the SHOCKEY family discussion group. > SHOCKEY-L@rootsweb.com > Visit the Jackson County, WVGenWeb Page, part of USGenWeb Project at: > http://www.rootsweb.com/~wvjackso/JACK.HTM > Visit the (West Virginia) WVGenWeb: > http://www.rootsweb.com/~wvgenweb/

Just received this link which might be of interest to some on Cemetery Restoration: http://www.terryscemeteryrestoration.com/ It appears to be in Iowa - R/S MAK WI ASC __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com

At 09:22 PM 3/3/2004 -0700, you wrote: >Richard, >The Idaho Genweb has held an election that finished at 9pm today. They >group elected my self Jason Mendenhall as the new state Coordinatoor for >Idaho. >Can you tell me if there is a mailing list for state coordintors, and how >to subscribe. I also need to know if there is any one else I need to >report this election to. > >Thanks > >Jason Mendenhall Hi Jason- Congratulations! I have copied your message to Pam Reid so she can update the National site, To Ellen Pack so the Elections Committee can find you and to the SC list so the other SCs will know of the change. You will need to elect or appoint a new Assistant State Coordinator to fill the position you have vacated. On behalf of The Project, thanks to Rhonda Smith for a job well done, and best wishes to you for a productive term as IDGenWeb State Coordinator. -Isaiah Isaiah Harrison National Coordinator The USGenWeb Project

I'll agree with that, and add that "Contents of the website should be updated at least quarterly and reviewed under the supervision of the state coordinator" has problems. The time period is too specific. This is something that needs to be determined by each state. I'm also not sure how to interpret "under the supervision of the state coordinator." My guess would be the state coordinator checks the sites or assigns someone else to review them. If that's it, say so. Susan David W. Morgan wrote: > I am not in favor of denying the right to vote to some of our volunteers > and I will definitely vote against this when the time comes. > > David

I am not in favor of denying the right to vote to some of our volunteers and I will definitely vote against this when the time comes. David > ----- Original Message ----- > From: "Roger Swafford" <sagitta56@mchsi.com> > To: <USGENWEB-DISCUSS-L@rootsweb.com> > Sent: Tuesday, March 02, 2004 5:41 PM > Subject: [USGW-Discuss] Bylaws Revision -- News > > > > (**Please forward to all appropriate project lists**) > > > > The Bylaws Revision Committee (BRC) is starting the final review process > of > > first draft proposals. Members are encouraged to respond with comments or > > suggestions related to the following articles. > > > > > > ARTICLE IX. COPYRIGHT > > Section 1. Members of The USGenWeb Project shall comply with copyright > laws > > of the United States (title 17, U.S. Code). > > A10 > > > > ARTICLE X. LOCAL PROJECTS > > Section 1. Each state organization shall provide local websites which > > reflect whatever divisional structure is appropriate for that state. > > Section 2. Local Project Coordinators shall be appointed by the State > > Coordinator in accordance with national and state guidelines. In making > > Local Coordinator selections, consideration should be given to knowledge > and > > interest in genealogy in the area, technical ability, activity in The > > USGenWeb Project, and existing workload. All Local Project Co-Coordinator > > and Assistant Coordinator appointments must be authorized and approved by > > the State Coordinator. Local Projects are limited to one Local Project > > Coordinator and one Local Project Co-Coordinator, if desired, who will > each > > have full voting rights within The USGenWeb Project. Local Projects may > > have as many Assistant Coordinators as they wish, subject to authorization > > and approval by the State Coordinator. Assistant Local Project > Coordinators > > shall not have voting rights. All Local Coordinators shall be subscribed > to > > the state mailing list. > > Section 3. The local website shall be created and maintained in accordance > > to all national and state guidelines. The website should include on the > > home page, a direct link to the state and national projects; an easily > > accessible area devoted to researcher's queries, the name(s) of the > > coordinator(s) with current email link(s), and any additional requirements > > specified by the state organization. Contents of the website should be > > updated at least quarterly and reviewed under the supervision of the state > > coordinator. > > Section 4. If a Local Coordinator can no longer perform their duties for > > any reason, (including, but not limited to, abandonment of the site, > > resignation or dismissal for valid cause), content of the website > submitted > > by contributors shall remain with the website, unless the contributor(s) > > otherwise request. > > > > All revision drafts may be viewed at http://home.mchsi.com/~sagitta56/ > > > > Roger Swafford > > BRC - Chairman > > David W. Morgan dmorgan@efn.org Honolulu Hawaii SC - TXGenWeb http://www.rootsweb.com/~txgenweb/ ** http://freepages.genealogy.rootsweb.com/~dmorgan/

<http://www.nwhp.org/tlp/links/links.html#ssresources> This is a link to state-specific resources at the National Women's History Project. Bob Sullivan NY

The KYGenWeb Project is very proud to announce the latest addition to our "Special Collections" of research references for those with Kentucky roots, the Kentucky Vital Records Project. (http://www.rootsweb.com/~kygenweb/kvrp) What began as a "dream" of 3 of us involved with the KYGenWeb Project and the KYGenWeb Archives, a centralized collection of Kentucky birth, marriage and death records, is now available in the first stages for Kentucky researchers. Currently, the browsable index lists all of the deaths in the KY Death Index (1911-1999). We are in the process of adding digital images and transcriptions of actual death certificates. These digital images and transcriptions will be linked to the browsable index as they are added to the collection. Records for this project will be a combination of researcher-contributed records and a coordinated extraction program so we can get them up as quickly as possible. We will begin adding birth records about 15 April 2004 and marriage records about 1 June 2004. As these records are added, they will also be linked to the index. (NOTE: Birth records will only be added for persons born before the year 1854, unless proof of death is provided. We want to ensure that the privacy and safety of living individuals is not compromised.) The browsable index will be a great help to KY researchers by itself, as you'll be able to search for those "creative" spellings that all of us have been blessed (or cursed) with. Tens of thousands of corrections have already been made to the original index. Corrections from site visitors are encouraged. As corrected or additional information is received on any of the records, it will be incorporated into the index for the benefit of future site visitors. In addition to the browsable index, be sure to check out the site search engine, as it will pick up additional information in the transcriptions (most importantly, parents' and spouse's names, if given). We invite everyone to stop in and check out this newest addition. Our hope is that you'll find some "treasures" here and that you'll then share your collections so that others can find theirs too. Feel free to forward this message to other mail lists.