Rich Freeman wrote:
> How about "contact" instead of team.
> there is no meaning to a contact besides being CC'ed on bugs.
Please simply call it cc then? :)
//Peter
On Tue, 9 Dec 2014 16:23:57 +0100
Jeroen Roovers wrote:
> On Tue, 9 Dec 2014 12:59:26 +0100
> Ulrich Mueller wrote:
>
> > > On Tue, 9 Dec 2014, Michał Górny wrote:
> >
> > > As for the exact details, I've pretty much decided to go for
> > > featurism here, IOW making everyone happy. It als
On 2014-12-10 10:41, Sergey Popov wrote:
> 09.12.2014 14:59, Ulrich Mueller пишет:
> > "proxy-maintainer" is very confusing because you won't put the proxy
> > maintainer there, but the user who is being proxied. Please rename
> > to something like "proxied" (assuming that this exists as a word in
On Tue, Dec 9, 2014 at 11:04 AM, Michał Górny wrote:
> Dnia 2014-12-09, o godz. 12:59:26
> Ulrich Mueller napisał(a):
>
>>
>> As the previously stated goal was to get rid of herds, I don't
>> understand why you want to reintroduce them as a value of the
>> type attribute. The existing herd elemen
On Wed, Dec 10, 2014 at 2:06 AM, Ulrich Mueller wrote:
>> On Tue, 9 Dec 2014, Rich Freeman wrote:
>
>> I thought we were generally agreed we wanted to get rid of herds.
>> The goal wasn't to rename them, but to get rid of them.
>
>> We could have email aliases for bugs so that people can sign
09.12.2014 14:59, Ulrich Mueller пишет:
> "proxy-maintainer" is very confusing because you won't put the proxy
> maintainer there, but the user who is being proxied. Please rename
> to something like "proxied" (assuming that this exists as a word in
> English) or "by-proxy".
+1 for that.
Proxy ma
Dnia 2014-12-09, o godz. 00:46:28
Michał Górny napisał(a):
> So considering the previous thread, the Council and QA discussions, I
> have prepared a new version of the metadata.xml update. To hopefully
> make everyone happy, I come with this three-step process:
And the Council meeting brought a
On 09/12/14 17:34, Michał Górny wrote:
I'm all for keeping it simple. However, backwards compatibility makes
it hard to keep things simple. I'd love to do, say, metadata.yml
supporting stuff like:
- maintainer: f...@gentoo.org, b...@gentoo.org
- maintainer:
- name: Foo Bar
email: f...@
> On Tue, 9 Dec 2014, Rich Freeman wrote:
> I thought we were generally agreed we wanted to get rid of herds.
> The goal wasn't to rename them, but to get rid of them.
> We could have email aliases for bugs so that people can sign up for
> notifications, but they would NOT be considered maint
Dnia 2014-12-09, o godz. 10:15:09
Michał Górny napisał(a):
> Dnia 2014-12-09, o godz. 00:46:28
> Michał Górny napisał(a):
>
> > Hello, all.
> >
> > So considering the previous thread, the Council and QA discussions, I
> > have prepared a new version of the metadata.xml update. To hopefully
> >
Dnia 2014-12-09, o godz. 18:59:22
Ulrich Mueller napisał(a):
> > On Tue, 9 Dec 2014, Michał Górny wrote:
>
> > That is *precisely the goal* of this. We scratch and
> > , and just use well-supported tag. type=""
> > is entirely optional, unobtrusive and backwards-compatible with
> > existin
> On Tue, 9 Dec 2014, Michał Górny wrote:
> That is *precisely the goal* of this. We scratch and
> , and just use well-supported tag. type=""
> is entirely optional, unobtrusive and backwards-compatible with
> existing apps. And yes, with just tag the rule in bug
> assignment is always to t
Dnia 2014-12-09, o godz. 17:17:35
"Andreas K. Huettel" napisał(a):
>
> > > As far as I know the typical way to edit metadata.xml files for all of us
> > > is still by hand in a text editor, and I prefer a lot typing
> > >
> > > kde
> > >
> > > over
> > >
> > > kde
> >
> >
> > k...@gentoo.
> > As far as I know the typical way to edit metadata.xml files for all of us
> > is still by hand in a text editor, and I prefer a lot typing
> >
> > kde
> >
> > over
> >
> > kde
>
>
> k...@gentoo.org
> Lovely KDE herd
>
>
> to be more precise.
Ugh. Even more ugly stuff from the depar
Dnia 2014-12-09, o godz. 12:59:26
Ulrich Mueller napisał(a):
> > On Tue, 9 Dec 2014, Michał Górny wrote:
>
> > As for the exact details, I've pretty much decided to go for
> > featurism here, IOW making everyone happy. It also proves how absurd
> > typing maintainers is but if you really fee
Dnia 2014-12-09, o godz. 16:49:24
"Andreas K. Huettel" napisał(a):
> Am Dienstag 09 Dezember 2014, 00:46:28 schrieb Michał Górny:
> > 2. Convert to ,
>
> Could any please explain to me why this additional
> xmlfication is of any ?
>
> As far as I know the typical way to edit metadata.xml fil
Am Dienstag 09 Dezember 2014, 00:46:28 schrieb Michał Górny:
> 2. Convert to ,
Could any please explain to me why this additional
xmlfication is of any ?
As far as I know the typical way to edit metadata.xml files for all of us is
still by hand in a text editor, and I prefer a lot typing
kde
On Tue, 9 Dec 2014 12:59:26 +0100
Ulrich Mueller wrote:
> > On Tue, 9 Dec 2014, Michał Górny wrote:
>
> > As for the exact details, I've pretty much decided to go for
> > featurism here, IOW making everyone happy. It also proves how absurd
> > typing maintainers is but if you really feel lik
> On Tue, 9 Dec 2014, Michał Górny wrote:
> As for the exact details, I've pretty much decided to go for
> featurism here, IOW making everyone happy. It also proves how absurd
> typing maintainers is but if you really feel like having it, sure.
> The default is 'developer', tags would be conv
Dnia 2014-12-09, o godz. 00:46:28
Michał Górny napisał(a):
> Hello, all.
>
> So considering the previous thread, the Council and QA discussions, I
> have prepared a new version of the metadata.xml update. To hopefully
> make everyone happy, I come with this three-step process:
>
> 1. Add type="
Hello, all.
So considering the previous thread, the Council and QA discussions, I
have prepared a new version of the metadata.xml update. To hopefully
make everyone happy, I come with this three-step process:
1. Add type="" attribute to tag (see attached patch),
2. Convert to ,
3. Eventually
21 matches
Mail list logo