>>>>> "Bastian" == Bastian Blank <waldi@debian.org> writes:
Bastian> Please describe the design changes you added to address our
Bastian> concerns. The risk assessment still lists things we
Bastian> described as no-go.
Bastian> Sorry, but I don't see how we can go forward, while you
Bastian> seem to be either unable to understand what we want to tell
Bastian> you or just decided to ignore it. I don't think it makes
Bastian> sense to continue this discussion without a mediator.
I do think it would be valuable to confirm whether we're at an impasse.
It sounds like Ian may think that resolving your concerns would be a
no-go and that you think that his design is a no-go.
Confirming whether that's true would actually be valuable. I think the
ball is probably in Ian's court on that issue.
I also think it would be very interesting to get Joerg's personal
opinion on designs in this space because it sounds like he's thought
about it for a while.
I'd really like to find ways to get more experience with tag2upload-like
things.
I've proposed my ideas for running experiments with the technology in
limited fassions to Ian.
Sadly none of my ideas were all that helpful so far.
Also, if Ansgar is going to implement his solution it would be valuable
to get experience with that. One of the factors we as a project will
consider is whether other implementations emerge or whether Ian is the
only one who will choose to implement in this space.
Ultimately, if we are at an impasse, and we've reached the point where
it's time to make a decision, I do think there is a way forward. We can
delegate a specific decision (probably something like deciding an
initial policy for archive integrity) to a group of developers. We'd
want to include members of ftpmaster, people who want something like
tag2upload, and some respected neutral parties to balance things out.
Yes, such a delegation would have power that overlapped with ftpmaster.
That's clearly constitutionally fine, but I also think in a limited
circumstance like a specific decision it is both appropriate and a
reasonable way to break a logjam.
Right now, I think it's too early to do something like that.
Attachment:
signature.asc
Description: PGP signature