[Theforum] Proposed Task List (was Framing the House?)

[Ron Dorman]

"Luther, Ron" wrote:

> I'm thinking that a task list might lend itself to consolidation into
> logical units -- then we have our 'officers' / 'standing committees' /
> 'departments' -- whatever we want to call them.  {e.g. kind of a "form
> will follow ... once we understand function" kind of thing}
>
> I'm hearing possible needs for things like:
>
> ** technical committee ... boxen tuning, chairing/directing codefest
> type activities, "ruling" on technical suggestions / methods for
> implementation.
>
> ** correspondence committee ... handle email inbox, "escalate (wtf would
> THAT mean?)" significant issues/opportunities, update FAQ list, etc.
>
> ** fundraising/finance ... [even NFPs need a budget!], bake sale, floppy
> wash, t-shirts, begging for corporate donations, writing letters/filling
> out forms to philanthropic foundations, etc.  {"evolt - brought to you
> by Pillsbury and a generous grant from the Chester C. Chester foundation
> ... and by coders like YOU!"}   ;-)
>
> ** ... and other junk I may have forgotton or missed.
>
> There may also be an odd need for non-standing committee work to address
> things like stylistic issues that may arise from time to time.

Reposting from another thread on Wed.

Been reading everything, letting it soak in a bit.  We seem to be a bit
anxious still.  I am hoping things will slow and calm some over the
next 2 - 3 days.  I am hoping this happens so we can give serious
thought to our task and the future of evolt.  I am hoping we regain
the original vision and enhance it with our experiences to define and
develop systems that allow us to achieve the vision of evolt.

When I say systems, I mean ways to communicate better, methods to
administer the servers and sites, guidelines to follow, administrative
bodies to form, etc.  As we think about our task/s we should be aware
that we are carving out some new, refining existing and defining a better
future.  We are doing this for and, more importantly, with a community,
all users of evolt.

I think the vision and scope of evolt has been pretty well defined but
needs to be written and published, with very high visibility.  This
will provide the starting point, direction and path to be followed.
This, I think should be priority one and should include feedback
from the community at large.

We then develop a system/s to support the vision.  Developing a good
system is the make/break of successful endeavors.  The system/s can be
very loose and free as open source development is.  They can be very
tight as would be needed in scientific research.  The vision of evolt will
be
our overall guide to developing the system/s and will probably include
sub-systems of varying degrees of flexibility's.

We can use some existing systems, modify some existing systems, merge
some existing systems and make some new ones.  I believe we will eventually
define, design and develop a unique system that others can follow and
use.

All this will take time and sincere, unselfish effort.  Maybe a good
first task list would be:
    a) Publish existing evolt vision and mission statement.
    b) Get feedback from all evolt on vision.
    c) Publish final evolt vision and mission statement
    d) Define system/s needed to support vision and mission statement
    e) Let groups assemble to develop needed system/s  (this allows
        all evolt members to contribute in their area of expertise/interest)

    f) Implement, evaluate, refine.
    g) Repeat e and f indefinitely.

Ron D.