GNOME.org
 

Re: [gnome-love]Hi!

Is there a page where I can read about the purpose of gnome-love.


Miguel has been working on the document that describes 
the gnome-love project but he has been busy latelly, this
is the only reason we have not announced it in
gnome-announce-list gnome org 


The real problem is that Chema is afraid of writing anything that
looks like documentation.  He has some sort of panic to anything
remotely that looks like a collection of english paragraphs.

So I have indeed a set of HTML files that describes what the project
is, but they are not finished.  Here they are:

<html>
<title>The Gnome Love Project</title>
<body bgcolor="white" fgcolor="black">
<link rel="STYLESHEET" type="text/css" href="style.css">

<center>
<b>
<font size=+3>The Gnome Love Project</font><br>
<br>
<font size=+2>Miguel de Icaza</font><br>(<a href="mailto:miguel gnome org"><tt>miguel gnome org</tt></a>)
</b>
</center>

<p>
<h3>Introduction to the The Gnome Love project.</h3>

        The Gnome project has produced a confortable desktop
        environment to use.  New members have joined our community and
        sometimes they do not know how to work together with us, or
        something they just need a helping hand that will guide them
        through the process of contributing to Gnome.  <p>

        The `Gnome Love' project is an effort to match people
        interested in improving Gnome, our applications, our desktop
        and our libraries with people who can guide them through this
        process and can hold their hands: we are basically trying to
        create a Gnome Hacking School. <p>

        The attendees to the Internet-based Gnome Hacking School get
        to learn how to work with other teams, how to work with the
        Gnome community, how to work with the Gnome technologies, and
        they get to innovate and create on a rich platform.<p>

        The Gnome project benefits from the motivation and the courage
        of new and motivated people who come fresh to the project, and
        can introduce new ideas, more innovation, and fresh energy
        into the project.<p>

</body>
</html>

<html>
<title>GNOME Love Projects</title>
<body bgcolor="white" fgcolor="black">
<link rel="STYLESHEET" type="text/css" href="style.css">

<h1>Areas of Work.</h1>

There are many areas in which you can cooperate to improve GNOME
depending on your skills, please refer to:

<a
href="http://developer.gnome.org/doc/tutorials/joining-gnome/choosingtherightjob.html";>http://developer.gnome.org/doc/tutorials/joining-gnome/choosingtherightjob.html</a>


<ul>
        <li><b>Programmers:</b> <a href="#improving">Improving
        existing applications</a>; <a href="#bugfixes">Bug Fixing
        existing applications</a>; <a href="#new">Writing new
        programs</a><p>

        <li><b>Finding problems:</b> Finding problems in GNOME is an
        important task as this will help new programmers to pick up
        tasks and improve GNOME.  Without your valuable input there is
        not much we can do.
</ul>

<h2>Improving Documentation</h2>

<h2>Hacking Tasks</h2>

<a name="improving">
<h3>Improving Existing Applications</h3>

        Current applications might lack some functionality in one or
        more areas, and we could improve an existing application to
        make it better for day to day use.<p>
        
        There are various areas in which an application can be
        improved:
        <ul>
                <li><b>Usability:</b> many times an application will
                have all the features that it is supposed to have, but
                using some of those features might be complicated, or
                it would inflict some pain in the user in terms of
                repetitive actions.  Applications should be written in
                such a way that they help the user become more
                effective while using the program.
                <p>
                Joel has a lot of information on this subject: <a
                href="http://joel.editthispage.com/stories/storyReader$51";>here</a>
                and <a href="http://joel.editthispage.com/stories/storyReader$55";>here</a>
                <p>
                
                <li><b>Robustness:</b> it is important to make applications
                robust when dealing with user input.  The application
                should do what it is expected to do and not have any
                special surprises.<p>
                
                <li><b>Making applications simpler:</b> It is our job as
                engineers of the GNOME system to make a number of
                decisions for our users, because most of the time
                people are not using our application because that is
                the only thing they care about in life.  They are
                using it because they are trying to get something
                done.
                <p>
                Our task here is to reduce the number of configuration
                options in some applications and provide better, saner
                defaults.  To learn more about this, read <a
                href="http://joel.editthispage.com/stories/storyReader$61";>
                Joel again</a>, quoting him:<p>

                <blockquote>
                <i>
                Every time you provide an option,
                you're asking the user to make a decision. That means
                they will have to think about something and decide
                about it. It's not necessarily a bad thing, but, in
                general, you should always try to minimize the number
                of decisions that people have to make.
                </i>
                </blockquote>
                <p>
                
        </ul>
        
<a name="bugfixes">
<h3>Bug Fixing Existing Applications</h3>

        There are many problems in existing applications: bugs,
        usability problems, people or design mistakes.  Many people do
        file bugs to the GNOME bug tracking system.
        <p>
        A good source of problems in GNOME are the bugtracking
        systems:
        <ul>
                <li><b>GNOME Bugzilla:</b> <a
                href="http://bugzilla.gnome.org";>http://bugzilla.gnome.org</a>.
                Most components of the GNOME desktop have their "bug
                home" here.<p> 

                <li><b>Eazel Bugzilla:</b> <a
                href="http://bugzilla.eazel.com";>http://bugzilla.eazel.com</a>,
                covers Nautilus, Medusa, OAF, Sawfish, Gnome Pilot,
                reef, xml-i18n-tools, GNOME VFS and Eazel Tools.<p>

                <li><b>Ximian Bugzilla:</b> <a
                href="http://bugzilla.ximian.com";>http://bugzilla.ximian.com</a>,
                covers Bonobo, Evolution, Gal, GtkHTML, GdkPixbuf, Red
                Carpet, Ximian Setup Tools.
        </ul>

        <p>

        
        
        
<a name="new">
<h3>Writing New Programs</h3>

        Before you start a 
</body>
</html>
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]