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
Mineral County supports the Recall Admendment =)
Gerri
>===== Original Message From "Patrick Hays" <patrick(a)migrations.org> =====
> I have been convinced to bring back last years popular Recall Amendment
>with some minor adjustments to make it more acceptable to more people. Last
>year the Recall Amendment received a majority of votes, but was not quite up
>to the 2/3 required. I guess that means we should do it again. The
>deadline for amendments is very close, but there only needs to be one
>sponsor before the deadline, co-sponsors can come later, as last year set
>the precedent.
> Therefore, I am proposing that Colorado again spearhead a change for
>accountability in the USGenWeb Advisory Board, and be the sponsor of the
>Recall Amendment.
>
>
>ARTICLE XVII RECALL
>SEC. 1. Recall is the power of the members to remove an elective
>officer for violation of rules or confidence.
>SEC. 2. (a) Recall of an Advisory Board Member is initiated by
>delivering to the Advisory Board a petition alleging reason for
>recall. Reasons for recall are to be limited to: violation of
>bylaws, improper handling of information and/or legal/ethical
>violations.
>(b) A recall petition will consist of one e-mail containing the
>names and e-mail addresses of those in favor of recall which are
>to be collected by a USGenWeb Project Member. This petition must
>be verified to determine validity. In the event that there are
>multiple lists from multiple members for the Recall of the same
>person, they will be combined into one list. All signatories to the
>petition must provide their position within the Project to ease in
>determining the validity of their signature.
>(c) A petition to recall any Advisory Board Member (including the
>National Coordinator) must be signed by voting members equal in
>number to at least 20 percent of the last vote for the office. Any
>Advisory Board Member may be recalled, but only by their own
>constituents. The Election Committee shall certify the signatures
>on the petition, maintain a continuous count of the signatures
>certified and deliver a report to the Advisory Board and to the
>constituents in question if there are enough signatures to force a
>recall vote.
>(d) In the event that a Recall petition does not have enough
>signatures to force a Recall, that list can be added to for up to one month
>after the receipt of the initial list. After that a new list must be begun.
>SEC. 3. (a) An election to determine whether to recall an Advisory
>Board Member shall be called by the Election Committee Chairman,
>and held not less than 30 days nor more than 50 days from the date
>of certification of sufficient signatures.
>(b) If the simple majority vote of those voting on the question is
>to recall, the Member is removed and nominations for the successor
>must be immediately collected. If the recall action fails, the Advisory
>Board Member retains their position.
>(d) Votes in recall elections are subject to verification and
>certification by the Election Committee.
>SEC. 4. The Election Committee shall provide for circulation,
>filing, and certification of petitions, nomination of candidates,
>and the recall election.
>SEC. 5. If recall of the National Coordinator is successful, the
>duties of that office shall be performed by the At-Large Representative
>until there is a new National Coordinator.
>SEC. 6. An Advisory Board Member who faces a recall election, but
>who is not recalled shall not have another recall action initiated
>against the member for the same offense until six months after the recall
>election.
>SEC. 7. Terms of elective offices provided for by this Article,
>commence immediately following the election, and shall last until
>the term of the recalled Member expires.
>SEC. 8. In the event of conflict between any Other Articles of the
>USGenWeb Bylaws and this Article, this Article shall take
>precedence.
>
>Patrick Hays
>Custer Co., COGenWeb
>
>
>
>==== COGEN Mailing List ====
> This list is for the discussion of topics related to the COGenWeb project.
> It's primary audience is the county coordinators, state coordinator and
> other volunteers for the project.
------------------------------------------------------------
Get your FREE web-based e-mail and newsgroup access at:
http://MailAndNews.com
Create a new mailbox, or access your existing IMAP4 or
POP3 mailbox from anywhere with just a web browser.
------------------------------------------------------------
I support CoGenWeb going ahead with sponsoring this amendment.
don stanwyck
> -----Original Message-----
> From: Patrick Hays [mailto:patrick@migrations.org]
> Sent: Thursday, May 24, 2001 4:46 PM
> To: COGEN-L(a)rootsweb.com
> Subject: [COGEN] Recall Amendment
>
>
> I have been convinced to bring back last years popular Recall
> Amendment
> with some minor adjustments to make it more acceptable to more
> people. Last
> year the Recall Amendment received a majority of votes, but was
> not quite up
> to the 2/3 required. I guess that means we should do it again. The
> deadline for amendments is very close, but there only needs to be one
> sponsor before the deadline, co-sponsors can come later, as last year set
> the precedent.
> Therefore, I am proposing that Colorado again spearhead a change for
> accountability in the USGenWeb Advisory Board, and be the sponsor of the
> Recall Amendment.
>
>
> ARTICLE XVII RECALL
> SEC. 1. Recall is the power of the members to remove an elective
> officer for violation of rules or confidence.
> SEC. 2. (a) Recall of an Advisory Board Member is initiated by
> delivering to the Advisory Board a petition alleging reason for
> recall. Reasons for recall are to be limited to: violation of
> bylaws, improper handling of information and/or legal/ethical
> violations.
> (b) A recall petition will consist of one e-mail containing the
> names and e-mail addresses of those in favor of recall which are
> to be collected by a USGenWeb Project Member. This petition must
> be verified to determine validity. In the event that there are
> multiple lists from multiple members for the Recall of the same
> person, they will be combined into one list. All signatories to the
> petition must provide their position within the Project to ease in
> determining the validity of their signature.
> (c) A petition to recall any Advisory Board Member (including the
> National Coordinator) must be signed by voting members equal in
> number to at least 20 percent of the last vote for the office. Any
> Advisory Board Member may be recalled, but only by their own
> constituents. The Election Committee shall certify the signatures
> on the petition, maintain a continuous count of the signatures
> certified and deliver a report to the Advisory Board and to the
> constituents in question if there are enough signatures to force a
> recall vote.
> (d) In the event that a Recall petition does not have enough
> signatures to force a Recall, that list can be added to for up to
> one month
> after the receipt of the initial list. After that a new list must
> be begun.
> SEC. 3. (a) An election to determine whether to recall an Advisory
> Board Member shall be called by the Election Committee Chairman,
> and held not less than 30 days nor more than 50 days from the date
> of certification of sufficient signatures.
> (b) If the simple majority vote of those voting on the question is
> to recall, the Member is removed and nominations for the successor
> must be immediately collected. If the recall action fails, the Advisory
> Board Member retains their position.
> (d) Votes in recall elections are subject to verification and
> certification by the Election Committee.
> SEC. 4. The Election Committee shall provide for circulation,
> filing, and certification of petitions, nomination of candidates,
> and the recall election.
> SEC. 5. If recall of the National Coordinator is successful, the
> duties of that office shall be performed by the At-Large Representative
> until there is a new National Coordinator.
> SEC. 6. An Advisory Board Member who faces a recall election, but
> who is not recalled shall not have another recall action initiated
> against the member for the same offense until six months after the recall
> election.
> SEC. 7. Terms of elective offices provided for by this Article,
> commence immediately following the election, and shall last until
> the term of the recalled Member expires.
> SEC. 8. In the event of conflict between any Other Articles of the
> USGenWeb Bylaws and this Article, this Article shall take
> precedence.
>
> Patrick Hays
> Custer Co., COGenWeb
>
>
>
> ==== COGEN Mailing List ====
> This list is for the discussion of topics related to the
> COGenWeb project.
> It's primary audience is the county coordinators, state coordinator and
> other volunteers for the project.
>
>
I have been convinced to bring back last years popular Recall Amendment
with some minor adjustments to make it more acceptable to more people. Last
year the Recall Amendment received a majority of votes, but was not quite up
to the 2/3 required. I guess that means we should do it again. The
deadline for amendments is very close, but there only needs to be one
sponsor before the deadline, co-sponsors can come later, as last year set
the precedent.
Therefore, I am proposing that Colorado again spearhead a change for
accountability in the USGenWeb Advisory Board, and be the sponsor of the
Recall Amendment.
ARTICLE XVII RECALL
SEC. 1. Recall is the power of the members to remove an elective
officer for violation of rules or confidence.
SEC. 2. (a) Recall of an Advisory Board Member is initiated by
delivering to the Advisory Board a petition alleging reason for
recall. Reasons for recall are to be limited to: violation of
bylaws, improper handling of information and/or legal/ethical
violations.
(b) A recall petition will consist of one e-mail containing the
names and e-mail addresses of those in favor of recall which are
to be collected by a USGenWeb Project Member. This petition must
be verified to determine validity. In the event that there are
multiple lists from multiple members for the Recall of the same
person, they will be combined into one list. All signatories to the
petition must provide their position within the Project to ease in
determining the validity of their signature.
(c) A petition to recall any Advisory Board Member (including the
National Coordinator) must be signed by voting members equal in
number to at least 20 percent of the last vote for the office. Any
Advisory Board Member may be recalled, but only by their own
constituents. The Election Committee shall certify the signatures
on the petition, maintain a continuous count of the signatures
certified and deliver a report to the Advisory Board and to the
constituents in question if there are enough signatures to force a
recall vote.
(d) In the event that a Recall petition does not have enough
signatures to force a Recall, that list can be added to for up to one month
after the receipt of the initial list. After that a new list must be begun.
SEC. 3. (a) An election to determine whether to recall an Advisory
Board Member shall be called by the Election Committee Chairman,
and held not less than 30 days nor more than 50 days from the date
of certification of sufficient signatures.
(b) If the simple majority vote of those voting on the question is
to recall, the Member is removed and nominations for the successor
must be immediately collected. If the recall action fails, the Advisory
Board Member retains their position.
(d) Votes in recall elections are subject to verification and
certification by the Election Committee.
SEC. 4. The Election Committee shall provide for circulation,
filing, and certification of petitions, nomination of candidates,
and the recall election.
SEC. 5. If recall of the National Coordinator is successful, the
duties of that office shall be performed by the At-Large Representative
until there is a new National Coordinator.
SEC. 6. An Advisory Board Member who faces a recall election, but
who is not recalled shall not have another recall action initiated
against the member for the same offense until six months after the recall
election.
SEC. 7. Terms of elective offices provided for by this Article,
commence immediately following the election, and shall last until
the term of the recalled Member expires.
SEC. 8. In the event of conflict between any Other Articles of the
USGenWeb Bylaws and this Article, this Article shall take
precedence.
Patrick Hays
Custer Co., COGenWeb
In a message dated 5/21/2001 9:06:59 PM Eastern Daylight Time,
TVick65536(a)aol.com writes:
> Word has been received across many USGenWeb Project lists of the passing of
> Jeff Murphy, a founder and friend of the USGenWeb Project. Please all join
> in with others throughout the project in extending thoughts and prayers to
> the Murphy family in their time of sorrow.
>
> Tina Vickery
> SC WIGenWeb Project
>
Custer Co is still here. I did some updating on the page. The index is
up to over 9800 surnames (I bet Surname Helper never planned for an index
like this. It takes forever to edit it now!). Because of moving I have not
kept up on hits queries and such. There were between 300 and 310 hits in
April, which is the most since October. Page views were similarly high...
between 850 and 900. It would be relatively easy to check queries and such,
but if I don't send this and leave, I'll be late for work.
Patrick Hays
http://www.geocities.com/gsdownr_2000/custer1.htmlhttp://www.geocities.com/gsdownr_2000/comig.html
I saw a thing from someone on the list saying that the crawlers had
gotten their email address and they are now getting zillions of junk
mails.
Instead of coding your email address/link like this:
<A HREF="mailto:oldham@pagosasprings.net">oldham(a)pagosasprings.net</A>
Code it with a little javascript code as below and the crawlers are not
able to pick the address off of your page.
<SCRIPT LANGUAGE="JavaScript">
user = "oldham";
site = "pagosasprings.net";
document.write('<a href=\"mailto:' + user + '@' + site + '\">');
document.write(user + '@' + site + '</a>');
</SCRIPT>
Of course where my name appears as user and my server appears as site,
you would naturally use your own.
The above code courtesy of cdr software.
Of course when someone else has your email address on their page there
is no way to protect yourself.
Leroy
Hi everyone.
Just wanted to let you know that I am changing my email addy for my Colorado
GenWeb sites. The new address is cogenweb(a)hotmail.com
This is due to a bizarre new group of spammers that are sending me about 150
spams per day - all identical. Please change your records accordingly.
Sorry for the inconvenience
Vikki Gray, Delta, Gunnison, San Miguel and Pitkin County GenWebs
Hi, Mineral County checking in, not much happening here so far but I am hoping
that will change <G>
>===== Original Message From DPaulC13(a)aol.com =====
>Howdy. Still here, alive and kicking.
>Chaffee 216 visitors
>Garfield 376 visits
>Moffat 71 visits
>Summit 62 visits
>Everything is going well.
>Doug Cullen
>
>
>==== COGEN Mailing List ====
>Genealogy: Where you confuse the dead and irritate the living
------------------------------------------------------------
Get your FREE web-based e-mail and newsgroup access at:
http://MailAndNews.com
Create a new mailbox, or access your existing IMAP4 or
POP3 mailbox from anywhere with just a web browser.
------------------------------------------------------------
"HELP BRING OUR KOREAN WAR SOLDIERS HOME!" by Megan Smolenyak
===================================================================
Baltimore Payne was born in 1912 in Illinois to parents who had
ventured slightly north from Missouri. He was one of ten children and
grew up to marry, have children, and join the Army. In 1950, he was
sent to Korea where he paid the ultimate price, dying just as most
Americans were celebrating Thanksgiving. Unfortunately, the
circumstances of his death were such that his remains were never
found, so his family was denied the chance to pay their respects,
bury him, and properly grieve.
The U.S. Army's Repatriation and Family Affairs Division--which
recently traced his family to people with five surnames residing in
four states--is working to change that. The objective of this
organization is to locate and re-establish ties with the family
members of the 6,318 soldiers who were never accounted for in the
Korean War. To put this into perspective, this is about three times
as many soldiers as those still unaccounted for from Vietnam. The
ticking clock--50 years and counting--makes it both urgent and
somewhat difficult to find these soldiers' families.
By locating family members, the Army hopes not only to help with the
inevitable, unanswered questions, but also to build a database of
mitochondrial DNA (mtDNA) samples. With relations with North Korea
slowly improving (this, in spite of the fact that an official
cessation of hostilities was never declared!) and search and recovery
efforts escalating, the Army has more hope of bringing soldiers home
now than they did in the first four decades following the war.
During the 1990s, several hundred sets of remains were repatriated,
but now the challenge is to identify them so they can be accorded a
formal military funeral.
At this point, approximately 30 percent of the soldiers' families
have been found and the mtDNA database contains samples for slightly
more than 20 percent of the soldiers. As the database grows, so do
the chances of matches confirming the identification of Baltimore
Payne or any individual missing soldier.
The Army would like your help in finding the other 4,000+ families.
Please don't think you can't help just because you weren't even born
then. Almost everyone in the U.S. knows of someone who served in
Korea, whether he returned or not. Maybe it was your grandfather or
your brother. Maybe it was that acquaintance from high school. Maybe
it was that fellow who worked at the mill with your father. Or maybe
it was you.
If you have any connection--no matter how remote--to someone who
served in Korea, please visit http://www.koreanwar.org
This site lists all the men who are still unaccounted for. You can
search for a soldier's name and then leave a remembrance with
whatever details you might have. No detail is too insignificant, but
ones pertaining to the soldiers' families are especially helpful.
Names of siblings (generally not contained in the soldiers' files)
can often bring a case to resolution. A remarriage of the soldier's
mother or the fact that his brood moved from New Jersey to Arizona
can be enormously useful. Just think for yourself what information
you would need to trace a line in your own extended clan forward from
1950. The same information is needed by the Army. Remember, too, that
others who served frequently knew quite a lot about the Stateside
lives of their fellow soldiers. Please consider quizzing any Korean
War veterans you might know about the men they served with.
Should you note a "DNA" tag next to the soldier's name, this means
his family is being actively sought. If you see this, you might want
to consider calling the Army directly at 800-892-2490 in addition to
leaving a remembrance.
Baltimore gave his life for his country. That it happened 50 years
ago makes it no smaller a sacrifice or any less important. The Korean
War was fought from 1950 to 1953, so we are in the midst of an
extended 50th anniversary. What more fitting tribute than to see that
as many of these soldiers as possible are properly honored and
interred?
____________________________________________________________________
Megan Smolenyak is an international marketing consultant who has been
researching her family history since she was in the sixth grade.
Megan has appeared on "Today" with Jack Ford and is the lead
researcher of the PBS Series "Ancestors." She also wrote the
companion book for that series, "In Search of Our Ancestors: 101
Inspiring Stories of Serendipity and Connection in Rediscovering Our
Family History." She has also published dozens of articles in
genealogical publications and business magazines and delivers
seminars and workshops on genealogical subjects.
Karen Mitchell
2001 has been declared "The Year of "Love". Pass it on.
km1109(a)rmi.net
US GenWeb Project County Coordinator
Huerfano County Coordinator
http://www.rootsweb.com/~cohuerfa/index.htm
Huerfano County List Owner
COHUERFA-L(a)rootsweb.com
Taos County Coordinator
http://www.rootsweb.com/~nmtaos/index.htm
Taos County List Owner
NMTAOS-L(a)rootsweb.com
All is quiet in Logan & Park Counties...
However:
2 queries were posted in Logan for Apr 2001 [also 2 in Mar 2001]
and
1 query was posted in Park for Apr [none in Mar 2001]
Sincerely,
Edward, Sr.
Cheyenne County
147 hits Total 5511
1 query
2 obits
16 surnames
Kiowa County
84 hits Total 1526
4 obit s
1 query
15 surnames
Lincoln County
82 hits Total 3643
2 queries
5 surnames
Karla Mahlberg
Costilla County -
197 hits
6 bio's all written and donated by Maria C. Martinez of Costilla County.
1 obit
Saguache County -
146 hits
1 bio written and donated by Maria C. Martinez of Costilla County.
1 surname added
Marta
April Stats
Washington Co.
Hits 116
Queries 2
Obits 1
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
I have major spring fever and I'm trying to ignore my county sites for a day
or two. So far ignoring them isn't working :) Here are my stats:
Delta 259 hits
Gunnison 214 hits
Pitkin 146 hits
San Miguel 127 hits
Morgan 156 hits
Vikki Gray