High Performance SSH/SCP - HPN-SSH

Michael Stahnke mastahnke at gmail.com
Thu Jul 12 19:10:19 UTC 2007


On 7/12/07, Jeff Spaleta <jspaleta at gmail.com> wrote:
> On 7/12/07, Rex Dieter <rdieter at math.unl.edu> wrote:
> > Diverging from upstream is a wee-bit against fedora's objectives/goals, but
> > ultimately, it is the pkg maintainer's call to make.
>
>
> When upstream is working actively with downstream contributors, this
> policy works well.
> If upstream blows off downstream contributors who are trying to play
> ball (and there isn't some sort of weird personality conflict
> nastiness) the policy can feel burdensome because its re-enforcing a
> broken process instead of re-enforcing a healthy innovation process.
>
> I can't judge the problem here, but if this work has been going on in
> parallel for 3+ years, something in the upstream communication is
> broken. The question is, is this a fixable or a forkable situation?
> Does Fedora has as a community have any leverage with upstream openssh
> (via an active fedora contributor who conributes to upstream perhaps?)
> to put this functionality/patch firmly onto the roadmap for upstream
> adoption?

You might want to post to comp.security.ssh, Darren Tucker (one of the
Upstream devs from OpenSSH) often responds quickly and politely.

stahnma


>
> -jef
>
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>




More information about the devel mailing list