Re: FVWM: fvwm development
On Fri, 30 Nov 2012 02:28:16 -0800 (PST), Jason wrote: > is fvwm still being developed anymore? Check the source code repository¹? :-) > are there any features planned or is it a dying project? FVWM works great for me, so - to me - that means it is a very successful project. I don't miss any features currently, so if there are no features planned that doesn't make it a dying project, in my eyes. If you want revolutions every other week, other projects are probably more worth your while. I think it would be much more accurate to call FVWM "mature". Best regards, Adam ¹: Here is a service that makes statistics and stuff from free software repositories: https://www.ohloh.net/p/fvwm -- "I am still twitching at the idea that you need to Adam Sjøgren load code into the kernel in order to re-map a a...@koldfront.dk mouse button."
Re: FVWM: fvwm development - and interview idea
On 21 February 2010 20:23, David Chanters wrote: > Hi all > > I've noticed a lot of activity with fvwm lately, and was wondering: > > - is there a way of improving documentation? > - what's the roadmap for fvwm's future? > - when will fvwm 2.6 be released? > > Is there a document to describe this? > > Also, i would like to offer the chance to interview some of the > developers of fvwm so i can publish the exchange online - who is best > for this please? i was thinking recent development thats been interesting - i know there's the history.php page on fvwm.org already This would be an email interview. David
Re: FVWM: fvwm development - and interview idea
David Chanters writes: > Hi all > > I've noticed a lot of activity with fvwm lately, and was wondering: > > - is there a way of improving documentation? Submit patches. > - what's the roadmap for fvwm's future? > - when will fvwm 2.6 be released? > Is there a document to describe this? Look at the TODO file in the source tree. > Also, i would like to offer the chance to interview some of the > developers of fvwm so i can publish the exchange online - who is best > for this please? They're shy so I'll do a little promotion for them. Thomas Adam has been doing most of the recent development. Dominik Vogt has probably contributed more than any other single person to Fvwm and has become the unquestioned expert. Viktor Griph has been pretty active too.
Re: FVWM: fvwm development - and interview idea
On 23 February 2010 00:16, wrote: > Submit patches. Er, ok. i will try >> - what's the roadmap for fvwm's future? >> - when will fvwm 2.6 be released? >> Is there a document to describe this? > > Look at the TODO file in the source tree. i saw this, but is it accurate for the current dev work? > Thomas Adam has been doing most of the recent development. > Dominik Vogt has probably contributed more than any other single > person to Fvwm and has become the unquestioned expert. > Viktor Griph has been pretty active too. ok - then i will wait and see! thansk David
Re: FVWM: fvwm development - and interview idea
Hello -- On 23 February 2010 00:16, wrote: > They're shy so I'll do a little promotion for them. > > Thomas Adam has been doing most of the recent development. Ah, I really don't think I can say that I've done much -- I am not sure what you'd get out of me personally from some sort of interview, so I'll politely decline. :) -- Thomas Adam
Re: FVWM: fvwm development - and interview idea
Hello -- On 21 February 2010 20:23, David Chanters wrote: > Hi all > > I've noticed a lot of activity with fvwm lately, and was wondering: > > - is there a way of improving documentation? Which documentation? Something in the man page or larger volumes of text, such as random guides/tutorials which are floating around on the 'net? You might want to try and contribute to the FvwmWiki if it's nothing too specific and you feel you have something you would like to contribute. > - what's the roadmap for fvwm's future? > - when will fvwm 2.6 be released? When it's ready. I'm really trying to push to get it out the door beginning of May, but there's some things still left to do on my own TODO list, most of which is already referenced in the TODO file in the source tree --- I do make a habit of updating it as I go along. ;) > Is there a document to describe this? Dan Espen has already mentioned the TODO file. See above, also. -- Thomas Adam
Re: FVWM: fvwm development - and interview idea
On 23 February 2010 11:11, Thomas Adam wrote: > Which documentation? Something in the man page or larger volumes of > text, such as random guides/tutorials which are floating around on the > 'net? You might want to try and contribute to the FvwmWiki if it's > nothing too specific and you feel you have something you would like to > contribute. i hoped for a tutorial. i will check the wiki then, thank you. > When it's ready. I'm really trying to push to get it out the door > beginning of May, but there's some things still left to do on my own > TODO list, most of which is already referenced in the TODO file in the > source tree --- I do make a habit of updating it as I go along. ;) thank you - i have read this so will wait patiently. David
Re: FVWM: fvwm development - and interview idea
On 23 February 2010 11:08, Thomas Adam wrote: > Ah, I really don't think I can say that I've done much -- I am not > sure what you'd get out of me personally from some sort of interview, > so I'll politely decline. :) that is disappointing as i recall reading things from you on the internet about fvwm. but ok. thanks for telling me :) David
Re: FVWM: fvwm development - and interview idea
On 23 February 2010 00:16, wrote: > Look at the TODO file in the source tree. i did this, and have some questions: - whats the update with the fvwm-convert2.6 script? - according to the TODO file, the only thing remaining is this script? whats outstanding with the convert2.6 script thats holding 2.5.x becoming 2.6.0? Thanks! David
Re: FVWM: fvwm development - and interview idea
On 24 February 2010 22:50, David Chanters wrote: > On 23 February 2010 00:16, wrote: >> Look at the TODO file in the source tree. > > i did this, and have some questions: > > - whats the update with the fvwm-convert2.6 script? Functional, as far as I know. I have a patch kicking around to get it to try and convert over FvwmTheme config lines to Colorsets, although it's a little tricky, and won't ever be able to completely automate the process. > - according to the TODO file, the only thing remaining is this script? No -- there's test-cases to write, which I am in the process of. The whole purify test suite needs an overhaul anyway. If I can't be bothered^H^H^H^^get round to doing it at that level, then I'll list it as a potential GSOC project. This isn't hard -- it's just very boring work. :) I have a number of patches in my queue for review, as well as fixing another MinOverlap bug. These should probably take slightly higher priority than test-cases, although none of the patches up for review are bug-fixes. > whats outstanding with the convert2.6 script thats holding 2.5.x becoming > 2.6.0? It just needs a shed-load more testing than it's gotten at the moment (i.e., other than me scouting the Internet for older config files. :P) Does that answer your question? -- Thomas Adam
