Hi Eskil, thanks for your informations! I think, my reply was a little bit missleading ;-). We already know about Gitorious, and I think I was the second who cloned the repository (nevertheless I did not contribute til now, because of lack of time). The questions of Klemens lead to the problem how we should deal with an external binding like the binding for the property browser.
The property browser is not part of the Qt release right now, the binding depends on a specific version of the property browser code. So the questions are: * where should we publish a binding for something external to Qt (and therefore to QtJambi), I guess you would not merge it in the QtJambi tree, if it is not part of the original Qt-Release * should we publish original C++ code together with the binding, or should we reference a specific version of the C++-Code somewhere (the repository where the C++ Property Browser solution is maintained) What do you think? Thanks and kind regards Alex Eskil Abrahamsen Blomfeldt schrieb: > Alexander Vukovic wrote: > >> Where is the QTJambi community? Does anyone know, where we could share >> this hard piece of work with the world? >> >> > > Hi, Alexander! > > Currently, the Qt Jambi project is hosted on Gitorious: > > http://qt.gitorious.org/qt-jambi > > The master branch is owned by Qt Software as long as there are still > official releases. To get a change into Qt Jambi in that period, you can > clone the repository and request a merge, which will then be reviewed by > us and either committed to the master branch or rejected with an > explanation of why and what could potentially be changed to have it > approved. > > Related projects could be hosted in Gitorious if you wish, or anywhere > else you choose, as long as they do not contain changes that need to be > merged into Qt Jambi during the official maintenance period. > > When Qt Jambi reaches its official end-of-life, we hope someone else is > willing to take over control of the master branch, either in Gitorious > or in some other code hosting facility. They will then take over > responsibility of handling the merge requests. > > There is a wiki in Gitorious which is editable by anyone, and which some > people have started using to share their experiences with Qt Jambi. I > also plan to update this wiki with information gathered in the years of > development of Qt Jambi which may be helpful to future maintainers. > > We will also keep this mailing list going to have an easy way of > communicating within the community. If you guys decide to set up a > separate forum or something, we will definitely consider logging in > there to see what is going on as well. We welcome any efforts to get a > real community started around Qt Jambi. > > However, until the final official patch release, we will have to keep > the release branch of Qt Jambi in Gitorious and use the system for code > contributions available there, since we need this system for legal reasons. > > -- Eskil > > > _______________________________________________ > Qt-jambi-interest mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest > > -- > SEQIS Spam & Virus Agent: Message ok > > -- SEQIS Spam & Virus Agent: Message ok _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
