bfallik commented on pull request #35774: URL: https://github.com/apache/spark/pull/35774#issuecomment-1064169342
Hi @itholic , Please know that I appreciate all the hard work, often thankless, that project committers undertake to try and manage community activity into a sensible workflow, but this is starting to feel like a lot of back-and-forth for a documentation change to correct an obvious misspelling. I did review the contribution guidelines before posting this PR. The section on "Contributing documentation changes" says > To propose a change to release documentation (that is, docs that appear under https://spark.apache.org/docs/), edit the Markdown source files in Spark’s [docs/](https://github.com/apache/spark/tree/master/docs) directory, whose README file shows how to build the documentation locally to test your changes. The process to propose a doc change is otherwise the same as the process for proposing code changes below. and, notably, the section on "Contributing code changes" says > 2. If the change is new, then it usually needs a new JIRA. However, trivial changes, where the what should change is virtually the same as the how it should change do not require a JIRA. Example: Fix typos in Foo scaladoc I read that example and assumed this trivial change didn't need a JIRA ticket. I'll go ahead and edit the description to address your most recent suggestion. Appreciate your help getting the automated checks to pass. Thanks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
