Hello everybody. I write this to make a request, I just recently joined the mailing list, so I don't even know if this is the right list I'm writing to, but anyway... The company I'm working for (mediaphil digital media, Germany) is interested in contributing quite some time to the Jyve project as we we're currently working on two projects which will actually incorporate a Jyve-based Knowledge Base System. Adding the code we'll develop while doing so is probably the least we can do for the project. I think that it helps any open source project if some people who are working on it are getting paid for all the stuff they do. Now let me describe the changes we want to commit: - We will localize the whole project to German. In the TODO it is stated that localization features (changing the look and feel) have been postponed to version 2. Actually, we would like to possibly change that plan and implement localization features over the next few months. As we will need the full German version until the middle of february we will first of all just hack all of the English text in the different classes and adjust them to our layout and then switch to a truly localized version afterwards, which will also allow us to stay up to date with the rest of the codebase. The first localization process will take us about 5 hours and will be done on the then most up-to-date cvs codebase. We will submit it as an unsupported package when it's done. The implementation of real localization features will at the earliest take place after the CeBit 2000 (Computer Exhibition/Trade show in Hannover, Germany in the middle of February). - We are planning to enhance the search classes to support most of the standard boolean expressions. This will probably happen over the next few weeks and will consist of a SQL-Statement creator and Search expression parser. - We are planning to add feedback capability. This will allow users to submit some feedback i.e. "Has this article helped you to solve your problems ? Yes, No, Perhaps". This information will be stored in the database and will probably include some Classes to make this feedback available to authors/engineers in a percentage based display, probably including the ability to render these statistics in a graphical way, too. We are currently thinking about ways to implement this outside of the current codebase so one can plug this feature in and out of the existing systems at will without being tied to some old codebase or proprietary code which generates the graphics. The code described will be made available to the community under the current license. All we would like to see is cooperation of the current developer group i.e. suggestions, critical statements and so on. As I said, I joined this list today and don't know about the currently planned feature changes in the near future or plans that have already been made for version 2, so I really would like to hear from you, perhaps filling me in on the details. Btw, I am the designated project manager for this project, so don't hesitate to contact me. Best regards, Jonas Maurus Project manager [!] mediaphil digital media Munich, Germany -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
