Wish to contribute to Cassandra wiki

[RAHUL PANCHAL]

Hi



My username is RahulPanchal. I would like to contribute to the

Cassandra wiki please.



Thanks

Rahul

Re: What would a pluggable logging implementation look like?

[Murukesh Mohanan]

Thanks! Based on this and a suggestion by Jon, I'm working on a pluggable 
query-logging implementation. Can somebody have a quick look at the last patch 
submitted for CASSANDRA-13001 and tell me if I'm heading in the right direction?

Quoting my comment for that file to summarize:

- a new interface o.a.c.db.monitoring.IQueryLogger, with one function void 
logQueries(MonitoringTask.AggregatedOperations operations, 
MonitoringTask.OperationType type, long elapsed), accordingly, various elements 
in MonitoringTask have been made public
- Two classes implementing it, o.a.c.d.m.QueryDebugLogger and 
{{o.a.c.d.m.QueryTableLogger. The former implements the current debug.log 
behaviour and is default, and the latter saves stats and metadata to a table 
(hard-coded to perf.slow_log, looking for better ideas on this).
- New configuration setting slow_query_logger, works like authenticator.
- Rolled up both timed out and slow operation logging in MonitoringTask to use 
the interface. Accordingly cleaned up MonitoringTask. Perhaps the configuration 
setting should be renamed, again looking for ideas.

On 2017-03-01 19:42 (+0900), Romain Hardouin  
wrote: 
> Hi,
> I think you have to look at how authenticator/authorizer/role_manager are 
> handled.e.g. 
> https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L103https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/auth/AllowAllAuthenticator.java
> Best,Romain 
> Le Mercredi 1 mars 2017 6h19, Murukesh Mohanan 
>  a écrit :
>  
>  I'm looking at CASSANDRA-13001 (pluggable slow query logging / handling). I 
> wrote a hacky patch, where my main goal was to touch as few files as possible 
> - so I did what I could within MonitoringTask, mostly. However, it seems that 
> I completely misunderstood what the feature request was. Jon Haddad noted 
> that pluggable means:
> 
> > 1. It's going to be java code
> > 2. the pluggable thing implements an interface defined in cassandra.
> > 3. the class would be compiled and dropped in lib (loaded into classpath 
> > automatically)
> > 4. The class can be specified in the yaml and is loaded by Class.forName() 
> > to pull the interface in
> > 
> > We would need to convert the current slow query logger into a class of the 
> > defined interface and have it be the default if no class is specified in 
> > the yaml.
> 
> Can someone point me to an existing implementation of this, that I can learn 
> from? A previous patch that contributed something similar, perhaps?
> 
> 
>

Re: Contribute to the Cassandra wiki

[Anthony Grasso]

On 14 March 2017 at 03:55, Jonathan Haddad  wrote:

>
> I urge you to try giving the in-tree docs a chance.  It may not be the way
> *you* want it but I have to point out that they're the best we've seen in
> Cassandra world.  Making them prettier won't help anything.
>

Agreed


>
> Part of CASSANDRA-8700 was to shut down the wiki.  I still advocate for
> this. At the very minimum we should make it read only with a big notice
> that points people to the in-tree docs.
>

Agreed. Am unable to see the value that the old wiki provides. We should at
the very least change it to say it is deprecated and point to the in-tree
docs. I am more than happy to make these changes if we think this is a good
idea.


>
> On Mon, Mar 13, 2017 at 8:49 AM Jeremy Hanna 
> wrote:
>
> > The moinmoin wiki was preferred but because of spam, images couldn’t be
> > attached.  The options were to use confluence or have a moderated list of
> > individuals be approved to update the wiki.  The decision was made to go
> > with the latter because of the preference to stick with moinmoin rather
> > than confluence.  That’s my understanding of the history there.  I don’t
> > know if people would like to revisit using one or the other at this
> point,
> > though it would take a bit of work to convert.
> >
> > > On Mar 13, 2017, at 9:42 AM, Nate McCall  wrote:
> > >
> > >> Isn't there a way to split tech docs (aka reference) and more
> > >> user-generated and use-case related/content oriented docs? And maybe
> to
> > use
> > >> a more modern WIKI software or scheme. The CS wiki looks like 1998.
> > >
> > > The wiki is what ASF Infra provides by default. Agree that it is a bit
> > > "old-school."
> > >
> > > I'll ask around about what other projects are doing (or folks who are
> > > involved in other ASF projects, please chime in).
> >
> >
>

Re: Contribute to the Cassandra wiki

[benjamin roth]

Contribution Guide +1
Github WebUI +1
Pull requests +1

Rest: Inspect + Adapt

2017-03-13 19:38 GMT+01:00 Stefan Podkowinski :

> Agreed. Let's not give up on this as quickly. My suggestion is to at
> least provide a getting started guide for writing docs, before
> complaining about too few contributions. I'll try to draft something up
> this week.
>
> What people are probably not aware of is how easy it is to contribute
> docs through github. Just clone our repo, create a document and add your
> content. It's all possible through the github web UI including
> reStructuredText support for the viewer/editor. I'd even say to lower
> the barrier for contributing docs even further by accepting pull
> requests for them, so we can have a fully github based workflow for
> casual contributors.
>
>
> On 03/13/2017 05:55 PM, Jonathan Haddad wrote:
> > Ugh... Let's put a few facts out in the open before we start pushing to
> > move back to the wiki.
> >
> > First off, take a look at CASSANDRA-8700.  There's plenty of reasoning
> for
> > why the docs are now located in tree.  The TL;DR is:
> >
> > 1. Nobody used the wiki.  Like, ever.  A handful of edits per year.
> > 2. Docs in the wiki were out of sync w/ cassandra.  Trying to outline the
> > difference in implementations w/ nuanced behavior was difficult /
> > impossible.  With in-tree, you just check the docs that come w/ the
> version
> > you installed.  And you get them locally.  Huzzah!
> > 3. The in-tree docs are a million times better quality than the wiki
> *ever*
> > was.
> >
> > I urge you to try giving the in-tree docs a chance.  It may not be the
> way
> > *you* want it but I have to point out that they're the best we've seen in
> > Cassandra world.  Making them prettier won't help anything.
> >
> > I do agree that the process needs to be a bit smoother for people to add
> > stuff to the in tree side.  For instance, maybe for every features that's
> > written we start creating a corresponding JIRA for the documentation.
> Not
> > every developer wants to write docs, and that's fair.  The accompanying
> > JIRA would serve as a way for 2 or more people to collaborate on the
> > feature & the docs in tandem.  It may also be beneficial to use the
> dev-ml
> > to say "hey, i'm working on feature X, anyone want to help me write the
> > docs for it?  check out CASSANDRA-XYZ"
> >
> > Part of CASSANDRA-8700 was to shut down the wiki.  I still advocate for
> > this. At the very minimum we should make it read only with a big notice
> > that points people to the in-tree docs.
> >
> > On Mon, Mar 13, 2017 at 8:49 AM Jeremy Hanna  >
> > wrote:
> >
> >> The moinmoin wiki was preferred but because of spam, images couldn’t be
> >> attached.  The options were to use confluence or have a moderated list
> of
> >> individuals be approved to update the wiki.  The decision was made to go
> >> with the latter because of the preference to stick with moinmoin rather
> >> than confluence.  That’s my understanding of the history there.  I don’t
> >> know if people would like to revisit using one or the other at this
> point,
> >> though it would take a bit of work to convert.
> >>
> >>> On Mar 13, 2017, at 9:42 AM, Nate McCall  wrote:
> >>>
>  Isn't there a way to split tech docs (aka reference) and more
>  user-generated and use-case related/content oriented docs? And maybe
> to
> >> use
>  a more modern WIKI software or scheme. The CS wiki looks like 1998.
> >>> The wiki is what ASF Infra provides by default. Agree that it is a bit
> >>> "old-school."
> >>>
> >>> I'll ask around about what other projects are doing (or folks who are
> >>> involved in other ASF projects, please chime in).
> >>
>
>

Re: Contribute to the Cassandra wiki

[Stefan Podkowinski]

Agreed. Let's not give up on this as quickly. My suggestion is to at
least provide a getting started guide for writing docs, before
complaining about too few contributions. I'll try to draft something up
this week.

What people are probably not aware of is how easy it is to contribute
docs through github. Just clone our repo, create a document and add your
content. It's all possible through the github web UI including
reStructuredText support for the viewer/editor. I'd even say to lower
the barrier for contributing docs even further by accepting pull
requests for them, so we can have a fully github based workflow for
casual contributors.


On 03/13/2017 05:55 PM, Jonathan Haddad wrote:
> Ugh... Let's put a few facts out in the open before we start pushing to
> move back to the wiki.
>
> First off, take a look at CASSANDRA-8700.  There's plenty of reasoning for
> why the docs are now located in tree.  The TL;DR is:
>
> 1. Nobody used the wiki.  Like, ever.  A handful of edits per year.
> 2. Docs in the wiki were out of sync w/ cassandra.  Trying to outline the
> difference in implementations w/ nuanced behavior was difficult /
> impossible.  With in-tree, you just check the docs that come w/ the version
> you installed.  And you get them locally.  Huzzah!
> 3. The in-tree docs are a million times better quality than the wiki *ever*
> was.
>
> I urge you to try giving the in-tree docs a chance.  It may not be the way
> *you* want it but I have to point out that they're the best we've seen in
> Cassandra world.  Making them prettier won't help anything.
>
> I do agree that the process needs to be a bit smoother for people to add
> stuff to the in tree side.  For instance, maybe for every features that's
> written we start creating a corresponding JIRA for the documentation.  Not
> every developer wants to write docs, and that's fair.  The accompanying
> JIRA would serve as a way for 2 or more people to collaborate on the
> feature & the docs in tandem.  It may also be beneficial to use the dev-ml
> to say "hey, i'm working on feature X, anyone want to help me write the
> docs for it?  check out CASSANDRA-XYZ"
>
> Part of CASSANDRA-8700 was to shut down the wiki.  I still advocate for
> this. At the very minimum we should make it read only with a big notice
> that points people to the in-tree docs.
>
> On Mon, Mar 13, 2017 at 8:49 AM Jeremy Hanna 
> wrote:
>
>> The moinmoin wiki was preferred but because of spam, images couldn’t be
>> attached.  The options were to use confluence or have a moderated list of
>> individuals be approved to update the wiki.  The decision was made to go
>> with the latter because of the preference to stick with moinmoin rather
>> than confluence.  That’s my understanding of the history there.  I don’t
>> know if people would like to revisit using one or the other at this point,
>> though it would take a bit of work to convert.
>>
>>> On Mar 13, 2017, at 9:42 AM, Nate McCall  wrote:
>>>
 Isn't there a way to split tech docs (aka reference) and more
 user-generated and use-case related/content oriented docs? And maybe to
>> use
 a more modern WIKI software or scheme. The CS wiki looks like 1998.
>>> The wiki is what ASF Infra provides by default. Agree that it is a bit
>>> "old-school."
>>>
>>> I'll ask around about what other projects are doing (or folks who are
>>> involved in other ASF projects, please chime in).
>>

Re: Contribute to the Cassandra wiki

[Jonathan Haddad]

Ugh... Let's put a few facts out in the open before we start pushing to
move back to the wiki.

First off, take a look at CASSANDRA-8700.  There's plenty of reasoning for
why the docs are now located in tree.  The TL;DR is:

1. Nobody used the wiki.  Like, ever.  A handful of edits per year.
2. Docs in the wiki were out of sync w/ cassandra.  Trying to outline the
difference in implementations w/ nuanced behavior was difficult /
impossible.  With in-tree, you just check the docs that come w/ the version
you installed.  And you get them locally.  Huzzah!
3. The in-tree docs are a million times better quality than the wiki *ever*
was.

I urge you to try giving the in-tree docs a chance.  It may not be the way
*you* want it but I have to point out that they're the best we've seen in
Cassandra world.  Making them prettier won't help anything.

I do agree that the process needs to be a bit smoother for people to add
stuff to the in tree side.  For instance, maybe for every features that's
written we start creating a corresponding JIRA for the documentation.  Not
every developer wants to write docs, and that's fair.  The accompanying
JIRA would serve as a way for 2 or more people to collaborate on the
feature & the docs in tandem.  It may also be beneficial to use the dev-ml
to say "hey, i'm working on feature X, anyone want to help me write the
docs for it?  check out CASSANDRA-XYZ"

Part of CASSANDRA-8700 was to shut down the wiki.  I still advocate for
this. At the very minimum we should make it read only with a big notice
that points people to the in-tree docs.

On Mon, Mar 13, 2017 at 8:49 AM Jeremy Hanna 
wrote:

> The moinmoin wiki was preferred but because of spam, images couldn’t be
> attached.  The options were to use confluence or have a moderated list of
> individuals be approved to update the wiki.  The decision was made to go
> with the latter because of the preference to stick with moinmoin rather
> than confluence.  That’s my understanding of the history there.  I don’t
> know if people would like to revisit using one or the other at this point,
> though it would take a bit of work to convert.
>
> > On Mar 13, 2017, at 9:42 AM, Nate McCall  wrote:
> >
> >> Isn't there a way to split tech docs (aka reference) and more
> >> user-generated and use-case related/content oriented docs? And maybe to
> use
> >> a more modern WIKI software or scheme. The CS wiki looks like 1998.
> >
> > The wiki is what ASF Infra provides by default. Agree that it is a bit
> > "old-school."
> >
> > I'll ask around about what other projects are doing (or folks who are
> > involved in other ASF projects, please chime in).
>
>

[GitHub] cassandra issue #98: Fix cassandra 13246

[MikkelTAndersen]

Github user MikkelTAndersen commented on the issue:

https://github.com/apache/cassandra/pull/98
  
If anything is missing please let me know and I will fix it asap...

Den 13. mar. 2017 3.09 PM skrev "Mikkel Andersen" <
mikkel.t.ander...@gmail.com>:

> Thanks Benjamin - I added a test for list, set and map. its all in this
> patch
>
> On Mon, Mar 13, 2017 at 2:02 PM, Benjamin Lerer 
> wrote:
>
>> You can look into org.apache.cassandra.cql3.vali
>> dation.entities.SecondaryIndexTest for some examples. It is where you
>> test should go.
>>
>> Otherwise just generate a patch using: git format-patch and attach the
>> output to the JIRA ticket. I guess that the problem must be there since 
3.0
>> so the patch should be for this version.
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> , or 
mute
>> the thread
>> 

>> .
>>
>
>
>
> --
> Venlig Hilsen
> Mikkel T. Andersen
> Skjoldborgvej 8
> 7100 Vejle
> Mobil: +45 40 26 79 26 <40%2026%2079%2026>
>



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Contribute to the Cassandra wiki

[Jeremy Hanna]

The moinmoin wiki was preferred but because of spam, images couldn’t be 
attached.  The options were to use confluence or have a moderated list of 
individuals be approved to update the wiki.  The decision was made to go with 
the latter because of the preference to stick with moinmoin rather than 
confluence.  That’s my understanding of the history there.  I don’t know if 
people would like to revisit using one or the other at this point, though it 
would take a bit of work to convert.

> On Mar 13, 2017, at 9:42 AM, Nate McCall  wrote:
> 
>> Isn't there a way to split tech docs (aka reference) and more
>> user-generated and use-case related/content oriented docs? And maybe to use
>> a more modern WIKI software or scheme. The CS wiki looks like 1998.
> 
> The wiki is what ASF Infra provides by default. Agree that it is a bit
> "old-school."
> 
> I'll ask around about what other projects are doing (or folks who are
> involved in other ASF projects, please chime in).

Re: Contribute to the Cassandra wiki

[Jeremy Hanna]

The moinmoin wiki was preferred but because of spam, images couldn’t be 
attached.  The options were to use confluence or have a moderated list of 
individuals be approved to update the wiki.  The decision was made to go with 
the latter because of the preference to stick with moinmoin rather than 
confluence.  That’s my understanding of the history there.  I don’t know if 
people would like to revisit using one or the other at this point, though it 
would take a bit of work to convert.

> On Mar 13, 2017, at 9:42 AM, Nate McCall  wrote:
> 
>> Isn't there a way to split tech docs (aka reference) and more
>> user-generated and use-case related/content oriented docs? And maybe to use
>> a more modern WIKI software or scheme. The CS wiki looks like 1998.
> 
> The wiki is what ASF Infra provides by default. Agree that it is a bit
> "old-school."
> 
> I'll ask around about what other projects are doing (or folks who are
> involved in other ASF projects, please chime in).

[GitHub] cassandra issue #98: Fix cassandra 13246

[MikkelTAndersen]

Github user MikkelTAndersen commented on the issue:

https://github.com/apache/cassandra/pull/98
  
I will see what you have already then : )

On Mon, Mar 13, 2017 at 1:44 PM, Benjamin Lerer 
wrote:

> @MikkelTAndersen  Could you also add
> some unit tests to your patch?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or 
mute
> the thread
> 

> .
>



-- 
Venlig Hilsen
Mikkel T. Andersen
Skjoldborgvej 8
7100 Vejle
Mobil: +45 40 26 79 26



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra issue #98: Fix cassandra 13246

[blerer]

Github user blerer commented on the issue:

https://github.com/apache/cassandra/pull/98
  
@MikkelTAndersen Could you also add some unit tests to your patch?  


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra issue #98: Fix cassandra 13246

[MikkelTAndersen]

Github user MikkelTAndersen commented on the issue:

https://github.com/apache/cassandra/pull/98
  
Ahh sorry - it seems to complicated, its a simple null check - any chance
you can add it Alex ? I have attached the patch.

On Mon, Mar 13, 2017 at 1:38 PM, Alex Petrov 
wrote:

> Hi @MikkelTAndersen . Cassandra does
> not use pull requests for Apache Cassandra. Please use JIRA directly.
>
> You can get more information on the contribution process here
> https://wiki.apache.org/cassandra/HowToContribute
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or 
mute
> the thread
> 

> .
>



-- 
Venlig Hilsen
Mikkel T. Andersen
Skjoldborgvej 8
7100 Vejle
Mobil: +45 40 26 79 26

From dac39d0268ba82b6be033e0c63ebd653ae0517cc Mon Sep 17 00:00:00 2001
From: Mikkel Andersen 
Date: Mon, 13 Mar 2017 10:21:27 +0100
Subject: [PATCH] added null check - see CASSANDRA-13246

---
 .../org/apache/cassandra/db/filter/RowFilter.java  | 22 
--
 1 file changed, 12 insertions(+), 10 deletions(-)

diff --git a/src/java/org/apache/cassandra/db/filter/RowFilter.java 
b/src/java/org/apache/cassandra/db/filter/RowFilter.java
index bf65e96..c26c1ad 100644
--- a/src/java/org/apache/cassandra/db/filter/RowFilter.java
+++ b/src/java/org/apache/cassandra/db/filter/RowFilter.java
@@ -611,17 +611,19 @@ public abstract class RowFilter implements 
Iterable
 if (column.isComplex())
 {
 ComplexColumnData complexData = 
row.getComplexColumnData(column);
-for (Cell cell : complexData)
-{
-if (type.kind == CollectionType.Kind.SET)
-{
-if 
(type.nameComparator().compare(cell.path().get(0), value) == 0)
-return true;
-}
-else
+if (complexData != null) {
+for (Cell cell : complexData)
 {
-if 
(type.valueComparator().compare(cell.value(), value) == 0)
-return true;
+if (type.kind == CollectionType.Kind.SET)
+{
+if 
(type.nameComparator().compare(cell.path().get(0), value) == 0)
+return true;
+}
+else
+{
+if 
(type.valueComparator().compare(cell.value(), value) == 0)
+return true;
+}
 }
 }
 return false;
-- 
2.0.1

From 145087e3b5d748ce25e8792f91c249d2a05de3e5 Mon Sep 17 00:00:00 2001
From: Mikkel Andersen 
Date: Mon, 13 Mar 2017 10:22:53 +0100
Subject: [PATCH] fixed formatting

---
 src/java/org/apache/cassandra/db/filter/RowFilter.java | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/java/org/apache/cassandra/db/filter/RowFilter.java 
b/src/java/org/apache/cassandra/db/filter/RowFilter.java
index c26c1ad..d3fc301 100644
--- a/src/java/org/apache/cassandra/db/filter/RowFilter.java
+++ b/src/java/org/apache/cassandra/db/filter/RowFilter.java
@@ -611,7 +611,8 @@ public abstract class RowFilter implements 
Iterable
 if (column.isComplex())
 {
 ComplexColumnData complexData = 
row.getComplexColumnData(column);
-if (complexData != null) {
+if (complexData != null)
+{
 for (Cell cell : complexData)
 {
 if (type.kind == CollectionType.Kind.SET)
-- 
2.0.1




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact 

[GitHub] cassandra issue #98: Fix cassandra 13246

[ifesdjeen]

Github user ifesdjeen commented on the issue:

https://github.com/apache/cassandra/pull/98
  
Hi @MikkelTAndersen. Cassandra does not use pull requests for Apache 
Cassandra. Please use JIRA directly.

You can get more information on the contribution process here 
https://wiki.apache.org/cassandra/HowToContribute


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra issue #98: Fix cassandra 13246

[MikkelTAndersen]

Github user MikkelTAndersen commented on the issue:

https://github.com/apache/cassandra/pull/98
  
This is a simple fix for when you query with CONTAINS and the collection is 
empty (which ends up as null in the database) ... this is a blocking issue for 
my company so would appreciate if it could get into the next release.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #98: Fix cassandra 13246

[MikkelTAndersen]

GitHub user MikkelTAndersen opened a pull request:

https://github.com/apache/cassandra/pull/98

Fix cassandra 13246

This should fix null pointer if the content of the column is null.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MikkelTAndersen/cassandra fix_CASSANDRA-13246

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/98.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #98


commit dac39d0268ba82b6be033e0c63ebd653ae0517cc
Author: Mikkel Andersen 
Date:   2017-03-13T09:21:27Z

added null check - see CASSANDRA-13246

commit 145087e3b5d748ce25e8792f91c249d2a05de3e5
Author: Mikkel Andersen 
Date:   2017-03-13T09:22:53Z

fixed formatting




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Contribute to the Cassandra wiki

[benjamin roth]

First: I am positively surprised how many guys would like to contribute to
docs.

Some days ago I posted to the dev-list about doc-contribution. I think this
applies here again. From my point of view "in-tree docs" are a good choice
for technical references that go closely with the code versioning.
But for content-oriented docs like tutorials, FAQs, Knowledge base I think
this is not a good place especially if the doc-contributors are not that
deeply involved into dev/code.
For that purpose, Stefan Podkowinsky created a repo for collaboration that
"Proxies" access to the CS repo. Thats a nice gesture but IMHO that can
only work as an intermediate solution. "User-Docs" do not require a CI or
complex build + publishing process. They require a simple and "beautiful"
way to contribute. Especially if you wish to encourage more "outside" users
to contribute.

Isn't there a way to split tech docs (aka reference) and more
user-generated and use-case related/content oriented docs? And maybe to use
a more modern WIKI software or scheme. The CS wiki looks like 1998.


2017-03-12 23:26 GMT+01:00 Jeff Jirsa :

> We're trying to use the in-tree docs. Those are preferred, updating the
> wiki is OK, but the wiki is VERY out of date.
>
> --
> Jeff Jirsa
>
>
> > On Mar 12, 2017, at 3:21 PM, Long Quanzheng  wrote:
> >
> > Is the wiki still being used?
> > https://wiki.apache.org/cassandra
> > says:
> > Cassandra is moving away from this wiki for user-facing documentation in
> > favor of in-tree docs, linked below. (Pull requests welcome
> > !)
> >
> >
> > 2017-03-12 14:21 GMT-07:00 Brandon Williams :
> >
> >> I've added you.
> >>
> >> On Sun, Mar 12, 2017 at 1:43 PM, ThisHosting.Rocks! <
> >> contact@thishosting.rocks> wrote:
> >>
> >>> Hi,
> >>>
> >>>
> >>> My username is NickReiner and I'd like to contribute to the Cassandra
> >> wiki.
> >>>
> >>> Please. :)
> >>>
> >>> Nick Reiner
> >>> THR Support.
> >>>
> >>
>