News for hackers. Stuff that matters.
Re:Winding down my Debian involvement by giovannibajo1 on Sunday March 10, 2019 @02:24PM (#19353392)
Those changes are reviewed by maintainers. The fact that a random stranger is able to push a change and get it reviewed, approved, merged, and available in minutes should be the goal of most open source projects. On the contrary, older projects tend to be too reactionary when it comes to infrastructure tools, so in turn they get very slow interactions. This becomes a demotivator for anybody who is used to more efficient workflows.

It is not a coincidence that the author became demotivated after doing some professional experience.

Re:Winding down my Debian involvement by ethbro on Sunday March 10, 2019 @05:31PM (#19354674)
> The fact that a random stranger is able to push a change and get it reviewed, approved, merged, and available in minutes should be the goal of most open source projects

> On the contrary, older projects tend to be too reactionary when it comes to infrastructure tools, so in turn they get very slow interactions

Well said.

'Open source' doesn't say anything about infrastructure. But it's just as important.

Re:Winding down my Debian involvement by msh on Monday March 11, 2019 @05:05AM (#19357588)
> The fact that a random stranger is able to push a change and get it reviewed, approved, merged, and available in minutes should be the goal of most open source projects.

That sounds like a security risk to me.

Re:Winding down my Debian involvement by pawelmurias on Monday March 11, 2019 @06:45AM (#19357948)
How much safer is it if pushing in a malicious change takes two months?
Re:Winding down my Debian involvement by sidcom on Monday March 11, 2019 @01:40PM (#19360965)
I had to re-read it too. He does not say that the same dev should do all these things