Re: [RFC] Linux Kernel Subversion Howto

From: Jon Smirl (jonsmirl_at_gmail.com)
Date: 02/11/05

  • Next message: Larry McVoy: "Re: [RFC] Linux Kernel Subversion Howto" 
    Date:	Fri, 11 Feb 2005 11:13:23 -0500
To: Alexandre Oliva <aoliva@redhat.com>

    On Fri, 11 Feb 2005 07:39:47 -0800 (PST), Alexandre Oliva
    <aoliva@redhat.com> wrote:
    > The bit I don't understand is that you've claimed you'd be willing to
    > implement the code needed to export the additional information that
    > Roman, myself and probably many others would like to have, if someone
    > would pay for that, but you're not willing to grant him access to this
    > information such that he can write the code himself. How come you
    > wouldn't welcome a BK-export piece of software that you could use
    > yourself to create and maintain the CVS tree, without having to
    > develop and maintain the software, and insist on developing such
    > software yourself, but only if someone else pays for it?

    Think about it from Larry's side for a minute. BK is a proprietary
    piece of software, it is not open source. That means that anyone who
    works on it needs to be an employee or contractor of Bitmover and have
    signed all of the appropriate non-disclosure and non-compete
    documents. These documents exist at all proprietary software
    companies, they are not specific to Bitmover. None of you guys are
    willing to sign those documents.

    It's not Larry choosing not to have you do the work, you are self
    selecting not to do it because you won't sign the contracts. Larry
    also has to be reasonably confident that if you do sign you won't
    violate them.

    The conclusion is that someone else who is willing to sign the
    documents has to do the work. That person needs to be hired and paid.
    It is unreasonable to ask Larry to add features like you want on his
    own dime.

    There is a solution on the table:
    1) Written proposal describing in detail the commands you want added to bk
    2) Submit it for a quote.
    3) Raise the money
    4) Negotiate for exact delivery dates.

    Since no one has bothered to put together a real proposal, I can only
    conclude that you are more interested in writing email complaints than
    actually achieving a solution. 

    -- 
Jon Smirl
jonsmirl@gmail.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Larry McVoy: "Re: [RFC] Linux Kernel Subversion Howto"

    Relevant Pages

    • Re: Scaling noise
      ... Larry was possibly referring to IRIX scaling to 1024 CPUs, ... It appears that SGI is working to scale the Altix to 128 CPUs on Linux. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Kernel SCM saga..
      ... >bkcvs or bkweb and it's the most crucial information to make the bk data ... Larry was previously very clear about this that he ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: BK kernel workflow
      ... >> that BK already gives you documented ways to interoperate, ... and server using the documented interfaces that BK has. ... So Larry claims that he's ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: x86, ARM, PARISC, PPC, MIPS and Sparc folks please run this
      ... >> I mean in the same group of threads with the same struct mm, ... > Larry means that it's perfectly normal for libc to map the same file ... Practical tests indicate that the vast majority of applications do not ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)