User talk:Barto

From ProofWiki
Jump to: navigation, search

Splitting Theorem and Definition

Thanks for your work on Definition:Z-Module Associated with Abelian Group, it was long overdue.

In the future, please take care to duplicate any sources listed on the original integrated page on both resultants, and flag them with Template:SourceReview. This way, we can ensure to continue representing the content of said sources as faithfully as possible.

If applicable, please also attend to any links to the page via "Tools -> What links here" in the sidebar menu. They might have to be updated to the new definition. — Lord_Farin (talk) 16:46, 5 December 2016 (EST)

I'll keep it in mind.--barto (talk) 03:24, 6 December 2016 (EST)
Also please note the wording of the SourceReview template, with particular reference to the word "following". It is how we distinguish between sources which have been reviewed and those we have not. --prime mover (talk) 06:56, 6 December 2016 (EST)

Consistent naming

Thank you for taking the time and effort to improve the structure of this area -- it is long overdue.

The reason for inconsistent naming between e.g. direct product of groups and direct sum of rings is purely as a result of the source works that the material came from.

The definition namespace of $\mathsf{Pr} \infty \mathsf{fWiki}$ was conceived more or less as a dictionary of existing usage, and as such we make the effort to stick to what is found in the source works which are plundered to provide material. If it just so happens that the source work used uses "sum", then that, by default, is what was taken.

So I don't think there are problems with renaming Ring Direct Sum to Ring Direct Product, and I don't think there are many pages that would need to be changed to accommodate it. As is our usual technique, we can of course use "Also known as" to explain the differences in terminology.

As for removing "external" from all "external direct product" pages -- again, I think that should be okay. I was specifically using "external" as opposed to "internal" as I had trouble with this when first studying group theory and I needed to make sure I was very sure what was being discussed -- particularly when I was battling with the Internal Direct Product Theorem -- but now I look back on it, I think we would be okay to just use "Direct Product" for what is now "External Direct Product", using an "also known as" section to explain the alternative terms. --prime mover (talk) 06:53, 17 December 2016 (EST)

Thank you for your assistance! Indeed, because for finite families they coincide, different authors may (rightfully!) use different names if they do not consider the infinite case. As for External: While I do prefer "Direct Product" over "External Direct Product"; I would not mind if page names include "External" as long as there are appropriate redirects to them. As for Internal Sum vs. Internal Product: Both are used and mean the same (at least for groups, rings, modules). Naturally, sum is reserved for the commutative case; that is, for modules (and vector spaces), while product is used in the non-commutative case (so more fitting for groups and rings). The reason we do not make a distinction between internal direct sum and internal direct product is that within a structure, we cannot take infinite sums/products --barto (talk) 07:07, 17 December 2016 (EST)
You seem to have a far better handle on this than me, who, since my MMath, my entire knowledge is self-learned and haphazard. Feel free to go ahead, as you know where the devils are in the details. --prime mover (talk) 07:10, 17 December 2016 (EST)
Before we start renaming pages: do we go for X Direct Product (as in Definition:Module Direct Product and many others) or Direct Product of X'es (as in Definition:External Direct Sum of Rings and Definition:Direct Product of Vector Spaces )? Are there cons of Direct Product of X'es besides alphabetic ordering? --barto (talk) 08:12, 17 December 2016 (EST)
I believe that "Group Direct Product" is a standard term used commonly in AbAlg and Group Theory as I have seen it a few times in source works. I don't know about modules. My gut tells me to go with whatever is most "standard" and if that means naming is inconsistent, then that is of less importance than intellectual accessibility, but it is not a point I feel strongly about. If you feel it would be an improvement to be consistent, then DP of Xs works better for me as a general standard than XDP. Others may differ, but it is up to them to express an opinion, and if they don't it is assumed they may not be strongly concerned either way. --prime mover (talk) 08:23, 17 December 2016 (EST)

I vote DP of Xs. Looking at your ambitious plans, one point of attention is the approach of universal properties. Because there is always the open point of integrating all this with the category-theoretic perspective one day, where of course the universal property is the defining concept, and the abstract-algebraic definition is a means of fulfilling this definition.

But maybe it's not a thing that realistically can be incorporated at this point. Feel free to proceed even if you're not able to come up with a universal approach (heh ;)). — Lord_Farin (talk) 15:53, 18 December 2016 (EST)

Making the definitions more complicated

We have a specific policy on $\mathsf{Pr} \infty \mathsf{fWiki}$ to put only definitions in a definition page, and not clutter it up with justifications for the validity of the definition. If there is a genuine need to justify the existence of an object because it is non-intuitive, then we add it as a separate proof page.

Hence I reversed out your additions to Ceiling and Floor definitions. --prime mover (talk) 01:11, 29 January 2017 (EST)

Okay. What about adding just one sentence to the definition, just to link to a page where it is shown that the definition is valid? --barto (talk) 03:38, 29 January 2017 (EST)
See the "Also see" section. --prime mover (talk) 04:31, 29 January 2017 (EST)

Continued good work

I appreciate the way you've got the general "feel" of $\mathsf{Pr} \infty \mathsf{fWiki}$ and you're generating some seriously worthwhile content.

Please do not feel offended if I (or others) spontaneously amend (or even reverse out) some of your changes, or change the notation, presentational style and even source code style in ways which may look arbitrary. It's all working towards completely consistency of content and structure. --prime mover (talk) 16:23, 23 April 2017 (EDT)

No problem. I'm happy to contribute, especially if it's things you most likely won't find anywhere else (because nobody has made the effort to write out a proof). Of all the small amendments I can think of only one I dislike, which is the use of \left ... \right for every pair of brackets. It creates additional spacing before the brackets, which I don't find aesthetic: $f\left(x\right)$ vs. $f(x)$, or worse: $\gcd\left(a,b\right)$ vs $\gcd(a,b)$. It's as if the $\gcd$ has nothing to do with $(a,b)$. --barto (talk) 16:31, 23 April 2017 (EDT)
You're not alone, nobody likes the \left...\right. :-) OTOH I personally do prefer the extra gap before the brackets. This is one area where not everybody is going to be happy.
Oh yeah -- I was actually taught $\gcd \left\{ {a, b}\right\}$ because "it doesn't matter what order the operands go in". There are (generally unresolved) debates about the general wisdom of using set notation for such argument lists throughout the talk pages of $\mathsf{Pr} \infty \mathsf{fWiki}$. --prime mover (talk) 16:38, 23 April 2017 (EDT)
I imagine. What was the motivation to begin to use set notation, except the fact that we can? Does a certain author use this? I don't like it neither, because it hides things like $\gcd(a,b,b,a,b)=\gcd(a,b)$ (and not only $\gcd(a,b)=\gcd(b,a)$). Also, in general rings (that are not $\Z$ or polynomial rings over fields), $\gcd(a,b)$ becomes the ideal $(a,b)$, and then we use round brackets and not set notation for obvious reasons. --barto (talk) 16:50, 23 April 2017 (EDT)
I think it came from my M203 course in my MMath (OTOH might have been the Number Theory module). Didn't much like it, but thought that was the way it should be done. That was the same course that liked $]a, b[$ for an open interval, which I really didn't like.
In general we are trying to use the most up-to-date notation we can find which is not too specialised, trying at the same time to pick notation which is as unambiguous as possible, even if this means not using the most conventional notation. Hence the need to define the notation when it is being used: "where $a \mathrel \backslash b$ denotes that $a$ is a divisor of $b$" and so on. --prime mover (talk) 16:58, 23 April 2017 (EDT)
I think $\gcd\{a,b\}$ is more ambiguous than $\gcd(a,b)$. --barto (talk) 08:40, 28 April 2017 (EDT)
As long as we're consistent don't care what we use. We are already using $\gcd \left({a, b}\right)$, so. --prime mover (talk) 11:27, 28 April 2017 (EDT)
Okay. I try to make it a priority to create new content and not to discuss tangential issues too much, but sometimes I can't resist :) Part of the job is making proofwiki user-friendly and attractive. --barto (talk) 11:50, 28 April 2017 (EDT)
It's more like this: we have already evolved a style and a structure which has proved to work. We have evolved a notational convention which we believe is as good as any other, which has proved adequate. If there is a choice of notations to use, some will prefer one style, some will prefer another. A colossal amount of the time spent on this site is in refactoring and rework, and we really, really, really don't want to spend a lot of time doing an unnecessary package of work purely because a different way looks as though it is "better" without a solid reason to believe that it will be better.
My belief is that it is user-friendly and attractive. --prime mover (talk) 12:43, 28 April 2017 (EDT)
I hesitated between writing 'make' or 'keep' user-friendly, should have taken the other one :) As regards page lay-out, conciseness, coverage and especially the self-containedness of the pages and the omnipresence of links you've certainly done a great job so far. I mainly see room for improvement in the search function. --barto (talk) 12:56, 28 April 2017 (EDT)


Seriously how many redirects to Definition:Infimum of Set/Real Numbers do we need? We already have one: "Definition:Infimum of Subset of Real Numbers" which should be adequate. One of the things that another contributor to this site is keen on is not proliferating redirects (don't know why but he's the boss). So unless you have a really good reason for having them, we might want to rethink this latest strategy. --prime mover (talk) 18:03, 24 April 2017 (EDT)

Okay, I admit that was exaggerated. I'm curious though as to what the reason is to not like redirects. I can think of one reason, which is that it clutters search results. Redirects may become less needed if the search function recognizes spelling mistakes/variants, as on Wikipedia. Not sure what it takes to allow that. --barto (talk) 18:17, 24 April 2017 (EDT)
In this context "Definition:Infimum" takes you to the master page, and in this context you are then able to navigate with little difficulty to Definition:Infimum of Set/Real Numbers. Then one does "What links here" and finds the go-to redirect, which one can then use, and it is a specifically stated title: it's the infimum of a subset of the real numbers.
I contend that Infimum (Real Numbers) and Infimum (Real Analysis) are not specific enough. There exists an infimum of a real function and/or real-valued function (I can't remember without checking) and it is not immediately obvious whether, for example, Infimum (Real Analysis) refers to Definition:Infimum of Set/Real Numbers or (ah, here we are) Definition:Infimum of Mapping/Real-Valued Function.
In all cases, unambiguity takes first place on the podium, understandability second, and consistency 3rd. --prime mover (talk) 18:58, 24 April 2017 (EDT)

Beware renaming

I see you renamed "Vector Space has Basis" to "Vector Space has Basis between Linearly Independent Set and Spanning Set" (sorry, I renamed it from "Between" to "between" better to reflect our house style), and then renamed the corollary to "Vector Space has Basis" -- but please beware of doing this, because of the danger of links to the original "Vector Space has Basis" now pointing towards the one you renamed it to.

Also note that the general structure of a MediaWiki page is such that pages whose name is of the form "(pagename)/(subpage)" then get a link on the page at the top to the parent page. This allows a convenient link, and an immediate way of referring back to the page which is its parent. So the old "Vector Space has Basis/Corollary" used to have a link to "Vector Space has Basis" at the top. This new "Vector Space has Basis" page no longer has this link back to "Vector Space has Basis between Linearly Independent Set and Spanning Set", which can be seen as being a subtle nuance that has now been lost.

I understand you have a vision for this site which is wider, more comprehensive and richer than that of those who first put this site together, but please beware that implementing that vision may compromise some of the carefully-thought-out decisions of the past. Yes I know this stuff is not all documented in the various help pages and instructions on how to build this site. This is something that stupidly I and colleagues had failed to anticipate when we wrote that stuff. --prime mover (talk) 02:11, 2 May 2017 (EDT)

Also, when you do rename, please update the links to the renamed page. You can find what they are by the "What links here" link at the left hand side on the menu -- but you need to wait a short while (a minute or so) for the internal MediaWiki database to update itself to show those links. --prime mover (talk) 02:15, 2 May 2017 (EDT)
... and finally, please remember to add that extra gap between sections so as to preserve consistency. An extra gap between sections improves the look. --prime mover (talk) 02:22, 2 May 2017 (EDT)

And another very important thing: you renamed "Linearly Independent Subset of Finitely Generated Vector Space" to "Size of Linearly Independent Subset is at Most Size of Finite Generator" without renaming its "/Proof n" subpages. Please please please, when you rename such a page, please tick the box to rename the subpages as well -- and then amend all links to all such subpages. This, I admit, is a pain in the arse, but if you really want the page renamed, please can you do the work to make sure everything remains consistent? I had plans to do other stuff this morning which I am no longer going to be able to do because I have to clear all this up. --prime mover (talk) 02:29, 2 May 2017 (EDT)

Yes, I understand completely. Apart from updating the links to the renamed pages, those things you mentioned, I didn't notice them, so I'm sorry. Normally I would tick that box to rename subpages, but this time I didn't notice there were any. Next time, you can just post on my talk page and leave the dirty work to me. I'm aware of all the work that has to be done, except this time I procrastinated it a bit and there were some things I just overlooked. --barto (talk) 07:55, 2 May 2017 (EDT)
No worries, I have gone through and done the updating (or at least, as much as I had time to this morning, I'm back to the day job now).
A suggestion (which I learned the hard way) is to rename pages one at a time. Rename one, clean it up, redirects and all, and only then go through and rename another one. --prime mover (talk) 08:17, 2 May 2017 (EDT)
Yes, makes sense. I was too enthusiastic. --barto (talk) 08:31, 2 May 2017 (EDT)

hang on a minute

Look I'm working on it, I said in the page for Baire Space that I'm working on it, please give me a minute fragment of a microsecond before jumping in, please? --prime mover (talk) 06:01, 5 August 2017 (EDT)

Sorry about that, but I was right in the middle of code development there, and we had an edit conflict.
Okay, I've finished now, feel free to tidy up the spacing if you can improve it. --prime mover (talk) 06:13, 5 August 2017 (EDT)

Outline of Proof

Hi, I'm clearing up my backlog of missed changes during a longer hiatus, and I see that you started on your "Outline of Proof" idea. I think this is really valuable and adds to the understanding.

I also have the feeling that many a Finish template can be used to construct at least outlines of proofs, which is better than just Finish or Stub being there.

One thing to think about is how we are going to structure this in a way that it works with multiple-proof transclusions. Because then we would need some crafty heading level play to provide each Proof # together with Outline #. Just something for your spare brain cycles to ponder on.

Otherwise, keep up the good work! — Lord_Farin (talk) 08:34, 20 August 2017 (EDT)

Thanks for the feedback. I don't know what to do with multiple proofs and outlines. Maybe some day the <section> tag will provide a solution. In the case of multiple and long proofs (such as for the PNT, I was thinking that an option would be to transclude only the outlines. --barto (talk) 08:56, 20 August 2017 (EDT)

More praise

As I saw some of your edits in the Help realm, I was compelled to checking them out. And it turns out they are great! Really clear, specific pages that help people to edit in a way that works.

Definitely a step up from my last round of refactoring from some years back (although I still like to think that was also a big improvement in the coherence department).

Great! — Lord_Farin (talk) 15:17, 24 August 2017 (EDT)

I'm sure it was, and some day I will say the same when someone else improves it even more :) Feel free to improve the writing. English is not my native language, so when I write about non-mathematical things like these I feel a bit handicapped. --barto (talk) 15:25, 24 August 2017 (EDT)

Out of office

I will be less active next year due to other occupations. I'm aware that I leave many of my projects unfinished. I will still try to respond to remarks about my contributions, but probably won't make any big changes. When I'm back, I'd like to focus on expanding the $\mathsf{Pr} \infty \mathsf{fWiki}$ community rather than creating new content. You can find some ideas to this end on my user page. --barto (talk) 15:36, 24 August 2017 (EDT)

Trusted user

About two weeks ago I made you a trusted user (a decision long overdue). This means you are able to carry out everything that is required for regular work on $\mathsf{Pr} \infty \mathsf{fWiki}$, including deleting pages.

I mention this with regard to Equivalent Definition of Ordering, where you placed a Template:Delete call. Happy editing :). — Lord_Farin (talk) 15:45, 5 September 2017 (EDT)

Yes, I noticed. Thanks, by the way. But it hasn't made me more bold, so I'm still very careful when I move or delete a page. --barto (talk) 16:15, 5 September 2017 (EDT)

Whitespace topic

Hi. I just wanted to draw your attention to my remarks on your efforts regarding the whitespace convention on the main talk page. In particular it would be appreciated if the new convention (regarding onlyinclude) is not put into effect until at least a chance to respond (in particular, to disagree) has had its place.

In similar vein, I note the move to start omitting the double blank lines before headings. This currently breaks display uniformity until the jQuery script has been implemented into common.js.

I appreciate the devotion you have towards making ProofWiki better, but please make sure to leave the site in a consistent state after each of your quantum leaps.

In summary, please regard the above as a call to 1. avoid unilateral movement (particularly in the style domain); and 2. ensure changes are phased in a way that ensures consistency at all times. — Lord_Farin (talk) 15:48, 10 September 2017 (EDT)

All right. --barto (talk) 15:54, 10 September 2017 (EDT)
It seems that the above points need reiteration. I see a lot of unilateral decisions in the past hours. I draw your attention to the fact that this is not the way we work over here. I don't care how relentless your quest is, but currently it seems that the one "tyranny" (in your words) has been replaced by your tyranny. Please take some time to reflect on your actions and how much effort it would have been to logically explain what you do. Currently not every page is in consistent state because you are doing too many things at once. I know that there is work to be done, but it's not getting better by mixing up all the different tasks at once.
So please step back and explain clearly what decisions you have been making under what motivation with which end goal in mind. And then we can discuss whether or not all that was a good way to achieve the end goal to begin with. — Lord_Farin (talk) 08:45, 12 November 2017 (EST)
I'm sorry if I introduced whitespace inconsistencies.
The idea is to make templates more meaningful, so that one can choose a specific task to work on. (e.g., reviewing if a certain axiom is needed). (Some templates still need to be created indeed.) I'll expand on this at the main talk page.
The absence of feedback on recent proposals made me do it without stating the intentions first. I'll take care do it in the reverse order from now on. --barto (talk) (contribs) 10:02, 12 November 2017 (EST)

Yes please. And please do note that not only were there whitespace inconsistencies, but also image sizing, nonexistent templates, outright nonsense produced by calling a different template with the same input.

And I'm not even mentioning the breaking of naming tradition by introducing lowercase word separation all over. I'm willing to discuss anything, but not like this.

The biggest problem with all the above was that it was done in a cluttered mess that nobody can make sense of as separate initiatives afterwards.

Please consider that other users may have a day job or many other occupations to attend to, so that replying to comprehensive proposals might take more time than a few hours or a day or two. — Lord_Farin (talk) 10:14, 12 November 2017 (EST)

Please finish what you start

I notice a lot of work developed by you (definitions mainly) that leave so many redlinks it makes each page look like an accident in a guillotine factory. Yes I know I'm not blameless here myself (leaving a lot of unfinished proofs behind me) but please try and make sure that when you develop a body of work that you make some attempt to define the concepts from the bottom up.

It would also be greatly appreciated if you would start to make an effort to write your pages in house style. I'm fed up of clearing up after you. I have better things to do, quite frankly, and it demotivates me. --prime mover (talk) 17:19, 18 February 2018 (EST)

House style

Seriously, do you actually have a good reason for not bothering to follow house style? --prime mover (talk) 19:35, 9 March 2018 (EST)

I wrote something at Talk:Main Page#Two comments on brackets in MathJax. Regarding refactoring of multiple definitions, I may not do so right away when the broader page structure and the order of the definitions needs more thought. The unfinished definition page then allows to write a bit and get a better picture of what it should look like. --barto (talk) (contribs) 06:37, 18 March 2018 (EDT)
Yes I read your comments, and I see your opinion on the matter, but it is what it is. I don't like many of the house rules in Wikipedia (in particular the arbitrary way stuff just gets deleted without reason), but I live with it because those are the rules and it cramps my style to be barred for disobeying. --prime mover (talk) 07:51, 18 March 2018 (EDT)

Representable vs Hom

I did some research and took over your proposal to switch to "Hom Functor". I think I was reasonably complete merging the stuff, please check. Also, please be advised that there is some standard usage for elements of a category, notably we try to keep an intuitive distinction between categories ($\mathbf C$), objects ($C$) and morphisms ($f$). Functors go by $F$ as per literature standard. Please adhere so that the average reader is not confused. Or object on good grounds, but then accept that there is work to be done, and schedule accordingly (at the least we should formalise a standard and start flagging stuff with Tidy). — Lord_Farin (talk) 16:26, 19 March 2018 (EDT)

Last warning

After spending an inordinate amount of time completely changing vast areas of the look and feel of this site's templates, and giving us more and more ever more stringent hoops to jump through, you can't even be bothered to follow the guidelines for these things that you yourself have set up.

I can think of the following reasons for your behaviour:

a) You are too stupid to learn.
b) You are being deliberately contrary and confrontational for the sake of it.
c) You are a child who does not know any better.
d} You are attempting a takeover bid on behalf of a hostile power (that shower of ordure Stackexchange, probably).

There may be other reasons but I can't think of any.

The only solutions are:

a) To block you, so your disruptive actions compromise the structure of $\mathsf{Pr} \infty \mathsf{fWiki}$ no longer.
b) For you to change your ways.

Changing your ways, in this context, means:

a) Adhering the following rules:
i) Using the required left-right delimiters complete with braces: \left({ ... }\right) and not (...) everywhere. (Set up a hotkey, if you know how.)
ii) Using spaces between logical entities, in the standard style, inthesamewayyouwouldifyouweretowriteinnaturallanguage. (EDIT: Actually, I see you have already picked up on that. Fair play.)
iii) No more definition pages, including redirect pages, unless you can find them in a published hard-copy source work, and to add a citation to that source work as a page footer. Too long have you got away with this, and I am seeing that a lot of what you are posting is rubbish.
b) Making use of the templates that you yourself have insisted that we use, in places where it is appropriate to use them. Cases here are TFAE and the Example categories. (Okay, so maybe not all the templates were written by you, but you have seen examples of their use, I expect it to be no more than common courtesy for you to use them on your new pages.

Please respond to the above by tomorrow. If your response is inadequate, you will be blocked. --prime mover (talk) 05:27, 25 March 2018 (EDT)

Before the above warning and subsequent actions are attributed to the tension existing between the two of you, let me add that I have on several occasions had similar experiences, where also non-TeX-related recommendations and best practices were not followed up. It seems that you have been purely interested in making ProofWiki what you want it to be, instead of taking into account its status as a community effort. This is regrettable and therefore I support the gist of the warning above.
Lastly it be noted that there were 5 days between the warning and the blocking, in which time you have made edits to the site but not addressed the concerns at hand.
Above considerations mean that I have no reason to disagree with the resulting actions taken. This is sad, because despite all the disputes, you have advanced ProofWiki in many areas and cleared up long overdue tasks. It was therefore not an easy decision but nonetheless the block has my support. You are still able to edit this page so please feel free to address the points raised. — Lord_Farin (talk) 12:30, 1 April 2018 (EDT)
Thanks for the reply; I didn't know I can still edit this page. Let me say that I find part of the warning rude and offensive, and it includes an ultimatum for me to agree with a viewpoint in an ongoing(...) dialogue at main talk. I hope that it does not come as a complete surprise that I'm reluctant to reply to it. (And I figured that commenting on specific talk pages will be more helpful.) It has crossed my mind before, that communication is perhaps the most fundamental aspect in which the ProofWiki community (its policies?) can improve, in favor of overall contributor satisfaction.
Am I unwilling to discuss policies? Of course not. Am I unwilling to make compromises? No, in fact my view on this project has converged a lot towards the mainstream one, over time. In particular, contributing for me has nothing to do with pride, "power", "putting a personal stamp". (Some words that have been dropped; don't take any of this personally.) There are suggestions I have abandoned because they turned out to be arguably bad, others that are still awaiting feedback. But please do note that I also listen to the voices of past contributors who, it appears, and it saddens me deeply, have abandoned hope in situations similar to this.
"ultimatum for me to agree with a viewpoint in an ongoing(...) dialogue at main talk" -- no, this is not a "viewpoint", it is a house style rule. There are plenty of these on a number of wikis around the internet. This is one such wiki. As such, a "house style rule" is no more a "viewpoint" than, for example, a rule that says you need to dress and deport yourself in a certain way in certain public places. You may consider it a viewpoint, but turning up to a nightclub wearing certain footwear can cause you to not be allowed in. --prime mover (talk) 17:35, 6 April 2018 (EDT)
In order to not let the speaking in generalities make us forget what it is about (and it's too easy to end up exaggerating or understating), let me get back to some specific issues. A few days earlier I've seen some comments hinting at other issues, that haven't yet received the attention they merit: I think of unsourced definitions and pages relying on incomplete work. (There's also an ongoing thread about redirects.) So I take it that there is more than a) and b) that led us here. One cannot expect all of that to be solved in a week time, especially with a limited number of active users to help in making decisions. There's too much to say and this is not the place, so here are a few quick thoughts:
  • b) I find the category templates difficult with all the links and transclusions; I haven't yet studied the most recent changes. The TFAE situation is the one discussed here I assume.
You actively encouraged the use of certain of the category templates, and made a number of changes to these templates -- and now you just decide you're not going to bother with them. As to finding it "difficult with all the links and transclusions" -- well, you did do a lot of this work, so to say you find it "difficult" is disingenuous. --prime mover (talk) 17:35, 6 April 2018 (EDT)
  • Regarding unsourced definitions, there is a slight contradiction. On the one hand one doesn't want to risk having wrong definitions, so it makes sense to have a source for each. On the other hand, I learned that the aim is to document modern tendencies, which happen to be found primarily online, in articles or preprints, and in lecture notes that are impossible to reference. (I welcome any questions about where I got the things I wrote.)
As you were informed, we should not have to "ask questions" -- sources (specifically for definitions, but optionally for proofs) should be documented. There are many usages that you can find on line where the usage is an ad hoc one-off used for the sole purpose of allowing for an elegant exposition of a proof. But more to the point, many of the definitions being added are instances of a general definition, which you have put into a disambiguation page despite having been requested to consider the overall design strategy of transclusion into a larger scheme. Disambiguation is specifically for more-or-less unconnected uses of a concept, and not as a lazy catch-all for delicately interlinked and co-dependent pages which merit the technique of transclusion. But no, you find transclusion too "difficult" and so our requests for this to stop are continually ignored. --prime mover (talk) 17:35, 6 April 2018 (EDT)
  • Pages relying on not yet existing pages: Yes, it's good to limit them, in line with ProofWiki's goals. But not all theorems in, say, elementary set theory or linear algebra are already there, and when writing a proof it's not practical to make sure first if all elementary lemmas are there already, and dig deeper and deeper. Also, one may simply be unable to find the page, but somebody else who sees the red link may know where it is.
(I am busy lately and may take a while to respond.) --barto (talk) (contribs) 07:05, 4 April 2018 (EDT)
In all your contributions, the vast majority are these abovementioned fragmentational definitions, which have no use in any proofs (except maybe the occasional equivalence proofs) and no notion of the context in which they are used. Assembling this stuff is going to be an onerous chore, which will give little benefit. The name of the site, as I have said elsewhere, is $\mathsf{Pr} \infty \mathsf{fWiki}$, not DefinitionWiki, not DisambiguationWiki, and not RedLinkWiki.
As a consequence of your disinclination to adhere to the evolved philosophy of $\mathsf{Pr} \infty \mathsf{fWiki}$, it appears that there are fundamental incompatibility issues here. We are trying to build something with a specific structure which has evolved into something with a distinct shape, which we would like to continue as it is, because it works. --prime mover (talk) 17:35, 6 April 2018 (EDT)

Getting to the gist of it, it seems the above can be summarised as follows.

You (Barto):

  • claim benevolent intent;
  • claim openness for discussion regarding policies;
  • claim to have acted on certain reasons when critiqued for non-adherence to policies.

At the same time, we:

  • find new policies being taken into effect before any discussion resolves in a satisfactory way;
  • fail to find requests for clarification (in case of category templates)
  • fail to find general inquiries about how to unify the desire to incorporate recent material with the requirement for sourced material (for definition pages);
  • fail to find expressions of your problem that building blocks are missing;
  • observe continued non-adherence to the more maintenance-heavy policies existing on $\mathsf{Pr} \infty \mathsf{fWiki}$, omitting even the simplest steps of flagging things for review.

The above observations subsequently lead to the following as my impression.

Namely, that you have certain visions about what $\mathsf{Pr} \infty \mathsf{fWiki}$ could be; visions which have huge implications in how the site is built up in many essential ways. I personally think this is a good thing. However, what seems to be continually missing is the patience and respect to discuss these changes until a consensus is reached (in some aspects, to have the discussion at all); additionally, to ensure consistency in other parts of contribution. Time and again you have ignored the requests to prepare certain changes in user space ("sandbox"), to demonstrate benefits, ultimately, to convince others. When one proposes to change the status quo, the onus lies on the one proposing the change to convince others to satisfactory extent. When consensus cannot be reached, a completely new alternative may need to be developed that avoids a compromise on essential aspects. I agree that such a process may be cumbersome, but to cut it short is a way to destroy what little value has been accumulated in this website over the years. The task to organise the thousands of textbooks and other materials on mathematics into a congruent whole is monumental. We will fail if we do not meticulously strive for uniformity. And ultimately, when forced to choose between losing a highly valued contributor and compromising $\mathsf{Pr} \infty \mathsf{fWiki}$'s end goal, I have only one option. Rather than continuing to use that option, however, I would like that the conflict is avoided and we can work together profitably. Maybe through automation. Maybe through collaborative workflows. Maybe through endless discussion. Maybe through ways I cannot think of right now. Surprise us. Convince us. — Lord_Farin (talk) 13:10, 8 April 2018 (EDT)