[prev in list] [next in list] [prev in thread] [next in thread] 

List:       taglib-devel
Subject:    Re: TagLib's future
From:       "Ibrahim Sha'ath" <ibrahimshaath () gmail ! com>
Date:       2015-05-14 14:44:11
Message-ID: CAHpOMzuCr1ONWQHNqkUE_AffBqb7PYvUmbCjHF7PC9AMguU9wg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I definitely don't have the time (or sufficient domain knowledge) to really
contribute to TagLib but I'd like to say thank you, Luk=C3=A1=C5=A1, for al=
l your
hard work.

--
Ibrahim

On 14 May 2015 at 15:32, Sander Jansen <s.jansen@gmail.com> wrote:

>
>
> On Wed, May 13, 2015 at 9:06 AM, Tsuda Kageyu <tsuda.kageyu@gmail.com>
> wrote:
>
>> Hi Luk=C3=A1=C5=A1,
>>
>> First, thank you for kindly accepting a lot of pull requests of mine.
>>
>> Although I'm willing to take on your burden and repay your kindness, I
>> don't think I'm an appropriate person for reviewing the code, since most
>> changes since v1.9.1 has been made by me. (And I'm the type of individua=
l
>> that doesn't hesitate to make drastic changes as you know.)
>>
>> So I suggest that we release beta versions several times and call for
>> feedback from the users (especially developers of the projects rely on
>> TagLib).
>>
>> Cheers,
>> Kageyu
>>
>> 2015-05-13 8:20 GMT+09:00 Luk=C3=A1=C5=A1 Lalinsk=C3=BD <lalinsky@gmail.=
com>:
>>
>>> Hi all,
>>>
>>> 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 a=
nd
>>> generally become the maintainer of the project, but since then I have n=
ot
>>> worked on many projects that use TagLib and I currently have no direct =
use
>>> for it myself.
>>>
>>> We have have a long list of pull requests on GitHub, a lot of changes i=
n
>>> 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 relea=
se,
>>> it will end similarly badly.
>>>
>>> So I'd like to discuss what would be the best way to go forward.
>>>
>>> Lukas
>>>
>>>
>>> _______________________________________________
>>> taglib-devel mailing list
>>> taglib-devel@kde.org
>>> https://mail.kde.org/mailman/listinfo/taglib-devel
>>>
>>>
>>
>> _______________________________________________
>> taglib-devel mailing list
>> taglib-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/taglib-devel
>>
>>
> I'd be happy to review current master branch changes. Should I use github
> comments to add a reviewed by?
>
>
>
> _______________________________________________
> taglib-devel mailing list
> taglib-devel@kde.org
> https://mail.kde.org/mailman/listinfo/taglib-devel
>
>

[Attachment #5 (text/html)]

<div dir="ltr">I definitely don&#39;t have the time (or sufficient domain knowledge) \
to really contribute to TagLib but I&#39;d like to say thank you, Lukáš, for all \
your hard work.<br><div><br></div><div>--</div><div>Ibrahim</div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On 14 May 2015 at 15:32, Sander \
Jansen <span dir="ltr">&lt;<a href="mailto:s.jansen@gmail.com" \
target="_blank">s.jansen@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div><div class="h5"><br><div \
class="gmail_extra"><br><div class="gmail_quote">On Wed, May 13, 2015 at 9:06 AM, \
Tsuda Kageyu <span dir="ltr">&lt;<a href="mailto:tsuda.kageyu@gmail.com" \
target="_blank">tsuda.kageyu@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div>Hi \
Lukáš,</div><div><br></div><div>First, thank you for kindly accepting a lot of pull \
requests of mine.</div><div><br></div><div>Although I&#39;m willing to take on your \
burden and repay your kindness, I don&#39;t think I&#39;m an appropriate person for \
reviewing the code, since most changes since v1.9.1 has been made by me. (And I&#39;m \
the type of individual that doesn&#39;t hesitate to make drastic changes as you \
know.)</div><div><br></div><div>So I suggest that we release beta versions several \
times and call for feedback from the users (especially developers of the projects \
rely on TagLib).</div><div><br></div><div>Cheers,</div><div>Kageyu</div></div><div \
class="gmail_extra"><br><div class="gmail_quote"><div><div>2015-05-13 8:20 GMT+09:00 \
Lukáš Lalinský <span dir="ltr">&lt;<a href="mailto:lalinsky@gmail.com" \
target="_blank">lalinsky@gmail.com</a>&gt;</span>:<br></div></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div><div><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&#39;m not really able to do it, I&#39;d like to discuss TagLib&#39;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&#39;t take my time to review all \
the changes properly and the result was not very good. I&#39;m afraid that if I try \
to do this new release, it will end similarly badly.</div><div><br></div><div>So \
I&#39;d like to discuss what would be the best way to go forward.  \
</div><div><br></div><div>Lukas</div><div><br></div></div> \
<br></div></div>_______________________________________________<br> taglib-devel \
mailing list<br> <a href="mailto:taglib-devel@kde.org" \
target="_blank">taglib-devel@kde.org</a><br> <a \
href="https://mail.kde.org/mailman/listinfo/taglib-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br> \
<br></blockquote></div><br></div> \
<br>_______________________________________________<br> taglib-devel mailing list<br>
<a href="mailto:taglib-devel@kde.org" target="_blank">taglib-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/taglib-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br> \
<br></blockquote></div><br></div></div></div><div class="gmail_extra">I&#39;d be \
happy to review current master branch changes. Should I use github comments to add a \
reviewed by?</div><div class="gmail_extra"><br></div><div \
class="gmail_extra"><br></div></div> \
<br>_______________________________________________<br> taglib-devel mailing list<br>
<a href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/taglib-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br> \
<br></blockquote></div><br></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