[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bits from the DPL (May 2019)



>>>>> "Bastian" == Bastian Blank <waldi@debian.org> 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 in Debian LDAP does not get a Salsa
    Bastian> account, at least not an usable one.  Currently only users
    Bastian> in the Debian group are allowed.

No, but my understanding is that basically anyone on the internet can go
sign up for foo-guest at salsa.

    >> There are transitions like someone retiring from the project
    >> where we actually would be delighted if they continued to use
    >> salsa in some capacity.

    Bastian> The largest technical problem with that is providing the
    Bastian> user with a valid e-mail address.  Apart from that we need
    Bastian> DSA to properly define states in LDAP.

OK, that's useful input.
I do feel we're talking past each other here though.

Norbert and some other folks said they wanted salsa to behave
differently.

Alex jumped in and said "salsa doesn't work that way."
Sure, we all know that.
And yet, salsa and really all of Debian can change if we want them to
and the right we are willing to do the work.

I tried to explain why some people might want a change and said I'd
bring that up as one of the points to consider.

Now you're talking about why the change would be hard.
I do think understanding the cost of a change is important, but
sometimes I also think it's helpful not to jump right to the technical
details.  Sometimes I think it might help to spend a bit of time asking
in the abstract what we want before getting micro-focused on how we'd
get it if we did.

Obviously you can't entirely separate these things.  Things cost
people's time, money, and various other things (like risk of security
compromise).
But I think sometimes it harms a discussion if you jump right to the
implementation challenges.

--Sam


Reply to: