The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

dpkg/dselect changes needed

Ian Jackson,

This message is copied to debian-private.  I'm writing in response to
the recent discussions about dpkg/dselect/deb-make . In response to
them, I again suggested on debian-private that we switch to RPM. You'll
be happy to know that the maintainers were as adamant on that subject as
last time - they still want to use dpkg. Unfortunately, there have been
some long-standing problems with dpkg/dselect that we can no longer
ignore, and changes are necessary. I've solicited developer opinion on
what changes should happen, and I've made some decisions using that input.

1. Discussion:
Dselect ease-of-use issues have been a problem for a year and there
has been very little improvement. None of the people who have proposed
to work on category-selection tools or a simpler interface to dselect
have been able to get anything done. A simpler interface has been on your
to-do list for at least a year.

Decision:
If we are to continue to support dpkg/dselect, providing a simpler user
interface must be an overriding priority, and work on things like
deb-make should be on the back-burner until that is done. We need to
have a schedule for dselect improvements, some assurance that people
are actually working on it, and regular progress reports.

2. Discussion:
There's been little movement on dpkg/dselect issues in the past year
except for work that you have explicitly not condoned. Part of this is
because you've been busy, but you really can't expect to suddenly find
tons of time to work on Debian now. I think the project's become too
big for one person, at least if we want to see any significant changes
in dpkg and dselect.

Decision: Dpkg, dselect, and deb-make (or deb-make's replacement)
should be developed by an organized a team of people, not just one.
It's logical for you to lead the dpkg/dselect team, _except_ for one
problem - you're extremely undiplomatic, and people have a difficult
time working for you because of that. For that reason, you might want
to consider making someone else the team leader for dpkg/dselect, while
you retain the role of architect.

What I'd like to see is some _movement_ - a dpkg/dselect group
organized, work being done _by_other_people_ with your cooperation, and
results getting to the user. It's doubly clear now the developers don't
want to abandon dpkg/dselect. However, if I don't see much movement I
think I might eventually have to intervene and put someone else in charge
of the package system.

	Thanks

	Bruce
--
Bruce Perens K6BP   Bruce@Pixar.com   510-215-3502
Finger bruce@master.Debian.org for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6  1F 89 6A 76 95 24 87 B3 


--
Please respect the confidentiality of material on the debian-private list.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com