It always surprises me to see a large unexpected patch, but I get why people do that sometimes. I've done it too. Hopefully this email isn't like that. :-)
I did see large patches mentioned at https://cwiki.apache.org/confluence/display/FINERACT/Pull+Request+Size+Limit and https://cwiki.apache.org/ confluence/display/FINERACT/Take+Your+First+Steps#TakeYourFirstSteps-Discussnon-trivialcontributionideaswiththecommunity which is great, but it did take me a while to read through many contributor / getting started docs: https://github.com/apache/fineract#community https://github.com/apache/fineract#developers https://github.com/apache/fineract/blob/develop/CONTRIBUTING.md https://fineract.apache.org/docs/current/#_contribute https://cwiki.apache.org/confluence/display/FINERACT/Take+Your+First+Steps https://cwiki.apache.org/confluence/display/FINERACT/Fineract+101 https://fineract-academy.com How about if we consolidate those so there's one first/best place contributors can start (and developers can refer to), and the rest just links there (as much as possible)? If that sounds like a good idea, what's that "best" place? Maybe the asciidoc published regularly to https://fineract.apache.org/docs/ ? https://fineract.apache.org/docs/ appears to be regularly spidered/indexed, at least, I'm able to easily and quickly find info there using my favorite web search engine. I forget if I made that explicit back in my old Mifos days, but that was definitely a goal of mine that as much as possible about (ye olde) Mifos development activity / documentation / chats / emails was (besides it being high-quality) that it always be index-able by search engines. Is this a goal of the Fineract community? Assuming yes... How about if we make Fineract-relevant Slack channels searchable? Has anyone looked into this? By way of example: Mike and James discussed Scarf the other day <https://lists.apache.org/thread/vnvdowzrhp9lxd6ogy3996h75y47lzzf>. I brought it up with James back in December and we discussed it in the ASF Slack #fineract channel <https://the-asf.slack.com/archives/C4QPZURQQ/p1734055342213539>. I mention it again here not to re-hash it, but to point out that our conversation is behind a registration wall. I get that it's free to register, but I don't like that you can't search the web to read our discussion. I'm happy to help with any/all of my suggestions above. On Sun, Jan 12, 2025 at 10:25 AM James Dailey <jdai...@apache.org> wrote: > hi - to rephrase my earlier email, thank you for the contribution > "AryanVBW" and please, it would be nice to have an introduction. Are you > subscribed to the listserv? How are you involved in using fineract? > > I think these changes are significant enough and anyway are the "front > door" of our project : i.e. our Website home page. So, in that way, I > think that they should be discussed first here on the listserv at least a > little bit. I'm supportive of the changes, with a few tweaks. I'm now > making comments on github. So, thank you. > > > > > On Sun, Jan 12, 2025 at 9:08 AM Ádám Sághy <adamsa...@gmail.com> wrote: > >> Hi >> >> Usually I dont mind any visual upgrade, but personally I really dont like >> this hover effect which moves the hovered item with a couple pixels up and >> to the right... 😵 >> >> The rest looks okay to me but this hover effect makes me dizzy...😵💫 >> >> Regards, >> Adam Saghy >> >> Sent from my iPhone >> >> On 12 Jan 2025, at 16:50, James Dailey <jdai...@apache.org> wrote: >> >> >> Thanks for bringing this to the attention of the community. I, for one, >> was unaware. >> >> Can the person proposing the PR send an email and explain? >> >> >> On Sun, Jan 12, 2025 at 5:52 AM Michael Vorburger >> <m...@vorburger.ch.invalid> wrote: >> >>> Hello, >>> >>> Hope you are all doing well. >>> >>> I stumbled, by coincidence, over >>> https://github.com/apache/fineract-site/pull/35. >>> >>> It "looks cool" to me, but at my current level of involvement in this >>> community I am not comfortable to "just" merge this major visual overhaul >>> of this community's https://fineract.apache.org/ homepage alone. >>> >>> Would others like to contribute to reviewing, and merge, if OK? >>> >>> Or does anyone note any objections to this overhaul? >>> >>> Tx, >>> M. >>> >>> PS: One [minor] thing this includes, other than the more important >>> visual overhaul, is drop the use of https://about.scarf.sh (with this >>> change), which given yesterday's "[NOTICE] New Content Security Policy for >>> all ASF project websites" to annou...@infra.apache.org & >>> us...@infra.apache.org might have to go anyway. >>> >>
