I'm sorry, Adam. I don't get it. What's TCL? What can I or infrastructure do to help? Should we come up with proposed plan of actionf or installing gump on aapache machine so that we can start debating it *before* the machine arrives?
TLC = Tender Love and Care. ;-)
Basically the "workflow" of using Gump as a standalone set of scripts for debugging a single module/project. The GUI would be good for this, the scripts (with an improved commandline) would be good. They just need a little attention to detail.
BTW: Since moof doesn't appear to be for general public usage, I wonder if we ought maintain an instance purely for committer debugging. Sure we can get to a GUI, or a webapp [and maybe we should] but the quickest way to ease folks pain would be complete the scripts & allow a public install. I'm ambivalent about the best longer term choice...
I say: let's KISS.
Moof is an empty box for committers to play with over osx-land (mostly,make sure that httpd compiles, even if almost all httpd developers run macosx anyway).
as for wrapping scripts, I would try to avoid them entirely to keep maximum OS portability (I'm thinking unix/windows)
As for love and care, boy, I'm installing our new beefy server as we speak, so expect tons of polishing (and questions) from my side and I'm going to focus on gumpy.
I plan to make all DSpace, Haystack and Simile build on that box. Is it currently possible to be part of the gump servers and build *more stuff* than the ASF machines?
we should try to think at how to make the gump federation a little more consistent... allowing people to donate their resources to the mix.... and keeping in mind multi-platform ability for non-java projects.
-- Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
