On Sun, 13 Sep 2009 21:03:58 +0200 "Carlos R. Mafra" <[email protected]> wrote:
> On Sun 13.Sep'09 at 19:25:30 +0200, Daniel Isenmann wrote: > > Hi, > > > > I'm the Arch Linux package maintainer of WindowMaker. I have sent > > the attached eMail to the developer-mailinglist of Arch Linux to > > discuss a switch of the official package to the new git repository > > of Carlos R. Mafra. The last official release of WindowMaker is a > > little bit old and the mentioned GIT repository looks very > > promising for bugfixes and new features. > > > > I hope we can help you a little bit with this step in testing and > > reporting bugs to your great work in the GIT repository. > > > > I have to wait for approval from the others developers, but normally > > that should be no problem. After that, there will be regular > > snapshots of the GIT repository available as official Arch Linux > > packages in our [extra]-repository. > > I am honored by this. But at the same time I would like to stress that > people should not expect much from me, except a fast handling of > other people's patches :-) > > Although I can sometimes get motivated into looking at some > particular bug (especially if it affects me), I can't make any > promises of even trying to fix them myself. > > Other than that, I have an obssessive compulsive disorder of trying > to make the code simpler to read. So every now and then when I, for > some reason, start to read the code I feel like some parts could > be streamlined. I would like to encourage everyone to do such things > (e.g. the patch by Tamas TEVESZ which cleaned up src/keybind.h). > It can make the code more maintainable (even smaller in some cases), > and it is a good way to know the code better. > > So it is not in my plans to make a revolution with wmaker, because > it is good enough for my usage. The idea is to have a place where > the code can be embellished and have some of the (few) annoyances > fixed. > > On the other hand, the recent issue with noisy appicons reported > by Joel Bertrand made me remember that one of the things which > Dan Pascu wanted to do was to replace the wrlib code with > the cairo lib. Their work can be found here > http://devel.windowmaker.info/cgi-bin/darcsweb.cgi?r=wm2;a=summary > > Perhaps someone can find the motivation to complete the work? > I think that would be a nice overall cleanup! What I like to see is that all the different CVS/SVN/GIT/mercurial work which are on the net is concentrated in one. As you mentioned it, the work of replacing wrlib with cairo sounds great, but it was never finished nor added to any other repository. That's really sad. I see a lot of effort in your GIT repository at the moment and I would really like to see, that your code will be merged sometime to the original one (best would be with the changes from Dan Pascu to use cairo). I really appreciate your work in the GIT repository and your handling of patches from the others. This behaviour should be done in the main mercurial repository of windowmaker to concentrate the work and release a new and hopefully better release of WindowMaker in the future. I will switch the package as soon as possible to follow your GIT repository, maybe there will be a new official release of WindowMaker with the patches which was already applied to the your repository and I will switch back to the official one. But at the moment your GIT repo is the most active one I have seen. And it seems that there are a lots of people who would like to see that WindowMaker becomes more popular than now, according to the wmaker-dev mailinglist and the log of GIT repo I would say that your GIT repo has become the most interested repo for WindowMaker development at the moment. That was one of my main reason for the decision to switch the package to your GIT repo. As I said it before, I would really like to see that all the work from the different repositories would be managed in one to provide the best WindowMaker experience and to (re-)activate the official WindowMaker development. Cheers, Daniel -- To unsubscribe, send mail to [email protected].
