[
https://issues.apache.org/jira/browse/SOLR-16121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513935#comment-17513935
]
Jan Høydahl commented on SOLR-16121:
------------------------------------
IMO the confluence page is so bloated and discusses too many topics too
in-depth for one page.
I'd like for solr to have a CONTRIBUTING.md file similar to Lucene's just for
getting started, running tests and producing a PR. Then iterate from there,
adding content to dev-docs/ folder for more detailed content such as frequently
failing tests, beasting or whatever. I'm even willing to refer to dev-docs for
the patch-in-Jira approach and focus only on PR flow to keep the initial guide
compact.
> Move "how to contribute" documentation to the git repo (convert the wiki to
> CONTRIBUTING.md)
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-16121
> URL: https://issues.apache.org/jira/browse/SOLR-16121
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tomoko Uchida
> Priority: Minor
>
> The same as [LUCENE-10184]. (this was suggested also for solr in there)
> I reviewed [How to Contribute to
> Solr|https://cwiki.apache.org/confluence/display/solr/HowToContribute]. Its
> volume is far larger than that of lucene and it says some contents "needs
> reworking" (also some too old information should be cleaned up to me).
> Copy-pasting the contents wouldn't work, but sadly, I don't think I can make
> it up-to-date... I hope developers who have the knowledge to reorganize the
> information take over this issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
