GNOME/Wiki Layout

From openSUSE

Background

The goal of this proposal is:

1. Make GNOME-related content well-organized
2. Help GNOME in openSUSE's Wiki be easily discoverable
3. Encourage participation in the openSUSE GNOME Project

Please take a moment and review the following proposal and offer your own suggestions. Are we missing something? Are there other pages in the Wiki already we should be linking to?

Tasks

GNOME Wiki Tasks

Layout Guidelines

• New pages related to "GNOME" should be created as a subpage of /GNOME/ (many examples above)
  • For example,

    http://en.opensuse.org/GNOME/My_New_Page

• New (and already existing) pages should be marked with

  [[Category:GNOME]]

  which will make them show up at Category:GNOME.

Meetings

• All meeting information should be collected under GNOME/Meetings
• All meeting information pages shoulde use Template:Meeting_GNOME
• Individual meetings are at GNOME/Meetings/YYYYMMDD
• GNOME/Meetings/Current redirects to the next meeting
• Links to past meetings should be added to GNOME/Meetings/Archives and Meetings/Archive
• Meetings/GNOME_Meeting_YYYY-MM-DD redirects to GNOME/Meetings/YYYYMMDD
• Meetings/GNOME_Meeting_YYYY-MM-DD/transcript redirects to GNOME/Meetings/YYYYMMDD/transcript

When?

Right now! Jump in and help on the Wiki Tasks page.

Initial Layout Proposal

• Make http://en.opensuse.org/GNOME the main "jumping-off" point for the wiki where the bulk of this below will be included
  • Have http://en.opensuse.org/GNOME_Team include a link to the GNOME page
  • Use a table split up into four areas to help people know where to get information
    • Participating
      • Code of Conduct - I don't see anything like this on openSUSE.org, but perhaps we could start something similar to GNOME's Code of Conduct page. It'd be completely voluntary, but strongly encouraged. People who've agreed to follow the GNOME Code of Conduct have signed the signatures page.
        • See Guiding Principles. Contributors to openSUSE in the future will also be required to sign these in the upcoming User Directory. --apokryphos 22:16, 18 September 2007 (UTC)
        • In comparing Guiding Principles and the GNOME Code of Conduct pages, I find the latter to be much easier to digest, wrap my hands around, and feel confident about "signing" in agreement. I wonder if there's any way we could change the short version in the Guiding Principles to be more direct and concise. --btimothy
      • Link to openSUSE install page
      • Link directly to submitting a bug for GNOME in openSUSE
      • New ideas for openSUSE?
        • Link to openSUSE GNOME Wishlist
          • List the software you think should be added to the distro here
        • Link to openSUSE Idea Website
          • List new project ideas here
        • Link to openSUSE GNOME Ideas Page
          • New wiki page where people can suggest GNOME-specific ideas for openSUSE
          • This should be used for any sort of off-the-cuff brainstorming. If you have a quick idea that doesn't really require the structure of the Idea Website, jot it down here!
      • Software Repositories (Link to http://en.opensuse.org/GNOME/Software_Repositories)
        • Migrate the information currently on http://en.opensuse.org/GNOME to this page
      • Link to translating pages (both openSUSE pages and upstream GNOME)
    • Developing
      • Packaging Standards and Practices (Link to http://en.opensuse.org/Packaging)
      • Patch Guidelines (Link to http://en.opensuse.org/GNOME/Patches )
        • New document that describes the recommended way the GNOME team should create patches
        • Should describe how to name patches (i.e., *.patch, *.diff, *.dif), whether to include the bug number, etc.
        • What, if any comment at the top of the patch file should be added?
        • Howto/link of how to create patches
      • Upstreaming Practices (Link to http://en.opensuse.org/GNOME/Upstreaming )
        • Describe general process of upstreaming or link to it
        • Detail general conditions of when to upstream a bug and what should be done
      • Most Annoying Bugs (Link to http://en.opensuse.org/GNOME/Bugs)
      • Code (http://en.opensuse.org/GNOME/Code)
        • Links to SVN, tarballs, and other resources where developers can get access to code
      • Link to some sort of page that would explain GNOME:Community and its policies
    • Planning
      • Team Goals (Link to http://en.opensuse.org/GNOME/Goals)
        • List the goals of the openSUSE GNOME Team
          • Next 90 days
          • Future
        • The goals should encourage others to join the team to help accomplish them?
      • Team Tasks (Link to http://en.opensuse.org/GNOME/Tasks)
        • List team assignments
          • Show the assignee or whether it's up for grabs by anyone
      • GNOME Roadmap for the 10.3 Release (Link to existing 10.3 Release Roadmap)
        • http://en.opensuse.org/Roadmap/10.3:GNOME
      • GNOME Roadmap for the 11.0 Release
        • Create a new roadmap/plan for what the GNOME team will be doing for openSUSE 11 and link to it here
        • openSUSE GNOME post 10.3 ideas
      • Meeting Agendas (Link to http://en.opensuse.org/GNOME/Meetings, which should list the archived pages of all past meetings)
        • Do we need to describe the formats of our meetings, like to say who's a moderator/etc.?
        • Show page link to the next meeting so people can review/add/edit the agenda as needed.
          • This should likely be created immediately following an agenda so there's not a mad rush to figure out what to do at the last second.
      • Add links to GNOME's RoadMap (upstream)
    • Communicating
      • List #opensuse-gnome IRC
      • List opensuse-gnome mailing list
      • Link to the GNOME Team Page