[ 
https://issues.apache.org/jira/browse/FINERACT-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18056802#comment-18056802
 ] 

Adam Monsen edited comment on FINERACT-2171 at 2/6/26 4:44 AM:
---------------------------------------------------------------

[~airajena] thanks. Did you create that doc by hand, or was it 
AI-assisted/generated? If the latter, what AI did you use, and what was the 
prompt?

Do you plan on using AI tools when you get to coding? Which ones?

Maybe just start small with something–anything–that works. Study the Slack API 
and figure out what's doable. Make some test scripts that work. I'll try them 
too.

 
{quote}Language: Java, Build tool: Gradle
{quote}
If you want. Or Groovy. Or Python. Python might be better suited for this kind 
of work, now that I think about it. There's nothing there yet so use whatever 
of these you're comfortable with.
{quote}Output: AsciiDoc rendered by GitHub Pages
{quote}
GitHub Pages uses jekyll, doesn't it? And 
[https://jekyllrb.com|https://jekyllrb.com/] says sources are markdown, liquid, 
html, and css. CSV might also be handy--it's up to you. Just use whatever makes 
the most sense with GitHub Pages.
{quote}Archive messages from a configured allowlist of public channels
{quote}
Sounds good. Initially this list is just {{#fineract}} on the Mifos Slack 
server.
{quote}Store one AsciiDoc file per day
{quote}
Sure, or, more likely, markdown.
{quote}Data Model
{quote}
Why store both {{ts}} and {{{}date{}}}?
{quote}Output Format: Time (UTC)
{quote}
Yes. Good. Maybe localize to user's timezone if you have that from the web 
browser.
{quote}Idempotency: Only re-render affected days if edits or deletions are 
detected
{quote}
How will these be detected?

Maybe it's obvious, but it wouldn't hurt to be explicit that we're adding any 
new messages since last cursor position (time/date).


was (Author: meonkeys):
[~airajena] thanks. Did you create that doc by hand, or was it 
AI-assisted/generated? If the latter, what AI did you use, and what was the 
prompt?

Do you plan on using AI tools when you get to coding? Which ones?

Maybe just start small with something–anything–that works. Study the Slack API 
and figure out what's doable. Make some test scripts that work. I'll try them 
too.

 
{quote}Language: Java, Build tool: Gradle
{quote}
If you want. Or Groovy. Or Python. Python might be better suited for this kind 
of work, now that I think about it. There's nothing there yet so use whatever 
of these you're comfortable with.
{quote}Output: AsciiDoc rendered by GitHub Pages
{quote}
GitHub Pages uses jekyll, doesn't it? And 
[https://jekyllrb.com|https://jekyllrb.com/] says sources are markdown, liquid, 
html, and css. CSV might also be handy--it's up to you. Just use whatever makes 
the most sense with GitHub Pages.
{quote}Archive messages from a configured allowlist of public channels
{quote}
Sounds good. Initially this list is just {{#fineract}} on the Mifos Slack 
server.
{quote}Store one AsciiDoc file per day
{quote}
Sure, or--more likely--markdown.
{quote}Data Model
{quote}
Why store both {{ts}} and {{{}date{}}}?
{quote}Output Format: Time (UTC)
{quote}
Yes. Good. Maybe localize to user's timezone if you have that from the web 
browser.
{quote}Idempotency: Only re-render affected days if edits or deletions are 
detected
{quote}
How will these be detected?

Maybe it's obvious, but it wouldn't hurt to be explicit that we're adding any 
new messages since last cursor position (time/date).

> make Slack messages discoverable by search engines
> --------------------------------------------------
>
>                 Key: FINERACT-2171
>                 URL: https://issues.apache.org/jira/browse/FINERACT-2171
>             Project: Apache Fineract
>          Issue Type: Wish
>          Components: Docs
>            Reporter: Adam Monsen
>            Priority: Minor
>         Attachments: FINERACT-2171-implementation-plan-v2.md, 
> FINERACT-2171-implementation-plan.md, screenshot-1.png
>
>
> To improve discoverability of Fineract knowledge, lessons learned, and 
> actions taken, let's automatically capture Slack messages and post them 
> somewhere online/public/index-able.
> See also: 
> [https://lists.apache.org/thread/rlqx239p10xt8w9odmh27ojto25r147w|https://lists.apache.org/thread/zf3zmblj96mqo9gl69tpgz5xorzxgw3z]
> Acceptance criteria suggestion: {*}a web search for, e.g. "mifos fineract 
> mockito" returns relevant Slack messages{*}. A similar criteria should be 
> useful for improving index-ability of issues, patches, mailing list messages, 
> etc.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to