On Tue, Aug 4, 2020 at 2:32 PM Maciej Szymkiewicz <mszymkiew...@gmail.com> wrote: > > First of all why ASF ownership? > > For the project of this size maintaining high quality (it is not hard to use > stubgen or monkeytype, but resulting annotations are rather simplistic) > annotations independent of the actual codebase is far from trivial. For > starters, changes which are mostly transparent to the final user (like > pyspark.ml changes in 3.0 / 3.1) might require significant changes in the > annotations. Additionally some signature changes are rather hard to track and > such separation can easily lead to divergence. > > Additionally, annotations are as much about describing facts, as showing > intended usage (the simplest use case is documenting argument dependencies). > This makes process of annotation rather subjective and requires good > understanding of author's intention. > > Finally, annotation-friendly signatures require conscious decisions (see for > example https://github.com/python/mypy/issues/5621). > > Overall, ASF ownership is probably the best way to ensure long-term > sustainability and quality of annotations. >
Yes, but the general argument you make here is: if you tie this project to the main project, it will _have_ to be maintained by everyone. That's good, but also exactly I think the downside we want to avoid at this stage (I thought?) I understand for some undertakings, it's just not feasible to start outside the main project, but is there no proof of concept even possible before taking this step -- which more or less implies it's going to be owned and merged and have to be maintained in the main project. --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
