Re: Structured list of my patches

[ng0]

Pjotr Prins writes:

> Thanks ng0,
>
> Embarrassing.

I don't agree, but okay.

> At FOSDEM I'll bring up the topic again of our submission system. Good
> topic for the 'Future of Guix' panel.

I have ideas, as I made some further investigations over the last
months into source code managements and issue/bug tracking
systems, but I think at this point it's better a discussion that
we should have in an meeting (AFK/IRL) and not per email/irc
discussion. It requires no immediate solution, but we could meet
this summer?
I'm also curious about the input and results from chats and
discussions at FOSDEM, can you (or someone else) try to make an
protocol or some other quick format of notes to publish?

Among other things I discovered features of Mantis 2.0 (close
bugs via some keyword in git commits!), I discovered tuleap
(https://www.tuleap.org/), pagure (https://pagure.io/pagure ,
https://fedoramagazine.org/pagure-diy-git-project-hosting/ ) and
thought a bit more about the review situation which is also
rooted in the fact that much more people contribute than review.
My personal contribution to help the current review situation is
to do at least one review per week now.

Now for this long list of patches (I know I don't have to explain
myself, but it's probably appropriate in this case): I evaluate
what I do regulary, and the result was that realized that I got
off the road(map) a bit. This chaos is the reason everything
roadmap related is at 80% but the last 20% were suffering from
distraction.

> Pj.
>
> On Thu, Feb 02, 2017 at 12:26:08AM +0000, ng0 wrote:
>> Recently I started to sent 3 classes of patches, and hoped that
>> the coverletters description would help. Apparently it doesn't.
>> 
>> I will add the lists.gnu.org archive links as I don't think the
>> majority of people here can search for mailids with their mail
>> readers.
>> 
>> I am pretty sure I missed some patches, but that's it for now.
>> Looking at the public[0] part of my branches, I have about 15-20
>> more batches of packages I must drop/finish/get rid off so that I
>> can focus on my work again.
>> 
>> * Patches which need QA review (considered DONE from my side)
>> 
>>   * no-more-secrets
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02365.html
>>   * sedsed
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02336.html
>>   * libextractor inputs
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02319.html
>>   * blists
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02316.html
>>   * tinycm
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02308.html
>>   * python-pykka (I won't debbug the testsuite and will drop this
>>     at the end of the month, but I am willing apply small
>>     changes)
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02272.html
>>   * mbedtls, hiawatha
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02105.html
>>   * Murmur (mumble server)
>>     https://lists.gnu.org/archive/html/guix-devel/2017-02/msg00021.html
>>   * emacs-pretty-mode
>>     https://lists.gnu.org/archive/html/guix-devel/2017-02/msg00017.html
>>   * lush2
>>   * scsh
>>   * shadow (update)
>> 
>> * Patches which are dropped from my tree (ie: deleted), free for
>>   others to pick up
>> 
>>   * supercollider
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02284.html
>>   * Krita
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02294.html
>>   * GNOME evolution
>> 
>> * Patches which are status: RFC
>> 
>>   * sway
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02345.html
>>   * debbugs (currently debbuging this, but comments are welcome)
>>     https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02110.html
>> 
>> 
>> 
>> 
>> [0]: https://pagure.io/guix-dev
>> -- 
>> ng0 . https://www.inventati.org/patternsinthechaos/
>> 


-- 
ng0 . https://www.inventati.org/patternsinthechaos/