GnomeAmor

De Wiki GNOME Chile
Saltar a: navegación, buscar

http://ramnet.se/~nisse/diverse/temp/gnomelovelogo.png

GnomeAmor es una iniciativa que pretende ayudar a las personas que quieren comenzar a contribuir en GNOME. Esta página ofrese una colección de enlaces a recursos utiles para un aspirante a desarrollador, "testers", documentadores o simples entuciastas de GNOME.

Contenido

Contactos

Además de esta página, el proyecto GnomeAmor también posee:

Esta página está enfocada en desarroladores, pero también existen otras formas de unirtenos.

Comenzando

Estas guías proveen información útil en los distintos pasos que un principiante puede seguir para comenzar a contribuir, y saber como funcionan las cosas.

Guías Tecnicas

Please maintain consistency when adding a new reference to keep this page as clear as possible...

  • A Getting Started Guide for those interested in developing with GNOME is being written. It hasn't been updated for a few months, but it currently contains
  • Quick overviews of the important tools you need to use and websites you should be aware of
  • Programming tutorials in c, c++, perl, and python for using glade/libglade and gconf (with gtk+ being learned along the way)
  • Debugging tutorials covering gdb, strace, and valgrind (specifically memcheck)
  • Detailed guide on building GNOME from CVS (use of jhbuild)
  • A "What in the world is that?!?" section to help explain all the cryptic but common tools, libraries, and filenames.
  • Overview of the GNOME Platform (by ShaunMcCance)
  • A GnomeGlossary of the terms that get bandied around mailing lists
  • [wiki:Self:GettingTraces Capturing Stack Traces]: If you are trying to fix a specific bug in GNOME that is a crash, this guide explains how to obtain a stack trace --one of the first important pieces of information needed in most cases to move towards fixing the problem.
  • [wiki:Self:GnomeLove/SubmittingPatches Submitting Patches]: In order to submit improvements you make to various GNOME modules, you will need to make and submit patches. This page explains how to do so (more thoroughly than does the section in the above tutorial on this topic).
  • [wiki:Self:JhbuildDependencies Jhbuild Dependencies]: Jhbuild is used to compile GNOME from CVS. This page lists what software you will need to run jhbuild.

Giving love to projects

||<tablewidth="100%" #eeeeee> /!\ Please always ask the maintainers before starting a task by adding a note in bugzilla for the corresponding bug.||

Case 1: You don't want to work on a specific project

Then the GnomeGoals are made for you. Instead of project-based bug correction, it generally consists of task-based desktop-wide bug corrections. You then learn a single task, but touch to every project, which is a good exercise to get started. The tasks are usually simple and short, and accompanied with guidelines. You also need less commitment in the project, so this is perfect for people wanting to contribute on an irregular basis.

Case 2: You don't know which project you want to work on

Look at bugzilla bugs with the gnome-love keyword. These are tasks suitable for new developers, for many GNOME projects.

Case 3: You want to work on a specific project

Then check out the ModuleMaintenanceWorkspaces and pick up a project. Following the associated love-bugs link will lead you to the tasks suitable for GNOME Lovers for that project.

Some projects also have a favorite entry point, or additionnal info for GNOME Lovers:

  • /GnomeKeyringManager - Project developed only by GNOME lovers. Go there to learn and contribute to it.
  • [wiki:Self:LockdownEditor Lockdown Editor] - A simple idea in need of developers.
  • ["GStreamer"] task list
  • ["GnomeApplets"]
  • ["Gedit"]
  • The GNOME System Tools task list.
  • Totem: [1].
  • ["Yelp"]
  • ["Metacity"]: The HACKING and code overview files orient you to the code, point out relevant standards, explain a lot of the specialized utilities for testing metacity, show how to debug your code (debuggers don't work well for Metacity), and provide a list of tasks you can work on.
  • ["Epiphany"]: There are lots of older, sometimes untargeted bugs for Epiphany that the development team doesn't get around to. Help would be most welcome!
  • GnomePanel

Other applications:

Case 4: You want to work on new projects or new features

There are a bunch of ideas for new projects and features in GNOME, make sure to get the opinion of the affected maintainers or the community because the project in question could have become obsolete, invalid or yet implemented with the passing of time:

  • [wiki:Self:MentoredProjects Mentored Projects].
  • [wiki:Self:SummerOfCode2006/Ideas Ideas] and [wiki:Self:SummerOfCode2006/Performance Performance projects] from [wiki:Self:SummerOfCode2006 SummerOfCode2006].
  • [wiki:Self:SummerOutreachProjects Summer Outreach Projects]
  • GNOME desktop bounties

GNOME Love Days

The underlying idea behind this, is to have one special day for a given task, for example finding bugs, or improving a specific part of GNOME... On this day, someone will stay on the #gnome-love irc channel to give some support and help you on this task. ||When||Topic|| ||2005-10-30, from 14:00 UTC||[wiki:Self:GnomeLove_2fPerformanceLoveDay Performance Love Day]||

Articles and tutorials

Tips & Tricks

  • [:WritingPortableCode:Writing Portable Code]
  • [wiki:Self:BestPractices Best Practices]
  • wiki:Self:Bloopers
  • [wiki:Self:GnomeRecipes GNOME Recipes]

Internationalization

GUI

  • [wiki:Self:GnomeLove/UIManagerTutorial GtkUIManager tutorial] for making Menus and Toolbars
  • [wiki:Self:GnomeLove/DragNDropTutorial Drag and drop tutorial] for your GTK+ applications
  • GtkTreeView tutorial by Tim-Philipp Muller
  • GtkTextView tutorial by Vijay Kumars
  • [:GnomeLove/PanelAppletTutorial:Panel Applet Tutorial]

Other

Books

  • Matthias Warkus wrote a book covering the GNOME 2 desktop environment.

{en} The Official GNOME 2 Developer's Guide

{de} GNOME 2.0: Das Entwickler-Handbuch

Herramientas personales
Espacios de nombres

Variantes
Acciones
Navegación
Herramientas