Ubuntu Wiki

General Agenda Items and Proposals

PLEASE COME TO THE MEETINGS PREPARED.

This means:

1. If there is an issue for the project add it to the agenda.
2. Agenda items then should be discussed "informally" on #ubuntu-learning or using the mailing list.
3. Ideally, meetings then are for decision making, project votes.
4. Agenda items that require more then 5 minutes of discussion may need to be deferred.

details on agenda topics

• Mission Statement:
  • "Our mission with this project is to create an interactive learning environment based on Moodle to support new users becoming more engaged in the Ubuntu community. Our goal is to take new motivated users and turn them into contributing members of the community."

    
    I would like to reword this so it is not too narrow in focus. A simple mission statement would be:

    The project is focused on building and maintaining an interactive learning environment(s) to support all aspects of the Ubuntu Ecosystem. - combined effort of doctormo / pleia2 / cprofitt

• Goals:
  • Goal generation methodology:
    • The Learning project represents a variety of different approaches to learning within the community. A representative from each of the key portions of the community (IRC-based learning, Real Life Classroom-based learning, Moodle-based learning, Project-centric -motu, -docs, -bugs, etc learning, etc) should come up with their own list of goals.
  • On Current Page:
    • Our goal is to take new motivated users and turn them into contributing members of the community.
    • Our initial goal is to provide four programs for the new user, the sysadmin, marketing, and a stream for someone who wants to contribute to Ubuntu.
  • Suggested:
    • to produce courses that make it easier for organizations and users to adopt Ubuntu as their OS
    • to provide courses for users who wish to advocate for Ubuntu adoption (examples below)
      • GIMP
      • IRC moderation / channel management
      • Live Streaming Video w/ Ubuntu
    • etc.
• Structure:
  • The structure of this team has not been discussed. I think one of the steps that need to be addressed is the structure of the team. In oder for cohesion to be maintained I think that some form of board should be formed involving the various teams that will be participating in the project. With or without a board some roles and responsibilities should be determined (assigned) as well.
• Meetings:
  • We need to determine when the majority of people can meet. Weekends are not a good time for most people. I would like to suggest 23:00 GMT every other Friday while we are building steam, but I am open to other suggestions.