Finding a confluence macro to display all tagged pages for improvement is one of the objective of the project. Does all these macros or solutions that we are going to propose should be free solutions? I have found really good confluence, JIRA, trello integration tools and macros where some are free only upto a certain limit.
It’s preferable to leverage features that are built into Confluence wherever possible. We try to limit use of third party plugins, since they require maintenance and attention and can make the wiki less stable.
For example, confluence has built-in macros to list pages by characteristics (e.g., labels).
Thanks @uthpala for making this post. I am also interested in this project for GSOD 2020.
I am doing warm up practises for GSOD 2020 and working on trello tasks too.
May I know that OpenMRS uses both JIRA and Trello now? In the future is there any plan to have only a single mechanism to record tasks or to have both ways?
Now Wiki page can be edited by any OpenMRS member. Is it a practise that we need to continue? Is that okay to limit the page for few people like the page who created and recently edited so that there can be control over wiki pages.
the wiki pages are always edited by every member and since we are a big community,so many good things can be added on wiki and we cannot limit others,what we do is always to overlook the changed pages
As i was iterating through the solutions of finding outdated pages (pages not modified for a year) in Active Projects, i decided to use the already existing CQL search macro to search the pages that have not been modified by a year. I named the page Outdated pages (but the name can re-edited to what makes more meaning).
Another alternative I hard was to create a macro that displays or hides information (an alert stating “This page is Outdated”) depending on a certain condition (date of last modification of the page). This became hard to achieve because even if i hard managed to create it, pasting it on every descendant pages in Active Projects page would modify the lastModified date so i decided to cancel out that option. Unless their is another alternative.
The alternative i opted for was able to reduce entropy (i suppose) since i reused an existing feature.
However, am now a little puzzled, on the idea of finding pages that are duplicated, what is the best option to use? If i continue with the Confluence macro, Should i use this same page, change its name like to "OpenMRS conflicting pages", and create two sections: a) Labled “Outdated Pages” and b) “Duplicated pages”?
If that’s the best alternative should i search by title? But some pages share common content but different titles. How best can i write a querry to compare contents in each and every page to find out if the page has been duplicated or not?
The requirements of this project are really not so specific (to me). I request @jennifer, @herbert24 (mentors) and any member of the community willing to help, to please give us more details of what this project requires, beyond just ensuring that pages aren’t both duplicated and outdated?