Where does this review happens?Is it possible to put code somewhere like GitHub/BitBucket/GitLab, so that other people can comment conveniently, because mailing list is kind of weird (personal opinion) in 2016.
I'm participating in other projects, and GitHub (even mirror just for PRs and their discussion, not primary repo) helps significantly. It is really useful when 3 non-maintainers wrote some comments, PR is improved in process and when maintainer comes there is less work for him.
Passing all this information through everyone on mailing list is counterproductive in many ways.
Sincerely, Nazar Mokrynskyi github.com/nazar-pc Skype: nazar-pc Diaspora: [email protected] Tox: A9D95C9AA5F7A3ED75D83D0292E22ACE84BA40E912185939414475AF28FD2B2A5C8EF5261249 On 28.03.16 11:42, Alexander E. Patrakov wrote:
28.03.2016 12:13, Arun Raghavan wrote:Our current way of doing things is good for keeping up code quality, but I think over time, with such a large patch backlog, we end up spending more and more time performing reviews, and less and less time working on features. This becomes quite draining and drops our overall productivity in contributing to the project.I think it is in our interests to think how to get these features, where possible, without reviewing too many patches and without sacrificing the code quality of PulseAudio. That includes encouraging our contributors to implement features externally to PulseAudio if it is easier. And an external module SDK would also be a step forward.I also think I should try porting the existing RAOP2 patch set to make it an ALSA plugin instead, to set an example of the "externally where it is easier" rule.
smime.p7s
Description: Кріптографічний підпис S/MIME
_______________________________________________ pulseaudio-discuss mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
