[jira] [Commented] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379853#comment-17379853
 ] 

Rahul Singh commented on CASSANDRA-16536:
-

Mick, I think this was already posted.
https://cassandra.apache.org/blog/Cassandra-and-Kubernetes-SIG-Update-2.html


Rahul Singh

Chief Executive Officer | Business Platform Architect m: 202.905.2818 e:
rahul.si...@anant.us li: http://linkedin.com/in/xingh ca:
http://calendly.com/xingh

*We create, support, and manage real-time global data & analytics platforms
for the modern enterprise.*

*Anant | https://anant.us *

3 Washington Circle, Suite 301

Washington, D.C. 20037

*http://Cassandra.Link * : The best resources for
Apache Cassandra


On Mon, Jul 12, 2021 at 5:15 PM Michael Semb Wever (Jira) 



> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
> 
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: High
>  Labels: pull-request-available
> Fix For: 4.0.x
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG 
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309528#comment-17309528
 ] 

Rahul Singh commented on CASSANDRA-16536:
-

Done 

> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
> 
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: High
>  Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG 
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308847#comment-17308847
 ] 

Rahul Singh commented on CASSANDRA-16536:
-

PR updated 

[https://github.com/apache/cassandra-website/pull/39]

 

> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
> 
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: High
>  Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG 
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308807#comment-17308807
 ] 

Rahul Singh commented on CASSANDRA-16536:
-

acknowledged 

 

will make updates and do update the pull request

> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
> 
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: High
>  Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG 
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308226#comment-17308226
 ] 

Rahul Singh commented on CASSANDRA-16536:
-

Pull request at [https://github.com/apache/cassandra-website/pull/39]

 

 

> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
> 
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG 
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16536:

Attachment: image-2021-03-24-18-57-08-450.png

> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
> 
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
> Attachments: image-2021-03-24-18-57-08-450.png
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG 
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16536:

Description: 
We're getting another update up for the Cassandra & Kubernetes SIG 

 

[https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
 

 

  was:
We're getting a blog post out before/coinciding with Kubecon 2020. Content code 
is mostly ready 

 

 

[https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]


> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
> 
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0, 4.0-beta2
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG 
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16536:

Fix Version/s: (was: 4.0-beta2)
   4.0-beta5

> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
> 
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0-beta5, 4.0
>
>
> We're getting another update up for the Cassandra & Kubernetes SIG 
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16536:

Source Control Link:   (was: 
https://github.com/apache/cassandra-website/commit/ecb519dc1cb84477d1be604a0d88628911807001)

> BLOG - Post about Cassandra & Kubernetes - SIG Update #2
> 
>
> Key: CASSANDRA-16536
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Michael Semb Wever
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0, 4.0-beta2
>
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content 
> code is mostly ready 
>  
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2

[Rahul Singh (Jira)]

Rahul Singh created CASSANDRA-16536:
---

 Summary: BLOG - Post about Cassandra & Kubernetes - SIG Update #2
 Key: CASSANDRA-16536
 URL: https://issues.apache.org/jira/browse/CASSANDRA-16536
 Project: Cassandra
  Issue Type: Improvement
  Components: Documentation/Blog
Reporter: Rahul Singh
Assignee: Michael Semb Wever
 Fix For: 4.0, 4.0-beta2


We're getting a blog post out before/coinciding with Kubecon 2020. Content code 
is mostly ready 

 

 

[https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-15588) 4.0 quality testing: Cluster Upgrade

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-15588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202443#comment-17202443
 ] 

Rahul Singh commented on CASSANDRA-15588:
-

What's the acceptance criteria for a cluster? Also what versions need to be 
tested from.

> 4.0 quality testing: Cluster Upgrade
> 
>
> Key: CASSANDRA-15588
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15588
> Project: Cassandra
>  Issue Type: Task
>  Components: Test/dtest/java, Test/dtest/python
>Reporter: Josh McKenzie
>Priority: Normal
> Fix For: 4.0-beta
>
>
> We've historically had numerous bugs concerning upgrading clusters from one 
> version to the other. Let's establish the supported upgrade path and ensure 
> that users can safely perform the upgrades in production.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-16122) Blog / Docs - Create Cassandra on Kubernetes Content

[Rahul Singh (Jira)]

Rahul Singh created CASSANDRA-16122:
---

 Summary: Blog / Docs - Create Cassandra on Kubernetes Content 
 Key: CASSANDRA-16122
 URL: https://issues.apache.org/jira/browse/CASSANDRA-16122
 Project: Cassandra
  Issue Type: New Feature
  Components: Documentation/Blog, Documentation/Website
Reporter: Rahul Singh
Assignee: Rahul Singh


The Cassandra Kubernetes SIG met and determined that the next best outcome of 
the group is to create definitive documentation that the current contributors 
to the existing operators can get behind as a clear guide to Cassandra on 
Kubernetes that is published on the cassandra.apache.org site.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-16122) Blog / Docs - Create Cassandra on Kubernetes Content

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16122:

Description: 
The Cassandra Kubernetes SIG met and determined that the next best outcome of 
the group is to create definitive documentation that the current contributors 
to the existing operators can get behind as a clear guide to Cassandra on 
Kubernetes that is published on the cassandra.apache.org site.

 

Outline / Collaboration Google Doc : 
[https://docs.google.com/document/d/15sZhAL-m9-a-6iuWmXdyKxsGraaJY9M6_xf9Qj2gSw4/edit?userstoinvite=jim.dickin...@datastax.com&ts=5f5a72f7]
 

  was:The Cassandra Kubernetes SIG met and determined that the next best 
outcome of the group is to create definitive documentation that the current 
contributors to the existing operators can get behind as a clear guide to 
Cassandra on Kubernetes that is published on the cassandra.apache.org site.


> Blog / Docs - Create Cassandra on Kubernetes Content 
> -
>
> Key: CASSANDRA-16122
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16122
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Documentation/Blog, Documentation/Website
>Reporter: Rahul Singh
>Assignee: Rahul Singh
>Priority: Normal
>
> The Cassandra Kubernetes SIG met and determined that the next best outcome of 
> the group is to create definitive documentation that the current contributors 
> to the existing operators can get behind as a clear guide to Cassandra on 
> Kubernetes that is published on the cassandra.apache.org site.
>  
> Outline / Collaboration Google Doc : 
> [https://docs.google.com/document/d/15sZhAL-m9-a-6iuWmXdyKxsGraaJY9M6_xf9Qj2gSw4/edit?userstoinvite=jim.dickin...@datastax.com&ts=5f5a72f7]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192803#comment-17192803
 ] 

Rahul Singh edited comment on CASSANDRA-16066 at 9/9/20, 11:44 AM:
---

Thanks [~polandll]

I think we all understand your proposal. The issue that [~mck] had was not on 
the workflow per-se, but the licensing conflicts artifacts related to Antora in 
the cassandra repository which is used to create a distributed docs released 
with cassandra itself. 

 

_I will just make the point that the reason we were building a docker container 
that "runs" antora in cassandra was to facilitate a writer/developer building a 
preview of the docs they are changing. We want to make it as easy as possible 
for a contributor to check whether the doc change they propose will build 
correctly._

+*I think this is a great goal.*+ While a user is able to preview / edit docs 
in the cassandra repo, there will still need to be a way to generate in-tree 
docs. For this specific need, [~mck] 's concern was about Antora's licensing. 

_Also, please understand that there are only yaml files for antora located in 
the cassandra repo (site.yml for the preview build and antora.yml for the docs 
source)._

+*We are all on the same page here.*+  

_Lastly, the cassandra-website antora yaml files will build the whole site, 
docs and non-docs pages. It will use the cassandra repo as one content source 
(for the docs), and the cassandra-website repo as a second content source (for 
the non-docs). Docs will not be built in the cassandra repo then moved, but 
rather that repo will be sourced to build the docs as the website is built._

Acknowledged. +*We are all on the same page here as well.*+ We weren't 
suggesting that it would. This is reflected in the diagram already.. all *site* 
related doc generation is done in the cassandra-website repository using both a 
local cassandra-website src and a remote cassandra/docs src.

 
 _I think your diagram is not in agreement with what I just described. But I've 
just had my first chance to try and digest this long convo._
  
 Understood, but the goal of the diagram is not to represent your proposal but 
to mitigate the licensing issue that [~mck] brought. It is not a critique on 
your proposal, but rather a potential compromise to
 # standardize the docs / site via asciidoc format (current proposal)
 # generate nice looking sites + docs with antora (current proposal)
 # have a license-conflict-free way to generate docs that get distributed with 
the binaries using the same asciidoc format with an alternate tool that doesn't 
have licensing restrictions for distributed artifacts. (additional suggestion 
to current proposal) 


was (Author: xingh):
Thanks [~polandll]

I think we all understand your proposal. The issue that [~mck] had was not on 
the workflow per-se, but the licensing conflicts artifacts related to Antora in 
the cassandra repository which is used to create a distributed docs released 
with cassandra itself. 

 

_I will just make the point that the reason we were building a docker container 
that "runs" antora in cassandra was to facilitate a writer/developer building a 
preview of the docs they are changing. We want to make it as easy as possible 
for a contributor to check whether the doc change they propose will build 
correctly._

+*I think this is a great goal.*+ While a use is able to preview / edit docs in 
the cassandra repo, there will still need to be a way to generate in-tree docs. 
For this specific need, [~mck] 's concern was about Antora's licensing. 

_Also, please understand that there are only yaml files for antora located in 
the cassandra repo (site.yml for the preview build and antora.yml for the docs 
source)._

+*We are all on the same page here.*+  

_Lastly, the cassandra-website antora yaml files will build the whole site, 
docs and non-docs pages. It will use the cassandra repo as one content source 
(for the docs), and the cassandra-website repo as a second content source (for 
the non-docs). Docs will not be built in the cassandra repo then moved, but 
rather that repo will be sourced to build the docs as the website is built._

Acknowledged. +*We are all on the same page here as well.*+ We weren't 
suggesting that it would. This is reflected in the diagram already.. all *site* 
related doc generation is done in the cassandra-website repository using both a 
local cassandra-website src and a remote cassandra/docs src.

 
 _I think your diagram is not in agreement with what I just described. But I've 
just had my first chance to try and digest this long convo._
  
 Understood, but the goal of the diagram is not to represent your proposal but 
to mitigate the licensing issue that [~mck] brought. It is not a critique on 
your proposal, but rather a potential compromise to
 # standardize the docs / site via asciidoc f

[jira] [Comment Edited] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192803#comment-17192803
 ] 

Rahul Singh edited comment on CASSANDRA-16066 at 9/9/20, 11:43 AM:
---

Thanks [~polandll]

I think we all understand your proposal. The issue that [~mck] had was not on 
the workflow per-se, but the licensing conflicts artifacts related to Antora in 
the cassandra repository which is used to create a distributed docs released 
with cassandra itself. 

 

_I will just make the point that the reason we were building a docker container 
that "runs" antora in cassandra was to facilitate a writer/developer building a 
preview of the docs they are changing. We want to make it as easy as possible 
for a contributor to check whether the doc change they propose will build 
correctly._

+*I think this is a great goal.*+ While a use is able to preview / edit docs in 
the cassandra repo, there will still need to be a way to generate in-tree docs. 
For this specific need, [~mck] 's concern was about Antora's licensing. 

_Also, please understand that there are only yaml files for antora located in 
the cassandra repo (site.yml for the preview build and antora.yml for the docs 
source)._

+*We are all on the same page here.*+  

_Lastly, the cassandra-website antora yaml files will build the whole site, 
docs and non-docs pages. It will use the cassandra repo as one content source 
(for the docs), and the cassandra-website repo as a second content source (for 
the non-docs). Docs will not be built in the cassandra repo then moved, but 
rather that repo will be sourced to build the docs as the website is built._

Acknowledged. +*We are all on the same page here as well.*+ We weren't 
suggesting that it would. This is reflected in the diagram already.. all *site* 
related doc generation is done in the cassandra-website repository using both a 
local cassandra-website src and a remote cassandra/docs src.

 
 _I think your diagram is not in agreement with what I just described. But I've 
just had my first chance to try and digest this long convo._
  
 Understood, but the goal of the diagram is not to represent your proposal but 
to mitigate the licensing issue that [~mck] brought. It is not a critique on 
your proposal, but rather a potential compromise to
 # standardize the docs / site via asciidoc format (current proposal)
 # generate nice looking sites + docs with antora (current proposal)
 # have a license-conflict-free way to generate docs that get distributed with 
the binaries using the same asciidoc format with an alternate tool that doesn't 
have licensing restrictions for distributed artifacts. (additional suggestion 
to current proposal) 


was (Author: xingh):
Thanks [~polandll]

I think we all understand that your proposal – the issue that [~mck] had was 
not on the workflow per se, but the artifacts related to Antora in the 
cassandra repository which is distributed. 

 

_I will just make the point that the reason we were building a docker container 
that "runs" antora in cassandra was to facilitate a writer/developer building a 
preview of the docs they are changing. We want to make it as easy as possible 
for a contributor to check whether the doc change they propose will build 
correctly._

+*I think this is a great goal.*+ While a use is able to preview / edit docs in 
the cassandra repo, there will still need to be a way to generate in-tree docs. 
For this specific need, [~mck] 's concern was about Antora's licensing. 

_Also, please understand that there are only yaml files for antora located in 
the cassandra repo (site.yml for the preview build and antora.yml for the docs 
source)._

+*We are all on the same page here.*+  

_Lastly, the cassandra-website antora yaml files will build the whole site, 
docs and non-docs pages. It will use the cassandra repo as one content source 
(for the docs), and the cassandra-website repo as a second content source (for 
the non-docs). Docs will not be built in the cassandra repo then moved, but 
rather that repo will be sourced to build the docs as the website is built._

Acknowledged. +*We are all on the same page here as well.*+ We weren't 
suggesting that it would. This is reflected in the diagram already.. all *site* 
related doc generation is done in the cassandra-website repository using both a 
local cassandra-website src and a remote cassandra/docs src.

 
_I think your diagram is not in agreement with what I just described. But I've 
just had my first chance to try and digest this long convo._
 
Understood, but the goal of the diagram is not to represent your proposal but 
to mitigate the licensing issue that [~mck] brought. It is not a critique on 
your proposal, but rather a potential compromise to
 # standardize the docs / site via asciidoc format (current proposal)
 # generate nice looking sites + docs with anto

[jira] [Commented] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192803#comment-17192803
 ] 

Rahul Singh commented on CASSANDRA-16066:
-

Thanks [~polandll]

I think we all understand that your proposal – the issue that [~mck] had was 
not on the workflow per se, but the artifacts related to Antora in the 
cassandra repository which is distributed. 

 

_I will just make the point that the reason we were building a docker container 
that "runs" antora in cassandra was to facilitate a writer/developer building a 
preview of the docs they are changing. We want to make it as easy as possible 
for a contributor to check whether the doc change they propose will build 
correctly._

+*I think this is a great goal.*+ While a use is able to preview / edit docs in 
the cassandra repo, there will still need to be a way to generate in-tree docs. 
For this specific need, [~mck] 's concern was about Antora's licensing. 

_Also, please understand that there are only yaml files for antora located in 
the cassandra repo (site.yml for the preview build and antora.yml for the docs 
source)._

+*We are all on the same page here.*+  

_Lastly, the cassandra-website antora yaml files will build the whole site, 
docs and non-docs pages. It will use the cassandra repo as one content source 
(for the docs), and the cassandra-website repo as a second content source (for 
the non-docs). Docs will not be built in the cassandra repo then moved, but 
rather that repo will be sourced to build the docs as the website is built._

Acknowledged. +*We are all on the same page here as well.*+ We weren't 
suggesting that it would. This is reflected in the diagram already.. all *site* 
related doc generation is done in the cassandra-website repository using both a 
local cassandra-website src and a remote cassandra/docs src.

 
_I think your diagram is not in agreement with what I just described. But I've 
just had my first chance to try and digest this long convo._
 
Understood, but the goal of the diagram is not to represent your proposal but 
to mitigate the licensing issue that [~mck] brought. It is not a critique on 
your proposal, but rather a potential compromise to
 # standardize the docs / site via asciidoc format (current proposal)
 # generate nice looking sites + docs with antora (current proposal)
 # have a license-conflict-free way to generate docs that get distributed with 
the binaries using the same asciidoc format with an alternate tool that doesn't 
have licensing restrictions for distributed artifacts. (additional suggestion 
to current proposal) 

> Update and rework cassandra-website material to work with Antora
> 
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
> Attachments: image-2020-09-05-13-24-13-606.png, 
> image-2020-09-06-07-17-14-705.png
>
>
> *We want to modernise the way the website is built*
>  Rework the cassandra-website repository to generate a UI bundle containing 
> resources that Antora will use when generating the Cassandra documents and 
> website.
> *The existing method is starting to become dated*
>  The documentation and website templates are currently in markdown format. 
> Sphinx is used to generate the Cassandra documentation and Jekyll generates 
> the website content. One of the major issues with the existing website 
> tooling is that the live preview server (render site as it is being updated) 
> is really slow. There is a preview server that is really fast, however it is 
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
>  The work in CASSANDRA-16029 is converting the document templates to AsciiDoc 
> format. Sphinx is being replaced by Antora to generate the documentation 
> content. This change has two advantages:
>  * More flexibility if the Apache Cassandra documentation look and feel needs 
> to be updated or redesigned.
>  * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
>  Antora could also be used to generate the Cassandra website content. As 
> suggested on the [mailing 
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html] 
> this would require the existing markdown templates to be converted to 
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
>  For Antora to generate the document content and potentially the website 
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the 
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and 
> (sit

[jira] [Commented] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191242#comment-17191242
 ] 

Rahul Singh commented on CASSANDRA-16066:
-

Acknowledged [~mck] I've updated the diagram. Thanks for the Jira issue related 
to the Antora licensing. This was helpful.

 With Antora we can keep the UI bundle *and anything to do with antora* only in 
cassandra-website. Even though Antora can be used to generate the / and /docs 
section of the website and push to asf-staging, it shouldn't need to be a 
requirement to generate docs in the release. As mentioned earlier, this can be 
achieved with other tools for a basic doc conversion from Asciidoc to HTML or 
PDF. e.g. Asciidoctor uses MIT License.  We will need to ensure that our 
Asciidocs are managed in a way that is conducive to both *Antora* and something 
like *Asciidoctor* . (Any non-conflicting licensed tool can be used .. as 
mentioned before.)

 
{noformat}
Permission is hereby granted, free of charge, to any person obtaining a copy of 
this software and associated documentation files (the "Software"), to deal in 
the Software without restriction, including without limitation the rights to 
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies 
of the Software, and to permit persons to whom the Software is furnished to do 
so, subject to the following conditions:
{noformat}
 

!image-2020-09-06-07-17-14-705.png!

> Update and rework cassandra-website material to work with Antora
> 
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
> Attachments: image-2020-09-05-13-24-13-606.png, 
> image-2020-09-06-07-17-14-705.png
>
>
> *We want to modernise the way the website is built*
>  Rework the cassandra-website repository to generate a UI bundle containing 
> resources that Antora will use when generating the Cassandra documents and 
> website.
> *The existing method is starting to become dated*
>  The documentation and website templates are currently in markdown format. 
> Sphinx is used to generate the Cassandra documentation and Jekyll generates 
> the website content. One of the major issues with the existing website 
> tooling is that the live preview server (render site as it is being updated) 
> is really slow. There is a preview server that is really fast, however it is 
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
>  The work in CASSANDRA-16029 is converting the document templates to AsciiDoc 
> format. Sphinx is being replaced by Antora to generate the documentation 
> content. This change has two advantages:
>  * More flexibility if the Apache Cassandra documentation look and feel needs 
> to be updated or redesigned.
>  * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
>  Antora could also be used to generate the Cassandra website content. As 
> suggested on the [mailing 
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html] 
> this would require the existing markdown templates to be converted to 
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
>  For Antora to generate the document content and potentially the website 
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the 
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and 
> (site-wide) images. As such, it provides both the visual theme and user 
> interactions for the documentation. Effectively the UI bundle is the 
> templates and styling that are applied to the documentation and website 
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository can be used to generate the UI bundle*
>  All the resources associated with templating and styling the documentation 
> and website can be placed in the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> In this case the repository would serve two purposes;
>  * Generation of the UI bundle resources.
>  * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain 
> the documentation material, while the rest of the non-versioned pages would 
> contain that material*
>  * All other material that is used to generate documentation would live in 
> the [cassandra|https://github.com/apache/cassandra] repository. In this case 
> Antora would run on the 
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in 
> a UI bundle released on t

[jira] [Updated] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16066:

Attachment: image-2020-09-06-07-17-14-705.png

> Update and rework cassandra-website material to work with Antora
> 
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
> Attachments: image-2020-09-05-13-24-13-606.png, 
> image-2020-09-06-07-17-14-705.png
>
>
> *We want to modernise the way the website is built*
>  Rework the cassandra-website repository to generate a UI bundle containing 
> resources that Antora will use when generating the Cassandra documents and 
> website.
> *The existing method is starting to become dated*
>  The documentation and website templates are currently in markdown format. 
> Sphinx is used to generate the Cassandra documentation and Jekyll generates 
> the website content. One of the major issues with the existing website 
> tooling is that the live preview server (render site as it is being updated) 
> is really slow. There is a preview server that is really fast, however it is 
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
>  The work in CASSANDRA-16029 is converting the document templates to AsciiDoc 
> format. Sphinx is being replaced by Antora to generate the documentation 
> content. This change has two advantages:
>  * More flexibility if the Apache Cassandra documentation look and feel needs 
> to be updated or redesigned.
>  * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
>  Antora could also be used to generate the Cassandra website content. As 
> suggested on the [mailing 
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html] 
> this would require the existing markdown templates to be converted to 
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
>  For Antora to generate the document content and potentially the website 
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the 
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and 
> (site-wide) images. As such, it provides both the visual theme and user 
> interactions for the documentation. Effectively the UI bundle is the 
> templates and styling that are applied to the documentation and website 
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository can be used to generate the UI bundle*
>  All the resources associated with templating and styling the documentation 
> and website can be placed in the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> In this case the repository would serve two purposes;
>  * Generation of the UI bundle resources.
>  * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain 
> the documentation material, while the rest of the non-versioned pages would 
> contain that material*
>  * All other material that is used to generate documentation would live in 
> the [cassandra|https://github.com/apache/cassandra] repository. In this case 
> Antora would run on the 
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in 
> a UI bundle released on the GitHub 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> The content generated by Antora using the site.yml file located in this repo 
> can be used to preview the docs for review.
>  * All other non-versioned material, such as the blogs, development 
> instructions, and third-party page would live in the GitHub 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> Antora will generate the full website using the site.yml located in this 
> repo, using both as content sources the material located in both the 
> [cassandra|https://github.com/apache/cassandra] and 
> [cassandra-website|https://github.com/apache/cassandra-website] repositories.
> *Design, content, and layout would remain the same*
>  This proposal means the roles of each repository will change. In addition, 
> the workflow to publish material will change as well. However, the website 
> design, content, and layout will remain the same.
> As an added bonus the tooling would allow for a live preview server that is 
> fast and responsive. However, the time to build and generate the {{nodetool}} 
> and Cassandra YAML AssciDoc files will still take in the order of minutes to 
> complete.
> *The [cassandra-website|https://github.com/apache

[jira] [Commented] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191118#comment-17191118
 ] 

Rahul Singh commented on CASSANDRA-16066:
-

Lorina's proposal above mentions a docker container in the cassandra src to 
generate documentation as well in the cassandra-website src. 

If the Antora license constraint prevents us from placing Antora artifacts in 
the cassandra.git, does it still count if the actual build process is 100% done 
by a prebuilt docker image ? If so, then what you ask

 [~mck] based on what you mentioned about Antora license, does this mean it 
prevents us from even having a Dockerfile that mentions an Antora image + 
configuration yml which tells which files to convert?

*"For the releases, can the in-tree asciidocs be built without antora and 
solely in-tree?*

If we can't have Antora what-so-ever  on the cassandra.git, then we can use a 
much more basic asciidoc to html/pdf generator which doesn't have such 
constraints. There are plenty out there and some of them may just be a HTML/JS 
shell that renders Asciidoc to HTML dynamically without the need for a 
generation step for intree docs. 
([https://gist.github.com/briandominick/e5754cc8438dd9503d936ef65fffbb2d,] 

At the same time, Antora being run in the cassandra-website repo would pull the 
same asciidoc files and create nice looking site out of it. 

 

!image-2020-09-05-13-24-13-606.png!

 

> Update and rework cassandra-website material to work with Antora
> 
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
> Attachments: image-2020-09-05-13-24-13-606.png
>
>
> *We want to modernise the way the website is built*
>  Rework the cassandra-website repository to generate a UI bundle containing 
> resources that Antora will use when generating the Cassandra documents and 
> website.
> *The existing method is starting to become dated*
>  The documentation and website templates are currently in markdown format. 
> Sphinx is used to generate the Cassandra documentation and Jekyll generates 
> the website content. One of the major issues with the existing website 
> tooling is that the live preview server (render site as it is being updated) 
> is really slow. There is a preview server that is really fast, however it is 
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
>  The work in CASSANDRA-16029 is converting the document templates to AsciiDoc 
> format. Sphinx is being replaced by Antora to generate the documentation 
> content. This change has two advantages:
>  * More flexibility if the Apache Cassandra documentation look and feel needs 
> to be updated or redesigned.
>  * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
>  Antora could also be used to generate the Cassandra website content. As 
> suggested on the [mailing 
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html] 
> this would require the existing markdown templates to be converted to 
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
>  For Antora to generate the document content and potentially the website 
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the 
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and 
> (site-wide) images. As such, it provides both the visual theme and user 
> interactions for the documentation. Effectively the UI bundle is the 
> templates and styling that are applied to the documentation and website 
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository can be used to generate the UI bundle*
>  All the resources associated with templating and styling the documentation 
> and website can be placed in the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> In this case the repository would serve two purposes;
>  * Generation of the UI bundle resources.
>  * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain 
> the documentation material, while the rest of the non-versioned pages would 
> contain that material*
>  * All other material that is used to generate documentation would live in 
> the [cassandra|https://github.com/apache/cassandra] repository. In this case 
> Antora would run on the 
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in 
> a UI bundle released on the GitHub 
> [cassandra-website|https://github.com/apa

[jira] [Updated] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16066:

Attachment: image-2020-09-05-13-24-13-606.png

> Update and rework cassandra-website material to work with Antora
> 
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
> Attachments: image-2020-09-05-13-24-13-606.png
>
>
> *We want to modernise the way the website is built*
>  Rework the cassandra-website repository to generate a UI bundle containing 
> resources that Antora will use when generating the Cassandra documents and 
> website.
> *The existing method is starting to become dated*
>  The documentation and website templates are currently in markdown format. 
> Sphinx is used to generate the Cassandra documentation and Jekyll generates 
> the website content. One of the major issues with the existing website 
> tooling is that the live preview server (render site as it is being updated) 
> is really slow. There is a preview server that is really fast, however it is 
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
>  The work in CASSANDRA-16029 is converting the document templates to AsciiDoc 
> format. Sphinx is being replaced by Antora to generate the documentation 
> content. This change has two advantages:
>  * More flexibility if the Apache Cassandra documentation look and feel needs 
> to be updated or redesigned.
>  * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
>  Antora could also be used to generate the Cassandra website content. As 
> suggested on the [mailing 
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html] 
> this would require the existing markdown templates to be converted to 
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
>  For Antora to generate the document content and potentially the website 
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the 
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and 
> (site-wide) images. As such, it provides both the visual theme and user 
> interactions for the documentation. Effectively the UI bundle is the 
> templates and styling that are applied to the documentation and website 
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository can be used to generate the UI bundle*
>  All the resources associated with templating and styling the documentation 
> and website can be placed in the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> In this case the repository would serve two purposes;
>  * Generation of the UI bundle resources.
>  * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain 
> the documentation material, while the rest of the non-versioned pages would 
> contain that material*
>  * All other material that is used to generate documentation would live in 
> the [cassandra|https://github.com/apache/cassandra] repository. In this case 
> Antora would run on the 
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in 
> a UI bundle released on the GitHub 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> The content generated by Antora using the site.yml file located in this repo 
> can be used to preview the docs for review.
>  * All other non-versioned material, such as the blogs, development 
> instructions, and third-party page would live in the GitHub 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> Antora will generate the full website using the site.yml located in this 
> repo, using both as content sources the material located in both the 
> [cassandra|https://github.com/apache/cassandra] and 
> [cassandra-website|https://github.com/apache/cassandra-website] repositories.
> *Design, content, and layout would remain the same*
>  This proposal means the roles of each repository will change. In addition, 
> the workflow to publish material will change as well. However, the website 
> design, content, and layout will remain the same.
> As an added bonus the tooling would allow for a live preview server that is 
> fast and responsive. However, the time to build and generate the {{nodetool}} 
> and Cassandra YAML AssciDoc files will still take in the order of minutes to 
> complete.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository woul

[jira] [Commented] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191037#comment-17191037
 ] 

Rahul Singh commented on CASSANDRA-16066:
-

Thanks for clarifying the antora license constraint. I like your approach 
because it achieves the same thing with two build processes that run within the 
cassandra-website : 1 to update / from contents in the website repo and 2 to 
update /docs/ from the cassandra repo. 

I'll review the links again and circle back but I think what you are saying is 
possible. Antora can do local, remote public or remote private repos. The only 
change from [~polandll] 's plan is to make sure we only run Antora in the 
cassandra-website source for both sets of artifacts. 

 

> Update and rework cassandra-website material to work with Antora
> 
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
>
> *We want to modernise the way the website is built*
>  Rework the cassandra-website repository to generate a UI bundle containing 
> resources that Antora will use when generating the Cassandra documents and 
> website.
> *The existing method is starting to become dated*
>  The documentation and website templates are currently in markdown format. 
> Sphinx is used to generate the Cassandra documentation and Jekyll generates 
> the website content. One of the major issues with the existing website 
> tooling is that the live preview server (render site as it is being updated) 
> is really slow. There is a preview server that is really fast, however it is 
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
>  The work in CASSANDRA-16029 is converting the document templates to AsciiDoc 
> format. Sphinx is being replaced by Antora to generate the documentation 
> content. This change has two advantages:
>  * More flexibility if the Apache Cassandra documentation look and feel needs 
> to be updated or redesigned.
>  * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
>  Antora could also be used to generate the Cassandra website content. As 
> suggested on the [mailing 
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html] 
> this would require the existing markdown templates to be converted to 
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
>  For Antora to generate the document content and potentially the website 
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the 
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and 
> (site-wide) images. As such, it provides both the visual theme and user 
> interactions for the documentation. Effectively the UI bundle is the 
> templates and styling that are applied to the documentation and website 
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository can be used to generate the UI bundle*
>  All the resources associated with templating and styling the documentation 
> and website can be placed in the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> In this case the repository would serve two purposes;
>  * Generation of the UI bundle resources.
>  * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain 
> the documentation material, while the rest of the non-versioned pages would 
> contain that material*
>  * All other material that is used to generate documentation would live in 
> the [cassandra|https://github.com/apache/cassandra] repository. In this case 
> Antora would run on the 
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in 
> a UI bundle released on the GitHub 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> The content generated by Antora using the site.yml file located in this repo 
> can be used to preview the docs for review.
>  * All other non-versioned material, such as the blogs, development 
> instructions, and third-party page would live in the GitHub 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> Antora will generate the full website using the site.yml located in this 
> repo, using both as content sources the material located in both the 
> [cassandra|https://github.com/apache/cassandra] and 
> [cassandra-website|https://github.com/apache/cassandra-website] repositories.
> *Design, content, and layout would remain the same*
>  This proposal means the roles o

[jira] [Commented] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190746#comment-17190746
 ] 

Rahul Singh commented on CASSANDRA-16066:
-

>From my understanding, this is what I think lorina is suggesting. 

 
 * cassandra / docs / intree docs - have a dockerfile so that the the asciidocs 
can be used to create artifacts related just for documentation. 
 * cassandra-website - have a docker file so that the asciidocs can be used to 
create artifacts just for the site 

 

both of them will refer to the same ui package (referenced in git)
 * When a release is cut, the in tree build process would generate HTML/PDF 
whatever to be tarred up (we should make a "lite" version without the docs) 
with the .tar.gz
 * when the website is published, the website build process would build the 
static site content and may need to rely on the dockerfile from cassandra.git 
to produce a full website release**

*I propose this (or this is what the intention may have been all along)*
 * build process for cassandra
 ** uses docs/dockerfile as needed on releases to include in release
 ** uses docs/dockerfile as needed on releases to *publish* only /docs/ section 
of the site ( separate public path to push docs content to)
 * build process for cassandra-website
 ** uses /dockerfile as needed on *publish* blog/ etc. to / section of the site 
( separate public path to push site content to)

> Update and rework cassandra-website material to work with Antora
> 
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
>
> *We want to modernise the way the website is built*
>  Rework the cassandra-website repository to generate a UI bundle containing 
> resources that Antora will use when generating the Cassandra documents and 
> website.
> *The existing method is starting to become dated*
>  The documentation and website templates are currently in markdown format. 
> Sphinx is used to generate the Cassandra documentation and Jekyll generates 
> the website content. One of the major issues with the existing website 
> tooling is that the live preview server (render site as it is being updated) 
> is really slow. There is a preview server that is really fast, however it is 
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
>  The work in CASSANDRA-16029 is converting the document templates to AsciiDoc 
> format. Sphinx is being replaced by Antora to generate the documentation 
> content. This change has two advantages:
>  * More flexibility if the Apache Cassandra documentation look and feel needs 
> to be updated or redesigned.
>  * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
>  Antora could also be used to generate the Cassandra website content. As 
> suggested on the [mailing 
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html] 
> this would require the existing markdown templates to be converted to 
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
>  For Antora to generate the document content and potentially the website 
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the 
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and 
> (site-wide) images. As such, it provides both the visual theme and user 
> interactions for the documentation. Effectively the UI bundle is the 
> templates and styling that are applied to the documentation and website 
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository can be used to generate the UI bundle*
>  All the resources associated with templating and styling the documentation 
> and website can be placed in the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> In this case the repository would serve two purposes;
>  * Generation of the UI bundle resources.
>  * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain 
> the documentation material, while the rest of the non-versioned pages would 
> contain that material*
>  * All other material that is used to generate documentation would live in 
> the [cassandra|https://github.com/apache/cassandra] repository. In this case 
> Antora would run on the 
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in 
> a UI bundle released on the GitHub 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> The content generated by 

[jira] [Commented] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186063#comment-17186063
 ] 

Rahul Singh commented on CASSANDRA-16066:
-

Great! Looking forward to the POC. Where does the actual build of the docs 
happen. e.g. Will someone pull down cassandra-website and do edits/previews, or 
will they pull down cassandra .. I see that the dockerfile right now is in the 
main cassandra repo. 

> Update and rework cassandra-website material to work with Antora
> 
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
>
> *We want to modernise the way the website is built*
>  Rework the cassandra-website repository to generate a UI bundle containing 
> resources that Antora will use when generating the Cassandra documents and 
> website.
> *The existing method is starting to become dated*
>  The documentation and website templates are currently in markdown format. 
> Sphinx is used to generate the Cassandra documentation and Jekyll generates 
> the website content. One of the major issues with the existing website 
> tooling is that the live preview server (render site as it is being updated) 
> is really slow. There is a preview server that is really fast, however it is 
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
>  The work in CASSANDRA-16029 is converting the document templates to AsciiDoc 
> format. Sphinx is being replaced by Antora to generate the documentation 
> content. This change has two advantages:
>  * More flexibility if the Apache Cassandra documentation look and feel needs 
> to be updated or redesigned.
>  * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
>  Antora could also be used to generate the Cassandra website content. As 
> suggested on the [mailing 
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html] 
> this would require the existing markdown templates to be converted to 
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
>  For Antora to generate the document content and potentially the website 
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the 
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and 
> (site-wide) images. As such, it provides both the visual theme and user 
> interactions for the documentation. Effectively the UI bundle is the 
> templates and styling that are applied to the documentation and website 
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository can be used to generate the UI bundle*
>  All the resources associated with templating and styling the documentation 
> and website can be placed in the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> In this case the repository would serve two purposes;
>  * Generation of the UI bundle resources.
>  * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain 
> the site material*
>  All other material that is used to generate documentation, blogs and project 
> information would live in the [cassandra|https://github.com/apache/cassandra] 
> repository. In this case Antora would run on the 
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in 
> a UI bundle released on the GitHub 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> The content generated by Antora would be placed in the 
> [cassandra-website/content|https://github.com/apache/cassandra-website/content]
>  directory
> *Design, content, and layout would remain the same*
>  This proposal means the roles of each repository will change. In addition, 
> the workflow to publish material will change as well. However, the website 
> design, content, and layout will remain the same.
> As an added bonus the tooling would allow for a live preview server that is 
> fast and responsive. However, the time to build and generate the {{nodetool}} 
> and Cassandra YAML AssciDoc files will still take in the order of minutes to 
> complete.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository would need to be modified*
>  The following changes would need to be made to the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository:
> ||File/Directory||Action||Reason||
> |[content/|https://github.com/apache/cassandra-website/content]|keep|Production
>  site content served from this directo

[jira] [Commented] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182177#comment-17182177
 ] 

Rahul Singh commented on CASSANDRA-16066:
-

I agree. I think SSGs are great. I use Hugo and Gatsby and have gotten used to 
Jekyll. Antora seems to be purpose built for documentation w/ TOCs etc. 

I’d recommend keeping the “marketing” / landing pages as @Jon mentioned 
separate and maybe in the future using something that is more focused on 
content rather than documentation  that makes it appealing and easy to add / 
edit content. 

> Update and rework cassandra-website material to work with Antora
> 
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
>
> *We want to modernise the way the website is built*
>  Rework the cassandra-website repository to generate a UI bundle containing 
> resources that Antora will use when generating the Cassandra documents and 
> website.
> *The existing method is starting to become dated*
>  The documentation and website templates are currently in markdown format. 
> Sphinx is used to generate the Cassandra documentation and Jekyll generates 
> the website content. One of the major issues with the existing website 
> tooling is that the live preview server (render site as it is being updated) 
> is really slow. There is a preview server that is really fast, however it is 
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
>  The work in CASSANDRA-16029 is converting the document templates to AsciiDoc 
> format. Sphinx is being replaced by Antora to generate the documentation 
> content. This change has two advantages:
>  * More flexibility if the Apache Cassandra documentation look and feel needs 
> to be updated or redesigned.
>  * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
>  Antora could also be used to generate the Cassandra website content. As 
> suggested on the [mailing 
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html] 
> this would require the existing markdown templates to be converted to 
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
>  For Antora to generate the document content and potentially the website 
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the 
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and 
> (site-wide) images. As such, it provides both the visual theme and user 
> interactions for the documentation. Effectively the UI bundle is the 
> templates and styling that are applied to the documentation and website 
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository can be used to generate the UI bundle*
>  All the resources associated with templating and styling the documentation 
> and website can be placed in the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> In this case the repository would serve two purposes;
>  * Generation of the UI bundle resources.
>  * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain 
> the site material*
>  All other material that is used to generate documentation, blogs and project 
> information would live in the [cassandra|https://github.com/apache/cassandra] 
> repository. In this case Antora would run on the 
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in 
> a UI bundle released on the GitHub 
> [cassandra-website|https://github.com/apache/cassandra-website] repository. 
> The content generated by Antora would be placed in the 
> [cassandra-website/content|https://github.com/apache/cassandra-website/content]
>  directory
> *Design, content, and layout would remain the same*
>  This proposal means the roles of each repository will change. In addition, 
> the workflow to publish material will change as well. However, the website 
> design, content, and layout will remain the same.
> As an added bonus the tooling would allow for a live preview server that is 
> fast and responsive. However, the time to build and generate the {{nodetool}} 
> and Cassandra YAML AssciDoc files will still take in the order of minutes to 
> complete.
> *The [cassandra-website|https://github.com/apache/cassandra-website] 
> repository would need to be modified*
>  The following changes would need to be made to the 
> [cassandra-website|https://github.com/apache/cassandra-website] repository:
> ||File/Directory||Acti

[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16046:

Test and Documentation Plan: Ran locally in docker and tested edits. Looks 
good. 
 Status: Patch Available  (was: In Progress)

> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Rahul Singh
>Priority: Normal
>  Labels: pull-request-available
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content 
> code is mostly ready 
>  
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

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

Rahul Singh reassigned CASSANDRA-16046:
---

Assignee: Mick Semb Wever  (was: Rahul Singh)

> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Mick Semb Wever
>Priority: Normal
>  Labels: pull-request-available
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content 
> code is mostly ready 
>  
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

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

Rahul Singh reassigned CASSANDRA-16046:
---

Assignee: Rahul Singh  (was: Anthony Grasso)

> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Rahul Singh
>Priority: Normal
>  Labels: pull-request-available
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content 
> code is mostly ready 
>  
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16046:

Authors: Rahul Singh  (was: Anthony Grasso)

> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Anthony Grasso
>Priority: Normal
>  Labels: pull-request-available
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content 
> code is mostly ready 
>  
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

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

Rahul Singh reassigned CASSANDRA-16046:
---

Assignee: Anthony Grasso  (was: Rahul Singh)

> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Anthony Grasso
>Priority: Normal
>  Labels: pull-request-available
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content 
> code is mostly ready 
>  
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16046:

Labels:   (was: pull-request-available)

> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Rahul Singh
>Priority: Normal
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content 
> code is mostly ready 
>  
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177062#comment-17177062
 ] 

Rahul Singh commented on CASSANDRA-16046:
-

[https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]
 

Most current content. 

> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Rahul Singh
>Priority: Normal
>  Labels: pull-request-available
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content 
> code is mostly ready 
>  
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-16046:

Description: 
We're getting a blog post out before/coinciding with Kubecon 2020. Content code 
is mostly ready 

 

 

[https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]

  was:
We're getting a blog post out before/coinciding with Kubecon 2020. Content is 
ready 

[https://docs.google.com/document/d/1r8XOav0H_QqXPSkgxJ_naS-NbQfWxsmC2L8Idh7N1Hk/edit?ts=5f31ae5c]

 

Code is mostly ready. 

[https://github.com/Anant/cassandra-website/blob/master/src/img/blog-post-cassandra-and-kubernetes-sig-update/operator-capabilities.png]


> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Rahul Singh
>Priority: Normal
>  Labels: pull-request-available
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content 
> code is mostly ready 
>  
>  
> [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177053#comment-17177053
 ] 

Rahul Singh commented on CASSANDRA-16046:
-

Adding another edit today/tomorrow with hopefully the survey link and a few of 
the other mentioned resources linked. I'm going to retract this pull request 
for now and make a new one when it's ready. 

> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Rahul Singh
>Priority: Normal
>  Labels: pull-request-available
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content is 
> ready 
> [https://docs.google.com/document/d/1r8XOav0H_QqXPSkgxJ_naS-NbQfWxsmC2L8Idh7N1Hk/edit?ts=5f31ae5c]
>  
> Code is mostly ready. 
> [https://github.com/Anant/cassandra-website/blob/master/src/img/blog-post-cassandra-and-kubernetes-sig-update/operator-capabilities.png]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176697#comment-17176697
 ] 

Rahul Singh commented on CASSANDRA-16046:
-

Created PR [https://github.com/apache/cassandra-website/pull/15] 

> BLOG - Post about Cassandra & Kubernetes - SIG Update
> -
>
> Key: CASSANDRA-16046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation/Blog
>Reporter: Rahul Singh
>Assignee: Rahul Singh
>Priority: Normal
>  Labels: pull-request-available
>
> We're getting a blog post out before/coinciding with Kubecon 2020. Content is 
> ready 
> [https://docs.google.com/document/d/1r8XOav0H_QqXPSkgxJ_naS-NbQfWxsmC2L8Idh7N1Hk/edit?ts=5f31ae5c]
>  
> Code is mostly ready. 
> [https://github.com/Anant/cassandra-website/blob/master/src/img/blog-post-cassandra-and-kubernetes-sig-update/operator-capabilities.png]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-16046) BLOG - Post about Cassandra & Kubernetes - SIG Update

[Rahul Singh (Jira)]

Rahul Singh created CASSANDRA-16046:
---

 Summary: BLOG - Post about Cassandra & Kubernetes - SIG Update
 Key: CASSANDRA-16046
 URL: https://issues.apache.org/jira/browse/CASSANDRA-16046
 Project: Cassandra
  Issue Type: Improvement
  Components: Documentation/Blog
Reporter: Rahul Singh
Assignee: Rahul Singh


We're getting a blog post out before/coinciding with Kubecon 2020. Content is 
ready 

[https://docs.google.com/document/d/1r8XOav0H_QqXPSkgxJ_naS-NbQfWxsmC2L8Idh7N1Hk/edit?ts=5f31ae5c]

 

Code is mostly ready. 

[https://github.com/Anant/cassandra-website/blob/master/src/img/blog-post-cassandra-and-kubernetes-sig-update/operator-capabilities.png]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14258) document process of changing token count by adding a new DC

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050736#comment-17050736
 ] 

Rahul Singh commented on CASSANDRA-14258:
-

[~TanakaRM] did you make any progress on this? 

Heres a suggested outline 
 * Overview of Single vs. VNode
 * Overview of new DC approach to change token count
 ** Example from single to 8 vnodes
 ** Example from 256 to 16 vnodes

> document process of changing token count by adding a new DC
> ---
>
> Key: CASSANDRA-14258
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14258
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Tanaka
>Priority: Normal
>
> also provide warnings around not adding instances of different sizes to try 
> to migrate and why it's horrible.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-15087) Find a place for the professional services page

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-15087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050725#comment-17050725
 ] 

Rahul Singh commented on CASSANDRA-15087:
-

Outlining next actions 
 * Double check to see if companies are still in business 
 * Start with a simple page with a listing of company name, link to company, 
short description 
 * Iterate with logos, social media links etc 

> Find a place for the professional services page
> ---
>
> Key: CASSANDRA-15087
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15087
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Rahul Singh
>Priority: Low
>
> We've got a link to our old wiki on the Cassandra homepage for third party 
> support. We link to the old Wiki, which will eventually be sunset. We should 
> migrate this information to a page in the static site and link to it there.
>  
> Current link : 
> [https://cwiki.apache.org/confluence/display/CASSANDRA2/ThirdPartySupport]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-15087) Find a place for the professional services page

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-15087:

Description: 
We've got a link to our old wiki on the Cassandra homepage for third party 
support. We link to the old Wiki, which will eventually be sunset. We should 
migrate this information to a page in the static site and link to it there.

 

Current link : 
[https://cwiki.apache.org/confluence/display/CASSANDRA2/ThirdPartySupport]

  was:We've got a link to our old wiki on the Cassandra homepage for third 
party support.  We link to the old Wiki, which will eventually be sunset.  We 
should migrate this information to a page in the static site and link to it 
there.


> Find a place for the professional services page
> ---
>
> Key: CASSANDRA-15087
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15087
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Rahul Singh
>Priority: Low
>
> We've got a link to our old wiki on the Cassandra homepage for third party 
> support. We link to the old Wiki, which will eventually be sunset. We should 
> migrate this information to a page in the static site and link to it there.
>  
> Current link : 
> [https://cwiki.apache.org/confluence/display/CASSANDRA2/ThirdPartySupport]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-15087) Find a place for the professional services page

[Rahul Singh (Jira)]

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

Rahul Singh reassigned CASSANDRA-15087:
---

Assignee: Rahul Singh

> Find a place for the professional services page
> ---
>
> Key: CASSANDRA-15087
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15087
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Rahul Singh
>Priority: Low
>
> We've got a link to our old wiki on the Cassandra homepage for third party 
> support.  We link to the old Wiki, which will eventually be sunset.  We 
> should migrate this information to a page in the static site and link to it 
> there.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13960) update cassandra.yaml links to point to new docs instead of the wiki

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050723#comment-17050723
 ] 

Rahul Singh commented on CASSANDRA-13960:
-

[~gnlima] how're you doing on this ? 

Outling next actions

 
 * Move relevant info if applicable from 
 ** [http://wiki.apache.org/cassandra/StorageConfiguration]
 ** 
[https://cwiki.apache.org/confluence/display/CASSANDRA2/StorageConfiguration]
 ** -[http://wiki.apache.org/cassandra/Operations]-
 ** -[http://wiki.apache.org/cassandra/HintedHandoff]- 
 ** [https://cwiki.apache.org/confluence/display/CASSANDRA2/HintedHandoff]
 * Replace cassandra.yaml references to new links 
 ** [http://cassandra.apache.org/doc/latest/operating/index.html] 
 ** 
[http://cassandra.apache.org/doc/latest/operating/hints.html|http://cassandra.apache.org/doc/latest/operating/hints.html?highlight=storage]
 ** 
[http://cassandra.apache.org/doc/latest/configuration/cassandra_config_file.html]

> update cassandra.yaml links to point to new docs instead of the wiki
> 
>
> Key: CASSANDRA-13960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13960
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Gabriel Nobrega
>Priority: Low
>  Labels: lhf
>
> The wiki is dead, let's clean up the links and be sure we have the right into 
> on cassandra.apache.org.
> {code}
> # NOTE:
> #   See http://wiki.apache.org/cassandra/StorageConfiguration for
> #   full explanations of configuration directives
> # /NOTE
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13823) The Getting Started page should have instructions on setting up a cluster

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050719#comment-17050719
 ] 

Rahul Singh commented on CASSANDRA-13823:
-

[~sumanth.pasupuleti] any progress on this ? One easy way to push a ticket 
forward is to make an outline as your next physical action. 

Here's a suggestion 
 * Overview of Installation Methods
 ** Local using Binaries
 ** Local using CCM
 ** Local using VM
 ** Local using Containers
 ** 

 

> The Getting Started page should have instructions on setting up a cluster
> -
>
> Key: CASSANDRA-13823
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13823
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Sumanth Pasupuleti
>Priority: Low
>  Labels: lhf
>
> Currently the docs don't have an easy to follow guide on setting up a 
> cluster.  I think it would benefit from a nice easy to follow walkthrough.
> https://cassandra.apache.org/doc/latest/getting_started/index.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-12584) document SASI functionality

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-12584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050715#comment-17050715
 ] 

Rahul Singh commented on CASSANDRA-12584:
-

This can be condensed to a few hundred words to start. 
 * Overview
 ** Overview of SASI vs. Secondary Index
 ** Overview of different indexing options 
 *** prefix
 *** suffix
 *** suffix_all_case
 *** contains
 *** sparse
 ** Overview of analyzers
 * Examples
 ** Wildcard
 ** LIKE
 ** stop words

> document SASI functionality
> ---
>
> Key: CASSANDRA-12584
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12584
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Rahul Singh
>Priority: Low
>
> It doesn't look like SASI indexes are documented in tree.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-12584) document SASI functionality

[Rahul Singh (Jira)]

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

Rahul Singh reassigned CASSANDRA-12584:
---

Assignee: Rahul Singh

> document SASI functionality
> ---
>
> Key: CASSANDRA-12584
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12584
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Rahul Singh
>Priority: Low
>
> It doesn't look like SASI indexes are documented in tree.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-12692) document read path

[Rahul Singh (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050703#comment-17050703
 ] 

Rahul Singh commented on CASSANDRA-12692:
-

* Need to assemble a decent visual of the read path first 
 * The text is mostly accurate but will need to make sure any changes since 3x 
are reflected. 

> document read path
> --
>
> Key: CASSANDRA-12692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12692
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Rahul Singh
>Priority: Low
>
> I'm not seeing any docs for the read path. We should port this over from the 
> wiki, assuming it's correct:
> [-https://wiki.apache.org/cassandra/ReadPathForUsers-]
> [https://cwiki.apache.org/confluence/display/CASSANDRA2/ReadPathForUsers]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-12692) document read path

[Rahul Singh (Jira)]

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

Rahul Singh updated CASSANDRA-12692:

Description: 
I'm not seeing any docs for the read path. We should port this over from the 
wiki, assuming it's correct:

[-https://wiki.apache.org/cassandra/ReadPathForUsers-]

[https://cwiki.apache.org/confluence/display/CASSANDRA2/ReadPathForUsers]

  was:
I'm not seeing any docs for the read path.  We should port this over from the 
wiki, assuming it's correct:

https://wiki.apache.org/cassandra/ReadPathForUsers


> document read path
> --
>
> Key: CASSANDRA-12692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12692
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Rahul Singh
>Priority: Low
>
> I'm not seeing any docs for the read path. We should port this over from the 
> wiki, assuming it's correct:
> [-https://wiki.apache.org/cassandra/ReadPathForUsers-]
> [https://cwiki.apache.org/confluence/display/CASSANDRA2/ReadPathForUsers]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-12692) document read path

[Rahul Singh (Jira)]

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

Rahul Singh reassigned CASSANDRA-12692:
---

Assignee: Rahul Singh  (was: Jon Haddad)

> document read path
> --
>
> Key: CASSANDRA-12692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12692
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Documentation and Website
>Reporter: Jon Haddad
>Assignee: Rahul Singh
>Priority: Low
>
> I'm not seeing any docs for the read path.  We should port this over from the 
> wiki, assuming it's correct:
> https://wiki.apache.org/cassandra/ReadPathForUsers



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14954) Website documentation for stable and latest, with stable as default linked

[Rahul Singh (JIRA)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896705#comment-16896705
 ] 

Rahul Singh commented on CASSANDRA-14954:
-

Nevermind, the patch is against cassandra-site repository.  Closest thing I can 
find is the SVN repo [https://svn.apache.org/repos/asf/cassandra/site/] 

 

Is there any other authoritative location  [~muru] [~michaelsembwever]

> Website documentation for stable and latest, with stable as default linked
> --
>
> Key: CASSANDRA-14954
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14954
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: mck
>Assignee: Rahul Singh
>Priority: Low
> Fix For: 3.11.x, 4.x
>
> Attachments: make-add-stable-doc.patch
>
>
> The website should link Documentation to the docs generated for our most 
> recent stable release.
> By providing directory listing (using {{`htaccess Indexes`}}) under /doc/, 
> and having two symlinks {{latest}} and {{stable}}, we can by default link to 
> {{stable}}.
> The following patch
>  - adds to the website Makefile the task {{add-stable-doc}}
>  - changes the default documentation link to {{/doc/stable/}}
>  - removes the html redirecting from {{doc/ --> doc/latest/}}
>  - adds directory listing to {{/doc/}} for a simple view of versioned docs 
> available



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14954) Website documentation for stable and latest, with stable as default linked

[Rahul Singh (JIRA)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896093#comment-16896093
 ] 

Rahul Singh commented on CASSANDRA-14954:
-

Apply check has some errors, probably due to directory changes since this was 
done. I tried on trunk and cassandra-3.11 branches. Will review the patch 
individually and make changes and submit another patch if needed. 

> Website documentation for stable and latest, with stable as default linked
> --
>
> Key: CASSANDRA-14954
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14954
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: mck
>Assignee: mck
>Priority: Low
> Fix For: 3.11.x, 4.x
>
> Attachments: make-add-stable-doc.patch
>
>
> The website should link Documentation to the docs generated for our most 
> recent stable release.
> By providing directory listing (using {{`htaccess Indexes`}}) under /doc/, 
> and having two symlinks {{latest}} and {{stable}}, we can by default link to 
> {{stable}}.
> The following patch
>  - adds to the website Makefile the task {{add-stable-doc}}
>  - changes the default documentation link to {{/doc/stable/}}
>  - removes the html redirecting from {{doc/ --> doc/latest/}}
>  - adds directory listing to {{/doc/}} for a simple view of versioned docs 
> available



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-14954) Website documentation for stable and latest, with stable as default linked

[Rahul Singh (JIRA)]

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

Rahul Singh reassigned CASSANDRA-14954:
---

Assignee: Rahul Singh  (was: mck)

> Website documentation for stable and latest, with stable as default linked
> --
>
> Key: CASSANDRA-14954
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14954
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: mck
>Assignee: Rahul Singh
>Priority: Low
> Fix For: 3.11.x, 4.x
>
> Attachments: make-add-stable-doc.patch
>
>
> The website should link Documentation to the docs generated for our most 
> recent stable release.
> By providing directory listing (using {{`htaccess Indexes`}}) under /doc/, 
> and having two symlinks {{latest}} and {{stable}}, we can by default link to 
> {{stable}}.
> The following patch
>  - adds to the website Makefile the task {{add-stable-doc}}
>  - changes the default documentation link to {{/doc/stable/}}
>  - removes the html redirecting from {{doc/ --> doc/latest/}}
>  - adds directory listing to {{/doc/}} for a simple view of versioned docs 
> available



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14954) Website documentation for stable and latest, with stable as default linked

[Rahul Singh (JIRA)]

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

Rahul Singh updated CASSANDRA-14954:

Reviewers: Rahul Singh  (was: Jason Brown)

> Website documentation for stable and latest, with stable as default linked
> --
>
> Key: CASSANDRA-14954
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14954
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: mck
>Assignee: mck
>Priority: Low
> Fix For: 3.11.x, 4.x
>
> Attachments: make-add-stable-doc.patch
>
>
> The website should link Documentation to the docs generated for our most 
> recent stable release.
> By providing directory listing (using {{`htaccess Indexes`}}) under /doc/, 
> and having two symlinks {{latest}} and {{stable}}, we can by default link to 
> {{stable}}.
> The following patch
>  - adds to the website Makefile the task {{add-stable-doc}}
>  - changes the default documentation link to {{/doc/stable/}}
>  - removes the html redirecting from {{doc/ --> doc/latest/}}
>  - adds directory listing to {{/doc/}} for a simple view of versioned docs 
> available



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-15237) Professionally Support Link is Broken

[Rahul Singh (JIRA)]

Rahul Singh created CASSANDRA-15237:
---

 Summary: Professionally Support Link is Broken
 Key: CASSANDRA-15237
 URL: https://issues.apache.org/jira/browse/CASSANDRA-15237
 Project: Cassandra
  Issue Type: Improvement
  Components: Documentation/Website
Reporter: Rahul Singh
Assignee: Rahul Singh
 Attachments: image-2019-07-18-11-05-30-440.png, 
image-2019-07-18-11-06-03-030.png

Link is broken. Either it should go to the new confluence page we are working 
on or the link be taken down. 

 

!image-2019-07-18-11-06-03-030.png!

 

 

!image-2019-07-18-11-05-30-440.png!



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14128) Prune dead links from cassandra.apache.org

[Rahul Singh (JIRA)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763951#comment-16763951
 ] 

Rahul Singh commented on CASSANDRA-14128:
-

It depends on the audience. There are many who still don't know what Cassandra 
is or how different it is from Mongo. The data practitioners or technology 
leaders in an organization may now know what it is and what it does, but it 
still has an uphill battle at the other 60% of the fortune 500. 

Having a list of frequently updated cases however helps the overall public 
relations for the technology, in which folks that use it feel proud to be 
listed, and service providers who service Cassandra have the closest thing to a 
partnership with the community. 

A little bit of credit goes a long way. 

> Prune dead links from cassandra.apache.org
> --
>
> Key: CASSANDRA-14128
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14128
> Project: Cassandra
>  Issue Type: Task
>  Components: Legacy/Documentation and Website
>Reporter: Jeff Jirsa
>Assignee: Kurt Greaves
>Priority: Trivial
>  Labels: lhf
> Attachments: 14128-site.patch
>
>
> Lots of dead links on the site, including the homepage. Should do some 
> pruning cleanup.
> Site repo is [here|https://svn.apache.org/repos/asf/cassandra/site/] (in svn) 
> for anyone who wishes to give this a shot.



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

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org