<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet title="XSL formatting" type="text/xsl" href="https://www.vuntz.net/journal/feed/rss2/xslt" ?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>mon journal - par Vincent - Planet answers      - Comments</title>
    <link>https://www.vuntz.net/journal/</link>
    <atom:link href="https://www.vuntz.net/journal/feed/rss2/comments/353" rel="self" type="application/rss+xml" />
    <description>mon journal - par Vincent</description>
    <language>en</language>
    <pubDate>Mon, 09 Feb 2026 20:56:34 +0000</pubDate>
    <copyright></copyright>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <generator>Dotclear</generator>
                        <item>
          <title>Planet answers - Cassidy</title>
          <link>https://www.vuntz.net/journal/post/2005/12/19/353-planet-answers#c1769</link>
          <guid isPermaLink="false">urn:md5:39fb5b15cca53d849210b16e5c0f6010</guid>
          <pubDate>Mon, 19 Dec 2005 21:16:03 +0000</pubDate>
          <dc:creator>Cassidy</dc:creator>
          <description>&lt;p&gt;I agree, a gnome-patch-review-day could be a great idea.&lt;br /&gt;
Just sorting patch to be reviewed in some categories (trivial,minor,big) using a wiki page, a bugzilla feature or something like that; then maintainers would have a better idea of what sort of patches they have to review.&lt;br /&gt;
That would be also interesting to put the light on modules where the maintainer doesn't have time enough to review patchs (when this list become too big).&lt;/p&gt;</description>
        </item>
                              <item>
          <title>Planet answers - Murray Cumming</title>
          <link>https://www.vuntz.net/journal/post/2005/12/19/353-planet-answers#c1768</link>
          <guid isPermaLink="false">urn:md5:00e7ab05e887a0ade57e6b148bb63aa3</guid>
          <pubDate>Mon, 19 Dec 2005 15:20:54 +0000</pubDate>
          <dc:creator>Murray Cumming</dc:creator>
          <description>&lt;p&gt;The solution to ignored patches is for maintainers to ask for co-maintainers. I don't understand why some maintainers don't ask for help.&lt;/p&gt;</description>
        </item>
                              <item>
          <title>Planet answers - Devin</title>
          <link>https://www.vuntz.net/journal/post/2005/12/19/353-planet-answers#c1767</link>
          <guid isPermaLink="false">urn:md5:7b93c5000817633fe01b93a91e218e47</guid>
          <pubDate>Mon, 19 Dec 2005 13:46:06 +0000</pubDate>
          <dc:creator>Devin</dc:creator>
          <description>&lt;p&gt;We have Gnome-Love days, and Gnome-Bug-Days, why not have Gnome-Patch-Review-Days? I'm sure lots of people can help to review those small-three-lines-patches, and take care of them.&lt;br /&gt;
&lt;br /&gt;
I know its not that simple with large patches, and that these ones must be reviewed by maintainers, but who sends a large-patch already knows it, and will wait.&lt;br /&gt;
&lt;br /&gt;
In my own opinion a gnome-patch-day, could help a coder to get involved into gnome, by getting a patch, checking it, testing it, etc... You can get in contact with gnome in a gnome-love day, and then continue as a natural way in a gnome-review-patch-day.&lt;br /&gt;
&lt;br /&gt;
&lt;/p&gt;</description>
        </item>
                              <item>
          <title>Planet answers - yop</title>
          <link>https://www.vuntz.net/journal/post/2005/12/19/353-planet-answers#c1766</link>
          <guid isPermaLink="false">urn:md5:264f07343e96654f905c156735104b0d</guid>
          <pubDate>Mon, 19 Dec 2005 13:33:20 +0000</pubDate>
          <dc:creator>yop</dc:creator>
          <description>&lt;p&gt;I'd have to agree that new contributors (patches) often gets completly ignored.&lt;br /&gt;
Or sometimes a contribution is rejected by the maintainer because they want to add the feature&lt;br /&gt;
their own way. Happened to me on well know KDE music player for a popular requested feature.&lt;br /&gt;
People don't like being ignored, and people not being stupid go away and sometimes never come back.&lt;br /&gt;
In fact, large projects such as GNOME or KDE feel close source because you can't get anything&lt;br /&gt;
in if you're not friend with the developer or spend 24/24 in IRC. My feeling is it's just&lt;br /&gt;
a waste of time.&lt;br /&gt;
I would advice new contributors to help a smaller project, it's much more easy to get accepted&lt;br /&gt;
and not lost in the general noise. Another good way to get a grasp of the project if to fix bugs but if &lt;br /&gt;
there are ignored or if it take 6 months to get the code in it's also a big waste of time...&lt;br /&gt;
&lt;/p&gt;</description>
        </item>
                              <item>
          <title>Planet answers - Staz</title>
          <link>https://www.vuntz.net/journal/post/2005/12/19/353-planet-answers#c1765</link>
          <guid isPermaLink="false">urn:md5:825e514539c293b529f7b6c451ada679</guid>
          <pubDate>Mon, 19 Dec 2005 13:14:06 +0000</pubDate>
          <dc:creator>Staz</dc:creator>
          <description>&lt;p&gt;As said in Luis' blog' comments, one of the principal problem is that potential contributer are getting ignored, having to wait months to get a review on a 3 lines patchs ... &lt;br /&gt;
In fact after discuting a little on IRC, it's even worse, some maintener thinks it's *normal* to wait. One even told me than it's nothing to wait 6 months to contribute to the gnome project :/&lt;br /&gt;
&lt;br /&gt;
And yes technical is also a problem (I don't like C much) and lack of technical doc too.&lt;br /&gt;
&lt;/p&gt;</description>
        </item>
            </channel>
</rss>
