From: Stefan K. <Ste...@ga...> - 2003-06-04 14:07:44
|
@luca: [...] We are going to use postwrap, and guess what, we'll need to convert = it to Oracle. How do we usually proceed with modules not developed by the envo community?= [...] This is a fundamental problem. Because if we want to distribute 3rd-party-m= odules including some changes for eNvo, it is not easy to hold them = up-to-date, if there are some updates and fixes published by module-owner. = We have to implement them manually into the modified files. Or we use = these modules as is (based on xxx, version 123) and develop it in future = under eNvo without the support of the owner. [...] Do we try to get the approval of the author? can we ask him to = accept and include the modifiers on the source so that it colud be = preserved for future releases and bug fix? [...] This would be the better way. But it is neccessary to share all work. This = is a two-way development: Owner -> eNvo, eNvo -> owner Possible that not all changes would be shared. [...] Can we try to pull these developers in the envo community? [...] And this would be the best way. But not every developer want to work only = for one community. They have some different interests, ideas, etc. to = distribute their work. But if he want to develop his modules also for eNvo, it would be possible, = that he can update his changes on our CVS. So we can share all automaticall= y. Try it.... ;) WindMeUp |