Another challenge I've seen is trying to connect the code it github to the documentation on the site (and visa versa). I wonder if a low effort option would be to add a metadata field for the project(s) to link documentation pages in github, something like:
title=Test Page type=page status=published tags=tag1,tag2 repos=auth-form,scripting-jsp-taglib ~~~~~~ And that would render links either at the top or bottom of the page to: - https://github.com/apache/sling-org-apache-sling-auth-form - https://github.com/apache/sling-org-apache-sling-scripting-jsp-taglib Without updating all the README's manually I'm not sure how to fix things in GitHub side, but that'd be helpful as well. On Wed, Mar 6, 2019 at 12:43 PM Stefan Seifert <[email protected]> wrote: > > To spot those stale PRs we can consider building a dashboard of open > pull requests. Alternatively, an automated email once per week to dev@sling > mightalso work (or might get ignored). > > i think this would be very helpful. PRs often get overlooked in all the > mail traffic. > mail report would be fine - if we make sure that those PRs which were > added since the last mail report are listed separately from the old ones to > easily spot what is new. > > stefan > >
