On Mon, 1 Apr 2024 at 19:28, Vincent Bernat wrote:
>
> On 2024-04-01 18:05, Jonathan Carter wrote:
> > The included firmware contributed to Debian 12 being a huge success,
> > but it wasn't the only factor.
>
> Unfortunately, the shipped firmwares are now almost a year old,
> including for
Le lundi, 1 avril 2024, 19.41:45 h CEST Andrey Rakhmatullin a écrit :
> Why is updating the firmware packages not trivial? Is it because of
> licensing issues? I always thought it's just copying a bunch of files from
> the linux-firmware repo (but I also often wondered why is the package
> often
Andrey Rakhmatullin dijo [Mon, Apr 01, 2024 at 10:41:45PM +0500]:
> Why is updating the firmware packages not trivial? Is it because of
> licensing issues? I always thought it's just copying a bunch of files from
> the linux-firmware repo (but I also often wondered why is the package
> often not
Hi Jonathan,
just a brief correction:
On 2024-04-01 18:05, Jonathan Carter wrote:
> I don't want to single out DSA there, it's difficult and affects many
> other teams. The Salsa CI team also spent a lot of resources (time and
> money wise) to extend testing on AMD GPUs and other AMD hardware.
On Mon, Apr 01, 2024 at 06:27:29PM +0200, Vincent Bernat wrote:
> On 2024-04-01 18:05, Jonathan Carter wrote:
> > The included firmware contributed to Debian 12 being a huge success,
> > but it wasn't the only factor.
>
> Unfortunately, the shipped firmwares are now almost a year old, including
>
On 2024-04-01 18:05, Jonathan Carter wrote:
The included firmware contributed to Debian 12 being a huge success,
but it wasn't the only factor.
Unfortunately, the shipped firmwares are now almost a year old,
including for unstable. I am following the progress since quite a few
years and I
On 2022/04/20 08:25, j...@debian.org wrote:
2022-01-12 - Milestone 1 - Transition and toolchain freeze 2022-02-12 -
Milestone 2 - Soft Freeze 2022-03-12 - Milestone 3 - Hard Freeze - for key
packages and packages without autopkgtests To be announced - Milestone 4
- Full
Freeze
Oops, that
Hello Sam,
Am Montag, 6. April 2020, 11:34:12 CEST schrieb Sam Hartman:
> Thinking about Covid-19 and what this means for the world has taken up
> much of my emotional bandwidth in March.
I haven't read anything that describes what has happened to me
as matching like this.
*distance hugs*
On Sat, Nov 2, 2019 at 7:06 AM Bernd Zeimetz wrote:
> That leads to the question how long it takes until these bugs are being
> noticed.
>
> I am definitely not going to test init scripts properly when the systemd
> units are exactly doing what they are supposed to. The number of people
> not
On 10/31/19 8:07 PM, Alf Gaida wrote:
> I read it the same way - and also a logical consequece: if these
> patches lead to bugs, the maintainer should not be forced to fix the
> mess. I for myself would just remove buggy things that nobody care in a
> certain amount of time.
That leads to the
❦ 31 octobre 2019 21:49 +01, Thomas Goirand :
> The idea has always been that it would be on best-effort from people who
> volunteer, without forcing anyone to do any sysv-rc support if they
> don't feel like it. What you describe goes along this line.
I have raised my concern about this a few
Thomas Goirand schrieb:
> "I’d very happily maintain the init script."
>
> I haven't read all the bug entry, but if someone is claiming that
> accepting such contribution is mandatory, then that's very much right,
> at least that the consensus we're in right now, indeed.
This isn't limited to
On 10/31/19 8:07 PM, Alf Gaida wrote:
> I read it the same way - and also a logical consequece: if these
> patches lead to bugs, the maintainer should not be forced to fix the
> mess. I for myself would just remove buggy things that nobody care in a
> certain amount of time.
I'd be very much fine
On 10/31/19 7:36 PM, Moritz Mühlenhoff wrote:
> Thomas Goirand schrieb:
>> My understanding is that the current guidance is that doing init script
>> isn't mandatory.
>
> With policy not updated, people claim it's mandatory, see e.g.
> #925473 on Tomcat.
Well, the policy is wrong, and should be
Simon Richter dijo [Wed, Oct 30, 2019 at 12:46:21PM +0100]:
> Hi,
>
> On Tue, Oct 29, 2019 at 10:38:32PM +0100, Thomas Goirand wrote:
>
> > If we have such vote again, I'll continue on this direction: I'd prefer
> > if we didn't have to vote.
>
> >From a Policy perspective, packages are
On Thu, 31 Oct 2019 18:40:58 +0100
Thomas Goirand wrote:
> On 10/29/19 11:19 PM, Russ Allbery wrote:
> > of clear project guidance, no one is clearly empowered to prevent
> > it from bitrotting.
What is wrong with bitrotting if nobody cares about - in case nobody
cares about it's the logical
Thomas Goirand schrieb:
> My understanding is that the current guidance is that doing init script
> isn't mandatory.
With policy not updated, people claim it's mandatory, see e.g.
#925473 on Tomcat.
The discussed GRs would provide clarification on what the project
at large actually wants (and
Russ,
On 10/29/19 11:19 PM, Russ Allbery wrote:
> [...] we do not have clear
> project consensus that sysvinit support is mandatory in new packages, so
> the support is starting to bitrot, and given the lack of clear project
> guidance, no one is clearly empowered to prevent it from bitrotting.
Sam,
thanks for the bits mail. Very interesting as usual! Just a minor
nitpick...
On Tue, Oct 29, 2019 at 01:16:21PM -0400, Sam Hartman wrote:
> * I spent some money.
No, you didn't, Debian did, as you correctly described below. You
approved that spending.
--
cheers,
Holger
(I'm not
Hi,
On Tue, Oct 29, 2019 at 10:38:32PM +0100, Thomas Goirand wrote:
> If we have such vote again, I'll continue on this direction: I'd prefer
> if we didn't have to vote.
>From a Policy perspective, packages are supposed to integrate into the
system by providing init scripts, and Policy has a
> "Wouter" == Wouter Verhelst writes:
Wouter> Having said that,
Wouter> Sam: I notice that you've not sent a draft of your GR
Wouter> proposal to the -vote mailing list yet. It has been my
Wouter> experience over the years that that is not generally a good
Wouter> idea.
On Tue, Oct 29, 2019 at 03:19:03PM -0700, Russ Allbery wrote:
> We've now had several years of essentially declining to make a decision
> and trying to see if the project can muddle through, and while I feel
> somewhat vindicated by the fact that this didn't immediately fall apart
> and has sort
Thomas Goirand writes:
> The last time we've had a GR on init systems, the general response was
> that we don't want to vote, and we preferred the TC to decide.
I don't think the core questions here are technical questions. I think
they're more fundamental questions of project direction and
On 10/29/19 6:16 PM, Sam Hartman wrote:
> Init System Policy
> ==
>
> last Bits mail, I talked about how I was considering whether we needed a
> GR on Init System Policy.
The last time we've had a GR on init systems, the general response was
that we don't want to vote, and we
On 10/1/19 9:24 PM, Samuel Henrique wrote:
> and the centralization
> of the discussion in a "tree like" structure are things that I miss a
> lot here.
Are you saying that you're reading -devel without the "tree like"
display of the thread? Outch! I'd strongly suggest using a better client
if
On 9/19/19 6:30 AM, Jerome BENOIT wrote:
>
>
> On 19/09/2019 00:46, Sam Hartman wrote:
>
>> Init System Diversity
>> =
>
>> So perhaps sysvinit and init scripts have had their chance and it is
>> time to move on. We could move away from init scripts as the default
>>
On 10/1/19 5:06 PM, Enrico Zini wrote:
> If I say something that 1000 people like and one person hates, the
> net visible effect in my inbox is probably one angry reply.
I very much agree with that. Which is why I don't feel comfortable when
Sam making summaries and conclusions of discussions we
Sorry about the lateness here, been busy...
On Tue, Oct 01, 2019 at 12:22:34PM -0400, Sam Hartman wrote:
> > "Sean" == Sean Whitton writes:
>
> Sean> You might separate your detailed, narrative descriptions of
> Sean> how discussions went from what you took away from the
> Sean>
Hello,
On Tue 01 Oct 2019 at 12:22PM -04, Sam Hartman wrote:
>> "Sean" == Sean Whitton writes:
>
> Sean> You might separate your detailed, narrative descriptions of
> Sean> how discussions went from what you took away from the
> Sean> discussions. You could either drop the
Hi Sam!
First of all thanks for your work you do as DPL, you put a lot of
energy, time and enthusiasm in it, and this is very visible!
On Tue, Oct 01, 2019 at 09:57:38AM -0400, Sam Hartman wrote:
> > "Holger" == Holger Levsen writes:
>
>
> Holger> So to me this is more the consensus
❦ 2 octobre 2019 05:47 +02, Jean-Philippe MENGUAL :
> An idea: establishing a time of discussion. At the end, if there is not
> consensus (as Gitlab), there is not. If there is, ensuring every DD can
> still have an opinion via GR or changes proposals in some guidelines
> (Debian Policy, etc).
Hi,
An idea: establishing a time of discussion. At the end, if there is not
consensus (as Gitlab), there is not. If there is, ensuring every DD can
still have an opinion via GR or changes proposals in some guidelines
(Debian Policy, etc). While mails are too much and so long to be
followed by
On 10/1/19 3:57 PM, Sam Hartman wrote:
> What would be more useful than this criticism is concrete advice on how
> I can shorten them while still accomplishing my goals.
after flying over your d-d-a mail again, my suggestion:
- create a blog post for each point you are discussing
-
On 10/1/19 3:57 PM, Sam Hartman wrote:
>> "Holger" == Holger Levsen writes:
>
>
> Holger> So to me this is more the consensus of those with the
> Holger> priveledge to read, process and repond to this mailinglist,
> Holger> yet there are many more people packaging software in
On 2019-10-01 16:13:03 -0400 (-0400), Sam Hartman wrote:
> A couple of people active in Gnome have suggested discourse for
> this sort of thing. It's got enough email integration that perhaps
> we would not lose people who want that interface.
>
> I t would be interesting if someone wanted to
> "Jonathan" == Jonathan Carter writes:
Jonathan> I try to follow debian-devel really closely, and mostly
Jonathan> manage to succeed, but this was probably the toughest
Jonathan> topics for me to follow, there's lots of repetition,
Jonathan> me-toos, posts that don't really
Hi Sam
On 2019/10/01 15:57, Sam Hartman wrote:
> I'd say it is a consensus of those who prioritize participating in this
> discussion enough to do so, consented to by the rest of the project.
> If we get it sufficiently wrong people in the broader community will let
> us know.
>
> Yes, because
A couple of people active in Gnome have suggested discourse for this
sort of thing.
It's got enough email integration that perhaps we would not lose people
who want that interface.
I t would be interesting if someone wanted to spend the time to pilot
that.
>
> Am I really expected to add a "me too" response every time I agree with
> what
> someone else took the time to write... making it harder for people with
> limited
> time to follow? This seems especially cruel to those that don't speak
> English
> natively, and those that rely on translation
> "Michael" == Michael Lustfield writes:
Michael> On Tue, 1 Oct 2019 14:32:10 +
Michael> Holger Levsen wrote:
>> On Tue, Oct 01, 2019 at 09:57:38AM -0400, Sam Hartman wrote:
>> > I'd say it is a consensus of those who prioritize participating
>> in this > discussion
On Tue, 1 Oct 2019 14:32:10 +
Holger Levsen wrote:
> On Tue, Oct 01, 2019 at 09:57:38AM -0400, Sam Hartman wrote:
> > I'd say it is a consensus of those who prioritize participating in this
> > discussion enough to do so, consented to by the rest of the project.
>
> I'm sorry, but I
> "Sean" == Sean Whitton writes:
Sean> You might separate your detailed, narrative descriptions of
Sean> how discussions went from what you took away from the
Sean> discussions. You could either drop the former, or put it in a
Sean> "read this if you want more details"
On Tue, Oct 01, 2019 at 02:32:10PM +, Holger Levsen wrote:
> On Tue, Oct 01, 2019 at 09:57:38AM -0400, Sam Hartman wrote:
> > I'd say it is a consensus of those who prioritize participating in this
> > discussion enough to do so, consented to by the rest of the project.
> I'm sorry, but I
On Tue, Oct 01, 2019 at 09:57:38AM -0400, Sam Hartman wrote:
> I'd say it is a consensus of those who prioritize participating in this
> discussion enough to do so, consented to by the rest of the project.
I'm sorry, but I disagree. Silence is not always consent.
--
cheers,
Holger
On Tue, Oct 01, 2019 at 07:21:20AM -0700, Sean Whitton wrote:
> May I ask whether you review your d-d-a e-mails, specifically with an
> eye to brevity, before sending them out? Given how many people read
> them, time invested in editing for brevity would be well spent.
that.
> You might
Hello Sam,
On Tue 01 Oct 2019 at 09:57AM -04, Sam Hartman wrote:
> Holger> And then, 'spreading to more places' reminds me of another
> Holger> critisism I have with your reports: they are too long. :-D
>
>
> What would be more useful than this criticism is concrete advice on how
> I
> "Holger" == Holger Levsen writes:
Holger> So to me this is more the consensus of those with the
Holger> priveledge to read, process and repond to this mailinglist,
Holger> yet there are many more people packaging software in Debian.
I'd say it is a consensus of those who
Dear Sam,
first of all, many thanks for writing these 'Bits from the DPL' mails
regularily, much appreciated!
On Wed, Sep 18, 2019 at 04:46:14PM -0400, Sam Hartman wrote:
> Git Packaging
> =
[...]
> The discussion generated enough mail that I have not yet found time to
> issue a
On 2019-09-24 07:34, Martin Steigerwald wrote:
> Dear Mo.
>
> Mo Zhou - 24.09.19, 04:58:06 CEST:
>> For desktop users, non-systemd init plus a mordern desktop environment
>> such as Plasma or Gnome would be impossible on Debian, as they depend
>> on systemd. Some other distro such as Gentoo and
Dear Mo.
Mo Zhou - 24.09.19, 04:58:06 CEST:
> For desktop users, non-systemd init plus a mordern desktop environment
> such as Plasma or Gnome would be impossible on Debian, as they depend
> on systemd. Some other distro such as Gentoo and FreeBSD have somehow
> removed the systemd dependency for
Hi,
On 2019-09-23 23:29, Sam Hartman wrote:
> Samuel> I'm not saying maintainers should spend time on maintaining
> Samuel> init files etc. but at least leave room for people who want
>
> Obviously if we had a vote the project could choose to agree with you or
> not.
FYI, two important
> "Samuel" == Samuel Thibault writes:
Samuel> Hello, Sam Hartman, le mer. 18 sept. 2019 16:46:14 -0400, a
Samuel> ecrit:
>> We could stop caring about sysvinit (which isn't quite the same
>> thing but is related). That would leave non-linux ports in an
>> unfortunate
Hello,
Sam Hartman, le mer. 18 sept. 2019 16:46:14 -0400, a ecrit:
> We could stop caring about sysvinit (which isn't quite the same thing
> but is related). That would leave non-linux ports in an unfortunate
> position. But right now there are no non-linux ports in the main
> archive. So
On Thu, Sep 19 2019, Bálint Réczey wrote:
> I would like to just remind ourselves that in WSL and Docker
> containers systemd is not running as the init system and systemd
> services can't be started easily but init.d scripts can be.
FWIW, with buster, systemd becomes possible in unprivileged
On 2019/09/19 11:18, Martin Steigerwald wrote:
> I also feel sad cause I saw the enormous efforts of Devuan and Debian
> people as well as the new Sysvinit upstream maintainer to improve the
> quality of sysvinit, startpart, insserv, runit, openrc you name them
> packages and to actually
Hi,
Sam Hartman ezt írta (időpont: 2019. szept. 18.,
Sze, 22:47):
>
>
> Dear Debian:
>
...
> Init System Diversity
> =
..
> Honestly, I'm not entirely sure how to move forward. Perhaps it's just
> that I haven't talked to someone I need to. Perhaps someone will read
> this,
Hi Sam!
I took long time to write this even on still recovering from a pace in
my life that feels too quick for me. But I intended this to be carefully
worded in order to not hurt anyone. I hope I succeeded. My invitation:
Before taking anything personal and making the choice to feel hurt
On dj., set. 19 2019, Jerome BENOIT wrote:
On 19/09/2019 00:46, Sam Hartman wrote:
Init System Diversity
=
So perhaps sysvinit and init scripts have had their chance and
it is
time to move on. We could move away from init scripts as the
default
representation. We
> "Jerome" == Jerome BENOIT writes:
Jerome> On 19/09/2019 00:46, Sam Hartman wrote:
>> Init System Diversity =
Jerome>
>> So perhaps sysvinit and init scripts have had their chance and it
>> is time to move on. We could move away from init
On 19/09/2019 00:46, Sam Hartman wrote:
> Init System Diversity
> =
> So perhaps sysvinit and init scripts have had their chance and it is
> time to move on. We could move away from init scripts as the default
> representation. We could stop caring about sysvinit
On Thu, 06 Jun 2019, Sam Hartman wrote:
> > "Bastian" == Bastian Blank writes:
>
> Bastian> Hi Sam
> Bastian> On Thu, Jun 06, 2019 at 11:57:41AM -0400, Sam Hartman wrote:
> >> However, it's a lot easier to get a foo-guest account on salsa
> >> than it is to get a foo guest
> A guest account in Debian LDAP does not get a Salsa account, at least
> not an usable one. Currently only users in the Debian group are
> allowed.Hmm - so salsa is useless at all - i don't think so. Change
your pov and see it otherwise: A guest can open a project - all members
of the Debian
> "Bastian" == Bastian Blank writes:
Bastian> Hi Sam
Bastian> On Thu, Jun 06, 2019 at 11:57:41AM -0400, Sam Hartman wrote:
>> However, it's a lot easier to get a foo-guest account on salsa
>> than it is to get a foo guest account in Debian LDAP.
Bastian> A guest account
Hi Sam
On Thu, Jun 06, 2019 at 11:57:41AM -0400, Sam Hartman wrote:
> However, it's a lot easier to get a foo-guest account on salsa than it
> is to get a foo guest account in Debian LDAP.
A guest account in Debian LDAP does not get a Salsa account, at least
not an usable one. Currently only
> "Alexander" == Alexander Wirt writes:
Alexander> On Wed, 05 Jun 2019, Adrian Bunk wrote:
I understand that is how it is today.
Disabling an account is something we clearly want to be able to do.
However, it's a lot easier to get a foo-guest account on salsa than it
is to get a foo
On Wed, 05 Jun 2019, Adrian Bunk wrote:
> On Wed, Jun 05, 2019 at 10:14:50AM -0400, Sam Hartman wrote:
> > > "Norbert" == Norbert Preining writes:
> >
> > Norbert> I would propose something else: Debian rights are defined
> > Norbert> by presence/absence of a GPG key in certain key
On Thu, 06 Jun 2019, Andreas Tille wrote:
> On Wed, Jun 05, 2019 at 10:14:50AM -0400, Sam Hartman wrote:
> > > "Norbert" == Norbert Preining writes:
> >
> > Norbert> I would propose something else: Debian rights are defined
> > Norbert> by presence/absence of a GPG key in certain
On Wed, Jun 05, 2019 at 10:14:50AM -0400, Sam Hartman wrote:
> > "Norbert" == Norbert Preining writes:
>
> Norbert> I would propose something else: Debian rights are defined
> Norbert> by presence/absence of a GPG key in certain key rings. This
> Norbert> should be completely
On Wed, Jun 05, 2019 at 10:14:50AM -0400, Sam Hartman wrote:
> > "Norbert" == Norbert Preining writes:
>
> Norbert> I would propose something else: Debian rights are defined
> Norbert> by presence/absence of a GPG key in certain key rings. This
> Norbert> should be completely
> "Norbert" == Norbert Preining writes:
Norbert> I would propose something else: Debian rights are defined
Norbert> by presence/absence of a GPG key in certain key rings. This
Norbert> should be completely independent from what one can do on
Norbert> salsa. So I propose that
Hi,
> https://lists.debian.org/msgid-search/tsl5zpyigx4@suchdamage.org
Thanks, sounds reasonable.
> I'll take this as input that we should have better transition strategies
> for salsa when a project owner's status changes.
I would propose something else: Debian rights are defined by
> "Norbert" == Norbert Preining writes:
Norbert> Hi, (please Cc, not reading d-d)
Norbert> On Sun, 02 Jun 2019, Sam Hartman wrote:
Norbert> And would you be so helpful in providing a link to that
Norbert> understanding of consensus? Only posting a link to the
Norbert>
Hi,
(please Cc, not reading d-d)
On Sun, 02 Jun 2019, Sam Hartman wrote:
> Dh as a Preferred Packaging Style
> =
>
> As promised, I started a discussion [3] on whether we wanted to prefer
> (and in some cases require) the dh sequencer from Debhelper as a package
Thanks very much for the reply!
Have you been discussing this with the gitlab people?
They seem very open to discuss with projects, e.g. see
https://gitlab.com/gitlab-org/gitlab-ce/issues/53206
I understand your points (especially agree on moving bugs between
different projects) and that there is
On Jan 01 2019, Chris Lamb wrote:
> Hi Nikolaus,
>
>> > * Followed-up on progress regarding potential new "Member Benefits"
>> >[9] and ensured that some previously-promised reports for events
>> >funded by Debian ended up appearing on Planet [10].
>> >
>> >I also provided solicited
Hi Nikolaus,
> > * Followed-up on progress regarding potential new "Member Benefits"
> >[9] and ensured that some previously-promised reports for events
> >funded by Debian ended up appearing on Planet [10].
> >
> >I also provided solicited (!) advice to a few other developers on
> >
On Dec 31 2018, Chris Lamb wrote:
> * Followed-up on progress regarding potential new "Member Benefits"
>[9] and ensured that some previously-promised reports for events
>funded by Debian ended up appearing on Planet [10].
>
>I also provided solicited (!) advice to a few other
Dear Yves-Alexis,
> > I can let you know the details privately if you wish, but I'd rather
> > not shout the parties involved from the rooftops
[…]
> No need, thanks. It was merely just to know if the reason was technical or
> not
Thank you for thinking of this. Alas, not all problems can be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2018-05-31 at 21:40 +0100, Chris Lamb wrote:
> You did not miss anything; it was not discussed in public.
Ok.
>
> I can let you know the details privately if you wish, but I'd rather
> not shout the parties involved from the rooftops just
Hi Yves-Alexis,
> > * Discussing a potential scenario where we could provide hardware
> >encryption keys for all Developers,
[…]
> would it be possible to get more details on this? If it was
> already discussed publicly I have missed it
You did not miss anything; it was not discussed in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2018-05-31 at 17:33 +0100, Chris Lamb wrote:
> * Discussing a potential scenario where we could provide hardware
>encryption keys for all Developers, partly as another benefit of being a
>DD [25] but moreoever to raise the general
unsubscribe
Den 31 dec. 2017 7:04 em skrev "Chris Lamb" :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dear fellow developers,
>
> I hope you have all had a merry Christmas and are currently enjoying
> seeing in
> the New Year.
>
> Before I head out myself for this
Sorry to disturb you but I'm a low-vision person, what is the way to
answer on HN? It seems it's no longer possible.
Best regards.
Le 01/07/2017 à 17:01, Chris Lamb a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear fellow developers,
Here's what I've been getting up to as your
On Mon, Mar 13, 2017 at 12:58 AM, jathan wrote:
> Hello. If I want to organize a Bug Squashing Party in my city, it could
> be in any month before July 2017? Thanks and regards.
You can organise a BSP at any time, but obviously before the release
is more helpful to the release :)
--
bye,
pabs
On 12/03/17 01:14, Mehdi Dogguy wrote:
> Dear fellow developers,
>
> Here is my report for January and February 2017.
>
>
> Stretch Freeze
> ==
>
> As planned, the Release Team announced the freeze of Stretch [1]. It
> is now our turn to squash bugs and help them to make the
On 12/03/17 01:14, Mehdi Dogguy wrote:
> Dear fellow developers,
>
> Here is my report for January and February 2017.
>
>
> Stretch Freeze
> ==
>
> As planned, the Release Team announced the freeze of Stretch [1]. It
> is now our turn to squash bugs and help them to make the
]] Mehdi Dogguy
> So DAMs asked to purchase Yubikey 4 tokens. They now have a common GPG key
> to make it easier to contact them confidentially (rather than have to look
> up their individual keys).
We have a sponsorship from Yubico for some more yubikeys, so we can
probably use those for the
On Mon, Jun 27, 2016 at 10:03:49PM +0200, Mehdi Dogguy wrote:
> I am sorry if it was not clear and it is indeed the last one. I thought it
> was clear enough given the context described in my email (Newmaint, Debian
> Maintainers, etc...). Besides, we will probably stop listing it in the
>
Hi,
On 27/06/2016 21:26, Iustin Pop wrote:
> On 2016-06-27 18:10:00, Mehdi Dogguy wrote:
>> - - Approved purchase of PGP hardware tokens for DAMs. (Up to 200€)
>
> Could you please tell which hardware was this? Just curious for my own
> use—still have to migrate to such a solution, so I'm
Hi,
On 27/06/2016 20:52, Jonathan Wiltshire wrote:
> On Mon, Jun 27, 2016 at 06:10:00PM +0200, Mehdi Dogguy wrote:
>> Newmaint delegation revoked
>> ===
>>
>> The Newmaint team is responsible of checking new Debian Maintainers
>> applications, and ask addition of the
On 2016-06-27 18:10:00, Mehdi Dogguy wrote:
> - - Approved purchase of PGP hardware tokens for DAMs. (Up to 200€)
Could you please tell which hardware was this? Just curious for my own
use—still have to migrate to such a solution, so I'm wondering what are
others use, especially in/related to
On Mon, Jun 27, 2016 at 06:10:00PM +0200, Mehdi Dogguy wrote:
> Newmaint delegation revoked
> ===
>
> The Newmaint team is responsible of checking new Debian Maintainers
> applications, and ask addition of the applicants keys to the Debian
> Maintainers keyring.
Could you
Hi,
Santiago Vila:
To me, it's sad to see that we seem to be officially endorsing Bitcoin
without any debate at all. If we accept Bitcoin, we should probably
accept competing so-called-cryptocurrencies as well. Should Debian
favour one cryptocurrency over the others?
No, but it's the most
On Sun, Aug 24, 2014 at 09:28:11AM -0700, Lucas Nussbaum wrote:
Donations in Bitcoin
Crytocurrencies have been the subject of a lot of attention recently.
Debian received its first Bitcoin donation, which was handled in a ad-hoc
manner as we don't have any
Le Wed, Aug 27, 2014 at 02:08:03AM +0200, Santiago Vila a écrit :
I don't think Debian should accept donations in Bitcoin, as such thing
could be considered as an endorsement of Bitcoin. The EFF has a very
well written rationale why accepting Bitcoins is not necessarily a
good idea, see
Hi,
Santiago Vila wrote (27 Aug 2014 00:08:03 GMT) :
The EFF has a very well written rationale why accepting Bitcoins is
not necessarily a good idea, see point 3 here:
https://www.eff.org/deeplinks/2011/06/eff-and-bitcoin
It seems useful to note that, since then, they've decided to accept
On Wed, Aug 27, 2014 at 09:40:15AM +0900, Charles Plessy wrote:
The EFF changed its mind two years later.
https://www.eff.org/deeplinks/2013/05/eff-will-accept-bitcoins-support-digital-liberty
Ok, from the above link:
You can now give Bitcoins to EFF in the same way that you can give
On Sun, Aug 24, 2014 at 09:28:11AM -0700, Lucas Nussbaum wrote:
Debian logo now registered as a trademark
=
Thanks to the work of the Debian trademark team and the Software Freedom
Law Center (SFLC), the Debian logo is now officially registered as a
On Mon, Aug 25, 2014 at 2:13 PM, Steve Langasek wrote:
Does this list of expenses mean that you now have a good overview of
Debian's cash flow? In April, I understood that this was a major
outstanding problem. I'm happy to see that we are spending Debian money on
useful sprints and events;
On 25/08/14 at 14:13 -0700, Steve Langasek wrote:
On Sun, Aug 24, 2014 at 09:28:11AM -0700, Lucas Nussbaum wrote:
Debian logo now registered as a trademark
=
Thanks to the work of the Debian trademark team and the Software Freedom
Law Center
1 - 100 of 180 matches
Mail list logo