For completeness, I'll mention that there was a short-lived effort 13 years ago to make a catalog of keywords to use; see https://wiki.sagemath.org/TracKeywords?action=info
On Thursday, September 28, 2023 at 12:46:57 PM UTC-7 Matthias Koeppe wrote: > On Trac, keywords were completely free-form; there was nothing to click, > and there wasn't an agreement whether multiple keywords are separated by > whitespaces or commas or semicolons. > > In the migration, we did a frequency count of words and phrases used there > and transformed some of the most frequently used key words and phrases to > "c: " labels or other labels. See > https://github.com/sagemath/trac-to-github/blob/master/migrate.cfg.sagetracmigrationarchive#L44 > > On Thursday, September 28, 2023 at 10:28:00 AM UTC-7 Martin R wrote: > >> I would like to have trac keywords back. Searching issues in github >> seems quite difficult, for example, it seems that wildcards are not >> supported: >> >> "is:pr is:open lazypower" finds nothing wereas "is:pr is:open >> lazypowerseries" does. >> >> On trac, I used keywords to collect the issues that concerned me and make >> them available on one click. I.e., whenever someone submitted something >> about "FriCAS", I added that keyword, or "LazyPowerSeries", or "species". >> Of course, I can add keywords myself now, as I could do on trac, but on >> trac it was easier to remember the keywords I used, because they were >> available by one click. >> >> Is there another way to achieve something similar? >> >> Martin >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/930d9c1e-0299-457d-a850-e1c0482a7b44n%40googlegroups.com.
