> > Well, a positive review in Sage is just two persons agreeing together. >
Maybe you nailed exactly where the problem is. The problem might very well be that the person that ends up agreeing on the ticket review at the end is the only one that stuck around. I think that is a strong possibility. Also part of the problem is that everyone else either: - thinks they should be doing research instead (which is shortsighted and toxic to really bring sage to another level, in my view); - doesn't want to argue because they find it very unpleasant. (these two are of course not mutually exclusive) Due to the unfortunate absence of professional programmers to write and review our code and of mature professional mathematicians to establish clear strategic decisions for sage, we should actually as a research community be welcoming of diverse (already-coded) ideas, as long as they are not disruptive to other people's research objectives (the burden should be to prove that they disrupt). And even if there were, the burden should be for anyone to _improve_ code that is considered useful by them, not remove. This is because we have to be mindful that we are building mathematics software, and that as a consequence no individual (even a mathematician) will ever be able to comprehend the whole complexity that is being integrated into the software. Yet we want to provide as consistent of an experience as possible to cover various use cases. Fortunately, we can inform ourselves, learn what others are doing, take classes, go to conferences, and build up joint research projects with other disciplines. In light of this, please reflect on the amount of mathematics you know yourself. Do you know about L-functions? Have you tried to learn about them in Edinburgh or when I went to Paris to explain it to Nicolas and Florent? Do you know about category theory and what Nicolas is trying to do? (you have said several times explicitly on the list that you were not interested, but it is not clear to me that you understand it. One thing is sure: that you feel qualified to comment on it). It might be that individuals feel that they understand what findstat is doing but are failing to understand the broader context, which might explain why projects like findstat, LMFDB or even sage-combinat have unnecessarily complicated relationships with the sage core itself, and why some of my contributions end up in the LMFDB code and not sage itself. Also, have you talked to Francoise and the Logilab people at the Edinburgh workshop, people who are professional developing software in the sciences to handle research results? Do you know about semantic web technologies and things like that, especially as it is being applied to mathematics? Anyways, even if you don't know about all those things, don't worry: it is actually possible, for someone with an open mind, to learn those things or at least a sufficiently general picture. Paul > Perhaps I could just as a friend of mine who agrees that find_start > should be totally remved from Sage and let him give a positive review > to my ticket ? > > That's why we discuss stuff, and that's why you should feel > responsible when people are against what you implement. > > > The way I remember, nothing was really agreed at the end of this endless > discussion last year. If you want to open a ticket to remove > graph.to_partition, just do so. > > http://trac.sagemath.org/ticket/16403 > > Nathann > > -- > You received this message because you are subscribed to the Google Groups > "sage-combinat-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-combinat-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-combinat-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-combinat-devel. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/d/optout.
