Hello,
I am looking for review and sponsorship
of initial 'verdigris' upload.
This is the first time me following your team's guidelines,
so take it easy :)
repo: https://salsa.debian.org/qt-kde-team/qt-extras/verdigris
mentors: https://mentors.debian.net/package/verdigris
Thanks,
Olzhas Rakhimo
El viernes, 16 de febrero de 2018 18:03:42 -03 Olzhas Rakhimov escribió:
> On Fri, Feb 16, 2018 at 06:01:15PM -0300, Lisandro Damián Nicanor Pérez
Meyer wrote:
> > salsa account accepted, would you like verdigris as repo name?
>
> Thanks!
> Yes, verdigris name is ok for the repo.
>
> Olzhas
Her
On Fri, Feb 16, 2018 at 06:01:15PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> salsa account accepted, would you like verdigris as repo name?
Thanks!
Yes, verdigris name is ok for the repo.
Olzhas
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
On Fri, Feb 16, 2018 at 09:57:45AM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> I think that if you are interested in maintaining it then it's interesting,
> and sounds like qt-extras is a great place for it. I hardly doubt that we will
> use it on Qt/KDE packages by default right now, but
El viernes, 16 de febrero de 2018 05:45:33 -03 Boris Pek escribió:
> Hi,
>
> >> Ok. In this case I may suggest you to use workflow similar to one in
> >> Debian
> >> Perl Group [1]. They do not add extra members to the main group [2], but
> >> allow members joining to specific sub-groups (for
El jueves, 15 de febrero de 2018 16:19:52 -03 Andrey Rahmatullin escribió:
> On Thu, Feb 15, 2018 at 04:02:01PM -0300, Lisandro Damián Nicanor Pérez
Meyer wrote:
> > - Is anyone willing to take kchmviewer?
>
> Yes, I still intend to update it.
Great! I must admit it's in my ToDo list too, but I
El jueves, 15 de febrero de 2018 18:23:01 -03 Olzhas Rakhimov escribió:
[snip]
> > What would we gain from using it?
>
> The major points for me from replacing Qt moc w/ Verdigris:
>
> 0. Works w/ modern C++ code (templates, nested classes)
> 1. Compilation time improvement
>(easy parallel bu
Hi,
>> Ok. In this case I may suggest you to use workflow similar to one in Debian
>> Perl Group [1]. They do not add extra members to the main group [2], but
>> allow members joining to specific sub-groups (for example, [3]). Though
>> it is only in plans; they have not done the migration fro
