public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Maintainer for Compiz?
Date: Thu, 23 Feb 2012 01:41:05 -0500	[thread overview]
Message-ID: <CAJ0EP42eMzyfY7BNkOJX39g1PdTT8jhP44zsQ3VyN_X4K5fXhw@mail.gmail.com> (raw)
In-Reply-To: <20120222230334.5585ba23@Michelle>

On Wed, Feb 22, 2012 at 6:03 PM, Chandler Paul <thatslyude@gmail.com> wrote:
> Hello, I've asked this question around in the IRC, and I've done a bit of Googling, but I haven't been able to find anything on this, so I hope that this is the correct place to ask. Apparently, the Compiz-fusion package is masked because it lacks a maintainer. However, from what it looks like it's not a proxied maintainer, as it's not on the list. I was thinking of stepping up to be a maintainer for it, but I'm assuming that would mean writing patches for it. I do have a relatively OK understanding of C and C++, but I don't know if it would be good enough to be able to write patches for it. So, I guess what I'm asking is what exactly would maintaining the package entail, and how would I go about becoming a maintainer?
> Also, I really hope this isn't the wrong place to ask, as I didn't go straight to here before doing some research, hopefully it isn't though...
>

Compiz has "desktop-effects" listed as its maintainer. However, the
desktop-effects herd has indicated that they are no longer maintaining
compiz. You are welcome to proxy maintain it if you feel you are up to
the task.

Maintaining a package means a few things:

- Troubleshooting bug reports. I think this is probably the most important part.
- Following upstream development, and working with them to resolve issues.
- Ebuild maintenance. This may involve some patching to fix issues
when necessary.

So, as a starting point, I would suggest you take a look through
bugs.gentoo.org for open bug reports related to compiz.

You will want to set up a local portage overlay to play with if you
have not done so already. You can use this to test any fixes you may
develop, as well as improve your ebuild writing skills.



  reply	other threads:[~2012-02-23  9:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 23:03 [gentoo-project] Maintainer for Compiz? Chandler Paul
2012-02-23  6:41 ` Mike Gilbert [this message]
2012-02-23  7:32 ` "Paweł Hajdan, Jr."

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ0EP42eMzyfY7BNkOJX39g1PdTT8jhP44zsQ3VyN_X4K5fXhw@mail.gmail.com \
    --to=floppym@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox