On 13.10.2011 21:11, Stefan Steiniger wrote: > > a) Well.. for the licences.. > don't know how it works with being readable? > >> would look like that >> http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/core/trunk/etc/readme.txt?view=markup >> >> not elegant, but at least up to date > I was more thinking how you would include it in the wiki? just as a link? > in this case - would rather think we write the basics (for OJ core) and > then, yes for the details (for Plus?) we link to the file... or so. >
but even only the basics would be outdated at some point and i really do not see someone taking the time to update this periodically. how about setting up a cronjob that periodically downloads readme.txt from svn to our webspace. this way we would have a readable text file for linking and only one source to be maintained? ..ede ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
