Re: Contribute to the Cassandra Wiki

[Dave Brosius]

done

---


On 2017-03-17 06:02, Rahul S wrote:

Hi
I would like to contribute to the Cassandra wiki please. My username
is rahul3.

Thanks
Rahul

From Alia to Anushka, Arijit to Armaan, Papon to Pritam, Sonu to
Sukhwinder and Varun to Diljit - the biggest music and Bollywood stars
say Music ko Mirchi ka Salaam! Catch the Royal Stag Mirchi Music
Awards on 19th March at 8 PM on Zee TV.

Contribute to the Cassandra Wiki

[Rahul S]

Hi
I would like to contribute to the Cassandra wiki please. My username is 
rahul3.

Thanks
Rahul

From Alia to Anushka, Arijit to Armaan, Papon to Pritam, Sonu to Sukhwinder and 
Varun to Diljit - the biggest music and Bollywood stars say Music ko Mirchi ka 
Salaam! Catch the Royal Stag Mirchi Music Awards on 19th March at 8 PM on Zee 
TV.

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).
>
>

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).

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 <jji...@gmail.com>:

> 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 <prc...@gmail.com> 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
> > <https://github.com/apache/cassandra/tree/trunk/doc>!)
> >
> >
> > 2017-03-12 14:21 GMT-07:00 Brandon Williams <dri...@gmail.com>:
> >
> >> 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.
> >>>
> >>
>

Re: Contribute to the Cassandra wiki

[Dave Brosius]

You've been added


On 03/12/2017 07:14 PM, Anthony Grasso wrote:

Hi

My username is AnthonyGrasso and I would like to contribute to the
Cassandra wiki please.

Kind regards,
Anthony

Contribute to the Cassandra wiki

[ThisHosting.Rocks!]

Hi,


My username is NickReiner and I'd like to contribute to the Cassandra wiki.

Please. :)

Nick Reiner
THR Support.

Contribute to the Cassandra wiki

[Anthony Grasso]

Hi

My username is AnthonyGrasso and I would like to contribute to the
Cassandra wiki please.

Kind regards,
Anthony

Re: Contribute to the Cassandra wiki

[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 <prc...@gmail.com> 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
> <https://github.com/apache/cassandra/tree/trunk/doc>!)
> 
> 
> 2017-03-12 14:21 GMT-07:00 Brandon Williams <dri...@gmail.com>:
> 
>> 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.
>>> 
>> 

Contribute to the Cassandra Wiki

[Long Quanzheng]

Hi,
My username is qlong. I would like to contribute to the wiki.

Thanks,
Quanzheng Long

Re: Contribute to the Cassandra wiki

[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.
>

Re: Would like to contribute to Apache/Cassandra wiki

[Dave Brosius]

try now


On 08/10/2016 12:13 PM, Danielle Blake wrote:

Hi,
I would like to contribute to https://wiki.apache.org/
cassandra/ThirdPartySupport
I would like to get the Company I work for, OpenCredo
, on this page.

Username: Danielle Blake

Kind regards,

Danielle Blake

Marketing Executive

M. +44 (0) 7403 565 785

T.  +44 (0) 207 928 9200

Opencredo.com . Twitter  . LinkedIn


OpenCredo Ltd -- Excellence in Enterprise Application Development

Registered Office:  5-11 Lavington St, London SE1 0NZ

Registered in UK. No 3943999

If you have received this e-mail in error please accept our apologies,
destroy it immediately and it immediately and it would be greatly
appreciated if you notified the sender.  It is your responsibility to
protect your system from viruses and any other harmful code or device.
We try to eliminate them from e-mails and attachments; but we accept no
liability for any that remain. We may monitor or access any or all
e-mails sent to us.

Re: Would like to contribute to Apache/Cassandra wiki

[Danielle Blake]

>
> Hi,
> I would like to contribute to https://wiki.apache.org/
> cassandra/ThirdPartySupport
> I would like to get the Company I work for, OpenCredo
> , on this page.
>
> Username: Danielle Blake
>
> Kind regards,
>
> Danielle Blake
>
> Marketing Executive
>
> M. +44 (0) 7403 565 785
>
> T.  +44 (0) 207 928 9200
>
> Opencredo.com . Twitter  . LinkedIn
> 
>
> OpenCredo Ltd -- Excellence in Enterprise Application Development
>
> Registered Office:  5-11 Lavington St, London SE1 0NZ
>
> Registered in UK. No 3943999
>
> If you have received this e-mail in error please accept our apologies,
> destroy it immediately and it immediately and it would be greatly
> appreciated if you notified the sender.  It is your responsibility to
> protect your system from viruses and any other harmful code or device.
> We try to eliminate them from e-mails and attachments; but we accept no
> liability for any that remain. We may monitor or access any or all
> e-mails sent to us.
>
>

-- 


opencredo.com  . Twitter 
 . LinkedIn 



OpenCredo Ltd -- Excellence in Enterprise Application Development

Registered Office:  5-11 Lavington Street, London, SE1 0NZ
Registered in UK. No 3943999

Want to contribute to the Cassandra wiki

[Suraiya Khan]

Hi there,
I would like to contribute to the wiki.

My wiki user name: SuraiyaKhan

Thanks.

Suraiya

Re: Want to contribute to the Cassandra wiki

[Suraiya Khan]

Sorry the user name is: Suraiya Khan (ther is a space in between)

Thanks.

On Wed, Jun 22, 2016 at 12:43 AM, Suraiya Khan 
wrote:

> Hi there,
> I would like to contribute to the wiki.
>
> My wiki user name: SuraiyaKhan
>
> Thanks.
>
> Suraiya
>