SC Decisions Voted On and Passed

Name of umbrella conference:

IEEE Symposia on Human-Centric Computing Languages and Environments (HCC) Oct. 12, 2000: Passed with the lowest sum of ranks (where 1=first choice) out of all 9 SC members voting. Oct. 17, 2000: Acronym (HCC) selected same as above.

Proposed mission statement:

Design, formalization, implementation, and evaluation of computing languages that are easier to learn, easier to use, and easier to understand by a broader group of people. Sept. 26, 2000: Passed with 6 "yes" votes and 0 "no" votes. (On Sept. 27, another "yes" vote arrived.)

Charter changes: Note that these changes were eventually also approved using the charter changing procedure in April 2001.

Changes to Charter Point 1

a. The name of VL is changed to the IEEE Symposia on Human-Centric Computing Languages and Environments (HCC)

b. The mission is:

Design, formalization, implementation, and evaluation of computing languages that are easier to learn, easier to use, and easier to understand by a broader group of people.

This includes all research aimed at the above mission, regardless of whether they use entirely visual technology, text, or instead use sound, taste, virtual reality, the web, or any other technologies. Examples of research addressing this problem include but are not limited to language/environmental design aspects, theory that supports the many media used toward this goal, implementation aspects, empirical work, software comprehension aspects (including software visualization), and software modeling and/or software engineering aspects.


Changes to Charter Point 4.1

The General Chair's additional responsibilities regarding ICSs are listed in Charter point 6. --------

Addition of Charter Point 6

a. The conference will consist of "Individual Contained Symposia" (ICSs), each of which has a strong sub-theme, integrated with some common paper presentations, keynote presentations, and special events. Each ICS will have its own Program Chair and its own Program Committee, who will be coordinated by the General Chair, and who will follow the HCC conference standards and rules.

The General Chair organizes the overall conference, and provides services to the ICS Chairs, including providing for a common proceedings, registration, management of the financial aspects, the social program, a paper submissions mechanism, a review tracking mechanism, local arrangements, tutorials, and publicity. The General Chair may appoint additional chairs as desired (such as a Finance Chair, Tutorials Chair, etc.) to assist in these matters.

ICS Program Chairs' responsibilities are to put together a Program Committee (to be approved by the Steering Committee), to put together an announcement of the particular ICS to be used for publicity, to encourage high-quality technical submissions, to manage the ICS Program Committee through its review process, and to attract program attendees. ICS Program Committees have an independent paper selection process and have primary responsibility for the organization of their program, subject to appropriate coordination with the General Chair over common events and general conference operation. ICS Program Chairs will suggest papers, keynote speakers, panels, special events, etc., to the General Chair, who will select from and coordinate such ICS suggestions as is appropriate for the general conference.

b. Over time, some ICSs will be eliminated and others will be added, as interest in subareas evolves. There is no prescribed limit to the number of ICSs that the conference will support, and hence, adding an ICS need not require elimination of another. Still, to continue to be present at HCC, an ICS must adhere to the HCC paper acceptance rates (see conference guidelines) and have enough paid attendees to pay for itself (computed as a fraction of total HCC conference expenses based on the ICS's number of days) in one out of every two consecutive offerings of the ICS. In addition, any ICS that is not, in the opinion of the Steering Committee, contributing to the overall success of the conference may be cut regardless of current or prior performance; however, such occurrence should be rare if ICSs are chosen appropriately initially. When practical considerations limit the number of slots, for a continuing ICS to be selected to continue over other ICSs competing for its "spot", it must be reasonably expected, based in part on its past history, to continue to attract at least as many paid attendees as proposed ICSs competing for its slot.

c. After HCC 2001, proposals for new ICSs must be submitted to the Steering Committee at least one year in advance of the first proposed occurrence of the ICS. Proposals should include the ICS's planned strategy for fulfilling the above requirements.

Dec. 29, 2000: Passed with 6 "yes" votes and 0 "no" votes.

Exception to usual paper acceptance rate for End-User Programming ICS:

For HCC'01 (only), we will allow the End-User Programming ICS (only) to accept up to 12 papers. (This pertains only to full papers, and does not stipulate anything about posters that can be accepted.) May 14, 2001: Passed: 5 "yes" votes, 2 "no" votes, 1 abstention, and 1 person did not vote.

VL/HCC Bibliography rule:

Starting with HCC'02, authors of accepted full papers are required to list their papers in the bibliography. (This is actually true of HCC'01, but since the rule was passed very late for HCC'01, no enforcement is expected if authors cannot be enticed to submit their information.) June 29, 2001: Passed: 8 "yes" votes, and 1 person did not vote.