“The meeting initially planned at 5pm GMT on the phone actually occured on
IRC due to difficulties with international phone calls.”

Minutes of the GNOME-2.0 Coordination meeting 11 September 2001
From: Daniel Veillard 
To: foundation-announce@gnome.org
Cc: gnome-hackers@gnome.org
Date: Thu, 13 Sep 2001 08:31:27 -0400


Minutes of the GNOME-2.0 Coordination meeting 11 September 2001
      ===============================================================

 The meeting initially planned at 5pm GMT on the phone actually occured on
IRC due to difficulties with international phone calls.

Presents:
=========

    Daniel Veillard  (chairing, minutes) (dropped 6:11)
    Sander Vesik
    Maciej Stachowiak (chaired once DV got disconnected)
    Dan Mueth
    Gregory Leblanc
    Calum Benson
    Jamin Gray
    Jeff Waugh
    Telsa Gwynne
    Kjartan Maraas   (joined 5:39)
    Michael Meeks    (joined 6:21)


Regrets or missing:
===================
    Seth Nickell (represented by Calum Benson)
    Karl Gaffney

Decisions:
==========
    - The main goal of that meeting was to build a team and split task
      identified by Maciej in a mail before the call.
    - The team has been defined, the task have been split between members
    - The meeting schedule has been defined, every week at least on Fridays

New Actions:
============

  ACTION: Jeff to send the full IRC logs to DV for the minutes
    => done

  ACTION: Sander to set up weekly phone conferences 

  ACTION: Dan to ask John Fleck about Docs coordinator duties

Discussion:
===========

 - collecting people on IRC after a short phone debacle

 - getting a temporary chair and minute taker for this first meeting
   => DV

 - presentation of the people and motivation for working on the Gnome-2.0
   coordination, the following miss presentations from the people who joined
   late or were missing the meeting:

   Daniel Veillard (DV): 
     primarilly interested in making sure that we have a process to
     get Gnome-2.0 out in a reasonable time frame. I can commit to
     administrative tasks like chairing or taking minutes, not that I feel
     urged to do them but to make sure there will be someone doing
     them. Will happilly work on other stuff if I'm confident my help is
     not needed

   Maciej Stachowiak (mjs):
     As far as motivation, I'd like to help get things organized and
     carry over some of the lessons from GNOME 1.4 and other large-scale
     release efforts I have seen

   Sander Vesik (sander):
     Got picked as one of two Gnome2 release co-coordinators, interested
     to see that there is a Gnome2 that is relatively timely, bugfree
     and actually works

   Jamin Gray (Jamin):
     I was one of the GNOME 1.4 Fifth Toe coordinators, and volunteered
     to do the same for GNOME 2.  I'm interested in making it a very
     solid release.

   Jeff Waugh (jdub):
     Would like to assist with bugs, outreach, doing the dirty work for
     better developers so GNOME 2.0 rocks very hard.

   Greg Leblanc (greg):
     trying to make sure that we have binaries for GNOME, so that we can test

   Jody Goldberg (jody): 
     I maintain Gnumeric and would like to help with GNOME Office and 5th Toe.

   Calum Benson (calum):
     deputising for Seth Nickell... who's hoping to beat up people about
     usability bugs and prioritise the ones that need fixing before
     we'll allow a release...

   Dan Mueth (muet):
     I plan to help out coordinating the docs and hope to help carry
     over some of the experience learned by GNOME 1.4 release team,
     along with mjs.

   Though not strictly minutes from the meeting, we noted at that point that
   Michael volunteered for the "Technical Coordinator" role and Karl for
   "QA Coordinator"

  - The list of roles identified by Maciej are available from the the release
    list archive them associated with their description [1], I will enclose
    a copy below since access to the archive is not public.

    There is 15 roles identified, and the goal is to allocate people to
    them accoding to:
      - their willingness to do it
      - time available
      - previous experience

  - Most of the following discussion was to check and allocate each role
    ending up with the following composition of the Gnome-2.0 Release Team:

      - Chair: Maciej Stachowiak
      - Secretary: Jeff Waugh
      - Bugmeister: Kjartan Marass and Telsa Gwynne
      - Project Manager: Maciej Stachowiak
      - Release Engineer: Sander Vesik
      - QA Coordinator: Karl Gaffney
      - Docs Coordinator: Dan Mueth (unless John Fleck want to step in)
      - L10N Coordinator: Kjartan Marass
      - Packaging Coordinator: Greg Leblanc
      - HI Coordinator: Seth Nickell
      - Technical Coordinator: Michael Meeks
      - Apps Coordinator: Sander Vesik
      - Fifth Toe Coordinator: Jamin Gray
      - GNOME Office Coordinator: Jody Golberg
      - PR Coordinator: Jeff Waugh (possibly backed up with a more
                        formal contact)

  - Deciding the date/time for the next meetings, which tend to be hard
    considering there are people in Europe, USA (both coasts) and Australia.
    Those will be phone meeting hosted by Sun Microsystem and likely to be
    becked up by an IRC log.

Daniel

[1] http://mail.gnome.org/mailman/private/gnome2-release-team/2001-September/msg00004.html 

----------- Maciej description of the Roles ------------
Some of these roles involve performing a specific function in
meetings. Others cover a project-wide aspect of project
management. Still others involve focusing on specific modules or
groups of modules. Anyway, here are some of the roles I think are
useful:


Chair      - Runs meetings; sends out agenda prior to meetings;
             makes sure agenda is covered.

Secretary  - Takes minutes at meetings; Makes sure they get sent out
             in a timely fashion.

Bugmeister - Keeps track of all critical bugs for release; makes sure
             bugs get filed as needed; does regular bugzilla queries
             to identify problem areas; works with various area
             coordinators to ensure that specific critical bug lists
             are appropriately tagged in bugzilla; goes over bug lists
             to close duplicates and other noise bugs; keeps
             bugzilla's nose clean in general.

Project Manager - Sends out schedule announcements and reminders;
                  reminds maintainers to upload packages for releases;
                  makes sure maintainers are on top of key bugs, with
                  the assistance of the bugmeister and QA coordinator;
                  works with maintainers of packages that are at risk of
                  delay to ensure problems are resolved; works with
                  release engineer to enforce freezes.

Release Engineer - Does the footwork of actually staging the release
                   packages (could be a different person for fifth toe
                   and core release); may also write or maintain tools
                   to help with the release project (library status
                   web pages, tinderbox, etc); works with project
                   manager to enforce freezes.

QA Coordinator - Organizes the testing effort by providing test plans,
                 recruiting testers, etc; ensures adequate time for QA
                 in the schedule; reports problem areas to release
                 team; works with bugmeister to make sure critical bugs
                 are in bugzilla; works with project manager to ensure
                 key bugs are given attention.

Docs Coordinator - Organizes documentation effort; ensures adequate
                   time for documentation in the schedule; works with
                   bugmeister and project manager in the area of bugs
                   that block the documentation effort; works to
                   ensure libraries have complete developer docs.

L10N Coordinator - Organizes localization / translation effort;
                   ensures adequate time for localization in schedule;
                   works with bugmeister and project manager to ensure
                   localizability bugs are recorded and given adequate
                   visibility.

Packaging Coordinator - Organizes binary packaging effort; ensures
                        availability of binaries for test releases;
                         coordinates with third-party packagers.

HI Coordinator - Works with maintainers, developers and the community
                 to determine the critical release-blocking
                 technical/infrastructure problems; works with bugmeister
                 and project manager to ensure bugs are tagged
                 appropriately and given appropriate visibility.

Technical Coordiator - Works with maintainers and developers
                       to determine the critical release-blocking
                       technical / infrastructure problems with the
                       platform; works with bugmeister to ensure these
                       are accurately reflected in bugzilla; works
                       with project manager to ensure they are given
                       appropriate attention.

Apps Coordinator - Like the technical coordinator but focuses on core
                   desktop apps (especially file manager, help
                   browser, panel, window manager and control center)
                   and integration issues among them.

Fifth Toe Coordinator - Reponsible for overall organization of fifth
                         toe release.

GNOME Office Coordinator - Reponsible for overall organization of
                           GNOME Office release, if we decide to have
                           one.

PR Coordinator - Coordinates press releases, press coverage, etc for
                 the release; not really needed until close to the end
                 of the cycle.


We don't necessarily need all of these roles filled, and as I said
previously, people could double or triple up. I think the likely
toughest role is Bugmeister so we should make sure not to overload
whoever does that. Also, the area coordinators don't necessarily have
to be the same as the person who is leader of the corresponding
project, but should be in good communication with the project leader
and have a good working knowledge of the issues.

Maciej
---------------------------



-- 
Daniel Veillard      | Red Hat Network http://redhat.com/products/network/
veillard@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

_______________________________________________
foundation-announce mailing list
foundation-announce@gnome.org
http://mail.gnome.org/mailman/listinfo/foundation-announce

NWFusion: “AT&T, Sun Microsystems, and Swiss banking software
vendor Temenos were among the technology companies
with offices in the two towers destroyed in the terrorist
attack. AT&T said it had 10 employees working on the
51st floor of the North tower — the first tower hit by a plane
— and a larger networking team working in that tower’s
basement. All escaped, according to AT&T spokesman
Phil Coathup.”

MSNBC: Here are a couple of amazing shots taken from the international space station.

ZDNET: “Last week, the Justice department relaxed its stance in the remedy phase of its case against Microsoft. According to a
recent news report, the Justice Department informed Microsoft this week that it would not pursue the tying
issue–essentially whether the integrating of Microsoft’s Internet Explorer browser with the Windows 95 and 98
operating systems was illegal. The DOJ said in a statement that it was taking these steps “in an effort to obtain
prompt, effective and certain relief for consumers.”

Advogato: “Maybe like me, some of you, some very few of you, have realized that so many geeks are showing their fear of what happens if we fight back against terrorists, but really, these are the same people who fight (in a less literal sense mind you) for such _trivial_ causes as encryption and removal of the DMCA from law. These very people are happy to be complacent to the bullies of the modern world, terrorists, but they aren’t willing to accept that fighting back, no matter how scary, may be justified.”

Kelly McNeill writes: “I think it’s fair to say that Microsoft understands the customers they are providing products for. What still puzzles me is why Microsoft has decided to take such an irresponsible attitude toward these users when integrating scripting languages into its desktop applications. A word processor, for example, does not need a scripting language that is capable of deleting the contents of a hard drive. An e-mail client does not need to be so integrated with the OS that a sender can potentially run any command they wish on the recipient’s computer, all by use of a cleverly written mail signature.”

– By Dan Berkes –
September, at least the version of it that plays in the Northern Hemisphere, is a time for changes. Minor changes, like the temperature dropping by a couple of degrees, or a few impatient leaves changing color to red and gold and dropping off. September does have one big event, however: The official start of the school year. The use of computers in education has come a long way in the 16 years that have passed since my freshman year of high school. During those dark ages of computing, we were herded in groups of 35 into the school’s computer lab for our state-mandated two weeks of computer education. For some reason that has been lost to the passage of time, we weren’t actually allowed to touch the terminals (A networked group of Acorns, believe it or not) we sat in front of until the last three or four days of the course.

When we were allowed to touch the sacred keyboards, I think the hands-on experience involved tapping in a few BASIC commands, and learning how to use some word processing program that bore no resemblance to any text editor I’ve ever used since then. And I don’t know if it’s just coincidence, but it seems there’s an awful lot of people my age who attended high school in Arizona who have a mild aversion or (in rare cases) an abnormal fear and dislike of computers. I seem to have avoided that, probably from playing on the Macintoshes and Tandy Color Computers that belonged to friends and neighbors.

It goes without saying that the computing resources available in today’s schools have vastly improved. I understand that students are even allowed to use the computers these days, and not just during some state-mandated class. Computer hardware is cheap, but commercial software is not, and that’s why it might not be surprising to discover that there’s at least a handful of academic labs running Linux. Finding decent free or affordable software to run on those boxes can be a frustrating tax: As with any other operating system, precious few titles exist.

A computer tends to take on the role of a tutor or teacher’s assistant during the early primary grades, and it’s at this level where software is most needed.

One project that shows plenty of promise is Tux4Kids, a non-profit organization formed to produce freely-available educational software for Linux and other platforms. So far, the project has released an educational typing tutor for Linux, Windows and BeOS. Also in the works are a math problem-solving game and a speech synthesis program designed to help children in learning how to read. All programs are freely available from the Tux4Kids Web site, and donations of resources (including development skills) are gratefully accepted.

You can find a wide variety of Linux-based educational software at Linux For Kids, but be prepared (as you should be anyway) to closely evaluate the software to see if it’s appropriate for your academic needs. As of this writing, one of the titles featured on the main page is Simutrans, which is an economic simulation game that’s similar in play to Railroad Tycoon. Build up an infrastructure of road, rail, and ocean transportation services to move cargo and passengers. Other games featured at Linux For Kids include math, spelling, language, arts, and even educational utility programs designed to help instructors.

Instructors and others interested in educational software can meet and exchange ideas at the Simple End User Linux education project, known better as SEUL/edu. The project hosts a mailing list for anyone interested in using Linux for all areas of education. In addition to the ongoing discussion, the project publishes a twice-monthly report on the state of Linux in education. The report highlights major or interesting items of discussion from the mailing list.

For older students interested in more than a connection to a Web search engine, consider nudging them in the direction of programming languages and Open Source projects. Or perhaps getting involved yourself — after all, the next generation of new and improved quality software has to come from somewhere, right?

We’ll have more on Linux in education in the coming weeks.

ZDNet reviews Linux-Mandrake Corporate Server version 1.0. “Networking has always been the simple solution for sharing resources, but implementing a network has never been an easy task. Linux-Mandrake Corporate Server claims to solve that problem by offering “a complete enterprise solution… [that] includes everything you need to rapidly deploy world-class Linux applications in the enterprise.” But does Mandrake Corporate Server deliver? After a week with the product we can give it a resounding “yes, maybe.””

From ZDNet: “Tuesday’s terrorist attacks in the United States and a new federal report are generating fresh debate about a system used to pinpoint a cell phone user’s location that wireless carriers are supposed to begin using Oct. 1.”

Linux Devices has the Embedded Linux Newsletter for the week of September 13th, 2001.