Hi Anthony, Benjamin, all,
I am back :)
So I closed two tiny tickets(CASSANDRA-16894 and CASSANDRA-17182) with docs
and website updates last week and in my opinion things are quite
straightforward if there are no additional changes to script/process
planned. (Thanks Mick for confirming things for
Hi Anthony,
Great news! Thanks everyone for all the work and time invested. IMHO docs
are as important as well written code.
“Would we reopen it to fix the problem or would we open a new ticket? Do we
have project guidelines around this? I would think in this scenario a new
ticket would be create
It seems to me that we could use that work to attract new contributors.
If we provide some clear process and divide the work in small chunks we can
advertise the work on Twitter to get some volunteers. :-)
Le lun. 10 janv. 2022 à 07:59, Anthony Grasso a
écrit :
> Hi Stefan and Ekaterina,
>
> Fi
Hi Stefan and Ekaterina,
First point to note is CASSANDRA-16763 is now closed. A big thank you to
Lorina Poland for converting the Cassandra documentation from
reStructuredText to AsciiDoc and to Mick Semb Wever for working over the
holiday period to get the ticket over the line! We are now at a p
Hey Stefan,
Thank you for your support and spending the time to think about this.
If I understand you correctly, you suggest reopening the old tickets to
finish the docs, I have two concerns:
- we might work a few times on one and the same doc until we bring it to
the latest state instead of gett
Hey,
I got an idea how this might be simplified.
Every commit in Cassandra repository belongs to a ticket (except
ninjas but they are irrelevant here).
So if you look over the commits, what about looking at what Jira
ticket they belong to (this information is in each commit message) and
then go
Hi Stefan,
I agree with your thoughts around grouping together changes touching a
subsystem. This is exactly how I started doing the backporting work a few
weeks ago. For example I started by looking at all the changes in the
'doc/source/architecture' folder of the rST docs, and back ported only
t
Hey Stefan,
Thank you for your response.
“If it was feasible to gather all related changes touching a subsystem
under one umbrella ticket, that would be very nice but I do not know
if that makes sense from your point of view (what workflow you have).”
It is up to us to decide what would be the m
Hi Lorina, Ekaterina,
In general your approach sounds good to me. I am also +1 on not
creating too many tickets as I can see it will be easy to get lost in.
If it was feasible to gather all related changes touching a subsystem
under one umbrella ticket, that would be very nice but I do not know
i
Hey Lorina,
First of all - thank you so much for all the work done by you and the rest
of the people! The website and the docs are our front door as a project!
+1 on your proposal. My understanding is we need 1)+5) and then everything
else will be able to roll out and more people will be able to
Thanks Lorina for all your work.
+1 Your proposal makes sense to me.
Le mer. 6 oct. 2021 à 00:34, Lorina Poland a écrit :
> This is a discussion about how to tackle getting the docs “fixed”.
>
> As many of you know, I started months ago to convert the Apache Cassandra
> in-tree docs
> from reSt
This is a discussion about how to tackle getting the docs “fixed”.
As many of you know, I started months ago to convert the Apache Cassandra
in-tree docs
from reStructedText (rST)to AsciiDoc. [1]
The conversion required both the docs source files to be converted, but
also the cassandra-website
sou
12 matches
Mail list logo
