Re: [fvwmorg/fvwm] b753a0: Remove stale files

[Dominik Vogt]

On Sun, Oct 23, 2016 at 01:55:38AM +0100, Dominik Vogt wrote:
> On Sun, Oct 23, 2016 at 01:32:17AM +0100, Thomas Adam wrote:
> > On Sun, Oct 23, 2016 at 01:28:17AM +0100, Dominik Vogt wrote:
> > > On Thu, Aug 11, 2016 at 04:23:47PM -0700, GitHub wrote:
> > > >   Branch: refs/heads/ta/install
> > > >   Home:   https://github.com/fvwmorg/fvwm
> > > >   Commit: b753a06d2eb0325fd682563fcc127acbd6cf7813
> > > >   
> > > > https://github.com/fvwmorg/fvwm/commit/b753a06d2eb0325fd682563fcc127acbd6cf7813
> > > >   Author: Thomas Adam 
> > > >   Date:   2016-08-11 (Thu, 11 Aug 2016)
> > > > 
> > > >   Changed paths:
> > > > R ChangeLog
> > > > R ChangeLog-pre-2.4
> > > > R ChangeLog-pre-2.6.6
> > > > R NEWS
> > > 
> > > Hm, what's the logic behind removing the NEWS file?  Is it
> > > somewhere else now?
> > 
> > It's mostly here:  http://fvwm.org/features/ (because stuff hasn't changed),
> 
> > and its successor will be release notes for the next version on Github 
> > anyway.
> 
> Okay, and where is the source for the release notes?  This needs
> to be kept in the fvwm source tree.  I don't see me writing up any
> decent quality release notes, say, half a year after committing a
> patch.  This stuff needs to be written down when the work is done,
> not at some indefinite time in the future.
> 
> (I see fvwm more as a GNU style project rather than a Github style
> project.  Using features of git or Github is fine, but I don't
> think we should give up the GNU project standards, where
> applicable: https://www.gnu.org/prep/standards/standards.txt

Specifically, it won't cost much to to stick to the following:

  3.5 Conditional Compilation
  4.4 Formatting Error Messages -> future work
  4.5 Standards for Interfaces Generally
  4.6 Standards for Graphical Interfaces
  4.7 Standards for Command Line Interfaces
  4.8 Standards for Dynamic Plug-in Interfaces
  4.9 Table of Long Options
  5.5 Portability between System Types
  5.6 Portability between CPUs
  5.7 Calling System Functions
  5.8 Internationalization
  5.9 Character Set
  5.10 Quote Characters
  6.7 The NEWS File
  6.8 Change Logs -> now kept in Git
  6.9 Man Pages
  7.1 How Configuration Should Work
  7.2 Makefile Conventions

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt

Re: [fvwmorg/fvwm] b753a0: Remove stale files

[Thomas Adam]

On Sun, Oct 23, 2016 at 01:55:38AM +0100, Dominik Vogt wrote:
> The NEWS file has been a readable summary of user visible changes.
> I don't see how this could be generated from commit information
> and diffs in git.

It's back.

-- Thomas Adam

Re: [fvwmorg/fvwm] b753a0: Remove stale files

[Dominik Vogt]

On Sun, Oct 23, 2016 at 01:32:17AM +0100, Thomas Adam wrote:
> On Sun, Oct 23, 2016 at 01:28:17AM +0100, Dominik Vogt wrote:
> > On Thu, Aug 11, 2016 at 04:23:47PM -0700, GitHub wrote:
> > >   Branch: refs/heads/ta/install
> > >   Home:   https://github.com/fvwmorg/fvwm
> > >   Commit: b753a06d2eb0325fd682563fcc127acbd6cf7813
> > >   
> > > https://github.com/fvwmorg/fvwm/commit/b753a06d2eb0325fd682563fcc127acbd6cf7813
> > >   Author: Thomas Adam 
> > >   Date:   2016-08-11 (Thu, 11 Aug 2016)
> > > 
> > >   Changed paths:
> > > R ChangeLog
> > > R ChangeLog-pre-2.4
> > > R ChangeLog-pre-2.6.6
> > > R NEWS
> > 
> > Hm, what's the logic behind removing the NEWS file?  Is it
> > somewhere else now?
> 
> It's mostly here:  http://fvwm.org/features/ (because stuff hasn't changed),

> and its successor will be release notes for the next version on Github anyway.

Okay, and where is the source for the release notes?  This needs
to be kept in the fvwm source tree.  I don't see me writing up any
decent quality release notes, say, half a year after committing a
patch.  This stuff needs to be written down when the work is done,
not at some indefinite time in the future.

(I see fvwm more as a GNU style project rather than a Github style
project.  Using features of git or Github is fine, but I don't
think we should give up the GNU project standards, where
applicable: https://www.gnu.org/prep/standards/standards.txt
)

I don't care much about the other files (ChangeLogs and such), but
fvwm should have a NEWS file like other GNU projects.

> If people really want more detail they can look in git.  The point of removing
> these files is duplicating these things when git provides most of them is a
> good thing.

The NEWS file has been a readable summary of user visible changes.
I don't see how this could be generated from commit information
and diffs in git.

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt

Re: [fvwmorg/fvwm] b753a0: Remove stale files

[Thomas Adam]

On Sun, Oct 23, 2016 at 01:28:17AM +0100, Dominik Vogt wrote:
> On Thu, Aug 11, 2016 at 04:23:47PM -0700, GitHub wrote:
> >   Branch: refs/heads/ta/install
> >   Home:   https://github.com/fvwmorg/fvwm
> >   Commit: b753a06d2eb0325fd682563fcc127acbd6cf7813
> >   
> > https://github.com/fvwmorg/fvwm/commit/b753a06d2eb0325fd682563fcc127acbd6cf7813
> >   Author: Thomas Adam 
> >   Date:   2016-08-11 (Thu, 11 Aug 2016)
> > 
> >   Changed paths:
> > R ChangeLog
> > R ChangeLog-pre-2.4
> > R ChangeLog-pre-2.6.6
> > R NEWS
> 
> Hm, what's the logic behind removing the NEWS file?  Is it
> somewhere else now?

It's mostly here:  http://fvwm.org/features/ (because stuff hasn't changed),
and its successor will be release notes for the next version on Github anyway.

If people really want more detail they can look in git.  The point of removing
these files is duplicating these things when git provides most of them is a
good thing.

-- Thomas Adam

Re: [fvwmorg/fvwm] b753a0: Remove stale files

[Dominik Vogt]

On Thu, Aug 11, 2016 at 04:23:47PM -0700, GitHub wrote:
>   Branch: refs/heads/ta/install
>   Home:   https://github.com/fvwmorg/fvwm
>   Commit: b753a06d2eb0325fd682563fcc127acbd6cf7813
>   
> https://github.com/fvwmorg/fvwm/commit/b753a06d2eb0325fd682563fcc127acbd6cf7813
>   Author: Thomas Adam 
>   Date:   2016-08-11 (Thu, 11 Aug 2016)
> 
>   Changed paths:
> R ChangeLog
> R ChangeLog-pre-2.4
> R ChangeLog-pre-2.6.6
> R NEWS

Hm, what's the logic behind removing the NEWS file?  Is it
somewhere else now?

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt