Anatoly, First of all, your post is off-topic for this list. We are here to discuss the workflow of core Python development and related tools, not to have general discussions about workflow.
Next, using a title such as "agile (gameplay) vs rigid (process)" is inflammatory (= will make people angry) but uninformative and unhelpful. Furthermore, to the extent of my understanding of the relevant terms, you show a complete misunderstanding of them. Here are some specific examples: > Agile workflows often take into account > personalities, habits and environment of people > involved in a process. I have never encountered a workflow which specifically takes into account personalities and habits. In my opinion it is silly to say that agile workflows take personalities and habits into account while other workflows do not. On the other hand, regardless of workflow, any specific development group should take into account many considerations, including the environment and its members' personalities and habits. This has nothing to do with workflow, so I simply cannot make any sense of your above statement. > Just think about why different people don't feel fun > contributing to Python overall, who are those people, > why Python community needs them, and how you > can help them by removing obstacles. This is precisely what the Python developers and the PSF have always done. Specifically, in recent years they have been spending more and more time and effort on this. Despite this you have repeatedly (now and in the past) accused them all of not doing so, and you are simply completely *wrong*. This just shows how distorted your view of the Python developers is. > workflow types: agile (gameplay) vs rigid (process) This is ridiculous. Every agile methodology I have heard of includes some specific process for development. From all of the development groups I have been in or worked with, those which used "agile" methods had much clearer processes which they actually stuck to and which were usually more effective. "Agile" does not mean not taking work seriously and it is not an excuse for lack of process. Perhaps you have met some developers who used "agile" as an excuse for not defining processes, but you would be wrong to think this is true of all other groups who use "agile" methods. To summarize, this post is off-topic, inflammatory and contains several grossly incorrect statements. In my opinion this discussion should not continue here. - Tal Einat _______________________________________________ core-workflow mailing list [email protected] https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
