Once discussion is complete, the comments should be removed leaving just the final text. (Reason, keep it simple for future readers) and the final agreed policies will be transferred to the main Conference Committee page

Comments should be in red font, starting with the authors name.

Motion 1: proposed by Steven Feldman

Role of the Committee and the broader community on the Conference_Dev list

Everyday topics will be decided upon by an open vote of all list participants in a clearly designated separate mail thread (+1/-1) over a minimum of two business days with a minimum participation of 3 votes. Ideally we aim for consensus falling back on simple majority vote where necessary. The result will be clearly declared afterwards (or whatever is decided). (Maxi: 3 votes out of 11 members and 2 days seems to me too restricted) (Steven: we have to set a quorum and a time limit on votes - sometimes decisions are needed relatively quickly) (Maria: in general the vote is not considered valid if there is less than a given percentage of people voting.) (Cameron: This is in line with other OSGeo committees/PSCs. If tweaking we could distinguish between minor decisions, and major decisions, such as location of next conference.)(Venka: The quorum for a meeting should be more than 50% of the members and majority suggested (3 votes out of 11 for a motion to be pass/fail) needs to be modified.)

Election of conference committee is by secret vote and restricted to the remaining conference committee members and board members who are not members of the conference committee. (Maxi: I would like to see the votes open to all participants - all the charter member that are part of the conference mailing list or are registered as interested) (Steven: The role of the conference committee requires the expertise of past chairs. Only 5 of 11 places are allocated to past chairs, the other places are open to regional chairs or others with equivalent relevant experience)

FOSS4G Selection - All Letters of Intent and subsequent proposals will be posted to the list for open comment by all list participants. The selection of the winning proposal is by secret vote of conference committee members only (for the avoidance of doubt the Board do not vote in the selection process but they do ratify the conference committee’s recommendation).

Any committee member who has a potential conflict of interest is expected to withdraw from vote. A member of the committee who is part of a bidding team, intends to become part of the LOC or is employed by a company playing an active part in a bid should exclude themselves from voting in the selection process. In the event of a disagreement regarding a potential conflict of interest the committee chair has the authority to make a decision.

Votes in 2 and 3 are to an online voting service or by email to an independent teller appointed by CC Chair

Conference Committee membership policy and process

The conference committee aims to retain up to 11 active members, preferably an odd number (David Bitner: I would definitely like to have more room in the target than simply 11.)(Venka: There is more room in the CC than for just 11 members)

The committee aims for half of these members to be chairs (or vice chairs) of the most recent FOSS4G global events. The chair of the most recent FOSS4G event will automatically be invited to become a member (Jachym: ... or any other member of LOC, suggested by the chair of most recent FOSS4G) (Maxi: I don't like the idea that only who has chaired a conference is entitled to take decision on the conference)

The remaining membership is open, ideally attracting people from earlier past chairs or active LOC members from past Global, Regional FOSS4G or related conferences

Each year (after FOSS4G) 3 committee members should retire from the committee: (Venka: Having people who are and wish to be active in a committee step down just because they seem to have been around too long, is not the best way of manage the membership of committees, especially so in a volunteer organization)

The longest standing past FOSS4G chair

The longest standing 2 committee members remaining

Each year, prior to releasing the Global FOSS4G RfP, the remaining committee members should fill available vacancies, using the above criteria as voting guidelines. OSGeo Board members who are not on the conference committee will also be invited to vote.

Past committee members including those who have stood down due to length of service may stand for re-election

Votes will be secret either using an online voting system or by email to a designated teller who is not a voter. The mechanism will be selected by the committee chair.

Motion 3: adjusted based on feedback by Cameron Shorter

Decisions

Anyone may contribute to conference committee discussions. All votes will be noted, but only conference committee member votes count toward decisions.

Voting will use convention of:

+1 : For

+0: Mildly for

0: Indifferent

-0: Mildly against

-1 : Strongly against. This is expected to be accompanied by a reason and alternative proposal.

Everyday topics will be decided by an open vote of all members in a clearly designated separate mail thread over a minimum of 2 business days with a minimum participation of 3 votes.

For major decisions, such as conference venue selection, a minimum of one week shall be allocated to try and ensure at least 50% voter participation.

The committee aims for consensus, and will specifically attempt to address all -1 votes, but will revert to a majority vote where necessary.

The result will be clearly declared afterwards.

Secret voting, when required, will use an online voting service or use an email to an independent teller appointed by CC Chair.

FOSS4G Selection

All Letters of Intent and subsequent proposals will be posted to the list for open comment by all.

The selection of the winning proposal is by secret vote of conference committee members.

The OSGeo Board will be requested to ratify the conference committee’s recommendation.

Any committee member who has a potential conflict of interest is expected to withdraw from voting. A member of the committee who is part of a bidding team, intends to become part of the LOC or is employed by a company playing an active part in a bid should exclude themselves from voting in the selection process. In the event of a disagreement regarding a potential conflict of interest the committee chair has the authority to make a decision.

Membership

To ensure voting control for key decisions remains with experienced people, the committee aims for more than 50% of members to be chairs (or vice chairs) of past FOSS4G global events. The chair of the most recent FOSS4G event will automatically be invited to become a member but still requires a motion and vote.

The conference committee aims to retain a chair or vice-chair from the 5 most recent global FOSS4G conferences.

The remaining membership, less than 50% of members, is open, ideally attracting chairs or LOC members from past Global or Regional FOSS4G or related conferences.

Each year, prior to releasing the Global FOSS4G RfP, the membership list shall be re-visited.

Existing members shall be asked whether they wish to continue on the committee. If a member doesn't respond, after a number of attempts to contact them, they shall be retired.

Interested people may be suggested, or request to be voted onto the conference committee.

If less than 50% of membership would be past global FOSS4G chair/vice chairs, then non global FOSS4G chair/vice chair positions shall be up for re-election.

Election of conference committee members is by secret vote by the existing conference committee and board members who are not already members of the conference committee. Voters will vote Yes/No/Abstain for each candidate. Voters may select "Yes" for up to the number of positions available.

Votes will be secret either using an online voting system or by email to a designated teller who is not a voter. The mechanism will be selected by the committee chair.