Difference between revisions of "Free Software Directory talk:Backlog active"
(Added note about the experiments made.) |
Usernumber9 (talk | contribs) m (taking out asterisks) |
||
| (56 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | == Specifications == |
| − | [[User | + | |
| − | * | + | Hi [[User:Adfeno|Felipe]], you seem determined to take care of the backlog. I'll leave you a couple of tips to prevent issues in future: |
| − | + | * respect at least the [https://directory.fsf.org/wiki?title=Template_talk:BacklogIssue&oldid=81569 preexisting specifications] in order to preserve the existing user experience, so the changes won't result in a downgrade. In particular, at any time the referencing system must continue to work in order to not break the existing remote links and produce new anchors using the same algorithm; | |
| − | * | + | * clarify in the documentation when the [[Free Software Directory:Single-page JS tracker]] will be used, so your current/future peers won't erroneously think it was arbitrarily discarded/replaced; |
| + | * rename the Single-page JS tracker to ''Single-page HTML5 tracker'' (or equivalent), as JS is implemented as an optional dependency and GNU uses JS as a pejorative attribute. Keeping the name, as much as the descriptions, as technical and neutral as possible is a wise idea; | ||
| + | * keep all the documentation of each template inside its discussion page, because neither you or the others can remember everything forever. Be verbose, add examples. If everyone knows how everything works, then everyone will be able to replace you when you are unavailable for whatever reason; | ||
| + | * you won't be able to avoid JS and HTML 5 forever. If you need to add some JS, add it. The only wariness is that you must ensure it is used only for ''optional/extended'' functionality or to enhance the existing user experience and of course don't include external scripts, keep all local as much as possible.<br> | ||
| + | Bye, keep up with the good work. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 04:38, 28 July 2021 (EDT) | ||
| + | |||
| + | |||
| + | Edit by User9 | ||
| + | |||
| + | * it would be nice to have a field that records/lists the 'last updated date' for each particular property of a page. Mayb not all fields could use this, but for example, I'm taking on the taks of updating the 'Accepts Cryptocurrency Donations' field for the FSD. There are over 16k entries in the FSD. So, when I look at a project and I see that it says it DOES NOT accept crypto donations, I ask myself whether I should verify that, whether it may have changed since this entry was last updated. If it was last checked and/or updated 6 months ago, that's pertinent info and will help me determine whether I should verify it again, or skip to a project that hasn't been verified or checked for, say 2 years. When I go and check if a project accepts crypto, if I see that the FSF is correct in that they DO or DON'T accept it, then it would be nice to be able to just somehow update that 'last updated date' or whatever and say it's verified to be the same, or that I changed it on that date. | ||
Latest revision as of 14:43, 3 September 2021
Specifications
Hi Felipe, you seem determined to take care of the backlog. I'll leave you a couple of tips to prevent issues in future:
- respect at least the preexisting specifications in order to preserve the existing user experience, so the changes won't result in a downgrade. In particular, at any time the referencing system must continue to work in order to not break the existing remote links and produce new anchors using the same algorithm;
- clarify in the documentation when the Free Software Directory:Single-page JS tracker will be used, so your current/future peers won't erroneously think it was arbitrarily discarded/replaced;
- rename the Single-page JS tracker to Single-page HTML5 tracker (or equivalent), as JS is implemented as an optional dependency and GNU uses JS as a pejorative attribute. Keeping the name, as much as the descriptions, as technical and neutral as possible is a wise idea;
- keep all the documentation of each template inside its discussion page, because neither you or the others can remember everything forever. Be verbose, add examples. If everyone knows how everything works, then everyone will be able to replace you when you are unavailable for whatever reason;
- you won't be able to avoid JS and HTML 5 forever. If you need to add some JS, add it. The only wariness is that you must ensure it is used only for optional/extended functionality or to enhance the existing user experience and of course don't include external scripts, keep all local as much as possible.
Bye, keep up with the good work. --LorenzoAncora (talk) 04:38, 28 July 2021 (EDT)
Edit by User9
- it would be nice to have a field that records/lists the 'last updated date' for each particular property of a page. Mayb not all fields could use this, but for example, I'm taking on the taks of updating the 'Accepts Cryptocurrency Donations' field for the FSD. There are over 16k entries in the FSD. So, when I look at a project and I see that it says it DOES NOT accept crypto donations, I ask myself whether I should verify that, whether it may have changed since this entry was last updated. If it was last checked and/or updated 6 months ago, that's pertinent info and will help me determine whether I should verify it again, or skip to a project that hasn't been verified or checked for, say 2 years. When I go and check if a project accepts crypto, if I see that the FSF is correct in that they DO or DON'T accept it, then it would be nice to be able to just somehow update that 'last updated date' or whatever and say it's verified to be the same, or that I changed it on that date.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.