Unlike in 2019, GSoD does not provide a budgetary service, and the applicant
organization would need to submit a budget including an account detail, which
Apache Cassandra does not have, I assume, and the following message from GSoD
provides the info about getting an account; the message is received by
contacting GSoD directly and not in the GSoD official page.
Thank you for reaching out, Deepak.
If you don’t have a bank account for your project, you can sign up with Open
Source Collective to be your fiscal host, which means they will hold the funds
on your behalf as you pay them out. No fees from Open Source Collective will
apply to your grant payment. You can find more information on grants and
opening an Open Collective account here or email Open Collective directly for
more information through [email protected].
|
|
|
| | |
|
|
|
| |
Grants for organizations | Google Season of Docs | Google Developers
|
|
|
Regarding technical writers, please review the selecting a technical writer
guide and our GitHub page.
Best,Season of Docs team
On Wednesday, February 1, 2023 at 02:08:37 p.m. EST, Lorina Poland
<[email protected]> wrote:
I've not had any comment on this topic. Can I assume that no one has
objections?
Lorina
On 2023/01/25 19:02:41 Lorina Poland wrote:
> Greetings!
>
> I'm gearing up to help get the Cassandra 5.0 docs in good order before the
> GA release occurs later this year. Recently, I've been thinking about a
> more standardized organization to docs, to make it simpler for users to
> find what they are looking for, separate from searching. [That's the kind
> of thing docs nerds think about.] To that end, I've created a unified
> information architecture (IA) that can apply to any kind of documentation,
> including the Apache C* docs.
>
> Up front, I'll say, not every section of this organization applies to
> Apache C* docs, but reorganizing the docs to follow this pattern as much as
> possible will help users find what they need.
>
> I'd like your input into this IA that I've outlined. Please give me
> feedback about your opinions! If I can tackle this issue before launching
> into adding CEP features, working down the existing JIRA tickets for
> documentation, and backfilling missing items, it would be immensely
> helpful. No opinion will go unaddressed, so please take a few minutes to
> take a look.
>
> I'm linking a google doc, to make it easy for anyone to make comments:
> https://docs.google.com/document/d/1A96K73vj9MbJoD7wJNgIKWrOkLq-ZL2cNZAEXSWrciY/edit?usp=sharing
>
> I'm also drafting an Apache C* 5.0 Doc Plan for the work, to make it simple
> for anyone to know what is being done, and will share that next. In
> addition, I've started consolidating the current Documentation tickets that
> are open under the JIRA project, component "Documentation".
>
> Thanks,
> Lorina Poland
>
