Mo Zhou writes:
> Is the recommendation working well under most circumstances?
> I mean, different teams have already made their conventions
> at these point, such as go team, rust team, nvidia team, etc.
> These team designed "local" recommendations always adapt
> well with special property of th
> "Mo" == Mo Zhou writes:
Mo> As you said, recommendations are merely recommendations. Debian
Mo> developers customed to their own workflow may not necessarily
Mo> follow the recommendations. However, the recommendation makes a
Mo> difference for newbies or newcomers, if thei
On 2019-09-25 07:15, Sam Hartman wrote:
>> "Scott" == Scott Kitterman writes:
>
> >> For several of these recommendations if I cannot get consensus, I
> >> will call for a GR myself.
>
> Scott> What do you think is important enough in this area that you
> Scott> would rather
On September 24, 2019 11:15:33 PM UTC, Sam Hartman wrote:
>> "Scott" == Scott Kitterman writes:
>
> >> For several of these recommendations if I cannot get consensus, I
>>> will call for a GR myself.
>
>Scott> What do you think is important enough in this area that you
>Scott
On 2019-09-25 05:32, Bernd Zeimetz wrote:
> On 9/24/19 3:21 PM, Holger Levsen wrote:
>> On Tue, Sep 24, 2019 at 08:10:39AM -0400, Sam Hartman wrote:
>>> For several of these recommendations if I cannot get consensus, I will
>>> call for a GR myself.
>>
>> TBH, I'm not thrilled to read this, though
> "Scott" == Scott Kitterman writes:
>> For several of these recommendations if I cannot get consensus, I
>> will call for a GR myself.
Scott> What do you think is important enough in this area that you
Scott> would rather have people not contribute to Debian if they
Scot
On 9/24/19 3:21 PM, Holger Levsen wrote:
> On Tue, Sep 24, 2019 at 08:10:39AM -0400, Sam Hartman wrote:
>> For several of these recommendations if I cannot get consensus, I will
>> call for a GR myself.
>
> TBH, I'm not thrilled to read this, though of course it's in your rights
> to do that.
Hi,
On 9/24/19 8:45 AM, Thomas Goirand wrote:
> Why would it be unacceptable that the whole of the archive be maintained
> in Git using Salsa? Wouldn't it be much nicer for everyone?
basically because sometimes it makes sense to have packages on github
(or gitlab, ...), close (or even within) ups
On September 24, 2019 12:10:39 PM UTC, Sam Hartman wrote:
>> "Bernd" == Bernd Zeimetz writes:
>
>Bernd> On 7/23/19 7:31 PM, Thomas Goirand wrote:
>>> 1- Mandating VcsGit and VcsBrowser, meaning we do mandate using
>>> Git for packaging.
>
> Bernd> why is that a reason for a G
The following changes to the debian-maintainers keyring have just been
activated:
jianfen...@ubuntukylin.com
Full name: handsome_feng
Added key: 86C8001E95309DA7195964829BB850C013111F0C
jlle...@member.fsf.org
Full name: Joan Lledó
Added key: 8ADC0DB9D4DB344D91F7888CA199D76BCA469
Hello,
On Tue 24 Sep 2019 at 08:10AM -04, Sam Hartman wrote:
> So, I agree that a GR would be the wrong approach if we thought that we
> could get to a consensus strong enough for the policy editors.
>
> I also agree that the policy editors have the technical authority to use
> a different (non-c
On Tue, Sep 24, 2019 at 08:10:39AM -0400, Sam Hartman wrote:
> For several of these recommendations if I cannot get consensus, I will
> call for a GR myself.
TBH, I'm not thrilled to read this, though of course it's in your rights
to do that. (I'm afraid such GRs would cost a lot of time which co
> "Bernd" == Bernd Zeimetz writes:
Bernd> On 7/23/19 7:31 PM, Thomas Goirand wrote:
>> 1- Mandating VcsGit and VcsBrowser, meaning we do mandate using
>> Git for packaging.
Bernd> why is that a reason for a GR? its a question for the policy
Bernd> editors.
So, I agree t
13 matches
Mail list logo
