[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733352#comment-16733352 ] Jan Høydahl commented on SOLR-12018: Now that we move to Gitbox we'll be able to merge PRs directly from GH, so perhaps the time is ripe for adding this link now? > 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.6, 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506542#comment-16506542 ] Jan Høydahl commented on SOLR-12018: 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. Example for the Analyzers page: [https://github.com/apache/lucene-solr/blob/master/solr/solr-ref-guide/src/analyzers.adoc] > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506117#comment-16506117 ] Cassandra Targett commented on SOLR-12018: -- bq. I guess the Apache one will eventually come back online I honestly don't think it's going to. We were apparently the only project officially using it, so I think it will sit on the backburner forever. I had an idea that maybe we should replace it with something like an annotation system where people can comment on specific lines or paragraphs instead of the entire page. Five minutes of vague and interrupted "research" led me to https://web.hypothes.is/, which appears to share our values - free, nonprofit, open source - but I really haven't thought about it more than just looking at their website for a couple minutes and watching a demo (which looked cool, but the devil is in the details). > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506076#comment-16506076 ] Jan Høydahl commented on SOLR-12018: We could setup our own with [https://github.com/adtac/commento] but I guess the Apache one will eventually come back online > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504858#comment-16504858 ] ASF subversion and git services commented on SOLR-12018: Commit 377da9ca94871e651b8251e7029e06791c60c594 in lucene-solr's branch refs/heads/branch_7_4 from [~ctargett] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=377da9c ] SOLR-12018: add committer attribution > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504854#comment-16504854 ] ASF subversion and git services commented on SOLR-12018: Commit 9d48bd9d2a980c99c2277a000c5bd955e2d01c2c in lucene-solr's branch refs/heads/branch_7x from [~ctargett] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9d48bd9 ] SOLR-12018: add committer attribution > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504851#comment-16504851 ] ASF subversion and git services commented on SOLR-12018: Commit 8cb6e3d3c88182f1fdc3fc4f6de640db13a88745 in lucene-solr's branch refs/heads/master from [~ctargett] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8cb6e3d ] SOLR-12018: add committer attribution > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504814#comment-16504814 ] Cassandra Targett commented on SOLR-12018: -- I've removed it for 7.4 and the future; leaving this open until I have time to deal with older versions that are still broken. > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504809#comment-16504809 ] ASF subversion and git services commented on SOLR-12018: Commit 920cefd2fa06d7b3449d2d7ebcdf5d9830a0ad05 in lucene-solr's branch refs/heads/branch_7_4 from [~ctargett] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=920cefd ] SOLR-12018: Remove comments.apache.org integration for the Ref Guide > 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 > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504805#comment-16504805 ] ASF subversion and git services commented on SOLR-12018: Commit b7881e45ddbfddeba81c5f6eca2b97a37dc9b775 in lucene-solr's branch refs/heads/branch_7x from [~ctargett] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b7881e4 ] SOLR-12018: Remove comments.apache.org integration for the Ref Guide > 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 > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504798#comment-16504798 ] ASF subversion and git services commented on SOLR-12018: Commit 6e880352976e15f876fa2b3c578a563c4d26cd2d in lucene-solr's branch refs/heads/master from [~ctargett] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6e88035 ] SOLR-12018: Remove comments.apache.org integration for the Ref Guide > 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 > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503457#comment-16503457 ] Cassandra Targett commented on SOLR-12018: -- I've attached a patch that completely removes the comments JS and related CSS from the Ref Guide, I'll commit it in a little bit. > 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 > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494055#comment-16494055 ] Cassandra Targett commented on SOLR-12018: -- INFRA-15947 has had no progress and I finally got some confirmation that it's very much back burner, so it doesn't make sense to wait. I'll pull the comments code out of the pages so we stop publishing pages with a broken comments section. I'll also figure out what to do about existing pages that are all broken - either republish or just do surgery on the HTML. > 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 > Attachments: RefGuideCommentsBroken.png > > > 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
[jira] [Commented] (SOLR-12018) Ref Guide: Comment system is offline
[ https://issues.apache.org/jira/browse/SOLR-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373379#comment-16373379 ] Erick Erickson commented on SOLR-12018: --- +1 to (1). I'm sure you have one or two other things on your plate that would be a better use of time ;) > 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 > Attachments: RefGuideCommentsBroken.png > > > 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
