Ulrich Mayring wrote:
thanks, but that won't be neccessary. We know there's broken links, it's just that they need fixing :DBerin Loritsch wrote:The site is up and running at: http://avalon.apache.org/ If Apache has a "bad link checker", then we need to check with infrastructure to be automatically nagged when there is a bad link on the site.I can add something in my crontab meanwhile, if you like. Auto-Nags for broken links are a bit troublesome in my experience, if run daily. On a sufficiently large website there are always errors and for good reasons, too. A weekly run should be ok, though.
The usual idea with OSS contributions is not that we send materials to someone to work on, but rather that those who are willing to contribute get the things they want to work on from CVS, do their thing, generate a diff using 'cvs diff -u', and then send these differences in by putting them in bugzilla (or sending them to the mailing list).If you would rather work with CVS and its diff functionality, then the appropriate module is "jakarta-avalon-site".Not sure what you mean here?
The biggest advantage of this is that it reduces the load on the developers who need to actually check in the changes. So basically, if you want to do proofreading do a
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic login
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic checkout \
jakarta-avalon/proposal \
jakarta-avalon-site/src \
jakarta-avalon-phoenix/src/documentation \
jakarta-avalon-logkit/src/xdocs \
jakarta-avalon-phoenix/src/documentation \
jakarta-avalon-cornerstone/src/xdocs \
jakarta-avalon-excalibur \
avalon-sandbox
(warning: takes some time :D)
work on all the *.xml files you just checked out, then when done you do `cvs diff -u` for the modules you modified, which generates a file you put into bugzilla as an attachment. The developer applying your patch can then just do
patch -p0 < ulrichs.patch
cvs commit -R 'apply ulrichs patch'
in other words, you help make life easy that way :D
On the subject of review, the developer who will apply your patch is the one who will be doing the review. It's much easier if you just send in contributions into bugzilla or to the -dev mailing list; that way the developer who happens to have some free time can apply your patch.
that clear things up?
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
