lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (SOLR-12018) Ref Guide: Comment system is offline
Date Thu, 22 Feb 2018 18:58:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cassandra Targett reassigned SOLR-12018:
----------------------------------------

    Assignee: Cassandra Targett

> Ref Guide: Comment system is offline
> ------------------------------------
>
>                 Key: SOLR-12018
>                 URL: https://issues.apache.org/jira/browse/SOLR-12018
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Cassandra Targett
>            Assignee: Cassandra Targett
>            Priority: Major
>
> The Ref Guide uses comments.apache.org to allow user comments. Sometime in December/early
January, it was taken offline. 
> I filed INFRA-15947 to ask after it's long-term status, and recently got an answer that
it an ETA is mid-March for a permanent INFRA-hosted system. However, it's of course possible
changes in priorities or other factors will delay that timeline.
> Every Ref Guide page currently invites users to leave comments, but since the whole Comments
area is pulled in via JavaScript from a non-existent server, there's no space to do so (see
attached screenshot). While we wait for the permanent server to be online, we have a couple
of options:
> # Leave it the way it is and hopefully by mid-March it will be back
> # Change the text to tell users it's not working temporarily on all published versions
> # Remove it from all the published versions and put it back when it's back
> I'm not a great fan of #2 or #3, because it'd be a bit of work for me to backport changes
to 4 branches and republish every guide just to fix it again in a month or so. I'm fine with
option #1 since I've known about it for about a month at least and as far as I can tell no
one else has noticed. But if people feel strongly about it now that they know about it, we
can figure something out.
> If for some reason it takes longer than mid-March to get it back, or INFRA chooses to
stop supporting it entirely, this issue can morph into what we should do for an alternative
permanent solution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message