Hi James, I would definitely be interested in helping. For task b, what would be considered a linkback? The PR should directly have a reference to the JIRA Ticket URL? Also, what would be the preferred form to highlight that?
Thanks in advance! On Tue, Oct 1, 2024 at 2:41 PM James Dailey <jdai...@apache.org> wrote: > So, there are a few tasks I would see if any new contributor would like to > take on... > > The theme is making the project more transparent and accessible to devs > and new community members. > > Go through the existing PRs in recent weeks or months and find: > a) If any of them relate to the existing FSIPs. If so, create a link to > the Jira ticket and the PR on the FSIP wiki pages. > For example, create a link on the Wiki page for Cucumber tests. > https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Significant+Improvement+Proposals > <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Significant+Improvement+Proposals> > > b) if any PR in Github is missing a linkback to a Jira ticket, identify > and highlight > > c) if any PR is for a ticket that is closed or marked for a previous > release, highlight that. > > For more experienced contributors, go through the Wiki Pages and suggest, > in an email post, which sections of the wiki are out of date or that need a > refresh, or to be deleted. > > That is, perhaps create a list of specific wiki pages that should be > removed, or marked deprecated. > e.g. > Deprecate or update?: > https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI > > <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI> > > We also have hundreds of Jira tickets that are open but not being worked > on... there is a lack of information on those tickets. There is a need to > either close them as "will not fix" or archive, or validate that they are > still useful to have as "should be worked on". > > >
