[prev in list] [next in list] [prev in thread] [next in thread]
List: taglib-devel
Subject: Re: TagLib's future
From: Sander Jansen <s.jansen () gmail ! com>
Date: 2015-05-17 14:20:23
Message-ID: CACj81kGxLo2qwDFaLphXQkm7qfZ1+gShcbmP2PmRein0=OhoKg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, May 12, 2015 at 6:20 PM, Luk=C3=A1=C5=A1 Lalinsk=C3=BD <lalinsky@gm=
ail.com> wrote:
> Hi all,
>
> Since there are people asking for a new release more and more often and i=
t
> seems that I'm not really able to do it, I'd like to discuss TagLib's
> future. A few years back Scott asked me to coordinate the 1.6 release and
> generally become the maintainer of the project, but since then I have not
> worked on many projects that use TagLib and I currently have no direct us=
e
> for it myself.
>
> We have have a long list of pull requests on GitHub, a lot of changes in
> master and at least one backward-compatible release pending. I find it ve=
ry
> hard to motivate myself to review pull requests, especially if they are
> questionable in some way. This was already showing in the last release,
> where I didn't take my time to review all the changes properly and the
> result was not very good. I'm afraid that if I try to do this new release=
,
> it will end similarly badly.
>
> So I'd like to discuss what would be the best way to go forward.
>
> Lukas
>
>
A few questions come to mind.....
How involved do you think you'll be in the near future or a year from now?
Do you have time and interest in doing a 2.0 release out this year?
Do you still want to maintain taglib? Who else has currently git write
access?
Depending on how you answers those, it may be beneficial to find additional
co-maintainers to handle releases more often (especially the bugfix
releases).
Cheers,
Sander
[Attachment #5 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May \
12, 2015 at 6:20 PM, Lukáš Lalinský <span dir="ltr"><<a \
href="mailto:lalinsky@gmail.com" target="_blank">lalinsky@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>Since there \
are people asking for a new release more and more often and it seems that I'm not \
really able to do it, I'd like to discuss TagLib's future. A few years back \
Scott asked me to coordinate the 1.6 release and generally become the maintainer of \
the project, but since then I have not worked on many projects that use TagLib and I \
currently have no direct use for it myself.</div><div><br></div><div>We have have a \
long list of pull requests on GitHub, a lot of changes in master and at least one \
backward-compatible release pending. I find it very hard to motivate myself to review \
pull requests, especially if they are questionable in some way. This was already \
showing in the last release, where I didn't take my time to review all the \
changes properly and the result was not very good. I'm afraid that if I try to do \
this new release, it will end similarly badly.</div><div><br></div><div>So I'd \
like to discuss what would be the best way to go forward. \
</div><div><br></div><div>Lukas</div><div><br></div></div></blockquote><div><br></div><div>A \
few questions come to mind.....</div><div>How involved do you think you'll be in \
the near future or a year from now? Do you have time and interest in doing a 2.0 \
release out this year?</div><div>Do you still want to maintain taglib? Who else has \
currently git write access? </div><div><br></div><div>Depending on how you answers \
those, it may be beneficial to find additional co-maintainers to handle releases more \
often (especially the bugfix \
releases).</div><div><br></div><div>Cheers,</div><div><br></div><div>Sander</div><div> \
</div></div></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
taglib-devel mailing list
taglib-devel@kde.org
https://mail.kde.org/mailman/listinfo/taglib-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic