From: Anjo K. <anj...@t-...> - 2003-10-27 08:25:56
|
Hi Max, Am Freitag, 24.10.03 um 07:16 Uhr schrieb Max Muller: > Hi David, > I have been following subversion with keen interest, I live in cvs > day in day out. My main concern with subversion is that it hasn't hit > 1.0 yet. I personally think that the subversion crew is just being a > bit too cautious. My biggest fear in moving the repository from > sourceforge is that when something goes wrong (and it will) we will > have to deal with it. My vote would be to wait until subversion hits > 1.0 and then see if sourceforge starts supporting it, if not or the > subversion guys can't hit 1.0 within the next three months then let's > revisit the issue. Just my 0.02. I'd guess that they definitely wont hit 1.0 in this time frame, given the slow version number progression in the past. I could live with the 3-month wait, but I'd definitely do it before the next real update to Wonder, when (if) we actually move stuff into finer grained packages. Cheers, Anjo > Regards, > Max > > On Thursday, October 16, 2003, at 12:07 PM, David Teran wrote: > >> Hi Jan, >> >> there is a lot of javadoc but there is no tutorial. One could write >> -a lot- of documentation about project wonder but it appears no one >> has the time for that. Moving from CVS to subversion is done 'in a >> minute' if one know to use cvs from the command line. All you need to >> know is "cvs checkout", "cvs commit" "cvs update". With subversion >> you get some easier commands for move, rename and copy. Thats all the >> question was about. >> >> On Oct 16, 2003, at 8:53 PM, Jan Willem Luiten wrote: >> >>> Yes indeed, there are precompiled frameworks but where's the >>> documentation and where are usable example projects that a normal >>> user would expect? You're completely disregarding the fact that you, >>> Anjo and others probably have been working on this project for a >>> long time, whereas others simply want to incorporate the >>> functionality the project offers. After all, that's the goal of a >>> open source project, isn't it? A lot of the stuff that's part of the >>> project is obvious to you and some others. Not so for the "normal" >>> user that installs the precompiled frameworks. Allow me some small >>> examples. >>> >>> There's a sample app called BugTracker. This app requires some >>> content in various databasetables. As far as I can see, there's no >>> documentation on how to set this up using a databaseengine other >>> than MySQL. To worsen things further, there's no documentation on >>> what information must be stored in the database in order to get >>> BugTracker to work, let alone MySQL based batchfiles to set up this >>> information. The "normal" user you refer to, will not be able to get >>> this working without having a look in the sources. A few lines of >>> documentation would work Wonders and would get project Wonder to >>> work. >>> >>> Another example is the ERXEOFAppender in the ERExtension framework >>> and ERCLogentry in the ERCoreBusiness framework. While this is good >>> and important functionality, the ERCLogEntry class does not >>> implement the ERCLogEntryInterface. Also, there is no class derived >>> from ERCLogEntry implementing this interface, nor is there any >>> documentation that says "write your own class deriving from >>> ERCLogEntry and implementing ERCLogEntryInterface". In these matters >>> there's also no documentation to be found on what properties to use >>> in order to configure the functionality. Again, the "normal" user >>> must resort to having a peek into the sources to get things working. >>> >>> To wrap things up, your "normal" user will, at this point in time >>> not be able to get things to work without reading through the >>> sources. >>> >> Yes, i think every knows this but apparently no one has time to fix >> this. If you want and have the time maybe you can write some >> documentation and fix up things, too. It seems that you have spend >> some time with project wonder or maybe you are able to fix the things >> you mentioned below. >> >>>> >>>> Besides this you are right, some things should be fixed in the >>>> current source from the cvs. But this has nothing to do with the >>>> question 'switch to subversion as scm tool or not'. >>>> >>> Pehaps not directly.You might be right in the assumption that >>> spending time on subversion will pay-off handsomely very fast. On >>> the other hand, your "normal" user does ot benefit directly, as he >>> would from better documentation and working sample programs. >>> >> >> My only question was and is: anyone else interested in moving to >> subversion? Its great, fast and 100times better than cvs. This >> question is more or less only interesting for people with cvs-commit >> rights. >> >> regards David >> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: SF.net Giveback Program. >> SourceForge.net hosts over 70,000 Open Source Projects. >> See the people who have HELPED US provide better services: >> Click here: http://sourceforge.net/supporters.php >> _______________________________________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc > > > > ------------------------------------------------------- > This SF.net email is sponsored by: The SF.net Donation Program. > Do you like what SourceForge.net is doing for the Open > Source Community? Make a contribution, and help us add new > features and functionality. Click here: http://sourceforge.net/donate/ > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc > > |