SIG Governing Board-Executive Committee Motions - FY'03
The hotel contracting process must be changed to mirror the standard practices of ACM including:
- Standard site selection process - going through ACM national sales and ACM convention and visitors bureau contacts
- Hotel negotiation to secure all ACMs standard concessions and phrasing
- Hotel contracts to be reviewed and approved by ACM HQ staff - it should be understood that at least one week is required for review.
Motion: Move to support SIGAPP proposal for $4K as requested.
Motion: Move to endorse the chartering of the Special Interest Group for Information Technology Education (SIGITE) contingent on the approval of the SGB. The VC for Emerging Technology, Small SIG Advisor and the Director of SIG Services will work with the leaders to develop their budget and finalize their bylaws.
Motion: Move to endorse exception to policy and permit a one-year extension of the contracts for AVW, SBA Marketing Media and SBA conference management.
Motion: Move to endorse SIGGRAPH's request to extend the term of the housing contractor for up to 5 years based on their performance.
Motion: Move to continue SIGMIS as a multi-service SIG for the next 4 years.
Motion: Move to continue SIGSIM as a conference-only SIG for the next 2 years.
Motion: The SGB EC thanks Elli Mylonas, SIGWEB Chair for her efforts to revitalize SIGWEB. The SGB EC recommends that SIGWEB remain in transition.
A report will be presented to the SGB EC at the next SGB meeting. The report should include the progress on making up the back newsletter issues, and also an update on other SIG activities. The SGB EC will make a recommendation on transition or changing of status. In addition a communication should be sent to the membership informing them of the newsletter status and the plans for SIGWEB.
Motion: The SGB EC thanks John Goldthwaite, SIGCAPH Chair for his efforts to revitalize SIGCAPH. The SGB EC recommends that SIGCAPH remain in transition.
A report should be presented to the SGB EC at the next SGB meeting. The report should include the progress on making up the back newsletter issues, and also a final decision on whether or not SIGCAPH will switch to conference-only SIG status. The SGB EC will then make a recommendation on transition or changing of status. In addition the EC advises SIGCAPH to issue a letter to the membership informing them of the newsletter status and the direction the SIG will be taking.
Motion: The SGB EC thanks Gary Lamont, SIGAPP Chair, for keeping us informed on SAC activities. The SGB EC recommends that SIGAPP remain in transition.
Before the next SGB meeting SIGAPP should provide a plan for volunteer development and a recommendation for the new SIG Chair. When this is approved the rest of the SIGAPP Executive Committee can be appointed by the Chair. The Chair will present a report on SIGAPP to the SGB EC at the next SGB meeting.
Motion: The SGB EC thanks SIGAPL Chair Bob Brown for bringing the SIG's newsletter issues up to date. SIGAPL is now a conference SIG and is no longer in transition. Viability review in 2 years.
Motion: The SGB EC appreciates the efforts of Wolfgang Prinz to reorganize SIGGROUP and bring it out of transition. The SGB EC will take SIGGROUP out of transition allowing them to conduct an election, once a full slate of candidates has been submitted.
The slate must be communicated to Alan Bernbaum by May 31st. The SGB EC appoints Wolfgang Prinz acting Chair until the election is completed. The SIG Chair will present an update on the proposed SIGGROUP activities (conferences, bulletin, Kluwer journal, awards) to the SGB EC at the next meeting SGB meeting
ACM Queue’s “Research for Practice” serves up expert-curated guides to the best of computing research, and relates these breakthroughs to the challenges that software engineers face every day. This installment, “The DevOps Phenomenon” by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald and Helmut Krcmar, gives an overview of stories from across the industry about software organizations overcoming early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between software and operations teams, faster delivery times for new software features, and achieving higher levels of stability.
Written by leading domain experts for software engineers, ACM Case Studies provide an in-depth look at how software teams overcome specific challenges by implementing new technologies, adopting new practices, or a combination of both. Often through first-hand accounts, these pieces explore what the challenges were, the tools and techniques that were used to combat them, and the solution that was achieved.