Normalize contribution docs with Briefcase/Toga #428
Labels
documentation
An improvement required in the project's documentation.
enhancement
New features, or improvements to existing features.
good first issue
Is this your first time contributing? This could be a good place to start!
What is the problem or limitation you are having?
Rubicon has a contribution guide for docs and code; so do Toga and Briefcase. However, there are some elements of the Toga and Briefcase docs that would be useful to include in the Rubicon docs.
Describe the solution you'd like
Replicate the sections of the Toga and Briefcase contribution guides that aren't Briefcase- or Toga-specific in the Rubicon docs. The one section I've noticed in particular is the discussion about running CI checks locally as part of the PR submission process; there may be others.
Describe alternatives you've considered
Consolidate these docs upstream (on the beeware.org website) so that the content isn't duplicated unnecessarily. However, developing a good narrative flow with an external site like that may be complex.
Additional context
See also beeware/briefcase#1696, beeware/toga#2453.
The text was updated successfully, but these errors were encountered: