2

I have submitted a few bug reports over the years, most have never been closed (not closed fixed, anyway). I think I could speed this process a bit if I submitted patches. However:

  • How do I submit code? Would just diff output do? Should I create a Launchpad project branching from the corresponding Ubuntu project?

    If this were on Github, I'd do a fork-and-pull-request. On Launchpad, there seems to be a parallel as documented in this answer.

  • Are there conventions? Something like the Debian Policy Manual? How does this apply to non-code submissions, like documentation in the form of manpages, etc.?

  • Are there special licensing requirements? IIRC the FSF requires that ownership of code contributions to FSF-copyrighted GNU software be transferred to them. Does Canonical have some such requirement?

  • Is Launchpad sufficient as a medium of communication, or do I have to post on mailing lists as well (maybe ubuntu-devel, maybe some other list)?

  • Should I add unit tests to code that I touch and submit those tests as well, assuming they aren't tested already?

This question applies to contributing code to software that's purely from Ubuntu (like the Ubiquity installer or the Ubuntu manpages repository) or patches for third party software to fix regressions that are unlikely to be fixed upstream (for example, Ubuntu maintained patches for GNOME Terminal). Essentially, work that Canonical devs maintain.

3

0

You must log in to answer this question.

Browse other questions tagged .