Sorry for reverting all of your edits to AUR. I initially tried to just fix them up a bit, but in the end they were just duplicating information from git and other sections of the AUR article. Your version was definitely easier to read for someone who has no git experience and wants to contribute to the AUR, but Help:Style#Hypertext metaphor forbids that kind of duplication. Unfortunately it is the nature of AUR4 that contributors must be familiar with git, and git is the appropriate place to learn about that. Silverhammermba (talk) 19:55, 5 March 2016 (UTC)
- The point is that transitioning to AUR4 is not just a matter of educating new users: existing users must unlearn the old process and adjust to the new one. I think having a clear and consise example, as I laid out, will accelerate progress. Can't an exeption be made?
- —This unsigned comment is by Quequotion (talk) 20:38, 2016 March 5. Please sign your posts with ~~~~!
- No, I'm not kidding. Arch users are expected to read and learn about anything they don't understand (see Arch Linux#User centrality), so AUR contributors who don't know git are expected to be able to click the link to the git article and read about it there. Things like setting up remotes and a text editor for commit messages are not AUR-specific and are already explained in detail in git. Duplicating them on the AUR article--while easier to read for certain users--increases maintenance if git is updated, decreases readability if the user already knows git and just wants the AUR info, and discourages unfamiliar users from reading the main article (which explains things better).
- If you take a look around the wiki you will see plenty of cases where clear and concise examples are forgone in favor of a link to the main article.
- Silverhammermba (talk) 22:25, 5 March 2016 (UTC)