Difference between revisions of "Free Software Directory talk:Backlog active"

From Free Software Directory
Jump to: navigation, search
(→‎Column width: indent for clarity)
m (taking out asterisks)
 
(21 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
==Upgrade history==
+
== Specifications ==
  
−
It seems unprobable that the following issues appeared on their own, most probably MediaWiki extensions got updated and some things do no longer work as before. Would be good to know the history of upgrades to identify changes that has been made and how they have affected this wiki. &nbsp;«&nbsp;[[User:Saper|Saper]]<span style="font-size: 70%">&nbsp;//&nbsp;</span>[[User talk:Saper|@talk]]&nbsp;»&nbsp; 10:58, 27 January 2018 (EST)
+
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)
  
−
==Prioritized issues==
 
−
The '''Log''' sections are used to track edit revisions so they can be reverted if necessary.
 
  
−
===Link text===
+
Edit by User9
−
[[User talk:Adfeno|Adfeno]]:
 
−
* I specifically need your help to fix all issues at https://directory.fsf.org/wiki/Free_Software_Directory:Backlog#Semantic_Forms. --David Hedlund (talk) 17:47, 14 January 2018 (EST)
 
  
−
====IRC (temporarily fixed)====
+
* 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.
−
 
 
−
* I attempted to fix this but it seems that something is interfering with the formatting. Strangely enough, if I make a simple page without the form, and use the IRC template, it works as expected. I don't know if this is the case, but I think there is some template interfering.--[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 23:23, 26 January 2018 (EST)
 
−
* As requested in #fsf IRC channel, here is the comment I made there, describing my studies so far:
 
−
** It basically involves three templates (it might involve more, but I only researched three so far) {{tl|Print entry}} {{tl|Entry}} and {{tl|Show}}. There is a fourth one ({{tl|IRC}}) but I think we might be able to replace it ({{tl|Print entry}} calls it, so instead of calling {{tl|IRC}}: we can take the code from it and insert in the caller template).
 
−
::: I think that #replace will just mask the underlying issue. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 10:49, 27 January 2018 (EST)
 
−
** I think there is so far the following possibilities:
 
−
**# an issue between the templates used;
 
−
**# an issue with the <code>#ask:</code> queries and the <code>template</code> result format;
 
−
**# we have reached a setting limit that makes the formatting not work (perhaps a limit on the <code>template</code> result format, although I have tried to remove the call to {{tl|IRC}} but it didn't work, we might have to make tests by simplifying the <code>template</code> result calls even further to see if this is indeed the problematic setting);
 
−
**# an issue with the "IRC [level name]" properties when setting (<code>#set:</code>) or their query and display.
 
−
*: I think we can make use of <code>#nowiki</code> or <code>#-</code> display parameters when querying for the <nowiki>"IRC [level"</nowiki> properties of an entry (this is queried for in {{tl|Show}}) in order to take the property value in raw (example: <code>irc:chat.freenode.net/fsf</code>) but then we will need to change either {{tl|Print entry}} or {{tl|IRC}} (the first one is the problematic, so I recommend to test with it first) so that it removes <code>irc:</code> but also allows any other <code>:</code> (because the URL scheme allows port numbers).
 
−
*: --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 08:47, 27 January 2018 (EST)
 
−
* While MediaWiki understands IRC URLs very well, Our copy Semantic MediaWiki gets confused if a property of type <code>URL</code> has a protocol different from HTTP, this problem also happens if the property definition/setting is invisible (using <code>#set:</code>), but in all cases it works as expected if the protocol is HTTP. I don't know if this is a bug in Semantic MediaWiki (or MediaWiki) but this affects at least our copy of it. An example of the issue with IRC property can be seen in: https://directory.fsf.org/wiki?title=Free_Software_Directory:Sandbox&oldid=48884 --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 11:32, 27 January 2018 (EST)
 
−
* As of SMW 2.5.1, http https and ftp URL schemes will be printed with double slashes, all other without: https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/568d058ea68859d134654a959001ba0739c781e3/includes/dataitems/SMW_DI_URI.php#L68-L70 &nbsp;«&nbsp;[[User:Saper|Saper]]<span style="font-size: 70%">&nbsp;//&nbsp;</span>[[User talk:Saper|@talk]]&nbsp;»&nbsp; 12:49, 27 January 2018 (EST)
 
−
=====Log=====
 
−
* [https://directory.fsf.org/wiki?title=Template:Print_entry&diff=48853&oldid=48834 Adding <code>#-</code>] didn't seem to help. &nbsp;«&nbsp;[[User:Saper|Saper]]<span style="font-size: 70%">&nbsp;//&nbsp;</span>[[User talk:Saper|@talk]]&nbsp;»&nbsp; 08:54, 27 January 2018 (EST)
 
−
** We unfortunately need a function to remove <code>irc:</code> in order to use <code>#nowiki</code> or <code>#-</code>.--[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 09:35, 27 January 2018 (EST)
 
−
* Removed dependency on {{tl|IRC}}: https://directory.fsf.org/wiki?title=Template:Print_entry&oldid=48860
 
−
* Use <code>#replace</code> in IRC URL properties to get the address correctly: https://directory.fsf.org/wiki?title=Template:Print_entry&oldid=48889 --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 11:59, 27 January 2018 (EST)
 
−
* Use <code>#nowiki</code> in the query for IRC URL properties to pass the property value to {{tl|Print entry}}: https://directory.fsf.org/wiki?title=Template:Show&oldid=48890 --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 11:59, 27 January 2018 (EST)
 
−
 
 
−
====Multiple software categories====
 
−
* (analysis) This issue occurs when multiple items in one software category are selected in the form. The property value seems to contain space-separated values. But {{tl|Print software category}} seems to use <code>[[:mw:Extension:Page_Forms/Page_Forms_and_templates#arraymap|#arraymap]]</code> with a separator <code>,</code> to split values.
 
−
* [https://semantic-mediawiki.org/wiki/Help:Using_a_space_to_separate_multiple_values_in_set/subobject Using a space to separate multiple values in set/subobject] from SMW website cmay or may not be helpful
 
−
 
 
−
=====Log=====
 
−
* It didn't help to edit <nowiki>{{</nowiki>[[Template:Print_software_category|Print_software_category]]<nowiki>}}</nowiki> and replace comma with <nowiki>&#32</nowiki> in <nowiki>{{#if:{{{15|}}}|{{#arraymap:{{{15}}}|,|xvarx|<li>[[Category/Interface/xvarx{{!}}Interface:xvarx]]</li>|}}|<nowiki/>}}</nowiki>, see https://directory.fsf.org/wiki?title=Template:Print_software_category&diff=48880&oldid=48746
 
−
 
 
−
===Column width===
 
−
* https://lists.gnu.org/archive/html/directory-discuss/2016-05/msg00005.html. --David Hedlund (talk) 18:59, 14 January 2018 (EST)
 
−
* (analysis) Edit {{tl|Print entry}}:
 
−
** Try to remove "width: 350px" from <code><nowiki><div style="float:left; width:350px; margin: 2px 4px 0px 4px;"></nowiki></code>
 
−
** Also remove "width: 300px" later. Both widths could be replaced by percentages (e.g 60% and 30%).
 
−
*::&nbsp;«&nbsp;[[User:Saper|Saper]]<span style="font-size: 70%">&nbsp;//&nbsp;</span>[[User talk:Saper|@talk]]&nbsp;»&nbsp; 13:35, 27 January 2018 (EST)
 

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.

Retrieved from "https://directory.fsf.org/wiki?title=Free_Software_Directory_talk:Backlog_active&oldid=85548"