Le Fri, 30 Nov 2012 09:33:00 -0500,
Tom Horsley horsley1...@gmail.com a écrit :
On Fri, 30 Nov 2012 14:06:36 +0100
Adam Sjøgren wrote:
I think it would be much more accurate to call FVWM mature.
An even better word is useful (unlike many linux products under
frenetic active development
Hi,
Is it true that fvwm has no maintainer now? if so, is fvwm still being
developed anymore? are there any features planned or is it a dying project?
TIA!
Jason
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
On Fri, Nov 30, 2012 at 02:28:16AM -0800, Jason Timrod wrote:
Hi,
Is it true that fvwm has no maintainer now? if so, is fvwm still being
No. For years, FVWN has had no *one* maintainer *by design*. Any one with
a commit bit is effectively able to commit back.
-- Thomas Adam
On Fri, 30 Nov 2012 14:06:36 +0100
Adam Sjøgren wrote:
I think it would be much more accurate to call FVWM mature.
An even better word is useful (unlike many linux products under
frenetic active development by folks who believe change is always
good no matter how stupid it is :-).
On 24 February 2010 22:50, David Chanters david.chant...@googlemail.com wrote:
On 23 February 2010 00:16, des...@verizon.net 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
On 23 February 2010 00:16, des...@verizon.net 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
On 23 February 2010 11:08, Thomas Adam tho...@xteddy.org 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
On 23 February 2010 00:16, des...@verizon.net 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
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
10 matches
Mail list logo
