open source terminal and scanning

[Fairlight]

On Mon, Oct 25, 2010 at 05:54:56PM -0400, after drawing runes in goat's blood,
Brian K. White cast forth these immortal, mystical words:
> 
> Also I put the source into a gitweb but I haven't really figured out git 
> or gitweb. I managed to create a git repo out of the source archive, and 
> get it publicly browseable via gitweb, then managed to get the url to be 
> nicer via vhost setup on the host machine, but in the process broke the 
> ability of gitweb to execute gzip, so the download snapshot button 
> doesn't work (you get a zero byte tar.gz and error_log on the host shows 
> permission denied executing /bin/gzip)

Personally, I think SVN is a smarter move.  It's five years more mature
than Git, and it's far more widely used, with variants like TortoiseSVN for
Windows, etc.

> Also, since I would wish this to become a more community effort I am 
> thinking of changing the name from Aljex to something generic like open 
> vertical terminal or similar. The idea is, the app is meant for use in a 

How about naming it Spackle?  Fits with the PuTTY theme, and it does fill
in some of the functional holes identified in the original.  Could also
call it "double-glaze" and use dg:// for your URI.  Just some thoughts...

> If anyone knows anything about git and wants to help make this work and 
> have commit access to improve the code let me know.

If you were using SVN, I could have you set up in an hour or two, both
regular SVN port and Apache WebDAV access.  It's been about ten months
since I last set up SVN from scratch, so that's why it'd take a bit longer
than one might expect...that, and SVN isn't known for compiling terribly
quickly in the first place--it's pretty big.

I know nothing at all about using Git.  I can't speak to Git.  If you're
married to Git, luck with that. :)

I imagine no matter what CMS you use, you're going to need to manage
accounts to which you give write permission to commit changes back, besides
a generic access to read the project.  So if you do this, be aware you're
going to likely be acting as an account manager for the project, and that
it's not going to run itself.  You can automate sign-up and such with a
little CGI, but I'd advise against it for a project like this.  Don't
anticipate it being fire-and-forget, so make sure you're committed to doing
this on an ongoing basis; even if the management is minimal, there will
likely still be -some- ongoing management.

mark->
-- 
Audio panton, cogito singularis.