On Thu, Sep 4, 2008 at 9:43 AM, David Cantrell <[EMAIL PROTECTED]> wrote: > On Thu, Sep 04, 2008 at 07:13:44AM -0400, David Golden wrote: >> On Thu, Sep 4, 2008 at 4:19 AM, Eric Wilhelm <[EMAIL PROTECTED]> wrote: >> > What are the issues in that time? Code or non-code? >> mostly $job, @family, %life stuff > > Is there anyone involved who would be able to put more time in with a > TPF grant? eg, someone who works as a contractor and so doesn't have a > long-term job to keep?
Let me add that I think the first major hurdle is finding the right balance in the design. It would be easy to hack out something that fixes the immediate pain points but winds up just as brittle. At the same time, we don't want to spend too long designing the "perfect" system that can be all things to all people. If that first part winds up sufficiently elegant, than I don't think the infrastructure code is that hard to write. The second major hurdle will be changing all the various tools and getting testers to switch over. The third major hurdle will be the migration plan -- how to cut over to the new system, whether to port over old reports from NNTP, and what to do about stragglers that still send reports the old way. So I don't think the challenge is really a TPF-supported coder -- I think we need a small group of knowledgeable people to set aside time to hammer out a design and pressure-test it. -- David
