Most FOSS licenses don't require
attribution (although ethically it's better to do so), however, almost all requires the preservation of
copyright notices, and the name of the author is always part of the notice. For example,
> Copyright (C) $years $author
> Permission is hereby granted, free of charge, to any person [...] subject to the following conditions:
> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
And usually, the copyright notices appear in the beginning of all files for clarity.
Although some projects with too many developers may agree to use alternative attribution and copyright identification methods, such as git "Sign-Off", an author file, or SPDX machine-readable license notice. In these cases, it's considered a common practice to use a collective name in the copyright notice, such as
> // Copyright 2019 The Chromium Authors. All rights reserved.
But in most cases, it's a bad idea to remove any name from the header.
---
In the Guake's case, the copyright notice is changed to,
> Copyright (C) 2007-2013 Guake authors
with the original name removed. On one hand, the use of a collective name is common, it's not too different from Chromium, or other major projects. In a sense, it's acceptable, as long as the method of author identification is clearly defined (e.g. git sign-off). Anyone contributes the project is assumed to have accepted how attribution is done implicitly.
However, the problem is that the original name is removed - changing the notice retroactively should be done with the permission of the author, which is clearly not obtained here. A common practice in such circumstance is leaving the original copyright year and author in place, and appending new copyright information below (or above) the original notice, so it should be something like this,
> Copyright (C) 2007 Gabriel Falcão
> Copyright (C) 2008-2013 Guake authors
This example is generally considered "good" since (1) credit is given where credit is due, (2) it also shows the copyright holders responsible for the project in different period of time.
For example, the copyright notice of Python is,
> Copyright (c) 2001-2019 Python Software Foundation.
> All Rights Reserved.
> Copyright (c) 2000 BeOpen.com.
> All Rights Reserved.
> Copyright (c) 1995-2001 Corporation for National Research Initiatives.
> All Rights Reserved.
> Copyright (c) 1991-1995 Stichting Mathematisch Centrum, Amsterdam.
> All Rights Reserved.