- Issue created by @xjm
- ๐บ๐ธUnited States xjm
Questions regarding the PHP versions:
- Do we need them at all?
- Can we remove the tags for EOL PHP versions?
- Can we at least remove the tags for really, really EOL PHP versions?
Similarly, while we can debate whether to keep around tags pertaining to D7, we definitely should remove the ones pertaining to D6 and earlier. All they do is make the page harder to read and clutter up the autocomplete. The historical issue data will still be there.
- ๐บ๐ธUnited States xjm
I guess there are two questions: Whether to remove the tags from the list (easy), and whether to actually delete the old tags (harder, but still a case to be made, because string references will still exist on the issues). We can keep the scope of this issue to the first, but the second might become relevant in the GitLab issue migration.
- ๐ฎ๐นItaly apaderno Brescia, ๐ฎ๐น
(I apologize: I read the issue as removing the issue tags, not removing them from the documentation guide.)
- ๐บ๐ธUnited States xjm
Note that it is a "magic" documentation page that gets parsed by d.o, which is part of why it's not just something anyone can or should edit by themselves.
- ๐บ๐ธUnited States xjm
Although, apparently the page is now actually generated as a view, not parsed anymore. So I think this is the correct queue.
I do have access to administer the tags myself, but again, I don't think I should make unilateral decisions about them.
- ๐บ๐ธUnited States xjm
Clarify IS that this is about removing from the list of "special" tags (with descriptions), not deleting them entirely (which would be a possible followup)
- ๐ฎ๐นItaly apaderno Brescia, ๐ฎ๐น
The view is defined in the features/drupalorg_documentation/drupalorg_documentation.views_default.inc file.
Deleting issue tags seems simpler than filtering them out from that view's output. If there are semi-rude terms, should not those be edited or deleted directly?
- ๐บ๐ธUnited States xjm
@avpaderno, I don't think the list of tags is hard-coded; it's just based on what has a description AFAIK. I'm not proposing altering the view; just changing the specific tags we list.
- ๐ฎ๐นItaly apaderno Brescia, ๐ฎ๐น
I know the tags are not hard-coded, but if you want to avoid showing some tags from that view, without editing them, that is only possible by changing the view.
If editing the issue tags to remove the description is fine, then editing the view is not necessary. - ๐ฎ๐นItaly apaderno Brescia, ๐ฎ๐น
(The view shows only issue tags whose description is more than five characters.)
- ๐ฎ๐นItaly apaderno Brescia, ๐ฎ๐น
harder, but still a case to be made, because string references will still exist on the issues
When an issue tag is deleted, the view listing all the issues using it will show no issues. The issues will still see a comment showing the issue tag has been added, but that comment will not link back to the issue tag. That should not be worse than keeping the issue tag and have a view showing all the issues using it.
- ๐ณ๐ฟNew Zealand quietone
As I understand it then, a special tag can be removed from the view simply by removing the description. But, are there tags where the description is historically useful but is no longer needed in the view?
I suggest that the PHPX.Y and the 'Needs backport to X' are self explanatory and the description can be removed. Are there 'domain owners' for the these tags?
- ๐ญ๐บHungary Gรกbor Hojtsy Hungary
Is there a list of tags that is proposed to be changed?