Re: Plug-in no longer working since update on Manjaro

--===============2274356620652435981==
Content-Type: multipart/alternative; boundary="00000000000095a3e6058e944cb8"

--00000000000095a3e6058e944cb8
Content-Type: text/plain; charset="UTF-8"

On Thu, Jul 25, 2019 at 5:50 PM Kip Warner <[email protected]> wrote:

> I think this would be a good project for my friend Reed to look into
> maintaining. I've copied him. Please consider following up with him.
>

Great! I'm following up to the list at the same time as I guess this is
interesting for everyone.

I don't think we have a written 'policy' for taking over a possibly
abandoned project, but this is my advice.

1. Get familiar with the codebase, open merge requests for some open issues
you find on GitLab (this issue with extensions might be a good starting
point).
2. Create a personal fork. Look at the existing merge requests and include
any good ones in your fork. Leave questions and comments on the MRs that
you're not sure about merging. Get people from the community to test out
your fork.
3. Try to speak with the existing maintainers (see the MAINTAINERS file in
the tree). They may have already noticed your review activity and your
existing fork, if not, be sure to make them aware of it. The work you've
done will make it obvious that you're ready to step up as a maintainer.
They'll hopefully advise you how to proceed.
4. If you can't get in touch with any maintainers, things are a bit more
difficult, but you'll be able to get the right permissions eventually. Ask
for help whenever you are stuck. https://wiki.gnome.org/MaintainersCorner
gives a rough guide of what to do.

Sam

--00000000000095a3e6058e944cb8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Thu, Jul 25, 2019 at 5:50 PM Kip Warner &lt;<a href=3D"mailto:kip=
@thevertigo.com">[email protected]</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
I think this would be a good project for my friend Reed to look into<br>
maintaining. I&#39;ve copied him. Please consider following up with him.<br=
></blockquote><div><br></div><div>Great! I&#39;m following up to the list a=
t the same time as I guess this is interesting for everyone.</div></div><di=
v class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">I don&#39;t th=
ink we have a written &#39;policy&#39; for taking over a possibly abandoned=
 project, but this is my advice.<br></div><div class=3D"gmail_quote"><br></=
div><div class=3D"gmail_quote">1. Get familiar with the codebase, open merg=
e requests for some open issues you find on GitLab (this issue with extensi=
ons might be a good starting point).</div><div class=3D"gmail_quote">2. Cre=
ate a personal fork. Look at the existing merge requests and include any go=
od ones in your fork. Leave questions and comments on the MRs that you&#39;=
re not sure about merging. Get people from the community to test out your f=
ork.<br></div><div class=3D"gmail_quote">3. Try to speak with the existing =
maintainers (see the MAINTAINERS file in the tree). They may have already n=
oticed your review activity and your existing fork, if not, be sure to make=
 them aware of it. The work you&#39;ve done will make it obvious that you&#=
39;re ready to step up as a maintainer. They&#39;ll hopefully advise you ho=
w to proceed.</div><div class=3D"gmail_quote">4. If you can&#39;t get in to=
uch with any maintainers, things are a bit more difficult, but you&#39;ll b=
e able to get the right permissions eventually. Ask for help whenever you a=
re stuck. <a href=3D"https://wiki.gnome.org/MaintainersCorner">https://wiki=
.gnome.org/MaintainersCorner</a> gives a rough guide of what to do.</div><d=
iv class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">Sam<br></div>=
</div>

--00000000000095a3e6058e944cb8--

--===============2274356620652435981==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rhythmbox-devel mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/rhythmbox-devel

--===============2274356620652435981==--