Derick,
Nowhere in the USGenWeb bylaws states the 12 items you listed below. Where
did you come up with such a list?
Here are the state project bylaws to refresh everyones memory:
ARTICLE XII. STATE PROJECTS
Section 1. Each state shall have a State Coordinator who manages the state
website and oversees the state project. In addition, each state shall have
an Assistant State Coordinator or other support team in place that can take
charge in case the State Coordinator becomes unavailable for a period of 30
days, unless there are extenuating circumstances.
Section 2. The state website shall include direct links to the county pages,
The USGenWeb Project national website, The USGenWeb Project Archives
(Digital Library) at both their own state and the national levels, The
USGenWeb Project's Guidelines/Standards for county websites (which includes
a link to the Official Project Name/Logo page), The USGenWeb Project
Copyright Information page, and the WorldGenWeb Project.
Section 3. It shall be the responsibility of each state organization to
ensure that the state project is in compliance with the stated bylaws of The
USGenWeb Project.
Section 4. State Coordinators shall remain subscribed to the State
Coordinators mailing list and maintain a current mailing list of all
local-level coordinators. State Coordinators shall provide their name,
postal address, and phone number to the National Coordinator to be held in
strictest confidence and only used in the case of an emergency.
Section 5. State projects are empowered to develop/adopt any additional
rules/bylaws and guidelines, as appropriate, for their state so long as they
do not conflict with these bylaws. State projects shall be highly encouraged
to develop and adopt rules/bylaws that cover grievance procedures within the
state
Section 6. It shall be the responsibility of each state project to
periodically review local-level project websites to ensure compliance with
The USGenWeb Project/XXGenWeb Project established guidelines/standards.
Section 7. The state project shall have the responsibility to remove any
links to websites which fail to meet The USGenWeb Project/XXGenWeb Project
established guidelines/standards.
Section 8. State Coordinators shall be elected to those positions by the
local-level coordinators within the state. Those State Coordinators and
Assistant State Coordinators in place at the time these bylaws are adopted
shall be exempt from election procedures, unless he/she/they are removed,
resign, or are unable to perform their duties.
Section 9. State Coordinators and Assistant State Coordinators are subject
to possible removal by a 2/3 vote of the Advisory Board and a 2/3 vote of
the Local Coordinators within the state. A quorum of 75% of the Local
Coordinators shall participate in order for the vote to be binding.
Section 10. 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 the state. In the case of state projects with
more than one Assistant State Coordinator, they shall choose one among
themselves to serve in the interim.
***TB.....According to the above bylaws, the State Coordinator
responsibilities are:
1. Manage the state website, fix links and make sure website is in
compliance and oversee the project
2. Have a backup ASC or team in case the SC is unavailable for more than 30
days
3. Insure Counties have links to national, state, and that they comply with
the bylaws.
4. Be subscribed to the State Coordinator's list
5. plus our voted on rules or whatever you call them said that the State
Coordinator was to keep the CC's informed on issues
that concerned us via the manditory list.
6. maintain current list of CC's for voting purposes, that isn't mentioned
in the bylaws, but is a commonly known fact.
Nobody has a problem with you delegating some of this work to your chosen
ASC's, but we do have a problem with a written plan that looks more like
bylaws or guidelines than a delegation of authority. The problem we have
with it is that we didn't have a voice in whether we want to accept all
those guidelines.
Terria
PS...most of the CC's in this project have to do many of those things you
listed below as part of our maintaining our sites like buying software,
learning html, etc.
----- Original Message -----
From: "Derick S. Hartshorn" <derickh(a)charter.net>
To: <NCGENWEB-DISCUSS-L(a)rootsweb.com>
Sent: Tuesday, July 30, 2002 7:26 PM
Subject: [NCGENWEB-DISCUSS] Explanation of organization
RE:
http://www.rootsweb.com/~ncgenweb/organiza.htm
This additional posting to the NCGENWEB-L (mandatory list) is being made
because some folks who are subscribed to the NCGENWEB-DISCUSS-L (optional
list) may not be aware of the NCGenWeb Organizational Structure. Some
folks
have either not read this page or do not completely understand the
content
or intent. For that reason, I will address the three major points made by
some of our fellow CCs. I may not have notified everyone in the Project,
telling what my intent, focus and goals would be for the next year, or
possibly longer.
One of the first concerns I became aware of was that some folks thought
that a radical and unnecessary reorganization was taking place without
their say-so. If carried to extremes, we could probably use then analogy
of
a sinking passenger liner. While it might be proper and just to
organize a
committee assigning seats on a lifeboat, there are probably better, more
expedient ways of achieving the bigger objective.
Please be clear on this matter: The NCGenWeb Project is not being
re-organized. It is being allowed to achieve a degree of excellence that
was not possible before. This has nothing to do with prior leadership. It
has everything to do with technology and the ability to network. I have
been elected to State Coordinator and I have accepted your challenge to
lead. And lead I will---and to the very best of my ability. I may not
always agree with your opinions but I will always support your right to
express them whether or not you support my goals.
If those who voted for me expected me to:
1. Maintain the NCGW lists.
2. Pass appropriate information to District CCs (links, neat pages,
etc.)
3. Design and maintain an information system to enhance
communications
between CCs and outside related sources for the purpose of providing
each
CC the maximum amount of available information.
4. Ensure at communications between CCs were optimized and that every
CC would have an equal voice.
5. Maintain the NCGenWeb Project HelpDesk. Acquire the necessary
reference material at my own expense to provide excellence in service.
6. Develop and maintain a skills inventory of each CC so that each
person might have the opportunity to contribute to the Project to the
degree they were willing to commit.
7. Maintain and, as necessary, design web pages for the NCGenWeb
Project. Become familiar with HTML and all necessary tools to create and
revise web pages. Purchase, at own expense, necessary software to
accomplish above.
8. Post relevant local material to CCs and their lists.
9. Develop and maintain a "CC Page" designed to provide a bio, web
page and responsibilities of each CC, provided by the CCs.
10. Maintain a directory of each CC, with e-mail address and Project
home page.
11. Develop a list, page or other method of informing the NCGW family
of available NCGW archives.
12. Lend help in supplying or assisting CCs in furnising a page
indicating repositories of local records.
If you expected me to do all this you were expecting a great deal.
Regardless of what you may think, I DO have another life. I have no
designs
for power and am looking forward to that time down the road where I
can
again research and write.
Bearing in mind that the above twelve tasks would consume much more time
than I could accomplish alone, I designated three Assistant County
Coordinators for the express purpose of dividing up these
responsibilities.
With 107 present and former counties and districts and 74(?) CCs, I
felt
that someone should personally represent each one. Moses appointed Jethro,
I appointed Ron Eason. I sought out the qualified, the willing, and those
who expressed a willingness to expend time and effort for the common good
of the NCGenWeb Project. At this moment, I feel that I we have the very
best team in the USGW, BAR NONE
In order to apportion these tasks, I have asked Paul Buckley to assume
tasks #1-4, Elizabeth Harris to undertake tasks #5-8 and Angie Rayfield to
take on tasks #9-12.
It's that simple--at least on paper. We all need help from each and every
CC. While I have proposed a method of how I plan to operate as the SC, I
am, and have always been, open to suggestions. I have yet heard from
anyone
with specific points relating to the organization plan, but welcome
them.
History suggests that laws became necessary when confusion exists between
one way and another. If they are necessary, we will make every effort to
adopt them. I would hope that you consider the points I have made in the
organization plan.
Finally, I have not delegated any power to anyone. The first rule in
business is that power can not be delegated. I have delegated
responsibilities and tasks, regardless of what their title might suggest.
I
never was much for titles, I just want to the USGenWeb Project
preeminent
among all other on-line genealogical resources---the one that researches
visit first.
Please help me.
Derick
SC, NCGW