<story><title>Helping Cairo, the rendering library</title><url>https://people.gnome.org/~federico/blog/helping-cairo.html</url></story><parent_chain><item><author>kjksf</author><text>Unfortunate reality is that Cairo project doesn&amp;#x27;t want to be helped.&lt;p&gt;I&amp;#x27;ve been checking Cairo from time to time for a very long time. There was a period of active development because it was used by FireFox and, I think, had at least one dev working on it paid by Intel.&lt;p&gt;But there&amp;#x27;s no indication that the project wants your help. See &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.cairographics.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.cairographics.org&amp;#x2F;&lt;/a&gt; and try to find the part that tells you how to submit a patch. To submit a bug you need to use a mailing list or antiquated bugzilla instance.&lt;p&gt;Cairo is ostensibly a Gnome-affiliated project as it&amp;#x27;s used in Gtk. Federico is a big deal in Gnome project.&lt;p&gt;It&amp;#x27;s telling that he had to setup up essentially a personal fork of Cairo on gitlab to do any work.&lt;p&gt;At this point in time, moving the code officially to GitHub (or GitLab) from anongit.freedesktop.org should be a no brainer if your goal is to have contributors.</text></item></parent_chain><comment><author>tetromino_</author><text>You are claiming that Cairo doesn&amp;#x27;t want to be helped, but your actual complaint seems to be that Cairo uses a development workflow that you personally dislike and see as old-fashioned.</text></comment>
<story><title>Helping Cairo, the rendering library</title><url>https://people.gnome.org/~federico/blog/helping-cairo.html</url></story><parent_chain><item><author>kjksf</author><text>Unfortunate reality is that Cairo project doesn&amp;#x27;t want to be helped.&lt;p&gt;I&amp;#x27;ve been checking Cairo from time to time for a very long time. There was a period of active development because it was used by FireFox and, I think, had at least one dev working on it paid by Intel.&lt;p&gt;But there&amp;#x27;s no indication that the project wants your help. See &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.cairographics.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.cairographics.org&amp;#x2F;&lt;/a&gt; and try to find the part that tells you how to submit a patch. To submit a bug you need to use a mailing list or antiquated bugzilla instance.&lt;p&gt;Cairo is ostensibly a Gnome-affiliated project as it&amp;#x27;s used in Gtk. Federico is a big deal in Gnome project.&lt;p&gt;It&amp;#x27;s telling that he had to setup up essentially a personal fork of Cairo on gitlab to do any work.&lt;p&gt;At this point in time, moving the code officially to GitHub (or GitLab) from anongit.freedesktop.org should be a no brainer if your goal is to have contributors.</text></item></parent_chain><comment><author>newnewpdro</author><text>They talk about patch submission in the downloads page git subsection, and the documentation page welcomes contributions in the first paragraph.&lt;p&gt;I can&amp;#x27;t speak for the Cairo project, but some projects prefer there to be a slight barrier to patch submissions to improve the signal:noise ratio.  Anyone vested in a well-formed patch should be motivated enough to send an email to either a mailing list or any of the developers found in the git commit history.  Reviewing patches takes significant time, so it can make sense to require the submitter to invest a bit of time before consuming yours as maintainer.</text></comment>