> On Tue, 9 Sep 2014 21:45:49 +0200
> Michał Górny wrote:
>>
>> Let's keep it short: I think herds don't serve any special purpose
>> nowadays. Their existence is mostly resulting in lack of consistency
>> and inconveniences.
>>
Resurrecting this thread per the last council decision:
"The counci
On Sat, 27 Sep 2014 18:45:12 -0400
Rich Freeman wrote:
> So, there was some discussion on -dev, apparently some discussion I
> wasn't a part of, and some that I was (such is the nature of IRC).
Knowledge codification is nice; otherwise, this is just-another-thread.
> I think it would make sense
On Sun, 28 Sep 2014 00:21:43 +0200
Michał Górny wrote:
> I don't know if you know it but setting up the project wiki page takes
> less time than reaching into depths of CVS and editing herds.xml.
Editing and committing a change to herds.xml takes me less characters
than this quoted paragraph, do
> On Sun, 28 Sep 2014, Tom Wijsman wrote:
> Yes, if you do create a one-on-one mapping then it becomes possible.
> The question becomes "does every herd want to become a
> (sub)project?".
Another example: The Emacs project maintains two herds "emacs" and
"xemacs", for GNU Emacs and XEmacs rel
On Sat, Sep 27, 2014 at 6:13 PM, Tom Wijsman wrote:
> The question becomes "does every herd want to become a (sub)project?".
>
So, there was some discussion on -dev, apparently some discussion I
wasn't a part of, and some that I was (such is the nature of IRC).
I think it would make sense to tak
Dnia 2014-09-28, o godz. 00:13:15
Tom Wijsman napisał(a):
> On Sat, 27 Sep 2014 17:54:48 -0400
> "Anthony G. Basile" wrote:
>
> > The hardened project has two herds: hardened and hardened-kernel, the
> > former for toolchain related stuff and the latter for the kernel. We
> > really need to
On Sat, 27 Sep 2014 17:54:48 -0400
"Anthony G. Basile" wrote:
> The hardened project has two herds: hardened and hardened-kernel, the
> former for toolchain related stuff and the latter for the kernel. We
> really need to keep that distinction. So mapping herds to projects
> doesn't work. B
On 09/27/14 17:35, Tom Wijsman wrote:
On Sat, 27 Sep 2014 06:25:28 -0400
Rich Freeman wrote:
On Sat, Sep 27, 2014 at 4:58 AM, Jeroen Roovers
wrote:
Right now, CC'ing a single alias is inconvenient, but under your
proposal, you might need to CC a dozen or more people instead of
that alias.
Am Samstag, 27. September 2014, 23:41:04 schrieb Tom Wijsman:
> On Sat, 27 Sep 2014 09:11:57 -0400
>
> Rich Freeman wrote:
> > Is there some policy that says that a project cannot be a maintainer?
>
> Is there some policy that says that a herd cannot be a herd?
Only for sufficiently small value
On Sat, 27 Sep 2014 09:11:57 -0400
Rich Freeman wrote:
> Is there some policy that says that a project cannot be a maintainer?
Is there some policy that says that a herd cannot be a herd?
On Sat, 27 Sep 2014 06:25:28 -0400
Rich Freeman wrote:
> On Sat, Sep 27, 2014 at 4:58 AM, Jeroen Roovers
> wrote:
> >
> > Right now, CC'ing a single alias is inconvenient, but under your
> > proposal, you might need to CC a dozen or more people instead of
> > that alias.
> >
>
> That is incorre
On Sat, 27 Sep 2014 09:11:57 -0400
Rich Freeman wrote:
> Is there some policy that says that a project cannot be a maintainer?
I guess you missed an interesting discussion on #gentoo-dev today.
jer
On Sat, Sep 27, 2014 at 6:51 AM, Jeroen Roovers wrote:
> On Sat, 27 Sep 2014 06:25:28 -0400
> Rich Freeman wrote:
>
>> On Sat, Sep 27, 2014 at 4:58 AM, Jeroen Roovers
>> wrote:
>> >
>> > Right now, CC'ing a single alias is inconvenient, but under your
>> > proposal, you might need to CC a dozen
On Sat, 27 Sep 2014 06:25:28 -0400
Rich Freeman wrote:
> On Sat, Sep 27, 2014 at 4:58 AM, Jeroen Roovers
> wrote:
> >
> > Right now, CC'ing a single alias is inconvenient, but under your
> > proposal, you might need to CC a dozen or more people instead of
> > that alias.
> >
>
> That is incorre
On Sat, Sep 27, 2014 at 4:58 AM, Jeroen Roovers wrote:
>
> Right now, CC'ing a single alias is inconvenient, but under your
> proposal, you might need to CC a dozen or more people instead of that
> alias.
>
That is incorrect. Herds would be replaced with projects, not with
lists of individual (n
On Tue, 9 Sep 2014 21:45:49 +0200
Michał Górny wrote:
> Hello,
>
> Let's keep it short: I think herds don't serve any special purpose
> nowadays. Their existence is mostly resulting in lack of consistency
> and inconveniences.
>
> In particular:
>
> 1. We have two different tags in metadata.xm
On Thu, Sep 25, 2014 at 11:49:53AM -0400, Rich Freeman wrote:
> On Thu, Sep 25, 2014 at 11:29 AM, W. Trevor King wrote:
> > What about a entry in metadata.xml that points people to
> > the suggested mailing list for discussing a package? Bugzilla
> > could automatically add the list to its CC li
On Thu, Sep 25, 2014 at 11:29 AM, W. Trevor King wrote:
>
> What about a entry in metadata.xml that points people to the
> suggested mailing list for discussing a package? Bugzilla could
> automatically add the list to its CC list, and both devs and non-devs
> could join the list without adding
On Thu, Sep 25, 2014 at 11:00:32AM -0400, Rich Freeman wrote:
> On Wed, Sep 24, 2014 at 12:31 PM, W. Trevor King wrote:
> > On Wed, Sep 10, 2014 at 04:18:40PM +0200, Michał Górny wrote:
> >>
> >> 4. A mail alias that is not project :). For example, we have
> >> clang@ for easily aggregating all cla
On Wed, Sep 24, 2014 at 12:31 PM, W. Trevor King wrote:
> On Wed, Sep 10, 2014 at 04:18:40PM +0200, Michał Górny wrote:
>>
>> 4. A mail alias that is not project :). For example, we have clang@ for
>> easily aggregating all clang-related build failures and other bugs but
>> it isn't a formal team.
On Wed, Sep 10, 2014 at 04:18:40PM +0200, Michał Górny wrote:
> Dnia 2014-09-10, o godz. 07:53:31 Rich Freeman napisał(a):
> > On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos wrote:
> > > Personally I would vote for simply have a tag pointing to
> > > the alias but we would still need to keep a list
On Thu, 11 Sep 2014 21:00:16 +0100
Markos Chandras wrote:
> please do not go offtopic discussing the recruitment process. I simply
> mentioned one of the designated ways we have to ask for help. If you
> don't like it, propose a better method.
Please do not go offtopic about your own "getting pe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/11/2014 07:30 PM, Tom Wijsman wrote:
> On Wed, 10 Sep 2014 21:21:24 +0100 Markos Chandras
> wrote:
>
>> On 09/10/2014 03:01 PM, Tom Wijsman wrote:
>>>
>>> +1; to summarize my thoughts: Herds misrepresent manpower.
>>>
>> true and false.
>
On Wed, 10 Sep 2014 21:21:24 +0100
Markos Chandras wrote:
> On 09/10/2014 03:01 PM, Tom Wijsman wrote:
> >
> > +1; to summarize my thoughts: Herds misrepresent manpower.
> >
> true and false.
More true than false.
> undertakers often remove dead herds.
How often? What is considered dead? How
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/10/2014 03:01 PM, Tom Wijsman wrote:
> On Tue, 9 Sep 2014 21:45:49 +0200 Michał Górny
> wrote:
>
>> Let's keep it short: I think herds don't serve any special
>> purpose nowadays. Their existence is mostly resulting in lack of
>> consistency
On Wed, Sep 10, 2014 at 10:18 AM, Michał Górny wrote:
> Dnia 2014-09-10, o godz. 07:53:31
> Rich Freeman napisał(a):
>
>> On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos wrote:
>> >
>> > Personally I would vote for simply have a tag pointing to
>> > the alias but we would still need to keep a list
Dnia 2014-09-10, o godz. 07:53:31
Rich Freeman napisał(a):
> On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos wrote:
> >
> > Personally I would vote for simply have a tag pointing to
> > the alias but we would still need to keep a list of real maintainers for
> > that alias as usually not all peopl
On Tue, 9 Sep 2014 21:45:49 +0200
Michał Górny wrote:
> Let's keep it short: I think herds don't serve any special purpose
> nowadays. Their existence is mostly resulting in lack of consistency
> and inconveniences.
+1; to summarize my thoughts: Herds misrepresent manpower.
On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos wrote:
>
> Personally I would vote for simply have a tag pointing to
> the alias but we would still need to keep a list of real maintainers for
> that alias as usually not all people listed in the alias are willing to
> maintain the packages.
>
I thin
On Tue, Sep 9, 2014 at 6:54 PM, Kent Fredric wrote:
>
> On 10 September 2014 10:23, Michał Górny wrote:
>>
>> I don't understand your concern. I'm only saying we should stop relying
>> on that stupid out-of-repository herds.xml file and put the e-mail
>> address directly in metadata.xml. Bugzilla
El mar, 09-09-2014 a las 21:45 +0200, Michał Górny escribió:
[...]
> I believe it would be benfiicial to just deprecate and eventually drop
> in favor of explicit using the alias. I don't know
> if someone has other use of herds.xml but it the contents are either
> outdated or redundant. Therefor
On 10 September 2014 10:23, Michał Górny wrote:
> I don't understand your concern. I'm only saying we should stop relying
> on that stupid out-of-repository herds.xml file and put the e-mail
> address directly in metadata.xml. Bugzilla and bug assignment would
> work pretty much the same -- excep
Dnia 2014-09-09, o godz. 16:46:29
"Anthony G. Basile" napisał(a):
> On 09/09/14 15:56, Rich Freeman wrote:
> > On Tue, Sep 9, 2014 at 3:45 PM, Michał Górny wrote:
> >> Let's keep it short: I think herds don't serve any special purpose
> >> nowadays. Their existence is mostly resulting in lack of
On 09/09/14 15:56, Rich Freeman wrote:
On Tue, Sep 9, 2014 at 3:45 PM, Michał Górny wrote:
Let's keep it short: I think herds don't serve any special purpose
nowadays. Their existence is mostly resulting in lack of consistency
and inconveniences.
The original design was that packages belong t
On Tue, Sep 9, 2014 at 3:45 PM, Michał Górny wrote:
>
> Let's keep it short: I think herds don't serve any special purpose
> nowadays. Their existence is mostly resulting in lack of consistency
> and inconveniences.
>
The original design was that packages belong to herds, and developers
belong to
Hello,
Let's keep it short: I think herds don't serve any special purpose
nowadays. Their existence is mostly resulting in lack of consistency
and inconveniences.
In particular:
1. We have two different tags in metadata.xml that serve a similar
purpose -- and , with being less
descriptive. For
36 matches
Mail list logo
