Re: [boost] A history of the Boost Foundation
On Wed, Sep 11, 2024 at 2:41 PM Vladimir Prus
1) The Board does not impose its will on the developers on this list. It does sometimes make recommendations or official "calls" of some kind, like saying we should use CMake
So the email about cutting ties with the C++ Alliance, which started all this, was just non-binding minority report?
I don't get it. Isn't this the thing the developers are voting on right now? How is the Board imposing a change on the developers?
The original email had no proposal of a vote. Nor did it sound like a recommendation.
Right. But again, where was the impact on the Boost developers? I, as a Boost developer was not expected to, nor asked to, do anything differently from what I had done before. This vote was all about the Board not wanting to deal with the Alliance. We think that there would be an adverse impact on the Bosot developers, and think, "screw the developers!" If we expected our decision to adversely affect Boost development, we would have made a different one. Zach
No dia 11 de set. de 2024, às 21:53, Zach Laine via Boost
escreveu: Right. But again, where was the impact on the Boost developers? I, as a Boost developer was not expected to, nor asked to, do anything differently from what I had done before. This vote was all about the Board not wanting to deal with the Alliance. We think that there would be an adverse impact on the Bosot developers, and think, "screw the developers!" If we expected our decision to adversely affect Boost development, we would have made a different one.
I understood at the time that cutting ties with the alliance implied not accepting their funding of some functionalities like downloads, CI etc that certainly impact developers and users. Or maybe the proposal was to let them continue doing that, but without communication from the Boost Foundation? Joaquin M Lopez Munoz
On Wed, Sep 11, 2024 at 3:00 PM Joaquín M López Muñoz via Boost
No dia 11 de set. de 2024, às 21:53, Zach Laine via Boost
escreveu: Right. But again, where was the impact on the Boost developers? I, as a Boost developer was not expected to, nor asked to, do anything differently from what I had done before. This vote was all about the Board not wanting to deal with the Alliance. We think that there would be an adverse impact on the Bosot developers, and think, "screw the developers!" If we expected our decision to adversely affect Boost development, we would have made a different one.
I understood at the time that cutting ties with the alliance implied not accepting their funding of some functionalities like downloads, CI etc that certainly impact developers and users. Or maybe the proposal was to let them continue doing that, but without communication from the Boost Foundation?
The latter. We voted that we didn't want to keep trying to cooperate with them on future efforts, due to its being so frustrating. Zach
participants (2)
-
Joaquín M López Muñoz
-
Zach Laine