I think we're good with respect to JIRA.

Ed and I discussed JIRA tickets a bit off-list. I don't have the
authoritative answer, but I'm guessing most tickets are currently
indexable. For example, searching Google for

  site:issues.apache.org inurl:fineract loan

returns many tickets in search results, such as FINERACT-2020 and
FINERACT-1721.

I'm not a robots.txt expert, but this is what I'd expect given explicit
permission for Google's spiders in https://issues.apache.org/robots.txt and
nothing blocking JIRA issue indexing in
https://issues.apache.org/jira/robots.txt . Looks like DuckDuckGo/Bing and
Archive.org are also indexing our JIRA tickets.

We did notice some search result idiosyncrasies for queries across
different search engines, but I don't find this surprising. Who knows how
these things actually work.

Re: Slack, Ed wrote:

> https://gist.github.com/shubhampal62/f7e5331dc58af05f19e959f847c9d3e5


I see "Slack conversations were manually scraped out from the respective
slack channels" in that gist, so I'm not clear on how they actually got the
data... maybe a one-off manual export?

I do still think it's a good idea to 1. automatically capture Slack
messages and 2. post them somewhere online/public/index-able). The messages
are a valuable community asset. #2 seems easily solvable. I would think it
would also be easy / automatic to do #1, but if there's a way I haven't
found it. Maybe I'm using the wrong search terms, or not doing the obvious
thing (reviewing Slack settings / API). The LLM I asked seems to think it
would be pretty easy to write a message logger, but I'm not convinced and I
didn't try running the code it generated.

I created https://issues.apache.org/jira/browse/FINERACT-2171 : "make Slack
messages discoverable by search engines". If you agree that's of value,
please add a vote. Maybe that'd be a good student/intern/first contribution.

I forget how we did this with IRC in the old days. I think a 3rd party
service's bot sat in the channel, logging and posting messages somewhere
online, but I can't find that now.

Reply via email to