Welcome to the Voting Information Page!

Interim JOS President

Title: Election of an Interim JOS "President"
Type: Ordinary
Proposer: Iain Shigeoka [ iainshigeoka@yahoo.com ]
Seconder: TBD [ TBD ]
Administrator: TBD [ TBD ]
Proposal posted: Sept. 20, 2000
Voting Begins: Sept. 27, 2000
Voting Ends: Oct. 01, 2000

Vote

Votes can be emailed to the Vote Administrator no earlier than the "vote begin" date (Sept 27, 2000) and no later than the "vote end" date (Oct. 01, 2000).

The JOS Project shall be led by an interim President for no more than 3 months beginning Oct. 2, 2000. The President shall have the powers and responsibilities enumerated on the VoteInfo page of the JOS Wiki.

Please vote [yes/no/neither/abstain]:

If this vote passes with a 'yes' vote, I elect the following person to the position of President:

A> List
B> of
C> President
D> Candidates

[This list will be compiled during the Vote Advertisement period]

Comments:

Presidential Candidates

The following members have been nominated as presidential candidates (see their wiki page for information on each member):

Iain Shigeoka -- IainS -- [ iainshigeoka@yahoo.com ]
Add your name here

Vote Proposal

A single JOS member will become interim "President" for a period not to exceed 3 months.

During the interim President's term, (s)he is responsible for:

Forming and passing an "extraordinary" vote on creating a small (~3 person) "JOS cabal" to lead the project in the future.
Set a definitive and focused road map for the JOS project (including reasonable deliverables)
Establish a single, project-wide, license for all JOS project code.
Establish a more focused short term and long term vision for the project.
Reorganize the website and other online resources to reflect the new focus of JOS
Create procedures, resources, etc to recruit new JOS members/developers, and to retain and better utilize existing JOS members.
Identify and address existing problems which is inhibiting JOS's progress, and its inability to retain and fully utilize current members. This is the most open ended requirement for the president but probably the most important.

The Interim President is granted the following "extraordinary" powers to enable completion of the above duties:

Propose and "expedite" ordinary votes on the vote-info mailing list. Many issues must be resolved and clarified during the re-organization. For the sake of speed and project focus, the president may hold "informal" votes on the vote-info mailing lists. These votes will be conducted as a compressed version of normal "ordinary" voting procedures. President may make proposals for a 24 hour period (no need for seconding), and hold a vote for a 24 hour period (no quorum required). So, during the 3 month presidency, interested members should be monitor the vote-info mailing list DAILY !
Make decisions normally requiring an "ordinary" vote. These decisions must be followed by confirmation (or be overruled) as a vote on the vote-info mailing list (this can be an expedited vote).
Negotiate with third parties on behalf of JOS.

These powers essentially allow the President to act as a "benevolent dictator" within the JOS Project. We feel that this power is required in order to effect a re-organization that will re-energize the JOS Project and provide a stronger project focus. It is assumed that despite these powers, the President will attempt to gain consensus whenever practical and foster a sense of community and common purpose.

The JOS interim President may be removed at anytime by an "extraordinary" vote of the membership.

Why should what takes an ordinary vote to establish take an extraordinary vote to undo? If it takes an extraordinary vote to undo, it should take an extraordinary vote to establish. -- AveryRegier

Vote Background

Around this time of the year three years ago on the old JavaLobby forums, the idea of creating an operating system based on the Java programming language was discussed, out of this discussion the JOS project started.

Now over those years the JOS project has remained quite small with the number of active contributes staying about the same. But interest is still quite high with new people joining all the time, but there has been just as many leaving as joining. We believe this is because there has been very little progress as a group, although some individuals have made quite a bit of progress.

Now we have always promoted the idea of there being multiple implementation of every component. With the best being chosen by natural selection, but this hasn't worked each component is too strong and just won't die. The problem with this is that the whole project will die off because new members don't know where to start and then leave.

So far each developer has worked on there own project with little help from other developers, and nobody wants to give up there project and work on someone else's.

Now for this to change we need to all stop working on our own projects and work together on a new unified project. We should treat all the current project as prototypes and leave them behind, and just bring all the good ideas with us on the new unified project.

For this to succeed we need to jump into the deep-end, new mailing lists, web site, cvs server. We can keep the old stuff around but only for reference.

[ Ruthlessly plagerized and edited from Robert Fitzsimons original: http://cjos.sourceforge.net/redist/mail/general/2000-September/000196.html ]

Content of these pages are owned and copyrighted by the poster.
Hosted by: