Looks good to me! 🍻
On Wed, 16 Mar 2022 at 08:17, Chris Thornett wrote:
> As requested, I'm posting content contributions for community review on
> the ML for those that might not spot them on Slack.
>
> We're currently mid-review for our first contributor Q&A which is with
> Lorina Poland:
>
>
As requested, I'm posting content contributions for community review on the
ML for those that might not spot them on Slack.
We're currently mid-review for our first contributor Q&A which is with
Lorina Poland:
https://docs.google.com/document/d/1nnH4V1XvTcfTeeUdZ_mjSxlNlWTbSXFu_qKtJRQUFBk/edit.
Pl
Thanks, Rags. But if this is for ApacheCon then we're not quite there yet.
The Cassandra track has to be accepted first before we can send out a call
for papers so stay tuned for details. Cheers!
On Wed, 16 Mar 2022 at 01:36, Raghavan "Rags" N. Srinivas
wrote:
> Hi all:
>
> I would like to make
Hi all:
I would like to make a submission and help out with this effort.
How do we get this started?
Thanks!
Rags
Hi,
I hope it’s OK I jump to the discussion.
I find it is important to automate code formatting and have a build check to
verify it, otherwise there are many examples in other projects that formatting
is not followed. To make formatting to be not painful for contributors it will
be good to set
I agree with the single commit approach to fix it all. TBH Javadocs
are a little bit messy as well, warnings on generating them,
incomplete, in a lot of cases obsolete or they do not reflect the code
anymore etc.
On Tue, 15 Mar 2022 at 09:44, bened...@apache.org wrote:
>
> I’d be fine with that,
I’d be fine with that, though I think if we want to start enforcing imports we
probably want to mass correct them first. It’s not like other style
requirements in that there should not be unintended consequences. A single
(huge) commit to standardise the orders and introduce a build-time check w
