On Mon, Aug 18, 2014 at 12:37:37PM +0100, Michael Treibton wrote: > On 18 August 2014 05:50, Dan Espen <[email protected]> wrote: > > Brian <[email protected]> writes: > > > >> On Sun, 17 Aug 2014 15:25:43 +0100 > >> Michael Treibton <[email protected]> wrote: > >> > >>> On 15 August 2014 21:05, Dominik Vogt <[email protected]> wrote: > >>> > I'll start a new mail thread about parsing with the prefix > >>> > "REWRITE: " in a minute. > >>> > > >>> > In the mean time I've created a github user id 'domivogt' and > >>> > cloned the mvwm repository and would be happy if you gave me push > >>> > access so that I can start to work in topic branches there. > >>> > >>> Can I help in some way? > >>> > >>> Michael > >> > >> I too would like to help someway. Is there a person to send a > >> skills resume to for review and assignment to the project? > >> Brian Amundsen in Minnesota. > > > > Read this: > > > > http://fvwm.org/documentation/dev_cvs.php > > > > anyone can write and submit a patch. > > Thank you, Dan. I was hoping more for mvwm. I can't see how the > instructions would be the same?
They're not the same, but at the present time, there's nothing in term of mvwm development we need, other than to document the way the parser works at the moment, which is what Dominik and I are currently working on. Is this perhaps not clear enough? I appreciate the enthusiasm, but this groundwork is really important before we can move forward. Unless there's anyone else who wishes to help out with this---which would mean understanding a fair amount of fvwm internals at this point, etc., I am not sure what else to suggest you can do for now. If you've found a genuine bug in fvwm which you're wanting to fix, then the instructions Dan is pointing you to are precisely what you need to follow in terms of generating a patch, etc. HTH, -- Thomas Adam
