4 ms·

> to ensure future funding and volunteer hours are used efficiently and effectively. One of the reasons that Python’s development has been so haphazard in the

by pansa2 6y ago

> to ensure future funding and volunteer hours are used efficiently and effectively. One of the reasons that Python’s development has been so haphazard in the past few years is because the language is primarily developed by volunteers, and the philosophy has been that “you can’t tell volunteers what to work on”. I wonder if something’s going to change there.

dragonwriter 6y ago
Google paying for approximately 1 developer isn’t going to change that the vast majority of Python work is done by volunteers who the PSF isn’t in a position to direct, no.
- pansa2 6y ago
  How are they planning to “ensure volunteer hours are used effectively” if they can’t direct those volunteers?
  - dragonwriter 6y ago
    There is presumably some volunteer work of some kind done directly for PSF, which they can direct, but most of the Python development work isn't done that way. You can probably improve (ensure is to strong of a term) the effectiveness of outside volunteer development in a number of ways, though, such as improving community communication of priorities and improving processes around accepting, reviewing, and providing feedback on contributed code.
  - bregma 6y ago
    The volunteer hours are used to offer contributions. Those contributions are accepted or rejected. If you control what gets accepted or rejected, you control the definition of how the volunteer hours are used effectively in terms of the final result. Remember: "open source" has never meant anyone can get changes upstreamed. It has always only meant anyone can use the source downstream. This confusion has resulted in a lot of indignant outrage by armchair contributors.
forgotmypw17 6y ago
Well, if Mozilla is any indicator... Python will become a slower clone of Go, dropping useful features and adding ones no one asked for, while Python Foundation will acquire a completely unrelated data collection company :D

by pansa2 6y ago

dragonwriter 6y ago

Google paying for approximately 1 developer isn’t going to change that the vast majority of Python work is done by volunteers who the PSF isn’t in a position to direct, no.

pansa2 6y ago
How are they planning to “ensure volunteer hours are used effectively” if they can’t direct those volunteers?
- dragonwriter 6y ago
  There is presumably some volunteer work of some kind done directly for PSF, which they can direct, but most of the Python development work isn't done that way. You can probably improve (ensure is to strong of a term) the effectiveness of outside volunteer development in a number of ways, though, such as improving community communication of priorities and improving processes around accepting, reviewing, and providing feedback on contributed code.
- bregma 6y ago
  The volunteer hours are used to offer contributions. Those contributions are accepted or rejected. If you control what gets accepted or rejected, you control the definition of how the volunteer hours are used effectively in terms of the final result. Remember: "open source" has never meant anyone can get changes upstreamed. It has always only meant anyone can use the source downstream. This confusion has resulted in a lot of indignant outrage by armchair contributors.

forgotmypw17 6y ago

Well, if Mozilla is any indicator... Python will become a slower clone of Go, dropping useful features and adding ones no one asked for, while Python Foundation will acquire a completely unrelated data collection company :D