But I have applied any suggested patches up to now. Not being able to pay much attention to it right know, doesn't mean that I am abandoning it. Maybe later I will still be able to work on it.
Sorry, but I think that right now it is not right to give right access to anybody. You can still manage it with subversion locally and submit patches time after time. It is not a matter of mistrust, but I think that it is not neccessary. Regards, Dashamir --- Simos Xenitellis <[EMAIL PROTECTED]> wrote: > O/H Torsten Schlabach ÎγÏαÏε: > > Dashamir! > > > > > When I was using DocBookWiki to maintain some > > > documents, I had to fix any bug that would not > > > allow me to continue using it. > > > > > > But now that I am not using it anymore, it is > > > like a pain to debug and fix it for the others. > > > So, don't expect me to fix everything, but try > > > to get your hands dirty instead. > > > > I do, as you can see. I wanted to make sure I > don't just report the > > bug but fix it. But its nice if you find the time > to integrate patches > > that get submitted. > > > > You still have the option to give some more people > who you trust to > > take the project further write access to the SVN > if you want to. They > > could then take care of bugfixing. It would still > be your project. > > > > I really like DocBookWiki and it would be a pitty > if it died. But it > > will, if nobody maintains it and keeps fixing it. > Indeed. > Dashamir, if you could please add more developers to > the doc-book > project, it would be great. > My SourceForge username is "simos". > > As it would be work in progress, I would like to > make my changes in a > different branch. Therefore, you would have to > create a branch (is that > SVN lingo?). > > Cheers, > Simos > > > > Regards, > > Torsten > > > > > > Dashamir Hoxha schrieb: > >> When I was using DocBookWiki to maintain some > >> documents, I had to fix any bug that would not > >> allow me to continue using it. > >> > >> But now that I am not using it anymore, it is > >> like a pain to debug and fix it for the others. > >> So, don't expect me to fix everything, but try > >> to get your hands dirty instead. > >> > >> Thank you for your understanding, > >> Dashamir > >> > >> --- Torsten Schlabach <[EMAIL PROTECTED]> wrote: > >> > >> > >>> Hi! > >>> > >>> I need to continue the discussion about creating > a > >>> new book again. > >>> > >>> Dashamir wrote in an earlier email: > >>> > >>> > 1 - After importing a new book you should also > >>> > add an entry for it in > >>> > 'content/SVN/book_list.sh' > >>> > (maybe this should be done automatically by > >>> > the system, I am not sure about it) > >>> > >>> Ok, I have done that. > >>> > >>> > 2 - After making changes to the book, you > should > >>> > approve and commit them. This would > >>> synchronize > >>> > the workspace and the public copy, and the > >>> > changes would appear in the imploded docs, > >>> > downloads etc. (because the public copy > >>> > is imploded by default). > >>> > >>> I don't find a way of doing this. > >>> > >>> I cannot make changes to my new book because I > >>> cannot edit anything. > >>> > >>> The error message still is: > >>> > >>> WebApp Error: Parser::parse_file(): file > >>> 'content/books/cache/vhcs2ref/en/./content.html' > >>> does not exist. WebApp Error: > Parser::parse_file(): file > >>> > 'content/books/cache/vhcs2ref/en/./subnodes.html' > >>> does not exist. > >>> > >>> Because I cannot edit, I cannot approve. The > button > >>> is grayed out. > >>> > >>> I also tried to just run make-all-downloads.sh, > but > >>> this fails as well: > >>> > >>> Commiting 'my_docs/linux_server_admin_sq_AL.xml' > >>> cp: cannot stat `../books/xml/vhcs2ref/en/*': No > >>> such file or directory > >>> Imploding 'vhcs2ref/en' to > >>> ../implode/tmp/vhcs2ref.xml > >>> warning: failed to load external entity > >>> "tmp/vhcs2ref/index.xml" > >>> unable to parse tmp/vhcs2ref/index.xml > >>> Commiting 'my_docs/vhcs2ref_en.xml' > >>> svn: Commit failed (details follow): > >>> svn: > >> > >> > '/var/www/virtual/docbook.rent-a-wiki.com/book-cvs-20060329/content/SVN/my_docs/vhcs2ref_en.xml' > > >> > >> > >>> is not under version control > >>> At revision 1. > >>> > >>> How can I add my new book to version control? > >>> > >>> And which version control would that be? The one > >>> which keeps the imploded docbook XML files or > the one which keeps > >>> the exploded chunk XML files? > >>> > >>> Regards, > >>> Torsten > > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support > web services, security? > Get stuff done quickly with pre-integrated > technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 > based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Doc-book-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/doc-book-users > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Doc-book-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/doc-book-users
