Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-04-02 Thread Jaimos Skriletz
On Fri, Apr 1, 2016 at 5:43 PM, Thomas Adam wrote: > On Fri, Apr 01, 2016 at 02:47:24PM -0600, Jaimos Skriletz wrote: > > ​​ > > Thanks! It looks really good. We can remove the Changelog section; people > can look at the release descriptions and/or Git history from now on. > Maintaining this is

Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-04-02 Thread Dan Espen
Jaimos Skriletz writes: > Also I am unsure if these various markdown files, FAQ.md, AUTHORS.md, > DEVELOPERS.md, etc should be located and maintained on the webpage or > in $FVWM.GIT source. I think either can work with git.io so it is > probably a matter of preference. But agreed, these markdown

Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-04-02 Thread Thomas Adam
On Sat, Apr 02, 2016 at 11:58:41AM -0600, Jaimos Skriletz wrote: > On Fri, Apr 1, 2016 at 5:43 PM, Thomas Adam wrote: > > > On Fri, Apr 01, 2016 at 02:47:24PM -0600, Jaimos Skriletz wrote: > > > ​​ > > > > Thanks! It looks really good. We can remove the Changelog section; people > > can look at

Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-04-02 Thread Thomas Adam
On Sat, Apr 02, 2016 at 02:45:22PM -0400, Dan Espen wrote: > Jaimos Skriletz writes: > > > Also I am unsure if these various markdown files, FAQ.md, AUTHORS.md, > > DEVELOPERS.md, etc should be located and maintained on the webpage or > > in $FVWM.GIT source. I think either can work with git.io s