[
https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506555#comment-16506555
]
Cassandra Targett commented on SOLR-12018:
------------------------------------------
bq. Another simple idea I had was to include a link to the GitHub version of
the page, from where the user (if he/she is logged in to GitHub) can click the
edit button (pencil icon), do the suggested changes and submit a PR directly
from that page
+1. I've seen it done and it wouldn't take much work at all. I think our GitHub
PR workflow is fundamentally broken (in the sense that we can't just merge the
PR from the GH interface, but instead have to download a diff or patch, etc.),
but it shouldn't stop us from making it easier for non-committers to contribute.
> 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
> Fix For: 7.4, master (8.0)
>
> Attachments: RefGuideCommentsBroken.png, SOLR-12018.patch
>
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
