Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Cor Nouws
Hi, Thorsten Behrens wrote on 14/03/2022 21:20: Caolán McNamara wrote: I tend to agree. I don't think making it trivial to deattic something by applying a set of superficial commits to a very large code base which don't achieve meaningful change while f.e. unaddressed security issues mount up,

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Thorsten Behrens
Hi *, Caolán McNamara wrote: > I tend to agree. I don't think making it trivial to deattic something > by applying a set of superficial commits to a very large code base > which don't achieve meaningful change while f.e. unaddressed security > issues mount up, creating a sort of zombie would be a

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Paolo Vecchi
Hi Jan, On 14/03/2022 19:43, Jan Holesovsky wrote: Hi Paolo, Paolo Vecchi píše v Po 14. 03. 2022 v 17:07 +0100: I have to agree with you that the process seems to be too cumbersome and it would very likely lead to the end of the project, so may as well delete it, or to forks that will never

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Michael Stahl
hi Andreas, On 14.03.22 18:36, Andreas Mantke wrote: and with the proposal the Android Viewer had to be put the attic and wouldn't currently get the chance to get out of this state (because only one developer looking for it). that's a bad example: the Android Viewer is in the core.git

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Jan Holesovsky
Hi Paolo, Paolo Vecchi píše v Po 14. 03. 2022 v 17:07 +0100: > I have to agree with you that the process seems to be too cumbersome > and > it would very likely lead to the end of the project, so may as well > delete it, or to forks that will never come back. Interestingly when I've read the

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Cor Nouws
Hi, Andreas Mantke wrote on 14/03/2022 18:36: and with the proposal the Android Viewer had to be put the attic and wouldn't currently get the chance to get out of this state (because only one developer looking for it). Fair point. One could think of a way that the activity/nr of devs asked,

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Andreas Mantke
Hi Cor, all, Am 14.03.22 um 17:34 schrieb Cor Nouws: Hi Andras, Andreas Mantke wrote on 13/03/2022 16:12: the quintessence of he proposal would be that a project will at 99,9% or more wouldn't get out of the attic state inside the TDF resources. The barriers to de-attic a project and make it

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Caolán McNamara
On Mon, 2022-03-14 at 17:34 +0100, Cor Nouws wrote: > For me the clear demands in the proposal are to prevent a situation > where projects restart without a good change on success, which is IMO > quite relevant for TDF's good name. I tend to agree. I don't think making it trivial to deattic

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Cor Nouws
Cor Nouws wrote on 14/03/2022 17:34: Hi Andras, Andreas Mantke wrote on 13/03/2022 16:12: the quintessence of he proposal would be that a project will at 99,9% or more wouldn't get out of the attic state inside the TDF resources. The barriers to de-attic a project and make it an active

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Cor Nouws
Hi Andras, Andreas Mantke wrote on 13/03/2022 16:12: the quintessence of he proposal would be that a project will at 99,9% or more wouldn't get out of the attic state inside the TDF resources. The barriers to de-attic a project and make it an active project inside TDF are much higher than

Re: [board-discuss] Draft text: an "attic" proposal - version 2.0

2022-03-14 Thread Paolo Vecchi
Hi Andreas, thanks for your feedback. I have to agree with you that the process seems to be too cumbersome and it would very likely lead to the end of the project, so may as well delete it, or to forks that will never come back. The point here is also to try to understand what the scope of

[board-discuss] [DECISION] Approve version 1.3.2 of the CoI policy

2022-03-14 Thread Florian Effenberger
Hello, The Board of Directors at the time of voting consists of 7 seat holders (not including deputies). In order to be quorate, the vote needs to have 1/2 or more of the Board of Directors members, which gives 4. A total of 6 Board of Directors members have participated in the vote. The