robert engels wrote: > You already have a CVS repository. To create a branch is 1 command.
I know. So it is to create a tag, yet it still happens that I forget to tag the CVS when I make a release. > It does allow others though to keep other versions alive more easily. OK, if I'm ignorant, then please explain the difference. If there is a 1.4.x branch on SourceForge, but we don't keep it up to date; like for instance the steve-appling branch: http://itext.cvs.sourceforge.net/itext/src/com/lowagie/text/pdf/PdfWriter.java?view=log&pathrev=steve-appling How does this help you? You can't commit to CVS @ SF. You can only create your own CVS with iText based on that branch. However: you don't need a branch for that; you could get a tagged version, or a version at some point in time... > You are are too > egotistical to allow the input/work of anyone else - even when they > clearly know more about the subject than yourselves. It's not a matter of being egotistical. We have been granting and revoking CVS access to different people in the past. Of course, those people have motivated why they should be added; calling us names isn't a good way to get access to the CVS ;-) > It is clear you have little in terms > of professional software development education or experience. I've never hidden the fact that I'm not a programmer; I'm a civil engineer in architecture (buildings not software). I do have a lot of experience though ;-) > You have let the success of iText go to your head, Success? No, when I'm grumpy, it's because of the price of that what you call success: being bugged by people day and night. Having to clean up shiploads of SPAM from all my sites every day. If that's success, I'm glad to share it with you ;-) > when it is clearly not > a success due to the high quality of the code/project, Hey, I never claimed the quality of the code was perfect. Some part look as if they're written in C. But the design isn't bad, at least not compared to some other tools. > but rather > that it fills a need with a decent product at a FREE price point. Yep. > Maybe if you got down of your high-horse and were not so afraid of > allowing other people to contribute, iText would be even better than > it is today, and you would have to do less work (but maybe that is > what this is all about, some sort of veiled job security). But... but... we have a complete list of people who have sent us contributions: http://itext.ugent.be/library/acknowledgements.php You're even on it: http://itext.ugent.be/library/acknowledgements.php?id=148 > You would benefit greatly from watching the Lucene project. You will > see how the founder still "provides" direction, but also how the > project has grown and developed without his input, due to the > multitude of people that now contribute. You should review the code > quality. You should review the release process. It might give you > many helpful ideas. I've just reviewed a book proposal by one of the Lucene guys. I gave him a very good review. I am very willing to learn, but there are only 24 hours in one day. And we don't have a company like Apache behind us. We are doing the best we can. > Best of luck to you. Well, at least you got to vent your frustration. In my experience that helps. As for the content of your mail: I'm sorry, but I have no idea what it's about. I know you asked something about a 1.4.x branch, but I don't understand the whole litany about not accepting contributions. best regards, Bruno ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://itext.ugent.be/itext-in-action/
