You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by James Dailey <ja...@gmail.com> on 2023/01/31 01:52:59 UTC
Website and Wiki for Fineract updates
All -
We have a lot of good content on the wiki but it's been 3+ years since we
did a clean sweep of it. We also have a front landing page at
https://fineract.apache.org that could be better at communicating the
project and community. Who wants to work on this with me?
PROPOSED CHANGES
---
On the front "Landing" page:
- Add blog feed
- Add feed to dev list
- Include FAQ
- Split FineractCN and Fineract
As we hope to see a FineractCN release soon, I think we should have a top
level split on the main page as well, or perhaps a separate landing page
for FineractCN.
---
On the wiki - new suggested structure (figure out how to show two levels):
- FAQ
- About Fineract
- New top level functional descriptions
- About FineractCN
- TBD
- Project Management
- Quarterly reports to the Apache Board (this needs to be more
prominent)
- Community meetings organized by date (most recent at top)
- Surveys
- Release processes
- How do I get involved?
- Committer guides
- Links to JIRA and GitHUB
- Standards
- Documentation
- Replace with links to the new dynamically generated documentation.
- Move Comms related stuff (talks, opinion pieces, etc) ... all go to
blog
Are there things we should keep or not keep?
The current high level structure:
- FAQ (frequently asked questions)
<https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
-
GETTING INVOLVED (commit, contribute)
<https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
-
FINERACT
<https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
-
FINERACT CN
<https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
-
Fineract Data, Credit Scoring, AI
<https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
-
Fineract Project Security Report
<https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
-
COMMS: Blogs, Talks, and Links
<https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
-
ApacheCon EU 2016 Fineract Speaker's Notes
<https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
-
How-to articles
<https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
-
ApacheCON Fineract Track
<https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
-
Meeting notes
<https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Tekle -
Can I ask you to go through the current wiki and determine which content is
already covered at
https://fineract.apache.org/docs/current/ ?
Mark which wiki pages can be removed or deprecated by placing a text, in
red, on that page
"This page will be deprecated in favor of content found at
https://fineract.apache.org/docs/current/."
Is this task clear? Do you still want to help on this? Can you do this
before March 31st?
Bruce -
I would like you to become the expert on content at
https://fineract.apache.org/docs/current/
Please go through that document and then send an email to the list
identifying 3-5 areas of new content that you would like to see.
e.g. What gaps are in that document that you would want to see filled?
what other content do you think we have for those areas?
Is this task clear? Do you still want to help on this? Can you do this
before March 31st?
BOTH - Is there a better use of your time that you want to suggest?
thanks
James Dailey
On Tue, Jan 31, 2023 at 12:24 AM Tekle Gebreyohannes <te...@gmail.com>
wrote:
> Hi James,
> I would like to help with this. Where can I start?
>
> Best regards,
> Tekle
>
> On Tue, Jan 31, 2023 at 4:53 AM James Dailey <ja...@gmail.com>
> wrote:
>
>> All -
>>
>> We have a lot of good content on the wiki but it's been 3+ years since we
>> did a clean sweep of it. We also have a front landing page at
>> https://fineract.apache.org that could be better at communicating the
>> project and community. Who wants to work on this with me?
>>
>> PROPOSED CHANGES
>> ---
>> On the front "Landing" page:
>>
>> - Add blog feed
>> - Add feed to dev list
>> - Include FAQ
>> - Split FineractCN and Fineract
>>
>> As we hope to see a FineractCN release soon, I think we should have a top
>> level split on the main page as well, or perhaps a separate landing page
>> for FineractCN.
>>
>> ---
>> On the wiki - new suggested structure (figure out how to show two
>> levels):
>>
>> - FAQ
>> - About Fineract
>> - New top level functional descriptions
>> - About FineractCN
>> - TBD
>> - Project Management
>> - Quarterly reports to the Apache Board (this needs to be more
>> prominent)
>> - Community meetings organized by date (most recent at top)
>> - Surveys
>> - Release processes
>> - How do I get involved?
>> - Committer guides
>> - Links to JIRA and GitHUB
>> - Standards
>> - Documentation
>> - Replace with links to the new dynamically generated
>> documentation.
>> - Move Comms related stuff (talks, opinion pieces, etc) ... all go
>> to blog
>>
>>
>>
>> Are there things we should keep or not keep?
>>
>>
>>
>> The current high level structure:
>>
>> - FAQ (frequently asked questions)
>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>> -
>> GETTING INVOLVED (commit, contribute)
>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>> -
>> FINERACT
>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>> -
>> FINERACT CN
>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>> -
>> Fineract Data, Credit Scoring, AI
>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>> -
>> Fineract Project Security Report
>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>> -
>> COMMS: Blogs, Talks, and Links
>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>> -
>> ApacheCon EU 2016 Fineract Speaker's Notes
>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>> -
>> How-to articles
>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>> -
>> ApacheCON Fineract Track
>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>> -
>> Meeting notes
>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>
>>
>>
>>
>>
>>
Re: Website and Wiki for Fineract updates
Posted by Tekle Gebreyohannes <te...@gmail.com>.
Hi James,
I would like to help with this. Where can I start?
Best regards,
Tekle
On Tue, Jan 31, 2023 at 4:53 AM James Dailey <ja...@gmail.com> wrote:
> All -
>
> We have a lot of good content on the wiki but it's been 3+ years since we
> did a clean sweep of it. We also have a front landing page at
> https://fineract.apache.org that could be better at communicating the
> project and community. Who wants to work on this with me?
>
> PROPOSED CHANGES
> ---
> On the front "Landing" page:
>
> - Add blog feed
> - Add feed to dev list
> - Include FAQ
> - Split FineractCN and Fineract
>
> As we hope to see a FineractCN release soon, I think we should have a top
> level split on the main page as well, or perhaps a separate landing page
> for FineractCN.
>
> ---
> On the wiki - new suggested structure (figure out how to show two levels):
>
> - FAQ
> - About Fineract
> - New top level functional descriptions
> - About FineractCN
> - TBD
> - Project Management
> - Quarterly reports to the Apache Board (this needs to be more
> prominent)
> - Community meetings organized by date (most recent at top)
> - Surveys
> - Release processes
> - How do I get involved?
> - Committer guides
> - Links to JIRA and GitHUB
> - Standards
> - Documentation
> - Replace with links to the new dynamically generated
> documentation.
> - Move Comms related stuff (talks, opinion pieces, etc) ... all go
> to blog
>
>
>
> Are there things we should keep or not keep?
>
>
>
> The current high level structure:
>
> - FAQ (frequently asked questions)
> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
> -
> GETTING INVOLVED (commit, contribute)
> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
> -
> FINERACT
> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
> -
> FINERACT CN
> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
> -
> Fineract Data, Credit Scoring, AI
> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
> -
> Fineract Project Security Report
> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
> -
> COMMS: Blogs, Talks, and Links
> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
> -
> ApacheCon EU 2016 Fineract Speaker's Notes
> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
> -
> How-to articles
> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
> -
> ApacheCON Fineract Track
> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
> -
> Meeting notes
> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>
>
>
>
>
>
Re: Website and Wiki for Fineract updates
Posted by John Gathogo <jo...@fiter.io>.
I am almost done with adding documentation aimed at business/functional
users. I will be sharing this soon for review and feedback.
On Tue, Jun 6, 2023 at 11:45 PM James Dailey <ja...@gmail.com> wrote:
> Checking in on these tasks. Please update here.
>
> Thanks,
>
>
> On Wed, May 17, 2023 at 12:47 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> Checking in - Any updates on the tasks?
>> @inzemamhaq05
>> @John Gathogo <jo...@fiter.io>
>> +Abhinav Sinha
>>
>> James Dailey
>>
>>
>>
>> On Thu, May 11, 2023 at 12:05 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Hi all - We held our conversation today on Zoom about the design of the
>>> Landing page and our overall strategy of organizing content on our web
>>> presence.
>>>
>>> Currently, we have the landing page: http://fineract.apache.org
>>> (within links to various places on the wiki and github)
>>> and we have the project site
>>> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home
>>> (with a complex navigation and content structure)
>>> and we have the new Platform Documentation at
>>> https://fineract.apache.org/docs/current/ (from github)
>>>
>>> Each of these serves a unique value:
>>> * landing page is where technical and business people come to learn
>>> more, where interested devs can easily find their way to a release or to
>>> documentation or to dev tasks
>>> * wiki is where we organize our project and community and thus
>>> everything that is "in process" like links to Jira tickets
>>> * Platform Documentation for things that are developed (completed, in
>>> the Platform)
>>>
>>> next up:
>>> Inzemam will provide a new version of the landing page and start a
>>> fork of the current page so that we can see his approach to keeping the
>>> html/css/javascript easy to maintain.
>>> and John with help from Abhinav will work on assessing which pieces of
>>> the wiki can be trimmed (if it exists on the Platform documentation or can
>>> move over there)
>>>
>>> Please see the meeting notes from the ZOOM call here
>>>
>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>
>>> Thank you to those who joined today but also, if you didn't join, you
>>> are welcome to join in the work. This is an important way to make the
>>> project more maintainable and approachable.
>>>
>>> Thanks,
>>> James
>>>
>>>
>>> On Thu, May 11, 2023 at 11:38 AM Dejan Juric <de...@j13kventures.com>
>>> wrote:
>>>
>>>> Hi,
>>>> please also add me.
>>>>
>>>> Thx,
>>>> Dejan
>>>>
>>>> On Thu, May 11, 2023 at 12:55 PM Federico Benitez <fe...@nubloq.co>
>>>> wrote:
>>>>
>>>>> Pls add me
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On 10/05/2023, at 14:33, comsky juste <co...@gmail.com> wrote:
>>>>>
>>>>>
>>>>> Please add me.
>>>>>
>>>>> On Wed, May 10, 2023, 3:58 AM Abhinav Sinha <ab...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Could you pls add me to the call as well
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Abhinav
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From: *James Dailey <ja...@gmail.com>
>>>>>> *Date: *Tuesday, May 9, 2023 at 9:53 PM
>>>>>> *To: *dev@fineract.apache.org <de...@fineract.apache.org>
>>>>>> *Subject: *Re: Website and Wiki for Fineract updates
>>>>>>
>>>>>> We will update this wiki page during and after the meeting
>>>>>>
>>>>>>
>>>>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>>>>
>>>>>>
>>>>>>
>>>>>> (John - added)
>>>>>>
>>>>>> (Ernesto -added)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
>>>>>>
>>>>>> Please add me to this call.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
>>>>>> <eo...@yahoo.com.invalid> wrote:
>>>>>>
>>>>>> Please add me
>>>>>>
>>>>>>
>>>>>> Sent from Yahoo Mail for iPhone
>>>>>> <https://overview.mail.yahoo.com/?.src=iOS>
>>>>>>
>>>>>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>
>>>>>> Yep I'll be there in meet call.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> W can organize a zoom call. Then report back to the list here.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I’ll suggest May 11th , 9am Pacific (PDT)
>>>>>>
>>>>>> I’ll send zoom link to anyone expressing interest.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hello James,
>>>>>>
>>>>>> Sorry for the late reply I was stuck in gsoc but I know I'll get
>>>>>> rejected so finally I am looking forward on the website as we dealt before.
>>>>>>
>>>>>> Can we have a zoom call? So we can get an idea of what exactly we are
>>>>>> gonna place on the website as from the previous responses I am only getting
>>>>>> that some of the things should be changed or replaced but with whom I can't
>>>>>> get it.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Inzemamul Haq
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hi Bruce - Good to know about those gaps in deployment and tools, but
>>>>>> are those the only gaps in the documentation?
>>>>>>
>>>>>>
>>>>>>
>>>>>> So, question to you: is it already sufficiently clear on these
>>>>>> topics:
>>>>>>
>>>>>> * explaining what the software does
>>>>>>
>>>>>> * explaining the architecture
>>>>>>
>>>>>> * explaining relationship between different components
>>>>>>
>>>>>> * what features are in each release
>>>>>>
>>>>>> * how to set up development environment
>>>>>>
>>>>>> * how to access APIs
>>>>>>
>>>>>> * how to find additional resources
>>>>>>
>>>>>>
>>>>>>
>>>>>> I did ask for 3-5 priority things, so please do try to identify where
>>>>>> we start, even from your very long list or maybe adding to it, can we get
>>>>>> your opinion on a few key things?
>>>>>>
>>>>>>
>>>>>>
>>>>>> What would you say is a priority?
>>>>>>
>>>>>>
>>>>>>
>>>>>> As a project, I think we need to simply and only offer one or two
>>>>>> deployment options in our documentation, that way we can focus on getting
>>>>>> those accurate and keeping them up to date. Others are of course free to
>>>>>> offer their own improvements and alternatives.
>>>>>>
>>>>>>
>>>>>>
>>>>>> All - comments welcome.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> James
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>>
>>>>>> I hope this email finds you well. I wanted to share some observations
>>>>>> after going through the documentation for Fineract again.
>>>>>>
>>>>>> While the documentation provides an overview of deployment options
>>>>>> here https://fineract.apache.org/docs/current/#_deployment , I
>>>>>> noticed that several options, such as Docker Compose, Tomcat, Undertow,
>>>>>> Jetty, JBoss, Weblogic, and Payara, are marked as TBD, indicating a lack of
>>>>>> content and guidance for users. There is also no deployment content on Kubernetes, AWS
>>>>>> and Google Cloud. Let's address this.
>>>>>>
>>>>>> Additionally, the Fineract Development section here
>>>>>> https://fineract.apache.org/docs/current/#_fineract_development_environment appears
>>>>>> to be incomplete and in need of further content to cover important topics
>>>>>> related to Fineract development. This section also includes topics marked
>>>>>> as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
>>>>>> Docker Desktop, IDE selection and configuration (including IntelliJ,
>>>>>> Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
>>>>>> Microk8s, K3d, Helm Charts, and installation and usage of various
>>>>>> development tools like Brew for MacOS and Linux. I propose that the
>>>>>> community contibutes content for the following topics:
>>>>>>
>>>>>> - Docker: how to install, run, and use Docker containers for
>>>>>> Fineract
>>>>>> - Docker Compose: how to use Docker Compose to orchestrate
>>>>>> multiple containers for Fineract
>>>>>> - Podman: how to use Podman as an alternative to Docker for
>>>>>> running containers
>>>>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to
>>>>>> run Kubernetes clusters on one's local machine
>>>>>> - IDE: how to choose and configure an IDE for Fineract development
>>>>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>>>>> Fineract
>>>>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>>>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>>>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>>>>> clusters
>>>>>> - Minikube: how to use Minikube to run a local Kubernetes cluster
>>>>>> for Fineract
>>>>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>>>>> cluster for Fineract
>>>>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>>>>> Fineract
>>>>>> - Helm Charts: how to use Helm Charts to package and deploy
>>>>>> Fineract applications on Kubernetes
>>>>>> - Tools: how to install and use various tools that can help one
>>>>>> with Fineract development
>>>>>> - Brew: how to install and use Brew for MacOS and Linux
>>>>>>
>>>>>> By actively addressing these gaps in the documentation, we can
>>>>>> provide valuable support to the Fineract community and further showcase the
>>>>>> flexibility and compatibility of Fineract with different technologies and
>>>>>> platforms.
>>>>>>
>>>>>> I look forward to collaborating with the community to contribute
>>>>>> content for these important topics and improve the overall documentation
>>>>>> for Fineract.
>>>>>>
>>>>>> Best Regards
>>>>>>
>>>>>> Bruce
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Meta or Bruce - any updates?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>>>> the previous points you and others mentioned..
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> I've started to change some of the structure of the wiki. I'm just
>>>>>> trying to clean it up: Does anyone have an objection?
>>>>>>
>>>>>> * Noting where content is historical and deprecating it
>>>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>>>
>>>>>> This is incremental.
>>>>>>
>>>>>> Inzemam - can you provide a new design to review taking on the
>>>>>> feedback?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>> >
>>>>>> > Okay I'll be looking into it..
>>>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the
>>>>>> frontend fields. Surely working effectively with both the orgs by making
>>>>>> good designs with premium feel.
>>>>>> > Regards,
>>>>>> > Inzemam
>>>>>> >
>>>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>> >>
>>>>>> >> Please make a set of suggestions or revise your designs based on
>>>>>> input.
>>>>>> >>
>>>>>> >> Feel free to dive into this .
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>> >>>
>>>>>> >>> Hello James,
>>>>>> >>> When we are going to start the work or are we leaving it for
>>>>>> future?
>>>>>> >>>
>>>>>> >>> Regards,
>>>>>> >>> Inzemam
>>>>>> >>>
>>>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>>>> wrote:
>>>>>> >>>>
>>>>>> >>>> Hi James,
>>>>>> >>>> You are correct that we need to discuss more on the flows of
>>>>>> events and placements. And I am also agree with the point that we can
>>>>>> create a slack channel for this.
>>>>>> >>>> Also the code will be in simple html, css and js format so
>>>>>> anyone can create/change the things easily. The design is looking fancy and
>>>>>> complicated but the code is as smooth as butter. So need to worry about
>>>>>> maintainance.
>>>>>> >>>> Regards,
>>>>>> >>>> Inzemamul Haq
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>
>>>>>> >>>>> Hi - Thank you for this.
>>>>>> >>>>>
>>>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>>>> Javier's comments, which makes clear that we need to do a better job of
>>>>>> "Explaining" and "Positioning".
>>>>>> >>>>>
>>>>>> >>>>> ASIDE: Javier - I invite you to write more such text and
>>>>>> provide a top level set of bullet points that can be perhaps worked into
>>>>>> the content.
>>>>>> >>>>>
>>>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>>>> Nice.
>>>>>> >>>>>
>>>>>> >>>>> We need more revamping of the content before we can properly do
>>>>>> this design, so let's try to attack that problem.
>>>>>> >>>>>
>>>>>> >>>>> Here is a requirement that may not be clear to you:
>>>>>> >>>>> * Site should be very simple, easy to change by anyone opening
>>>>>> up a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>>>> hopefully with names that make sense
>>>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>>>> some text areas, adding content in specific sections.
>>>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>>>> three years, and avoid content that can get stale.
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> Message and Content issues:
>>>>>> >>>>>
>>>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>>>> the page today. Also, there is a common set of links and structure that you
>>>>>> can find in other Apache projects. It is not a requirement to follow other
>>>>>> Apache projects, but it would be useful to review them for commonalities:
>>>>>> >>>>> --> https://hadoop.apache.org
>>>>>> >>>>> --> https://airflow.apache.org
>>>>>> >>>>> --> https://kafka.apache.org
>>>>>> >>>>>
>>>>>> >>>>> * Note Community is there in each project. Check out the
>>>>>> content that each project has.
>>>>>> >>>>>
>>>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>>> >>>>> and this should then flow into the requirements for the other
>>>>>> sections on the front page and then onto the wiki structure that we need
>>>>>> >>>>>
>>>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>>>> "Additional community technologies"
>>>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>>>> positioning is controversial for some, but until we get a release out and
>>>>>> lots of active development and deployments, that project remains very much
>>>>>> a side project of the community. It may become a very important thing, but
>>>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>>>> the vast majority of the dev is going on, and the vast majority of the
>>>>>> users are there.
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>>>> should be a summary of the system.
>>>>>> >>>>>
>>>>>> >>>>> This may require more chat and discussion on list or on slack
>>>>>> and then development of a structure of content before you can really get a
>>>>>> design.
>>>>>> >>>>>
>>>>>> >>>>> Thank you again.
>>>>>> >>>>>
>>>>>> >>>>> James Dailey
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>
>>>>>> >>>>>> Hello James,
>>>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>>> >>>>>> Regards,
>>>>>> >>>>>> Inzemamul Haq
>>>>>> >>>>>>
>>>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>
>>>>>> >>>>>>> Hello Javier,
>>>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>>>> implement them as you suggested now what I need is some more brief about
>>>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>>>> change and add the things.
>>>>>> >>>>>>> As you mentioned in the last that it's a template but it's
>>>>>> not. It's designed by me on the figma and the assets I used are open source
>>>>>> so their will be no licencing issue. I always go for the development
>>>>>> through scratch so no need to worry about that.
>>>>>> >>>>>>> Regards,
>>>>>> >>>>>>> Inzemam
>>>>>> >>>>>>>
>>>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>>>> javier@fiter.io> wrote:
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Hy Meta,
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Great job; I like the enhancement of the visuals and
>>>>>> aesthetic in general, and it seems much more modern and suitable for the
>>>>>> next stage of our community.
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> My two cents:
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be
>>>>>> useful in other areas of the industry, not just banks. We need to convey
>>>>>> that Fineract is a platform for many use cases. Using a mobile phone and a
>>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>>>> be conceptual, not rigid on old paradigms.
>>>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>>> purchases are now digital.
>>>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have
>>>>>> the same exposure on our website as Fineract. Fineract CN it's still an
>>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>>> CN is not backward compatible with Fineract.
>>>>>> >>>>>>>> The project we are proud of: I will only use the project
>>>>>> part if we get three Fortune 500 companies using Fineract. It will also
>>>>>> open a new can of worms on which project gets selected and which criteria
>>>>>> we should use, on top of getting the right set of approvals from them to be
>>>>>> used as projects.
>>>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>>>> need the license of that template that allows us to use it without
>>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Javier
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> Hi James,
>>>>>> >>>>>>>>> Below is the drive link of complete page screenshot of
>>>>>> APACHE FINERACT redesigned website. Please review and let me know if you
>>>>>> have any questions or changes needed.
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>>
>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> Regards,
>>>>>> >>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>> +1
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> Hi
>>>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>>>> what exact is there on the website. I'll create a static mockup for the
>>>>>> website.
>>>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>>>> anyone new or experienced first comes to the website got confused of what's
>>>>>> happening and how things are going we can work upon it.
>>>>>> >>>>>>>>>>>>> Also I have a question are we going to implement
>>>>>> blogger on that website? I have ability to work on static websites where
>>>>>> the data comes from dynamic CMS.
>>>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>>>> >>>>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>>>> page website for the project, so not an app. The content needs to be
>>>>>> largely static or to pick up content we regularly post on blog. The current
>>>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>>>> is a design lens, in my view. But, a good UIX process does start with
>>>>>> who’s the audience and what’s their need when they land on the page.
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>> Hi,
>>>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we
>>>>>> can get a better Idea of what exactly has to be happen. By the 16th of Feb
>>>>>> I'll come up with a design also will share here in the thread and we can
>>>>>> get comments in the meeting.
>>>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>>>> overall UI/UX
>>>>>> >>>>>>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>>>> have four people who said they'd like to be involved.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>>>> mid February.
>>>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>>> document:
>>>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page
>>>>>> in detail.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where
>>>>>> is there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find
>>>>>> sections you think belong being "brought over". compile a list of those
>>>>>> pages. If none, great.
>>>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of
>>>>>> the landing page (Meta Cyrus?)
>>>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>>>> landing pages that you like
>>>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>>> confluence with links (james or ?)
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow
>>>>>> this thread.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> thanks
>>>>>> >>>>>>>>>>>>>>>> James
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>>>> d@gwocu.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>>>> and develop a good user reliable website.
>>>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>>>> >>>>>>>>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> All -
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>>>> landing page at https://fineract.apache.org that could be better at
>>>>>> communicating the project and community. Who wants to work on this with me?
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I
>>>>>> think we should have a top level split on the main page as well, or perhaps
>>>>>> a separate landing page for FineractCN.
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>>>> how to show two levels):
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> TBD
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs
>>>>>> to be more prominent)
>>>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent
>>>>>> at top)
>>>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>>> >>>>>>>>>>>>>>>>>> Standards
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically
>>>>>> generated documentation.
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>>>> etc) ... all go to blog
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> --
>>>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> --
>>>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>>>> >>
>>>>>> >> --
>>>>>> >> Sent from Gmail Mobile
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Sent from Gmail Mobile
>>>>>>
>>>>>>
>>>>> El contenido de este mensaje y sus archivos electrónicos adjuntos
>>>>> constituyen información confidencial, y puede además contener secretos
>>>>> comerciales o industriales que se encuentran protegidos bajo las leyes de
>>>>> propiedad intelectual. Su uso, divulgación, revelación y/o circulación no
>>>>> autorizados se encuentran estrictamente prohibidos, por lo que si usted no
>>>>> es el destinatario del mismo o lo recibió por error, notifique
>>>>> inmediatamente al remitente por correo electrónico y elimine el mensaje así
>>>>> como toda información adjunta de su sistema. En cumplimiento de lo
>>>>> establecido por las leyes de protección de datos personales, Nubloq S.A.S.
>>>>> hace de su conocimiento que se encuentra a su disposición la política de
>>>>> tratamiento de datos personales en la página de internet
>>>>> https://www.nubloq.co/legal/ a efecto de que pueda ejercer su derecho
>>>>> al hábeas data. Todos los datos personales entregados vía correo
>>>>> electrónico serán utilizados de acuerdo con las finalidades allí previstas.
>>>>> Puede también consultar nuestros términos y condiciones en
>>>>> https://www.nubloq.co/legal/.
>>>>>
>>>>> The contents of this message and its attachments are confidential
>>>>> information and can hold trade secrets subject to intellectual property
>>>>> regulations. Its unauthorized use, divulgation, reveal and/or circulation
>>>>> are therefore strictly prohibited. In the event that you are not the
>>>>> intended recipient of this email, please immediately notify the sender
>>>>> through email and delete the message and any attachments from your system. Pursuant
>>>>> to the regulations on data privacy, Nubloq S.A.S informs that the privacy
>>>>> policy is available for consultation at: https://www.nubloq.co/legal/.
>>>>> All personal data will be treated in accordance with the purposes provided
>>>>> therein. You can also review our terms and conditions at
>>>>> https://www.nubloq.co/legal/.
>>>>>
>>>>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Checking in on these tasks. Please update here.
Thanks,
On Wed, May 17, 2023 at 12:47 PM James Dailey <ja...@gmail.com>
wrote:
> Checking in - Any updates on the tasks?
> @inzemamhaq05
> @John Gathogo <jo...@fiter.io>
> +Abhinav Sinha
>
> James Dailey
>
>
>
> On Thu, May 11, 2023 at 12:05 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> Hi all - We held our conversation today on Zoom about the design of the
>> Landing page and our overall strategy of organizing content on our web
>> presence.
>>
>> Currently, we have the landing page: http://fineract.apache.org (within
>> links to various places on the wiki and github)
>> and we have the project site
>> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home
>> (with a complex navigation and content structure)
>> and we have the new Platform Documentation at
>> https://fineract.apache.org/docs/current/ (from github)
>>
>> Each of these serves a unique value:
>> * landing page is where technical and business people come to learn more,
>> where interested devs can easily find their way to a release or to
>> documentation or to dev tasks
>> * wiki is where we organize our project and community and thus everything
>> that is "in process" like links to Jira tickets
>> * Platform Documentation for things that are developed (completed, in the
>> Platform)
>>
>> next up:
>> Inzemam will provide a new version of the landing page and start a fork
>> of the current page so that we can see his approach to keeping the
>> html/css/javascript easy to maintain.
>> and John with help from Abhinav will work on assessing which pieces of
>> the wiki can be trimmed (if it exists on the Platform documentation or can
>> move over there)
>>
>> Please see the meeting notes from the ZOOM call here
>>
>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>
>> Thank you to those who joined today but also, if you didn't join, you are
>> welcome to join in the work. This is an important way to make the project
>> more maintainable and approachable.
>>
>> Thanks,
>> James
>>
>>
>> On Thu, May 11, 2023 at 11:38 AM Dejan Juric <de...@j13kventures.com>
>> wrote:
>>
>>> Hi,
>>> please also add me.
>>>
>>> Thx,
>>> Dejan
>>>
>>> On Thu, May 11, 2023 at 12:55 PM Federico Benitez <fe...@nubloq.co>
>>> wrote:
>>>
>>>> Pls add me
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On 10/05/2023, at 14:33, comsky juste <co...@gmail.com> wrote:
>>>>
>>>>
>>>> Please add me.
>>>>
>>>> On Wed, May 10, 2023, 3:58 AM Abhinav Sinha <ab...@gmail.com>
>>>> wrote:
>>>>
>>>>> Could you pls add me to the call as well
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Abhinav
>>>>>
>>>>>
>>>>>
>>>>> *From: *James Dailey <ja...@gmail.com>
>>>>> *Date: *Tuesday, May 9, 2023 at 9:53 PM
>>>>> *To: *dev@fineract.apache.org <de...@fineract.apache.org>
>>>>> *Subject: *Re: Website and Wiki for Fineract updates
>>>>>
>>>>> We will update this wiki page during and after the meeting
>>>>>
>>>>>
>>>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>>>
>>>>>
>>>>>
>>>>> (John - added)
>>>>>
>>>>> (Ernesto -added)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
>>>>>
>>>>> Please add me to this call.
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
>>>>> <eo...@yahoo.com.invalid> wrote:
>>>>>
>>>>> Please add me
>>>>>
>>>>>
>>>>> Sent from Yahoo Mail for iPhone
>>>>> <https://overview.mail.yahoo.com/?.src=iOS>
>>>>>
>>>>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>
>>>>> Yep I'll be there in meet call.
>>>>>
>>>>>
>>>>>
>>>>> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> W can organize a zoom call. Then report back to the list here.
>>>>>
>>>>>
>>>>>
>>>>> I’ll suggest May 11th , 9am Pacific (PDT)
>>>>>
>>>>> I’ll send zoom link to anyone expressing interest.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hello James,
>>>>>
>>>>> Sorry for the late reply I was stuck in gsoc but I know I'll get
>>>>> rejected so finally I am looking forward on the website as we dealt before.
>>>>>
>>>>> Can we have a zoom call? So we can get an idea of what exactly we are
>>>>> gonna place on the website as from the previous responses I am only getting
>>>>> that some of the things should be changed or replaced but with whom I can't
>>>>> get it.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Inzemamul Haq
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi Bruce - Good to know about those gaps in deployment and tools, but
>>>>> are those the only gaps in the documentation?
>>>>>
>>>>>
>>>>>
>>>>> So, question to you: is it already sufficiently clear on these
>>>>> topics:
>>>>>
>>>>> * explaining what the software does
>>>>>
>>>>> * explaining the architecture
>>>>>
>>>>> * explaining relationship between different components
>>>>>
>>>>> * what features are in each release
>>>>>
>>>>> * how to set up development environment
>>>>>
>>>>> * how to access APIs
>>>>>
>>>>> * how to find additional resources
>>>>>
>>>>>
>>>>>
>>>>> I did ask for 3-5 priority things, so please do try to identify where
>>>>> we start, even from your very long list or maybe adding to it, can we get
>>>>> your opinion on a few key things?
>>>>>
>>>>>
>>>>>
>>>>> What would you say is a priority?
>>>>>
>>>>>
>>>>>
>>>>> As a project, I think we need to simply and only offer one or two
>>>>> deployment options in our documentation, that way we can focus on getting
>>>>> those accurate and keeping them up to date. Others are of course free to
>>>>> offer their own improvements and alternatives.
>>>>>
>>>>>
>>>>>
>>>>> All - comments welcome.
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> James
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>> I hope this email finds you well. I wanted to share some observations
>>>>> after going through the documentation for Fineract again.
>>>>>
>>>>> While the documentation provides an overview of deployment options
>>>>> here https://fineract.apache.org/docs/current/#_deployment , I
>>>>> noticed that several options, such as Docker Compose, Tomcat, Undertow,
>>>>> Jetty, JBoss, Weblogic, and Payara, are marked as TBD, indicating a lack of
>>>>> content and guidance for users. There is also no deployment content on Kubernetes, AWS
>>>>> and Google Cloud. Let's address this.
>>>>>
>>>>> Additionally, the Fineract Development section here
>>>>> https://fineract.apache.org/docs/current/#_fineract_development_environment appears
>>>>> to be incomplete and in need of further content to cover important topics
>>>>> related to Fineract development. This section also includes topics marked
>>>>> as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
>>>>> Docker Desktop, IDE selection and configuration (including IntelliJ,
>>>>> Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
>>>>> Microk8s, K3d, Helm Charts, and installation and usage of various
>>>>> development tools like Brew for MacOS and Linux. I propose that the
>>>>> community contibutes content for the following topics:
>>>>>
>>>>> - Docker: how to install, run, and use Docker containers for
>>>>> Fineract
>>>>> - Docker Compose: how to use Docker Compose to orchestrate
>>>>> multiple containers for Fineract
>>>>> - Podman: how to use Podman as an alternative to Docker for
>>>>> running containers
>>>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>>>>> Kubernetes clusters on one's local machine
>>>>> - IDE: how to choose and configure an IDE for Fineract development
>>>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>>>> Fineract
>>>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>>>> clusters
>>>>> - Minikube: how to use Minikube to run a local Kubernetes cluster
>>>>> for Fineract
>>>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>>>> cluster for Fineract
>>>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>>>> Fineract
>>>>> - Helm Charts: how to use Helm Charts to package and deploy
>>>>> Fineract applications on Kubernetes
>>>>> - Tools: how to install and use various tools that can help one
>>>>> with Fineract development
>>>>> - Brew: how to install and use Brew for MacOS and Linux
>>>>>
>>>>> By actively addressing these gaps in the documentation, we can provide
>>>>> valuable support to the Fineract community and further showcase the
>>>>> flexibility and compatibility of Fineract with different technologies and
>>>>> platforms.
>>>>>
>>>>> I look forward to collaborating with the community to contribute
>>>>> content for these important topics and improve the overall documentation
>>>>> for Fineract.
>>>>>
>>>>> Best Regards
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Meta or Bruce - any updates?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>>> the previous points you and others mentioned..
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> I've started to change some of the structure of the wiki. I'm just
>>>>> trying to clean it up: Does anyone have an objection?
>>>>>
>>>>> * Noting where content is historical and deprecating it
>>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>>
>>>>> This is incremental.
>>>>>
>>>>> Inzemam - can you provide a new design to review taking on the
>>>>> feedback?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>> >
>>>>> > Okay I'll be looking into it..
>>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>>>>> fields. Surely working effectively with both the orgs by making good
>>>>> designs with premium feel.
>>>>> > Regards,
>>>>> > Inzemam
>>>>> >
>>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> Please make a set of suggestions or revise your designs based on
>>>>> input.
>>>>> >>
>>>>> >> Feel free to dive into this .
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>> >>>
>>>>> >>> Hello James,
>>>>> >>> When we are going to start the work or are we leaving it for
>>>>> future?
>>>>> >>>
>>>>> >>> Regards,
>>>>> >>> Inzemam
>>>>> >>>
>>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>>> wrote:
>>>>> >>>>
>>>>> >>>> Hi James,
>>>>> >>>> You are correct that we need to discuss more on the flows of
>>>>> events and placements. And I am also agree with the point that we can
>>>>> create a slack channel for this.
>>>>> >>>> Also the code will be in simple html, css and js format so anyone
>>>>> can create/change the things easily. The design is looking fancy and
>>>>> complicated but the code is as smooth as butter. So need to worry about
>>>>> maintainance.
>>>>> >>>> Regards,
>>>>> >>>> Inzemamul Haq
>>>>> >>>>
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>
>>>>> >>>>> Hi - Thank you for this.
>>>>> >>>>>
>>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>>> Javier's comments, which makes clear that we need to do a better job of
>>>>> "Explaining" and "Positioning".
>>>>> >>>>>
>>>>> >>>>> ASIDE: Javier - I invite you to write more such text and
>>>>> provide a top level set of bullet points that can be perhaps worked into
>>>>> the content.
>>>>> >>>>>
>>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>>> Nice.
>>>>> >>>>>
>>>>> >>>>> We need more revamping of the content before we can properly do
>>>>> this design, so let's try to attack that problem.
>>>>> >>>>>
>>>>> >>>>> Here is a requirement that may not be clear to you:
>>>>> >>>>> * Site should be very simple, easy to change by anyone opening
>>>>> up a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>>> hopefully with names that make sense
>>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>>> some text areas, adding content in specific sections.
>>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>>> three years, and avoid content that can get stale.
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> Message and Content issues:
>>>>> >>>>>
>>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>>> the page today. Also, there is a common set of links and structure that you
>>>>> can find in other Apache projects. It is not a requirement to follow other
>>>>> Apache projects, but it would be useful to review them for commonalities:
>>>>> >>>>> --> https://hadoop.apache.org
>>>>> >>>>> --> https://airflow.apache.org
>>>>> >>>>> --> https://kafka.apache.org
>>>>> >>>>>
>>>>> >>>>> * Note Community is there in each project. Check out the
>>>>> content that each project has.
>>>>> >>>>>
>>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>> >>>>> and this should then flow into the requirements for the other
>>>>> sections on the front page and then onto the wiki structure that we need
>>>>> >>>>>
>>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>>> "Additional community technologies"
>>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>>> positioning is controversial for some, but until we get a release out and
>>>>> lots of active development and deployments, that project remains very much
>>>>> a side project of the community. It may become a very important thing, but
>>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>>> the vast majority of the dev is going on, and the vast majority of the
>>>>> users are there.
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>>> should be a summary of the system.
>>>>> >>>>>
>>>>> >>>>> This may require more chat and discussion on list or on slack
>>>>> and then development of a structure of content before you can really get a
>>>>> design.
>>>>> >>>>>
>>>>> >>>>> Thank you again.
>>>>> >>>>>
>>>>> >>>>> James Dailey
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>
>>>>> >>>>>> Hello James,
>>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>> >>>>>> Regards,
>>>>> >>>>>> Inzemamul Haq
>>>>> >>>>>>
>>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>
>>>>> >>>>>>> Hello Javier,
>>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>>> implement them as you suggested now what I need is some more brief about
>>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>>> change and add the things.
>>>>> >>>>>>> As you mentioned in the last that it's a template but it's
>>>>> not. It's designed by me on the figma and the assets I used are open source
>>>>> so their will be no licencing issue. I always go for the development
>>>>> through scratch so no need to worry about that.
>>>>> >>>>>>> Regards,
>>>>> >>>>>>> Inzemam
>>>>> >>>>>>>
>>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>>> javier@fiter.io> wrote:
>>>>> >>>>>>>>
>>>>> >>>>>>>> Hy Meta,
>>>>> >>>>>>>>
>>>>> >>>>>>>> Great job; I like the enhancement of the visuals and
>>>>> aesthetic in general, and it seems much more modern and suitable for the
>>>>> next stage of our community.
>>>>> >>>>>>>>
>>>>> >>>>>>>> My two cents:
>>>>> >>>>>>>>
>>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful
>>>>> in other areas of the industry, not just banks. We need to convey that
>>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>>> be conceptual, not rigid on old paradigms.
>>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>> purchases are now digital.
>>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>> CN is not backward compatible with Fineract.
>>>>> >>>>>>>> The project we are proud of: I will only use the project part
>>>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>>>> new can of worms on which project gets selected and which criteria we
>>>>> should use, on top of getting the right set of approvals from them to be
>>>>> used as projects.
>>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>>> need the license of that template that allows us to use it without
>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>> >>>>>>>>
>>>>> >>>>>>>> Javier
>>>>> >>>>>>>>
>>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> Hi James,
>>>>> >>>>>>>>> Below is the drive link of complete page screenshot of
>>>>> APACHE FINERACT redesigned website. Please review and let me know if you
>>>>> have any questions or changes needed.
>>>>> >>>>>>>>>
>>>>> >>>>>>>>>
>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> Regards,
>>>>> >>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> +1
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> Hi
>>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>>> what exact is there on the website. I'll create a static mockup for the
>>>>> website.
>>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>>> anyone new or experienced first comes to the website got confused of what's
>>>>> happening and how things are going we can work upon it.
>>>>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger
>>>>> on that website? I have ability to work on static websites where the data
>>>>> comes from dynamic CMS.
>>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>>> >>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>>> page website for the project, so not an app. The content needs to be
>>>>> largely static or to pick up content we regularly post on blog. The current
>>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>>> is a design lens, in my view. But, a good UIX process does start with
>>>>> who’s the audience and what’s their need when they land on the page.
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> Hi,
>>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we
>>>>> can get a better Idea of what exactly has to be happen. By the 16th of Feb
>>>>> I'll come up with a design also will share here in the thread and we can
>>>>> get comments in the meeting.
>>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>>> overall UI/UX
>>>>> >>>>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>>> have four people who said they'd like to be involved.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>>> mid February.
>>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>> document:
>>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>>>> detail.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>>>>> there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find
>>>>> sections you think belong being "brought over". compile a list of those
>>>>> pages. If none, great.
>>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>>>> landing page (Meta Cyrus?)
>>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>>> landing pages that you like
>>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>> confluence with links (james or ?)
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>>>> thread.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> thanks
>>>>> >>>>>>>>>>>>>>>> James
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>>> d@gwocu.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>>> and develop a good user reliable website.
>>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>>> >>>>>>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> All -
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>>> landing page at https://fineract.apache.org that could be better at
>>>>> communicating the project and community. Who wants to work on this with me?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I
>>>>> think we should have a top level split on the main page as well, or perhaps
>>>>> a separate landing page for FineractCN.
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>>> how to show two levels):
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> TBD
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs
>>>>> to be more prominent)
>>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent
>>>>> at top)
>>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>> >>>>>>>>>>>>>>>>>> Standards
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>>>>> documentation.
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>>> etc) ... all go to blog
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> --
>>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> --
>>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>>> >>
>>>>> >> --
>>>>> >> Sent from Gmail Mobile
>>>>>
>>>>> --
>>>>>
>>>>> Sent from Gmail Mobile
>>>>>
>>>>>
>>>> El contenido de este mensaje y sus archivos electrónicos adjuntos
>>>> constituyen información confidencial, y puede además contener secretos
>>>> comerciales o industriales que se encuentran protegidos bajo las leyes de
>>>> propiedad intelectual. Su uso, divulgación, revelación y/o circulación no
>>>> autorizados se encuentran estrictamente prohibidos, por lo que si usted no
>>>> es el destinatario del mismo o lo recibió por error, notifique
>>>> inmediatamente al remitente por correo electrónico y elimine el mensaje así
>>>> como toda información adjunta de su sistema. En cumplimiento de lo
>>>> establecido por las leyes de protección de datos personales, Nubloq S.A.S.
>>>> hace de su conocimiento que se encuentra a su disposición la política de
>>>> tratamiento de datos personales en la página de internet
>>>> https://www.nubloq.co/legal/ a efecto de que pueda ejercer su derecho
>>>> al hábeas data. Todos los datos personales entregados vía correo
>>>> electrónico serán utilizados de acuerdo con las finalidades allí previstas.
>>>> Puede también consultar nuestros términos y condiciones en
>>>> https://www.nubloq.co/legal/.
>>>>
>>>> The contents of this message and its attachments are confidential
>>>> information and can hold trade secrets subject to intellectual property
>>>> regulations. Its unauthorized use, divulgation, reveal and/or circulation
>>>> are therefore strictly prohibited. In the event that you are not the
>>>> intended recipient of this email, please immediately notify the sender
>>>> through email and delete the message and any attachments from your system. Pursuant
>>>> to the regulations on data privacy, Nubloq S.A.S informs that the privacy
>>>> policy is available for consultation at: https://www.nubloq.co/legal/.
>>>> All personal data will be treated in accordance with the purposes provided
>>>> therein. You can also review our terms and conditions at
>>>> https://www.nubloq.co/legal/.
>>>>
>>>
Re: Website and Wiki for Fineract updates
Posted by Javier Borkenztain <ja...@fiter.io>.
+1 on the proposal! Let's use our "lacy consensus" and start :)
On Tue, May 23, 2023 at 1:34 AM James Dailey <ja...@gmail.com> wrote:
> John - nice work.
>
> Bringing attention back to John’s proposals regarding moving some
> content from docs/current to wiki , and so deletes on wiki and in
> docs/current content .
>
> Comments?
>
> On Wed, May 17, 2023 at 11:32 PM John Gathogo <jo...@fiter.io> wrote:
>
>> Hello everyone,
>>
>> In line with this guidance as communicated by James last week with
>> regards to what each documentation asset should focus on, i.e
>>
>> ** landing page is where technical and business people come to learn
>> more, where interested devs can easily find their way to a release or to
>> documentation or to dev tasks *
>> ** wiki is where we organize our project and community and thus
>> everything that is "in process" like links to Jira tickets *
>> ** Platform Documentation for things that are developed (completed, in
>> the Platform) *
>>
>> See below my proposal of content to be moved. Reply here with comments
>> and/or recommendations
>>
>> Remove FAQs from project documentation, have it a separate page linked to
>> landing page
>> Move documentation guide content from platform documentation to project
>> wiki
>> Move testing content to project wiki
>> Remove release guidelines from platform documentation since its already
>> in project wiki
>> Is Fineract Client Documentation still necessary or can be removed?
>> Remove all deployment methods indicated as TBD example: Docker, Undertow,
>> etc
>> Move Fineract development environment content to the wiki
>> Move Modules to wiki since its aimed at contributors
>> Move Introducing Business Date into Fineract - Community version to wiki
>> until feature is released
>> Move Loan account locking to wiki until feature is released
>> Move custom modules to wiki since its aimed at contributors or fineract
>> extenders
>> Move Fineract user zone content from wiki to project documentation
>> Move performance and scalability from wiki to content to project
>> documentation
>>
>> On Wed, May 17, 2023 at 10:48 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Checking in - Any updates on the tasks?
>>> @inzemamhaq05
>>> @John Gathogo <jo...@fiter.io>
>>> +Abhinav Sinha
>>>
>>> James Dailey
>>>
>>>
>>>
>>> On Thu, May 11, 2023 at 12:05 PM James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Hi all - We held our conversation today on Zoom about the design of the
>>>> Landing page and our overall strategy of organizing content on our web
>>>> presence.
>>>>
>>>> Currently, we have the landing page: http://fineract.apache.org
>>>> (within links to various places on the wiki and github)
>>>> and we have the project site
>>>> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home
>>>> (with a complex navigation and content structure)
>>>> and we have the new Platform Documentation at
>>>> https://fineract.apache.org/docs/current/ (from github)
>>>>
>>>> Each of these serves a unique value:
>>>> * landing page is where technical and business people come to learn
>>>> more, where interested devs can easily find their way to a release or to
>>>> documentation or to dev tasks
>>>> * wiki is where we organize our project and community and thus
>>>> everything that is "in process" like links to Jira tickets
>>>> * Platform Documentation for things that are developed (completed, in
>>>> the Platform)
>>>>
>>>> next up:
>>>> Inzemam will provide a new version of the landing page and start a
>>>> fork of the current page so that we can see his approach to keeping the
>>>> html/css/javascript easy to maintain.
>>>> and John with help from Abhinav will work on assessing which pieces of
>>>> the wiki can be trimmed (if it exists on the Platform documentation or can
>>>> move over there)
>>>>
>>>> Please see the meeting notes from the ZOOM call here
>>>>
>>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>>
>>>> Thank you to those who joined today but also, if you didn't join, you
>>>> are welcome to join in the work. This is an important way to make the
>>>> project more maintainable and approachable.
>>>>
>>>> Thanks,
>>>> James
>>>>
>>>>
>>>> On Thu, May 11, 2023 at 11:38 AM Dejan Juric <de...@j13kventures.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>> please also add me.
>>>>>
>>>>> Thx,
>>>>> Dejan
>>>>>
>>>>> On Thu, May 11, 2023 at 12:55 PM Federico Benitez <fe...@nubloq.co>
>>>>> wrote:
>>>>>
>>>>>> Pls add me
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>> On 10/05/2023, at 14:33, comsky juste <co...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Please add me.
>>>>>>
>>>>>> On Wed, May 10, 2023, 3:58 AM Abhinav Sinha <ab...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Could you pls add me to the call as well
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Abhinav
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *From: *James Dailey <ja...@gmail.com>
>>>>>>> *Date: *Tuesday, May 9, 2023 at 9:53 PM
>>>>>>> *To: *dev@fineract.apache.org <de...@fineract.apache.org>
>>>>>>> *Subject: *Re: Website and Wiki for Fineract updates
>>>>>>>
>>>>>>> We will update this wiki page during and after the meeting
>>>>>>>
>>>>>>>
>>>>>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> (John - added)
>>>>>>>
>>>>>>> (Ernesto -added)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
>>>>>>>
>>>>>>> Please add me to this call.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
>>>>>>> <eo...@yahoo.com.invalid> wrote:
>>>>>>>
>>>>>>> Please add me
>>>>>>>
>>>>>>>
>>>>>>> Sent from Yahoo Mail for iPhone
>>>>>>> <https://overview.mail.yahoo.com/?.src=iOS>
>>>>>>>
>>>>>>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>>
>>>>>>> Yep I'll be there in meet call.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> W can organize a zoom call. Then report back to the list here.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I’ll suggest May 11th , 9am Pacific (PDT)
>>>>>>>
>>>>>>> I’ll send zoom link to anyone expressing interest.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>>
>>>>>>> Hello James,
>>>>>>>
>>>>>>> Sorry for the late reply I was stuck in gsoc but I know I'll get
>>>>>>> rejected so finally I am looking forward on the website as we dealt before.
>>>>>>>
>>>>>>> Can we have a zoom call? So we can get an idea of what exactly we
>>>>>>> are gonna place on the website as from the previous responses I am only
>>>>>>> getting that some of the things should be changed or replaced but with whom
>>>>>>> I can't get it.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Inzemamul Haq
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Bruce - Good to know about those gaps in deployment and tools,
>>>>>>> but are those the only gaps in the documentation?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> So, question to you: is it already sufficiently clear on these
>>>>>>> topics:
>>>>>>>
>>>>>>> * explaining what the software does
>>>>>>>
>>>>>>> * explaining the architecture
>>>>>>>
>>>>>>> * explaining relationship between different components
>>>>>>>
>>>>>>> * what features are in each release
>>>>>>>
>>>>>>> * how to set up development environment
>>>>>>>
>>>>>>> * how to access APIs
>>>>>>>
>>>>>>> * how to find additional resources
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I did ask for 3-5 priority things, so please do try to identify
>>>>>>> where we start, even from your very long list or maybe adding to it, can we
>>>>>>> get your opinion on a few key things?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> What would you say is a priority?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> As a project, I think we need to simply and only offer one or two
>>>>>>> deployment options in our documentation, that way we can focus on getting
>>>>>>> those accurate and keeping them up to date. Others are of course free to
>>>>>>> offer their own improvements and alternatives.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> All - comments welcome.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> James
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I hope this email finds you well. I wanted to share some
>>>>>>> observations after going through the documentation for Fineract again.
>>>>>>>
>>>>>>> While the documentation provides an overview of deployment options
>>>>>>> here https://fineract.apache.org/docs/current/#_deployment , I
>>>>>>> noticed that several options, such as Docker Compose, Tomcat, Undertow,
>>>>>>> Jetty, JBoss, Weblogic, and Payara, are marked as TBD, indicating a lack of
>>>>>>> content and guidance for users. There is also no deployment content on Kubernetes, AWS
>>>>>>> and Google Cloud. Let's address this.
>>>>>>>
>>>>>>> Additionally, the Fineract Development section here
>>>>>>> https://fineract.apache.org/docs/current/#_fineract_development_environment appears
>>>>>>> to be incomplete and in need of further content to cover important topics
>>>>>>> related to Fineract development. This section also includes topics marked
>>>>>>> as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
>>>>>>> Docker Desktop, IDE selection and configuration (including IntelliJ,
>>>>>>> Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
>>>>>>> Microk8s, K3d, Helm Charts, and installation and usage of various
>>>>>>> development tools like Brew for MacOS and Linux. I propose that the
>>>>>>> community contibutes content for the following topics:
>>>>>>>
>>>>>>> - Docker: how to install, run, and use Docker containers for
>>>>>>> Fineract
>>>>>>> - Docker Compose: how to use Docker Compose to orchestrate
>>>>>>> multiple containers for Fineract
>>>>>>> - Podman: how to use Podman as an alternative to Docker for
>>>>>>> running containers
>>>>>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to
>>>>>>> run Kubernetes clusters on one's local machine
>>>>>>> - IDE: how to choose and configure an IDE for Fineract
>>>>>>> development
>>>>>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>>>>>> Fineract
>>>>>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>>>>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>>>>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>>>>>> clusters
>>>>>>> - Minikube: how to use Minikube to run a local Kubernetes
>>>>>>> cluster for Fineract
>>>>>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>>>>>> cluster for Fineract
>>>>>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>>>>>> Fineract
>>>>>>> - Helm Charts: how to use Helm Charts to package and deploy
>>>>>>> Fineract applications on Kubernetes
>>>>>>> - Tools: how to install and use various tools that can help one
>>>>>>> with Fineract development
>>>>>>> - Brew: how to install and use Brew for MacOS and Linux
>>>>>>>
>>>>>>> By actively addressing these gaps in the documentation, we can
>>>>>>> provide valuable support to the Fineract community and further showcase the
>>>>>>> flexibility and compatibility of Fineract with different technologies and
>>>>>>> platforms.
>>>>>>>
>>>>>>> I look forward to collaborating with the community to contribute
>>>>>>> content for these important topics and improve the overall documentation
>>>>>>> for Fineract.
>>>>>>>
>>>>>>> Best Regards
>>>>>>>
>>>>>>> Bruce
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Meta or Bruce - any updates?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>>>>> the previous points you and others mentioned..
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> I've started to change some of the structure of the wiki. I'm just
>>>>>>> trying to clean it up: Does anyone have an objection?
>>>>>>>
>>>>>>> * Noting where content is historical and deprecating it
>>>>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>>>>
>>>>>>> This is incremental.
>>>>>>>
>>>>>>> Inzemam - can you provide a new design to review taking on the
>>>>>>> feedback?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>> >
>>>>>>> > Okay I'll be looking into it..
>>>>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the
>>>>>>> frontend fields. Surely working effectively with both the orgs by making
>>>>>>> good designs with premium feel.
>>>>>>> > Regards,
>>>>>>> > Inzemam
>>>>>>> >
>>>>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>
>>>>>>> >> Please make a set of suggestions or revise your designs based on
>>>>>>> input.
>>>>>>> >>
>>>>>>> >> Feel free to dive into this .
>>>>>>> >>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>
>>>>>>> >>> Hello James,
>>>>>>> >>> When we are going to start the work or are we leaving it for
>>>>>>> future?
>>>>>>> >>>
>>>>>>> >>> Regards,
>>>>>>> >>> Inzemam
>>>>>>> >>>
>>>>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>
>>>>>>> >>>> Hi James,
>>>>>>> >>>> You are correct that we need to discuss more on the flows of
>>>>>>> events and placements. And I am also agree with the point that we can
>>>>>>> create a slack channel for this.
>>>>>>> >>>> Also the code will be in simple html, css and js format so
>>>>>>> anyone can create/change the things easily. The design is looking fancy and
>>>>>>> complicated but the code is as smooth as butter. So need to worry about
>>>>>>> maintainance.
>>>>>>> >>>> Regards,
>>>>>>> >>>> Inzemamul Haq
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>
>>>>>>> >>>>> Hi - Thank you for this.
>>>>>>> >>>>>
>>>>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>>>>> Javier's comments, which makes clear that we need to do a better job of
>>>>>>> "Explaining" and "Positioning".
>>>>>>> >>>>>
>>>>>>> >>>>> ASIDE: Javier - I invite you to write more such text and
>>>>>>> provide a top level set of bullet points that can be perhaps worked into
>>>>>>> the content.
>>>>>>> >>>>>
>>>>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>>>>> Nice.
>>>>>>> >>>>>
>>>>>>> >>>>> We need more revamping of the content before we can properly
>>>>>>> do this design, so let's try to attack that problem.
>>>>>>> >>>>>
>>>>>>> >>>>> Here is a requirement that may not be clear to you:
>>>>>>> >>>>> * Site should be very simple, easy to change by anyone opening
>>>>>>> up a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>>>>> hopefully with names that make sense
>>>>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>>>>> some text areas, adding content in specific sections.
>>>>>>> >>>>> * Assume that no-one touches the website for over a year,
>>>>>>> maybe three years, and avoid content that can get stale.
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>> Message and Content issues:
>>>>>>> >>>>>
>>>>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>>>>> the page today. Also, there is a common set of links and structure that you
>>>>>>> can find in other Apache projects. It is not a requirement to follow other
>>>>>>> Apache projects, but it would be useful to review them for commonalities:
>>>>>>> >>>>> --> https://hadoop.apache.org
>>>>>>> >>>>> --> https://airflow.apache.org
>>>>>>> >>>>> --> https://kafka.apache.org
>>>>>>> >>>>>
>>>>>>> >>>>> * Note Community is there in each project. Check out the
>>>>>>> content that each project has.
>>>>>>> >>>>>
>>>>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>>>> >>>>> and this should then flow into the requirements for the other
>>>>>>> sections on the front page and then onto the wiki structure that we need
>>>>>>> >>>>>
>>>>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>>>>> "Additional community technologies"
>>>>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>>>>> positioning is controversial for some, but until we get a release out and
>>>>>>> lots of active development and deployments, that project remains very much
>>>>>>> a side project of the community. It may become a very important thing, but
>>>>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>>>>> the vast majority of the dev is going on, and the vast majority of the
>>>>>>> users are there.
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>>>>> should be a summary of the system.
>>>>>>> >>>>>
>>>>>>> >>>>> This may require more chat and discussion on list or on slack
>>>>>>> and then development of a structure of content before you can really get a
>>>>>>> design.
>>>>>>> >>>>>
>>>>>>> >>>>> Thank you again.
>>>>>>> >>>>>
>>>>>>> >>>>> James Dailey
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>
>>>>>>> >>>>>> Hello James,
>>>>>>> >>>>>> Have you reviewed the website frame. Please share the
>>>>>>> feedback.
>>>>>>> >>>>>> Regards,
>>>>>>> >>>>>> Inzemamul Haq
>>>>>>> >>>>>>
>>>>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>
>>>>>>> >>>>>>> Hello Javier,
>>>>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>>>>> implement them as you suggested now what I need is some more brief about
>>>>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>>>>> change and add the things.
>>>>>>> >>>>>>> As you mentioned in the last that it's a template but it's
>>>>>>> not. It's designed by me on the figma and the assets I used are open source
>>>>>>> so their will be no licencing issue. I always go for the development
>>>>>>> through scratch so no need to worry about that.
>>>>>>> >>>>>>> Regards,
>>>>>>> >>>>>>> Inzemam
>>>>>>> >>>>>>>
>>>>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>>>>> javier@fiter.io> wrote:
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> Hy Meta,
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> Great job; I like the enhancement of the visuals and
>>>>>>> aesthetic in general, and it seems much more modern and suitable for the
>>>>>>> next stage of our community.
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> My two cents:
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be
>>>>>>> useful in other areas of the industry, not just banks. We need to convey
>>>>>>> that Fineract is a platform for many use cases. Using a mobile phone and a
>>>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>>>>> be conceptual, not rigid on old paradigms.
>>>>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>>>> purchases are now digital.
>>>>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have
>>>>>>> the same exposure on our website as Fineract. Fineract CN it's still an
>>>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>>>> CN is not backward compatible with Fineract.
>>>>>>> >>>>>>>> The project we are proud of: I will only use the project
>>>>>>> part if we get three Fortune 500 companies using Fineract. It will also
>>>>>>> open a new can of worms on which project gets selected and which criteria
>>>>>>> we should use, on top of getting the right set of approvals from them to be
>>>>>>> used as projects.
>>>>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>>>>> need the license of that template that allows us to use it without
>>>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> Javier
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> Hi James,
>>>>>>> >>>>>>>>> Below is the drive link of complete page screenshot of
>>>>>>> APACHE FINERACT redesigned website. Please review and let me know if you
>>>>>>> have any questions or changes needed.
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>>
>>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> Regards,
>>>>>>> >>>>>>>>> Inzemamul Haq
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>> +1
>>>>>>> >>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> Hi
>>>>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>>>>> what exact is there on the website. I'll create a static mockup for the
>>>>>>> website.
>>>>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>>>>> anyone new or experienced first comes to the website got confused of what's
>>>>>>> happening and how things are going we can work upon it.
>>>>>>> >>>>>>>>>>>>> Also I have a question are we going to implement
>>>>>>> blogger on that website? I have ability to work on static websites where
>>>>>>> the data comes from dynamic CMS.
>>>>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>>>>> >>>>>>>>>>>>> Regards,
>>>>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>>>>> page website for the project, so not an app. The content needs to be
>>>>>>> largely static or to pick up content we regularly post on blog. The current
>>>>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s
>>>>>>> needed is a design lens, in my view. But, a good UIX process does start
>>>>>>> with who’s the audience and what’s their need when they land on the page.
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>> Hi,
>>>>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we
>>>>>>> can get a better Idea of what exactly has to be happen. By the 16th of Feb
>>>>>>> I'll come up with a design also will share here in the thread and we can
>>>>>>> get comments in the meeting.
>>>>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>>>>> overall UI/UX
>>>>>>> >>>>>>>>>>>>>>> Regards,
>>>>>>> >>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>> >>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you.
>>>>>>> We have four people who said they'd like to be involved.
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>>>>> mid February.
>>>>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>>>> document:
>>>>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page
>>>>>>> in detail.
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where
>>>>>>> is there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find
>>>>>>> sections you think belong being "brought over". compile a list of those
>>>>>>> pages. If none, great.
>>>>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of
>>>>>>> the landing page (Meta Cyrus?)
>>>>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>>>>> landing pages that you like
>>>>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>>>> confluence with links (james or ?)
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow
>>>>>>> this thread.
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> thanks
>>>>>>> >>>>>>>>>>>>>>>> James
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>>>>> d@gwocu.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>>>>> and develop a good user reliable website.
>>>>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>>>>> >>>>>>>>>>>>>>>>> Regards,
>>>>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> All -
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but
>>>>>>> it's been 3+ years since we did a clean sweep of it. We also have a front
>>>>>>> landing page at https://fineract.apache.org that could be better
>>>>>>> at communicating the project and community. Who wants to work on this with
>>>>>>> me?
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I
>>>>>>> think we should have a top level split on the main page as well, or perhaps
>>>>>>> a separate landing page for FineractCN.
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>>>>> how to show two levels):
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> TBD
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs
>>>>>>> to be more prominent)
>>>>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent
>>>>>>> at top)
>>>>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>>>> >>>>>>>>>>>>>>>>>> Standards
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically
>>>>>>> generated documentation.
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>>>>> etc) ... all go to blog
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> --
>>>>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> --
>>>>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>>>>> >>
>>>>>>> >> --
>>>>>>> >> Sent from Gmail Mobile
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Sent from Gmail Mobile
>>>>>>>
>>>>>>>
>>>>>> El contenido de este mensaje y sus archivos electrónicos adjuntos
>>>>>> constituyen información confidencial, y puede además contener secretos
>>>>>> comerciales o industriales que se encuentran protegidos bajo las leyes de
>>>>>> propiedad intelectual. Su uso, divulgación, revelación y/o circulación no
>>>>>> autorizados se encuentran estrictamente prohibidos, por lo que si usted no
>>>>>> es el destinatario del mismo o lo recibió por error, notifique
>>>>>> inmediatamente al remitente por correo electrónico y elimine el mensaje así
>>>>>> como toda información adjunta de su sistema. En cumplimiento de lo
>>>>>> establecido por las leyes de protección de datos personales, Nubloq S.A.S.
>>>>>> hace de su conocimiento que se encuentra a su disposición la política de
>>>>>> tratamiento de datos personales en la página de internet
>>>>>> https://www.nubloq.co/legal/ a efecto de que pueda ejercer su
>>>>>> derecho al hábeas data. Todos los datos personales entregados vía correo
>>>>>> electrónico serán utilizados de acuerdo con las finalidades allí previstas.
>>>>>> Puede también consultar nuestros términos y condiciones en
>>>>>> https://www.nubloq.co/legal/.
>>>>>>
>>>>>> The contents of this message and its attachments are confidential
>>>>>> information and can hold trade secrets subject to intellectual property
>>>>>> regulations. Its unauthorized use, divulgation, reveal and/or circulation
>>>>>> are therefore strictly prohibited. In the event that you are not the
>>>>>> intended recipient of this email, please immediately notify the sender
>>>>>> through email and delete the message and any attachments from your system. Pursuant
>>>>>> to the regulations on data privacy, Nubloq S.A.S informs that the privacy
>>>>>> policy is available for consultation at: https://www.nubloq.co/legal/.
>>>>>> All personal data will be treated in accordance with the purposes provided
>>>>>> therein. You can also review our terms and conditions at
>>>>>> https://www.nubloq.co/legal/.
>>>>>>
>>>>> --
> Sent from Gmail Mobile
>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
John - nice work.
Bringing attention back to John’s proposals regarding moving some content
from docs/current to wiki , and so deletes on wiki and in docs/current
content .
Comments?
On Wed, May 17, 2023 at 11:32 PM John Gathogo <jo...@fiter.io> wrote:
> Hello everyone,
>
> In line with this guidance as communicated by James last week with regards
> to what each documentation asset should focus on, i.e
>
> ** landing page is where technical and business people come to learn more,
> where interested devs can easily find their way to a release or to
> documentation or to dev tasks *
> ** wiki is where we organize our project and community and thus everything
> that is "in process" like links to Jira tickets *
> ** Platform Documentation for things that are developed (completed, in the
> Platform) *
>
> See below my proposal of content to be moved. Reply here with comments
> and/or recommendations
>
> Remove FAQs from project documentation, have it a separate page linked to
> landing page
> Move documentation guide content from platform documentation to project
> wiki
> Move testing content to project wiki
> Remove release guidelines from platform documentation since its already in
> project wiki
> Is Fineract Client Documentation still necessary or can be removed?
> Remove all deployment methods indicated as TBD example: Docker, Undertow,
> etc
> Move Fineract development environment content to the wiki
> Move Modules to wiki since its aimed at contributors
> Move Introducing Business Date into Fineract - Community version to wiki
> until feature is released
> Move Loan account locking to wiki until feature is released
> Move custom modules to wiki since its aimed at contributors or fineract
> extenders
> Move Fineract user zone content from wiki to project documentation
> Move performance and scalability from wiki to content to project
> documentation
>
> On Wed, May 17, 2023 at 10:48 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> Checking in - Any updates on the tasks?
>> @inzemamhaq05
>> @John Gathogo <jo...@fiter.io>
>> +Abhinav Sinha
>>
>> James Dailey
>>
>>
>>
>> On Thu, May 11, 2023 at 12:05 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Hi all - We held our conversation today on Zoom about the design of the
>>> Landing page and our overall strategy of organizing content on our web
>>> presence.
>>>
>>> Currently, we have the landing page: http://fineract.apache.org
>>> (within links to various places on the wiki and github)
>>> and we have the project site
>>> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home
>>> (with a complex navigation and content structure)
>>> and we have the new Platform Documentation at
>>> https://fineract.apache.org/docs/current/ (from github)
>>>
>>> Each of these serves a unique value:
>>> * landing page is where technical and business people come to learn
>>> more, where interested devs can easily find their way to a release or to
>>> documentation or to dev tasks
>>> * wiki is where we organize our project and community and thus
>>> everything that is "in process" like links to Jira tickets
>>> * Platform Documentation for things that are developed (completed, in
>>> the Platform)
>>>
>>> next up:
>>> Inzemam will provide a new version of the landing page and start a
>>> fork of the current page so that we can see his approach to keeping the
>>> html/css/javascript easy to maintain.
>>> and John with help from Abhinav will work on assessing which pieces of
>>> the wiki can be trimmed (if it exists on the Platform documentation or can
>>> move over there)
>>>
>>> Please see the meeting notes from the ZOOM call here
>>>
>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>
>>> Thank you to those who joined today but also, if you didn't join, you
>>> are welcome to join in the work. This is an important way to make the
>>> project more maintainable and approachable.
>>>
>>> Thanks,
>>> James
>>>
>>>
>>> On Thu, May 11, 2023 at 11:38 AM Dejan Juric <de...@j13kventures.com>
>>> wrote:
>>>
>>>> Hi,
>>>> please also add me.
>>>>
>>>> Thx,
>>>> Dejan
>>>>
>>>> On Thu, May 11, 2023 at 12:55 PM Federico Benitez <fe...@nubloq.co>
>>>> wrote:
>>>>
>>>>> Pls add me
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On 10/05/2023, at 14:33, comsky juste <co...@gmail.com> wrote:
>>>>>
>>>>>
>>>>> Please add me.
>>>>>
>>>>> On Wed, May 10, 2023, 3:58 AM Abhinav Sinha <ab...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Could you pls add me to the call as well
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Abhinav
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From: *James Dailey <ja...@gmail.com>
>>>>>> *Date: *Tuesday, May 9, 2023 at 9:53 PM
>>>>>> *To: *dev@fineract.apache.org <de...@fineract.apache.org>
>>>>>> *Subject: *Re: Website and Wiki for Fineract updates
>>>>>>
>>>>>> We will update this wiki page during and after the meeting
>>>>>>
>>>>>>
>>>>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>>>>
>>>>>>
>>>>>>
>>>>>> (John - added)
>>>>>>
>>>>>> (Ernesto -added)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
>>>>>>
>>>>>> Please add me to this call.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
>>>>>> <eo...@yahoo.com.invalid> wrote:
>>>>>>
>>>>>> Please add me
>>>>>>
>>>>>>
>>>>>> Sent from Yahoo Mail for iPhone
>>>>>> <https://overview.mail.yahoo.com/?.src=iOS>
>>>>>>
>>>>>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>
>>>>>> Yep I'll be there in meet call.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> W can organize a zoom call. Then report back to the list here.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I’ll suggest May 11th , 9am Pacific (PDT)
>>>>>>
>>>>>> I’ll send zoom link to anyone expressing interest.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hello James,
>>>>>>
>>>>>> Sorry for the late reply I was stuck in gsoc but I know I'll get
>>>>>> rejected so finally I am looking forward on the website as we dealt before.
>>>>>>
>>>>>> Can we have a zoom call? So we can get an idea of what exactly we are
>>>>>> gonna place on the website as from the previous responses I am only getting
>>>>>> that some of the things should be changed or replaced but with whom I can't
>>>>>> get it.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Inzemamul Haq
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hi Bruce - Good to know about those gaps in deployment and tools, but
>>>>>> are those the only gaps in the documentation?
>>>>>>
>>>>>>
>>>>>>
>>>>>> So, question to you: is it already sufficiently clear on these
>>>>>> topics:
>>>>>>
>>>>>> * explaining what the software does
>>>>>>
>>>>>> * explaining the architecture
>>>>>>
>>>>>> * explaining relationship between different components
>>>>>>
>>>>>> * what features are in each release
>>>>>>
>>>>>> * how to set up development environment
>>>>>>
>>>>>> * how to access APIs
>>>>>>
>>>>>> * how to find additional resources
>>>>>>
>>>>>>
>>>>>>
>>>>>> I did ask for 3-5 priority things, so please do try to identify where
>>>>>> we start, even from your very long list or maybe adding to it, can we get
>>>>>> your opinion on a few key things?
>>>>>>
>>>>>>
>>>>>>
>>>>>> What would you say is a priority?
>>>>>>
>>>>>>
>>>>>>
>>>>>> As a project, I think we need to simply and only offer one or two
>>>>>> deployment options in our documentation, that way we can focus on getting
>>>>>> those accurate and keeping them up to date. Others are of course free to
>>>>>> offer their own improvements and alternatives.
>>>>>>
>>>>>>
>>>>>>
>>>>>> All - comments welcome.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> James
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>>
>>>>>> I hope this email finds you well. I wanted to share some observations
>>>>>> after going through the documentation for Fineract again.
>>>>>>
>>>>>> While the documentation provides an overview of deployment options
>>>>>> here https://fineract.apache.org/docs/current/#_deployment , I
>>>>>> noticed that several options, such as Docker Compose, Tomcat, Undertow,
>>>>>> Jetty, JBoss, Weblogic, and Payara, are marked as TBD, indicating a lack of
>>>>>> content and guidance for users. There is also no deployment content on Kubernetes, AWS
>>>>>> and Google Cloud. Let's address this.
>>>>>>
>>>>>> Additionally, the Fineract Development section here
>>>>>> https://fineract.apache.org/docs/current/#_fineract_development_environment appears
>>>>>> to be incomplete and in need of further content to cover important topics
>>>>>> related to Fineract development. This section also includes topics marked
>>>>>> as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
>>>>>> Docker Desktop, IDE selection and configuration (including IntelliJ,
>>>>>> Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
>>>>>> Microk8s, K3d, Helm Charts, and installation and usage of various
>>>>>> development tools like Brew for MacOS and Linux. I propose that the
>>>>>> community contibutes content for the following topics:
>>>>>>
>>>>>> - Docker: how to install, run, and use Docker containers for
>>>>>> Fineract
>>>>>> - Docker Compose: how to use Docker Compose to orchestrate
>>>>>> multiple containers for Fineract
>>>>>> - Podman: how to use Podman as an alternative to Docker for
>>>>>> running containers
>>>>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to
>>>>>> run Kubernetes clusters on one's local machine
>>>>>> - IDE: how to choose and configure an IDE for Fineract development
>>>>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>>>>> Fineract
>>>>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>>>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>>>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>>>>> clusters
>>>>>> - Minikube: how to use Minikube to run a local Kubernetes cluster
>>>>>> for Fineract
>>>>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>>>>> cluster for Fineract
>>>>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>>>>> Fineract
>>>>>> - Helm Charts: how to use Helm Charts to package and deploy
>>>>>> Fineract applications on Kubernetes
>>>>>> - Tools: how to install and use various tools that can help one
>>>>>> with Fineract development
>>>>>> - Brew: how to install and use Brew for MacOS and Linux
>>>>>>
>>>>>> By actively addressing these gaps in the documentation, we can
>>>>>> provide valuable support to the Fineract community and further showcase the
>>>>>> flexibility and compatibility of Fineract with different technologies and
>>>>>> platforms.
>>>>>>
>>>>>> I look forward to collaborating with the community to contribute
>>>>>> content for these important topics and improve the overall documentation
>>>>>> for Fineract.
>>>>>>
>>>>>> Best Regards
>>>>>>
>>>>>> Bruce
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Meta or Bruce - any updates?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>>>> the previous points you and others mentioned..
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> I've started to change some of the structure of the wiki. I'm just
>>>>>> trying to clean it up: Does anyone have an objection?
>>>>>>
>>>>>> * Noting where content is historical and deprecating it
>>>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>>>
>>>>>> This is incremental.
>>>>>>
>>>>>> Inzemam - can you provide a new design to review taking on the
>>>>>> feedback?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>> >
>>>>>> > Okay I'll be looking into it..
>>>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the
>>>>>> frontend fields. Surely working effectively with both the orgs by making
>>>>>> good designs with premium feel.
>>>>>> > Regards,
>>>>>> > Inzemam
>>>>>> >
>>>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>> >>
>>>>>> >> Please make a set of suggestions or revise your designs based on
>>>>>> input.
>>>>>> >>
>>>>>> >> Feel free to dive into this .
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>> >>>
>>>>>> >>> Hello James,
>>>>>> >>> When we are going to start the work or are we leaving it for
>>>>>> future?
>>>>>> >>>
>>>>>> >>> Regards,
>>>>>> >>> Inzemam
>>>>>> >>>
>>>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>>>> wrote:
>>>>>> >>>>
>>>>>> >>>> Hi James,
>>>>>> >>>> You are correct that we need to discuss more on the flows of
>>>>>> events and placements. And I am also agree with the point that we can
>>>>>> create a slack channel for this.
>>>>>> >>>> Also the code will be in simple html, css and js format so
>>>>>> anyone can create/change the things easily. The design is looking fancy and
>>>>>> complicated but the code is as smooth as butter. So need to worry about
>>>>>> maintainance.
>>>>>> >>>> Regards,
>>>>>> >>>> Inzemamul Haq
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>
>>>>>> >>>>> Hi - Thank you for this.
>>>>>> >>>>>
>>>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>>>> Javier's comments, which makes clear that we need to do a better job of
>>>>>> "Explaining" and "Positioning".
>>>>>> >>>>>
>>>>>> >>>>> ASIDE: Javier - I invite you to write more such text and
>>>>>> provide a top level set of bullet points that can be perhaps worked into
>>>>>> the content.
>>>>>> >>>>>
>>>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>>>> Nice.
>>>>>> >>>>>
>>>>>> >>>>> We need more revamping of the content before we can properly do
>>>>>> this design, so let's try to attack that problem.
>>>>>> >>>>>
>>>>>> >>>>> Here is a requirement that may not be clear to you:
>>>>>> >>>>> * Site should be very simple, easy to change by anyone opening
>>>>>> up a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>>>> hopefully with names that make sense
>>>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>>>> some text areas, adding content in specific sections.
>>>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>>>> three years, and avoid content that can get stale.
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> Message and Content issues:
>>>>>> >>>>>
>>>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>>>> the page today. Also, there is a common set of links and structure that you
>>>>>> can find in other Apache projects. It is not a requirement to follow other
>>>>>> Apache projects, but it would be useful to review them for commonalities:
>>>>>> >>>>> --> https://hadoop.apache.org
>>>>>> >>>>> --> https://airflow.apache.org
>>>>>> >>>>> --> https://kafka.apache.org
>>>>>> >>>>>
>>>>>> >>>>> * Note Community is there in each project. Check out the
>>>>>> content that each project has.
>>>>>> >>>>>
>>>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>>> >>>>> and this should then flow into the requirements for the other
>>>>>> sections on the front page and then onto the wiki structure that we need
>>>>>> >>>>>
>>>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>>>> "Additional community technologies"
>>>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>>>> positioning is controversial for some, but until we get a release out and
>>>>>> lots of active development and deployments, that project remains very much
>>>>>> a side project of the community. It may become a very important thing, but
>>>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>>>> the vast majority of the dev is going on, and the vast majority of the
>>>>>> users are there.
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>>>> should be a summary of the system.
>>>>>> >>>>>
>>>>>> >>>>> This may require more chat and discussion on list or on slack
>>>>>> and then development of a structure of content before you can really get a
>>>>>> design.
>>>>>> >>>>>
>>>>>> >>>>> Thank you again.
>>>>>> >>>>>
>>>>>> >>>>> James Dailey
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>
>>>>>> >>>>>> Hello James,
>>>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>>> >>>>>> Regards,
>>>>>> >>>>>> Inzemamul Haq
>>>>>> >>>>>>
>>>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>
>>>>>> >>>>>>> Hello Javier,
>>>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>>>> implement them as you suggested now what I need is some more brief about
>>>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>>>> change and add the things.
>>>>>> >>>>>>> As you mentioned in the last that it's a template but it's
>>>>>> not. It's designed by me on the figma and the assets I used are open source
>>>>>> so their will be no licencing issue. I always go for the development
>>>>>> through scratch so no need to worry about that.
>>>>>> >>>>>>> Regards,
>>>>>> >>>>>>> Inzemam
>>>>>> >>>>>>>
>>>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>>>> javier@fiter.io> wrote:
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Hy Meta,
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Great job; I like the enhancement of the visuals and
>>>>>> aesthetic in general, and it seems much more modern and suitable for the
>>>>>> next stage of our community.
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> My two cents:
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be
>>>>>> useful in other areas of the industry, not just banks. We need to convey
>>>>>> that Fineract is a platform for many use cases. Using a mobile phone and a
>>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>>>> be conceptual, not rigid on old paradigms.
>>>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>>> purchases are now digital.
>>>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have
>>>>>> the same exposure on our website as Fineract. Fineract CN it's still an
>>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>>> CN is not backward compatible with Fineract.
>>>>>> >>>>>>>> The project we are proud of: I will only use the project
>>>>>> part if we get three Fortune 500 companies using Fineract. It will also
>>>>>> open a new can of worms on which project gets selected and which criteria
>>>>>> we should use, on top of getting the right set of approvals from them to be
>>>>>> used as projects.
>>>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>>>> need the license of that template that allows us to use it without
>>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Javier
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> Hi James,
>>>>>> >>>>>>>>> Below is the drive link of complete page screenshot of
>>>>>> APACHE FINERACT redesigned website. Please review and let me know if you
>>>>>> have any questions or changes needed.
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>>
>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> Regards,
>>>>>> >>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>> +1
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> Hi
>>>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>>>> what exact is there on the website. I'll create a static mockup for the
>>>>>> website.
>>>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>>>> anyone new or experienced first comes to the website got confused of what's
>>>>>> happening and how things are going we can work upon it.
>>>>>> >>>>>>>>>>>>> Also I have a question are we going to implement
>>>>>> blogger on that website? I have ability to work on static websites where
>>>>>> the data comes from dynamic CMS.
>>>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>>>> >>>>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>>>> page website for the project, so not an app. The content needs to be
>>>>>> largely static or to pick up content we regularly post on blog. The current
>>>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>>>> is a design lens, in my view. But, a good UIX process does start with
>>>>>> who’s the audience and what’s their need when they land on the page.
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>> Hi,
>>>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we
>>>>>> can get a better Idea of what exactly has to be happen. By the 16th of Feb
>>>>>> I'll come up with a design also will share here in the thread and we can
>>>>>> get comments in the meeting.
>>>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>>>> overall UI/UX
>>>>>> >>>>>>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>>>> have four people who said they'd like to be involved.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>>>> mid February.
>>>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>>> document:
>>>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page
>>>>>> in detail.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where
>>>>>> is there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find
>>>>>> sections you think belong being "brought over". compile a list of those
>>>>>> pages. If none, great.
>>>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of
>>>>>> the landing page (Meta Cyrus?)
>>>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>>>> landing pages that you like
>>>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>>> confluence with links (james or ?)
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow
>>>>>> this thread.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> thanks
>>>>>> >>>>>>>>>>>>>>>> James
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>>>> d@gwocu.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>>>> and develop a good user reliable website.
>>>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>>>> >>>>>>>>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> All -
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>>>> landing page at https://fineract.apache.org that could be better at
>>>>>> communicating the project and community. Who wants to work on this with me?
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I
>>>>>> think we should have a top level split on the main page as well, or perhaps
>>>>>> a separate landing page for FineractCN.
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>>>> how to show two levels):
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> TBD
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs
>>>>>> to be more prominent)
>>>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent
>>>>>> at top)
>>>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>>> >>>>>>>>>>>>>>>>>> Standards
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically
>>>>>> generated documentation.
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>>>> etc) ... all go to blog
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> --
>>>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> --
>>>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>>>> >>
>>>>>> >> --
>>>>>> >> Sent from Gmail Mobile
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Sent from Gmail Mobile
>>>>>>
>>>>>>
>>>>> El contenido de este mensaje y sus archivos electrónicos adjuntos
>>>>> constituyen información confidencial, y puede además contener secretos
>>>>> comerciales o industriales que se encuentran protegidos bajo las leyes de
>>>>> propiedad intelectual. Su uso, divulgación, revelación y/o circulación no
>>>>> autorizados se encuentran estrictamente prohibidos, por lo que si usted no
>>>>> es el destinatario del mismo o lo recibió por error, notifique
>>>>> inmediatamente al remitente por correo electrónico y elimine el mensaje así
>>>>> como toda información adjunta de su sistema. En cumplimiento de lo
>>>>> establecido por las leyes de protección de datos personales, Nubloq S.A.S.
>>>>> hace de su conocimiento que se encuentra a su disposición la política de
>>>>> tratamiento de datos personales en la página de internet
>>>>> https://www.nubloq.co/legal/ a efecto de que pueda ejercer su derecho
>>>>> al hábeas data. Todos los datos personales entregados vía correo
>>>>> electrónico serán utilizados de acuerdo con las finalidades allí previstas.
>>>>> Puede también consultar nuestros términos y condiciones en
>>>>> https://www.nubloq.co/legal/.
>>>>>
>>>>> The contents of this message and its attachments are confidential
>>>>> information and can hold trade secrets subject to intellectual property
>>>>> regulations. Its unauthorized use, divulgation, reveal and/or circulation
>>>>> are therefore strictly prohibited. In the event that you are not the
>>>>> intended recipient of this email, please immediately notify the sender
>>>>> through email and delete the message and any attachments from your system. Pursuant
>>>>> to the regulations on data privacy, Nubloq S.A.S informs that the privacy
>>>>> policy is available for consultation at: https://www.nubloq.co/legal/.
>>>>> All personal data will be treated in accordance with the purposes provided
>>>>> therein. You can also review our terms and conditions at
>>>>> https://www.nubloq.co/legal/.
>>>>>
>>>> --
Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by John Gathogo <jo...@fiter.io>.
Hello everyone,
In line with this guidance as communicated by James last week with regards
to what each documentation asset should focus on, i.e
** landing page is where technical and business people come to learn more,
where interested devs can easily find their way to a release or to
documentation or to dev tasks *
** wiki is where we organize our project and community and thus everything
that is "in process" like links to Jira tickets *
** Platform Documentation for things that are developed (completed, in the
Platform) *
See below my proposal of content to be moved. Reply here with comments
and/or recommendations
Remove FAQs from project documentation, have it a separate page linked to
landing page
Move documentation guide content from platform documentation to project wiki
Move testing content to project wiki
Remove release guidelines from platform documentation since its already in
project wiki
Is Fineract Client Documentation still necessary or can be removed?
Remove all deployment methods indicated as TBD example: Docker, Undertow,
etc
Move Fineract development environment content to the wiki
Move Modules to wiki since its aimed at contributors
Move Introducing Business Date into Fineract - Community version to wiki
until feature is released
Move Loan account locking to wiki until feature is released
Move custom modules to wiki since its aimed at contributors or fineract
extenders
Move Fineract user zone content from wiki to project documentation
Move performance and scalability from wiki to content to project
documentation
On Wed, May 17, 2023 at 10:48 PM James Dailey <ja...@gmail.com>
wrote:
> Checking in - Any updates on the tasks?
> @inzemamhaq05
> @John Gathogo <jo...@fiter.io>
> +Abhinav Sinha
>
> James Dailey
>
>
>
> On Thu, May 11, 2023 at 12:05 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> Hi all - We held our conversation today on Zoom about the design of the
>> Landing page and our overall strategy of organizing content on our web
>> presence.
>>
>> Currently, we have the landing page: http://fineract.apache.org (within
>> links to various places on the wiki and github)
>> and we have the project site
>> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home
>> (with a complex navigation and content structure)
>> and we have the new Platform Documentation at
>> https://fineract.apache.org/docs/current/ (from github)
>>
>> Each of these serves a unique value:
>> * landing page is where technical and business people come to learn more,
>> where interested devs can easily find their way to a release or to
>> documentation or to dev tasks
>> * wiki is where we organize our project and community and thus everything
>> that is "in process" like links to Jira tickets
>> * Platform Documentation for things that are developed (completed, in the
>> Platform)
>>
>> next up:
>> Inzemam will provide a new version of the landing page and start a fork
>> of the current page so that we can see his approach to keeping the
>> html/css/javascript easy to maintain.
>> and John with help from Abhinav will work on assessing which pieces of
>> the wiki can be trimmed (if it exists on the Platform documentation or can
>> move over there)
>>
>> Please see the meeting notes from the ZOOM call here
>>
>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>
>> Thank you to those who joined today but also, if you didn't join, you are
>> welcome to join in the work. This is an important way to make the project
>> more maintainable and approachable.
>>
>> Thanks,
>> James
>>
>>
>> On Thu, May 11, 2023 at 11:38 AM Dejan Juric <de...@j13kventures.com>
>> wrote:
>>
>>> Hi,
>>> please also add me.
>>>
>>> Thx,
>>> Dejan
>>>
>>> On Thu, May 11, 2023 at 12:55 PM Federico Benitez <fe...@nubloq.co>
>>> wrote:
>>>
>>>> Pls add me
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On 10/05/2023, at 14:33, comsky juste <co...@gmail.com> wrote:
>>>>
>>>>
>>>> Please add me.
>>>>
>>>> On Wed, May 10, 2023, 3:58 AM Abhinav Sinha <ab...@gmail.com>
>>>> wrote:
>>>>
>>>>> Could you pls add me to the call as well
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Abhinav
>>>>>
>>>>>
>>>>>
>>>>> *From: *James Dailey <ja...@gmail.com>
>>>>> *Date: *Tuesday, May 9, 2023 at 9:53 PM
>>>>> *To: *dev@fineract.apache.org <de...@fineract.apache.org>
>>>>> *Subject: *Re: Website and Wiki for Fineract updates
>>>>>
>>>>> We will update this wiki page during and after the meeting
>>>>>
>>>>>
>>>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>>>
>>>>>
>>>>>
>>>>> (John - added)
>>>>>
>>>>> (Ernesto -added)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
>>>>>
>>>>> Please add me to this call.
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
>>>>> <eo...@yahoo.com.invalid> wrote:
>>>>>
>>>>> Please add me
>>>>>
>>>>>
>>>>> Sent from Yahoo Mail for iPhone
>>>>> <https://overview.mail.yahoo.com/?.src=iOS>
>>>>>
>>>>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>
>>>>> Yep I'll be there in meet call.
>>>>>
>>>>>
>>>>>
>>>>> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> W can organize a zoom call. Then report back to the list here.
>>>>>
>>>>>
>>>>>
>>>>> I’ll suggest May 11th , 9am Pacific (PDT)
>>>>>
>>>>> I’ll send zoom link to anyone expressing interest.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hello James,
>>>>>
>>>>> Sorry for the late reply I was stuck in gsoc but I know I'll get
>>>>> rejected so finally I am looking forward on the website as we dealt before.
>>>>>
>>>>> Can we have a zoom call? So we can get an idea of what exactly we are
>>>>> gonna place on the website as from the previous responses I am only getting
>>>>> that some of the things should be changed or replaced but with whom I can't
>>>>> get it.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Inzemamul Haq
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi Bruce - Good to know about those gaps in deployment and tools, but
>>>>> are those the only gaps in the documentation?
>>>>>
>>>>>
>>>>>
>>>>> So, question to you: is it already sufficiently clear on these
>>>>> topics:
>>>>>
>>>>> * explaining what the software does
>>>>>
>>>>> * explaining the architecture
>>>>>
>>>>> * explaining relationship between different components
>>>>>
>>>>> * what features are in each release
>>>>>
>>>>> * how to set up development environment
>>>>>
>>>>> * how to access APIs
>>>>>
>>>>> * how to find additional resources
>>>>>
>>>>>
>>>>>
>>>>> I did ask for 3-5 priority things, so please do try to identify where
>>>>> we start, even from your very long list or maybe adding to it, can we get
>>>>> your opinion on a few key things?
>>>>>
>>>>>
>>>>>
>>>>> What would you say is a priority?
>>>>>
>>>>>
>>>>>
>>>>> As a project, I think we need to simply and only offer one or two
>>>>> deployment options in our documentation, that way we can focus on getting
>>>>> those accurate and keeping them up to date. Others are of course free to
>>>>> offer their own improvements and alternatives.
>>>>>
>>>>>
>>>>>
>>>>> All - comments welcome.
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> James
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>> I hope this email finds you well. I wanted to share some observations
>>>>> after going through the documentation for Fineract again.
>>>>>
>>>>> While the documentation provides an overview of deployment options
>>>>> here https://fineract.apache.org/docs/current/#_deployment , I
>>>>> noticed that several options, such as Docker Compose, Tomcat, Undertow,
>>>>> Jetty, JBoss, Weblogic, and Payara, are marked as TBD, indicating a lack of
>>>>> content and guidance for users. There is also no deployment content on Kubernetes, AWS
>>>>> and Google Cloud. Let's address this.
>>>>>
>>>>> Additionally, the Fineract Development section here
>>>>> https://fineract.apache.org/docs/current/#_fineract_development_environment appears
>>>>> to be incomplete and in need of further content to cover important topics
>>>>> related to Fineract development. This section also includes topics marked
>>>>> as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
>>>>> Docker Desktop, IDE selection and configuration (including IntelliJ,
>>>>> Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
>>>>> Microk8s, K3d, Helm Charts, and installation and usage of various
>>>>> development tools like Brew for MacOS and Linux. I propose that the
>>>>> community contibutes content for the following topics:
>>>>>
>>>>> - Docker: how to install, run, and use Docker containers for
>>>>> Fineract
>>>>> - Docker Compose: how to use Docker Compose to orchestrate
>>>>> multiple containers for Fineract
>>>>> - Podman: how to use Podman as an alternative to Docker for
>>>>> running containers
>>>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>>>>> Kubernetes clusters on one's local machine
>>>>> - IDE: how to choose and configure an IDE for Fineract development
>>>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>>>> Fineract
>>>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>>>> clusters
>>>>> - Minikube: how to use Minikube to run a local Kubernetes cluster
>>>>> for Fineract
>>>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>>>> cluster for Fineract
>>>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>>>> Fineract
>>>>> - Helm Charts: how to use Helm Charts to package and deploy
>>>>> Fineract applications on Kubernetes
>>>>> - Tools: how to install and use various tools that can help one
>>>>> with Fineract development
>>>>> - Brew: how to install and use Brew for MacOS and Linux
>>>>>
>>>>> By actively addressing these gaps in the documentation, we can provide
>>>>> valuable support to the Fineract community and further showcase the
>>>>> flexibility and compatibility of Fineract with different technologies and
>>>>> platforms.
>>>>>
>>>>> I look forward to collaborating with the community to contribute
>>>>> content for these important topics and improve the overall documentation
>>>>> for Fineract.
>>>>>
>>>>> Best Regards
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Meta or Bruce - any updates?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>>> the previous points you and others mentioned..
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> I've started to change some of the structure of the wiki. I'm just
>>>>> trying to clean it up: Does anyone have an objection?
>>>>>
>>>>> * Noting where content is historical and deprecating it
>>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>>
>>>>> This is incremental.
>>>>>
>>>>> Inzemam - can you provide a new design to review taking on the
>>>>> feedback?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>> >
>>>>> > Okay I'll be looking into it..
>>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>>>>> fields. Surely working effectively with both the orgs by making good
>>>>> designs with premium feel.
>>>>> > Regards,
>>>>> > Inzemam
>>>>> >
>>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> Please make a set of suggestions or revise your designs based on
>>>>> input.
>>>>> >>
>>>>> >> Feel free to dive into this .
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>> >>>
>>>>> >>> Hello James,
>>>>> >>> When we are going to start the work or are we leaving it for
>>>>> future?
>>>>> >>>
>>>>> >>> Regards,
>>>>> >>> Inzemam
>>>>> >>>
>>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>>> wrote:
>>>>> >>>>
>>>>> >>>> Hi James,
>>>>> >>>> You are correct that we need to discuss more on the flows of
>>>>> events and placements. And I am also agree with the point that we can
>>>>> create a slack channel for this.
>>>>> >>>> Also the code will be in simple html, css and js format so anyone
>>>>> can create/change the things easily. The design is looking fancy and
>>>>> complicated but the code is as smooth as butter. So need to worry about
>>>>> maintainance.
>>>>> >>>> Regards,
>>>>> >>>> Inzemamul Haq
>>>>> >>>>
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>
>>>>> >>>>> Hi - Thank you for this.
>>>>> >>>>>
>>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>>> Javier's comments, which makes clear that we need to do a better job of
>>>>> "Explaining" and "Positioning".
>>>>> >>>>>
>>>>> >>>>> ASIDE: Javier - I invite you to write more such text and
>>>>> provide a top level set of bullet points that can be perhaps worked into
>>>>> the content.
>>>>> >>>>>
>>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>>> Nice.
>>>>> >>>>>
>>>>> >>>>> We need more revamping of the content before we can properly do
>>>>> this design, so let's try to attack that problem.
>>>>> >>>>>
>>>>> >>>>> Here is a requirement that may not be clear to you:
>>>>> >>>>> * Site should be very simple, easy to change by anyone opening
>>>>> up a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>>> hopefully with names that make sense
>>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>>> some text areas, adding content in specific sections.
>>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>>> three years, and avoid content that can get stale.
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> Message and Content issues:
>>>>> >>>>>
>>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>>> the page today. Also, there is a common set of links and structure that you
>>>>> can find in other Apache projects. It is not a requirement to follow other
>>>>> Apache projects, but it would be useful to review them for commonalities:
>>>>> >>>>> --> https://hadoop.apache.org
>>>>> >>>>> --> https://airflow.apache.org
>>>>> >>>>> --> https://kafka.apache.org
>>>>> >>>>>
>>>>> >>>>> * Note Community is there in each project. Check out the
>>>>> content that each project has.
>>>>> >>>>>
>>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>> >>>>> and this should then flow into the requirements for the other
>>>>> sections on the front page and then onto the wiki structure that we need
>>>>> >>>>>
>>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>>> "Additional community technologies"
>>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>>> positioning is controversial for some, but until we get a release out and
>>>>> lots of active development and deployments, that project remains very much
>>>>> a side project of the community. It may become a very important thing, but
>>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>>> the vast majority of the dev is going on, and the vast majority of the
>>>>> users are there.
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>>> should be a summary of the system.
>>>>> >>>>>
>>>>> >>>>> This may require more chat and discussion on list or on slack
>>>>> and then development of a structure of content before you can really get a
>>>>> design.
>>>>> >>>>>
>>>>> >>>>> Thank you again.
>>>>> >>>>>
>>>>> >>>>> James Dailey
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>
>>>>> >>>>>> Hello James,
>>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>> >>>>>> Regards,
>>>>> >>>>>> Inzemamul Haq
>>>>> >>>>>>
>>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>
>>>>> >>>>>>> Hello Javier,
>>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>>> implement them as you suggested now what I need is some more brief about
>>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>>> change and add the things.
>>>>> >>>>>>> As you mentioned in the last that it's a template but it's
>>>>> not. It's designed by me on the figma and the assets I used are open source
>>>>> so their will be no licencing issue. I always go for the development
>>>>> through scratch so no need to worry about that.
>>>>> >>>>>>> Regards,
>>>>> >>>>>>> Inzemam
>>>>> >>>>>>>
>>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>>> javier@fiter.io> wrote:
>>>>> >>>>>>>>
>>>>> >>>>>>>> Hy Meta,
>>>>> >>>>>>>>
>>>>> >>>>>>>> Great job; I like the enhancement of the visuals and
>>>>> aesthetic in general, and it seems much more modern and suitable for the
>>>>> next stage of our community.
>>>>> >>>>>>>>
>>>>> >>>>>>>> My two cents:
>>>>> >>>>>>>>
>>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful
>>>>> in other areas of the industry, not just banks. We need to convey that
>>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>>> be conceptual, not rigid on old paradigms.
>>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>> purchases are now digital.
>>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>> CN is not backward compatible with Fineract.
>>>>> >>>>>>>> The project we are proud of: I will only use the project part
>>>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>>>> new can of worms on which project gets selected and which criteria we
>>>>> should use, on top of getting the right set of approvals from them to be
>>>>> used as projects.
>>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>>> need the license of that template that allows us to use it without
>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>> >>>>>>>>
>>>>> >>>>>>>> Javier
>>>>> >>>>>>>>
>>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> Hi James,
>>>>> >>>>>>>>> Below is the drive link of complete page screenshot of
>>>>> APACHE FINERACT redesigned website. Please review and let me know if you
>>>>> have any questions or changes needed.
>>>>> >>>>>>>>>
>>>>> >>>>>>>>>
>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> Regards,
>>>>> >>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> +1
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> Hi
>>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>>> what exact is there on the website. I'll create a static mockup for the
>>>>> website.
>>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>>> anyone new or experienced first comes to the website got confused of what's
>>>>> happening and how things are going we can work upon it.
>>>>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger
>>>>> on that website? I have ability to work on static websites where the data
>>>>> comes from dynamic CMS.
>>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>>> >>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>>> page website for the project, so not an app. The content needs to be
>>>>> largely static or to pick up content we regularly post on blog. The current
>>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>>> is a design lens, in my view. But, a good UIX process does start with
>>>>> who’s the audience and what’s their need when they land on the page.
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> Hi,
>>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we
>>>>> can get a better Idea of what exactly has to be happen. By the 16th of Feb
>>>>> I'll come up with a design also will share here in the thread and we can
>>>>> get comments in the meeting.
>>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>>> overall UI/UX
>>>>> >>>>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>>> have four people who said they'd like to be involved.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>>> mid February.
>>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>> document:
>>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>>>> detail.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>>>>> there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find
>>>>> sections you think belong being "brought over". compile a list of those
>>>>> pages. If none, great.
>>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>>>> landing page (Meta Cyrus?)
>>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>>> landing pages that you like
>>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>> confluence with links (james or ?)
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>>>> thread.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> thanks
>>>>> >>>>>>>>>>>>>>>> James
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>>> d@gwocu.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>>> and develop a good user reliable website.
>>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>>> >>>>>>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> All -
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>>> landing page at https://fineract.apache.org that could be better at
>>>>> communicating the project and community. Who wants to work on this with me?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I
>>>>> think we should have a top level split on the main page as well, or perhaps
>>>>> a separate landing page for FineractCN.
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>>> how to show two levels):
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> TBD
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs
>>>>> to be more prominent)
>>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent
>>>>> at top)
>>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>> >>>>>>>>>>>>>>>>>> Standards
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>>>>> documentation.
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>>> etc) ... all go to blog
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> --
>>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> --
>>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>>> >>
>>>>> >> --
>>>>> >> Sent from Gmail Mobile
>>>>>
>>>>> --
>>>>>
>>>>> Sent from Gmail Mobile
>>>>>
>>>>>
>>>> El contenido de este mensaje y sus archivos electrónicos adjuntos
>>>> constituyen información confidencial, y puede además contener secretos
>>>> comerciales o industriales que se encuentran protegidos bajo las leyes de
>>>> propiedad intelectual. Su uso, divulgación, revelación y/o circulación no
>>>> autorizados se encuentran estrictamente prohibidos, por lo que si usted no
>>>> es el destinatario del mismo o lo recibió por error, notifique
>>>> inmediatamente al remitente por correo electrónico y elimine el mensaje así
>>>> como toda información adjunta de su sistema. En cumplimiento de lo
>>>> establecido por las leyes de protección de datos personales, Nubloq S.A.S.
>>>> hace de su conocimiento que se encuentra a su disposición la política de
>>>> tratamiento de datos personales en la página de internet
>>>> https://www.nubloq.co/legal/ a efecto de que pueda ejercer su derecho
>>>> al hábeas data. Todos los datos personales entregados vía correo
>>>> electrónico serán utilizados de acuerdo con las finalidades allí previstas.
>>>> Puede también consultar nuestros términos y condiciones en
>>>> https://www.nubloq.co/legal/.
>>>>
>>>> The contents of this message and its attachments are confidential
>>>> information and can hold trade secrets subject to intellectual property
>>>> regulations. Its unauthorized use, divulgation, reveal and/or circulation
>>>> are therefore strictly prohibited. In the event that you are not the
>>>> intended recipient of this email, please immediately notify the sender
>>>> through email and delete the message and any attachments from your system. Pursuant
>>>> to the regulations on data privacy, Nubloq S.A.S informs that the privacy
>>>> policy is available for consultation at: https://www.nubloq.co/legal/.
>>>> All personal data will be treated in accordance with the purposes provided
>>>> therein. You can also review our terms and conditions at
>>>> https://www.nubloq.co/legal/.
>>>>
>>>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Checking in - Any updates on the tasks?
@inzemamhaq05
@John Gathogo <jo...@fiter.io>
+Abhinav Sinha
James Dailey
On Thu, May 11, 2023 at 12:05 PM James Dailey <ja...@gmail.com>
wrote:
> Hi all - We held our conversation today on Zoom about the design of the
> Landing page and our overall strategy of organizing content on our web
> presence.
>
> Currently, we have the landing page: http://fineract.apache.org (within
> links to various places on the wiki and github)
> and we have the project site
> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home (with
> a complex navigation and content structure)
> and we have the new Platform Documentation at
> https://fineract.apache.org/docs/current/ (from github)
>
> Each of these serves a unique value:
> * landing page is where technical and business people come to learn more,
> where interested devs can easily find their way to a release or to
> documentation or to dev tasks
> * wiki is where we organize our project and community and thus everything
> that is "in process" like links to Jira tickets
> * Platform Documentation for things that are developed (completed, in the
> Platform)
>
> next up:
> Inzemam will provide a new version of the landing page and start a fork
> of the current page so that we can see his approach to keeping the
> html/css/javascript easy to maintain.
> and John with help from Abhinav will work on assessing which pieces of the
> wiki can be trimmed (if it exists on the Platform documentation or can move
> over there)
>
> Please see the meeting notes from the ZOOM call here
>
> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>
> Thank you to those who joined today but also, if you didn't join, you are
> welcome to join in the work. This is an important way to make the project
> more maintainable and approachable.
>
> Thanks,
> James
>
>
> On Thu, May 11, 2023 at 11:38 AM Dejan Juric <de...@j13kventures.com>
> wrote:
>
>> Hi,
>> please also add me.
>>
>> Thx,
>> Dejan
>>
>> On Thu, May 11, 2023 at 12:55 PM Federico Benitez <fe...@nubloq.co>
>> wrote:
>>
>>> Pls add me
>>>
>>> Sent from my iPhone
>>>
>>> On 10/05/2023, at 14:33, comsky juste <co...@gmail.com> wrote:
>>>
>>>
>>> Please add me.
>>>
>>> On Wed, May 10, 2023, 3:58 AM Abhinav Sinha <ab...@gmail.com>
>>> wrote:
>>>
>>>> Could you pls add me to the call as well
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Abhinav
>>>>
>>>>
>>>>
>>>> *From: *James Dailey <ja...@gmail.com>
>>>> *Date: *Tuesday, May 9, 2023 at 9:53 PM
>>>> *To: *dev@fineract.apache.org <de...@fineract.apache.org>
>>>> *Subject: *Re: Website and Wiki for Fineract updates
>>>>
>>>> We will update this wiki page during and after the meeting
>>>>
>>>>
>>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>>
>>>>
>>>>
>>>> (John - added)
>>>>
>>>> (Ernesto -added)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
>>>>
>>>> Please add me to this call.
>>>>
>>>>
>>>>
>>>> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
>>>> <eo...@yahoo.com.invalid> wrote:
>>>>
>>>> Please add me
>>>>
>>>>
>>>> Sent from Yahoo Mail for iPhone
>>>> <https://overview.mail.yahoo.com/?.src=iOS>
>>>>
>>>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <
>>>> inzemamhaq05@gmail.com> wrote:
>>>>
>>>> Yep I'll be there in meet call.
>>>>
>>>>
>>>>
>>>> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>> W can organize a zoom call. Then report back to the list here.
>>>>
>>>>
>>>>
>>>> I’ll suggest May 11th , 9am Pacific (PDT)
>>>>
>>>> I’ll send zoom link to anyone expressing interest.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
>>>> wrote:
>>>>
>>>> Hello James,
>>>>
>>>> Sorry for the late reply I was stuck in gsoc but I know I'll get
>>>> rejected so finally I am looking forward on the website as we dealt before.
>>>>
>>>> Can we have a zoom call? So we can get an idea of what exactly we are
>>>> gonna place on the website as from the previous responses I am only getting
>>>> that some of the things should be changed or replaced but with whom I can't
>>>> get it.
>>>>
>>>> Regards,
>>>>
>>>> Inzemamul Haq
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi Bruce - Good to know about those gaps in deployment and tools, but
>>>> are those the only gaps in the documentation?
>>>>
>>>>
>>>>
>>>> So, question to you: is it already sufficiently clear on these topics:
>>>>
>>>> * explaining what the software does
>>>>
>>>> * explaining the architecture
>>>>
>>>> * explaining relationship between different components
>>>>
>>>> * what features are in each release
>>>>
>>>> * how to set up development environment
>>>>
>>>> * how to access APIs
>>>>
>>>> * how to find additional resources
>>>>
>>>>
>>>>
>>>> I did ask for 3-5 priority things, so please do try to identify where
>>>> we start, even from your very long list or maybe adding to it, can we get
>>>> your opinion on a few key things?
>>>>
>>>>
>>>>
>>>> What would you say is a priority?
>>>>
>>>>
>>>>
>>>> As a project, I think we need to simply and only offer one or two
>>>> deployment options in our documentation, that way we can focus on getting
>>>> those accurate and keeping them up to date. Others are of course free to
>>>> offer their own improvements and alternatives.
>>>>
>>>>
>>>>
>>>> All - comments welcome.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> James
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> I hope this email finds you well. I wanted to share some observations
>>>> after going through the documentation for Fineract again.
>>>>
>>>> While the documentation provides an overview of deployment options here
>>>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>>>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>>>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>>>> guidance for users. There is also no deployment content on Kubernetes, AWS
>>>> and Google Cloud. Let's address this.
>>>>
>>>> Additionally, the Fineract Development section here
>>>> https://fineract.apache.org/docs/current/#_fineract_development_environment appears
>>>> to be incomplete and in need of further content to cover important topics
>>>> related to Fineract development. This section also includes topics marked
>>>> as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
>>>> Docker Desktop, IDE selection and configuration (including IntelliJ,
>>>> Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
>>>> Microk8s, K3d, Helm Charts, and installation and usage of various
>>>> development tools like Brew for MacOS and Linux. I propose that the
>>>> community contibutes content for the following topics:
>>>>
>>>> - Docker: how to install, run, and use Docker containers for
>>>> Fineract
>>>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>>>> containers for Fineract
>>>> - Podman: how to use Podman as an alternative to Docker for running
>>>> containers
>>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>>>> Kubernetes clusters on one's local machine
>>>> - IDE: how to choose and configure an IDE for Fineract development
>>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>>> Fineract
>>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>>> clusters
>>>> - Minikube: how to use Minikube to run a local Kubernetes cluster
>>>> for Fineract
>>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>>> cluster for Fineract
>>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>>> Fineract
>>>> - Helm Charts: how to use Helm Charts to package and deploy
>>>> Fineract applications on Kubernetes
>>>> - Tools: how to install and use various tools that can help one
>>>> with Fineract development
>>>> - Brew: how to install and use Brew for MacOS and Linux
>>>>
>>>> By actively addressing these gaps in the documentation, we can provide
>>>> valuable support to the Fineract community and further showcase the
>>>> flexibility and compatibility of Fineract with different technologies and
>>>> platforms.
>>>>
>>>> I look forward to collaborating with the community to contribute
>>>> content for these important topics and improve the overall documentation
>>>> for Fineract.
>>>>
>>>> Best Regards
>>>>
>>>> Bruce
>>>>
>>>>
>>>>
>>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>> Meta or Bruce - any updates?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>>
>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>> the previous points you and others mentioned..
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>> I've started to change some of the structure of the wiki. I'm just
>>>> trying to clean it up: Does anyone have an objection?
>>>>
>>>> * Noting where content is historical and deprecating it
>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>
>>>> This is incremental.
>>>>
>>>> Inzemam - can you provide a new design to review taking on the feedback?
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>> >
>>>> > Okay I'll be looking into it..
>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>>>> fields. Surely working effectively with both the orgs by making good
>>>> designs with premium feel.
>>>> > Regards,
>>>> > Inzemam
>>>> >
>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> Please make a set of suggestions or revise your designs based on
>>>> input.
>>>> >>
>>>> >> Feel free to dive into this .
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>> >>>
>>>> >>> Hello James,
>>>> >>> When we are going to start the work or are we leaving it for future?
>>>> >>>
>>>> >>> Regards,
>>>> >>> Inzemam
>>>> >>>
>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>> wrote:
>>>> >>>>
>>>> >>>> Hi James,
>>>> >>>> You are correct that we need to discuss more on the flows of
>>>> events and placements. And I am also agree with the point that we can
>>>> create a slack channel for this.
>>>> >>>> Also the code will be in simple html, css and js format so anyone
>>>> can create/change the things easily. The design is looking fancy and
>>>> complicated but the code is as smooth as butter. So need to worry about
>>>> maintainance.
>>>> >>>> Regards,
>>>> >>>> Inzemamul Haq
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>
>>>> >>>>> Hi - Thank you for this.
>>>> >>>>>
>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>> Javier's comments, which makes clear that we need to do a better job of
>>>> "Explaining" and "Positioning".
>>>> >>>>>
>>>> >>>>> ASIDE: Javier - I invite you to write more such text and provide
>>>> a top level set of bullet points that can be perhaps worked into the
>>>> content.
>>>> >>>>>
>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>> Nice.
>>>> >>>>>
>>>> >>>>> We need more revamping of the content before we can properly do
>>>> this design, so let's try to attack that problem.
>>>> >>>>>
>>>> >>>>> Here is a requirement that may not be clear to you:
>>>> >>>>> * Site should be very simple, easy to change by anyone opening up
>>>> a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>> hopefully with names that make sense
>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>> some text areas, adding content in specific sections.
>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>> three years, and avoid content that can get stale.
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> Message and Content issues:
>>>> >>>>>
>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>> the page today. Also, there is a common set of links and structure that you
>>>> can find in other Apache projects. It is not a requirement to follow other
>>>> Apache projects, but it would be useful to review them for commonalities:
>>>> >>>>> --> https://hadoop.apache.org
>>>> >>>>> --> https://airflow.apache.org
>>>> >>>>> --> https://kafka.apache.org
>>>> >>>>>
>>>> >>>>> * Note Community is there in each project. Check out the content
>>>> that each project has.
>>>> >>>>>
>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>> >>>>> and this should then flow into the requirements for the other
>>>> sections on the front page and then onto the wiki structure that we need
>>>> >>>>>
>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>> "Additional community technologies"
>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>> positioning is controversial for some, but until we get a release out and
>>>> lots of active development and deployments, that project remains very much
>>>> a side project of the community. It may become a very important thing, but
>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>> the vast majority of the dev is going on, and the vast majority of the
>>>> users are there.
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>> should be a summary of the system.
>>>> >>>>>
>>>> >>>>> This may require more chat and discussion on list or on slack and
>>>> then development of a structure of content before you can really get a
>>>> design.
>>>> >>>>>
>>>> >>>>> Thank you again.
>>>> >>>>>
>>>> >>>>> James Dailey
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>
>>>> >>>>>> Hello James,
>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>> >>>>>> Regards,
>>>> >>>>>> Inzemamul Haq
>>>> >>>>>>
>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>
>>>> >>>>>>> Hello Javier,
>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>> implement them as you suggested now what I need is some more brief about
>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>> change and add the things.
>>>> >>>>>>> As you mentioned in the last that it's a template but it's not.
>>>> It's designed by me on the figma and the assets I used are open source so
>>>> their will be no licencing issue. I always go for the development through
>>>> scratch so no need to worry about that.
>>>> >>>>>>> Regards,
>>>> >>>>>>> Inzemam
>>>> >>>>>>>
>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>> javier@fiter.io> wrote:
>>>> >>>>>>>>
>>>> >>>>>>>> Hy Meta,
>>>> >>>>>>>>
>>>> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic
>>>> in general, and it seems much more modern and suitable for the next stage
>>>> of our community.
>>>> >>>>>>>>
>>>> >>>>>>>> My two cents:
>>>> >>>>>>>>
>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful
>>>> in other areas of the industry, not just banks. We need to convey that
>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>> credit card as our visuals will put us in the last 20 years of the
>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>> be conceptual, not rigid on old paradigms.
>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>> paradigm of "Internet switches," allowing the users of financial
>>>> institutions to move their assets worldwide quickly and safely. All
>>>> purchases are now digital.
>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>> experiment while most of our community depends on and uses Fineract. This
>>>> must be clearly shown on the website and the real estate we dedicate to
>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>> CN is not backward compatible with Fineract.
>>>> >>>>>>>> The project we are proud of: I will only use the project part
>>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>>> new can of worms on which project gets selected and which criteria we
>>>> should use, on top of getting the right set of approvals from them to be
>>>> used as projects.
>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>> need the license of that template that allows us to use it without
>>>> limitations, and the template license is aligned with Apache 2.0.
>>>> >>>>>>>>
>>>> >>>>>>>> Javier
>>>> >>>>>>>>
>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>
>>>> >>>>>>>>> Hi James,
>>>> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
>>>> FINERACT redesigned website. Please review and let me know if you have any
>>>> questions or changes needed.
>>>> >>>>>>>>>
>>>> >>>>>>>>>
>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>> >>>>>>>>>
>>>> >>>>>>>>> Regards,
>>>> >>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>
>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>> +1
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> Hi
>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>> what exact is there on the website. I'll create a static mockup for the
>>>> website.
>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>> anyone new or experienced first comes to the website got confused of what's
>>>> happening and how things are going we can work upon it.
>>>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger
>>>> on that website? I have ability to work on static websites where the data
>>>> comes from dynamic CMS.
>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>> >>>>>>>>>>>>> Regards,
>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>> page website for the project, so not an app. The content needs to be
>>>> largely static or to pick up content we regularly post on blog. The current
>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>> is a design lens, in my view. But, a good UIX process does start with
>>>> who’s the audience and what’s their need when they land on the page.
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>> Hi,
>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
>>>> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
>>>> come up with a design also will share here in the thread and we can get
>>>> comments in the meeting.
>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>> overall UI/UX
>>>> >>>>>>>>>>>>>>> Regards,
>>>> >>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>> have four people who said they'd like to be involved.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>> mid February.
>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>> document:
>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>>> detail.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>>>> there a gap in content (Bruce, Tekle? - start a thread about this)
>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
>>>> you think belong being "brought over". compile a list of those pages. If
>>>> none, great.
>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>>> landing page (Meta Cyrus?)
>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>> landing pages that you like
>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>> confluence with links (james or ?)
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>>> thread.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> thanks
>>>> >>>>>>>>>>>>>>>> James
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>> d@gwocu.com> wrote:
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>> and develop a good user reliable website.
>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>> >>>>>>>>>>>>>>>>> Regards,
>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> All -
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>> landing page at https://fineract.apache.org that could be better at
>>>> communicating the project and community. Who wants to work on this with me?
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>> >>>>>>>>>>>>>>>>>> ---
>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think
>>>> we should have a top level split on the main page as well, or perhaps a
>>>> separate landing page for FineractCN.
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> ---
>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>> how to show two levels):
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> TBD
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to
>>>> be more prominent)
>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
>>>> top)
>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>> >>>>>>>>>>>>>>>>>> Standards
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>>>> documentation.
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>> etc) ... all go to blog
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> --
>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> --
>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>> >>
>>>> >> --
>>>> >> Sent from Gmail Mobile
>>>>
>>>> --
>>>>
>>>> Sent from Gmail Mobile
>>>>
>>>>
>>> El contenido de este mensaje y sus archivos electrónicos adjuntos
>>> constituyen información confidencial, y puede además contener secretos
>>> comerciales o industriales que se encuentran protegidos bajo las leyes de
>>> propiedad intelectual. Su uso, divulgación, revelación y/o circulación no
>>> autorizados se encuentran estrictamente prohibidos, por lo que si usted no
>>> es el destinatario del mismo o lo recibió por error, notifique
>>> inmediatamente al remitente por correo electrónico y elimine el mensaje así
>>> como toda información adjunta de su sistema. En cumplimiento de lo
>>> establecido por las leyes de protección de datos personales, Nubloq S.A.S.
>>> hace de su conocimiento que se encuentra a su disposición la política de
>>> tratamiento de datos personales en la página de internet
>>> https://www.nubloq.co/legal/ a efecto de que pueda ejercer su derecho
>>> al hábeas data. Todos los datos personales entregados vía correo
>>> electrónico serán utilizados de acuerdo con las finalidades allí previstas.
>>> Puede también consultar nuestros términos y condiciones en
>>> https://www.nubloq.co/legal/.
>>>
>>> The contents of this message and its attachments are confidential
>>> information and can hold trade secrets subject to intellectual property
>>> regulations. Its unauthorized use, divulgation, reveal and/or circulation
>>> are therefore strictly prohibited. In the event that you are not the
>>> intended recipient of this email, please immediately notify the sender
>>> through email and delete the message and any attachments from your system. Pursuant
>>> to the regulations on data privacy, Nubloq S.A.S informs that the privacy
>>> policy is available for consultation at: https://www.nubloq.co/legal/.
>>> All personal data will be treated in accordance with the purposes provided
>>> therein. You can also review our terms and conditions at
>>> https://www.nubloq.co/legal/.
>>>
>>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Hi all - We held our conversation today on Zoom about the design of the
Landing page and our overall strategy of organizing content on our web
presence.
Currently, we have the landing page: http://fineract.apache.org (within
links to various places on the wiki and github)
and we have the project site
https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home (with a
complex navigation and content structure)
and we have the new Platform Documentation at
https://fineract.apache.org/docs/current/ (from github)
Each of these serves a unique value:
* landing page is where technical and business people come to learn more,
where interested devs can easily find their way to a release or to
documentation or to dev tasks
* wiki is where we organize our project and community and thus everything
that is "in process" like links to Jira tickets
* Platform Documentation for things that are developed (completed, in the
Platform)
next up:
Inzemam will provide a new version of the landing page and start a fork
of the current page so that we can see his approach to keeping the
html/css/javascript easy to maintain.
and John with help from Abhinav will work on assessing which pieces of the
wiki can be trimmed (if it exists on the Platform documentation or can move
over there)
Please see the meeting notes from the ZOOM call here
https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
Thank you to those who joined today but also, if you didn't join, you are
welcome to join in the work. This is an important way to make the project
more maintainable and approachable.
Thanks,
James
On Thu, May 11, 2023 at 11:38 AM Dejan Juric <de...@j13kventures.com> wrote:
> Hi,
> please also add me.
>
> Thx,
> Dejan
>
> On Thu, May 11, 2023 at 12:55 PM Federico Benitez <fe...@nubloq.co>
> wrote:
>
>> Pls add me
>>
>> Sent from my iPhone
>>
>> On 10/05/2023, at 14:33, comsky juste <co...@gmail.com> wrote:
>>
>>
>> Please add me.
>>
>> On Wed, May 10, 2023, 3:58 AM Abhinav Sinha <ab...@gmail.com>
>> wrote:
>>
>>> Could you pls add me to the call as well
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Abhinav
>>>
>>>
>>>
>>> *From: *James Dailey <ja...@gmail.com>
>>> *Date: *Tuesday, May 9, 2023 at 9:53 PM
>>> *To: *dev@fineract.apache.org <de...@fineract.apache.org>
>>> *Subject: *Re: Website and Wiki for Fineract updates
>>>
>>> We will update this wiki page during and after the meeting
>>>
>>>
>>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>>
>>>
>>>
>>> (John - added)
>>>
>>> (Ernesto -added)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
>>>
>>> Please add me to this call.
>>>
>>>
>>>
>>> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
>>> <eo...@yahoo.com.invalid> wrote:
>>>
>>> Please add me
>>>
>>>
>>> Sent from Yahoo Mail for iPhone
>>> <https://overview.mail.yahoo.com/?.src=iOS>
>>>
>>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <
>>> inzemamhaq05@gmail.com> wrote:
>>>
>>> Yep I'll be there in meet call.
>>>
>>>
>>>
>>> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>> W can organize a zoom call. Then report back to the list here.
>>>
>>>
>>>
>>> I’ll suggest May 11th , 9am Pacific (PDT)
>>>
>>> I’ll send zoom link to anyone expressing interest.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
>>> wrote:
>>>
>>> Hello James,
>>>
>>> Sorry for the late reply I was stuck in gsoc but I know I'll get
>>> rejected so finally I am looking forward on the website as we dealt before.
>>>
>>> Can we have a zoom call? So we can get an idea of what exactly we are
>>> gonna place on the website as from the previous responses I am only getting
>>> that some of the things should be changed or replaced but with whom I can't
>>> get it.
>>>
>>> Regards,
>>>
>>> Inzemamul Haq
>>>
>>>
>>>
>>>
>>>
>>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>> Hi Bruce - Good to know about those gaps in deployment and tools, but
>>> are those the only gaps in the documentation?
>>>
>>>
>>>
>>> So, question to you: is it already sufficiently clear on these topics:
>>>
>>> * explaining what the software does
>>>
>>> * explaining the architecture
>>>
>>> * explaining relationship between different components
>>>
>>> * what features are in each release
>>>
>>> * how to set up development environment
>>>
>>> * how to access APIs
>>>
>>> * how to find additional resources
>>>
>>>
>>>
>>> I did ask for 3-5 priority things, so please do try to identify where we
>>> start, even from your very long list or maybe adding to it, can we get your
>>> opinion on a few key things?
>>>
>>>
>>>
>>> What would you say is a priority?
>>>
>>>
>>>
>>> As a project, I think we need to simply and only offer one or two
>>> deployment options in our documentation, that way we can focus on getting
>>> those accurate and keeping them up to date. Others are of course free to
>>> offer their own improvements and alternatives.
>>>
>>>
>>>
>>> All - comments welcome.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> James
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>>
>>>
>>> I hope this email finds you well. I wanted to share some observations
>>> after going through the documentation for Fineract again.
>>>
>>> While the documentation provides an overview of deployment options here
>>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>>> guidance for users. There is also no deployment content on Kubernetes, AWS
>>> and Google Cloud. Let's address this.
>>>
>>> Additionally, the Fineract Development section here
>>> https://fineract.apache.org/docs/current/#_fineract_development_environment appears
>>> to be incomplete and in need of further content to cover important topics
>>> related to Fineract development. This section also includes topics marked
>>> as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
>>> Docker Desktop, IDE selection and configuration (including IntelliJ,
>>> Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
>>> Microk8s, K3d, Helm Charts, and installation and usage of various
>>> development tools like Brew for MacOS and Linux. I propose that the
>>> community contibutes content for the following topics:
>>>
>>> - Docker: how to install, run, and use Docker containers for
>>> Fineract
>>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>>> containers for Fineract
>>> - Podman: how to use Podman as an alternative to Docker for running
>>> containers
>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>>> Kubernetes clusters on one's local machine
>>> - IDE: how to choose and configure an IDE for Fineract development
>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>> Fineract
>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>> clusters
>>> - Minikube: how to use Minikube to run a local Kubernetes cluster
>>> for Fineract
>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>> cluster for Fineract
>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>> Fineract
>>> - Helm Charts: how to use Helm Charts to package and deploy Fineract
>>> applications on Kubernetes
>>> - Tools: how to install and use various tools that can help one with
>>> Fineract development
>>> - Brew: how to install and use Brew for MacOS and Linux
>>>
>>> By actively addressing these gaps in the documentation, we can provide
>>> valuable support to the Fineract community and further showcase the
>>> flexibility and compatibility of Fineract with different technologies and
>>> platforms.
>>>
>>> I look forward to collaborating with the community to contribute content
>>> for these important topics and improve the overall documentation for
>>> Fineract.
>>>
>>> Best Regards
>>>
>>> Bruce
>>>
>>>
>>>
>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>> Meta or Bruce - any updates?
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>> Yep I'll be sharing the new design in which I hage taken care of all the
>>> previous points you and others mentioned..
>>>
>>>
>>>
>>>
>>>
>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>> I've started to change some of the structure of the wiki. I'm just
>>> trying to clean it up: Does anyone have an objection?
>>>
>>> * Noting where content is historical and deprecating it
>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>
>>> This is incremental.
>>>
>>> Inzemam - can you provide a new design to review taking on the feedback?
>>>
>>>
>>>
>>>
>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>> >
>>> > Okay I'll be looking into it..
>>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>>> fields. Surely working effectively with both the orgs by making good
>>> designs with premium feel.
>>> > Regards,
>>> > Inzemam
>>> >
>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>> >>
>>> >> Please make a set of suggestions or revise your designs based on
>>> input.
>>> >>
>>> >> Feel free to dive into this .
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>> >>>
>>> >>> Hello James,
>>> >>> When we are going to start the work or are we leaving it for future?
>>> >>>
>>> >>> Regards,
>>> >>> Inzemam
>>> >>>
>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>> wrote:
>>> >>>>
>>> >>>> Hi James,
>>> >>>> You are correct that we need to discuss more on the flows of events
>>> and placements. And I am also agree with the point that we can create a
>>> slack channel for this.
>>> >>>> Also the code will be in simple html, css and js format so anyone
>>> can create/change the things easily. The design is looking fancy and
>>> complicated but the code is as smooth as butter. So need to worry about
>>> maintainance.
>>> >>>> Regards,
>>> >>>> Inzemamul Haq
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>> >>>>>
>>> >>>>> Hi - Thank you for this.
>>> >>>>>
>>> >>>>> It's a very good conversation starter. I agreed with most of
>>> Javier's comments, which makes clear that we need to do a better job of
>>> "Explaining" and "Positioning".
>>> >>>>>
>>> >>>>> ASIDE: Javier - I invite you to write more such text and provide
>>> a top level set of bullet points that can be perhaps worked into the
>>> content.
>>> >>>>>
>>> >>>>> I think that the design colors are ok, the blue is appropriate for
>>> a financial system, meaning steady and trustworthy on the color wheel. Nice.
>>> >>>>>
>>> >>>>> We need more revamping of the content before we can properly do
>>> this design, so let's try to attack that problem.
>>> >>>>>
>>> >>>>> Here is a requirement that may not be clear to you:
>>> >>>>> * Site should be very simple, easy to change by anyone opening up
>>> a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>> hopefully with names that make sense
>>> >>>>> * Assume that you are gone and someone else has to modify just
>>> some text areas, adding content in specific sections.
>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>> three years, and avoid content that can get stale.
>>> >>>>>
>>> >>>>>
>>> >>>>> Message and Content issues:
>>> >>>>>
>>> >>>>> * Fineract is part of Apache and this is not always clear from the
>>> page today. Also, there is a common set of links and structure that you can
>>> find in other Apache projects. It is not a requirement to follow other
>>> Apache projects, but it would be useful to review them for commonalities:
>>> >>>>> --> https://hadoop.apache.org
>>> >>>>> --> https://airflow.apache.org
>>> >>>>> --> https://kafka.apache.org
>>> >>>>>
>>> >>>>> * Note Community is there in each project. Check out the content
>>> that each project has.
>>> >>>>>
>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>> >>>>> and this should then flow into the requirements for the other
>>> sections on the front page and then onto the wiki structure that we need
>>> >>>>>
>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>> billing as the Fineract1.x releases it is still trying to get to a first
>>> release and fineract1.x is releasing on a regular basis with lots of
>>> activity. So, move Fineract-CN to a bottom section that's something about
>>> "Additional community technologies"
>>> >>>>> I was and am a big fan of this framework, and I know this
>>> positioning is controversial for some, but until we get a release out and
>>> lots of active development and deployments, that project remains very much
>>> a side project of the community. It may become a very important thing, but
>>> for now we should reflect the reality which is that Fineract1.x is where
>>> the vast majority of the dev is going on, and the vast majority of the
>>> users are there.
>>> >>>>>
>>> >>>>>
>>> >>>>> * We need to emphasize the key features of Fineract - there should
>>> be a summary of the system.
>>> >>>>>
>>> >>>>> This may require more chat and discussion on list or on slack and
>>> then development of a structure of content before you can really get a
>>> design.
>>> >>>>>
>>> >>>>> Thank you again.
>>> >>>>>
>>> >>>>> James Dailey
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>
>>> >>>>>> Hello James,
>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>> >>>>>> Regards,
>>> >>>>>> Inzemamul Haq
>>> >>>>>>
>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
>>> wrote:
>>> >>>>>>>
>>> >>>>>>> Hello Javier,
>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>> implement them as you suggested now what I need is some more brief about
>>> the topics. This was the just an idea of how it'll look like surely we can
>>> change and add the things.
>>> >>>>>>> As you mentioned in the last that it's a template but it's not.
>>> It's designed by me on the figma and the assets I used are open source so
>>> their will be no licencing issue. I always go for the development through
>>> scratch so no need to worry about that.
>>> >>>>>>> Regards,
>>> >>>>>>> Inzemam
>>> >>>>>>>
>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>> javier@fiter.io> wrote:
>>> >>>>>>>>
>>> >>>>>>>> Hy Meta,
>>> >>>>>>>>
>>> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic
>>> in general, and it seems much more modern and suitable for the next stage
>>> of our community.
>>> >>>>>>>>
>>> >>>>>>>> My two cents:
>>> >>>>>>>>
>>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful
>>> in other areas of the industry, not just banks. We need to convey that
>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>> credit card as our visuals will put us in the last 20 years of the
>>> industry, and we are in the next 20 years. The images we need to use has to
>>> be conceptual, not rigid on old paradigms.
>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>> paradigm of "Internet switches," allowing the users of financial
>>> institutions to move their assets worldwide quickly and safely. All
>>> purchases are now digital.
>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>>> same exposure on our website as Fineract. Fineract CN it's still an
>>> experiment while most of our community depends on and uses Fineract. This
>>> must be clearly shown on the website and the real estate we dedicate to
>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>> CN is not backward compatible with Fineract.
>>> >>>>>>>> The project we are proud of: I will only use the project part
>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>> new can of worms on which project gets selected and which criteria we
>>> should use, on top of getting the right set of approvals from them to be
>>> used as projects.
>>> >>>>>>>> Last but not least, you used a template for the design. We need
>>> the license of that template that allows us to use it without limitations,
>>> and the template license is aligned with Apache 2.0.
>>> >>>>>>>>
>>> >>>>>>>> Javier
>>> >>>>>>>>
>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>
>>> >>>>>>>>> Hi James,
>>> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
>>> FINERACT redesigned website. Please review and let me know if you have any
>>> questions or changes needed.
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>> >>>>>>>>>
>>> >>>>>>>>> Regards,
>>> >>>>>>>>> Inzemamul Haq
>>> >>>>>>>>>
>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>
>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> Okay lemme begin the work.
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> +1
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Hi
>>> >>>>>>>>>>>>> I've been through the website and got it closely that what
>>> exact is there on the website. I'll create a static mockup for the website.
>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone
>>> new or experienced first comes to the website got confused of what's
>>> happening and how things are going we can work upon it.
>>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger
>>> on that website? I have ability to work on static websites where the data
>>> comes from dynamic CMS.
>>> >>>>>>>>>>>>> So I can work on tha too....
>>> >>>>>>>>>>>>> Regards,
>>> >>>>>>>>>>>>> Inzemamul Haq
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>> page website for the project, so not an app. The content needs to be
>>> largely static or to pick up content we regularly post on blog. The current
>>> site is basic html. Just making sure we’re talking about the same thing.
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is
>>> a design lens, in my view. But, a good UIX process does start with who’s
>>> the audience and what’s their need when they land on the page.
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Hi,
>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
>>> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
>>> come up with a design also will share here in the thread and we can get
>>> comments in the meeting.
>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>> overall UI/UX
>>> >>>>>>>>>>>>>>> Regards,
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>> have four people who said they'd like to be involved.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and
>>> then we can share back here on list and also hold a meeting on zoom in mid
>>> February.
>>> >>>>>>>>>>>>>>>> Feb 16th?
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>> document:
>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>> detail.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>>> there a gap in content (Bruce, Tekle? - start a thread about this)
>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
>>> you think belong being "brought over". compile a list of those pages. If
>>> none, great.
>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>> landing page (Meta Cyrus?)
>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>> landing pages that you like
>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>> functional description aimed at a Business Leader (Dick Dickson?)
>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>> confluence with links (james or ?)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>> thread.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> thanks
>>> >>>>>>>>>>>>>>>> James
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>> d@gwocu.com> wrote:
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> Hi James,
>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
>>> develop a good user reliable website.
>>> >>>>>>>>>>>>>>>>> Where I can start??
>>> >>>>>>>>>>>>>>>>> Regards,
>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> All -
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>> been 3+ years since we did a clean sweep of it. We also have a front
>>> landing page at https://fineract.apache.org that could be better at
>>> communicating the project and community. Who wants to work on this with me?
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>> >>>>>>>>>>>>>>>>>> ---
>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think
>>> we should have a top level split on the main page as well, or perhaps a
>>> separate landing page for FineractCN.
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> ---
>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how
>>> to show two levels):
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> FAQ
>>> >>>>>>>>>>>>>>>>>> About Fineract
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> TBD
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Project Management
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to
>>> be more prominent)
>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
>>> top)
>>> >>>>>>>>>>>>>>>>>> Surveys
>>> >>>>>>>>>>>>>>>>>> Release processes
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Committer guides
>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>> >>>>>>>>>>>>>>>>>> Standards
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Documentation
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>>> documentation.
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc)
>>> ... all go to blog
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>> >>>>>>>>>>>>>>>>>> FINERACT
>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> How-to articles
>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> --
>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>> >>>>>>>>>>
>>> >>>>>>>>>> --
>>> >>>>>>>>>> Sent from Gmail Mobile
>>> >>
>>> >> --
>>> >> Sent from Gmail Mobile
>>>
>>> --
>>>
>>> Sent from Gmail Mobile
>>>
>>>
>> El contenido de este mensaje y sus archivos electrónicos adjuntos
>> constituyen información confidencial, y puede además contener secretos
>> comerciales o industriales que se encuentran protegidos bajo las leyes de
>> propiedad intelectual. Su uso, divulgación, revelación y/o circulación no
>> autorizados se encuentran estrictamente prohibidos, por lo que si usted no
>> es el destinatario del mismo o lo recibió por error, notifique
>> inmediatamente al remitente por correo electrónico y elimine el mensaje así
>> como toda información adjunta de su sistema. En cumplimiento de lo
>> establecido por las leyes de protección de datos personales, Nubloq S.A.S.
>> hace de su conocimiento que se encuentra a su disposición la política de
>> tratamiento de datos personales en la página de internet
>> https://www.nubloq.co/legal/ a efecto de que pueda ejercer su derecho al
>> hábeas data. Todos los datos personales entregados vía correo electrónico
>> serán utilizados de acuerdo con las finalidades allí previstas. Puede
>> también consultar nuestros términos y condiciones en
>> https://www.nubloq.co/legal/.
>>
>> The contents of this message and its attachments are confidential
>> information and can hold trade secrets subject to intellectual property
>> regulations. Its unauthorized use, divulgation, reveal and/or circulation
>> are therefore strictly prohibited. In the event that you are not the
>> intended recipient of this email, please immediately notify the sender
>> through email and delete the message and any attachments from your system. Pursuant
>> to the regulations on data privacy, Nubloq S.A.S informs that the privacy
>> policy is available for consultation at: https://www.nubloq.co/legal/.
>> All personal data will be treated in accordance with the purposes provided
>> therein. You can also review our terms and conditions at
>> https://www.nubloq.co/legal/.
>>
>
Re: Website and Wiki for Fineract updates
Posted by Dejan Juric <de...@j13kventures.com>.
Hi,
please also add me.
Thx,
Dejan
On Thu, May 11, 2023 at 12:55 PM Federico Benitez <fe...@nubloq.co>
wrote:
> Pls add me
>
> Sent from my iPhone
>
> On 10/05/2023, at 14:33, comsky juste <co...@gmail.com> wrote:
>
>
> Please add me.
>
> On Wed, May 10, 2023, 3:58 AM Abhinav Sinha <ab...@gmail.com>
> wrote:
>
>> Could you pls add me to the call as well
>>
>>
>>
>> Thanks,
>>
>> Abhinav
>>
>>
>>
>> *From: *James Dailey <ja...@gmail.com>
>> *Date: *Tuesday, May 9, 2023 at 9:53 PM
>> *To: *dev@fineract.apache.org <de...@fineract.apache.org>
>> *Subject: *Re: Website and Wiki for Fineract updates
>>
>> We will update this wiki page during and after the meeting
>>
>>
>> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>>
>>
>>
>> (John - added)
>>
>> (Ernesto -added)
>>
>>
>>
>>
>>
>>
>>
>> On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
>>
>> Please add me to this call.
>>
>>
>>
>> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
>> <eo...@yahoo.com.invalid> wrote:
>>
>> Please add me
>>
>>
>> Sent from Yahoo Mail for iPhone
>> <https://overview.mail.yahoo.com/?.src=iOS>
>>
>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <in...@gmail.com>
>> wrote:
>>
>> Yep I'll be there in meet call.
>>
>>
>>
>> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>> W can organize a zoom call. Then report back to the list here.
>>
>>
>>
>> I’ll suggest May 11th , 9am Pacific (PDT)
>>
>> I’ll send zoom link to anyone expressing interest.
>>
>>
>>
>>
>>
>>
>>
>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
>> wrote:
>>
>> Hello James,
>>
>> Sorry for the late reply I was stuck in gsoc but I know I'll get rejected
>> so finally I am looking forward on the website as we dealt before.
>>
>> Can we have a zoom call? So we can get an idea of what exactly we are
>> gonna place on the website as from the previous responses I am only getting
>> that some of the things should be changed or replaced but with whom I can't
>> get it.
>>
>> Regards,
>>
>> Inzemamul Haq
>>
>>
>>
>>
>>
>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>> Hi Bruce - Good to know about those gaps in deployment and tools, but are
>> those the only gaps in the documentation?
>>
>>
>>
>> So, question to you: is it already sufficiently clear on these topics:
>>
>> * explaining what the software does
>>
>> * explaining the architecture
>>
>> * explaining relationship between different components
>>
>> * what features are in each release
>>
>> * how to set up development environment
>>
>> * how to access APIs
>>
>> * how to find additional resources
>>
>>
>>
>> I did ask for 3-5 priority things, so please do try to identify where we
>> start, even from your very long list or maybe adding to it, can we get your
>> opinion on a few key things?
>>
>>
>>
>> What would you say is a priority?
>>
>>
>>
>> As a project, I think we need to simply and only offer one or two
>> deployment options in our documentation, that way we can focus on getting
>> those accurate and keeping them up to date. Others are of course free to
>> offer their own improvements and alternatives.
>>
>>
>>
>> All - comments welcome.
>>
>>
>>
>> Thanks,
>>
>> James
>>
>>
>>
>>
>>
>>
>>
>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>
>> Hi,
>>
>>
>>
>> I hope this email finds you well. I wanted to share some observations
>> after going through the documentation for Fineract again.
>>
>> While the documentation provides an overview of deployment options here
>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>> guidance for users. There is also no deployment content on Kubernetes, AWS
>> and Google Cloud. Let's address this.
>>
>> Additionally, the Fineract Development section here
>> https://fineract.apache.org/docs/current/#_fineract_development_environment appears
>> to be incomplete and in need of further content to cover important topics
>> related to Fineract development. This section also includes topics marked
>> as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
>> Docker Desktop, IDE selection and configuration (including IntelliJ,
>> Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
>> Microk8s, K3d, Helm Charts, and installation and usage of various
>> development tools like Brew for MacOS and Linux. I propose that the
>> community contibutes content for the following topics:
>>
>> - Docker: how to install, run, and use Docker containers for Fineract
>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>> containers for Fineract
>> - Podman: how to use Podman as an alternative to Docker for running
>> containers
>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>> Kubernetes clusters on one's local machine
>> - IDE: how to choose and configure an IDE for Fineract development
>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>> - Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
>> - Minikube: how to use Minikube to run a local Kubernetes cluster for
>> Fineract
>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>> cluster for Fineract
>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>> Fineract
>> - Helm Charts: how to use Helm Charts to package and deploy Fineract
>> applications on Kubernetes
>> - Tools: how to install and use various tools that can help one with
>> Fineract development
>> - Brew: how to install and use Brew for MacOS and Linux
>>
>> By actively addressing these gaps in the documentation, we can provide
>> valuable support to the Fineract community and further showcase the
>> flexibility and compatibility of Fineract with different technologies and
>> platforms.
>>
>> I look forward to collaborating with the community to contribute content
>> for these important topics and improve the overall documentation for
>> Fineract.
>>
>> Best Regards
>>
>> Bruce
>>
>>
>>
>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>> Meta or Bruce - any updates?
>>
>>
>>
>>
>>
>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>> wrote:
>>
>> Yep I'll be sharing the new design in which I hage taken care of all the
>> previous points you and others mentioned..
>>
>>
>>
>>
>>
>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>> I've started to change some of the structure of the wiki. I'm just
>> trying to clean it up: Does anyone have an objection?
>>
>> * Noting where content is historical and deprecating it
>> * Moving the Quarterly PMC reports to slightly more prominence
>>
>> This is incremental.
>>
>> Inzemam - can you provide a new design to review taking on the feedback?
>>
>>
>>
>>
>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>> >
>> > Okay I'll be looking into it..
>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>> fields. Surely working effectively with both the orgs by making good
>> designs with premium feel.
>> > Regards,
>> > Inzemam
>> >
>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>> wrote:
>> >>
>> >> Please make a set of suggestions or revise your designs based on input.
>> >>
>> >> Feel free to dive into this .
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>> >>>
>> >>> Hello James,
>> >>> When we are going to start the work or are we leaving it for future?
>> >>>
>> >>> Regards,
>> >>> Inzemam
>> >>>
>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>> wrote:
>> >>>>
>> >>>> Hi James,
>> >>>> You are correct that we need to discuss more on the flows of events
>> and placements. And I am also agree with the point that we can create a
>> slack channel for this.
>> >>>> Also the code will be in simple html, css and js format so anyone
>> can create/change the things easily. The design is looking fancy and
>> complicated but the code is as smooth as butter. So need to worry about
>> maintainance.
>> >>>> Regards,
>> >>>> Inzemamul Haq
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
>> wrote:
>> >>>>>
>> >>>>> Hi - Thank you for this.
>> >>>>>
>> >>>>> It's a very good conversation starter. I agreed with most of
>> Javier's comments, which makes clear that we need to do a better job of
>> "Explaining" and "Positioning".
>> >>>>>
>> >>>>> ASIDE: Javier - I invite you to write more such text and provide a
>> top level set of bullet points that can be perhaps worked into the content.
>> >>>>>
>> >>>>> I think that the design colors are ok, the blue is appropriate for
>> a financial system, meaning steady and trustworthy on the color wheel. Nice.
>> >>>>>
>> >>>>> We need more revamping of the content before we can properly do
>> this design, so let's try to attack that problem.
>> >>>>>
>> >>>>> Here is a requirement that may not be clear to you:
>> >>>>> * Site should be very simple, easy to change by anyone opening up a
>> Text Editor and modifying the HTML directly. e.g. use CSS styles and
>> hopefully with names that make sense
>> >>>>> * Assume that you are gone and someone else has to modify just some
>> text areas, adding content in specific sections.
>> >>>>> * Assume that no-one touches the website for over a year, maybe
>> three years, and avoid content that can get stale.
>> >>>>>
>> >>>>>
>> >>>>> Message and Content issues:
>> >>>>>
>> >>>>> * Fineract is part of Apache and this is not always clear from the
>> page today. Also, there is a common set of links and structure that you can
>> find in other Apache projects. It is not a requirement to follow other
>> Apache projects, but it would be useful to review them for commonalities:
>> >>>>> --> https://hadoop.apache.org
>> >>>>> --> https://airflow.apache.org
>> >>>>> --> https://kafka.apache.org
>> >>>>>
>> >>>>> * Note Community is there in each project. Check out the content
>> that each project has.
>> >>>>>
>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>> >>>>> and this should then flow into the requirements for the other
>> sections on the front page and then onto the wiki structure that we need
>> >>>>>
>> >>>>> * At this time Fineract-CN should probably not receive equal
>> billing as the Fineract1.x releases it is still trying to get to a first
>> release and fineract1.x is releasing on a regular basis with lots of
>> activity. So, move Fineract-CN to a bottom section that's something about
>> "Additional community technologies"
>> >>>>> I was and am a big fan of this framework, and I know this
>> positioning is controversial for some, but until we get a release out and
>> lots of active development and deployments, that project remains very much
>> a side project of the community. It may become a very important thing, but
>> for now we should reflect the reality which is that Fineract1.x is where
>> the vast majority of the dev is going on, and the vast majority of the
>> users are there.
>> >>>>>
>> >>>>>
>> >>>>> * We need to emphasize the key features of Fineract - there should
>> be a summary of the system.
>> >>>>>
>> >>>>> This may require more chat and discussion on list or on slack and
>> then development of a structure of content before you can really get a
>> design.
>> >>>>>
>> >>>>> Thank you again.
>> >>>>>
>> >>>>> James Dailey
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>> >>>>>>
>> >>>>>> Hello James,
>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>> >>>>>> Regards,
>> >>>>>> Inzemamul Haq
>> >>>>>>
>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
>> wrote:
>> >>>>>>>
>> >>>>>>> Hello Javier,
>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>> implement them as you suggested now what I need is some more brief about
>> the topics. This was the just an idea of how it'll look like surely we can
>> change and add the things.
>> >>>>>>> As you mentioned in the last that it's a template but it's not.
>> It's designed by me on the figma and the assets I used are open source so
>> their will be no licencing issue. I always go for the development through
>> scratch so no need to worry about that.
>> >>>>>>> Regards,
>> >>>>>>> Inzemam
>> >>>>>>>
>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>> javier@fiter.io> wrote:
>> >>>>>>>>
>> >>>>>>>> Hy Meta,
>> >>>>>>>>
>> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic
>> in general, and it seems much more modern and suitable for the next stage
>> of our community.
>> >>>>>>>>
>> >>>>>>>> My two cents:
>> >>>>>>>>
>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful in
>> other areas of the industry, not just banks. We need to convey that
>> Fineract is a platform for many use cases. Using a mobile phone and a
>> credit card as our visuals will put us in the last 20 years of the
>> industry, and we are in the next 20 years. The images we need to use has to
>> be conceptual, not rigid on old paradigms.
>> >>>>>>>> Fineract is a backend. Fineract will help the financial industry
>> transcend from the old paradigm of "save deposit boxes" to the new paradigm
>> of "Internet switches," allowing the users of financial institutions to
>> move their assets worldwide quickly and safely. All purchases are now
>> digital.
>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>> same exposure on our website as Fineract. Fineract CN it's still an
>> experiment while most of our community depends on and uses Fineract. This
>> must be clearly shown on the website and the real estate we dedicate to
>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>> CN is not backward compatible with Fineract.
>> >>>>>>>> The project we are proud of: I will only use the project part if
>> we get three Fortune 500 companies using Fineract. It will also open a new
>> can of worms on which project gets selected and which criteria we should
>> use, on top of getting the right set of approvals from them to be used as
>> projects.
>> >>>>>>>> Last but not least, you used a template for the design. We need
>> the license of that template that allows us to use it without limitations,
>> and the template license is aligned with Apache 2.0.
>> >>>>>>>>
>> >>>>>>>> Javier
>> >>>>>>>>
>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>
>> >>>>>>>>> Hi James,
>> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
>> FINERACT redesigned website. Please review and let me know if you have any
>> questions or changes needed.
>> >>>>>>>>>
>> >>>>>>>>>
>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>> >>>>>>>>>
>> >>>>>>>>> Regards,
>> >>>>>>>>> Inzemamul Haq
>> >>>>>>>>>
>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>> Okay lemme begin the work.
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> +1
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Hi
>> >>>>>>>>>>>>> I've been through the website and got it closely that what
>> exact is there on the website. I'll create a static mockup for the website.
>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone
>> new or experienced first comes to the website got confused of what's
>> happening and how things are going we can work upon it.
>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger on
>> that website? I have ability to work on static websites where the data
>> comes from dynamic CMS.
>> >>>>>>>>>>>>> So I can work on tha too....
>> >>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>> Inzemamul Haq
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Inzemamul Haq -
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single page
>> website for the project, so not an app. The content needs to be largely
>> static or to pick up content we regularly post on blog. The current site is
>> basic html. Just making sure we’re talking about the same thing.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Fineract.Apache.org
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is
>> a design lens, in my view. But, a good UIX process does start with who’s
>> the audience and what’s their need when they land on the page.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Hi,
>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
>> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
>> come up with a design also will share here in the thread and we can get
>> comments in the meeting.
>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>> overall UI/UX
>> >>>>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Inzemamul Haq
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>> have four people who said they'd like to be involved.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and
>> then we can share back here on list and also hold a meeting on zoom in mid
>> February.
>> >>>>>>>>>>>>>>>> Feb 16th?
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>> document:
>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>> detail.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Proposed Tasks:
>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>> there a gap in content (Bruce, Tekle? - start a thread about this)
>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
>> you think belong being "brought over". compile a list of those pages. If
>> none, great.
>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>> landing page (Meta Cyrus?)
>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing
>> pages that you like
>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>> functional description aimed at a Business Leader (Dick Dickson?)
>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>> confluence with links (james or ?)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>> thread.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> thanks
>> >>>>>>>>>>>>>>>> James
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>> d@gwocu.com> wrote:
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Hi James,
>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
>> develop a good user reliable website.
>> >>>>>>>>>>>>>>>>> Where I can start??
>> >>>>>>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> All -
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>> been 3+ years since we did a clean sweep of it. We also have a front
>> landing page at https://fineract.apache.org that could be better at
>> communicating the project and community. Who wants to work on this with me?
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>> >>>>>>>>>>>>>>>>>> ---
>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Add blog feed
>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>> >>>>>>>>>>>>>>>>>> Include FAQ
>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think
>> we should have a top level split on the main page as well, or perhaps a
>> separate landing page for FineractCN.
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> ---
>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how
>> to show two levels):
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> FAQ
>> >>>>>>>>>>>>>>>>>> About Fineract
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> About FineractCN
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> TBD
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Project Management
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to
>> be more prominent)
>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
>> top)
>> >>>>>>>>>>>>>>>>>> Surveys
>> >>>>>>>>>>>>>>>>>> Release processes
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> How do I get involved?
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Committer guides
>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>> >>>>>>>>>>>>>>>>>> Standards
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Documentation
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>> documentation.
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc)
>> ... all go to blog
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> The current high level structure:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>> >>>>>>>>>>>>>>>>>> FINERACT
>> >>>>>>>>>>>>>>>>>> FINERACT CN
>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> How-to articles
>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>> >>>>>>>>>>>>>>>>>> Meeting notes
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> --
>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>> >>>>>>>>>>
>> >>>>>>>>>> --
>> >>>>>>>>>> Sent from Gmail Mobile
>> >>
>> >> --
>> >> Sent from Gmail Mobile
>>
>> --
>>
>> Sent from Gmail Mobile
>>
>>
> El contenido de este mensaje y sus archivos electrónicos adjuntos
> constituyen información confidencial, y puede además contener secretos
> comerciales o industriales que se encuentran protegidos bajo las leyes de
> propiedad intelectual. Su uso, divulgación, revelación y/o circulación no
> autorizados se encuentran estrictamente prohibidos, por lo que si usted no
> es el destinatario del mismo o lo recibió por error, notifique
> inmediatamente al remitente por correo electrónico y elimine el mensaje así
> como toda información adjunta de su sistema. En cumplimiento de lo
> establecido por las leyes de protección de datos personales, Nubloq S.A.S.
> hace de su conocimiento que se encuentra a su disposición la política de
> tratamiento de datos personales en la página de internet
> https://www.nubloq.co/legal/ a efecto de que pueda ejercer su derecho al
> hábeas data. Todos los datos personales entregados vía correo electrónico
> serán utilizados de acuerdo con las finalidades allí previstas. Puede
> también consultar nuestros términos y condiciones en
> https://www.nubloq.co/legal/.
>
> The contents of this message and its attachments are confidential
> information and can hold trade secrets subject to intellectual property
> regulations. Its unauthorized use, divulgation, reveal and/or circulation
> are therefore strictly prohibited. In the event that you are not the
> intended recipient of this email, please immediately notify the sender
> through email and delete the message and any attachments from your system. Pursuant
> to the regulations on data privacy, Nubloq S.A.S informs that the privacy
> policy is available for consultation at: https://www.nubloq.co/legal/.
> All personal data will be treated in accordance with the purposes provided
> therein. You can also review our terms and conditions at
> https://www.nubloq.co/legal/.
>
Re: Website and Wiki for Fineract updates
Posted by Federico Benitez <fe...@nubloq.co>.
Pls add me
Sent from my iPhone
> On 10/05/2023, at 14:33, comsky juste <co...@gmail.com> wrote:
>
>
>
>
> Please add me.
>
>
>
>
> On Wed, May 10, 2023, 3:58 AM Abhinav Sinha
> <[abhinav7.sinha@gmail.com](mailto:abhinav7.sinha@gmail.com)> wrote:
>
>
>> Could you pls add me to the call as well __ __
>>
>> __ __
>>
>> Thanks, __ __
>>
>> Abhinav __ __
>>
>> __ __
>>
>> **From:** James Dailey
<[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)>
> **Date:** Tuesday, May 9, 2023 at 9:53 PM
> **To:**[dev@fineract.apache.org](mailto:dev@fineract.apache.org)
> <[dev@fineract.apache.org](mailto:dev@fineract.apache.org)>
> **Subject:** Re: Website and Wiki for Fineract updates __ __
>>
>> We will update this wiki page during and after the meeting __ __
>>
>>
<https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes>____
>>
>> __ __
>>
>> (John - added) __ __
>>
>> (Ernesto -added) __ __
>>
>> __ __
>>
>> __ __
>>
>> __ __
>>
>> On Tue, May 9, 2023 at 10:48 AM John Gathogo
<[john@fiter.io](mailto:john@fiter.io)> wrote: __ __
>>
>>> Please add me to this call. __ __
>>>
>>> __ __
>>>
>>> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
<eo...@yahoo.com.invalid> wrote: __ __
>>>
>>>> Please add me
>
>
> [Sent from Yahoo Mail for
> iPhone](https://overview.mail.yahoo.com/?.src=iOS) __ __
>>>>
>>>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq
<[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote: __ __
>>>>
>>>>> Yep I'll be there in meet call. __ __
>>>>>
>>>>> __ __
>>>>>
>>>>> On Sun, 30 Apr, 2023, 12:00 am James Dailey,
<[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote: __ __
>>>>>
>>>>>> W can organize a zoom call. Then report back to the list here. __ __
>>>>>>
>>>>>> __ __
>>>>>>
>>>>>> I’ll suggest May 11th , 9am Pacific (PDT) __ __
>>>>>>
>>>>>> I’ll send zoom link to anyone expressing interest. __ __
>>>>>>
>>>>>> __ __
>>>>>>
>>>>>> __ __
>>>>>>
>>>>>> __ __
>>>>>>
>>>>>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq
<[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote: __ __
>>>>>>
>>>>>>> Hello James, __ __
>>>>>>>
>>>>>>> Sorry for the late reply I was stuck in gsoc but I know I'll get
rejected so finally I am looking forward on the website as we dealt before. __
__
>>>>>>>
>>>>>>> Can we have a zoom call? So we can get an idea of what exactly we are
gonna place on the website as from the previous responses I am only getting
that some of the things should be changed or replaced but with whom I can't
get it. __ __
>>>>>>>
>>>>>>> Regards, __ __
>>>>>>>
>>>>>>> Inzemamul Haq __ __
>>>>>>>
>>>>>>> __ __
>>>>>>>
>>>>>>> __ __
>>>>>>>
>>>>>>> On Sun, 9 Apr, 2023, 12:16 am James Dailey,
<[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote: __ __
>>>>>>>
>>>>>>>> Hi Bruce - Good to know about those gaps in deployment and tools, but
are those the only gaps in the documentation? __ __
>>>>>>>>
>>>>>>>> __ __
>>>>>>>>
>>>>>>>> So, question to you: is it already sufficiently clear on these
topics: __ __
>>>>>>>>
>>>>>>>> * explaining what the software does __ __
>>>>>>>>
>>>>>>>> * explaining the architecture __ __
>>>>>>>>
>>>>>>>> * explaining relationship between different components __ __
>>>>>>>>
>>>>>>>> * what features are in each release __ __
>>>>>>>>
>>>>>>>> * how to set up development environment __ __
>>>>>>>>
>>>>>>>> * how to access APIs __ __
>>>>>>>>
>>>>>>>> * how to find additional resources __ __
>>>>>>>>
>>>>>>>> __ __
>>>>>>>>
>>>>>>>> I did ask for 3-5 priority things, so please do try to identify where
we start, even from your very long list or maybe adding to it, can we get your
opinion on a few key things? __ __
>>>>>>>>
>>>>>>>> __ __
>>>>>>>>
>>>>>>>> What would you say is a priority? __ __
>>>>>>>>
>>>>>>>> __ __
>>>>>>>>
>>>>>>>> As a project, I think we need to simply and only offer one or two
deployment options in our documentation, that way we can focus on getting
those accurate and keeping them up to date. Others are of course free to
offer their own improvements and alternatives. __ __
>>>>>>>>
>>>>>>>> __ __
>>>>>>>>
>>>>>>>> All - comments welcome. __ __
>>>>>>>>
>>>>>>>> __ __
>>>>>>>>
>>>>>>>> Thanks, __ __
>>>>>>>>
>>>>>>>> James __ __
>>>>>>>>
>>>>>>>> __ __
>>>>>>>>
>>>>>>>> __ __
>>>>>>>>
>>>>>>>> __ __
>>>>>>>>
>>>>>>>> On Sat, Apr 8, 2023 at 10:33 AM Bruce
<[brucetushabe@gmail.com](mailto:brucetushabe@gmail.com)> wrote: __ __
>>>>>>>>
>>>>>>>>> Hi, __ __
>>>>>>>>>
>>>>>>>>> __ __
>>>>>>>>>
>>>>>>>>> I hope this email finds you well. I wanted to share some
observations after going through the documentation for Fineract again. __ __
>>>>>>>>>
>>>>>>>>> While the documentation provides an overview of deployment options
here <https://fineract.apache.org/docs/current/#_deployment> , I noticed that
several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
Weblogic, and Payara, are marked as TBD, indicating a lack of content and
guidance for users. There is also no deployment content on Kubernetes, AWS and
Google Cloud. Let's address this. __ __
>>>>>>>>>
>>>>>>>>> Additionally, the Fineract Development section here
<https://fineract.apache.org/docs/current/#_fineract_development_environment>
appears to be incomplete and in need of further content to cover important
topics related to Fineract development. This section also includes topics
marked as "TBD" on the website, such as Docker, Docker Compose, Podman,
Rancher Docker Desktop, IDE selection and configuration (including IntelliJ,
Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
Microk8s, K3d, Helm Charts, and installation and usage of various development
tools like Brew for MacOS and Linux. I propose that the community contibutes
content for the following topics: __ __
>>>>>>>>>
>>>>>>>>> * Docker: how to install, run, and use Docker containers for
Fineract __ __
>>>>>>>>> * Docker Compose: how to use Docker Compose to orchestrate
multiple containers for Fineract __ __
>>>>>>>>> * Podman: how to use Podman as an alternative to Docker for
running containers __ __
>>>>>>>>> * Rancher Docker Desktop: how to use Rancher Docker Desktop to run
Kubernetes clusters on one's local machine __ __
>>>>>>>>> * IDE: how to choose and configure an IDE for Fineract development
__ __
>>>>>>>>> * IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
Fineract __ __
>>>>>>>>> * Eclipse: how to set up and use Eclipse as an IDE for Fineract __
__
>>>>>>>>> * VSCode: how to set up and use VSCode as an IDE for Fineract __
__
>>>>>>>>> * Kubernetes: how to deploy and manage Fineract on Kubernetes
clusters __ __
>>>>>>>>> * Minikube: how to use Minikube to run a local Kubernetes cluster
for Fineract __ __
>>>>>>>>> * Microk8s: how to use Microk8s to run a lightweight Kubernetes
cluster for Fineract __ __
>>>>>>>>> * K3d: how to use K3d to run a Kubernetes cluster in Docker for
Fineract __ __
>>>>>>>>> * Helm Charts: how to use Helm Charts to package and deploy
Fineract applications on Kubernetes __ __
>>>>>>>>> * Tools: how to install and use various tools that can help one
with Fineract development __ __
>>>>>>>>> * Brew: how to install and use Brew for MacOS and Linux __ __
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> By actively addressing these gaps in the documentation, we can
provide valuable support to the Fineract community and further showcase the
flexibility and compatibility of Fineract with different technologies and
platforms. __ __
>>>>>>>>>
>>>>>>>>> I look forward to collaborating with the community to contribute
content for these important topics and improve the overall documentation for
Fineract. __ __
>>>>>>>>>
>>>>>>>>> Best Regards __ __
>>>>>>>>>
>>>>>>>>> Bruce __ __
>>>>>>>>>
>>>>>>>>> __ __
>>>>>>>>>
>>>>>>>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey
<[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote: __ __
>>>>>>>>>
>>>>>>>>>> Meta or Bruce - any updates? __ __
>>>>>>>>>>
>>>>>>>>>> __ __
>>>>>>>>>>
>>>>>>>>>> __ __
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus
<[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote: __ __
>>>>>>>>>>
>>>>>>>>>>> Yep I'll be sharing the new design in which I hage taken care of
all the previous points you and others mentioned.. __ __
>>>>>>>>>>>
>>>>>>>>>>> __ __
>>>>>>>>>>>
>>>>>>>>>>> __ __
>>>>>>>>>>>
>>>>>>>>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey,
<[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote: __ __
>>>>>>>>>>>
>>>>>>>>>>>> I've started to change some of the structure of the wiki. I'm
just
> trying to clean it up: Does anyone have an objection?
>
> * Noting where content is historical and deprecating it
> * Moving the Quarterly PMC reports to slightly more prominence
>
> This is incremental.
>
> Inzemam - can you provide a new design to review taking on the feedback?
>
>
>
>
> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >
> > Okay I'll be looking into it..
> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
> fields. Surely working effectively with both the orgs by making good designs
> with premium feel.
> > Regards,
> > Inzemam
> >
> > On Fri, 10 Mar, 2023, 1:03 am James Dailey,
> <[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote:
> >>
> >> Please make a set of suggestions or revise your designs based on input.
> >>
> >> Feel free to dive into this .
> >>
> >>
> >>
> >>
> >>
> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >>>
> >>> Hello James,
> >>> When we are going to start the work or are we leaving it for future?
> >>>
> >>> Regards,
> >>> Inzemam
> >>>
> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus,
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >>>>
> >>>> Hi James,
> >>>> You are correct that we need to discuss more on the flows of events
> and placements. And I am also agree with the point that we can create a
> slack channel for this.
> >>>> Also the code will be in simple html, css and js format so anyone can
> create/change the things easily. The design is looking fancy and complicated
> but the code is as smooth as butter. So need to worry about maintainance.
> >>>> Regards,
> >>>> Inzemamul Haq
> >>>>
> >>>>
> >>>>
> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey,
> <[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote:
> >>>>>
> >>>>> Hi - Thank you for this.
> >>>>>
> >>>>> It's a very good conversation starter. I agreed with most of
> Javier's comments, which makes clear that we need to do a better job of
> "Explaining" and "Positioning".
> >>>>>
> >>>>> ASIDE: Javier - I invite you to write more such text and provide a
> top level set of bullet points that can be perhaps worked into the content.
> >>>>>
> >>>>> I think that the design colors are ok, the blue is appropriate for a
> financial system, meaning steady and trustworthy on the color wheel. Nice.
> >>>>>
> >>>>> We need more revamping of the content before we can properly do this
> design, so let's try to attack that problem.
> >>>>>
> >>>>> Here is a requirement that may not be clear to you:
> >>>>> * Site should be very simple, easy to change by anyone opening up a
> Text Editor and modifying the HTML directly. e.g. use CSS styles and
> hopefully with names that make sense
> >>>>> * Assume that you are gone and someone else has to modify just some
> text areas, adding content in specific sections.
> >>>>> * Assume that no-one touches the website for over a year, maybe three
> years, and avoid content that can get stale.
> >>>>>
> >>>>>
> >>>>> Message and Content issues:
> >>>>>
> >>>>> * Fineract is part of Apache and this is not always clear from the
> page today. Also, there is a common set of links and structure that you can
> find in other Apache projects. It is not a requirement to follow other
> Apache projects, but it would be useful to review them for commonalities:
> >>>>> \--> <https://hadoop.apache.org>
> >>>>> \--> <https://airflow.apache.org>
> >>>>> \--> <https://kafka.apache.org>
> >>>>>
> >>>>> * Note Community is there in each project. Check out the content
> that each project has.
> >>>>>
> >>>>> * Key tasks should be up top : Learn more, Help, Download
> >>>>> and this should then flow into the requirements for the other
> sections on the front page and then onto the wiki structure that we need
> >>>>>
> >>>>> * At this time Fineract-CN should probably not receive equal billing
> as the Fineract1.x releases it is still trying to get to a first release and
> fineract1.x is releasing on a regular basis with lots of activity. So, move
> Fineract-CN to a bottom section that's something about "Additional community
> technologies"
> >>>>> I was and am a big fan of this framework, and I know this positioning
> is controversial for some, but until we get a release out and lots of active
> development and deployments, that project remains very much a side project
> of the community. It may become a very important thing, but for now we
> should reflect the reality which is that Fineract1.x is where the vast
> majority of the dev is going on, and the vast majority of the users are
> there.
> >>>>>
> >>>>>
> >>>>> * We need to emphasize the key features of Fineract - there should be
> a summary of the system.
> >>>>>
> >>>>> This may require more chat and discussion on list or on slack and
> then development of a structure of content before you can really get a
> design.
> >>>>>
> >>>>> Thank you again.
> >>>>>
> >>>>> James Dailey
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >>>>>>
> >>>>>> Hello James,
> >>>>>> Have you reviewed the website frame. Please share the feedback.
> >>>>>> Regards,
> >>>>>> Inzemamul Haq
> >>>>>>
> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus,
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >>>>>>>
> >>>>>>> Hello Javier,
> >>>>>>> Thanks for your feedback. The points you mentioned, I'll implement
> them as you suggested now what I need is some more brief about the topics.
> This was the just an idea of how it'll look like surely we can change and
> add the things.
> >>>>>>> As you mentioned in the last that it's a template but it's not.
> It's designed by me on the figma and the assets I used are open source so
> their will be no licencing issue. I always go for the development through
> scratch so no need to worry about that.
> >>>>>>> Regards,
> >>>>>>> Inzemam
> >>>>>>>
> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain,
> <[javier@fiter.io](mailto:javier@fiter.io)> wrote:
> >>>>>>>>
> >>>>>>>> Hy Meta,
> >>>>>>>>
> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic in
> general, and it seems much more modern and suitable for the next stage of
> our community.
> >>>>>>>>
> >>>>>>>> My two cents:
> >>>>>>>>
> >>>>>>>> It is too linked with banks. Fineract has proved to be useful in
> other areas of the industry, not just banks. We need to convey that Fineract
> is a platform for many use cases. Using a mobile phone and a credit card as
> our visuals will put us in the last 20 years of the industry, and we are in
> the next 20 years. The images we need to use has to be conceptual, not rigid
> on old paradigms.
> >>>>>>>> Fineract is a backend. Fineract will help the financial industry
> transcend from the old paradigm of "save deposit boxes" to the new paradigm
> of "Internet switches," allowing the users of financial institutions to move
> their assets worldwide quickly and safely. All purchases are now digital.
> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the same
> exposure on our website as Fineract. Fineract CN it's still an experiment
> while most of our community depends on and uses Fineract. This must be
> clearly shown on the website and the real estate we dedicate to each one.
> Fineract CN wasn't the project incubated originally, and Fineract CN is not
> backward compatible with Fineract.
> >>>>>>>> The project we are proud of: I will only use the project part if
> we get three Fortune 500 companies using Fineract. It will also open a new
> can of worms on which project gets selected and which criteria we should
> use, on top of getting the right set of approvals from them to be used as
> projects.
> >>>>>>>> Last but not least, you used a template for the design. We need
> the license of that template that allows us to use it without limitations,
> and the template license is aligned with Apache 2.0.
> >>>>>>>>
> >>>>>>>> Javier
> >>>>>>>>
> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi James,
> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
> FINERACT redesigned website. Please review and let me know if you have any
> questions or changes needed.
> >>>>>>>>>
> >>>>>>>>> [
> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk](https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk)
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Inzemamul Haq
> >>>>>>>>>
> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey,
> <[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hi Meta - Any updates from you on this?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Okay lemme begin the work.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey,
> <[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> +1
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hi
> >>>>>>>>>>>>> I've been through the website and got it closely that what
> exact is there on the website. I'll create a static mockup for the website.
> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone
> new or experienced first comes to the website got confused of what's
> happening and how things are going we can work upon it.
> >>>>>>>>>>>>> Also I have a question are we going to implement blogger on
> that website? I have ability to work on static websites where the data comes
> from dynamic CMS.
> >>>>>>>>>>>>> So I can work on tha too....
> >>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey,
> <[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Inzemamul Haq -
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Appreciate the response. This is revising our single page
> website for the project, so not an app. The content needs to be largely
> static or to pick up content we regularly post on blog. The current site is
> basic html. Just making sure we’re talking about the same thing.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> [Fineract.Apache.org](http://Fineract.Apache.org)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a
> design lens, in my view. But, a good UIX process does start with who’s the
> audience and what’s their need when they land on the page.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can get
> a better Idea of what exactly has to be happen. By the 16th of Feb I'll come
> up with a design also will share here in the thread and we can get comments
> in the meeting.
> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an overall
> UI/UX
> >>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey,
> <[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We have
> four people who said they'd like to be involved.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and
> then we can share back here on list and also hold a meeting on zoom in mid
> February.
> >>>>>>>>>>>>>>>> Feb 16th?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
> document:
> >>>>>>>>>>>>>>>> [
> https://fineract.apache.org/docs/current/](https://fineract.apache.org/docs/current/)
> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
> detail.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Proposed Tasks:
> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
> there a gap in content (Bruce, Tekle? - start a thread about this)
> >>>>>>>>>>>>>>>> \--> also, scan the current wiki and find sections
> you think belong being "brought over". compile a list of those pages. If
> none, great.
> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
> landing page (Meta Cyrus?)
> >>>>>>>>>>>>>>>> \--> also, scan other Apache projects to find landing
> pages that you like
> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level functional
> description aimed at a Business Leader (Dick Dickson?)
> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
> confluence with links (james or ?)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
> thread.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> thanks
> >>>>>>>>>>>>>>>> James
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson
> <[d@gwocu.com](mailto:d@gwocu.com)> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Sent from my iPhone
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus
> <[inzemamhaq05@gmail.com](mailto:inzemamhaq05@gmail.com)> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Hi James,
> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
> develop a good user reliable website.
> >>>>>>>>>>>>>>>>> Where I can start??
> >>>>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey,
> <[jamespdailey@gmail.com](mailto:jamespdailey@gmail.com)> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> All -
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been
> 3+ years since we did a clean sweep of it. We also have a front landing
> page at <https://fineract.apache.org> that could be better at communicating
> the project and community. Who wants to work on this with me?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
> >>>>>>>>>>>>>>>>>> \---
> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Add blog feed
> >>>>>>>>>>>>>>>>>> Add feed to dev list
> >>>>>>>>>>>>>>>>>> Include FAQ
> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we
> should have a top level split on the main page as well, or perhaps a
> separate landing page for FineractCN.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> \---
> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to
> show two levels):
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> FAQ
> >>>>>>>>>>>>>>>>>> About Fineract
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> New top level functional descriptions
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> About FineractCN
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> TBD
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Project Management
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to be
> more prominent)
> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
> top)
> >>>>>>>>>>>>>>>>>> Surveys
> >>>>>>>>>>>>>>>>>> Release processes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> How do I get involved?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Committer guides
> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
> >>>>>>>>>>>>>>>>>> Standards
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Documentation
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
> documentation.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc)
> ... all go to blog
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> The current high level structure:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
> >>>>>>>>>>>>>>>>>> FINERACT
> >>>>>>>>>>>>>>>>>> FINERACT CN
> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> How-to articles
> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
> >>>>>>>>>>>>>>>>>> Meeting notes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>> \--
> >>>>>>>>>>>>>> Sent from Gmail Mobile
> >>>>>>>>>>
> >>>>>>>>>> \--
> >>>>>>>>>> Sent from Gmail Mobile
> >>
> >> \--
> >> Sent from Gmail Mobile __ __
>>>>>>
>>>>>> \-- ____
>>>>>>
>>>>>> Sent from Gmail Mobile __ __
El contenido de este mensaje y sus archivos electrónicos adjuntos constituyen
información confidencial, y puede además contener secretos comerciales o
industriales que se encuentran protegidos bajo las leyes de propiedad
intelectual. Su uso, divulgación, revelación y/o circulación no autorizados se
encuentran estrictamente prohibidos, por lo que si usted no es el destinatario
del mismo o lo recibió por error, notifique inmediatamente al remitente por
correo electrónico y elimine el mensaje así como toda información adjunta de
su sistema. En cumplimiento de lo establecido por las leyes de protección de
datos personales, Nubloq S.A.S. hace de su conocimiento que se encuentra a su
disposición la política de tratamiento de datos personales en la página de
internet [https://www.nubloq.co/legal/](https://www.nubloq.co/legal/) a efecto
de que pueda ejercer su derecho al hábeas data. Todos los datos personales
entregados vía correo electrónico serán utilizados de acuerdo con las
finalidades allí previstas. Puede también consultar nuestros términos y
condiciones en [https://www.nubloq.co/legal/](https://www.nubloq.co/legal/).
The contents of this message and its attachments are confidential information
and can hold trade secrets subject to intellectual property regulations. Its
unauthorized use, divulgation, reveal and/or circulation are therefore
strictly prohibited. In the event that you are not the intended recipient of
this email, please immediately notify the sender through email and delete the
message and any attachments from your system. Pursuant to the regulations on
data privacy, Nubloq S.A.S informs that the privacy policy is available for
consultation at: [https://www.nubloq.co/legal/](https://www.nubloq.co/legal/).
All personal data will be treated in accordance with the purposes provided
therein. You can also review our terms and conditions at
<https://www.nubloq.co/legal/>.
Re: Website and Wiki for Fineract updates
Posted by comsky juste <co...@gmail.com>.
Please add me.
On Wed, May 10, 2023, 3:58 AM Abhinav Sinha <ab...@gmail.com>
wrote:
> Could you pls add me to the call as well
>
>
>
> Thanks,
>
> Abhinav
>
>
>
> *From: *James Dailey <ja...@gmail.com>
> *Date: *Tuesday, May 9, 2023 at 9:53 PM
> *To: *dev@fineract.apache.org <de...@fineract.apache.org>
> *Subject: *Re: Website and Wiki for Fineract updates
>
> We will update this wiki page during and after the meeting
>
>
> https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
>
>
>
> (John - added)
>
> (Ernesto -added)
>
>
>
>
>
>
>
> On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
>
> Please add me to this call.
>
>
>
> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
> <eo...@yahoo.com.invalid> wrote:
>
> Please add me
>
>
> Sent from Yahoo Mail for iPhone
> <https://overview.mail.yahoo.com/?.src=iOS>
>
> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <in...@gmail.com>
> wrote:
>
> Yep I'll be there in meet call.
>
>
>
> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
> wrote:
>
> W can organize a zoom call. Then report back to the list here.
>
>
>
> I’ll suggest May 11th , 9am Pacific (PDT)
>
> I’ll send zoom link to anyone expressing interest.
>
>
>
>
>
>
>
> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
> wrote:
>
> Hello James,
>
> Sorry for the late reply I was stuck in gsoc but I know I'll get rejected
> so finally I am looking forward on the website as we dealt before.
>
> Can we have a zoom call? So we can get an idea of what exactly we are
> gonna place on the website as from the previous responses I am only getting
> that some of the things should be changed or replaced but with whom I can't
> get it.
>
> Regards,
>
> Inzemamul Haq
>
>
>
>
>
> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
> wrote:
>
> Hi Bruce - Good to know about those gaps in deployment and tools, but are
> those the only gaps in the documentation?
>
>
>
> So, question to you: is it already sufficiently clear on these topics:
>
> * explaining what the software does
>
> * explaining the architecture
>
> * explaining relationship between different components
>
> * what features are in each release
>
> * how to set up development environment
>
> * how to access APIs
>
> * how to find additional resources
>
>
>
> I did ask for 3-5 priority things, so please do try to identify where we
> start, even from your very long list or maybe adding to it, can we get your
> opinion on a few key things?
>
>
>
> What would you say is a priority?
>
>
>
> As a project, I think we need to simply and only offer one or two
> deployment options in our documentation, that way we can focus on getting
> those accurate and keeping them up to date. Others are of course free to
> offer their own improvements and alternatives.
>
>
>
> All - comments welcome.
>
>
>
> Thanks,
>
> James
>
>
>
>
>
>
>
> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>
> Hi,
>
>
>
> I hope this email finds you well. I wanted to share some observations
> after going through the documentation for Fineract again.
>
> While the documentation provides an overview of deployment options here
> https://fineract.apache.org/docs/current/#_deployment , I noticed that
> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
> guidance for users. There is also no deployment content on Kubernetes, AWS
> and Google Cloud. Let's address this.
>
> Additionally, the Fineract Development section here
> https://fineract.apache.org/docs/current/#_fineract_development_environment appears
> to be incomplete and in need of further content to cover important topics
> related to Fineract development. This section also includes topics marked
> as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
> Docker Desktop, IDE selection and configuration (including IntelliJ,
> Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
> Microk8s, K3d, Helm Charts, and installation and usage of various
> development tools like Brew for MacOS and Linux. I propose that the
> community contibutes content for the following topics:
>
> - Docker: how to install, run, and use Docker containers for Fineract
> - Docker Compose: how to use Docker Compose to orchestrate multiple
> containers for Fineract
> - Podman: how to use Podman as an alternative to Docker for running
> containers
> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
> Kubernetes clusters on one's local machine
> - IDE: how to choose and configure an IDE for Fineract development
> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
> - VSCode: how to set up and use VSCode as an IDE for Fineract
> - Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
> - Minikube: how to use Minikube to run a local Kubernetes cluster for
> Fineract
> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
> cluster for Fineract
> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
> Fineract
> - Helm Charts: how to use Helm Charts to package and deploy Fineract
> applications on Kubernetes
> - Tools: how to install and use various tools that can help one with
> Fineract development
> - Brew: how to install and use Brew for MacOS and Linux
>
> By actively addressing these gaps in the documentation, we can provide
> valuable support to the Fineract community and further showcase the
> flexibility and compatibility of Fineract with different technologies and
> platforms.
>
> I look forward to collaborating with the community to contribute content
> for these important topics and improve the overall documentation for
> Fineract.
>
> Best Regards
>
> Bruce
>
>
>
> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
> wrote:
>
> Meta or Bruce - any updates?
>
>
>
>
>
> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
> wrote:
>
> Yep I'll be sharing the new design in which I hage taken care of all the
> previous points you and others mentioned..
>
>
>
>
>
> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
> wrote:
>
> I've started to change some of the structure of the wiki. I'm just
> trying to clean it up: Does anyone have an objection?
>
> * Noting where content is historical and deprecating it
> * Moving the Quarterly PMC reports to slightly more prominence
>
> This is incremental.
>
> Inzemam - can you provide a new design to review taking on the feedback?
>
>
>
>
> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com> wrote:
> >
> > Okay I'll be looking into it..
> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
> fields. Surely working effectively with both the orgs by making good
> designs with premium feel.
> > Regards,
> > Inzemam
> >
> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
> wrote:
> >>
> >> Please make a set of suggestions or revise your designs based on input.
> >>
> >> Feel free to dive into this .
> >>
> >>
> >>
> >>
> >>
> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
> wrote:
> >>>
> >>> Hello James,
> >>> When we are going to start the work or are we leaving it for future?
> >>>
> >>> Regards,
> >>> Inzemam
> >>>
> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
> wrote:
> >>>>
> >>>> Hi James,
> >>>> You are correct that we need to discuss more on the flows of events
> and placements. And I am also agree with the point that we can create a
> slack channel for this.
> >>>> Also the code will be in simple html, css and js format so anyone can
> create/change the things easily. The design is looking fancy and
> complicated but the code is as smooth as butter. So need to worry about
> maintainance.
> >>>> Regards,
> >>>> Inzemamul Haq
> >>>>
> >>>>
> >>>>
> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
> wrote:
> >>>>>
> >>>>> Hi - Thank you for this.
> >>>>>
> >>>>> It's a very good conversation starter. I agreed with most of
> Javier's comments, which makes clear that we need to do a better job of
> "Explaining" and "Positioning".
> >>>>>
> >>>>> ASIDE: Javier - I invite you to write more such text and provide a
> top level set of bullet points that can be perhaps worked into the content.
> >>>>>
> >>>>> I think that the design colors are ok, the blue is appropriate for a
> financial system, meaning steady and trustworthy on the color wheel. Nice.
> >>>>>
> >>>>> We need more revamping of the content before we can properly do this
> design, so let's try to attack that problem.
> >>>>>
> >>>>> Here is a requirement that may not be clear to you:
> >>>>> * Site should be very simple, easy to change by anyone opening up a
> Text Editor and modifying the HTML directly. e.g. use CSS styles and
> hopefully with names that make sense
> >>>>> * Assume that you are gone and someone else has to modify just some
> text areas, adding content in specific sections.
> >>>>> * Assume that no-one touches the website for over a year, maybe
> three years, and avoid content that can get stale.
> >>>>>
> >>>>>
> >>>>> Message and Content issues:
> >>>>>
> >>>>> * Fineract is part of Apache and this is not always clear from the
> page today. Also, there is a common set of links and structure that you can
> find in other Apache projects. It is not a requirement to follow other
> Apache projects, but it would be useful to review them for commonalities:
> >>>>> --> https://hadoop.apache.org
> >>>>> --> https://airflow.apache.org
> >>>>> --> https://kafka.apache.org
> >>>>>
> >>>>> * Note Community is there in each project. Check out the content
> that each project has.
> >>>>>
> >>>>> * Key tasks should be up top : Learn more, Help, Download
> >>>>> and this should then flow into the requirements for the other
> sections on the front page and then onto the wiki structure that we need
> >>>>>
> >>>>> * At this time Fineract-CN should probably not receive equal billing
> as the Fineract1.x releases it is still trying to get to a first release
> and fineract1.x is releasing on a regular basis with lots of activity. So,
> move Fineract-CN to a bottom section that's something about "Additional
> community technologies"
> >>>>> I was and am a big fan of this framework, and I know this
> positioning is controversial for some, but until we get a release out and
> lots of active development and deployments, that project remains very much
> a side project of the community. It may become a very important thing, but
> for now we should reflect the reality which is that Fineract1.x is where
> the vast majority of the dev is going on, and the vast majority of the
> users are there.
> >>>>>
> >>>>>
> >>>>> * We need to emphasize the key features of Fineract - there should
> be a summary of the system.
> >>>>>
> >>>>> This may require more chat and discussion on list or on slack and
> then development of a structure of content before you can really get a
> design.
> >>>>>
> >>>>> Thank you again.
> >>>>>
> >>>>> James Dailey
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
> wrote:
> >>>>>>
> >>>>>> Hello James,
> >>>>>> Have you reviewed the website frame. Please share the feedback.
> >>>>>> Regards,
> >>>>>> Inzemamul Haq
> >>>>>>
> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
> wrote:
> >>>>>>>
> >>>>>>> Hello Javier,
> >>>>>>> Thanks for your feedback. The points you mentioned, I'll implement
> them as you suggested now what I need is some more brief about the topics.
> This was the just an idea of how it'll look like surely we can change and
> add the things.
> >>>>>>> As you mentioned in the last that it's a template but it's not.
> It's designed by me on the figma and the assets I used are open source so
> their will be no licencing issue. I always go for the development through
> scratch so no need to worry about that.
> >>>>>>> Regards,
> >>>>>>> Inzemam
> >>>>>>>
> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io>
> wrote:
> >>>>>>>>
> >>>>>>>> Hy Meta,
> >>>>>>>>
> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic in
> general, and it seems much more modern and suitable for the next stage of
> our community.
> >>>>>>>>
> >>>>>>>> My two cents:
> >>>>>>>>
> >>>>>>>> It is too linked with banks. Fineract has proved to be useful in
> other areas of the industry, not just banks. We need to convey that
> Fineract is a platform for many use cases. Using a mobile phone and a
> credit card as our visuals will put us in the last 20 years of the
> industry, and we are in the next 20 years. The images we need to use has to
> be conceptual, not rigid on old paradigms.
> >>>>>>>> Fineract is a backend. Fineract will help the financial industry
> transcend from the old paradigm of "save deposit boxes" to the new paradigm
> of "Internet switches," allowing the users of financial institutions to
> move their assets worldwide quickly and safely. All purchases are now
> digital.
> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
> same exposure on our website as Fineract. Fineract CN it's still an
> experiment while most of our community depends on and uses Fineract. This
> must be clearly shown on the website and the real estate we dedicate to
> each one. Fineract CN wasn't the project incubated originally, and Fineract
> CN is not backward compatible with Fineract.
> >>>>>>>> The project we are proud of: I will only use the project part if
> we get three Fortune 500 companies using Fineract. It will also open a new
> can of worms on which project gets selected and which criteria we should
> use, on top of getting the right set of approvals from them to be used as
> projects.
> >>>>>>>> Last but not least, you used a template for the design. We need
> the license of that template that allows us to use it without limitations,
> and the template license is aligned with Apache 2.0.
> >>>>>>>>
> >>>>>>>> Javier
> >>>>>>>>
> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi James,
> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
> FINERACT redesigned website. Please review and let me know if you have any
> questions or changes needed.
> >>>>>>>>>
> >>>>>>>>>
> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Inzemamul Haq
> >>>>>>>>>
> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hi Meta - Any updates from you on this?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Okay lemme begin the work.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> +1
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hi
> >>>>>>>>>>>>> I've been through the website and got it closely that what
> exact is there on the website. I'll create a static mockup for the website.
> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone
> new or experienced first comes to the website got confused of what's
> happening and how things are going we can work upon it.
> >>>>>>>>>>>>> Also I have a question are we going to implement blogger on
> that website? I have ability to work on static websites where the data
> comes from dynamic CMS.
> >>>>>>>>>>>>> So I can work on tha too....
> >>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Inzemamul Haq -
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Appreciate the response. This is revising our single page
> website for the project, so not an app. The content needs to be largely
> static or to pick up content we regularly post on blog. The current site is
> basic html. Just making sure we’re talking about the same thing.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Fineract.Apache.org
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a
> design lens, in my view. But, a good UIX process does start with who’s the
> audience and what’s their need when they land on the page.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
> come up with a design also will share here in the thread and we can get
> comments in the meeting.
> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
> overall UI/UX
> >>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We have
> four people who said they'd like to be involved.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and
> then we can share back here on list and also hold a meeting on zoom in mid
> February.
> >>>>>>>>>>>>>>>> Feb 16th?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
> document:
> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
> detail.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Proposed Tasks:
> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
> there a gap in content (Bruce, Tekle? - start a thread about this)
> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
> you think belong being "brought over". compile a list of those pages. If
> none, great.
> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
> landing page (Meta Cyrus?)
> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing
> pages that you like
> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
> functional description aimed at a Business Leader (Dick Dickson?)
> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
> confluence with links (james or ?)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
> thread.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> thanks
> >>>>>>>>>>>>>>>> James
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com>
> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Sent from my iPhone
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Hi James,
> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
> develop a good user reliable website.
> >>>>>>>>>>>>>>>>> Where I can start??
> >>>>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> All -
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been
> 3+ years since we did a clean sweep of it. We also have a front landing
> page at https://fineract.apache.org that could be better at
> communicating the project and community. Who wants to work on this with me?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
> >>>>>>>>>>>>>>>>>> ---
> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Add blog feed
> >>>>>>>>>>>>>>>>>> Add feed to dev list
> >>>>>>>>>>>>>>>>>> Include FAQ
> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we
> should have a top level split on the main page as well, or perhaps a
> separate landing page for FineractCN.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ---
> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how
> to show two levels):
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> FAQ
> >>>>>>>>>>>>>>>>>> About Fineract
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> New top level functional descriptions
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> About FineractCN
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> TBD
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Project Management
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to be
> more prominent)
> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
> top)
> >>>>>>>>>>>>>>>>>> Surveys
> >>>>>>>>>>>>>>>>>> Release processes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> How do I get involved?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Committer guides
> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
> >>>>>>>>>>>>>>>>>> Standards
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Documentation
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
> documentation.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc)
> ... all go to blog
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> The current high level structure:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
> >>>>>>>>>>>>>>>>>> FINERACT
> >>>>>>>>>>>>>>>>>> FINERACT CN
> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> How-to articles
> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
> >>>>>>>>>>>>>>>>>> Meeting notes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Sent from Gmail Mobile
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Sent from Gmail Mobile
> >>
> >> --
> >> Sent from Gmail Mobile
>
> --
>
> Sent from Gmail Mobile
>
>
Re: Website and Wiki for Fineract updates
Posted by Abhinav Sinha <ab...@gmail.com>.
Could you pls add me to the call as well
Thanks,
Abhinav
From: James Dailey <ja...@gmail.com>
Date: Tuesday, May 9, 2023 at 9:53 PM
To: dev@fineract.apache.org <de...@fineract.apache.org>
Subject: Re: Website and Wiki for Fineract updates
We will update this wiki page during and after the meeting
https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
(John - added)
(Ernesto -added)
On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io>> wrote:
Please add me to this call.
On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena <eo...@yahoo.com.invalid> wrote:
Please add me
Sent from Yahoo Mail for iPhone<https://overview.mail.yahoo.com/?.src=iOS>
On Saturday, April 29, 2023, 15:43, Inzemamul Haq <in...@gmail.com>> wrote:
Yep I'll be there in meet call.
On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>> wrote:
W can organize a zoom call. Then report back to the list here.
I’ll suggest May 11th , 9am Pacific (PDT)
I’ll send zoom link to anyone expressing interest.
On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>> wrote:
Hello James,
Sorry for the late reply I was stuck in gsoc but I know I'll get rejected so finally I am looking forward on the website as we dealt before.
Can we have a zoom call? So we can get an idea of what exactly we are gonna place on the website as from the previous responses I am only getting that some of the things should be changed or replaced but with whom I can't get it.
Regards,
Inzemamul Haq
On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>> wrote:
Hi Bruce - Good to know about those gaps in deployment and tools, but are those the only gaps in the documentation?
So, question to you: is it already sufficiently clear on these topics:
* explaining what the software does
* explaining the architecture
* explaining relationship between different components
* what features are in each release
* how to set up development environment
* how to access APIs
* how to find additional resources
I did ask for 3-5 priority things, so please do try to identify where we start, even from your very long list or maybe adding to it, can we get your opinion on a few key things?
What would you say is a priority?
As a project, I think we need to simply and only offer one or two deployment options in our documentation, that way we can focus on getting those accurate and keeping them up to date. Others are of course free to offer their own improvements and alternatives.
All - comments welcome.
Thanks,
James
On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com>> wrote:
Hi,
I hope this email finds you well. I wanted to share some observations after going through the documentation for Fineract again.
While the documentation provides an overview of deployment options here https://fineract.apache.org/docs/current/#_deployment , I noticed that several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss, Weblogic, and Payara, are marked as TBD, indicating a lack of content and guidance for users. There is also no deployment content on Kubernetes, AWS and Google Cloud. Let's address this.
Additionally, the Fineract Development section here https://fineract.apache.org/docs/current/#_fineract_development_environment appears to be incomplete and in need of further content to cover important topics related to Fineract development. This section also includes topics marked as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher Docker Desktop, IDE selection and configuration (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and management, Minikube, Microk8s, K3d, Helm Charts, and installation and usage of various development tools like Brew for MacOS and Linux. I propose that the community contibutes content for the following topics:
* Docker: how to install, run, and use Docker containers for Fineract
* Docker Compose: how to use Docker Compose to orchestrate multiple containers for Fineract
* Podman: how to use Podman as an alternative to Docker for running containers
* Rancher Docker Desktop: how to use Rancher Docker Desktop to run Kubernetes clusters on one's local machine
* IDE: how to choose and configure an IDE for Fineract development
* IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
* Eclipse: how to set up and use Eclipse as an IDE for Fineract
* VSCode: how to set up and use VSCode as an IDE for Fineract
* Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
* Minikube: how to use Minikube to run a local Kubernetes cluster for Fineract
* Microk8s: how to use Microk8s to run a lightweight Kubernetes cluster for Fineract
* K3d: how to use K3d to run a Kubernetes cluster in Docker for Fineract
* Helm Charts: how to use Helm Charts to package and deploy Fineract applications on Kubernetes
* Tools: how to install and use various tools that can help one with Fineract development
* Brew: how to install and use Brew for MacOS and Linux
By actively addressing these gaps in the documentation, we can provide valuable support to the Fineract community and further showcase the flexibility and compatibility of Fineract with different technologies and platforms.
I look forward to collaborating with the community to contribute content for these important topics and improve the overall documentation for Fineract.
Best Regards
Bruce
On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>> wrote:
Meta or Bruce - any updates?
On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>> wrote:
Yep I'll be sharing the new design in which I hage taken care of all the previous points you and others mentioned..
On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>> wrote:
I've started to change some of the structure of the wiki. I'm just
trying to clean it up: Does anyone have an objection?
* Noting where content is historical and deprecating it
* Moving the Quarterly PMC reports to slightly more prominence
This is incremental.
Inzemam - can you provide a new design to review taking on the feedback?
On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>> wrote:
>
> Okay I'll be looking into it..
> Also I am looking forward for GSOC'23 for MIFOS too in the frontend fields. Surely working effectively with both the orgs by making good designs with premium feel.
> Regards,
> Inzemam
>
> On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>> wrote:
>>
>> Please make a set of suggestions or revise your designs based on input.
>>
>> Feel free to dive into this .
>>
>>
>>
>>
>>
>> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>> wrote:
>>>
>>> Hello James,
>>> When we are going to start the work or are we leaving it for future?
>>>
>>> Regards,
>>> Inzemam
>>>
>>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>> wrote:
>>>>
>>>> Hi James,
>>>> You are correct that we need to discuss more on the flows of events and placements. And I am also agree with the point that we can create a slack channel for this.
>>>> Also the code will be in simple html, css and js format so anyone can create/change the things easily. The design is looking fancy and complicated but the code is as smooth as butter. So need to worry about maintainance.
>>>> Regards,
>>>> Inzemamul Haq
>>>>
>>>>
>>>>
>>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>> wrote:
>>>>>
>>>>> Hi - Thank you for this.
>>>>>
>>>>> It's a very good conversation starter. I agreed with most of Javier's comments, which makes clear that we need to do a better job of "Explaining" and "Positioning".
>>>>>
>>>>> ASIDE: Javier - I invite you to write more such text and provide a top level set of bullet points that can be perhaps worked into the content.
>>>>>
>>>>> I think that the design colors are ok, the blue is appropriate for a financial system, meaning steady and trustworthy on the color wheel. Nice.
>>>>>
>>>>> We need more revamping of the content before we can properly do this design, so let's try to attack that problem.
>>>>>
>>>>> Here is a requirement that may not be clear to you:
>>>>> * Site should be very simple, easy to change by anyone opening up a Text Editor and modifying the HTML directly. e.g. use CSS styles and hopefully with names that make sense
>>>>> * Assume that you are gone and someone else has to modify just some text areas, adding content in specific sections.
>>>>> * Assume that no-one touches the website for over a year, maybe three years, and avoid content that can get stale.
>>>>>
>>>>>
>>>>> Message and Content issues:
>>>>>
>>>>> * Fineract is part of Apache and this is not always clear from the page today. Also, there is a common set of links and structure that you can find in other Apache projects. It is not a requirement to follow other Apache projects, but it would be useful to review them for commonalities:
>>>>> --> https://hadoop.apache.org
>>>>> --> https://airflow.apache.org
>>>>> --> https://kafka.apache.org
>>>>>
>>>>> * Note Community is there in each project. Check out the content that each project has.
>>>>>
>>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>> and this should then flow into the requirements for the other sections on the front page and then onto the wiki structure that we need
>>>>>
>>>>> * At this time Fineract-CN should probably not receive equal billing as the Fineract1.x releases it is still trying to get to a first release and fineract1.x is releasing on a regular basis with lots of activity. So, move Fineract-CN to a bottom section that's something about "Additional community technologies"
>>>>> I was and am a big fan of this framework, and I know this positioning is controversial for some, but until we get a release out and lots of active development and deployments, that project remains very much a side project of the community. It may become a very important thing, but for now we should reflect the reality which is that Fineract1.x is where the vast majority of the dev is going on, and the vast majority of the users are there.
>>>>>
>>>>>
>>>>> * We need to emphasize the key features of Fineract - there should be a summary of the system.
>>>>>
>>>>> This may require more chat and discussion on list or on slack and then development of a structure of content before you can really get a design.
>>>>>
>>>>> Thank you again.
>>>>>
>>>>> James Dailey
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>> wrote:
>>>>>>
>>>>>> Hello James,
>>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>>> Regards,
>>>>>> Inzemamul Haq
>>>>>>
>>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>> wrote:
>>>>>>>
>>>>>>> Hello Javier,
>>>>>>> Thanks for your feedback. The points you mentioned, I'll implement them as you suggested now what I need is some more brief about the topics. This was the just an idea of how it'll look like surely we can change and add the things.
>>>>>>> As you mentioned in the last that it's a template but it's not. It's designed by me on the figma and the assets I used are open source so their will be no licencing issue. I always go for the development through scratch so no need to worry about that.
>>>>>>> Regards,
>>>>>>> Inzemam
>>>>>>>
>>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io>> wrote:
>>>>>>>>
>>>>>>>> Hy Meta,
>>>>>>>>
>>>>>>>> Great job; I like the enhancement of the visuals and aesthetic in general, and it seems much more modern and suitable for the next stage of our community.
>>>>>>>>
>>>>>>>> My two cents:
>>>>>>>>
>>>>>>>> It is too linked with banks. Fineract has proved to be useful in other areas of the industry, not just banks. We need to convey that Fineract is a platform for many use cases. Using a mobile phone and a credit card as our visuals will put us in the last 20 years of the industry, and we are in the next 20 years. The images we need to use has to be conceptual, not rigid on old paradigms.
>>>>>>>> Fineract is a backend. Fineract will help the financial industry transcend from the old paradigm of "save deposit boxes" to the new paradigm of "Internet switches," allowing the users of financial institutions to move their assets worldwide quickly and safely. All purchases are now digital.
>>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the same exposure on our website as Fineract. Fineract CN it's still an experiment while most of our community depends on and uses Fineract. This must be clearly shown on the website and the real estate we dedicate to each one. Fineract CN wasn't the project incubated originally, and Fineract CN is not backward compatible with Fineract.
>>>>>>>> The project we are proud of: I will only use the project part if we get three Fortune 500 companies using Fineract. It will also open a new can of worms on which project gets selected and which criteria we should use, on top of getting the right set of approvals from them to be used as projects.
>>>>>>>> Last but not least, you used a template for the design. We need the license of that template that allows us to use it without limitations, and the template license is aligned with Apache 2.0.
>>>>>>>>
>>>>>>>> Javier
>>>>>>>>
>>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Hi James,
>>>>>>>>> Below is the drive link of complete page screenshot of APACHE FINERACT redesigned website. Please review and let me know if you have any questions or changes needed.
>>>>>>>>>
>>>>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Inzemamul Haq
>>>>>>>>>
>>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Okay lemme begin the work.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi
>>>>>>>>>>>>> I've been through the website and got it closely that what exact is there on the website. I'll create a static mockup for the website.
>>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone new or experienced first comes to the website got confused of what's happening and how things are going we can work upon it.
>>>>>>>>>>>>> Also I have a question are we going to implement blogger on that website? I have ability to work on static websites where the data comes from dynamic CMS.
>>>>>>>>>>>>> So I can work on tha too....
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Inzemamul Haq -
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Appreciate the response. This is revising our single page website for the project, so not an app. The content needs to be largely static or to pick up content we regularly post on blog. The current site is basic html. Just making sure we’re talking about the same thing.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Fineract.Apache.org<http://Fineract.Apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a design lens, in my view. But, a good UIX process does start with who’s the audience and what’s their need when they land on the page.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>> First I will create mockup using the figma where we can get a better Idea of what exactly has to be happen. By the 16th of Feb I'll come up with a design also will share here in the thread and we can get comments in the meeting.
>>>>>>>>>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We have four people who said they'd like to be involved.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and then we can share back here on list and also hold a meeting on zoom in mid February.
>>>>>>>>>>>>>>>> Feb 16th?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Proposed Tasks:
>>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections you think belong being "brought over". compile a list of those pages. If none, great.
>>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the landing page (Meta Cyrus?)
>>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing pages that you like
>>>>>>>>>>>>>>>> 3) Provide a document outline of the high level functional description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence with links (james or ?)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>>>> James
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d@...@gwocu.com>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi James,
>>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and develop a good user reliable website.
>>>>>>>>>>>>>>>>> Where I can start??
>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> All -
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years since we did a clean sweep of it. We also have a front landing page at https://fineract.apache.org that could be better at communicating the project and community. Who wants to work on this with me?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Add blog feed
>>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>>>>>>>>>>>>>>> Include FAQ
>>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should have a top level split on the main page as well, or perhaps a separate landing page for FineractCN.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to show two levels):
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> FAQ
>>>>>>>>>>>>>>>>>> About Fineract
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> About FineractCN
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> TBD
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Project Management
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to be more prominent)
>>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at top)
>>>>>>>>>>>>>>>>>> Surveys
>>>>>>>>>>>>>>>>>> Release processes
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> How do I get involved?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Committer guides
>>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>>>>>>>>>>>>>>> Standards
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Documentation
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated documentation.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc) ... all go to blog
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>>>>>>>> FINERACT
>>>>>>>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> How-to articles
>>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sent from Gmail Mobile
>>
>> --
>> Sent from Gmail Mobile
--
Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
We will update this wiki page during and after the meeting
https://cwiki.apache.org/confluence/display/FINERACT/2023-05-11+Meeting+notes
(John - added)
(Ernesto -added)
On Tue, May 9, 2023 at 10:48 AM John Gathogo <jo...@fiter.io> wrote:
> Please add me to this call.
>
> On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
> <eo...@yahoo.com.invalid> wrote:
>
>> Please add me
>>
>>
>> Sent from Yahoo Mail for iPhone
>> <https://overview.mail.yahoo.com/?.src=iOS>
>>
>> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <in...@gmail.com>
>> wrote:
>>
>> Yep I'll be there in meet call.
>>
>> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>> W can organize a zoom call. Then report back to the list here.
>>
>> I’ll suggest May 11th , 9am Pacific (PDT)
>> I’ll send zoom link to anyone expressing interest.
>>
>>
>>
>> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
>> wrote:
>>
>> Hello James,
>> Sorry for the late reply I was stuck in gsoc but I know I'll get rejected
>> so finally I am looking forward on the website as we dealt before.
>> Can we have a zoom call? So we can get an idea of what exactly we are
>> gonna place on the website as from the previous responses I am only getting
>> that some of the things should be changed or replaced but with whom I can't
>> get it.
>> Regards,
>> Inzemamul Haq
>>
>>
>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>> Hi Bruce - Good to know about those gaps in deployment and tools, but are
>> those the only gaps in the documentation?
>>
>> So, question to you: is it already sufficiently clear on these topics:
>> * explaining what the software does
>> * explaining the architecture
>> * explaining relationship between different components
>> * what features are in each release
>> * how to set up development environment
>> * how to access APIs
>> * how to find additional resources
>>
>> I did ask for 3-5 priority things, so please do try to identify where we
>> start, even from your very long list or maybe adding to it, can we get your
>> opinion on a few key things?
>>
>> What would you say is a priority?
>>
>> As a project, I think we need to simply and only offer one or two
>> deployment options in our documentation, that way we can focus on getting
>> those accurate and keeping them up to date. Others are of course free to
>> offer their own improvements and alternatives.
>>
>> All - comments welcome.
>>
>> Thanks,
>> James
>>
>>
>>
>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>
>> Hi,
>>
>> I hope this email finds you well. I wanted to share some observations
>> after going through the documentation for Fineract again.
>>
>> While the documentation provides an overview of deployment options here
>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>> guidance for users. There is also no deployment content on Kubernetes, AWS
>> and Google Cloud. Let's address this.
>>
>> Additionally, the Fineract Development section here
>> https://fineract.apache.org/docs/current/#_fineract_development_environment
>> appears to be incomplete and in need of further content to cover
>> important topics related to Fineract development. This section also
>> includes topics marked as "TBD" on the website, such as Docker, Docker
>> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
>> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
>> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
>> usage of various development tools like Brew for MacOS and Linux. I
>> propose that the community contibutes content for the following topics:
>>
>>
>> - Docker: how to install, run, and use Docker containers for Fineract
>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>> containers for Fineract
>> - Podman: how to use Podman as an alternative to Docker for running
>> containers
>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>> Kubernetes clusters on one's local machine
>> - IDE: how to choose and configure an IDE for Fineract development
>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>> - Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
>> - Minikube: how to use Minikube to run a local Kubernetes cluster for
>> Fineract
>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>> cluster for Fineract
>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>> Fineract
>> - Helm Charts: how to use Helm Charts to package and deploy Fineract
>> applications on Kubernetes
>> - Tools: how to install and use various tools that can help one with
>> Fineract development
>> - Brew: how to install and use Brew for MacOS and Linux
>>
>> By actively addressing these gaps in the documentation, we can provide
>> valuable support to the Fineract community and further showcase the
>> flexibility and compatibility of Fineract with different technologies and
>> platforms.
>>
>> I look forward to collaborating with the community to contribute content
>> for these important topics and improve the overall documentation for
>> Fineract.
>>
>> Best Regards
>>
>> Bruce
>>
>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>> Meta or Bruce - any updates?
>>
>>
>>
>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>> wrote:
>>
>> Yep I'll be sharing the new design in which I hage taken care of all the
>> previous points you and others mentioned..
>>
>>
>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>> I've started to change some of the structure of the wiki. I'm just
>> trying to clean it up: Does anyone have an objection?
>>
>> * Noting where content is historical and deprecating it
>> * Moving the Quarterly PMC reports to slightly more prominence
>>
>> This is incremental.
>>
>> Inzemam - can you provide a new design to review taking on the feedback?
>>
>>
>>
>>
>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>> >
>> > Okay I'll be looking into it..
>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>> fields. Surely working effectively with both the orgs by making good
>> designs with premium feel.
>> > Regards,
>> > Inzemam
>> >
>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>> wrote:
>> >>
>> >> Please make a set of suggestions or revise your designs based on input.
>> >>
>> >> Feel free to dive into this .
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>> >>>
>> >>> Hello James,
>> >>> When we are going to start the work or are we leaving it for future?
>> >>>
>> >>> Regards,
>> >>> Inzemam
>> >>>
>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>> wrote:
>> >>>>
>> >>>> Hi James,
>> >>>> You are correct that we need to discuss more on the flows of events
>> and placements. And I am also agree with the point that we can create a
>> slack channel for this.
>> >>>> Also the code will be in simple html, css and js format so anyone
>> can create/change the things easily. The design is looking fancy and
>> complicated but the code is as smooth as butter. So need to worry about
>> maintainance.
>> >>>> Regards,
>> >>>> Inzemamul Haq
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
>> wrote:
>> >>>>>
>> >>>>> Hi - Thank you for this.
>> >>>>>
>> >>>>> It's a very good conversation starter. I agreed with most of
>> Javier's comments, which makes clear that we need to do a better job of
>> "Explaining" and "Positioning".
>> >>>>>
>> >>>>> ASIDE: Javier - I invite you to write more such text and provide a
>> top level set of bullet points that can be perhaps worked into the content.
>> >>>>>
>> >>>>> I think that the design colors are ok, the blue is appropriate for
>> a financial system, meaning steady and trustworthy on the color wheel. Nice.
>> >>>>>
>> >>>>> We need more revamping of the content before we can properly do
>> this design, so let's try to attack that problem.
>> >>>>>
>> >>>>> Here is a requirement that may not be clear to you:
>> >>>>> * Site should be very simple, easy to change by anyone opening up a
>> Text Editor and modifying the HTML directly. e.g. use CSS styles and
>> hopefully with names that make sense
>> >>>>> * Assume that you are gone and someone else has to modify just some
>> text areas, adding content in specific sections.
>> >>>>> * Assume that no-one touches the website for over a year, maybe
>> three years, and avoid content that can get stale.
>> >>>>>
>> >>>>>
>> >>>>> Message and Content issues:
>> >>>>>
>> >>>>> * Fineract is part of Apache and this is not always clear from the
>> page today. Also, there is a common set of links and structure that you can
>> find in other Apache projects. It is not a requirement to follow other
>> Apache projects, but it would be useful to review them for commonalities:
>> >>>>> --> https://hadoop.apache.org
>> >>>>> --> https://airflow.apache.org
>> >>>>> --> https://kafka.apache.org
>> >>>>>
>> >>>>> * Note Community is there in each project. Check out the content
>> that each project has.
>> >>>>>
>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>> >>>>> and this should then flow into the requirements for the other
>> sections on the front page and then onto the wiki structure that we need
>> >>>>>
>> >>>>> * At this time Fineract-CN should probably not receive equal
>> billing as the Fineract1.x releases it is still trying to get to a first
>> release and fineract1.x is releasing on a regular basis with lots of
>> activity. So, move Fineract-CN to a bottom section that's something about
>> "Additional community technologies"
>> >>>>> I was and am a big fan of this framework, and I know this
>> positioning is controversial for some, but until we get a release out and
>> lots of active development and deployments, that project remains very much
>> a side project of the community. It may become a very important thing, but
>> for now we should reflect the reality which is that Fineract1.x is where
>> the vast majority of the dev is going on, and the vast majority of the
>> users are there.
>> >>>>>
>> >>>>>
>> >>>>> * We need to emphasize the key features of Fineract - there should
>> be a summary of the system.
>> >>>>>
>> >>>>> This may require more chat and discussion on list or on slack and
>> then development of a structure of content before you can really get a
>> design.
>> >>>>>
>> >>>>> Thank you again.
>> >>>>>
>> >>>>> James Dailey
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>> >>>>>>
>> >>>>>> Hello James,
>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>> >>>>>> Regards,
>> >>>>>> Inzemamul Haq
>> >>>>>>
>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
>> wrote:
>> >>>>>>>
>> >>>>>>> Hello Javier,
>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>> implement them as you suggested now what I need is some more brief about
>> the topics. This was the just an idea of how it'll look like surely we can
>> change and add the things.
>> >>>>>>> As you mentioned in the last that it's a template but it's not.
>> It's designed by me on the figma and the assets I used are open source so
>> their will be no licencing issue. I always go for the development through
>> scratch so no need to worry about that.
>> >>>>>>> Regards,
>> >>>>>>> Inzemam
>> >>>>>>>
>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>> javier@fiter.io> wrote:
>> >>>>>>>>
>> >>>>>>>> Hy Meta,
>> >>>>>>>>
>> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic
>> in general, and it seems much more modern and suitable for the next stage
>> of our community.
>> >>>>>>>>
>> >>>>>>>> My two cents:
>> >>>>>>>>
>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful in
>> other areas of the industry, not just banks. We need to convey that
>> Fineract is a platform for many use cases. Using a mobile phone and a
>> credit card as our visuals will put us in the last 20 years of the
>> industry, and we are in the next 20 years. The images we need to use has to
>> be conceptual, not rigid on old paradigms.
>> >>>>>>>> Fineract is a backend. Fineract will help the financial industry
>> transcend from the old paradigm of "save deposit boxes" to the new paradigm
>> of "Internet switches," allowing the users of financial institutions to
>> move their assets worldwide quickly and safely. All purchases are now
>> digital.
>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>> same exposure on our website as Fineract. Fineract CN it's still an
>> experiment while most of our community depends on and uses Fineract. This
>> must be clearly shown on the website and the real estate we dedicate to
>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>> CN is not backward compatible with Fineract.
>> >>>>>>>> The project we are proud of: I will only use the project part if
>> we get three Fortune 500 companies using Fineract. It will also open a new
>> can of worms on which project gets selected and which criteria we should
>> use, on top of getting the right set of approvals from them to be used as
>> projects.
>> >>>>>>>> Last but not least, you used a template for the design. We need
>> the license of that template that allows us to use it without limitations,
>> and the template license is aligned with Apache 2.0.
>> >>>>>>>>
>> >>>>>>>> Javier
>> >>>>>>>>
>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>
>> >>>>>>>>> Hi James,
>> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
>> FINERACT redesigned website. Please review and let me know if you have any
>> questions or changes needed.
>> >>>>>>>>>
>> >>>>>>>>>
>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>> >>>>>>>>>
>> >>>>>>>>> Regards,
>> >>>>>>>>> Inzemamul Haq
>> >>>>>>>>>
>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>> Okay lemme begin the work.
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> +1
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Hi
>> >>>>>>>>>>>>> I've been through the website and got it closely that what
>> exact is there on the website. I'll create a static mockup for the website.
>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone
>> new or experienced first comes to the website got confused of what's
>> happening and how things are going we can work upon it.
>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger on
>> that website? I have ability to work on static websites where the data
>> comes from dynamic CMS.
>> >>>>>>>>>>>>> So I can work on tha too....
>> >>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>> Inzemamul Haq
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Inzemamul Haq -
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single page
>> website for the project, so not an app. The content needs to be largely
>> static or to pick up content we regularly post on blog. The current site is
>> basic html. Just making sure we’re talking about the same thing.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Fineract.Apache.org
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is
>> a design lens, in my view. But, a good UIX process does start with who’s
>> the audience and what’s their need when they land on the page.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Hi,
>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
>> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
>> come up with a design also will share here in the thread and we can get
>> comments in the meeting.
>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>> overall UI/UX
>> >>>>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Inzemamul Haq
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>> have four people who said they'd like to be involved.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and
>> then we can share back here on list and also hold a meeting on zoom in mid
>> February.
>> >>>>>>>>>>>>>>>> Feb 16th?
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>> document:
>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>> detail.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Proposed Tasks:
>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>> there a gap in content (Bruce, Tekle? - start a thread about this)
>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
>> you think belong being "brought over". compile a list of those pages. If
>> none, great.
>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>> landing page (Meta Cyrus?)
>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing
>> pages that you like
>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>> functional description aimed at a Business Leader (Dick Dickson?)
>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>> confluence with links (james or ?)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>> thread.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> thanks
>> >>>>>>>>>>>>>>>> James
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>> d@gwocu.com> wrote:
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Hi James,
>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
>> develop a good user reliable website.
>> >>>>>>>>>>>>>>>>> Where I can start??
>> >>>>>>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> All -
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>> been 3+ years since we did a clean sweep of it. We also have a front
>> landing page at https://fineract.apache.org that could be better at
>> communicating the project and community. Who wants to work on this with me?
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>> >>>>>>>>>>>>>>>>>> ---
>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Add blog feed
>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>> >>>>>>>>>>>>>>>>>> Include FAQ
>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think
>> we should have a top level split on the main page as well, or perhaps a
>> separate landing page for FineractCN.
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> ---
>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how
>> to show two levels):
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> FAQ
>> >>>>>>>>>>>>>>>>>> About Fineract
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> About FineractCN
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> TBD
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Project Management
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to
>> be more prominent)
>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
>> top)
>> >>>>>>>>>>>>>>>>>> Surveys
>> >>>>>>>>>>>>>>>>>> Release processes
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> How do I get involved?
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Committer guides
>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>> >>>>>>>>>>>>>>>>>> Standards
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Documentation
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>> documentation.
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc)
>> ... all go to blog
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> The current high level structure:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>> >>>>>>>>>>>>>>>>>> FINERACT
>> >>>>>>>>>>>>>>>>>> FINERACT CN
>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> How-to articles
>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>> >>>>>>>>>>>>>>>>>> Meeting notes
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> --
>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>> >>>>>>>>>>
>> >>>>>>>>>> --
>> >>>>>>>>>> Sent from Gmail Mobile
>> >>
>> >> --
>> >> Sent from Gmail Mobile
>>
>> --
>> Sent from Gmail Mobile
>>
>>
Re: Website and Wiki for Fineract updates
Posted by John Gathogo <jo...@fiter.io>.
Please add me to this call.
On Sun, Apr 30, 2023 at 2:43 AM Ernesto J. Olivares Mena
<eo...@yahoo.com.invalid> wrote:
> Please add me
>
>
> Sent from Yahoo Mail for iPhone
> <https://overview.mail.yahoo.com/?.src=iOS>
>
> On Saturday, April 29, 2023, 15:43, Inzemamul Haq <in...@gmail.com>
> wrote:
>
> Yep I'll be there in meet call.
>
> On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com>
> wrote:
>
> W can organize a zoom call. Then report back to the list here.
>
> I’ll suggest May 11th , 9am Pacific (PDT)
> I’ll send zoom link to anyone expressing interest.
>
>
>
> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
> wrote:
>
> Hello James,
> Sorry for the late reply I was stuck in gsoc but I know I'll get rejected
> so finally I am looking forward on the website as we dealt before.
> Can we have a zoom call? So we can get an idea of what exactly we are
> gonna place on the website as from the previous responses I am only getting
> that some of the things should be changed or replaced but with whom I can't
> get it.
> Regards,
> Inzemamul Haq
>
>
> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
> wrote:
>
> Hi Bruce - Good to know about those gaps in deployment and tools, but are
> those the only gaps in the documentation?
>
> So, question to you: is it already sufficiently clear on these topics:
> * explaining what the software does
> * explaining the architecture
> * explaining relationship between different components
> * what features are in each release
> * how to set up development environment
> * how to access APIs
> * how to find additional resources
>
> I did ask for 3-5 priority things, so please do try to identify where we
> start, even from your very long list or maybe adding to it, can we get your
> opinion on a few key things?
>
> What would you say is a priority?
>
> As a project, I think we need to simply and only offer one or two
> deployment options in our documentation, that way we can focus on getting
> those accurate and keeping them up to date. Others are of course free to
> offer their own improvements and alternatives.
>
> All - comments welcome.
>
> Thanks,
> James
>
>
>
> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>
> Hi,
>
> I hope this email finds you well. I wanted to share some observations
> after going through the documentation for Fineract again.
>
> While the documentation provides an overview of deployment options here
> https://fineract.apache.org/docs/current/#_deployment , I noticed that
> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
> guidance for users. There is also no deployment content on Kubernetes, AWS
> and Google Cloud. Let's address this.
>
> Additionally, the Fineract Development section here
> https://fineract.apache.org/docs/current/#_fineract_development_environment
> appears to be incomplete and in need of further content to cover
> important topics related to Fineract development. This section also
> includes topics marked as "TBD" on the website, such as Docker, Docker
> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
> usage of various development tools like Brew for MacOS and Linux. I
> propose that the community contibutes content for the following topics:
>
>
> - Docker: how to install, run, and use Docker containers for Fineract
> - Docker Compose: how to use Docker Compose to orchestrate multiple
> containers for Fineract
> - Podman: how to use Podman as an alternative to Docker for running
> containers
> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
> Kubernetes clusters on one's local machine
> - IDE: how to choose and configure an IDE for Fineract development
> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
> - VSCode: how to set up and use VSCode as an IDE for Fineract
> - Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
> - Minikube: how to use Minikube to run a local Kubernetes cluster for
> Fineract
> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
> cluster for Fineract
> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
> Fineract
> - Helm Charts: how to use Helm Charts to package and deploy Fineract
> applications on Kubernetes
> - Tools: how to install and use various tools that can help one with
> Fineract development
> - Brew: how to install and use Brew for MacOS and Linux
>
> By actively addressing these gaps in the documentation, we can provide
> valuable support to the Fineract community and further showcase the
> flexibility and compatibility of Fineract with different technologies and
> platforms.
>
> I look forward to collaborating with the community to contribute content
> for these important topics and improve the overall documentation for
> Fineract.
>
> Best Regards
>
> Bruce
>
> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
> wrote:
>
> Meta or Bruce - any updates?
>
>
>
> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
> wrote:
>
> Yep I'll be sharing the new design in which I hage taken care of all the
> previous points you and others mentioned..
>
>
> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
> wrote:
>
> I've started to change some of the structure of the wiki. I'm just
> trying to clean it up: Does anyone have an objection?
>
> * Noting where content is historical and deprecating it
> * Moving the Quarterly PMC reports to slightly more prominence
>
> This is incremental.
>
> Inzemam - can you provide a new design to review taking on the feedback?
>
>
>
>
> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com> wrote:
> >
> > Okay I'll be looking into it..
> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
> fields. Surely working effectively with both the orgs by making good
> designs with premium feel.
> > Regards,
> > Inzemam
> >
> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
> wrote:
> >>
> >> Please make a set of suggestions or revise your designs based on input.
> >>
> >> Feel free to dive into this .
> >>
> >>
> >>
> >>
> >>
> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
> wrote:
> >>>
> >>> Hello James,
> >>> When we are going to start the work or are we leaving it for future?
> >>>
> >>> Regards,
> >>> Inzemam
> >>>
> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
> wrote:
> >>>>
> >>>> Hi James,
> >>>> You are correct that we need to discuss more on the flows of events
> and placements. And I am also agree with the point that we can create a
> slack channel for this.
> >>>> Also the code will be in simple html, css and js format so anyone can
> create/change the things easily. The design is looking fancy and
> complicated but the code is as smooth as butter. So need to worry about
> maintainance.
> >>>> Regards,
> >>>> Inzemamul Haq
> >>>>
> >>>>
> >>>>
> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
> wrote:
> >>>>>
> >>>>> Hi - Thank you for this.
> >>>>>
> >>>>> It's a very good conversation starter. I agreed with most of
> Javier's comments, which makes clear that we need to do a better job of
> "Explaining" and "Positioning".
> >>>>>
> >>>>> ASIDE: Javier - I invite you to write more such text and provide a
> top level set of bullet points that can be perhaps worked into the content.
> >>>>>
> >>>>> I think that the design colors are ok, the blue is appropriate for a
> financial system, meaning steady and trustworthy on the color wheel. Nice.
> >>>>>
> >>>>> We need more revamping of the content before we can properly do this
> design, so let's try to attack that problem.
> >>>>>
> >>>>> Here is a requirement that may not be clear to you:
> >>>>> * Site should be very simple, easy to change by anyone opening up a
> Text Editor and modifying the HTML directly. e.g. use CSS styles and
> hopefully with names that make sense
> >>>>> * Assume that you are gone and someone else has to modify just some
> text areas, adding content in specific sections.
> >>>>> * Assume that no-one touches the website for over a year, maybe
> three years, and avoid content that can get stale.
> >>>>>
> >>>>>
> >>>>> Message and Content issues:
> >>>>>
> >>>>> * Fineract is part of Apache and this is not always clear from the
> page today. Also, there is a common set of links and structure that you can
> find in other Apache projects. It is not a requirement to follow other
> Apache projects, but it would be useful to review them for commonalities:
> >>>>> --> https://hadoop.apache.org
> >>>>> --> https://airflow.apache.org
> >>>>> --> https://kafka.apache.org
> >>>>>
> >>>>> * Note Community is there in each project. Check out the content
> that each project has.
> >>>>>
> >>>>> * Key tasks should be up top : Learn more, Help, Download
> >>>>> and this should then flow into the requirements for the other
> sections on the front page and then onto the wiki structure that we need
> >>>>>
> >>>>> * At this time Fineract-CN should probably not receive equal billing
> as the Fineract1.x releases it is still trying to get to a first release
> and fineract1.x is releasing on a regular basis with lots of activity. So,
> move Fineract-CN to a bottom section that's something about "Additional
> community technologies"
> >>>>> I was and am a big fan of this framework, and I know this
> positioning is controversial for some, but until we get a release out and
> lots of active development and deployments, that project remains very much
> a side project of the community. It may become a very important thing, but
> for now we should reflect the reality which is that Fineract1.x is where
> the vast majority of the dev is going on, and the vast majority of the
> users are there.
> >>>>>
> >>>>>
> >>>>> * We need to emphasize the key features of Fineract - there should
> be a summary of the system.
> >>>>>
> >>>>> This may require more chat and discussion on list or on slack and
> then development of a structure of content before you can really get a
> design.
> >>>>>
> >>>>> Thank you again.
> >>>>>
> >>>>> James Dailey
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
> wrote:
> >>>>>>
> >>>>>> Hello James,
> >>>>>> Have you reviewed the website frame. Please share the feedback.
> >>>>>> Regards,
> >>>>>> Inzemamul Haq
> >>>>>>
> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
> wrote:
> >>>>>>>
> >>>>>>> Hello Javier,
> >>>>>>> Thanks for your feedback. The points you mentioned, I'll implement
> them as you suggested now what I need is some more brief about the topics.
> This was the just an idea of how it'll look like surely we can change and
> add the things.
> >>>>>>> As you mentioned in the last that it's a template but it's not.
> It's designed by me on the figma and the assets I used are open source so
> their will be no licencing issue. I always go for the development through
> scratch so no need to worry about that.
> >>>>>>> Regards,
> >>>>>>> Inzemam
> >>>>>>>
> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io>
> wrote:
> >>>>>>>>
> >>>>>>>> Hy Meta,
> >>>>>>>>
> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic in
> general, and it seems much more modern and suitable for the next stage of
> our community.
> >>>>>>>>
> >>>>>>>> My two cents:
> >>>>>>>>
> >>>>>>>> It is too linked with banks. Fineract has proved to be useful in
> other areas of the industry, not just banks. We need to convey that
> Fineract is a platform for many use cases. Using a mobile phone and a
> credit card as our visuals will put us in the last 20 years of the
> industry, and we are in the next 20 years. The images we need to use has to
> be conceptual, not rigid on old paradigms.
> >>>>>>>> Fineract is a backend. Fineract will help the financial industry
> transcend from the old paradigm of "save deposit boxes" to the new paradigm
> of "Internet switches," allowing the users of financial institutions to
> move their assets worldwide quickly and safely. All purchases are now
> digital.
> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
> same exposure on our website as Fineract. Fineract CN it's still an
> experiment while most of our community depends on and uses Fineract. This
> must be clearly shown on the website and the real estate we dedicate to
> each one. Fineract CN wasn't the project incubated originally, and Fineract
> CN is not backward compatible with Fineract.
> >>>>>>>> The project we are proud of: I will only use the project part if
> we get three Fortune 500 companies using Fineract. It will also open a new
> can of worms on which project gets selected and which criteria we should
> use, on top of getting the right set of approvals from them to be used as
> projects.
> >>>>>>>> Last but not least, you used a template for the design. We need
> the license of that template that allows us to use it without limitations,
> and the template license is aligned with Apache 2.0.
> >>>>>>>>
> >>>>>>>> Javier
> >>>>>>>>
> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi James,
> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
> FINERACT redesigned website. Please review and let me know if you have any
> questions or changes needed.
> >>>>>>>>>
> >>>>>>>>>
> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Inzemamul Haq
> >>>>>>>>>
> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hi Meta - Any updates from you on this?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Okay lemme begin the work.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> +1
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hi
> >>>>>>>>>>>>> I've been through the website and got it closely that what
> exact is there on the website. I'll create a static mockup for the website.
> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone
> new or experienced first comes to the website got confused of what's
> happening and how things are going we can work upon it.
> >>>>>>>>>>>>> Also I have a question are we going to implement blogger on
> that website? I have ability to work on static websites where the data
> comes from dynamic CMS.
> >>>>>>>>>>>>> So I can work on tha too....
> >>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Inzemamul Haq -
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Appreciate the response. This is revising our single page
> website for the project, so not an app. The content needs to be largely
> static or to pick up content we regularly post on blog. The current site is
> basic html. Just making sure we’re talking about the same thing.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Fineract.Apache.org
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a
> design lens, in my view. But, a good UIX process does start with who’s the
> audience and what’s their need when they land on the page.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
> come up with a design also will share here in the thread and we can get
> comments in the meeting.
> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
> overall UI/UX
> >>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We have
> four people who said they'd like to be involved.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and
> then we can share back here on list and also hold a meeting on zoom in mid
> February.
> >>>>>>>>>>>>>>>> Feb 16th?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
> document:
> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
> detail.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Proposed Tasks:
> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
> there a gap in content (Bruce, Tekle? - start a thread about this)
> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
> you think belong being "brought over". compile a list of those pages. If
> none, great.
> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
> landing page (Meta Cyrus?)
> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing
> pages that you like
> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
> functional description aimed at a Business Leader (Dick Dickson?)
> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
> confluence with links (james or ?)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
> thread.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> thanks
> >>>>>>>>>>>>>>>> James
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com>
> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Sent from my iPhone
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Hi James,
> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
> develop a good user reliable website.
> >>>>>>>>>>>>>>>>> Where I can start??
> >>>>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> All -
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been
> 3+ years since we did a clean sweep of it. We also have a front landing
> page at https://fineract.apache.org that could be better at
> communicating the project and community. Who wants to work on this with me?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
> >>>>>>>>>>>>>>>>>> ---
> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Add blog feed
> >>>>>>>>>>>>>>>>>> Add feed to dev list
> >>>>>>>>>>>>>>>>>> Include FAQ
> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we
> should have a top level split on the main page as well, or perhaps a
> separate landing page for FineractCN.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ---
> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how
> to show two levels):
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> FAQ
> >>>>>>>>>>>>>>>>>> About Fineract
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> New top level functional descriptions
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> About FineractCN
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> TBD
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Project Management
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to be
> more prominent)
> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
> top)
> >>>>>>>>>>>>>>>>>> Surveys
> >>>>>>>>>>>>>>>>>> Release processes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> How do I get involved?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Committer guides
> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
> >>>>>>>>>>>>>>>>>> Standards
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Documentation
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
> documentation.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc)
> ... all go to blog
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> The current high level structure:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
> >>>>>>>>>>>>>>>>>> FINERACT
> >>>>>>>>>>>>>>>>>> FINERACT CN
> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> How-to articles
> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
> >>>>>>>>>>>>>>>>>> Meeting notes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Sent from Gmail Mobile
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Sent from Gmail Mobile
> >>
> >> --
> >> Sent from Gmail Mobile
>
> --
> Sent from Gmail Mobile
>
>
Re: Website and Wiki for Fineract updates
Posted by "Ernesto J. Olivares Mena" <eo...@yahoo.com.INVALID>.
Please add me
Sent from Yahoo Mail for iPhone
On Saturday, April 29, 2023, 15:43, Inzemamul Haq <in...@gmail.com> wrote:
Yep I'll be there in meet call.
On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com> wrote:
W can organize a zoom call. Then report back to the list here.
I’ll suggest May 11th , 9am Pacific (PDT)I’ll send zoom link to anyone expressing interest.
On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com> wrote:
Hello James, Sorry for the late reply I was stuck in gsoc but I know I'll get rejected so finally I am looking forward on the website as we dealt before.Can we have a zoom call? So we can get an idea of what exactly we are gonna place on the website as from the previous responses I am only getting that some of the things should be changed or replaced but with whom I can't get it. Regards, Inzemamul Haq
On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com> wrote:
Hi Bruce - Good to know about those gaps in deployment and tools, but are those the only gaps in the documentation?
So, question to you: is it already sufficiently clear on these topics: * explaining what the software does
* explaining the architecture * explaining relationship between different components * what features are in each release
* how to set up development environment * how to access APIs * how to find additional resources
I did ask for 3-5 priority things, so please do try to identify where we start, even from your very long list or maybe adding to it, can we get your opinion on a few key things?
What would you say is a priority?
As a project, I think we need to simply and only offer one or two deployment options in our documentation, that way we can focus on getting those accurate and keeping them up to date. Others are of course free to offer their own improvements and alternatives.
All - comments welcome.
Thanks, James
On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
Hi,
I hope this email finds you well. I wanted to share someobservations after going through the documentation for Fineract again.
Whilethe documentation provides an overview of deployment options here https://fineract.apache.org/docs/current/#_deployment , Inoticed that several options, such as Docker Compose, Tomcat, Undertow, Jetty,JBoss, Weblogic, and Payara, are marked as TBD, indicating a lack of contentand guidance for users. There is also no deployment content on Kubernetes, AWS and Google Cloud. Let's address this.
Additionally, the Fineract Development section here https://fineract.apache.org/docs/current/#_fineract_development_environment appears to be incomplete and in need of further content tocover important topics related to Fineract development. This section alsoincludes topics marked as "TBD" on the website, such as Docker,Docker Compose, Podman, Rancher Docker Desktop, IDE selection and configuration(including IntelliJ, Eclipse, and VSCode), Kubernetes deployment andmanagement, Minikube, Microk8s, K3d, Helm Charts, and installation and usage ofvarious development tools like Brew for MacOS and Linux. I propose that the community contibutes content for the following topics:
- Docker: how to install, run, and use Docker containers forFineract
- Docker Compose: how to use Docker Compose to orchestratemultiple containers for Fineract
- Podman: how to use Podman as an alternative to Docker forrunning containers
- Rancher Docker Desktop: how to use Rancher Docker Desktopto run Kubernetes clusters on one's local machine
- IDE: how to choose and configure an IDE for Fineractdevelopment
- IntelliJ: how to set up and use IntelliJ IDEA as an IDEfor Fineract
- Eclipse: how to set up and use Eclipse as an IDE forFineract
- VSCode: how to set up and use VSCode as an IDE forFineract
- Kubernetes: how to deploy and manage Fineract onKubernetes clusters
- Minikube: how to use Minikube to run a local Kubernetescluster for Fineract
- Microk8s: how to use Microk8s to run a lightweightKubernetes cluster for Fineract
- K3d: how to use K3d to run a Kubernetes cluster in Dockerfor Fineract
- Helm Charts: how to use Helm Charts to package and deployFineract applications on Kubernetes
- Tools: how to install and use various tools that can help one with Fineract development
- Brew: how to install and use Brew for MacOS and Linux
By actively addressing these gaps in the documentation, wecan provide valuable support to the Fineract community and further showcase theflexibility and compatibility of Fineract with different technologies andplatforms.
I look forward to collaborating with the community tocontribute content for these important topics and improve the overalldocumentation for Fineract.
Best Regards
Bruce
On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com> wrote:
Meta or Bruce - any updates?
On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com> wrote:
Yep I'll be sharing the new design in which I hage taken care of all the previous points you and others mentioned..
On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com> wrote:
I've started to change some of the structure of the wiki. I'm just
trying to clean it up: Does anyone have an objection?
* Noting where content is historical and deprecating it
* Moving the Quarterly PMC reports to slightly more prominence
This is incremental.
Inzemam - can you provide a new design to review taking on the feedback?
On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com> wrote:
>
> Okay I'll be looking into it..
> Also I am looking forward for GSOC'23 for MIFOS too in the frontend fields. Surely working effectively with both the orgs by making good designs with premium feel.
> Regards,
> Inzemam
>
> On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com> wrote:
>>
>> Please make a set of suggestions or revise your designs based on input.
>>
>> Feel free to dive into this .
>>
>>
>>
>>
>>
>> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com> wrote:
>>>
>>> Hello James,
>>> When we are going to start the work or are we leaving it for future?
>>>
>>> Regards,
>>> Inzemam
>>>
>>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com> wrote:
>>>>
>>>> Hi James,
>>>> You are correct that we need to discuss more on the flows of events and placements. And I am also agree with the point that we can create a slack channel for this.
>>>> Also the code will be in simple html, css and js format so anyone can create/change the things easily. The design is looking fancy and complicated but the code is as smooth as butter. So need to worry about maintainance.
>>>> Regards,
>>>> Inzemamul Haq
>>>>
>>>>
>>>>
>>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com> wrote:
>>>>>
>>>>> Hi - Thank you for this.
>>>>>
>>>>> It's a very good conversation starter. I agreed with most of Javier's comments, which makes clear that we need to do a better job of "Explaining" and "Positioning".
>>>>>
>>>>> ASIDE: Javier - I invite you to write more such text and provide a top level set of bullet points that can be perhaps worked into the content.
>>>>>
>>>>> I think that the design colors are ok, the blue is appropriate for a financial system, meaning steady and trustworthy on the color wheel. Nice.
>>>>>
>>>>> We need more revamping of the content before we can properly do this design, so let's try to attack that problem.
>>>>>
>>>>> Here is a requirement that may not be clear to you:
>>>>> * Site should be very simple, easy to change by anyone opening up a Text Editor and modifying the HTML directly. e.g. use CSS styles and hopefully with names that make sense
>>>>> * Assume that you are gone and someone else has to modify just some text areas, adding content in specific sections.
>>>>> * Assume that no-one touches the website for over a year, maybe three years, and avoid content that can get stale.
>>>>>
>>>>>
>>>>> Message and Content issues:
>>>>>
>>>>> * Fineract is part of Apache and this is not always clear from the page today. Also, there is a common set of links and structure that you can find in other Apache projects. It is not a requirement to follow other Apache projects, but it would be useful to review them for commonalities:
>>>>> --> https://hadoop.apache.org
>>>>> --> https://airflow.apache.org
>>>>> --> https://kafka.apache.org
>>>>>
>>>>> * Note Community is there in each project. Check out the content that each project has.
>>>>>
>>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>> and this should then flow into the requirements for the other sections on the front page and then onto the wiki structure that we need
>>>>>
>>>>> * At this time Fineract-CN should probably not receive equal billing as the Fineract1.x releases it is still trying to get to a first release and fineract1.x is releasing on a regular basis with lots of activity. So, move Fineract-CN to a bottom section that's something about "Additional community technologies"
>>>>> I was and am a big fan of this framework, and I know this positioning is controversial for some, but until we get a release out and lots of active development and deployments, that project remains very much a side project of the community. It may become a very important thing, but for now we should reflect the reality which is that Fineract1.x is where the vast majority of the dev is going on, and the vast majority of the users are there.
>>>>>
>>>>>
>>>>> * We need to emphasize the key features of Fineract - there should be a summary of the system.
>>>>>
>>>>> This may require more chat and discussion on list or on slack and then development of a structure of content before you can really get a design.
>>>>>
>>>>> Thank you again.
>>>>>
>>>>> James Dailey
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>
>>>>>> Hello James,
>>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>>> Regards,
>>>>>> Inzemamul Haq
>>>>>>
>>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hello Javier,
>>>>>>> Thanks for your feedback. The points you mentioned, I'll implement them as you suggested now what I need is some more brief about the topics. This was the just an idea of how it'll look like surely we can change and add the things.
>>>>>>> As you mentioned in the last that it's a template but it's not. It's designed by me on the figma and the assets I used are open source so their will be no licencing issue. I always go for the development through scratch so no need to worry about that.
>>>>>>> Regards,
>>>>>>> Inzemam
>>>>>>>
>>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io> wrote:
>>>>>>>>
>>>>>>>> Hy Meta,
>>>>>>>>
>>>>>>>> Great job; I like the enhancement of the visuals and aesthetic in general, and it seems much more modern and suitable for the next stage of our community.
>>>>>>>>
>>>>>>>> My two cents:
>>>>>>>>
>>>>>>>> It is too linked with banks. Fineract has proved to be useful in other areas of the industry, not just banks. We need to convey that Fineract is a platform for many use cases. Using a mobile phone and a credit card as our visuals will put us in the last 20 years of the industry, and we are in the next 20 years. The images we need to use has to be conceptual, not rigid on old paradigms.
>>>>>>>> Fineract is a backend. Fineract will help the financial industry transcend from the old paradigm of "save deposit boxes" to the new paradigm of "Internet switches," allowing the users of financial institutions to move their assets worldwide quickly and safely. All purchases are now digital.
>>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the same exposure on our website as Fineract. Fineract CN it's still an experiment while most of our community depends on and uses Fineract. This must be clearly shown on the website and the real estate we dedicate to each one. Fineract CN wasn't the project incubated originally, and Fineract CN is not backward compatible with Fineract.
>>>>>>>> The project we are proud of: I will only use the project part if we get three Fortune 500 companies using Fineract. It will also open a new can of worms on which project gets selected and which criteria we should use, on top of getting the right set of approvals from them to be used as projects.
>>>>>>>> Last but not least, you used a template for the design. We need the license of that template that allows us to use it without limitations, and the template license is aligned with Apache 2.0.
>>>>>>>>
>>>>>>>> Javier
>>>>>>>>
>>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi James,
>>>>>>>>> Below is the drive link of complete page screenshot of APACHE FINERACT redesigned website. Please review and let me know if you have any questions or changes needed.
>>>>>>>>>
>>>>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Inzemamul Haq
>>>>>>>>>
>>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Okay lemme begin the work.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi
>>>>>>>>>>>>> I've been through the website and got it closely that what exact is there on the website. I'll create a static mockup for the website.
>>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone new or experienced first comes to the website got confused of what's happening and how things are going we can work upon it.
>>>>>>>>>>>>> Also I have a question are we going to implement blogger on that website? I have ability to work on static websites where the data comes from dynamic CMS.
>>>>>>>>>>>>> So I can work on tha too....
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Inzemamul Haq -
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Appreciate the response. This is revising our single page website for the project, so not an app. The content needs to be largely static or to pick up content we regularly post on blog. The current site is basic html. Just making sure we’re talking about the same thing.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Fineract.Apache.org
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a design lens, in my view. But, a good UIX process does start with who’s the audience and what’s their need when they land on the page.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>> First I will create mockup using the figma where we can get a better Idea of what exactly has to be happen. By the 16th of Feb I'll come up with a design also will share here in the thread and we can get comments in the meeting.
>>>>>>>>>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We have four people who said they'd like to be involved.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and then we can share back here on list and also hold a meeting on zoom in mid February.
>>>>>>>>>>>>>>>> Feb 16th?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Proposed Tasks:
>>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections you think belong being "brought over". compile a list of those pages. If none, great.
>>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the landing page (Meta Cyrus?)
>>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing pages that you like
>>>>>>>>>>>>>>>> 3) Provide a document outline of the high level functional description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence with links (james or ?)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>>>> James
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi James,
>>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and develop a good user reliable website.
>>>>>>>>>>>>>>>>> Where I can start??
>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> All -
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years since we did a clean sweep of it. We also have a front landing page at https://fineract.apache.org that could be better at communicating the project and community. Who wants to work on this with me?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Add blog feed
>>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>>>>>>>>>>>>>>> Include FAQ
>>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should have a top level split on the main page as well, or perhaps a separate landing page for FineractCN.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to show two levels):
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> FAQ
>>>>>>>>>>>>>>>>>> About Fineract
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> About FineractCN
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> TBD
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Project Management
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to be more prominent)
>>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at top)
>>>>>>>>>>>>>>>>>> Surveys
>>>>>>>>>>>>>>>>>> Release processes
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> How do I get involved?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Committer guides
>>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>>>>>>>>>>>>>>> Standards
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Documentation
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated documentation.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc) ... all go to blog
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>>>>>>>> FINERACT
>>>>>>>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> How-to articles
>>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sent from Gmail Mobile
>>
>> --
>> Sent from Gmail Mobile
--
Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by Inzemamul Haq <in...@gmail.com>.
Yep I'll be there in meet call.
On Sun, 30 Apr, 2023, 12:00 am James Dailey, <ja...@gmail.com> wrote:
> W can organize a zoom call. Then report back to the list here.
>
> I’ll suggest May 11th , 9am Pacific (PDT)
> I’ll send zoom link to anyone expressing interest.
>
>
>
> On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
> wrote:
>
>> Hello James,
>> Sorry for the late reply I was stuck in gsoc but I know I'll get rejected
>> so finally I am looking forward on the website as we dealt before.
>> Can we have a zoom call? So we can get an idea of what exactly we are
>> gonna place on the website as from the previous responses I am only getting
>> that some of the things should be changed or replaced but with whom I can't
>> get it.
>> Regards,
>> Inzemamul Haq
>>
>>
>> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> Hi Bruce - Good to know about those gaps in deployment and tools, but
>>> are those the only gaps in the documentation?
>>>
>>> So, question to you: is it already sufficiently clear on these topics:
>>> * explaining what the software does
>>> * explaining the architecture
>>> * explaining relationship between different components
>>> * what features are in each release
>>> * how to set up development environment
>>> * how to access APIs
>>> * how to find additional resources
>>>
>>> I did ask for 3-5 priority things, so please do try to identify where we
>>> start, even from your very long list or maybe adding to it, can we get your
>>> opinion on a few key things?
>>>
>>> What would you say is a priority?
>>>
>>> As a project, I think we need to simply and only offer one or two
>>> deployment options in our documentation, that way we can focus on getting
>>> those accurate and keeping them up to date. Others are of course free to
>>> offer their own improvements and alternatives.
>>>
>>> All - comments welcome.
>>>
>>> Thanks,
>>> James
>>>
>>>
>>>
>>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I hope this email finds you well. I wanted to share some observations
>>>> after going through the documentation for Fineract again.
>>>>
>>>> While the documentation provides an overview of deployment options here
>>>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>>>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>>>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>>>> guidance for users. There is also no deployment content on Kubernetes, AWS
>>>> and Google Cloud. Let's address this.
>>>>
>>>> Additionally, the Fineract Development section here
>>>> https://fineract.apache.org/docs/current/#_fineract_development_environment
>>>> appears to be incomplete and in need of further content to cover
>>>> important topics related to Fineract development. This section also
>>>> includes topics marked as "TBD" on the website, such as Docker, Docker
>>>> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
>>>> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
>>>> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
>>>> usage of various development tools like Brew for MacOS and Linux. I
>>>> propose that the community contibutes content for the following topics:
>>>>
>>>>
>>>> - Docker: how to install, run, and use Docker containers for
>>>> Fineract
>>>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>>>> containers for Fineract
>>>> - Podman: how to use Podman as an alternative to Docker for running
>>>> containers
>>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>>>> Kubernetes clusters on one's local machine
>>>> - IDE: how to choose and configure an IDE for Fineract development
>>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>>> Fineract
>>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>>> clusters
>>>> - Minikube: how to use Minikube to run a local Kubernetes cluster
>>>> for Fineract
>>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>>> cluster for Fineract
>>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>>> Fineract
>>>> - Helm Charts: how to use Helm Charts to package and deploy
>>>> Fineract applications on Kubernetes
>>>> - Tools: how to install and use various tools that can help one
>>>> with Fineract development
>>>> - Brew: how to install and use Brew for MacOS and Linux
>>>>
>>>> By actively addressing these gaps in the documentation, we can provide
>>>> valuable support to the Fineract community and further showcase the
>>>> flexibility and compatibility of Fineract with different technologies and
>>>> platforms.
>>>>
>>>> I look forward to collaborating with the community to contribute
>>>> content for these important topics and improve the overall documentation
>>>> for Fineract.
>>>>
>>>> Best Regards
>>>>
>>>> Bruce
>>>>
>>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Meta or Bruce - any updates?
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>>>> the previous points you and others mentioned..
>>>>>>
>>>>>>
>>>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I've started to change some of the structure of the wiki. I'm just
>>>>>>> trying to clean it up: Does anyone have an objection?
>>>>>>>
>>>>>>> * Noting where content is historical and deprecating it
>>>>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>>>>
>>>>>>> This is incremental.
>>>>>>>
>>>>>>> Inzemam - can you provide a new design to review taking on the
>>>>>>> feedback?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>> >
>>>>>>> > Okay I'll be looking into it..
>>>>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the
>>>>>>> frontend fields. Surely working effectively with both the orgs by making
>>>>>>> good designs with premium feel.
>>>>>>> > Regards,
>>>>>>> > Inzemam
>>>>>>> >
>>>>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>
>>>>>>> >> Please make a set of suggestions or revise your designs based on
>>>>>>> input.
>>>>>>> >>
>>>>>>> >> Feel free to dive into this .
>>>>>>> >>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>
>>>>>>> >>> Hello James,
>>>>>>> >>> When we are going to start the work or are we leaving it for
>>>>>>> future?
>>>>>>> >>>
>>>>>>> >>> Regards,
>>>>>>> >>> Inzemam
>>>>>>> >>>
>>>>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>
>>>>>>> >>>> Hi James,
>>>>>>> >>>> You are correct that we need to discuss more on the flows of
>>>>>>> events and placements. And I am also agree with the point that we can
>>>>>>> create a slack channel for this.
>>>>>>> >>>> Also the code will be in simple html, css and js format so
>>>>>>> anyone can create/change the things easily. The design is looking fancy and
>>>>>>> complicated but the code is as smooth as butter. So need to worry about
>>>>>>> maintainance.
>>>>>>> >>>> Regards,
>>>>>>> >>>> Inzemamul Haq
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>
>>>>>>> >>>>> Hi - Thank you for this.
>>>>>>> >>>>>
>>>>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>>>>> Javier's comments, which makes clear that we need to do a better job of
>>>>>>> "Explaining" and "Positioning".
>>>>>>> >>>>>
>>>>>>> >>>>> ASIDE: Javier - I invite you to write more such text and
>>>>>>> provide a top level set of bullet points that can be perhaps worked into
>>>>>>> the content.
>>>>>>> >>>>>
>>>>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>>>>> Nice.
>>>>>>> >>>>>
>>>>>>> >>>>> We need more revamping of the content before we can properly
>>>>>>> do this design, so let's try to attack that problem.
>>>>>>> >>>>>
>>>>>>> >>>>> Here is a requirement that may not be clear to you:
>>>>>>> >>>>> * Site should be very simple, easy to change by anyone opening
>>>>>>> up a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>>>>> hopefully with names that make sense
>>>>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>>>>> some text areas, adding content in specific sections.
>>>>>>> >>>>> * Assume that no-one touches the website for over a year,
>>>>>>> maybe three years, and avoid content that can get stale.
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>> Message and Content issues:
>>>>>>> >>>>>
>>>>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>>>>> the page today. Also, there is a common set of links and structure that you
>>>>>>> can find in other Apache projects. It is not a requirement to follow other
>>>>>>> Apache projects, but it would be useful to review them for commonalities:
>>>>>>> >>>>> --> https://hadoop.apache.org
>>>>>>> >>>>> --> https://airflow.apache.org
>>>>>>> >>>>> --> https://kafka.apache.org
>>>>>>> >>>>>
>>>>>>> >>>>> * Note Community is there in each project. Check out the
>>>>>>> content that each project has.
>>>>>>> >>>>>
>>>>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>>>> >>>>> and this should then flow into the requirements for the other
>>>>>>> sections on the front page and then onto the wiki structure that we need
>>>>>>> >>>>>
>>>>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>>>>> "Additional community technologies"
>>>>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>>>>> positioning is controversial for some, but until we get a release out and
>>>>>>> lots of active development and deployments, that project remains very much
>>>>>>> a side project of the community. It may become a very important thing, but
>>>>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>>>>> the vast majority of the dev is going on, and the vast majority of the
>>>>>>> users are there.
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>>>>> should be a summary of the system.
>>>>>>> >>>>>
>>>>>>> >>>>> This may require more chat and discussion on list or on slack
>>>>>>> and then development of a structure of content before you can really get a
>>>>>>> design.
>>>>>>> >>>>>
>>>>>>> >>>>> Thank you again.
>>>>>>> >>>>>
>>>>>>> >>>>> James Dailey
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>
>>>>>>> >>>>>> Hello James,
>>>>>>> >>>>>> Have you reviewed the website frame. Please share the
>>>>>>> feedback.
>>>>>>> >>>>>> Regards,
>>>>>>> >>>>>> Inzemamul Haq
>>>>>>> >>>>>>
>>>>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>
>>>>>>> >>>>>>> Hello Javier,
>>>>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>>>>> implement them as you suggested now what I need is some more brief about
>>>>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>>>>> change and add the things.
>>>>>>> >>>>>>> As you mentioned in the last that it's a template but it's
>>>>>>> not. It's designed by me on the figma and the assets I used are open source
>>>>>>> so their will be no licencing issue. I always go for the development
>>>>>>> through scratch so no need to worry about that.
>>>>>>> >>>>>>> Regards,
>>>>>>> >>>>>>> Inzemam
>>>>>>> >>>>>>>
>>>>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>>>>> javier@fiter.io> wrote:
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> Hy Meta,
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> Great job; I like the enhancement of the visuals and
>>>>>>> aesthetic in general, and it seems much more modern and suitable for the
>>>>>>> next stage of our community.
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> My two cents:
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be
>>>>>>> useful in other areas of the industry, not just banks. We need to convey
>>>>>>> that Fineract is a platform for many use cases. Using a mobile phone and a
>>>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>>>>> be conceptual, not rigid on old paradigms.
>>>>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>>>> purchases are now digital.
>>>>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have
>>>>>>> the same exposure on our website as Fineract. Fineract CN it's still an
>>>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>>>> CN is not backward compatible with Fineract.
>>>>>>> >>>>>>>> The project we are proud of: I will only use the project
>>>>>>> part if we get three Fortune 500 companies using Fineract. It will also
>>>>>>> open a new can of worms on which project gets selected and which criteria
>>>>>>> we should use, on top of getting the right set of approvals from them to be
>>>>>>> used as projects.
>>>>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>>>>> need the license of that template that allows us to use it without
>>>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> Javier
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> Hi James,
>>>>>>> >>>>>>>>> Below is the drive link of complete page screenshot of
>>>>>>> APACHE FINERACT redesigned website. Please review and let me know if you
>>>>>>> have any questions or changes needed.
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>>
>>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> Regards,
>>>>>>> >>>>>>>>> Inzemamul Haq
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>> +1
>>>>>>> >>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> Hi
>>>>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>>>>> what exact is there on the website. I'll create a static mockup for the
>>>>>>> website.
>>>>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>>>>> anyone new or experienced first comes to the website got confused of what's
>>>>>>> happening and how things are going we can work upon it.
>>>>>>> >>>>>>>>>>>>> Also I have a question are we going to implement
>>>>>>> blogger on that website? I have ability to work on static websites where
>>>>>>> the data comes from dynamic CMS.
>>>>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>>>>> >>>>>>>>>>>>> Regards,
>>>>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>>>>> page website for the project, so not an app. The content needs to be
>>>>>>> largely static or to pick up content we regularly post on blog. The current
>>>>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s
>>>>>>> needed is a design lens, in my view. But, a good UIX process does start
>>>>>>> with who’s the audience and what’s their need when they land on the page.
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>> Hi,
>>>>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we
>>>>>>> can get a better Idea of what exactly has to be happen. By the 16th of Feb
>>>>>>> I'll come up with a design also will share here in the thread and we can
>>>>>>> get comments in the meeting.
>>>>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>>>>> overall UI/UX
>>>>>>> >>>>>>>>>>>>>>> Regards,
>>>>>>> >>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>> >>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you.
>>>>>>> We have four people who said they'd like to be involved.
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>>>>> mid February.
>>>>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>>>> document:
>>>>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page
>>>>>>> in detail.
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where
>>>>>>> is there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find
>>>>>>> sections you think belong being "brought over". compile a list of those
>>>>>>> pages. If none, great.
>>>>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of
>>>>>>> the landing page (Meta Cyrus?)
>>>>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>>>>> landing pages that you like
>>>>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>>>> confluence with links (james or ?)
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow
>>>>>>> this thread.
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> thanks
>>>>>>> >>>>>>>>>>>>>>>> James
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>>>>> d@gwocu.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>>>>> and develop a good user reliable website.
>>>>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>>>>> >>>>>>>>>>>>>>>>> Regards,
>>>>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>> >>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> All -
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but
>>>>>>> it's been 3+ years since we did a clean sweep of it. We also have a front
>>>>>>> landing page at https://fineract.apache.org that could be better
>>>>>>> at communicating the project and community. Who wants to work on this with
>>>>>>> me?
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I
>>>>>>> think we should have a top level split on the main page as well, or perhaps
>>>>>>> a separate landing page for FineractCN.
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>>>>> how to show two levels):
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> TBD
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs
>>>>>>> to be more prominent)
>>>>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent
>>>>>>> at top)
>>>>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>>>> >>>>>>>>>>>>>>>>>> Standards
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically
>>>>>>> generated documentation.
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>>>>> etc) ... all go to blog
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> --
>>>>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> --
>>>>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>>>>> >>
>>>>>>> >> --
>>>>>>> >> Sent from Gmail Mobile
>>>>>>>
>>>>>> --
> Sent from Gmail Mobile
>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
W can organize a zoom call. Then report back to the list here.
I’ll suggest May 11th , 9am Pacific (PDT)
I’ll send zoom link to anyone expressing interest.
On Sat, Apr 29, 2023 at 8:33 AM Inzemamul Haq <in...@gmail.com>
wrote:
> Hello James,
> Sorry for the late reply I was stuck in gsoc but I know I'll get rejected
> so finally I am looking forward on the website as we dealt before.
> Can we have a zoom call? So we can get an idea of what exactly we are
> gonna place on the website as from the previous responses I am only getting
> that some of the things should be changed or replaced but with whom I can't
> get it.
> Regards,
> Inzemamul Haq
>
>
> On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com>
> wrote:
>
>> Hi Bruce - Good to know about those gaps in deployment and tools, but are
>> those the only gaps in the documentation?
>>
>> So, question to you: is it already sufficiently clear on these topics:
>> * explaining what the software does
>> * explaining the architecture
>> * explaining relationship between different components
>> * what features are in each release
>> * how to set up development environment
>> * how to access APIs
>> * how to find additional resources
>>
>> I did ask for 3-5 priority things, so please do try to identify where we
>> start, even from your very long list or maybe adding to it, can we get your
>> opinion on a few key things?
>>
>> What would you say is a priority?
>>
>> As a project, I think we need to simply and only offer one or two
>> deployment options in our documentation, that way we can focus on getting
>> those accurate and keeping them up to date. Others are of course free to
>> offer their own improvements and alternatives.
>>
>> All - comments welcome.
>>
>> Thanks,
>> James
>>
>>
>>
>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I hope this email finds you well. I wanted to share some observations
>>> after going through the documentation for Fineract again.
>>>
>>> While the documentation provides an overview of deployment options here
>>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>>> guidance for users. There is also no deployment content on Kubernetes, AWS
>>> and Google Cloud. Let's address this.
>>>
>>> Additionally, the Fineract Development section here
>>> https://fineract.apache.org/docs/current/#_fineract_development_environment
>>> appears to be incomplete and in need of further content to cover
>>> important topics related to Fineract development. This section also
>>> includes topics marked as "TBD" on the website, such as Docker, Docker
>>> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
>>> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
>>> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
>>> usage of various development tools like Brew for MacOS and Linux. I
>>> propose that the community contibutes content for the following topics:
>>>
>>>
>>> - Docker: how to install, run, and use Docker containers for
>>> Fineract
>>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>>> containers for Fineract
>>> - Podman: how to use Podman as an alternative to Docker for running
>>> containers
>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>>> Kubernetes clusters on one's local machine
>>> - IDE: how to choose and configure an IDE for Fineract development
>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>> Fineract
>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>> clusters
>>> - Minikube: how to use Minikube to run a local Kubernetes cluster
>>> for Fineract
>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>> cluster for Fineract
>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>> Fineract
>>> - Helm Charts: how to use Helm Charts to package and deploy Fineract
>>> applications on Kubernetes
>>> - Tools: how to install and use various tools that can help one with
>>> Fineract development
>>> - Brew: how to install and use Brew for MacOS and Linux
>>>
>>> By actively addressing these gaps in the documentation, we can provide
>>> valuable support to the Fineract community and further showcase the
>>> flexibility and compatibility of Fineract with different technologies and
>>> platforms.
>>>
>>> I look forward to collaborating with the community to contribute content
>>> for these important topics and improve the overall documentation for
>>> Fineract.
>>>
>>> Best Regards
>>>
>>> Bruce
>>>
>>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Meta or Bruce - any updates?
>>>>
>>>>
>>>>
>>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>>
>>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>>> the previous points you and others mentioned..
>>>>>
>>>>>
>>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> I've started to change some of the structure of the wiki. I'm just
>>>>>> trying to clean it up: Does anyone have an objection?
>>>>>>
>>>>>> * Noting where content is historical and deprecating it
>>>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>>>
>>>>>> This is incremental.
>>>>>>
>>>>>> Inzemam - can you provide a new design to review taking on the
>>>>>> feedback?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>> >
>>>>>> > Okay I'll be looking into it..
>>>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the
>>>>>> frontend fields. Surely working effectively with both the orgs by making
>>>>>> good designs with premium feel.
>>>>>> > Regards,
>>>>>> > Inzemam
>>>>>> >
>>>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>> >>
>>>>>> >> Please make a set of suggestions or revise your designs based on
>>>>>> input.
>>>>>> >>
>>>>>> >> Feel free to dive into this .
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>> >>>
>>>>>> >>> Hello James,
>>>>>> >>> When we are going to start the work or are we leaving it for
>>>>>> future?
>>>>>> >>>
>>>>>> >>> Regards,
>>>>>> >>> Inzemam
>>>>>> >>>
>>>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>>>> wrote:
>>>>>> >>>>
>>>>>> >>>> Hi James,
>>>>>> >>>> You are correct that we need to discuss more on the flows of
>>>>>> events and placements. And I am also agree with the point that we can
>>>>>> create a slack channel for this.
>>>>>> >>>> Also the code will be in simple html, css and js format so
>>>>>> anyone can create/change the things easily. The design is looking fancy and
>>>>>> complicated but the code is as smooth as butter. So need to worry about
>>>>>> maintainance.
>>>>>> >>>> Regards,
>>>>>> >>>> Inzemamul Haq
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>
>>>>>> >>>>> Hi - Thank you for this.
>>>>>> >>>>>
>>>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>>>> Javier's comments, which makes clear that we need to do a better job of
>>>>>> "Explaining" and "Positioning".
>>>>>> >>>>>
>>>>>> >>>>> ASIDE: Javier - I invite you to write more such text and
>>>>>> provide a top level set of bullet points that can be perhaps worked into
>>>>>> the content.
>>>>>> >>>>>
>>>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>>>> Nice.
>>>>>> >>>>>
>>>>>> >>>>> We need more revamping of the content before we can properly do
>>>>>> this design, so let's try to attack that problem.
>>>>>> >>>>>
>>>>>> >>>>> Here is a requirement that may not be clear to you:
>>>>>> >>>>> * Site should be very simple, easy to change by anyone opening
>>>>>> up a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>>>> hopefully with names that make sense
>>>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>>>> some text areas, adding content in specific sections.
>>>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>>>> three years, and avoid content that can get stale.
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> Message and Content issues:
>>>>>> >>>>>
>>>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>>>> the page today. Also, there is a common set of links and structure that you
>>>>>> can find in other Apache projects. It is not a requirement to follow other
>>>>>> Apache projects, but it would be useful to review them for commonalities:
>>>>>> >>>>> --> https://hadoop.apache.org
>>>>>> >>>>> --> https://airflow.apache.org
>>>>>> >>>>> --> https://kafka.apache.org
>>>>>> >>>>>
>>>>>> >>>>> * Note Community is there in each project. Check out the
>>>>>> content that each project has.
>>>>>> >>>>>
>>>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>>> >>>>> and this should then flow into the requirements for the other
>>>>>> sections on the front page and then onto the wiki structure that we need
>>>>>> >>>>>
>>>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>>>> "Additional community technologies"
>>>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>>>> positioning is controversial for some, but until we get a release out and
>>>>>> lots of active development and deployments, that project remains very much
>>>>>> a side project of the community. It may become a very important thing, but
>>>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>>>> the vast majority of the dev is going on, and the vast majority of the
>>>>>> users are there.
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>>>> should be a summary of the system.
>>>>>> >>>>>
>>>>>> >>>>> This may require more chat and discussion on list or on slack
>>>>>> and then development of a structure of content before you can really get a
>>>>>> design.
>>>>>> >>>>>
>>>>>> >>>>> Thank you again.
>>>>>> >>>>>
>>>>>> >>>>> James Dailey
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>
>>>>>> >>>>>> Hello James,
>>>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>>> >>>>>> Regards,
>>>>>> >>>>>> Inzemamul Haq
>>>>>> >>>>>>
>>>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>
>>>>>> >>>>>>> Hello Javier,
>>>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>>>> implement them as you suggested now what I need is some more brief about
>>>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>>>> change and add the things.
>>>>>> >>>>>>> As you mentioned in the last that it's a template but it's
>>>>>> not. It's designed by me on the figma and the assets I used are open source
>>>>>> so their will be no licencing issue. I always go for the development
>>>>>> through scratch so no need to worry about that.
>>>>>> >>>>>>> Regards,
>>>>>> >>>>>>> Inzemam
>>>>>> >>>>>>>
>>>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>>>> javier@fiter.io> wrote:
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Hy Meta,
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Great job; I like the enhancement of the visuals and
>>>>>> aesthetic in general, and it seems much more modern and suitable for the
>>>>>> next stage of our community.
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> My two cents:
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be
>>>>>> useful in other areas of the industry, not just banks. We need to convey
>>>>>> that Fineract is a platform for many use cases. Using a mobile phone and a
>>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>>>> be conceptual, not rigid on old paradigms.
>>>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>>> purchases are now digital.
>>>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have
>>>>>> the same exposure on our website as Fineract. Fineract CN it's still an
>>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>>> CN is not backward compatible with Fineract.
>>>>>> >>>>>>>> The project we are proud of: I will only use the project
>>>>>> part if we get three Fortune 500 companies using Fineract. It will also
>>>>>> open a new can of worms on which project gets selected and which criteria
>>>>>> we should use, on top of getting the right set of approvals from them to be
>>>>>> used as projects.
>>>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>>>> need the license of that template that allows us to use it without
>>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Javier
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> Hi James,
>>>>>> >>>>>>>>> Below is the drive link of complete page screenshot of
>>>>>> APACHE FINERACT redesigned website. Please review and let me know if you
>>>>>> have any questions or changes needed.
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>>
>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> Regards,
>>>>>> >>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>> +1
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> Hi
>>>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>>>> what exact is there on the website. I'll create a static mockup for the
>>>>>> website.
>>>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>>>> anyone new or experienced first comes to the website got confused of what's
>>>>>> happening and how things are going we can work upon it.
>>>>>> >>>>>>>>>>>>> Also I have a question are we going to implement
>>>>>> blogger on that website? I have ability to work on static websites where
>>>>>> the data comes from dynamic CMS.
>>>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>>>> >>>>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>>>> page website for the project, so not an app. The content needs to be
>>>>>> largely static or to pick up content we regularly post on blog. The current
>>>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>>>> is a design lens, in my view. But, a good UIX process does start with
>>>>>> who’s the audience and what’s their need when they land on the page.
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>> Hi,
>>>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we
>>>>>> can get a better Idea of what exactly has to be happen. By the 16th of Feb
>>>>>> I'll come up with a design also will share here in the thread and we can
>>>>>> get comments in the meeting.
>>>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>>>> overall UI/UX
>>>>>> >>>>>>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>>>> have four people who said they'd like to be involved.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>>>> mid February.
>>>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>>> document:
>>>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page
>>>>>> in detail.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where
>>>>>> is there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find
>>>>>> sections you think belong being "brought over". compile a list of those
>>>>>> pages. If none, great.
>>>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of
>>>>>> the landing page (Meta Cyrus?)
>>>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>>>> landing pages that you like
>>>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>>> confluence with links (james or ?)
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow
>>>>>> this thread.
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> thanks
>>>>>> >>>>>>>>>>>>>>>> James
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>>>> d@gwocu.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>>>> and develop a good user reliable website.
>>>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>>>> >>>>>>>>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>> >>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>> jamespdailey@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> All -
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>>>> landing page at https://fineract.apache.org that could be better at
>>>>>> communicating the project and community. Who wants to work on this with me?
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I
>>>>>> think we should have a top level split on the main page as well, or perhaps
>>>>>> a separate landing page for FineractCN.
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>>>> how to show two levels):
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> TBD
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs
>>>>>> to be more prominent)
>>>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent
>>>>>> at top)
>>>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>>> >>>>>>>>>>>>>>>>>> Standards
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically
>>>>>> generated documentation.
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>>>> etc) ... all go to blog
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> --
>>>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> --
>>>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>>>> >>
>>>>>> >> --
>>>>>> >> Sent from Gmail Mobile
>>>>>>
>>>>> --
Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by Inzemamul Haq <in...@gmail.com>.
Hello James,
Sorry for the late reply I was stuck in gsoc but I know I'll get rejected
so finally I am looking forward on the website as we dealt before.
Can we have a zoom call? So we can get an idea of what exactly we are gonna
place on the website as from the previous responses I am only getting that
some of the things should be changed or replaced but with whom I can't get
it.
Regards,
Inzemamul Haq
On Sun, 9 Apr, 2023, 12:16 am James Dailey, <ja...@gmail.com> wrote:
> Hi Bruce - Good to know about those gaps in deployment and tools, but are
> those the only gaps in the documentation?
>
> So, question to you: is it already sufficiently clear on these topics:
> * explaining what the software does
> * explaining the architecture
> * explaining relationship between different components
> * what features are in each release
> * how to set up development environment
> * how to access APIs
> * how to find additional resources
>
> I did ask for 3-5 priority things, so please do try to identify where we
> start, even from your very long list or maybe adding to it, can we get your
> opinion on a few key things?
>
> What would you say is a priority?
>
> As a project, I think we need to simply and only offer one or two
> deployment options in our documentation, that way we can focus on getting
> those accurate and keeping them up to date. Others are of course free to
> offer their own improvements and alternatives.
>
> All - comments welcome.
>
> Thanks,
> James
>
>
>
> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>
>> Hi,
>>
>> I hope this email finds you well. I wanted to share some observations
>> after going through the documentation for Fineract again.
>>
>> While the documentation provides an overview of deployment options here
>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>> guidance for users. There is also no deployment content on Kubernetes, AWS
>> and Google Cloud. Let's address this.
>>
>> Additionally, the Fineract Development section here
>> https://fineract.apache.org/docs/current/#_fineract_development_environment
>> appears to be incomplete and in need of further content to cover
>> important topics related to Fineract development. This section also
>> includes topics marked as "TBD" on the website, such as Docker, Docker
>> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
>> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
>> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
>> usage of various development tools like Brew for MacOS and Linux. I
>> propose that the community contibutes content for the following topics:
>>
>>
>> - Docker: how to install, run, and use Docker containers for Fineract
>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>> containers for Fineract
>> - Podman: how to use Podman as an alternative to Docker for running
>> containers
>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>> Kubernetes clusters on one's local machine
>> - IDE: how to choose and configure an IDE for Fineract development
>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>> - Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
>> - Minikube: how to use Minikube to run a local Kubernetes cluster for
>> Fineract
>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>> cluster for Fineract
>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>> Fineract
>> - Helm Charts: how to use Helm Charts to package and deploy Fineract
>> applications on Kubernetes
>> - Tools: how to install and use various tools that can help one with
>> Fineract development
>> - Brew: how to install and use Brew for MacOS and Linux
>>
>> By actively addressing these gaps in the documentation, we can provide
>> valuable support to the Fineract community and further showcase the
>> flexibility and compatibility of Fineract with different technologies and
>> platforms.
>>
>> I look forward to collaborating with the community to contribute content
>> for these important topics and improve the overall documentation for
>> Fineract.
>>
>> Best Regards
>>
>> Bruce
>>
>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Meta or Bruce - any updates?
>>>
>>>
>>>
>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>> the previous points you and others mentioned..
>>>>
>>>>
>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> I've started to change some of the structure of the wiki. I'm just
>>>>> trying to clean it up: Does anyone have an objection?
>>>>>
>>>>> * Noting where content is historical and deprecating it
>>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>>
>>>>> This is incremental.
>>>>>
>>>>> Inzemam - can you provide a new design to review taking on the
>>>>> feedback?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>> >
>>>>> > Okay I'll be looking into it..
>>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>>>>> fields. Surely working effectively with both the orgs by making good
>>>>> designs with premium feel.
>>>>> > Regards,
>>>>> > Inzemam
>>>>> >
>>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> Please make a set of suggestions or revise your designs based on
>>>>> input.
>>>>> >>
>>>>> >> Feel free to dive into this .
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>> >>>
>>>>> >>> Hello James,
>>>>> >>> When we are going to start the work or are we leaving it for
>>>>> future?
>>>>> >>>
>>>>> >>> Regards,
>>>>> >>> Inzemam
>>>>> >>>
>>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>>> wrote:
>>>>> >>>>
>>>>> >>>> Hi James,
>>>>> >>>> You are correct that we need to discuss more on the flows of
>>>>> events and placements. And I am also agree with the point that we can
>>>>> create a slack channel for this.
>>>>> >>>> Also the code will be in simple html, css and js format so anyone
>>>>> can create/change the things easily. The design is looking fancy and
>>>>> complicated but the code is as smooth as butter. So need to worry about
>>>>> maintainance.
>>>>> >>>> Regards,
>>>>> >>>> Inzemamul Haq
>>>>> >>>>
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>
>>>>> >>>>> Hi - Thank you for this.
>>>>> >>>>>
>>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>>> Javier's comments, which makes clear that we need to do a better job of
>>>>> "Explaining" and "Positioning".
>>>>> >>>>>
>>>>> >>>>> ASIDE: Javier - I invite you to write more such text and
>>>>> provide a top level set of bullet points that can be perhaps worked into
>>>>> the content.
>>>>> >>>>>
>>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>>> Nice.
>>>>> >>>>>
>>>>> >>>>> We need more revamping of the content before we can properly do
>>>>> this design, so let's try to attack that problem.
>>>>> >>>>>
>>>>> >>>>> Here is a requirement that may not be clear to you:
>>>>> >>>>> * Site should be very simple, easy to change by anyone opening
>>>>> up a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>>> hopefully with names that make sense
>>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>>> some text areas, adding content in specific sections.
>>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>>> three years, and avoid content that can get stale.
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> Message and Content issues:
>>>>> >>>>>
>>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>>> the page today. Also, there is a common set of links and structure that you
>>>>> can find in other Apache projects. It is not a requirement to follow other
>>>>> Apache projects, but it would be useful to review them for commonalities:
>>>>> >>>>> --> https://hadoop.apache.org
>>>>> >>>>> --> https://airflow.apache.org
>>>>> >>>>> --> https://kafka.apache.org
>>>>> >>>>>
>>>>> >>>>> * Note Community is there in each project. Check out the
>>>>> content that each project has.
>>>>> >>>>>
>>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>> >>>>> and this should then flow into the requirements for the other
>>>>> sections on the front page and then onto the wiki structure that we need
>>>>> >>>>>
>>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>>> "Additional community technologies"
>>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>>> positioning is controversial for some, but until we get a release out and
>>>>> lots of active development and deployments, that project remains very much
>>>>> a side project of the community. It may become a very important thing, but
>>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>>> the vast majority of the dev is going on, and the vast majority of the
>>>>> users are there.
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>>> should be a summary of the system.
>>>>> >>>>>
>>>>> >>>>> This may require more chat and discussion on list or on slack
>>>>> and then development of a structure of content before you can really get a
>>>>> design.
>>>>> >>>>>
>>>>> >>>>> Thank you again.
>>>>> >>>>>
>>>>> >>>>> James Dailey
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>
>>>>> >>>>>> Hello James,
>>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>> >>>>>> Regards,
>>>>> >>>>>> Inzemamul Haq
>>>>> >>>>>>
>>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>
>>>>> >>>>>>> Hello Javier,
>>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>>> implement them as you suggested now what I need is some more brief about
>>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>>> change and add the things.
>>>>> >>>>>>> As you mentioned in the last that it's a template but it's
>>>>> not. It's designed by me on the figma and the assets I used are open source
>>>>> so their will be no licencing issue. I always go for the development
>>>>> through scratch so no need to worry about that.
>>>>> >>>>>>> Regards,
>>>>> >>>>>>> Inzemam
>>>>> >>>>>>>
>>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>>> javier@fiter.io> wrote:
>>>>> >>>>>>>>
>>>>> >>>>>>>> Hy Meta,
>>>>> >>>>>>>>
>>>>> >>>>>>>> Great job; I like the enhancement of the visuals and
>>>>> aesthetic in general, and it seems much more modern and suitable for the
>>>>> next stage of our community.
>>>>> >>>>>>>>
>>>>> >>>>>>>> My two cents:
>>>>> >>>>>>>>
>>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful
>>>>> in other areas of the industry, not just banks. We need to convey that
>>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>>> be conceptual, not rigid on old paradigms.
>>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>> purchases are now digital.
>>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>> CN is not backward compatible with Fineract.
>>>>> >>>>>>>> The project we are proud of: I will only use the project part
>>>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>>>> new can of worms on which project gets selected and which criteria we
>>>>> should use, on top of getting the right set of approvals from them to be
>>>>> used as projects.
>>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>>> need the license of that template that allows us to use it without
>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>> >>>>>>>>
>>>>> >>>>>>>> Javier
>>>>> >>>>>>>>
>>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> Hi James,
>>>>> >>>>>>>>> Below is the drive link of complete page screenshot of
>>>>> APACHE FINERACT redesigned website. Please review and let me know if you
>>>>> have any questions or changes needed.
>>>>> >>>>>>>>>
>>>>> >>>>>>>>>
>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> Regards,
>>>>> >>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> +1
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> Hi
>>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>>> what exact is there on the website. I'll create a static mockup for the
>>>>> website.
>>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>>> anyone new or experienced first comes to the website got confused of what's
>>>>> happening and how things are going we can work upon it.
>>>>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger
>>>>> on that website? I have ability to work on static websites where the data
>>>>> comes from dynamic CMS.
>>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>>> >>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>>> page website for the project, so not an app. The content needs to be
>>>>> largely static or to pick up content we regularly post on blog. The current
>>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>>> is a design lens, in my view. But, a good UIX process does start with
>>>>> who’s the audience and what’s their need when they land on the page.
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> Hi,
>>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we
>>>>> can get a better Idea of what exactly has to be happen. By the 16th of Feb
>>>>> I'll come up with a design also will share here in the thread and we can
>>>>> get comments in the meeting.
>>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>>> overall UI/UX
>>>>> >>>>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>>> have four people who said they'd like to be involved.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>>> mid February.
>>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>> document:
>>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>>>> detail.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>>>>> there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find
>>>>> sections you think belong being "brought over". compile a list of those
>>>>> pages. If none, great.
>>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>>>> landing page (Meta Cyrus?)
>>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>>> landing pages that you like
>>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>> confluence with links (james or ?)
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>>>> thread.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> thanks
>>>>> >>>>>>>>>>>>>>>> James
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>>> d@gwocu.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>>> and develop a good user reliable website.
>>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>>> >>>>>>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> All -
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>>> landing page at https://fineract.apache.org that could be better at
>>>>> communicating the project and community. Who wants to work on this with me?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I
>>>>> think we should have a top level split on the main page as well, or perhaps
>>>>> a separate landing page for FineractCN.
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>>> how to show two levels):
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> TBD
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs
>>>>> to be more prominent)
>>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent
>>>>> at top)
>>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>> >>>>>>>>>>>>>>>>>> Standards
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>>>>> documentation.
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>>> etc) ... all go to blog
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> --
>>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> --
>>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>>> >>
>>>>> >> --
>>>>> >> Sent from Gmail Mobile
>>>>>
>>>>
Re: How To Spin Up Local Instance
Posted by VICTOR MANUEL ROMERO RODRIGUEZ <vi...@fintecheando.mx>.
Hello,
Fineract is now using Zulu 17 Alpine as as container
https://github.com/apache/fineract/blob/develop/custom/docker/build.gradle
3 months ago I wrote about the Quick (Non production) setup
https://github.com/openMF/mifos-x-containers
Regards
Víctor Romero
El mar, 13 jun 2023 a las 9:37, Rob Tompkins (<ch...@gmail.com>)
escribió:
> I would also wonder where you keep the source that backs the docs so that
> I can contribute there as I work my way through standing up a local env.
>
> Cheers,
> -ROb
>
> On Jun 12, 2023, at 1:36 PM, James Dailey <ja...@gmail.com> wrote:
>
> I should have started with:
>
> * This is a question we get a lot - how to get started as a developer
> * The advice we have given is to run Fineract via Docker-compose
>
> So, that should be straightforward and we should make sure this is up to
> date:
> https://hub.docker.com/r/apache/fineract
>
>
> On Mon, Jun 12, 2023 at 12:11 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> I don't think we need more than Docker to get most developers going.
>> Agreed?
>> (let's drop minikube or whatevers)
>>
>> and, what is the base of our current Docker? I proposed Alpine a few
>> years back, but cannot remember what we used. Can we get an update going?
>>
>> the documentation about this should be simple to follow
>>
>> Maybe we just list those other deployment ideas for "other ideas to do" -
>> more of an invitation than something that we support in our documentation.
>>
>> Any objection to those kinds of changes to the documentation ?
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: James Dailey <ja...@gmail.com>
>> Date: Sat, Apr 8, 2023 at 11:44 AM
>> Subject: Re: Website and Wiki for Fineract updates
>> To: <de...@fineract.apache.org>
>>
>>
>> Hi Bruce - Good to know about those gaps in deployment and tools, but are
>> those the only gaps in the documentation?
>>
>> So, question to you: is it already sufficiently clear on these topics:
>> * explaining what the software does
>> * explaining the architecture
>> * explaining relationship between different components
>> * what features are in each release
>> * how to set up development environment
>> * how to access APIs
>> * how to find additional resources
>>
>> I did ask for 3-5 priority things, so please do try to identify where we
>> start, even from your very long list or maybe adding to it, can we get your
>> opinion on a few key things?
>>
>> What would you say is a priority?
>>
>> As a project, I think we need to simply and only offer one or two
>> deployment options in our documentation, that way we can focus on getting
>> those accurate and keeping them up to date. Others are of course free to
>> offer their own improvements and alternatives.
>>
>> All - comments welcome.
>>
>> Thanks,
>> James
>>
>>
>>
>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I hope this email finds you well. I wanted to share some observations
>>> after going through the documentation for Fineract again.
>>>
>>> While the documentation provides an overview of deployment options here
>>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>>> guidance for users. There is also no deployment content on Kubernetes, AWS
>>> and Google Cloud. Let's address this.
>>>
>>> Additionally, the Fineract Development section here
>>> https://fineract.apache.org/docs/current/#_fineract_development_environment
>>> appears to be incomplete and in need of further content to cover
>>> important topics related to Fineract development. This section also
>>> includes topics marked as "TBD" on the website, such as Docker, Docker
>>> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
>>> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
>>> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
>>> usage of various development tools like Brew for MacOS and Linux. I
>>> propose that the community contibutes content for the following topics:
>>>
>>>
>>> - Docker: how to install, run, and use Docker containers for
>>> Fineract
>>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>>> containers for Fineract
>>> - Podman: how to use Podman as an alternative to Docker for running
>>> containers
>>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>>> Kubernetes clusters on one's local machine
>>> - IDE: how to choose and configure an IDE for Fineract development
>>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for
>>> Fineract
>>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>>> - Kubernetes: how to deploy and manage Fineract on Kubernetes
>>> clusters
>>> - Minikube: how to use Minikube to run a local Kubernetes cluster
>>> for Fineract
>>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>>> cluster for Fineract
>>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>>> Fineract
>>> - Helm Charts: how to use Helm Charts to package and deploy Fineract
>>> applications on Kubernetes
>>> - Tools: how to install and use various tools that can help one with
>>> Fineract development
>>> - Brew: how to install and use Brew for MacOS and Linux
>>>
>>>
>>> By actively addressing these gaps in the documentation, we can provide
>>> valuable support to the Fineract community and further showcase the
>>> flexibility and compatibility of Fineract with different technologies and
>>> platforms.
>>>
>>> I look forward to collaborating with the community to contribute content
>>> for these important topics and improve the overall documentation for
>>> Fineract.
>>>
>>> Best Regards
>>>
>>> Bruce
>>>
>>
>
Re: How To Spin Up Local Instance
Posted by Rob Tompkins <ch...@gmail.com>.
I would also wonder where you keep the source that backs the docs so that I can contribute there as I work my way through standing up a local env.
Cheers,
-ROb
> On Jun 12, 2023, at 1:36 PM, James Dailey <ja...@gmail.com> wrote:
>
> I should have started with:
>
> * This is a question we get a lot - how to get started as a developer
> * The advice we have given is to run Fineract via Docker-compose
>
> So, that should be straightforward and we should make sure this is up to date:
> https://hub.docker.com/r/apache/fineract
>
>
> On Mon, Jun 12, 2023 at 12:11 PM James Dailey <jamespdailey@gmail.com <ma...@gmail.com>> wrote:
>> I don't think we need more than Docker to get most developers going. Agreed?
>> (let's drop minikube or whatevers)
>>
>> and, what is the base of our current Docker? I proposed Alpine a few years back, but cannot remember what we used. Can we get an update going?
>>
>> the documentation about this should be simple to follow
>>
>> Maybe we just list those other deployment ideas for "other ideas to do" - more of an invitation than something that we support in our documentation.
>>
>> Any objection to those kinds of changes to the documentation ?
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: James Dailey <jamespdailey@gmail.com <ma...@gmail.com>>
>> Date: Sat, Apr 8, 2023 at 11:44 AM
>> Subject: Re: Website and Wiki for Fineract updates
>> To: <dev@fineract.apache.org <ma...@fineract.apache.org>>
>>
>>
>> Hi Bruce - Good to know about those gaps in deployment and tools, but are those the only gaps in the documentation?
>>
>> So, question to you: is it already sufficiently clear on these topics:
>> * explaining what the software does
>> * explaining the architecture
>> * explaining relationship between different components
>> * what features are in each release
>> * how to set up development environment
>> * how to access APIs
>> * how to find additional resources
>>
>> I did ask for 3-5 priority things, so please do try to identify where we start, even from your very long list or maybe adding to it, can we get your opinion on a few key things?
>>
>> What would you say is a priority?
>>
>> As a project, I think we need to simply and only offer one or two deployment options in our documentation, that way we can focus on getting those accurate and keeping them up to date. Others are of course free to offer their own improvements and alternatives.
>>
>> All - comments welcome.
>>
>> Thanks,
>> James
>>
>>
>>
>> On Sat, Apr 8, 2023 at 10:33 AM Bruce <brucetushabe@gmail.com <ma...@gmail.com>> wrote:
>>> Hi,
>>>
>>> I hope this email finds you well. I wanted to share some observations after going through the documentation for Fineract again.
>>>
>>> While the documentation provides an overview of deployment options here https://fineract.apache.org/docs/current/#_deployment , I noticed that several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss, Weblogic, and Payara, are marked as TBD, indicating a lack of content and guidance for users. There is also no deployment content on Kubernetes, AWS and Google Cloud. Let's address this.
>>>
>>> Additionally, the Fineract Development section here https://fineract.apache.org/docs/current/#_fineract_development_environment appears to be incomplete and in need of further content to cover important topics related to Fineract development. This section also includes topics marked as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher Docker Desktop, IDE selection and configuration (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and management, Minikube, Microk8s, K3d, Helm Charts, and installation and usage of various development tools like Brew for MacOS and Linux. I propose that the community contibutes content for the following topics:
>>>
>>>
>>> Docker: how to install, run, and use Docker containers for Fineract
>>> Docker Compose: how to use Docker Compose to orchestrate multiple containers for Fineract
>>> Podman: how to use Podman as an alternative to Docker for running containers
>>> Rancher Docker Desktop: how to use Rancher Docker Desktop to run Kubernetes clusters on one's local machine
>>> IDE: how to choose and configure an IDE for Fineract development
>>> IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
>>> Eclipse: how to set up and use Eclipse as an IDE for Fineract
>>> VSCode: how to set up and use VSCode as an IDE for Fineract
>>> Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
>>> Minikube: how to use Minikube to run a local Kubernetes cluster for Fineract
>>> Microk8s: how to use Microk8s to run a lightweight Kubernetes cluster for Fineract
>>> K3d: how to use K3d to run a Kubernetes cluster in Docker for Fineract
>>> Helm Charts: how to use Helm Charts to package and deploy Fineract applications on Kubernetes
>>> Tools: how to install and use various tools that can help one with Fineract development
>>> Brew: how to install and use Brew for MacOS and Linux
>>>
>>> By actively addressing these gaps in the documentation, we can provide valuable support to the Fineract community and further showcase the flexibility and compatibility of Fineract with different technologies and platforms.
>>>
>>> I look forward to collaborating with the community to contribute content for these important topics and improve the overall documentation for Fineract.
>>>
>>>
>>> Best Regards
>>>
>>> Bruce
>>>
Re: How To Spin Up Local Instance
Posted by James Dailey <ja...@gmail.com>.
I should have started with:
* This is a question we get a lot - how to get started as a developer
* The advice we have given is to run Fineract via Docker-compose
So, that should be straightforward and we should make sure this is up to
date:
https://hub.docker.com/r/apache/fineract
On Mon, Jun 12, 2023 at 12:11 PM James Dailey <ja...@gmail.com>
wrote:
> I don't think we need more than Docker to get most developers going.
> Agreed?
> (let's drop minikube or whatevers)
>
> and, what is the base of our current Docker? I proposed Alpine a few
> years back, but cannot remember what we used. Can we get an update going?
>
> the documentation about this should be simple to follow
>
> Maybe we just list those other deployment ideas for "other ideas to do" -
> more of an invitation than something that we support in our documentation.
>
> Any objection to those kinds of changes to the documentation ?
>
>
>
> ---------- Forwarded message ---------
> From: James Dailey <ja...@gmail.com>
> Date: Sat, Apr 8, 2023 at 11:44 AM
> Subject: Re: Website and Wiki for Fineract updates
> To: <de...@fineract.apache.org>
>
>
> Hi Bruce - Good to know about those gaps in deployment and tools, but are
> those the only gaps in the documentation?
>
> So, question to you: is it already sufficiently clear on these topics:
> * explaining what the software does
> * explaining the architecture
> * explaining relationship between different components
> * what features are in each release
> * how to set up development environment
> * how to access APIs
> * how to find additional resources
>
> I did ask for 3-5 priority things, so please do try to identify where we
> start, even from your very long list or maybe adding to it, can we get your
> opinion on a few key things?
>
> What would you say is a priority?
>
> As a project, I think we need to simply and only offer one or two
> deployment options in our documentation, that way we can focus on getting
> those accurate and keeping them up to date. Others are of course free to
> offer their own improvements and alternatives.
>
> All - comments welcome.
>
> Thanks,
> James
>
>
>
> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>
>> Hi,
>>
>> I hope this email finds you well. I wanted to share some observations
>> after going through the documentation for Fineract again.
>>
>> While the documentation provides an overview of deployment options here
>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>> guidance for users. There is also no deployment content on Kubernetes, AWS
>> and Google Cloud. Let's address this.
>>
>> Additionally, the Fineract Development section here
>> https://fineract.apache.org/docs/current/#_fineract_development_environment
>> appears to be incomplete and in need of further content to cover
>> important topics related to Fineract development. This section also
>> includes topics marked as "TBD" on the website, such as Docker, Docker
>> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
>> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
>> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
>> usage of various development tools like Brew for MacOS and Linux. I
>> propose that the community contibutes content for the following topics:
>>
>>
>> - Docker: how to install, run, and use Docker containers for Fineract
>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>> containers for Fineract
>> - Podman: how to use Podman as an alternative to Docker for running
>> containers
>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>> Kubernetes clusters on one's local machine
>> - IDE: how to choose and configure an IDE for Fineract development
>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>> - Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
>> - Minikube: how to use Minikube to run a local Kubernetes cluster for
>> Fineract
>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>> cluster for Fineract
>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>> Fineract
>> - Helm Charts: how to use Helm Charts to package and deploy Fineract
>> applications on Kubernetes
>> - Tools: how to install and use various tools that can help one with
>> Fineract development
>> - Brew: how to install and use Brew for MacOS and Linux
>>
>> By actively addressing these gaps in the documentation, we can provide
>> valuable support to the Fineract community and further showcase the
>> flexibility and compatibility of Fineract with different technologies and
>> platforms.
>>
>> I look forward to collaborating with the community to contribute content
>> for these important topics and improve the overall documentation for
>> Fineract.
>>
>> Best Regards
>>
>> Bruce
>>
>
Re: How To Spin Up Local Instance
Posted by John Gathogo <jo...@fiter.io>.
I support this 💯, docker should be the recommended (and supported)
deployment method. A financial institution interested in the other
deployment methods should have capacity to deploy and support them.
On Mon, Jun 12, 2023 at 10:11 PM James Dailey <ja...@gmail.com>
wrote:
> I don't think we need more than Docker to get most developers going.
> Agreed?
> (let's drop minikube or whatevers)
>
> and, what is the base of our current Docker? I proposed Alpine a few
> years back, but cannot remember what we used. Can we get an update going?
>
> the documentation about this should be simple to follow
>
> Maybe we just list those other deployment ideas for "other ideas to do" -
> more of an invitation than something that we support in our documentation.
>
> Any objection to those kinds of changes to the documentation ?
>
>
>
> ---------- Forwarded message ---------
> From: James Dailey <ja...@gmail.com>
> Date: Sat, Apr 8, 2023 at 11:44 AM
> Subject: Re: Website and Wiki for Fineract updates
> To: <de...@fineract.apache.org>
>
>
> Hi Bruce - Good to know about those gaps in deployment and tools, but are
> those the only gaps in the documentation?
>
> So, question to you: is it already sufficiently clear on these topics:
> * explaining what the software does
> * explaining the architecture
> * explaining relationship between different components
> * what features are in each release
> * how to set up development environment
> * how to access APIs
> * how to find additional resources
>
> I did ask for 3-5 priority things, so please do try to identify where we
> start, even from your very long list or maybe adding to it, can we get your
> opinion on a few key things?
>
> What would you say is a priority?
>
> As a project, I think we need to simply and only offer one or two
> deployment options in our documentation, that way we can focus on getting
> those accurate and keeping them up to date. Others are of course free to
> offer their own improvements and alternatives.
>
> All - comments welcome.
>
> Thanks,
> James
>
>
>
> On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
>
>> Hi,
>>
>> I hope this email finds you well. I wanted to share some observations
>> after going through the documentation for Fineract again.
>>
>> While the documentation provides an overview of deployment options here
>> https://fineract.apache.org/docs/current/#_deployment , I noticed that
>> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
>> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
>> guidance for users. There is also no deployment content on Kubernetes, AWS
>> and Google Cloud. Let's address this.
>>
>> Additionally, the Fineract Development section here
>> https://fineract.apache.org/docs/current/#_fineract_development_environment
>> appears to be incomplete and in need of further content to cover
>> important topics related to Fineract development. This section also
>> includes topics marked as "TBD" on the website, such as Docker, Docker
>> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
>> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
>> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
>> usage of various development tools like Brew for MacOS and Linux. I
>> propose that the community contibutes content for the following topics:
>>
>>
>> - Docker: how to install, run, and use Docker containers for Fineract
>> - Docker Compose: how to use Docker Compose to orchestrate multiple
>> containers for Fineract
>> - Podman: how to use Podman as an alternative to Docker for running
>> containers
>> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
>> Kubernetes clusters on one's local machine
>> - IDE: how to choose and configure an IDE for Fineract development
>> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
>> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
>> - VSCode: how to set up and use VSCode as an IDE for Fineract
>> - Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
>> - Minikube: how to use Minikube to run a local Kubernetes cluster for
>> Fineract
>> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
>> cluster for Fineract
>> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
>> Fineract
>> - Helm Charts: how to use Helm Charts to package and deploy Fineract
>> applications on Kubernetes
>> - Tools: how to install and use various tools that can help one with
>> Fineract development
>> - Brew: how to install and use Brew for MacOS and Linux
>>
>> By actively addressing these gaps in the documentation, we can provide
>> valuable support to the Fineract community and further showcase the
>> flexibility and compatibility of Fineract with different technologies and
>> platforms.
>>
>> I look forward to collaborating with the community to contribute content
>> for these important topics and improve the overall documentation for
>> Fineract.
>>
>> Best Regards
>>
>> Bruce
>>
>> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Meta or Bruce - any updates?
>>>
>>>
>>>
>>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>>> Yep I'll be sharing the new design in which I hage taken care of all
>>>> the previous points you and others mentioned..
>>>>
>>>>
>>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> I've started to change some of the structure of the wiki. I'm just
>>>>> trying to clean it up: Does anyone have an objection?
>>>>>
>>>>> * Noting where content is historical and deprecating it
>>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>>
>>>>> This is incremental.
>>>>>
>>>>> Inzemam - can you provide a new design to review taking on the
>>>>> feedback?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>> >
>>>>> > Okay I'll be looking into it..
>>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>>>>> fields. Surely working effectively with both the orgs by making good
>>>>> designs with premium feel.
>>>>> > Regards,
>>>>> > Inzemam
>>>>> >
>>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> Please make a set of suggestions or revise your designs based on
>>>>> input.
>>>>> >>
>>>>> >> Feel free to dive into this .
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>> >>>
>>>>> >>> Hello James,
>>>>> >>> When we are going to start the work or are we leaving it for
>>>>> future?
>>>>> >>>
>>>>> >>> Regards,
>>>>> >>> Inzemam
>>>>> >>>
>>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>>> wrote:
>>>>> >>>>
>>>>> >>>> Hi James,
>>>>> >>>> You are correct that we need to discuss more on the flows of
>>>>> events and placements. And I am also agree with the point that we can
>>>>> create a slack channel for this.
>>>>> >>>> Also the code will be in simple html, css and js format so anyone
>>>>> can create/change the things easily. The design is looking fancy and
>>>>> complicated but the code is as smooth as butter. So need to worry about
>>>>> maintainance.
>>>>> >>>> Regards,
>>>>> >>>> Inzemamul Haq
>>>>> >>>>
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>
>>>>> >>>>> Hi - Thank you for this.
>>>>> >>>>>
>>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>>> Javier's comments, which makes clear that we need to do a better job of
>>>>> "Explaining" and "Positioning".
>>>>> >>>>>
>>>>> >>>>> ASIDE: Javier - I invite you to write more such text and
>>>>> provide a top level set of bullet points that can be perhaps worked into
>>>>> the content.
>>>>> >>>>>
>>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>>> Nice.
>>>>> >>>>>
>>>>> >>>>> We need more revamping of the content before we can properly do
>>>>> this design, so let's try to attack that problem.
>>>>> >>>>>
>>>>> >>>>> Here is a requirement that may not be clear to you:
>>>>> >>>>> * Site should be very simple, easy to change by anyone opening
>>>>> up a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>>> hopefully with names that make sense
>>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>>> some text areas, adding content in specific sections.
>>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>>> three years, and avoid content that can get stale.
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> Message and Content issues:
>>>>> >>>>>
>>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>>> the page today. Also, there is a common set of links and structure that you
>>>>> can find in other Apache projects. It is not a requirement to follow other
>>>>> Apache projects, but it would be useful to review them for commonalities:
>>>>> >>>>> --> https://hadoop.apache.org
>>>>> >>>>> --> https://airflow.apache.org
>>>>> >>>>> --> https://kafka.apache.org
>>>>> >>>>>
>>>>> >>>>> * Note Community is there in each project. Check out the
>>>>> content that each project has.
>>>>> >>>>>
>>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>> >>>>> and this should then flow into the requirements for the other
>>>>> sections on the front page and then onto the wiki structure that we need
>>>>> >>>>>
>>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>>> "Additional community technologies"
>>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>>> positioning is controversial for some, but until we get a release out and
>>>>> lots of active development and deployments, that project remains very much
>>>>> a side project of the community. It may become a very important thing, but
>>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>>> the vast majority of the dev is going on, and the vast majority of the
>>>>> users are there.
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>>> should be a summary of the system.
>>>>> >>>>>
>>>>> >>>>> This may require more chat and discussion on list or on slack
>>>>> and then development of a structure of content before you can really get a
>>>>> design.
>>>>> >>>>>
>>>>> >>>>> Thank you again.
>>>>> >>>>>
>>>>> >>>>> James Dailey
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>
>>>>> >>>>>> Hello James,
>>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>> >>>>>> Regards,
>>>>> >>>>>> Inzemamul Haq
>>>>> >>>>>>
>>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>
>>>>> >>>>>>> Hello Javier,
>>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>>> implement them as you suggested now what I need is some more brief about
>>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>>> change and add the things.
>>>>> >>>>>>> As you mentioned in the last that it's a template but it's
>>>>> not. It's designed by me on the figma and the assets I used are open source
>>>>> so their will be no licencing issue. I always go for the development
>>>>> through scratch so no need to worry about that.
>>>>> >>>>>>> Regards,
>>>>> >>>>>>> Inzemam
>>>>> >>>>>>>
>>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>>> javier@fiter.io> wrote:
>>>>> >>>>>>>>
>>>>> >>>>>>>> Hy Meta,
>>>>> >>>>>>>>
>>>>> >>>>>>>> Great job; I like the enhancement of the visuals and
>>>>> aesthetic in general, and it seems much more modern and suitable for the
>>>>> next stage of our community.
>>>>> >>>>>>>>
>>>>> >>>>>>>> My two cents:
>>>>> >>>>>>>>
>>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful
>>>>> in other areas of the industry, not just banks. We need to convey that
>>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>>> be conceptual, not rigid on old paradigms.
>>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>> purchases are now digital.
>>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>> CN is not backward compatible with Fineract.
>>>>> >>>>>>>> The project we are proud of: I will only use the project part
>>>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>>>> new can of worms on which project gets selected and which criteria we
>>>>> should use, on top of getting the right set of approvals from them to be
>>>>> used as projects.
>>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>>> need the license of that template that allows us to use it without
>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>> >>>>>>>>
>>>>> >>>>>>>> Javier
>>>>> >>>>>>>>
>>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> Hi James,
>>>>> >>>>>>>>> Below is the drive link of complete page screenshot of
>>>>> APACHE FINERACT redesigned website. Please review and let me know if you
>>>>> have any questions or changes needed.
>>>>> >>>>>>>>>
>>>>> >>>>>>>>>
>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> Regards,
>>>>> >>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> +1
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> Hi
>>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>>> what exact is there on the website. I'll create a static mockup for the
>>>>> website.
>>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>>> anyone new or experienced first comes to the website got confused of what's
>>>>> happening and how things are going we can work upon it.
>>>>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger
>>>>> on that website? I have ability to work on static websites where the data
>>>>> comes from dynamic CMS.
>>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>>> >>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>>> page website for the project, so not an app. The content needs to be
>>>>> largely static or to pick up content we regularly post on blog. The current
>>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>>> is a design lens, in my view. But, a good UIX process does start with
>>>>> who’s the audience and what’s their need when they land on the page.
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> Hi,
>>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we
>>>>> can get a better Idea of what exactly has to be happen. By the 16th of Feb
>>>>> I'll come up with a design also will share here in the thread and we can
>>>>> get comments in the meeting.
>>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>>> overall UI/UX
>>>>> >>>>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>>> have four people who said they'd like to be involved.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>>> mid February.
>>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>> document:
>>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>>>> detail.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>>>>> there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find
>>>>> sections you think belong being "brought over". compile a list of those
>>>>> pages. If none, great.
>>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>>>> landing page (Meta Cyrus?)
>>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>>> landing pages that you like
>>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>> confluence with links (james or ?)
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>>>> thread.
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> thanks
>>>>> >>>>>>>>>>>>>>>> James
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>>> d@gwocu.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>> inzemamhaq05@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>>> and develop a good user reliable website.
>>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>>> >>>>>>>>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>> >>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>> jamespdailey@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> All -
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>>> landing page at https://fineract.apache.org that could be better at
>>>>> communicating the project and community. Who wants to work on this with me?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I
>>>>> think we should have a top level split on the main page as well, or perhaps
>>>>> a separate landing page for FineractCN.
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> ---
>>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>>> how to show two levels):
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> TBD
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs
>>>>> to be more prominent)
>>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent
>>>>> at top)
>>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>> >>>>>>>>>>>>>>>>>> Standards
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>>>>> documentation.
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>>> etc) ... all go to blog
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> --
>>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> --
>>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>>> >>
>>>>> >> --
>>>>> >> Sent from Gmail Mobile
>>>>>
>>>>
How To Spin Up Local Instance
Posted by James Dailey <ja...@gmail.com>.
I don't think we need more than Docker to get most developers going.
Agreed?
(let's drop minikube or whatevers)
and, what is the base of our current Docker? I proposed Alpine a few years
back, but cannot remember what we used. Can we get an update going?
the documentation about this should be simple to follow
Maybe we just list those other deployment ideas for "other ideas to do" -
more of an invitation than something that we support in our documentation.
Any objection to those kinds of changes to the documentation ?
---------- Forwarded message ---------
From: James Dailey <ja...@gmail.com>
Date: Sat, Apr 8, 2023 at 11:44 AM
Subject: Re: Website and Wiki for Fineract updates
To: <de...@fineract.apache.org>
Hi Bruce - Good to know about those gaps in deployment and tools, but are
those the only gaps in the documentation?
So, question to you: is it already sufficiently clear on these topics:
* explaining what the software does
* explaining the architecture
* explaining relationship between different components
* what features are in each release
* how to set up development environment
* how to access APIs
* how to find additional resources
I did ask for 3-5 priority things, so please do try to identify where we
start, even from your very long list or maybe adding to it, can we get your
opinion on a few key things?
What would you say is a priority?
As a project, I think we need to simply and only offer one or two
deployment options in our documentation, that way we can focus on getting
those accurate and keeping them up to date. Others are of course free to
offer their own improvements and alternatives.
All - comments welcome.
Thanks,
James
On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
> Hi,
>
> I hope this email finds you well. I wanted to share some observations
> after going through the documentation for Fineract again.
>
> While the documentation provides an overview of deployment options here
> https://fineract.apache.org/docs/current/#_deployment , I noticed that
> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
> guidance for users. There is also no deployment content on Kubernetes, AWS
> and Google Cloud. Let's address this.
>
> Additionally, the Fineract Development section here
> https://fineract.apache.org/docs/current/#_fineract_development_environment
> appears to be incomplete and in need of further content to cover
> important topics related to Fineract development. This section also
> includes topics marked as "TBD" on the website, such as Docker, Docker
> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
> usage of various development tools like Brew for MacOS and Linux. I
> propose that the community contibutes content for the following topics:
>
>
> - Docker: how to install, run, and use Docker containers for Fineract
> - Docker Compose: how to use Docker Compose to orchestrate multiple
> containers for Fineract
> - Podman: how to use Podman as an alternative to Docker for running
> containers
> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
> Kubernetes clusters on one's local machine
> - IDE: how to choose and configure an IDE for Fineract development
> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
> - VSCode: how to set up and use VSCode as an IDE for Fineract
> - Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
> - Minikube: how to use Minikube to run a local Kubernetes cluster for
> Fineract
> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
> cluster for Fineract
> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
> Fineract
> - Helm Charts: how to use Helm Charts to package and deploy Fineract
> applications on Kubernetes
> - Tools: how to install and use various tools that can help one with
> Fineract development
> - Brew: how to install and use Brew for MacOS and Linux
>
> By actively addressing these gaps in the documentation, we can provide
> valuable support to the Fineract community and further showcase the
> flexibility and compatibility of Fineract with different technologies and
> platforms.
>
> I look forward to collaborating with the community to contribute content
> for these important topics and improve the overall documentation for
> Fineract.
>
> Best Regards
>
> Bruce
>
> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> Meta or Bruce - any updates?
>>
>>
>>
>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>> wrote:
>>
>>> Yep I'll be sharing the new design in which I hage taken care of all the
>>> previous points you and others mentioned..
>>>
>>>
>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> I've started to change some of the structure of the wiki. I'm just
>>>> trying to clean it up: Does anyone have an objection?
>>>>
>>>> * Noting where content is historical and deprecating it
>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>
>>>> This is incremental.
>>>>
>>>> Inzemam - can you provide a new design to review taking on the feedback?
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>> >
>>>> > Okay I'll be looking into it..
>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>>>> fields. Surely working effectively with both the orgs by making good
>>>> designs with premium feel.
>>>> > Regards,
>>>> > Inzemam
>>>> >
>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> Please make a set of suggestions or revise your designs based on
>>>> input.
>>>> >>
>>>> >> Feel free to dive into this .
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>> >>>
>>>> >>> Hello James,
>>>> >>> When we are going to start the work or are we leaving it for future?
>>>> >>>
>>>> >>> Regards,
>>>> >>> Inzemam
>>>> >>>
>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>> wrote:
>>>> >>>>
>>>> >>>> Hi James,
>>>> >>>> You are correct that we need to discuss more on the flows of
>>>> events and placements. And I am also agree with the point that we can
>>>> create a slack channel for this.
>>>> >>>> Also the code will be in simple html, css and js format so anyone
>>>> can create/change the things easily. The design is looking fancy and
>>>> complicated but the code is as smooth as butter. So need to worry about
>>>> maintainance.
>>>> >>>> Regards,
>>>> >>>> Inzemamul Haq
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>
>>>> >>>>> Hi - Thank you for this.
>>>> >>>>>
>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>> Javier's comments, which makes clear that we need to do a better job of
>>>> "Explaining" and "Positioning".
>>>> >>>>>
>>>> >>>>> ASIDE: Javier - I invite you to write more such text and provide
>>>> a top level set of bullet points that can be perhaps worked into the
>>>> content.
>>>> >>>>>
>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>> Nice.
>>>> >>>>>
>>>> >>>>> We need more revamping of the content before we can properly do
>>>> this design, so let's try to attack that problem.
>>>> >>>>>
>>>> >>>>> Here is a requirement that may not be clear to you:
>>>> >>>>> * Site should be very simple, easy to change by anyone opening up
>>>> a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>> hopefully with names that make sense
>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>> some text areas, adding content in specific sections.
>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>> three years, and avoid content that can get stale.
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> Message and Content issues:
>>>> >>>>>
>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>> the page today. Also, there is a common set of links and structure that you
>>>> can find in other Apache projects. It is not a requirement to follow other
>>>> Apache projects, but it would be useful to review them for commonalities:
>>>> >>>>> --> https://hadoop.apache.org
>>>> >>>>> --> https://airflow.apache.org
>>>> >>>>> --> https://kafka.apache.org
>>>> >>>>>
>>>> >>>>> * Note Community is there in each project. Check out the content
>>>> that each project has.
>>>> >>>>>
>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>> >>>>> and this should then flow into the requirements for the other
>>>> sections on the front page and then onto the wiki structure that we need
>>>> >>>>>
>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>> "Additional community technologies"
>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>> positioning is controversial for some, but until we get a release out and
>>>> lots of active development and deployments, that project remains very much
>>>> a side project of the community. It may become a very important thing, but
>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>> the vast majority of the dev is going on, and the vast majority of the
>>>> users are there.
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>> should be a summary of the system.
>>>> >>>>>
>>>> >>>>> This may require more chat and discussion on list or on slack and
>>>> then development of a structure of content before you can really get a
>>>> design.
>>>> >>>>>
>>>> >>>>> Thank you again.
>>>> >>>>>
>>>> >>>>> James Dailey
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>
>>>> >>>>>> Hello James,
>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>> >>>>>> Regards,
>>>> >>>>>> Inzemamul Haq
>>>> >>>>>>
>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>
>>>> >>>>>>> Hello Javier,
>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>> implement them as you suggested now what I need is some more brief about
>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>> change and add the things.
>>>> >>>>>>> As you mentioned in the last that it's a template but it's not.
>>>> It's designed by me on the figma and the assets I used are open source so
>>>> their will be no licencing issue. I always go for the development through
>>>> scratch so no need to worry about that.
>>>> >>>>>>> Regards,
>>>> >>>>>>> Inzemam
>>>> >>>>>>>
>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>> javier@fiter.io> wrote:
>>>> >>>>>>>>
>>>> >>>>>>>> Hy Meta,
>>>> >>>>>>>>
>>>> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic
>>>> in general, and it seems much more modern and suitable for the next stage
>>>> of our community.
>>>> >>>>>>>>
>>>> >>>>>>>> My two cents:
>>>> >>>>>>>>
>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful
>>>> in other areas of the industry, not just banks. We need to convey that
>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>> credit card as our visuals will put us in the last 20 years of the
>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>> be conceptual, not rigid on old paradigms.
>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>> paradigm of "Internet switches," allowing the users of financial
>>>> institutions to move their assets worldwide quickly and safely. All
>>>> purchases are now digital.
>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>> experiment while most of our community depends on and uses Fineract. This
>>>> must be clearly shown on the website and the real estate we dedicate to
>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>> CN is not backward compatible with Fineract.
>>>> >>>>>>>> The project we are proud of: I will only use the project part
>>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>>> new can of worms on which project gets selected and which criteria we
>>>> should use, on top of getting the right set of approvals from them to be
>>>> used as projects.
>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>> need the license of that template that allows us to use it without
>>>> limitations, and the template license is aligned with Apache 2.0.
>>>> >>>>>>>>
>>>> >>>>>>>> Javier
>>>> >>>>>>>>
>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>
>>>> >>>>>>>>> Hi James,
>>>> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
>>>> FINERACT redesigned website. Please review and let me know if you have any
>>>> questions or changes needed.
>>>> >>>>>>>>>
>>>> >>>>>>>>>
>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>> >>>>>>>>>
>>>> >>>>>>>>> Regards,
>>>> >>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>
>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>> +1
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> Hi
>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>> what exact is there on the website. I'll create a static mockup for the
>>>> website.
>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>> anyone new or experienced first comes to the website got confused of what's
>>>> happening and how things are going we can work upon it.
>>>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger
>>>> on that website? I have ability to work on static websites where the data
>>>> comes from dynamic CMS.
>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>> >>>>>>>>>>>>> Regards,
>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>> page website for the project, so not an app. The content needs to be
>>>> largely static or to pick up content we regularly post on blog. The current
>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>> is a design lens, in my view. But, a good UIX process does start with
>>>> who’s the audience and what’s their need when they land on the page.
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>> Hi,
>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
>>>> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
>>>> come up with a design also will share here in the thread and we can get
>>>> comments in the meeting.
>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>> overall UI/UX
>>>> >>>>>>>>>>>>>>> Regards,
>>>> >>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>> have four people who said they'd like to be involved.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>> mid February.
>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>> document:
>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>>> detail.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>>>> there a gap in content (Bruce, Tekle? - start a thread about this)
>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
>>>> you think belong being "brought over". compile a list of those pages. If
>>>> none, great.
>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>>> landing page (Meta Cyrus?)
>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>> landing pages that you like
>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>> confluence with links (james or ?)
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>>> thread.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> thanks
>>>> >>>>>>>>>>>>>>>> James
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>> d@gwocu.com> wrote:
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>> and develop a good user reliable website.
>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>> >>>>>>>>>>>>>>>>> Regards,
>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> All -
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>> landing page at https://fineract.apache.org that could be better at
>>>> communicating the project and community. Who wants to work on this with me?
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>> >>>>>>>>>>>>>>>>>> ---
>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think
>>>> we should have a top level split on the main page as well, or perhaps a
>>>> separate landing page for FineractCN.
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> ---
>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>> how to show two levels):
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> TBD
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to
>>>> be more prominent)
>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
>>>> top)
>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>> >>>>>>>>>>>>>>>>>> Standards
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>>>> documentation.
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>> etc) ... all go to blog
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> --
>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> --
>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>> >>
>>>> >> --
>>>> >> Sent from Gmail Mobile
>>>>
>>>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Hi Bruce - Good to know about those gaps in deployment and tools, but are
those the only gaps in the documentation?
So, question to you: is it already sufficiently clear on these topics:
* explaining what the software does
* explaining the architecture
* explaining relationship between different components
* what features are in each release
* how to set up development environment
* how to access APIs
* how to find additional resources
I did ask for 3-5 priority things, so please do try to identify where we
start, even from your very long list or maybe adding to it, can we get your
opinion on a few key things?
What would you say is a priority?
As a project, I think we need to simply and only offer one or two
deployment options in our documentation, that way we can focus on getting
those accurate and keeping them up to date. Others are of course free to
offer their own improvements and alternatives.
All - comments welcome.
Thanks,
James
On Sat, Apr 8, 2023 at 10:33 AM Bruce <br...@gmail.com> wrote:
> Hi,
>
> I hope this email finds you well. I wanted to share some observations
> after going through the documentation for Fineract again.
>
> While the documentation provides an overview of deployment options here
> https://fineract.apache.org/docs/current/#_deployment , I noticed that
> several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
> Weblogic, and Payara, are marked as TBD, indicating a lack of content and
> guidance for users. There is also no deployment content on Kubernetes, AWS
> and Google Cloud. Let's address this.
>
> Additionally, the Fineract Development section here
> https://fineract.apache.org/docs/current/#_fineract_development_environment
> appears to be incomplete and in need of further content to cover
> important topics related to Fineract development. This section also
> includes topics marked as "TBD" on the website, such as Docker, Docker
> Compose, Podman, Rancher Docker Desktop, IDE selection and configuration
> (including IntelliJ, Eclipse, and VSCode), Kubernetes deployment and
> management, Minikube, Microk8s, K3d, Helm Charts, and installation and
> usage of various development tools like Brew for MacOS and Linux. I
> propose that the community contibutes content for the following topics:
>
>
> - Docker: how to install, run, and use Docker containers for Fineract
> - Docker Compose: how to use Docker Compose to orchestrate multiple
> containers for Fineract
> - Podman: how to use Podman as an alternative to Docker for running
> containers
> - Rancher Docker Desktop: how to use Rancher Docker Desktop to run
> Kubernetes clusters on one's local machine
> - IDE: how to choose and configure an IDE for Fineract development
> - IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
> - Eclipse: how to set up and use Eclipse as an IDE for Fineract
> - VSCode: how to set up and use VSCode as an IDE for Fineract
> - Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
> - Minikube: how to use Minikube to run a local Kubernetes cluster for
> Fineract
> - Microk8s: how to use Microk8s to run a lightweight Kubernetes
> cluster for Fineract
> - K3d: how to use K3d to run a Kubernetes cluster in Docker for
> Fineract
> - Helm Charts: how to use Helm Charts to package and deploy Fineract
> applications on Kubernetes
> - Tools: how to install and use various tools that can help one with
> Fineract development
> - Brew: how to install and use Brew for MacOS and Linux
>
> By actively addressing these gaps in the documentation, we can provide
> valuable support to the Fineract community and further showcase the
> flexibility and compatibility of Fineract with different technologies and
> platforms.
>
> I look forward to collaborating with the community to contribute content
> for these important topics and improve the overall documentation for
> Fineract.
>
> Best Regards
>
> Bruce
>
> On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> Meta or Bruce - any updates?
>>
>>
>>
>> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
>> wrote:
>>
>>> Yep I'll be sharing the new design in which I hage taken care of all the
>>> previous points you and others mentioned..
>>>
>>>
>>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> I've started to change some of the structure of the wiki. I'm just
>>>> trying to clean it up: Does anyone have an objection?
>>>>
>>>> * Noting where content is historical and deprecating it
>>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>>
>>>> This is incremental.
>>>>
>>>> Inzemam - can you provide a new design to review taking on the feedback?
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>> >
>>>> > Okay I'll be looking into it..
>>>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>>>> fields. Surely working effectively with both the orgs by making good
>>>> designs with premium feel.
>>>> > Regards,
>>>> > Inzemam
>>>> >
>>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> Please make a set of suggestions or revise your designs based on
>>>> input.
>>>> >>
>>>> >> Feel free to dive into this .
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>> >>>
>>>> >>> Hello James,
>>>> >>> When we are going to start the work or are we leaving it for future?
>>>> >>>
>>>> >>> Regards,
>>>> >>> Inzemam
>>>> >>>
>>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>>> wrote:
>>>> >>>>
>>>> >>>> Hi James,
>>>> >>>> You are correct that we need to discuss more on the flows of
>>>> events and placements. And I am also agree with the point that we can
>>>> create a slack channel for this.
>>>> >>>> Also the code will be in simple html, css and js format so anyone
>>>> can create/change the things easily. The design is looking fancy and
>>>> complicated but the code is as smooth as butter. So need to worry about
>>>> maintainance.
>>>> >>>> Regards,
>>>> >>>> Inzemamul Haq
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>
>>>> >>>>> Hi - Thank you for this.
>>>> >>>>>
>>>> >>>>> It's a very good conversation starter. I agreed with most of
>>>> Javier's comments, which makes clear that we need to do a better job of
>>>> "Explaining" and "Positioning".
>>>> >>>>>
>>>> >>>>> ASIDE: Javier - I invite you to write more such text and provide
>>>> a top level set of bullet points that can be perhaps worked into the
>>>> content.
>>>> >>>>>
>>>> >>>>> I think that the design colors are ok, the blue is appropriate
>>>> for a financial system, meaning steady and trustworthy on the color wheel.
>>>> Nice.
>>>> >>>>>
>>>> >>>>> We need more revamping of the content before we can properly do
>>>> this design, so let's try to attack that problem.
>>>> >>>>>
>>>> >>>>> Here is a requirement that may not be clear to you:
>>>> >>>>> * Site should be very simple, easy to change by anyone opening up
>>>> a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>> hopefully with names that make sense
>>>> >>>>> * Assume that you are gone and someone else has to modify just
>>>> some text areas, adding content in specific sections.
>>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>>> three years, and avoid content that can get stale.
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> Message and Content issues:
>>>> >>>>>
>>>> >>>>> * Fineract is part of Apache and this is not always clear from
>>>> the page today. Also, there is a common set of links and structure that you
>>>> can find in other Apache projects. It is not a requirement to follow other
>>>> Apache projects, but it would be useful to review them for commonalities:
>>>> >>>>> --> https://hadoop.apache.org
>>>> >>>>> --> https://airflow.apache.org
>>>> >>>>> --> https://kafka.apache.org
>>>> >>>>>
>>>> >>>>> * Note Community is there in each project. Check out the content
>>>> that each project has.
>>>> >>>>>
>>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>>> >>>>> and this should then flow into the requirements for the other
>>>> sections on the front page and then onto the wiki structure that we need
>>>> >>>>>
>>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>>> billing as the Fineract1.x releases it is still trying to get to a first
>>>> release and fineract1.x is releasing on a regular basis with lots of
>>>> activity. So, move Fineract-CN to a bottom section that's something about
>>>> "Additional community technologies"
>>>> >>>>> I was and am a big fan of this framework, and I know this
>>>> positioning is controversial for some, but until we get a release out and
>>>> lots of active development and deployments, that project remains very much
>>>> a side project of the community. It may become a very important thing, but
>>>> for now we should reflect the reality which is that Fineract1.x is where
>>>> the vast majority of the dev is going on, and the vast majority of the
>>>> users are there.
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> * We need to emphasize the key features of Fineract - there
>>>> should be a summary of the system.
>>>> >>>>>
>>>> >>>>> This may require more chat and discussion on list or on slack and
>>>> then development of a structure of content before you can really get a
>>>> design.
>>>> >>>>>
>>>> >>>>> Thank you again.
>>>> >>>>>
>>>> >>>>> James Dailey
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>
>>>> >>>>>> Hello James,
>>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>>> >>>>>> Regards,
>>>> >>>>>> Inzemamul Haq
>>>> >>>>>>
>>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>
>>>> >>>>>>> Hello Javier,
>>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>>> implement them as you suggested now what I need is some more brief about
>>>> the topics. This was the just an idea of how it'll look like surely we can
>>>> change and add the things.
>>>> >>>>>>> As you mentioned in the last that it's a template but it's not.
>>>> It's designed by me on the figma and the assets I used are open source so
>>>> their will be no licencing issue. I always go for the development through
>>>> scratch so no need to worry about that.
>>>> >>>>>>> Regards,
>>>> >>>>>>> Inzemam
>>>> >>>>>>>
>>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>>> javier@fiter.io> wrote:
>>>> >>>>>>>>
>>>> >>>>>>>> Hy Meta,
>>>> >>>>>>>>
>>>> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic
>>>> in general, and it seems much more modern and suitable for the next stage
>>>> of our community.
>>>> >>>>>>>>
>>>> >>>>>>>> My two cents:
>>>> >>>>>>>>
>>>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful
>>>> in other areas of the industry, not just banks. We need to convey that
>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>> credit card as our visuals will put us in the last 20 years of the
>>>> industry, and we are in the next 20 years. The images we need to use has to
>>>> be conceptual, not rigid on old paradigms.
>>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>> paradigm of "Internet switches," allowing the users of financial
>>>> institutions to move their assets worldwide quickly and safely. All
>>>> purchases are now digital.
>>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>> experiment while most of our community depends on and uses Fineract. This
>>>> must be clearly shown on the website and the real estate we dedicate to
>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>> CN is not backward compatible with Fineract.
>>>> >>>>>>>> The project we are proud of: I will only use the project part
>>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>>> new can of worms on which project gets selected and which criteria we
>>>> should use, on top of getting the right set of approvals from them to be
>>>> used as projects.
>>>> >>>>>>>> Last but not least, you used a template for the design. We
>>>> need the license of that template that allows us to use it without
>>>> limitations, and the template license is aligned with Apache 2.0.
>>>> >>>>>>>>
>>>> >>>>>>>> Javier
>>>> >>>>>>>>
>>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>
>>>> >>>>>>>>> Hi James,
>>>> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
>>>> FINERACT redesigned website. Please review and let me know if you have any
>>>> questions or changes needed.
>>>> >>>>>>>>>
>>>> >>>>>>>>>
>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>> >>>>>>>>>
>>>> >>>>>>>>> Regards,
>>>> >>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>
>>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Okay lemme begin the work.
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>> +1
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> Hi
>>>> >>>>>>>>>>>>> I've been through the website and got it closely that
>>>> what exact is there on the website. I'll create a static mockup for the
>>>> website.
>>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether
>>>> anyone new or experienced first comes to the website got confused of what's
>>>> happening and how things are going we can work upon it.
>>>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger
>>>> on that website? I have ability to work on static websites where the data
>>>> comes from dynamic CMS.
>>>> >>>>>>>>>>>>> So I can work on tha too....
>>>> >>>>>>>>>>>>> Regards,
>>>> >>>>>>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>>> page website for the project, so not an app. The content needs to be
>>>> largely static or to pick up content we regularly post on blog. The current
>>>> site is basic html. Just making sure we’re talking about the same thing.
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed
>>>> is a design lens, in my view. But, a good UIX process does start with
>>>> who’s the audience and what’s their need when they land on the page.
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>> Hi,
>>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
>>>> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
>>>> come up with a design also will share here in the thread and we can get
>>>> comments in the meeting.
>>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>>> overall UI/UX
>>>> >>>>>>>>>>>>>>> Regards,
>>>> >>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>>> have four people who said they'd like to be involved.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group
>>>> and then we can share back here on list and also hold a meeting on zoom in
>>>> mid February.
>>>> >>>>>>>>>>>>>>>> Feb 16th?
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>> document:
>>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>>> detail.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>>>> there a gap in content (Bruce, Tekle? - start a thread about this)
>>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
>>>> you think belong being "brought over". compile a list of those pages. If
>>>> none, great.
>>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>>> landing page (Meta Cyrus?)
>>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>>> landing pages that you like
>>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>>> functional description aimed at a Business Leader (Dick Dickson?)
>>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>> confluence with links (james or ?)
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>>> thread.
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> thanks
>>>> >>>>>>>>>>>>>>>> James
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>>> d@gwocu.com> wrote:
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>> inzemamhaq05@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> Hi James,
>>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design
>>>> and develop a good user reliable website.
>>>> >>>>>>>>>>>>>>>>> Where I can start??
>>>> >>>>>>>>>>>>>>>>> Regards,
>>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>>> >>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>> jamespdailey@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> All -
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>>> been 3+ years since we did a clean sweep of it. We also have a front
>>>> landing page at https://fineract.apache.org that could be better at
>>>> communicating the project and community. Who wants to work on this with me?
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>> >>>>>>>>>>>>>>>>>> ---
>>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think
>>>> we should have a top level split on the main page as well, or perhaps a
>>>> separate landing page for FineractCN.
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> ---
>>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out
>>>> how to show two levels):
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> FAQ
>>>> >>>>>>>>>>>>>>>>>> About Fineract
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> TBD
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Project Management
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to
>>>> be more prominent)
>>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
>>>> top)
>>>> >>>>>>>>>>>>>>>>>> Surveys
>>>> >>>>>>>>>>>>>>>>>> Release processes
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Committer guides
>>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>> >>>>>>>>>>>>>>>>>> Standards
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Documentation
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>>>> documentation.
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces,
>>>> etc) ... all go to blog
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>> >>>>>>>>>>>>>>>>>> FINERACT
>>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>> How-to articles
>>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> --
>>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> --
>>>> >>>>>>>>>> Sent from Gmail Mobile
>>>> >>
>>>> >> --
>>>> >> Sent from Gmail Mobile
>>>>
>>>
Re: Website and Wiki for Fineract updates
Posted by Bruce <br...@gmail.com>.
Hi,
I hope this email finds you well. I wanted to share some observations after
going through the documentation for Fineract again.
While the documentation provides an overview of deployment options here
https://fineract.apache.org/docs/current/#_deployment , I noticed that
several options, such as Docker Compose, Tomcat, Undertow, Jetty, JBoss,
Weblogic, and Payara, are marked as TBD, indicating a lack of content and
guidance for users. There is also no deployment content on Kubernetes, AWS
and Google Cloud. Let's address this.
Additionally, the Fineract Development section here
https://fineract.apache.org/docs/current/#_fineract_development_environment
appears
to be incomplete and in need of further content to cover important topics
related to Fineract development. This section also includes topics marked
as "TBD" on the website, such as Docker, Docker Compose, Podman, Rancher
Docker Desktop, IDE selection and configuration (including IntelliJ,
Eclipse, and VSCode), Kubernetes deployment and management, Minikube,
Microk8s, K3d, Helm Charts, and installation and usage of various
development tools like Brew for MacOS and Linux. I propose that the
community contibutes content for the following topics:
- Docker: how to install, run, and use Docker containers for Fineract
- Docker Compose: how to use Docker Compose to orchestrate multiple
containers for Fineract
- Podman: how to use Podman as an alternative to Docker for running
containers
- Rancher Docker Desktop: how to use Rancher Docker Desktop to run
Kubernetes clusters on one's local machine
- IDE: how to choose and configure an IDE for Fineract development
- IntelliJ: how to set up and use IntelliJ IDEA as an IDE for Fineract
- Eclipse: how to set up and use Eclipse as an IDE for Fineract
- VSCode: how to set up and use VSCode as an IDE for Fineract
- Kubernetes: how to deploy and manage Fineract on Kubernetes clusters
- Minikube: how to use Minikube to run a local Kubernetes cluster for
Fineract
- Microk8s: how to use Microk8s to run a lightweight Kubernetes cluster
for Fineract
- K3d: how to use K3d to run a Kubernetes cluster in Docker for Fineract
- Helm Charts: how to use Helm Charts to package and deploy Fineract
applications on Kubernetes
- Tools: how to install and use various tools that can help one with
Fineract development
- Brew: how to install and use Brew for MacOS and Linux
By actively addressing these gaps in the documentation, we can provide
valuable support to the Fineract community and further showcase the
flexibility and compatibility of Fineract with different technologies and
platforms.
I look forward to collaborating with the community to contribute content
for these important topics and improve the overall documentation for
Fineract.
Best Regards
Bruce
On Fri, Apr 7, 2023 at 10:03 PM James Dailey <ja...@gmail.com> wrote:
> Meta or Bruce - any updates?
>
>
>
> On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com>
> wrote:
>
>> Yep I'll be sharing the new design in which I hage taken care of all the
>> previous points you and others mentioned..
>>
>>
>> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> I've started to change some of the structure of the wiki. I'm just
>>> trying to clean it up: Does anyone have an objection?
>>>
>>> * Noting where content is historical and deprecating it
>>> * Moving the Quarterly PMC reports to slightly more prominence
>>>
>>> This is incremental.
>>>
>>> Inzemam - can you provide a new design to review taking on the feedback?
>>>
>>>
>>>
>>>
>>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>> >
>>> > Okay I'll be looking into it..
>>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>>> fields. Surely working effectively with both the orgs by making good
>>> designs with premium feel.
>>> > Regards,
>>> > Inzemam
>>> >
>>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>> >>
>>> >> Please make a set of suggestions or revise your designs based on
>>> input.
>>> >>
>>> >> Feel free to dive into this .
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>> >>>
>>> >>> Hello James,
>>> >>> When we are going to start the work or are we leaving it for future?
>>> >>>
>>> >>> Regards,
>>> >>> Inzemam
>>> >>>
>>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>>> wrote:
>>> >>>>
>>> >>>> Hi James,
>>> >>>> You are correct that we need to discuss more on the flows of events
>>> and placements. And I am also agree with the point that we can create a
>>> slack channel for this.
>>> >>>> Also the code will be in simple html, css and js format so anyone
>>> can create/change the things easily. The design is looking fancy and
>>> complicated but the code is as smooth as butter. So need to worry about
>>> maintainance.
>>> >>>> Regards,
>>> >>>> Inzemamul Haq
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>> >>>>>
>>> >>>>> Hi - Thank you for this.
>>> >>>>>
>>> >>>>> It's a very good conversation starter. I agreed with most of
>>> Javier's comments, which makes clear that we need to do a better job of
>>> "Explaining" and "Positioning".
>>> >>>>>
>>> >>>>> ASIDE: Javier - I invite you to write more such text and provide
>>> a top level set of bullet points that can be perhaps worked into the
>>> content.
>>> >>>>>
>>> >>>>> I think that the design colors are ok, the blue is appropriate for
>>> a financial system, meaning steady and trustworthy on the color wheel. Nice.
>>> >>>>>
>>> >>>>> We need more revamping of the content before we can properly do
>>> this design, so let's try to attack that problem.
>>> >>>>>
>>> >>>>> Here is a requirement that may not be clear to you:
>>> >>>>> * Site should be very simple, easy to change by anyone opening up
>>> a Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>> hopefully with names that make sense
>>> >>>>> * Assume that you are gone and someone else has to modify just
>>> some text areas, adding content in specific sections.
>>> >>>>> * Assume that no-one touches the website for over a year, maybe
>>> three years, and avoid content that can get stale.
>>> >>>>>
>>> >>>>>
>>> >>>>> Message and Content issues:
>>> >>>>>
>>> >>>>> * Fineract is part of Apache and this is not always clear from the
>>> page today. Also, there is a common set of links and structure that you can
>>> find in other Apache projects. It is not a requirement to follow other
>>> Apache projects, but it would be useful to review them for commonalities:
>>> >>>>> --> https://hadoop.apache.org
>>> >>>>> --> https://airflow.apache.org
>>> >>>>> --> https://kafka.apache.org
>>> >>>>>
>>> >>>>> * Note Community is there in each project. Check out the content
>>> that each project has.
>>> >>>>>
>>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>>> >>>>> and this should then flow into the requirements for the other
>>> sections on the front page and then onto the wiki structure that we need
>>> >>>>>
>>> >>>>> * At this time Fineract-CN should probably not receive equal
>>> billing as the Fineract1.x releases it is still trying to get to a first
>>> release and fineract1.x is releasing on a regular basis with lots of
>>> activity. So, move Fineract-CN to a bottom section that's something about
>>> "Additional community technologies"
>>> >>>>> I was and am a big fan of this framework, and I know this
>>> positioning is controversial for some, but until we get a release out and
>>> lots of active development and deployments, that project remains very much
>>> a side project of the community. It may become a very important thing, but
>>> for now we should reflect the reality which is that Fineract1.x is where
>>> the vast majority of the dev is going on, and the vast majority of the
>>> users are there.
>>> >>>>>
>>> >>>>>
>>> >>>>> * We need to emphasize the key features of Fineract - there should
>>> be a summary of the system.
>>> >>>>>
>>> >>>>> This may require more chat and discussion on list or on slack and
>>> then development of a structure of content before you can really get a
>>> design.
>>> >>>>>
>>> >>>>> Thank you again.
>>> >>>>>
>>> >>>>> James Dailey
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>
>>> >>>>>> Hello James,
>>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>>> >>>>>> Regards,
>>> >>>>>> Inzemamul Haq
>>> >>>>>>
>>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
>>> wrote:
>>> >>>>>>>
>>> >>>>>>> Hello Javier,
>>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>>> implement them as you suggested now what I need is some more brief about
>>> the topics. This was the just an idea of how it'll look like surely we can
>>> change and add the things.
>>> >>>>>>> As you mentioned in the last that it's a template but it's not.
>>> It's designed by me on the figma and the assets I used are open source so
>>> their will be no licencing issue. I always go for the development through
>>> scratch so no need to worry about that.
>>> >>>>>>> Regards,
>>> >>>>>>> Inzemam
>>> >>>>>>>
>>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>>> javier@fiter.io> wrote:
>>> >>>>>>>>
>>> >>>>>>>> Hy Meta,
>>> >>>>>>>>
>>> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic
>>> in general, and it seems much more modern and suitable for the next stage
>>> of our community.
>>> >>>>>>>>
>>> >>>>>>>> My two cents:
>>> >>>>>>>>
>>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful
>>> in other areas of the industry, not just banks. We need to convey that
>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>> credit card as our visuals will put us in the last 20 years of the
>>> industry, and we are in the next 20 years. The images we need to use has to
>>> be conceptual, not rigid on old paradigms.
>>> >>>>>>>> Fineract is a backend. Fineract will help the financial
>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>> paradigm of "Internet switches," allowing the users of financial
>>> institutions to move their assets worldwide quickly and safely. All
>>> purchases are now digital.
>>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>>> same exposure on our website as Fineract. Fineract CN it's still an
>>> experiment while most of our community depends on and uses Fineract. This
>>> must be clearly shown on the website and the real estate we dedicate to
>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>> CN is not backward compatible with Fineract.
>>> >>>>>>>> The project we are proud of: I will only use the project part
>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>> new can of worms on which project gets selected and which criteria we
>>> should use, on top of getting the right set of approvals from them to be
>>> used as projects.
>>> >>>>>>>> Last but not least, you used a template for the design. We need
>>> the license of that template that allows us to use it without limitations,
>>> and the template license is aligned with Apache 2.0.
>>> >>>>>>>>
>>> >>>>>>>> Javier
>>> >>>>>>>>
>>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>
>>> >>>>>>>>> Hi James,
>>> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
>>> FINERACT redesigned website. Please review and let me know if you have any
>>> questions or changes needed.
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>> >>>>>>>>>
>>> >>>>>>>>> Regards,
>>> >>>>>>>>> Inzemamul Haq
>>> >>>>>>>>>
>>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>
>>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> Okay lemme begin the work.
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> +1
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Hi
>>> >>>>>>>>>>>>> I've been through the website and got it closely that what
>>> exact is there on the website. I'll create a static mockup for the website.
>>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone
>>> new or experienced first comes to the website got confused of what's
>>> happening and how things are going we can work upon it.
>>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger
>>> on that website? I have ability to work on static websites where the data
>>> comes from dynamic CMS.
>>> >>>>>>>>>>>>> So I can work on tha too....
>>> >>>>>>>>>>>>> Regards,
>>> >>>>>>>>>>>>> Inzemamul Haq
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Inzemamul Haq -
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single
>>> page website for the project, so not an app. The content needs to be
>>> largely static or to pick up content we regularly post on blog. The current
>>> site is basic html. Just making sure we’re talking about the same thing.
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Fineract.Apache.org
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is
>>> a design lens, in my view. But, a good UIX process does start with who’s
>>> the audience and what’s their need when they land on the page.
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Hi,
>>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
>>> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
>>> come up with a design also will share here in the thread and we can get
>>> comments in the meeting.
>>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>>> overall UI/UX
>>> >>>>>>>>>>>>>>> Regards,
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Inzemamul Haq
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>>> have four people who said they'd like to be involved.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and
>>> then we can share back here on list and also hold a meeting on zoom in mid
>>> February.
>>> >>>>>>>>>>>>>>>> Feb 16th?
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>> document:
>>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>> detail.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> Proposed Tasks:
>>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>>> there a gap in content (Bruce, Tekle? - start a thread about this)
>>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
>>> you think belong being "brought over". compile a list of those pages. If
>>> none, great.
>>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>> landing page (Meta Cyrus?)
>>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find
>>> landing pages that you like
>>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>>> functional description aimed at a Business Leader (Dick Dickson?)
>>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>> confluence with links (james or ?)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>> thread.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> thanks
>>> >>>>>>>>>>>>>>>> James
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>>> d@gwocu.com> wrote:
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>> inzemamhaq05@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> Hi James,
>>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
>>> develop a good user reliable website.
>>> >>>>>>>>>>>>>>>>> Where I can start??
>>> >>>>>>>>>>>>>>>>> Regards,
>>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>> jamespdailey@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> All -
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>>> been 3+ years since we did a clean sweep of it. We also have a front
>>> landing page at https://fineract.apache.org that could be better at
>>> communicating the project and community. Who wants to work on this with me?
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>> >>>>>>>>>>>>>>>>>> ---
>>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Add blog feed
>>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>>> >>>>>>>>>>>>>>>>>> Include FAQ
>>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think
>>> we should have a top level split on the main page as well, or perhaps a
>>> separate landing page for FineractCN.
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> ---
>>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how
>>> to show two levels):
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> FAQ
>>> >>>>>>>>>>>>>>>>>> About Fineract
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> About FineractCN
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> TBD
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Project Management
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to
>>> be more prominent)
>>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
>>> top)
>>> >>>>>>>>>>>>>>>>>> Surveys
>>> >>>>>>>>>>>>>>>>>> Release processes
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> How do I get involved?
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Committer guides
>>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>> >>>>>>>>>>>>>>>>>> Standards
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Documentation
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>>> documentation.
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc)
>>> ... all go to blog
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> The current high level structure:
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>> >>>>>>>>>>>>>>>>>> FINERACT
>>> >>>>>>>>>>>>>>>>>> FINERACT CN
>>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> How-to articles
>>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>> >>>>>>>>>>>>>>>>>> Meeting notes
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> --
>>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>>> >>>>>>>>>>
>>> >>>>>>>>>> --
>>> >>>>>>>>>> Sent from Gmail Mobile
>>> >>
>>> >> --
>>> >> Sent from Gmail Mobile
>>>
>>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Meta or Bruce - any updates?
On Wed, Mar 22, 2023 at 11:17 PM Meta Cyrus <in...@gmail.com> wrote:
> Yep I'll be sharing the new design in which I hage taken care of all the
> previous points you and others mentioned..
>
>
> On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com>
> wrote:
>
>> I've started to change some of the structure of the wiki. I'm just
>> trying to clean it up: Does anyone have an objection?
>>
>> * Noting where content is historical and deprecating it
>> * Moving the Quarterly PMC reports to slightly more prominence
>>
>> This is incremental.
>>
>> Inzemam - can you provide a new design to review taking on the feedback?
>>
>>
>>
>>
>> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>> >
>> > Okay I'll be looking into it..
>> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
>> fields. Surely working effectively with both the orgs by making good
>> designs with premium feel.
>> > Regards,
>> > Inzemam
>> >
>> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
>> wrote:
>> >>
>> >> Please make a set of suggestions or revise your designs based on input.
>> >>
>> >> Feel free to dive into this .
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>> >>>
>> >>> Hello James,
>> >>> When we are going to start the work or are we leaving it for future?
>> >>>
>> >>> Regards,
>> >>> Inzemam
>> >>>
>> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
>> wrote:
>> >>>>
>> >>>> Hi James,
>> >>>> You are correct that we need to discuss more on the flows of events
>> and placements. And I am also agree with the point that we can create a
>> slack channel for this.
>> >>>> Also the code will be in simple html, css and js format so anyone
>> can create/change the things easily. The design is looking fancy and
>> complicated but the code is as smooth as butter. So need to worry about
>> maintainance.
>> >>>> Regards,
>> >>>> Inzemamul Haq
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
>> wrote:
>> >>>>>
>> >>>>> Hi - Thank you for this.
>> >>>>>
>> >>>>> It's a very good conversation starter. I agreed with most of
>> Javier's comments, which makes clear that we need to do a better job of
>> "Explaining" and "Positioning".
>> >>>>>
>> >>>>> ASIDE: Javier - I invite you to write more such text and provide a
>> top level set of bullet points that can be perhaps worked into the content.
>> >>>>>
>> >>>>> I think that the design colors are ok, the blue is appropriate for
>> a financial system, meaning steady and trustworthy on the color wheel. Nice.
>> >>>>>
>> >>>>> We need more revamping of the content before we can properly do
>> this design, so let's try to attack that problem.
>> >>>>>
>> >>>>> Here is a requirement that may not be clear to you:
>> >>>>> * Site should be very simple, easy to change by anyone opening up a
>> Text Editor and modifying the HTML directly. e.g. use CSS styles and
>> hopefully with names that make sense
>> >>>>> * Assume that you are gone and someone else has to modify just some
>> text areas, adding content in specific sections.
>> >>>>> * Assume that no-one touches the website for over a year, maybe
>> three years, and avoid content that can get stale.
>> >>>>>
>> >>>>>
>> >>>>> Message and Content issues:
>> >>>>>
>> >>>>> * Fineract is part of Apache and this is not always clear from the
>> page today. Also, there is a common set of links and structure that you can
>> find in other Apache projects. It is not a requirement to follow other
>> Apache projects, but it would be useful to review them for commonalities:
>> >>>>> --> https://hadoop.apache.org
>> >>>>> --> https://airflow.apache.org
>> >>>>> --> https://kafka.apache.org
>> >>>>>
>> >>>>> * Note Community is there in each project. Check out the content
>> that each project has.
>> >>>>>
>> >>>>> * Key tasks should be up top : Learn more, Help, Download
>> >>>>> and this should then flow into the requirements for the other
>> sections on the front page and then onto the wiki structure that we need
>> >>>>>
>> >>>>> * At this time Fineract-CN should probably not receive equal
>> billing as the Fineract1.x releases it is still trying to get to a first
>> release and fineract1.x is releasing on a regular basis with lots of
>> activity. So, move Fineract-CN to a bottom section that's something about
>> "Additional community technologies"
>> >>>>> I was and am a big fan of this framework, and I know this
>> positioning is controversial for some, but until we get a release out and
>> lots of active development and deployments, that project remains very much
>> a side project of the community. It may become a very important thing, but
>> for now we should reflect the reality which is that Fineract1.x is where
>> the vast majority of the dev is going on, and the vast majority of the
>> users are there.
>> >>>>>
>> >>>>>
>> >>>>> * We need to emphasize the key features of Fineract - there should
>> be a summary of the system.
>> >>>>>
>> >>>>> This may require more chat and discussion on list or on slack and
>> then development of a structure of content before you can really get a
>> design.
>> >>>>>
>> >>>>> Thank you again.
>> >>>>>
>> >>>>> James Dailey
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>> >>>>>>
>> >>>>>> Hello James,
>> >>>>>> Have you reviewed the website frame. Please share the feedback.
>> >>>>>> Regards,
>> >>>>>> Inzemamul Haq
>> >>>>>>
>> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
>> wrote:
>> >>>>>>>
>> >>>>>>> Hello Javier,
>> >>>>>>> Thanks for your feedback. The points you mentioned, I'll
>> implement them as you suggested now what I need is some more brief about
>> the topics. This was the just an idea of how it'll look like surely we can
>> change and add the things.
>> >>>>>>> As you mentioned in the last that it's a template but it's not.
>> It's designed by me on the figma and the assets I used are open source so
>> their will be no licencing issue. I always go for the development through
>> scratch so no need to worry about that.
>> >>>>>>> Regards,
>> >>>>>>> Inzemam
>> >>>>>>>
>> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <
>> javier@fiter.io> wrote:
>> >>>>>>>>
>> >>>>>>>> Hy Meta,
>> >>>>>>>>
>> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic
>> in general, and it seems much more modern and suitable for the next stage
>> of our community.
>> >>>>>>>>
>> >>>>>>>> My two cents:
>> >>>>>>>>
>> >>>>>>>> It is too linked with banks. Fineract has proved to be useful in
>> other areas of the industry, not just banks. We need to convey that
>> Fineract is a platform for many use cases. Using a mobile phone and a
>> credit card as our visuals will put us in the last 20 years of the
>> industry, and we are in the next 20 years. The images we need to use has to
>> be conceptual, not rigid on old paradigms.
>> >>>>>>>> Fineract is a backend. Fineract will help the financial industry
>> transcend from the old paradigm of "save deposit boxes" to the new paradigm
>> of "Internet switches," allowing the users of financial institutions to
>> move their assets worldwide quickly and safely. All purchases are now
>> digital.
>> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
>> same exposure on our website as Fineract. Fineract CN it's still an
>> experiment while most of our community depends on and uses Fineract. This
>> must be clearly shown on the website and the real estate we dedicate to
>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>> CN is not backward compatible with Fineract.
>> >>>>>>>> The project we are proud of: I will only use the project part if
>> we get three Fortune 500 companies using Fineract. It will also open a new
>> can of worms on which project gets selected and which criteria we should
>> use, on top of getting the right set of approvals from them to be used as
>> projects.
>> >>>>>>>> Last but not least, you used a template for the design. We need
>> the license of that template that allows us to use it without limitations,
>> and the template license is aligned with Apache 2.0.
>> >>>>>>>>
>> >>>>>>>> Javier
>> >>>>>>>>
>> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>
>> >>>>>>>>> Hi James,
>> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
>> FINERACT redesigned website. Please review and let me know if you have any
>> questions or changes needed.
>> >>>>>>>>>
>> >>>>>>>>>
>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>> >>>>>>>>>
>> >>>>>>>>> Regards,
>> >>>>>>>>> Inzemamul Haq
>> >>>>>>>>>
>> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Hi Meta - Any updates from you on this?
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>> Okay lemme begin the work.
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> +1
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Hi
>> >>>>>>>>>>>>> I've been through the website and got it closely that what
>> exact is there on the website. I'll create a static mockup for the website.
>> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone
>> new or experienced first comes to the website got confused of what's
>> happening and how things are going we can work upon it.
>> >>>>>>>>>>>>> Also I have a question are we going to implement blogger on
>> that website? I have ability to work on static websites where the data
>> comes from dynamic CMS.
>> >>>>>>>>>>>>> So I can work on tha too....
>> >>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>> Inzemamul Haq
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Inzemamul Haq -
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Appreciate the response. This is revising our single page
>> website for the project, so not an app. The content needs to be largely
>> static or to pick up content we regularly post on blog. The current site is
>> basic html. Just making sure we’re talking about the same thing.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Fineract.Apache.org
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is
>> a design lens, in my view. But, a good UIX process does start with who’s
>> the audience and what’s their need when they land on the page.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Hi,
>> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
>> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
>> come up with a design also will share here in the thread and we can get
>> comments in the meeting.
>> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
>> overall UI/UX
>> >>>>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Inzemamul Haq
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We
>> have four people who said they'd like to be involved.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and
>> then we can share back here on list and also hold a meeting on zoom in mid
>> February.
>> >>>>>>>>>>>>>>>> Feb 16th?
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>> document:
>> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>> detail.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Proposed Tasks:
>> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
>> there a gap in content (Bruce, Tekle? - start a thread about this)
>> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
>> you think belong being "brought over". compile a list of those pages. If
>> none, great.
>> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>> landing page (Meta Cyrus?)
>> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing
>> pages that you like
>> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
>> functional description aimed at a Business Leader (Dick Dickson?)
>> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>> confluence with links (james or ?)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>> thread.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> thanks
>> >>>>>>>>>>>>>>>> James
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <
>> d@gwocu.com> wrote:
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Sent from my iPhone
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>> inzemamhaq05@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Hi James,
>> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
>> develop a good user reliable website.
>> >>>>>>>>>>>>>>>>> Where I can start??
>> >>>>>>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>>>>>> Inzemamul Haq
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>> jamespdailey@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> All -
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's
>> been 3+ years since we did a clean sweep of it. We also have a front
>> landing page at https://fineract.apache.org that could be better at
>> communicating the project and community. Who wants to work on this with me?
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>> >>>>>>>>>>>>>>>>>> ---
>> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Add blog feed
>> >>>>>>>>>>>>>>>>>> Add feed to dev list
>> >>>>>>>>>>>>>>>>>> Include FAQ
>> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think
>> we should have a top level split on the main page as well, or perhaps a
>> separate landing page for FineractCN.
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> ---
>> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how
>> to show two levels):
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> FAQ
>> >>>>>>>>>>>>>>>>>> About Fineract
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> New top level functional descriptions
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> About FineractCN
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> TBD
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Project Management
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to
>> be more prominent)
>> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
>> top)
>> >>>>>>>>>>>>>>>>>> Surveys
>> >>>>>>>>>>>>>>>>>> Release processes
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> How do I get involved?
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Committer guides
>> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>> >>>>>>>>>>>>>>>>>> Standards
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Documentation
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
>> documentation.
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc)
>> ... all go to blog
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> The current high level structure:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>> >>>>>>>>>>>>>>>>>> FINERACT
>> >>>>>>>>>>>>>>>>>> FINERACT CN
>> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
>> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> How-to articles
>> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>> >>>>>>>>>>>>>>>>>> Meeting notes
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> --
>> >>>>>>>>>>>>>> Sent from Gmail Mobile
>> >>>>>>>>>>
>> >>>>>>>>>> --
>> >>>>>>>>>> Sent from Gmail Mobile
>> >>
>> >> --
>> >> Sent from Gmail Mobile
>>
>
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Yep I'll be sharing the new design in which I hage taken care of all the
previous points you and others mentioned..
On Thu, 23 Mar, 2023, 6:29 am James Dailey, <ja...@gmail.com> wrote:
> I've started to change some of the structure of the wiki. I'm just
> trying to clean it up: Does anyone have an objection?
>
> * Noting where content is historical and deprecating it
> * Moving the Quarterly PMC reports to slightly more prominence
>
> This is incremental.
>
> Inzemam - can you provide a new design to review taking on the feedback?
>
>
>
>
> On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com> wrote:
> >
> > Okay I'll be looking into it..
> > Also I am looking forward for GSOC'23 for MIFOS too in the frontend
> fields. Surely working effectively with both the orgs by making good
> designs with premium feel.
> > Regards,
> > Inzemam
> >
> > On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com>
> wrote:
> >>
> >> Please make a set of suggestions or revise your designs based on input.
> >>
> >> Feel free to dive into this .
> >>
> >>
> >>
> >>
> >>
> >> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com>
> wrote:
> >>>
> >>> Hello James,
> >>> When we are going to start the work or are we leaving it for future?
> >>>
> >>> Regards,
> >>> Inzemam
> >>>
> >>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com>
> wrote:
> >>>>
> >>>> Hi James,
> >>>> You are correct that we need to discuss more on the flows of events
> and placements. And I am also agree with the point that we can create a
> slack channel for this.
> >>>> Also the code will be in simple html, css and js format so anyone can
> create/change the things easily. The design is looking fancy and
> complicated but the code is as smooth as butter. So need to worry about
> maintainance.
> >>>> Regards,
> >>>> Inzemamul Haq
> >>>>
> >>>>
> >>>>
> >>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
> wrote:
> >>>>>
> >>>>> Hi - Thank you for this.
> >>>>>
> >>>>> It's a very good conversation starter. I agreed with most of
> Javier's comments, which makes clear that we need to do a better job of
> "Explaining" and "Positioning".
> >>>>>
> >>>>> ASIDE: Javier - I invite you to write more such text and provide a
> top level set of bullet points that can be perhaps worked into the content.
> >>>>>
> >>>>> I think that the design colors are ok, the blue is appropriate for a
> financial system, meaning steady and trustworthy on the color wheel. Nice.
> >>>>>
> >>>>> We need more revamping of the content before we can properly do this
> design, so let's try to attack that problem.
> >>>>>
> >>>>> Here is a requirement that may not be clear to you:
> >>>>> * Site should be very simple, easy to change by anyone opening up a
> Text Editor and modifying the HTML directly. e.g. use CSS styles and
> hopefully with names that make sense
> >>>>> * Assume that you are gone and someone else has to modify just some
> text areas, adding content in specific sections.
> >>>>> * Assume that no-one touches the website for over a year, maybe
> three years, and avoid content that can get stale.
> >>>>>
> >>>>>
> >>>>> Message and Content issues:
> >>>>>
> >>>>> * Fineract is part of Apache and this is not always clear from the
> page today. Also, there is a common set of links and structure that you can
> find in other Apache projects. It is not a requirement to follow other
> Apache projects, but it would be useful to review them for commonalities:
> >>>>> --> https://hadoop.apache.org
> >>>>> --> https://airflow.apache.org
> >>>>> --> https://kafka.apache.org
> >>>>>
> >>>>> * Note Community is there in each project. Check out the content
> that each project has.
> >>>>>
> >>>>> * Key tasks should be up top : Learn more, Help, Download
> >>>>> and this should then flow into the requirements for the other
> sections on the front page and then onto the wiki structure that we need
> >>>>>
> >>>>> * At this time Fineract-CN should probably not receive equal billing
> as the Fineract1.x releases it is still trying to get to a first release
> and fineract1.x is releasing on a regular basis with lots of activity. So,
> move Fineract-CN to a bottom section that's something about "Additional
> community technologies"
> >>>>> I was and am a big fan of this framework, and I know this
> positioning is controversial for some, but until we get a release out and
> lots of active development and deployments, that project remains very much
> a side project of the community. It may become a very important thing, but
> for now we should reflect the reality which is that Fineract1.x is where
> the vast majority of the dev is going on, and the vast majority of the
> users are there.
> >>>>>
> >>>>>
> >>>>> * We need to emphasize the key features of Fineract - there should
> be a summary of the system.
> >>>>>
> >>>>> This may require more chat and discussion on list or on slack and
> then development of a structure of content before you can really get a
> design.
> >>>>>
> >>>>> Thank you again.
> >>>>>
> >>>>> James Dailey
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
> wrote:
> >>>>>>
> >>>>>> Hello James,
> >>>>>> Have you reviewed the website frame. Please share the feedback.
> >>>>>> Regards,
> >>>>>> Inzemamul Haq
> >>>>>>
> >>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
> wrote:
> >>>>>>>
> >>>>>>> Hello Javier,
> >>>>>>> Thanks for your feedback. The points you mentioned, I'll implement
> them as you suggested now what I need is some more brief about the topics.
> This was the just an idea of how it'll look like surely we can change and
> add the things.
> >>>>>>> As you mentioned in the last that it's a template but it's not.
> It's designed by me on the figma and the assets I used are open source so
> their will be no licencing issue. I always go for the development through
> scratch so no need to worry about that.
> >>>>>>> Regards,
> >>>>>>> Inzemam
> >>>>>>>
> >>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io>
> wrote:
> >>>>>>>>
> >>>>>>>> Hy Meta,
> >>>>>>>>
> >>>>>>>> Great job; I like the enhancement of the visuals and aesthetic in
> general, and it seems much more modern and suitable for the next stage of
> our community.
> >>>>>>>>
> >>>>>>>> My two cents:
> >>>>>>>>
> >>>>>>>> It is too linked with banks. Fineract has proved to be useful in
> other areas of the industry, not just banks. We need to convey that
> Fineract is a platform for many use cases. Using a mobile phone and a
> credit card as our visuals will put us in the last 20 years of the
> industry, and we are in the next 20 years. The images we need to use has to
> be conceptual, not rigid on old paradigms.
> >>>>>>>> Fineract is a backend. Fineract will help the financial industry
> transcend from the old paradigm of "save deposit boxes" to the new paradigm
> of "Internet switches," allowing the users of financial institutions to
> move their assets worldwide quickly and safely. All purchases are now
> digital.
> >>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the
> same exposure on our website as Fineract. Fineract CN it's still an
> experiment while most of our community depends on and uses Fineract. This
> must be clearly shown on the website and the real estate we dedicate to
> each one. Fineract CN wasn't the project incubated originally, and Fineract
> CN is not backward compatible with Fineract.
> >>>>>>>> The project we are proud of: I will only use the project part if
> we get three Fortune 500 companies using Fineract. It will also open a new
> can of worms on which project gets selected and which criteria we should
> use, on top of getting the right set of approvals from them to be used as
> projects.
> >>>>>>>> Last but not least, you used a template for the design. We need
> the license of that template that allows us to use it without limitations,
> and the template license is aligned with Apache 2.0.
> >>>>>>>>
> >>>>>>>> Javier
> >>>>>>>>
> >>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi James,
> >>>>>>>>> Below is the drive link of complete page screenshot of APACHE
> FINERACT redesigned website. Please review and let me know if you have any
> questions or changes needed.
> >>>>>>>>>
> >>>>>>>>>
> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Inzemamul Haq
> >>>>>>>>>
> >>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hi Meta - Any updates from you on this?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Okay lemme begin the work.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> +1
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hi
> >>>>>>>>>>>>> I've been through the website and got it closely that what
> exact is there on the website. I'll create a static mockup for the website.
> >>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone
> new or experienced first comes to the website got confused of what's
> happening and how things are going we can work upon it.
> >>>>>>>>>>>>> Also I have a question are we going to implement blogger on
> that website? I have ability to work on static websites where the data
> comes from dynamic CMS.
> >>>>>>>>>>>>> So I can work on tha too....
> >>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Inzemamul Haq -
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Appreciate the response. This is revising our single page
> website for the project, so not an app. The content needs to be largely
> static or to pick up content we regularly post on blog. The current site is
> basic html. Just making sure we’re talking about the same thing.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Fineract.Apache.org
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a
> design lens, in my view. But, a good UIX process does start with who’s the
> audience and what’s their need when they land on the page.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>>> First I will create mockup using the figma where we can
> get a better Idea of what exactly has to be happen. By the 16th of Feb I'll
> come up with a design also will share here in the thread and we can get
> comments in the meeting.
> >>>>>>>>>>>>>>> I'll start looking other apache websites and get an
> overall UI/UX
> >>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We have
> four people who said they'd like to be involved.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and
> then we can share back here on list and also hold a meeting on zoom in mid
> February.
> >>>>>>>>>>>>>>>> Feb 16th?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
> document:
> >>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
> >>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
> detail.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Proposed Tasks:
> >>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is
> there a gap in content (Bruce, Tekle? - start a thread about this)
> >>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections
> you think belong being "brought over". compile a list of those pages. If
> none, great.
> >>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
> landing page (Meta Cyrus?)
> >>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing
> pages that you like
> >>>>>>>>>>>>>>>> 3) Provide a document outline of the high level
> functional description aimed at a Business Leader (Dick Dickson?)
> >>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
> confluence with links (james or ?)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
> thread.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> thanks
> >>>>>>>>>>>>>>>> James
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com>
> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Sent from my iPhone
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
> inzemamhaq05@gmail.com> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Hi James,
> >>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
> develop a good user reliable website.
> >>>>>>>>>>>>>>>>> Where I can start??
> >>>>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>>> Inzemamul Haq
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
> jamespdailey@gmail.com> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> All -
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been
> 3+ years since we did a clean sweep of it. We also have a front landing
> page at https://fineract.apache.org that could be better at
> communicating the project and community. Who wants to work on this with me?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> PROPOSED CHANGES
> >>>>>>>>>>>>>>>>>> ---
> >>>>>>>>>>>>>>>>>> On the front "Landing" page:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Add blog feed
> >>>>>>>>>>>>>>>>>> Add feed to dev list
> >>>>>>>>>>>>>>>>>> Include FAQ
> >>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we
> should have a top level split on the main page as well, or perhaps a
> separate landing page for FineractCN.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ---
> >>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how
> to show two levels):
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> FAQ
> >>>>>>>>>>>>>>>>>> About Fineract
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> New top level functional descriptions
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> About FineractCN
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> TBD
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Project Management
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to be
> more prominent)
> >>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at
> top)
> >>>>>>>>>>>>>>>>>> Surveys
> >>>>>>>>>>>>>>>>>> Release processes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> How do I get involved?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Committer guides
> >>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
> >>>>>>>>>>>>>>>>>> Standards
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Documentation
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated
> documentation.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc)
> ... all go to blog
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> The current high level structure:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
> >>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
> >>>>>>>>>>>>>>>>>> FINERACT
> >>>>>>>>>>>>>>>>>> FINERACT CN
> >>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
> >>>>>>>>>>>>>>>>>> Fineract Project Security Report
> >>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> How-to articles
> >>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
> >>>>>>>>>>>>>>>>>> Meeting notes
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Sent from Gmail Mobile
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Sent from Gmail Mobile
> >>
> >> --
> >> Sent from Gmail Mobile
>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
I've started to change some of the structure of the wiki. I'm just
trying to clean it up: Does anyone have an objection?
* Noting where content is historical and deprecating it
* Moving the Quarterly PMC reports to slightly more prominence
This is incremental.
Inzemam - can you provide a new design to review taking on the feedback?
On Thu, Mar 9, 2023 at 11:37 AM Meta Cyrus <in...@gmail.com> wrote:
>
> Okay I'll be looking into it..
> Also I am looking forward for GSOC'23 for MIFOS too in the frontend fields. Surely working effectively with both the orgs by making good designs with premium feel.
> Regards,
> Inzemam
>
> On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com> wrote:
>>
>> Please make a set of suggestions or revise your designs based on input.
>>
>> Feel free to dive into this .
>>
>>
>>
>>
>>
>> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com> wrote:
>>>
>>> Hello James,
>>> When we are going to start the work or are we leaving it for future?
>>>
>>> Regards,
>>> Inzemam
>>>
>>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com> wrote:
>>>>
>>>> Hi James,
>>>> You are correct that we need to discuss more on the flows of events and placements. And I am also agree with the point that we can create a slack channel for this.
>>>> Also the code will be in simple html, css and js format so anyone can create/change the things easily. The design is looking fancy and complicated but the code is as smooth as butter. So need to worry about maintainance.
>>>> Regards,
>>>> Inzemamul Haq
>>>>
>>>>
>>>>
>>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com> wrote:
>>>>>
>>>>> Hi - Thank you for this.
>>>>>
>>>>> It's a very good conversation starter. I agreed with most of Javier's comments, which makes clear that we need to do a better job of "Explaining" and "Positioning".
>>>>>
>>>>> ASIDE: Javier - I invite you to write more such text and provide a top level set of bullet points that can be perhaps worked into the content.
>>>>>
>>>>> I think that the design colors are ok, the blue is appropriate for a financial system, meaning steady and trustworthy on the color wheel. Nice.
>>>>>
>>>>> We need more revamping of the content before we can properly do this design, so let's try to attack that problem.
>>>>>
>>>>> Here is a requirement that may not be clear to you:
>>>>> * Site should be very simple, easy to change by anyone opening up a Text Editor and modifying the HTML directly. e.g. use CSS styles and hopefully with names that make sense
>>>>> * Assume that you are gone and someone else has to modify just some text areas, adding content in specific sections.
>>>>> * Assume that no-one touches the website for over a year, maybe three years, and avoid content that can get stale.
>>>>>
>>>>>
>>>>> Message and Content issues:
>>>>>
>>>>> * Fineract is part of Apache and this is not always clear from the page today. Also, there is a common set of links and structure that you can find in other Apache projects. It is not a requirement to follow other Apache projects, but it would be useful to review them for commonalities:
>>>>> --> https://hadoop.apache.org
>>>>> --> https://airflow.apache.org
>>>>> --> https://kafka.apache.org
>>>>>
>>>>> * Note Community is there in each project. Check out the content that each project has.
>>>>>
>>>>> * Key tasks should be up top : Learn more, Help, Download
>>>>> and this should then flow into the requirements for the other sections on the front page and then onto the wiki structure that we need
>>>>>
>>>>> * At this time Fineract-CN should probably not receive equal billing as the Fineract1.x releases it is still trying to get to a first release and fineract1.x is releasing on a regular basis with lots of activity. So, move Fineract-CN to a bottom section that's something about "Additional community technologies"
>>>>> I was and am a big fan of this framework, and I know this positioning is controversial for some, but until we get a release out and lots of active development and deployments, that project remains very much a side project of the community. It may become a very important thing, but for now we should reflect the reality which is that Fineract1.x is where the vast majority of the dev is going on, and the vast majority of the users are there.
>>>>>
>>>>>
>>>>> * We need to emphasize the key features of Fineract - there should be a summary of the system.
>>>>>
>>>>> This may require more chat and discussion on list or on slack and then development of a structure of content before you can really get a design.
>>>>>
>>>>> Thank you again.
>>>>>
>>>>> James Dailey
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>
>>>>>> Hello James,
>>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>>> Regards,
>>>>>> Inzemamul Haq
>>>>>>
>>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hello Javier,
>>>>>>> Thanks for your feedback. The points you mentioned, I'll implement them as you suggested now what I need is some more brief about the topics. This was the just an idea of how it'll look like surely we can change and add the things.
>>>>>>> As you mentioned in the last that it's a template but it's not. It's designed by me on the figma and the assets I used are open source so their will be no licencing issue. I always go for the development through scratch so no need to worry about that.
>>>>>>> Regards,
>>>>>>> Inzemam
>>>>>>>
>>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io> wrote:
>>>>>>>>
>>>>>>>> Hy Meta,
>>>>>>>>
>>>>>>>> Great job; I like the enhancement of the visuals and aesthetic in general, and it seems much more modern and suitable for the next stage of our community.
>>>>>>>>
>>>>>>>> My two cents:
>>>>>>>>
>>>>>>>> It is too linked with banks. Fineract has proved to be useful in other areas of the industry, not just banks. We need to convey that Fineract is a platform for many use cases. Using a mobile phone and a credit card as our visuals will put us in the last 20 years of the industry, and we are in the next 20 years. The images we need to use has to be conceptual, not rigid on old paradigms.
>>>>>>>> Fineract is a backend. Fineract will help the financial industry transcend from the old paradigm of "save deposit boxes" to the new paradigm of "Internet switches," allowing the users of financial institutions to move their assets worldwide quickly and safely. All purchases are now digital.
>>>>>>>> Fineract is not Fineract CN, and Fineract CN can not have the same exposure on our website as Fineract. Fineract CN it's still an experiment while most of our community depends on and uses Fineract. This must be clearly shown on the website and the real estate we dedicate to each one. Fineract CN wasn't the project incubated originally, and Fineract CN is not backward compatible with Fineract.
>>>>>>>> The project we are proud of: I will only use the project part if we get three Fortune 500 companies using Fineract. It will also open a new can of worms on which project gets selected and which criteria we should use, on top of getting the right set of approvals from them to be used as projects.
>>>>>>>> Last but not least, you used a template for the design. We need the license of that template that allows us to use it without limitations, and the template license is aligned with Apache 2.0.
>>>>>>>>
>>>>>>>> Javier
>>>>>>>>
>>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi James,
>>>>>>>>> Below is the drive link of complete page screenshot of APACHE FINERACT redesigned website. Please review and let me know if you have any questions or changes needed.
>>>>>>>>>
>>>>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Inzemamul Haq
>>>>>>>>>
>>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Okay lemme begin the work.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi
>>>>>>>>>>>>> I've been through the website and got it closely that what exact is there on the website. I'll create a static mockup for the website.
>>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone new or experienced first comes to the website got confused of what's happening and how things are going we can work upon it.
>>>>>>>>>>>>> Also I have a question are we going to implement blogger on that website? I have ability to work on static websites where the data comes from dynamic CMS.
>>>>>>>>>>>>> So I can work on tha too....
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Inzemamul Haq -
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Appreciate the response. This is revising our single page website for the project, so not an app. The content needs to be largely static or to pick up content we regularly post on blog. The current site is basic html. Just making sure we’re talking about the same thing.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Fineract.Apache.org
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a design lens, in my view. But, a good UIX process does start with who’s the audience and what’s their need when they land on the page.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>> First I will create mockup using the figma where we can get a better Idea of what exactly has to be happen. By the 16th of Feb I'll come up with a design also will share here in the thread and we can get comments in the meeting.
>>>>>>>>>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We have four people who said they'd like to be involved.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and then we can share back here on list and also hold a meeting on zoom in mid February.
>>>>>>>>>>>>>>>> Feb 16th?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Proposed Tasks:
>>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is there a gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections you think belong being "brought over". compile a list of those pages. If none, great.
>>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the landing page (Meta Cyrus?)
>>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing pages that you like
>>>>>>>>>>>>>>>> 3) Provide a document outline of the high level functional description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence with links (james or ?)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>>>> James
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi James,
>>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and develop a good user reliable website.
>>>>>>>>>>>>>>>>> Where I can start??
>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> All -
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years since we did a clean sweep of it. We also have a front landing page at https://fineract.apache.org that could be better at communicating the project and community. Who wants to work on this with me?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Add blog feed
>>>>>>>>>>>>>>>>>> Add feed to dev list
>>>>>>>>>>>>>>>>>> Include FAQ
>>>>>>>>>>>>>>>>>> Split FineractCN and Fineract
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should have a top level split on the main page as well, or perhaps a separate landing page for FineractCN.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to show two levels):
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> FAQ
>>>>>>>>>>>>>>>>>> About Fineract
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> New top level functional descriptions
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> About FineractCN
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> TBD
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Project Management
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Quarterly reports to the Apache Board (this needs to be more prominent)
>>>>>>>>>>>>>>>>>> Community meetings organized by date (most recent at top)
>>>>>>>>>>>>>>>>>> Surveys
>>>>>>>>>>>>>>>>>> Release processes
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> How do I get involved?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Committer guides
>>>>>>>>>>>>>>>>>> Links to JIRA and GitHUB
>>>>>>>>>>>>>>>>>> Standards
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Documentation
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Replace with links to the new dynamically generated documentation.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Move Comms related stuff (talks, opinion pieces, etc) ... all go to blog
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> FAQ (frequently asked questions)
>>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>>>>>>>> FINERACT
>>>>>>>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> How-to articles
>>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sent from Gmail Mobile
>>
>> --
>> Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Okay I'll be looking into it..
Also I am looking forward for GSOC'23 for MIFOS too in the frontend
fields. Surely working effectively with both the orgs by making good
designs with premium feel.
Regards,
Inzemam
On Fri, 10 Mar, 2023, 1:03 am James Dailey, <ja...@gmail.com> wrote:
> Please make a set of suggestions or revise your designs based on input.
>
> Feel free to dive into this .
>
>
>
>
>
> On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com> wrote:
>
>> Hello James,
>> When we are going to start the work or are we leaving it for future?
>>
>> Regards,
>> Inzemam
>>
>> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com> wrote:
>>
>>> Hi James,
>>> You are correct that we need to discuss more on the flows of events and
>>> placements. And I am also agree with the point that we can create a slack
>>> channel for this.
>>> Also the code will be in simple html, css and js format so anyone can
>>> create/change the things easily. The design is looking fancy and
>>> complicated but the code is as smooth as butter. So need to worry about
>>> maintainance.
>>> Regards,
>>> Inzemamul Haq
>>>
>>>
>>>
>>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> Hi - Thank you for this.
>>>>
>>>> It's a very good conversation starter. I agreed with most of Javier's
>>>> comments, which makes clear that we need to do a better job of "Explaining"
>>>> and "Positioning".
>>>>
>>>> ASIDE: Javier - I invite you to write more such text and provide a top
>>>> level set of bullet points that can be perhaps worked into the content.
>>>>
>>>> I think that the design colors are ok, the blue is appropriate for a
>>>> financial system, meaning steady and trustworthy on the color wheel. Nice.
>>>>
>>>> We need more revamping of the content before we can properly do this
>>>> design, so let's try to attack that problem.
>>>>
>>>> Here is a requirement that may not be clear to you:
>>>> * Site should be very simple, easy to change by anyone opening up a
>>>> Text Editor and modifying the HTML directly. e.g. use CSS styles and
>>>> hopefully with names that make sense
>>>> * Assume that you are gone and someone else has to modify just some
>>>> text areas, adding content in specific sections.
>>>> * Assume that no-one touches the website for over a year, maybe three
>>>> years, and avoid content that can get stale.
>>>>
>>>>
>>>> Message and Content issues:
>>>>
>>>> * Fineract is part of Apache and this is not always clear from the page
>>>> today. Also, there is a common set of links and structure that you can find
>>>> in other Apache projects. It is not a requirement to follow other Apache
>>>> projects, but it would be useful to review them for commonalities:
>>>> --> https://hadoop.apache.org
>>>> --> https://airflow.apache.org
>>>> --> https://kafka.apache.org
>>>>
>>>> * Note Community is there in each project. Check out the content that
>>>> each project has.
>>>>
>>>> * Key tasks should be up top : Learn more, Help, Download
>>>> and this should then flow into the requirements for the other sections
>>>> on the front page and then onto the wiki structure that we need
>>>>
>>>> * At this time Fineract-CN should probably not receive equal billing as
>>>> the Fineract1.x releases it is still trying to get to a first release and
>>>> fineract1.x is releasing on a regular basis with lots of activity. So,
>>>> move Fineract-CN to a bottom section that's something about "Additional
>>>> community technologies"
>>>> I was and am a big fan of this framework, and I know this positioning
>>>> is controversial for some, but until we get a release out and lots of
>>>> active development and deployments, that project remains very much a side
>>>> project of the community. It may become a very important thing, but for
>>>> now we should reflect the reality which is that Fineract1.x is where the
>>>> vast majority of the dev is going on, and the vast majority of the users
>>>> are there.
>>>>
>>>>
>>>> * We need to emphasize the key features of Fineract - there should be a
>>>> summary of the system.
>>>>
>>>> This may require more chat and discussion on list or on slack and then
>>>> development of a structure of content before you can really get a design.
>>>>
>>>> Thank you again.
>>>>
>>>> James Dailey
>>>>
>>>>
>>>>
>>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hello James,
>>>>> Have you reviewed the website frame. Please share the feedback.
>>>>> Regards,
>>>>> Inzemamul Haq
>>>>>
>>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hello Javier,
>>>>>> Thanks for your feedback. The points you mentioned, I'll implement
>>>>>> them as you suggested now what I need is some more brief about the topics.
>>>>>> This was the just an idea of how it'll look like surely we can change and
>>>>>> add the things.
>>>>>> As you mentioned in the last that it's a template but it's not. It's
>>>>>> designed by me on the figma and the assets I used are open source so their
>>>>>> will be no licencing issue. I always go for the development through scratch
>>>>>> so no need to worry about that.
>>>>>> Regards,
>>>>>> Inzemam
>>>>>>
>>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io>
>>>>>> wrote:
>>>>>>
>>>>>>> Hy Meta,
>>>>>>>
>>>>>>> Great job; I like the enhancement of the visuals and aesthetic in
>>>>>>> general, and it seems much more modern and suitable for the next stage of
>>>>>>> our community.
>>>>>>>
>>>>>>> My two cents:
>>>>>>>
>>>>>>> - It is too linked with banks. Fineract has proved to be useful
>>>>>>> in other areas of the industry, not just banks. We need to convey that
>>>>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>>>> industry, and *we are *in *the next 20 years.* The images we
>>>>>>> need to use has to be conceptual, not rigid on old paradigms.
>>>>>>> - Fineract is a backend. Fineract will help the financial
>>>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>>>> purchases are now digital.
>>>>>>> - Fineract is not Fineract CN, and Fineract CN can not have the
>>>>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>>>> CN is not backward compatible with Fineract.
>>>>>>> - The project we are proud of: I will only use the project part
>>>>>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>>>>>> new can of worms on which project gets selected and which criteria we
>>>>>>> should use, on top of getting the right set of approvals from them to be
>>>>>>> used as projects.
>>>>>>> - Last but not least, you used a template for the design. We
>>>>>>> need the license of that template that allows us to use it without
>>>>>>> limitations, and the template license is aligned with Apache 2.0.
>>>>>>>
>>>>>>> Javier
>>>>>>>
>>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi James,
>>>>>>>> Below is the drive link of complete page screenshot of APACHE
>>>>>>>> FINERACT redesigned website. Please review and let me know if you have any
>>>>>>>> questions or changes needed.
>>>>>>>>
>>>>>>>>
>>>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Inzemamul Haq
>>>>>>>>
>>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Okay lemme begin the work.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <
>>>>>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi
>>>>>>>>>>>> I've been through the website and got it closely that what
>>>>>>>>>>>> exact is there on the website. I'll create a static mockup for the website.
>>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone new
>>>>>>>>>>>> or experienced first comes to the website got confused of what's happening
>>>>>>>>>>>> and how things are going we can work upon it.
>>>>>>>>>>>> Also I have a question are we going to implement blogger on
>>>>>>>>>>>> that website? I have ability to work on static websites where the data
>>>>>>>>>>>> comes from dynamic CMS.
>>>>>>>>>>>> So I can work on tha too....
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Inzemamul Haq -
>>>>>>>>>>>>>
>>>>>>>>>>>>> Appreciate the response. This is revising our single page
>>>>>>>>>>>>> website for the project, so not an app. The content needs to be largely
>>>>>>>>>>>>> static or to pick up content we regularly post on blog. The current site is
>>>>>>>>>>>>> basic html. Just making sure we’re talking about the same thing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Fineract.Apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a
>>>>>>>>>>>>> design lens, in my view. But, a good UIX process does start with who’s the
>>>>>>>>>>>>> audience and what’s their need when they land on the page.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>>>>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>> First I will create mockup using the figma where we can get a
>>>>>>>>>>>>>> better Idea of what exactly has to be happen. By the 16th of Feb I'll come
>>>>>>>>>>>>>> up with a design also will share here in the thread and we can get comments
>>>>>>>>>>>>>> in the meeting.
>>>>>>>>>>>>>> I'll start looking other apache websites and get an overall
>>>>>>>>>>>>>> UI/UX
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> All those that volunteered for this - thank you. We have
>>>>>>>>>>>>>>> four people who said they'd like to be involved.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and then
>>>>>>>>>>>>>>> we can share back here on list and also hold a meeting on zoom in mid
>>>>>>>>>>>>>>> February.
>>>>>>>>>>>>>>> Feb 16th?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> First, everyone involved should read (or skim) this
>>>>>>>>>>>>>>> document:
>>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>>>>>>> and also look at the current wiki and landing page in
>>>>>>>>>>>>>>> detail.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Proposed Tasks:
>>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is there
>>>>>>>>>>>>>>> a gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>>>>>>> --> also, scan the current wiki and find sections you
>>>>>>>>>>>>>>> think belong being "brought over". compile a list of those pages. If
>>>>>>>>>>>>>>> none, great.
>>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the
>>>>>>>>>>>>>>> landing page (Meta Cyrus?)
>>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing
>>>>>>>>>>>>>>> pages that you like
>>>>>>>>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on
>>>>>>>>>>>>>>> confluence with links (james or ?)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this
>>>>>>>>>>>>>>> thread.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>>> James
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>>>>>>>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi James,
>>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
>>>>>>>>>>>>>>>> develop a good user reliable website.
>>>>>>>>>>>>>>>> Where I can start??
>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> All -
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+
>>>>>>>>>>>>>>>>> years since we did a clean sweep of it. We also have a front landing page
>>>>>>>>>>>>>>>>> at https://fineract.apache.org that could be better at
>>>>>>>>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>>>>>>>>> me?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> - Add blog feed
>>>>>>>>>>>>>>>>> - Add feed to dev list
>>>>>>>>>>>>>>>>> - Include FAQ
>>>>>>>>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we
>>>>>>>>>>>>>>>>> should have a top level split on the main page as well, or perhaps a
>>>>>>>>>>>>>>>>> separate landing page for FineractCN.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to
>>>>>>>>>>>>>>>>> show two levels):
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> - FAQ
>>>>>>>>>>>>>>>>> - About Fineract
>>>>>>>>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>>>>>>>>> - About FineractCN
>>>>>>>>>>>>>>>>> - TBD
>>>>>>>>>>>>>>>>> - Project Management
>>>>>>>>>>>>>>>>> - Quarterly reports to the Apache Board (this needs
>>>>>>>>>>>>>>>>> to be more prominent)
>>>>>>>>>>>>>>>>> - Community meetings organized by date (most recent
>>>>>>>>>>>>>>>>> at top)
>>>>>>>>>>>>>>>>> - Surveys
>>>>>>>>>>>>>>>>> - Release processes
>>>>>>>>>>>>>>>>> - How do I get involved?
>>>>>>>>>>>>>>>>> - Committer guides
>>>>>>>>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>>>>>>>>> - Standards
>>>>>>>>>>>>>>>>> - Documentation
>>>>>>>>>>>>>>>>> - Replace with links to the new dynamically
>>>>>>>>>>>>>>>>> generated documentation.
>>>>>>>>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces,
>>>>>>>>>>>>>>>>> etc) ... all go to blog
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> FINERACT
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> How-to articles
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>
>>>>>>>> --
> Sent from Gmail Mobile
>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Please make a set of suggestions or revise your designs based on input.
Feel free to dive into this .
On Thu, Mar 9, 2023 at 9:54 AM Meta Cyrus <in...@gmail.com> wrote:
> Hello James,
> When we are going to start the work or are we leaving it for future?
>
> Regards,
> Inzemam
>
> On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com> wrote:
>
>> Hi James,
>> You are correct that we need to discuss more on the flows of events and
>> placements. And I am also agree with the point that we can create a slack
>> channel for this.
>> Also the code will be in simple html, css and js format so anyone can
>> create/change the things easily. The design is looking fancy and
>> complicated but the code is as smooth as butter. So need to worry about
>> maintainance.
>> Regards,
>> Inzemamul Haq
>>
>>
>>
>> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> Hi - Thank you for this.
>>>
>>> It's a very good conversation starter. I agreed with most of Javier's
>>> comments, which makes clear that we need to do a better job of "Explaining"
>>> and "Positioning".
>>>
>>> ASIDE: Javier - I invite you to write more such text and provide a top
>>> level set of bullet points that can be perhaps worked into the content.
>>>
>>> I think that the design colors are ok, the blue is appropriate for a
>>> financial system, meaning steady and trustworthy on the color wheel. Nice.
>>>
>>> We need more revamping of the content before we can properly do this
>>> design, so let's try to attack that problem.
>>>
>>> Here is a requirement that may not be clear to you:
>>> * Site should be very simple, easy to change by anyone opening up a Text
>>> Editor and modifying the HTML directly. e.g. use CSS styles and hopefully
>>> with names that make sense
>>> * Assume that you are gone and someone else has to modify just some text
>>> areas, adding content in specific sections.
>>> * Assume that no-one touches the website for over a year, maybe three
>>> years, and avoid content that can get stale.
>>>
>>>
>>> Message and Content issues:
>>>
>>> * Fineract is part of Apache and this is not always clear from the page
>>> today. Also, there is a common set of links and structure that you can find
>>> in other Apache projects. It is not a requirement to follow other Apache
>>> projects, but it would be useful to review them for commonalities:
>>> --> https://hadoop.apache.org
>>> --> https://airflow.apache.org
>>> --> https://kafka.apache.org
>>>
>>> * Note Community is there in each project. Check out the content that
>>> each project has.
>>>
>>> * Key tasks should be up top : Learn more, Help, Download
>>> and this should then flow into the requirements for the other sections
>>> on the front page and then onto the wiki structure that we need
>>>
>>> * At this time Fineract-CN should probably not receive equal billing as
>>> the Fineract1.x releases it is still trying to get to a first release and
>>> fineract1.x is releasing on a regular basis with lots of activity. So,
>>> move Fineract-CN to a bottom section that's something about "Additional
>>> community technologies"
>>> I was and am a big fan of this framework, and I know this positioning is
>>> controversial for some, but until we get a release out and lots of active
>>> development and deployments, that project remains very much a side project
>>> of the community. It may become a very important thing, but for now we
>>> should reflect the reality which is that Fineract1.x is where the vast
>>> majority of the dev is going on, and the vast majority of the users are
>>> there.
>>>
>>>
>>> * We need to emphasize the key features of Fineract - there should be a
>>> summary of the system.
>>>
>>> This may require more chat and discussion on list or on slack and then
>>> development of a structure of content before you can really get a design.
>>>
>>> Thank you again.
>>>
>>> James Dailey
>>>
>>>
>>>
>>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>>> Hello James,
>>>> Have you reviewed the website frame. Please share the feedback.
>>>> Regards,
>>>> Inzemamul Haq
>>>>
>>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Javier,
>>>>> Thanks for your feedback. The points you mentioned, I'll implement
>>>>> them as you suggested now what I need is some more brief about the topics.
>>>>> This was the just an idea of how it'll look like surely we can change and
>>>>> add the things.
>>>>> As you mentioned in the last that it's a template but it's not. It's
>>>>> designed by me on the figma and the assets I used are open source so their
>>>>> will be no licencing issue. I always go for the development through scratch
>>>>> so no need to worry about that.
>>>>> Regards,
>>>>> Inzemam
>>>>>
>>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io>
>>>>> wrote:
>>>>>
>>>>>> Hy Meta,
>>>>>>
>>>>>> Great job; I like the enhancement of the visuals and aesthetic in
>>>>>> general, and it seems much more modern and suitable for the next stage of
>>>>>> our community.
>>>>>>
>>>>>> My two cents:
>>>>>>
>>>>>> - It is too linked with banks. Fineract has proved to be useful
>>>>>> in other areas of the industry, not just banks. We need to convey that
>>>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>>> industry, and *we are *in *the next 20 years.* The images we need
>>>>>> to use has to be conceptual, not rigid on old paradigms.
>>>>>> - Fineract is a backend. Fineract will help the financial
>>>>>> industry transcend from the old paradigm of "save deposit boxes" to the new
>>>>>> paradigm of "Internet switches," allowing the users of financial
>>>>>> institutions to move their assets worldwide quickly and safely. All
>>>>>> purchases are now digital.
>>>>>> - Fineract is not Fineract CN, and Fineract CN can not have the
>>>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>>> CN is not backward compatible with Fineract.
>>>>>> - The project we are proud of: I will only use the project part
>>>>>> if we get three Fortune 500 companies using Fineract. It will also open a
>>>>>> new can of worms on which project gets selected and which criteria we
>>>>>> should use, on top of getting the right set of approvals from them to be
>>>>>> used as projects.
>>>>>> - Last but not least, you used a template for the design. We need
>>>>>> the license of that template that allows us to use it without limitations,
>>>>>> and the template license is aligned with Apache 2.0.
>>>>>>
>>>>>> Javier
>>>>>>
>>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi James,
>>>>>>> Below is the drive link of complete page screenshot of APACHE
>>>>>>> FINERACT redesigned website. Please review and let me know if you have any
>>>>>>> questions or changes needed.
>>>>>>>
>>>>>>>
>>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>>>
>>>>>>> Regards,
>>>>>>> Inzemamul Haq
>>>>>>>
>>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Meta - Any updates from you on this?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Okay lemme begin the work.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <
>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi
>>>>>>>>>>> I've been through the website and got it closely that what exact
>>>>>>>>>>> is there on the website. I'll create a static mockup for the website.
>>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone new
>>>>>>>>>>> or experienced first comes to the website got confused of what's happening
>>>>>>>>>>> and how things are going we can work upon it.
>>>>>>>>>>> Also I have a question are we going to implement blogger on
>>>>>>>>>>> that website? I have ability to work on static websites where the data
>>>>>>>>>>> comes from dynamic CMS.
>>>>>>>>>>> So I can work on tha too....
>>>>>>>>>>> Regards,
>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>
>>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Inzemamul Haq -
>>>>>>>>>>>>
>>>>>>>>>>>> Appreciate the response. This is revising our single page
>>>>>>>>>>>> website for the project, so not an app. The content needs to be largely
>>>>>>>>>>>> static or to pick up content we regularly post on blog. The current site is
>>>>>>>>>>>> basic html. Just making sure we’re talking about the same thing.
>>>>>>>>>>>>
>>>>>>>>>>>> Fineract.Apache.org
>>>>>>>>>>>>
>>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a
>>>>>>>>>>>> design lens, in my view. But, a good UIX process does start with who’s the
>>>>>>>>>>>> audience and what’s their need when they land on the page.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>>>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>> First I will create mockup using the figma where we can get a
>>>>>>>>>>>>> better Idea of what exactly has to be happen. By the 16th of Feb I'll come
>>>>>>>>>>>>> up with a design also will share here in the thread and we can get comments
>>>>>>>>>>>>> in the meeting.
>>>>>>>>>>>>> I'll start looking other apache websites and get an overall
>>>>>>>>>>>>> UI/UX
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> All those that volunteered for this - thank you. We have
>>>>>>>>>>>>>> four people who said they'd like to be involved.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have a few tasks that I think may suit this group and then
>>>>>>>>>>>>>> we can share back here on list and also hold a meeting on zoom in mid
>>>>>>>>>>>>>> February.
>>>>>>>>>>>>>> Feb 16th?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Proposed Tasks:
>>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is there a
>>>>>>>>>>>>>> gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>>>>>> --> also, scan the current wiki and find sections you
>>>>>>>>>>>>>> think belong being "brought over". compile a list of those pages. If
>>>>>>>>>>>>>> none, great.
>>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the landing
>>>>>>>>>>>>>> page (Meta Cyrus?)
>>>>>>>>>>>>>> --> also, scan other Apache projects to find landing
>>>>>>>>>>>>>> pages that you like
>>>>>>>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence
>>>>>>>>>>>>>> with links (james or ?)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>> James
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <
>>>>>>>>>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi James,
>>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
>>>>>>>>>>>>>>> develop a good user reliable website.
>>>>>>>>>>>>>>> Where I can start??
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> All -
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+
>>>>>>>>>>>>>>>> years since we did a clean sweep of it. We also have a front landing page
>>>>>>>>>>>>>>>> at https://fineract.apache.org that could be better at
>>>>>>>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>>>>>>>> me?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> - Add blog feed
>>>>>>>>>>>>>>>> - Add feed to dev list
>>>>>>>>>>>>>>>> - Include FAQ
>>>>>>>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we
>>>>>>>>>>>>>>>> should have a top level split on the main page as well, or perhaps a
>>>>>>>>>>>>>>>> separate landing page for FineractCN.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to
>>>>>>>>>>>>>>>> show two levels):
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> - FAQ
>>>>>>>>>>>>>>>> - About Fineract
>>>>>>>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>>>>>>>> - About FineractCN
>>>>>>>>>>>>>>>> - TBD
>>>>>>>>>>>>>>>> - Project Management
>>>>>>>>>>>>>>>> - Quarterly reports to the Apache Board (this needs
>>>>>>>>>>>>>>>> to be more prominent)
>>>>>>>>>>>>>>>> - Community meetings organized by date (most recent
>>>>>>>>>>>>>>>> at top)
>>>>>>>>>>>>>>>> - Surveys
>>>>>>>>>>>>>>>> - Release processes
>>>>>>>>>>>>>>>> - How do I get involved?
>>>>>>>>>>>>>>>> - Committer guides
>>>>>>>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>>>>>>>> - Standards
>>>>>>>>>>>>>>>> - Documentation
>>>>>>>>>>>>>>>> - Replace with links to the new dynamically
>>>>>>>>>>>>>>>> generated documentation.
>>>>>>>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces,
>>>>>>>>>>>>>>>> etc) ... all go to blog
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> FINERACT
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> How-to articles
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>> Sent from Gmail Mobile
>>>>>>>>
>>>>>>> --
Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Hello James,
When we are going to start the work or are we leaving it for future?
Regards,
Inzemam
On Sun, 26 Feb, 2023, 7:40 am Meta Cyrus, <in...@gmail.com> wrote:
> Hi James,
> You are correct that we need to discuss more on the flows of events and
> placements. And I am also agree with the point that we can create a slack
> channel for this.
> Also the code will be in simple html, css and js format so anyone can
> create/change the things easily. The design is looking fancy and
> complicated but the code is as smooth as butter. So need to worry about
> maintainance.
> Regards,
> Inzemamul Haq
>
>
>
> On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com>
> wrote:
>
>> Hi - Thank you for this.
>>
>> It's a very good conversation starter. I agreed with most of Javier's
>> comments, which makes clear that we need to do a better job of "Explaining"
>> and "Positioning".
>>
>> ASIDE: Javier - I invite you to write more such text and provide a top
>> level set of bullet points that can be perhaps worked into the content.
>>
>> I think that the design colors are ok, the blue is appropriate for a
>> financial system, meaning steady and trustworthy on the color wheel. Nice.
>>
>> We need more revamping of the content before we can properly do this
>> design, so let's try to attack that problem.
>>
>> Here is a requirement that may not be clear to you:
>> * Site should be very simple, easy to change by anyone opening up a Text
>> Editor and modifying the HTML directly. e.g. use CSS styles and hopefully
>> with names that make sense
>> * Assume that you are gone and someone else has to modify just some text
>> areas, adding content in specific sections.
>> * Assume that no-one touches the website for over a year, maybe three
>> years, and avoid content that can get stale.
>>
>>
>> Message and Content issues:
>>
>> * Fineract is part of Apache and this is not always clear from the page
>> today. Also, there is a common set of links and structure that you can find
>> in other Apache projects. It is not a requirement to follow other Apache
>> projects, but it would be useful to review them for commonalities:
>> --> https://hadoop.apache.org
>> --> https://airflow.apache.org
>> --> https://kafka.apache.org
>>
>> * Note Community is there in each project. Check out the content that
>> each project has.
>>
>> * Key tasks should be up top : Learn more, Help, Download
>> and this should then flow into the requirements for the other sections on
>> the front page and then onto the wiki structure that we need
>>
>> * At this time Fineract-CN should probably not receive equal billing as
>> the Fineract1.x releases it is still trying to get to a first release and
>> fineract1.x is releasing on a regular basis with lots of activity. So,
>> move Fineract-CN to a bottom section that's something about "Additional
>> community technologies"
>> I was and am a big fan of this framework, and I know this positioning is
>> controversial for some, but until we get a release out and lots of active
>> development and deployments, that project remains very much a side project
>> of the community. It may become a very important thing, but for now we
>> should reflect the reality which is that Fineract1.x is where the vast
>> majority of the dev is going on, and the vast majority of the users are
>> there.
>>
>>
>> * We need to emphasize the key features of Fineract - there should be a
>> summary of the system.
>>
>> This may require more chat and discussion on list or on slack and then
>> development of a structure of content before you can really get a design.
>>
>> Thank you again.
>>
>> James Dailey
>>
>>
>>
>> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>>
>>> Hello James,
>>> Have you reviewed the website frame. Please share the feedback.
>>> Regards,
>>> Inzemamul Haq
>>>
>>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com>
>>> wrote:
>>>
>>>> Hello Javier,
>>>> Thanks for your feedback. The points you mentioned, I'll implement them
>>>> as you suggested now what I need is some more brief about the topics. This
>>>> was the just an idea of how it'll look like surely we can change and add
>>>> the things.
>>>> As you mentioned in the last that it's a template but it's not. It's
>>>> designed by me on the figma and the assets I used are open source so their
>>>> will be no licencing issue. I always go for the development through scratch
>>>> so no need to worry about that.
>>>> Regards,
>>>> Inzemam
>>>>
>>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io>
>>>> wrote:
>>>>
>>>>> Hy Meta,
>>>>>
>>>>> Great job; I like the enhancement of the visuals and aesthetic in
>>>>> general, and it seems much more modern and suitable for the next stage of
>>>>> our community.
>>>>>
>>>>> My two cents:
>>>>>
>>>>> - It is too linked with banks. Fineract has proved to be useful in
>>>>> other areas of the industry, not just banks. We need to convey that
>>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>>> credit card as our visuals will put us in the last 20 years of the
>>>>> industry, and *we are *in *the next 20 years.* The images we need
>>>>> to use has to be conceptual, not rigid on old paradigms.
>>>>> - Fineract is a backend. Fineract will help the financial industry
>>>>> transcend from the old paradigm of "save deposit boxes" to the new paradigm
>>>>> of "Internet switches," allowing the users of financial institutions to
>>>>> move their assets worldwide quickly and safely. All purchases are now
>>>>> digital.
>>>>> - Fineract is not Fineract CN, and Fineract CN can not have the
>>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>>> experiment while most of our community depends on and uses Fineract. This
>>>>> must be clearly shown on the website and the real estate we dedicate to
>>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>>> CN is not backward compatible with Fineract.
>>>>> - The project we are proud of: I will only use the project part if
>>>>> we get three Fortune 500 companies using Fineract. It will also open a new
>>>>> can of worms on which project gets selected and which criteria we should
>>>>> use, on top of getting the right set of approvals from them to be used as
>>>>> projects.
>>>>> - Last but not least, you used a template for the design. We need
>>>>> the license of that template that allows us to use it without limitations,
>>>>> and the template license is aligned with Apache 2.0.
>>>>>
>>>>> Javier
>>>>>
>>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi James,
>>>>>> Below is the drive link of complete page screenshot of APACHE
>>>>>> FINERACT redesigned website. Please review and let me know if you have any
>>>>>> questions or changes needed.
>>>>>>
>>>>>>
>>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>>
>>>>>> Regards,
>>>>>> Inzemamul Haq
>>>>>>
>>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Meta - Any updates from you on this?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Okay lemme begin the work.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi
>>>>>>>>>> I've been through the website and got it closely that what exact
>>>>>>>>>> is there on the website. I'll create a static mockup for the website.
>>>>>>>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>>>>>>>> experienced first comes to the website got confused of what's happening and
>>>>>>>>>> how things are going we can work upon it.
>>>>>>>>>> Also I have a question are we going to implement blogger on
>>>>>>>>>> that website? I have ability to work on static websites where the data
>>>>>>>>>> comes from dynamic CMS.
>>>>>>>>>> So I can work on tha too....
>>>>>>>>>> Regards,
>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>
>>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Inzemamul Haq -
>>>>>>>>>>>
>>>>>>>>>>> Appreciate the response. This is revising our single page
>>>>>>>>>>> website for the project, so not an app. The content needs to be largely
>>>>>>>>>>> static or to pick up content we regularly post on blog. The current site is
>>>>>>>>>>> basic html. Just making sure we’re talking about the same thing.
>>>>>>>>>>>
>>>>>>>>>>> Fineract.Apache.org
>>>>>>>>>>>
>>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a
>>>>>>>>>>> design lens, in my view. But, a good UIX process does start with who’s the
>>>>>>>>>>> audience and what’s their need when they land on the page.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>> First I will create mockup using the figma where we can get a
>>>>>>>>>>>> better Idea of what exactly has to be happen. By the 16th of Feb I'll come
>>>>>>>>>>>> up with a design also will share here in the thread and we can get comments
>>>>>>>>>>>> in the meeting.
>>>>>>>>>>>> I'll start looking other apache websites and get an overall
>>>>>>>>>>>> UI/UX
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>>>>>>>> people who said they'd like to be involved.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have a few tasks that I think may suit this group and then
>>>>>>>>>>>>> we can share back here on list and also hold a meeting on zoom in mid
>>>>>>>>>>>>> February.
>>>>>>>>>>>>> Feb 16th?
>>>>>>>>>>>>>
>>>>>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Proposed Tasks:
>>>>>>>>>>>>> 1) Comment - is the document clear enough or where is there a
>>>>>>>>>>>>> gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>>>>> --> also, scan the current wiki and find sections you
>>>>>>>>>>>>> think belong being "brought over". compile a list of those pages. If
>>>>>>>>>>>>> none, great.
>>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the landing
>>>>>>>>>>>>> page (Meta Cyrus?)
>>>>>>>>>>>>> --> also, scan other Apache projects to find landing pages
>>>>>>>>>>>>> that you like
>>>>>>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence
>>>>>>>>>>>>> with links (james or ?)
>>>>>>>>>>>>>
>>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> thanks
>>>>>>>>>>>>> James
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi James,
>>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and
>>>>>>>>>>>>>> develop a good user reliable website.
>>>>>>>>>>>>>> Where I can start??
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> All -
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+
>>>>>>>>>>>>>>> years since we did a clean sweep of it. We also have a front landing page
>>>>>>>>>>>>>>> at https://fineract.apache.org that could be better at
>>>>>>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>>>>>>> me?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> - Add blog feed
>>>>>>>>>>>>>>> - Add feed to dev list
>>>>>>>>>>>>>>> - Include FAQ
>>>>>>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we
>>>>>>>>>>>>>>> should have a top level split on the main page as well, or perhaps a
>>>>>>>>>>>>>>> separate landing page for FineractCN.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to
>>>>>>>>>>>>>>> show two levels):
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> - FAQ
>>>>>>>>>>>>>>> - About Fineract
>>>>>>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>>>>>>> - About FineractCN
>>>>>>>>>>>>>>> - TBD
>>>>>>>>>>>>>>> - Project Management
>>>>>>>>>>>>>>> - Quarterly reports to the Apache Board (this needs
>>>>>>>>>>>>>>> to be more prominent)
>>>>>>>>>>>>>>> - Community meetings organized by date (most recent
>>>>>>>>>>>>>>> at top)
>>>>>>>>>>>>>>> - Surveys
>>>>>>>>>>>>>>> - Release processes
>>>>>>>>>>>>>>> - How do I get involved?
>>>>>>>>>>>>>>> - Committer guides
>>>>>>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>>>>>>> - Standards
>>>>>>>>>>>>>>> - Documentation
>>>>>>>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>>>>>>>> documentation.
>>>>>>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces,
>>>>>>>>>>>>>>> etc) ... all go to blog
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> FINERACT
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> How-to articles
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>> Sent from Gmail Mobile
>>>>>>>
>>>>>>
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Hi James,
You are correct that we need to discuss more on the flows of events and
placements. And I am also agree with the point that we can create a slack
channel for this.
Also the code will be in simple html, css and js format so anyone can
create/change the things easily. The design is looking fancy and
complicated but the code is as smooth as butter. So need to worry about
maintainance.
Regards,
Inzemamul Haq
On Sun, 26 Feb, 2023, 1:35 am James Dailey, <ja...@gmail.com> wrote:
> Hi - Thank you for this.
>
> It's a very good conversation starter. I agreed with most of Javier's
> comments, which makes clear that we need to do a better job of "Explaining"
> and "Positioning".
>
> ASIDE: Javier - I invite you to write more such text and provide a top
> level set of bullet points that can be perhaps worked into the content.
>
> I think that the design colors are ok, the blue is appropriate for a
> financial system, meaning steady and trustworthy on the color wheel. Nice.
>
> We need more revamping of the content before we can properly do this
> design, so let's try to attack that problem.
>
> Here is a requirement that may not be clear to you:
> * Site should be very simple, easy to change by anyone opening up a Text
> Editor and modifying the HTML directly. e.g. use CSS styles and hopefully
> with names that make sense
> * Assume that you are gone and someone else has to modify just some text
> areas, adding content in specific sections.
> * Assume that no-one touches the website for over a year, maybe three
> years, and avoid content that can get stale.
>
>
> Message and Content issues:
>
> * Fineract is part of Apache and this is not always clear from the page
> today. Also, there is a common set of links and structure that you can find
> in other Apache projects. It is not a requirement to follow other Apache
> projects, but it would be useful to review them for commonalities:
> --> https://hadoop.apache.org
> --> https://airflow.apache.org
> --> https://kafka.apache.org
>
> * Note Community is there in each project. Check out the content that
> each project has.
>
> * Key tasks should be up top : Learn more, Help, Download
> and this should then flow into the requirements for the other sections on
> the front page and then onto the wiki structure that we need
>
> * At this time Fineract-CN should probably not receive equal billing as
> the Fineract1.x releases it is still trying to get to a first release and
> fineract1.x is releasing on a regular basis with lots of activity. So,
> move Fineract-CN to a bottom section that's something about "Additional
> community technologies"
> I was and am a big fan of this framework, and I know this positioning is
> controversial for some, but until we get a release out and lots of active
> development and deployments, that project remains very much a side project
> of the community. It may become a very important thing, but for now we
> should reflect the reality which is that Fineract1.x is where the vast
> majority of the dev is going on, and the vast majority of the users are
> there.
>
>
> * We need to emphasize the key features of Fineract - there should be a
> summary of the system.
>
> This may require more chat and discussion on list or on slack and then
> development of a structure of content before you can really get a design.
>
> Thank you again.
>
> James Dailey
>
>
>
> On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com>
> wrote:
>
>> Hello James,
>> Have you reviewed the website frame. Please share the feedback.
>> Regards,
>> Inzemamul Haq
>>
>> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com> wrote:
>>
>>> Hello Javier,
>>> Thanks for your feedback. The points you mentioned, I'll implement them
>>> as you suggested now what I need is some more brief about the topics. This
>>> was the just an idea of how it'll look like surely we can change and add
>>> the things.
>>> As you mentioned in the last that it's a template but it's not. It's
>>> designed by me on the figma and the assets I used are open source so their
>>> will be no licencing issue. I always go for the development through scratch
>>> so no need to worry about that.
>>> Regards,
>>> Inzemam
>>>
>>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io>
>>> wrote:
>>>
>>>> Hy Meta,
>>>>
>>>> Great job; I like the enhancement of the visuals and aesthetic in
>>>> general, and it seems much more modern and suitable for the next stage of
>>>> our community.
>>>>
>>>> My two cents:
>>>>
>>>> - It is too linked with banks. Fineract has proved to be useful in
>>>> other areas of the industry, not just banks. We need to convey that
>>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>>> credit card as our visuals will put us in the last 20 years of the
>>>> industry, and *we are *in *the next 20 years.* The images we need
>>>> to use has to be conceptual, not rigid on old paradigms.
>>>> - Fineract is a backend. Fineract will help the financial industry
>>>> transcend from the old paradigm of "save deposit boxes" to the new paradigm
>>>> of "Internet switches," allowing the users of financial institutions to
>>>> move their assets worldwide quickly and safely. All purchases are now
>>>> digital.
>>>> - Fineract is not Fineract CN, and Fineract CN can not have the
>>>> same exposure on our website as Fineract. Fineract CN it's still an
>>>> experiment while most of our community depends on and uses Fineract. This
>>>> must be clearly shown on the website and the real estate we dedicate to
>>>> each one. Fineract CN wasn't the project incubated originally, and Fineract
>>>> CN is not backward compatible with Fineract.
>>>> - The project we are proud of: I will only use the project part if
>>>> we get three Fortune 500 companies using Fineract. It will also open a new
>>>> can of worms on which project gets selected and which criteria we should
>>>> use, on top of getting the right set of approvals from them to be used as
>>>> projects.
>>>> - Last but not least, you used a template for the design. We need
>>>> the license of that template that allows us to use it without limitations,
>>>> and the template license is aligned with Apache 2.0.
>>>>
>>>> Javier
>>>>
>>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi James,
>>>>> Below is the drive link of complete page screenshot of APACHE FINERACT
>>>>> redesigned website. Please review and let me know if you have any questions
>>>>> or changes needed.
>>>>>
>>>>>
>>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>>
>>>>> Regards,
>>>>> Inzemamul Haq
>>>>>
>>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Meta - Any updates from you on this?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Okay lemme begin the work.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>> I've been through the website and got it closely that what exact
>>>>>>>>> is there on the website. I'll create a static mockup for the website.
>>>>>>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>>>>>>> experienced first comes to the website got confused of what's happening and
>>>>>>>>> how things are going we can work upon it.
>>>>>>>>> Also I have a question are we going to implement blogger on
>>>>>>>>> that website? I have ability to work on static websites where the data
>>>>>>>>> comes from dynamic CMS.
>>>>>>>>> So I can work on tha too....
>>>>>>>>> Regards,
>>>>>>>>> Inzemamul Haq
>>>>>>>>>
>>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <
>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Inzemamul Haq -
>>>>>>>>>>
>>>>>>>>>> Appreciate the response. This is revising our single page
>>>>>>>>>> website for the project, so not an app. The content needs to be largely
>>>>>>>>>> static or to pick up content we regularly post on blog. The current site is
>>>>>>>>>> basic html. Just making sure we’re talking about the same thing.
>>>>>>>>>>
>>>>>>>>>> Fineract.Apache.org
>>>>>>>>>>
>>>>>>>>>> Figma I associate w more complex flows. What’s needed is a
>>>>>>>>>> design lens, in my view. But, a good UIX process does start with who’s the
>>>>>>>>>> audience and what’s their need when they land on the page.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <
>>>>>>>>>> inzemamhaq05@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>> First I will create mockup using the figma where we can get a
>>>>>>>>>>> better Idea of what exactly has to be happen. By the 16th of Feb I'll come
>>>>>>>>>>> up with a design also will share here in the thread and we can get comments
>>>>>>>>>>> in the meeting.
>>>>>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>
>>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>>>>>>> people who said they'd like to be involved.
>>>>>>>>>>>>
>>>>>>>>>>>> I have a few tasks that I think may suit this group and then we
>>>>>>>>>>>> can share back here on list and also hold a meeting on zoom in mid
>>>>>>>>>>>> February.
>>>>>>>>>>>> Feb 16th?
>>>>>>>>>>>>
>>>>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>>>>
>>>>>>>>>>>> Proposed Tasks:
>>>>>>>>>>>> 1) Comment - is the document clear enough or where is there a
>>>>>>>>>>>> gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>>>> --> also, scan the current wiki and find sections you
>>>>>>>>>>>> think belong being "brought over". compile a list of those pages. If
>>>>>>>>>>>> none, great.
>>>>>>>>>>>> 2) Based on my comments above, create a mockup of the landing
>>>>>>>>>>>> page (Meta Cyrus?)
>>>>>>>>>>>> --> also, scan other Apache projects to find landing pages
>>>>>>>>>>>> that you like
>>>>>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence
>>>>>>>>>>>> with links (james or ?)
>>>>>>>>>>>>
>>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>>>
>>>>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>>>>
>>>>>>>>>>>> thanks
>>>>>>>>>>>> James
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>>>
>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi James,
>>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and develop
>>>>>>>>>>>>> a good user reliable website.
>>>>>>>>>>>>> Where I can start??
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> All -
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+
>>>>>>>>>>>>>> years since we did a clean sweep of it. We also have a front landing page
>>>>>>>>>>>>>> at https://fineract.apache.org that could be better at
>>>>>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>>>>>> me?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - Add blog feed
>>>>>>>>>>>>>> - Add feed to dev list
>>>>>>>>>>>>>> - Include FAQ
>>>>>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we
>>>>>>>>>>>>>> should have a top level split on the main page as well, or perhaps a
>>>>>>>>>>>>>> separate landing page for FineractCN.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to show
>>>>>>>>>>>>>> two levels):
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - FAQ
>>>>>>>>>>>>>> - About Fineract
>>>>>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>>>>>> - About FineractCN
>>>>>>>>>>>>>> - TBD
>>>>>>>>>>>>>> - Project Management
>>>>>>>>>>>>>> - Quarterly reports to the Apache Board (this needs to
>>>>>>>>>>>>>> be more prominent)
>>>>>>>>>>>>>> - Community meetings organized by date (most recent at
>>>>>>>>>>>>>> top)
>>>>>>>>>>>>>> - Surveys
>>>>>>>>>>>>>> - Release processes
>>>>>>>>>>>>>> - How do I get involved?
>>>>>>>>>>>>>> - Committer guides
>>>>>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>>>>>> - Standards
>>>>>>>>>>>>>> - Documentation
>>>>>>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>>>>>>> documentation.
>>>>>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces,
>>>>>>>>>>>>>> etc) ... all go to blog
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> FINERACT
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> How-to articles
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>
>>>>>>>>> --
>>>>>> Sent from Gmail Mobile
>>>>>>
>>>>>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Hi - Thank you for this.
It's a very good conversation starter. I agreed with most of Javier's
comments, which makes clear that we need to do a better job of "Explaining"
and "Positioning".
ASIDE: Javier - I invite you to write more such text and provide a top
level set of bullet points that can be perhaps worked into the content.
I think that the design colors are ok, the blue is appropriate for a
financial system, meaning steady and trustworthy on the color wheel. Nice.
We need more revamping of the content before we can properly do this
design, so let's try to attack that problem.
Here is a requirement that may not be clear to you:
* Site should be very simple, easy to change by anyone opening up a Text
Editor and modifying the HTML directly. e.g. use CSS styles and hopefully
with names that make sense
* Assume that you are gone and someone else has to modify just some text
areas, adding content in specific sections.
* Assume that no-one touches the website for over a year, maybe three
years, and avoid content that can get stale.
Message and Content issues:
* Fineract is part of Apache and this is not always clear from the page
today. Also, there is a common set of links and structure that you can find
in other Apache projects. It is not a requirement to follow other Apache
projects, but it would be useful to review them for commonalities:
--> https://hadoop.apache.org
--> https://airflow.apache.org
--> https://kafka.apache.org
* Note Community is there in each project. Check out the content that each
project has.
* Key tasks should be up top : Learn more, Help, Download
and this should then flow into the requirements for the other sections on
the front page and then onto the wiki structure that we need
* At this time Fineract-CN should probably not receive equal billing as the
Fineract1.x releases it is still trying to get to a first release and
fineract1.x is releasing on a regular basis with lots of activity. So,
move Fineract-CN to a bottom section that's something about "Additional
community technologies"
I was and am a big fan of this framework, and I know this positioning is
controversial for some, but until we get a release out and lots of active
development and deployments, that project remains very much a side project
of the community. It may become a very important thing, but for now we
should reflect the reality which is that Fineract1.x is where the vast
majority of the dev is going on, and the vast majority of the users are
there.
* We need to emphasize the key features of Fineract - there should be a
summary of the system.
This may require more chat and discussion on list or on slack and then
development of a structure of content before you can really get a design.
Thank you again.
James Dailey
On Thu, Feb 23, 2023 at 12:04 AM Meta Cyrus <in...@gmail.com> wrote:
> Hello James,
> Have you reviewed the website frame. Please share the feedback.
> Regards,
> Inzemamul Haq
>
> On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com> wrote:
>
>> Hello Javier,
>> Thanks for your feedback. The points you mentioned, I'll implement them
>> as you suggested now what I need is some more brief about the topics. This
>> was the just an idea of how it'll look like surely we can change and add
>> the things.
>> As you mentioned in the last that it's a template but it's not. It's
>> designed by me on the figma and the assets I used are open source so their
>> will be no licencing issue. I always go for the development through scratch
>> so no need to worry about that.
>> Regards,
>> Inzemam
>>
>> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io>
>> wrote:
>>
>>> Hy Meta,
>>>
>>> Great job; I like the enhancement of the visuals and aesthetic in
>>> general, and it seems much more modern and suitable for the next stage of
>>> our community.
>>>
>>> My two cents:
>>>
>>> - It is too linked with banks. Fineract has proved to be useful in
>>> other areas of the industry, not just banks. We need to convey that
>>> Fineract is a platform for many use cases. Using a mobile phone and a
>>> credit card as our visuals will put us in the last 20 years of the
>>> industry, and *we are *in *the next 20 years.* The images we need to
>>> use has to be conceptual, not rigid on old paradigms.
>>> - Fineract is a backend. Fineract will help the financial industry
>>> transcend from the old paradigm of "save deposit boxes" to the new paradigm
>>> of "Internet switches," allowing the users of financial institutions to
>>> move their assets worldwide quickly and safely. All purchases are now
>>> digital.
>>> - Fineract is not Fineract CN, and Fineract CN can not have the same
>>> exposure on our website as Fineract. Fineract CN it's still an experiment
>>> while most of our community depends on and uses Fineract. This must be
>>> clearly shown on the website and the real estate we dedicate to each one.
>>> Fineract CN wasn't the project incubated originally, and Fineract CN is not
>>> backward compatible with Fineract.
>>> - The project we are proud of: I will only use the project part if
>>> we get three Fortune 500 companies using Fineract. It will also open a new
>>> can of worms on which project gets selected and which criteria we should
>>> use, on top of getting the right set of approvals from them to be used as
>>> projects.
>>> - Last but not least, you used a template for the design. We need
>>> the license of that template that allows us to use it without limitations,
>>> and the template license is aligned with Apache 2.0.
>>>
>>> Javier
>>>
>>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>>> Hi James,
>>>> Below is the drive link of complete page screenshot of APACHE FINERACT
>>>> redesigned website. Please review and let me know if you have any questions
>>>> or changes needed.
>>>>
>>>>
>>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>>
>>>> Regards,
>>>> Inzemamul Haq
>>>>
>>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Meta - Any updates from you on this?
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Okay lemme begin the work.
>>>>>>
>>>>>>
>>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi
>>>>>>>> I've been through the website and got it closely that what exact is
>>>>>>>> there on the website. I'll create a static mockup for the website.
>>>>>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>>>>>> experienced first comes to the website got confused of what's happening and
>>>>>>>> how things are going we can work upon it.
>>>>>>>> Also I have a question are we going to implement blogger on
>>>>>>>> that website? I have ability to work on static websites where the data
>>>>>>>> comes from dynamic CMS.
>>>>>>>> So I can work on tha too....
>>>>>>>> Regards,
>>>>>>>> Inzemamul Haq
>>>>>>>>
>>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Inzemamul Haq -
>>>>>>>>>
>>>>>>>>> Appreciate the response. This is revising our single page website
>>>>>>>>> for the project, so not an app. The content needs to be largely static or
>>>>>>>>> to pick up content we regularly post on blog. The current site is basic
>>>>>>>>> html. Just making sure we’re talking about the same thing.
>>>>>>>>>
>>>>>>>>> Fineract.Apache.org
>>>>>>>>>
>>>>>>>>> Figma I associate w more complex flows. What’s needed is a design
>>>>>>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>>>>>>> audience and what’s their need when they land on the page.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>> First I will create mockup using the figma where we can get a
>>>>>>>>>> better Idea of what exactly has to be happen. By the 16th of Feb I'll come
>>>>>>>>>> up with a design also will share here in the thread and we can get comments
>>>>>>>>>> in the meeting.
>>>>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>
>>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>>>>>> people who said they'd like to be involved.
>>>>>>>>>>>
>>>>>>>>>>> I have a few tasks that I think may suit this group and then we
>>>>>>>>>>> can share back here on list and also hold a meeting on zoom in mid
>>>>>>>>>>> February.
>>>>>>>>>>> Feb 16th?
>>>>>>>>>>>
>>>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>>>
>>>>>>>>>>> Proposed Tasks:
>>>>>>>>>>> 1) Comment - is the document clear enough or where is there a
>>>>>>>>>>> gap in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>>> --> also, scan the current wiki and find sections you think
>>>>>>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>>>>>>> great.
>>>>>>>>>>> 2) Based on my comments above, create a mockup of the landing
>>>>>>>>>>> page (Meta Cyrus?)
>>>>>>>>>>> --> also, scan other Apache projects to find landing pages
>>>>>>>>>>> that you like
>>>>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence
>>>>>>>>>>> with links (james or ?)
>>>>>>>>>>>
>>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>>
>>>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>>>
>>>>>>>>>>> thanks
>>>>>>>>>>> James
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>>
>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>
>>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi James,
>>>>>>>>>>>> I am a good UI/UX and web developer who can Design and develop
>>>>>>>>>>>> a good user reliable website.
>>>>>>>>>>>> Where I can start??
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> All -
>>>>>>>>>>>>>
>>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+
>>>>>>>>>>>>> years since we did a clean sweep of it. We also have a front landing page
>>>>>>>>>>>>> at https://fineract.apache.org that could be better at
>>>>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>>>>> me?
>>>>>>>>>>>>>
>>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>>> ---
>>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>>
>>>>>>>>>>>>> - Add blog feed
>>>>>>>>>>>>> - Add feed to dev list
>>>>>>>>>>>>> - Include FAQ
>>>>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>>>>
>>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should
>>>>>>>>>>>>> have a top level split on the main page as well, or perhaps a separate
>>>>>>>>>>>>> landing page for FineractCN.
>>>>>>>>>>>>>
>>>>>>>>>>>>> ---
>>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to show
>>>>>>>>>>>>> two levels):
>>>>>>>>>>>>>
>>>>>>>>>>>>> - FAQ
>>>>>>>>>>>>> - About Fineract
>>>>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>>>>> - About FineractCN
>>>>>>>>>>>>> - TBD
>>>>>>>>>>>>> - Project Management
>>>>>>>>>>>>> - Quarterly reports to the Apache Board (this needs to
>>>>>>>>>>>>> be more prominent)
>>>>>>>>>>>>> - Community meetings organized by date (most recent at
>>>>>>>>>>>>> top)
>>>>>>>>>>>>> - Surveys
>>>>>>>>>>>>> - Release processes
>>>>>>>>>>>>> - How do I get involved?
>>>>>>>>>>>>> - Committer guides
>>>>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>>>>> - Standards
>>>>>>>>>>>>> - Documentation
>>>>>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>>>>>> documentation.
>>>>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc)
>>>>>>>>>>>>> ... all go to blog
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>>
>>>>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> FINERACT
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> How-to articles
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>
>>>>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>>
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Hello James,
Have you reviewed the website frame. Please share the feedback.
Regards,
Inzemamul Haq
On Mon, 20 Feb, 2023, 6:09 pm Meta Cyrus, <in...@gmail.com> wrote:
> Hello Javier,
> Thanks for your feedback. The points you mentioned, I'll implement them as
> you suggested now what I need is some more brief about the topics. This was
> the just an idea of how it'll look like surely we can change and add the
> things.
> As you mentioned in the last that it's a template but it's not. It's
> designed by me on the figma and the assets I used are open source so their
> will be no licencing issue. I always go for the development through scratch
> so no need to worry about that.
> Regards,
> Inzemam
>
> On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io> wrote:
>
>> Hy Meta,
>>
>> Great job; I like the enhancement of the visuals and aesthetic in
>> general, and it seems much more modern and suitable for the next stage of
>> our community.
>>
>> My two cents:
>>
>> - It is too linked with banks. Fineract has proved to be useful in
>> other areas of the industry, not just banks. We need to convey that
>> Fineract is a platform for many use cases. Using a mobile phone and a
>> credit card as our visuals will put us in the last 20 years of the
>> industry, and *we are *in *the next 20 years.* The images we need to
>> use has to be conceptual, not rigid on old paradigms.
>> - Fineract is a backend. Fineract will help the financial industry
>> transcend from the old paradigm of "save deposit boxes" to the new paradigm
>> of "Internet switches," allowing the users of financial institutions to
>> move their assets worldwide quickly and safely. All purchases are now
>> digital.
>> - Fineract is not Fineract CN, and Fineract CN can not have the same
>> exposure on our website as Fineract. Fineract CN it's still an experiment
>> while most of our community depends on and uses Fineract. This must be
>> clearly shown on the website and the real estate we dedicate to each one.
>> Fineract CN wasn't the project incubated originally, and Fineract CN is not
>> backward compatible with Fineract.
>> - The project we are proud of: I will only use the project part if we
>> get three Fortune 500 companies using Fineract. It will also open a new can
>> of worms on which project gets selected and which criteria we should use,
>> on top of getting the right set of approvals from them to be used as
>> projects.
>> - Last but not least, you used a template for the design. We need the
>> license of that template that allows us to use it without limitations, and
>> the template license is aligned with Apache 2.0.
>>
>> Javier
>>
>> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>>
>>> Hi James,
>>> Below is the drive link of complete page screenshot of APACHE FINERACT
>>> redesigned website. Please review and let me know if you have any questions
>>> or changes needed.
>>>
>>>
>>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>>
>>> Regards,
>>> Inzemamul Haq
>>>
>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> Hi Meta - Any updates from you on this?
>>>>
>>>>
>>>>
>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>>
>>>>> Okay lemme begin the work.
>>>>>
>>>>>
>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi
>>>>>>> I've been through the website and got it closely that what exact is
>>>>>>> there on the website. I'll create a static mockup for the website.
>>>>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>>>>> experienced first comes to the website got confused of what's happening and
>>>>>>> how things are going we can work upon it.
>>>>>>> Also I have a question are we going to implement blogger on
>>>>>>> that website? I have ability to work on static websites where the data
>>>>>>> comes from dynamic CMS.
>>>>>>> So I can work on tha too....
>>>>>>> Regards,
>>>>>>> Inzemamul Haq
>>>>>>>
>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Inzemamul Haq -
>>>>>>>>
>>>>>>>> Appreciate the response. This is revising our single page website
>>>>>>>> for the project, so not an app. The content needs to be largely static or
>>>>>>>> to pick up content we regularly post on blog. The current site is basic
>>>>>>>> html. Just making sure we’re talking about the same thing.
>>>>>>>>
>>>>>>>> Fineract.Apache.org
>>>>>>>>
>>>>>>>> Figma I associate w more complex flows. What’s needed is a design
>>>>>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>>>>>> audience and what’s their need when they land on the page.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>> First I will create mockup using the figma where we can get a
>>>>>>>>> better Idea of what exactly has to be happen. By the 16th of Feb I'll come
>>>>>>>>> up with a design also will share here in the thread and we can get comments
>>>>>>>>> in the meeting.
>>>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Inzemamul Haq
>>>>>>>>>
>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>>>>> people who said they'd like to be involved.
>>>>>>>>>>
>>>>>>>>>> I have a few tasks that I think may suit this group and then we
>>>>>>>>>> can share back here on list and also hold a meeting on zoom in mid
>>>>>>>>>> February.
>>>>>>>>>> Feb 16th?
>>>>>>>>>>
>>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>>
>>>>>>>>>> Proposed Tasks:
>>>>>>>>>> 1) Comment - is the document clear enough or where is there a gap
>>>>>>>>>> in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>> --> also, scan the current wiki and find sections you think
>>>>>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>>>>>> great.
>>>>>>>>>> 2) Based on my comments above, create a mockup of the landing
>>>>>>>>>> page (Meta Cyrus?)
>>>>>>>>>> --> also, scan other Apache projects to find landing pages
>>>>>>>>>> that you like
>>>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence
>>>>>>>>>> with links (james or ?)
>>>>>>>>>>
>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>
>>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>>
>>>>>>>>>> thanks
>>>>>>>>>> James
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>
>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>
>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi James,
>>>>>>>>>>> I am a good UI/UX and web developer who can Design and develop a
>>>>>>>>>>> good user reliable website.
>>>>>>>>>>> Where I can start??
>>>>>>>>>>> Regards,
>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>
>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> All -
>>>>>>>>>>>>
>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+
>>>>>>>>>>>> years since we did a clean sweep of it. We also have a front landing page
>>>>>>>>>>>> at https://fineract.apache.org that could be better at
>>>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>>>> me?
>>>>>>>>>>>>
>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>> ---
>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>
>>>>>>>>>>>> - Add blog feed
>>>>>>>>>>>> - Add feed to dev list
>>>>>>>>>>>> - Include FAQ
>>>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>>>
>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should
>>>>>>>>>>>> have a top level split on the main page as well, or perhaps a separate
>>>>>>>>>>>> landing page for FineractCN.
>>>>>>>>>>>>
>>>>>>>>>>>> ---
>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to show
>>>>>>>>>>>> two levels):
>>>>>>>>>>>>
>>>>>>>>>>>> - FAQ
>>>>>>>>>>>> - About Fineract
>>>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>>>> - About FineractCN
>>>>>>>>>>>> - TBD
>>>>>>>>>>>> - Project Management
>>>>>>>>>>>> - Quarterly reports to the Apache Board (this needs to
>>>>>>>>>>>> be more prominent)
>>>>>>>>>>>> - Community meetings organized by date (most recent at
>>>>>>>>>>>> top)
>>>>>>>>>>>> - Surveys
>>>>>>>>>>>> - Release processes
>>>>>>>>>>>> - How do I get involved?
>>>>>>>>>>>> - Committer guides
>>>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>>>> - Standards
>>>>>>>>>>>> - Documentation
>>>>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>>>>> documentation.
>>>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc)
>>>>>>>>>>>> ... all go to blog
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>
>>>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> FINERACT
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> How-to articles
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>> Sent from Gmail Mobile
>>>>>>>>
>>>>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>>
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Hello Javier,
Thanks for your feedback. The points you mentioned, I'll implement them as
you suggested now what I need is some more brief about the topics. This was
the just an idea of how it'll look like surely we can change and add the
things.
As you mentioned in the last that it's a template but it's not. It's
designed by me on the figma and the assets I used are open source so their
will be no licencing issue. I always go for the development through scratch
so no need to worry about that.
Regards,
Inzemam
On Mon, 20 Feb, 2023, 6:01 pm Javier Borkenztain, <ja...@fiter.io> wrote:
> Hy Meta,
>
> Great job; I like the enhancement of the visuals and aesthetic in general,
> and it seems much more modern and suitable for the next stage of our
> community.
>
> My two cents:
>
> - It is too linked with banks. Fineract has proved to be useful in
> other areas of the industry, not just banks. We need to convey that
> Fineract is a platform for many use cases. Using a mobile phone and a
> credit card as our visuals will put us in the last 20 years of the
> industry, and *we are *in *the next 20 years.* The images we need to
> use has to be conceptual, not rigid on old paradigms.
> - Fineract is a backend. Fineract will help the financial industry
> transcend from the old paradigm of "save deposit boxes" to the new paradigm
> of "Internet switches," allowing the users of financial institutions to
> move their assets worldwide quickly and safely. All purchases are now
> digital.
> - Fineract is not Fineract CN, and Fineract CN can not have the same
> exposure on our website as Fineract. Fineract CN it's still an experiment
> while most of our community depends on and uses Fineract. This must be
> clearly shown on the website and the real estate we dedicate to each one.
> Fineract CN wasn't the project incubated originally, and Fineract CN is not
> backward compatible with Fineract.
> - The project we are proud of: I will only use the project part if we
> get three Fortune 500 companies using Fineract. It will also open a new can
> of worms on which project gets selected and which criteria we should use,
> on top of getting the right set of approvals from them to be used as
> projects.
> - Last but not least, you used a template for the design. We need the
> license of that template that allows us to use it without limitations, and
> the template license is aligned with Apache 2.0.
>
> Javier
>
> On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com> wrote:
>
>> Hi James,
>> Below is the drive link of complete page screenshot of APACHE FINERACT
>> redesigned website. Please review and let me know if you have any questions
>> or changes needed.
>>
>>
>> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>>
>> Regards,
>> Inzemamul Haq
>>
>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> Hi Meta - Any updates from you on this?
>>>
>>>
>>>
>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>>> Okay lemme begin the work.
>>>>
>>>>
>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>>
>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>> I've been through the website and got it closely that what exact is
>>>>>> there on the website. I'll create a static mockup for the website.
>>>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>>>> experienced first comes to the website got confused of what's happening and
>>>>>> how things are going we can work upon it.
>>>>>> Also I have a question are we going to implement blogger on
>>>>>> that website? I have ability to work on static websites where the data
>>>>>> comes from dynamic CMS.
>>>>>> So I can work on tha too....
>>>>>> Regards,
>>>>>> Inzemamul Haq
>>>>>>
>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Inzemamul Haq -
>>>>>>>
>>>>>>> Appreciate the response. This is revising our single page website
>>>>>>> for the project, so not an app. The content needs to be largely static or
>>>>>>> to pick up content we regularly post on blog. The current site is basic
>>>>>>> html. Just making sure we’re talking about the same thing.
>>>>>>>
>>>>>>> Fineract.Apache.org
>>>>>>>
>>>>>>> Figma I associate w more complex flows. What’s needed is a design
>>>>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>>>>> audience and what’s their need when they land on the page.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>> First I will create mockup using the figma where we can get a
>>>>>>>> better Idea of what exactly has to be happen. By the 16th of Feb I'll come
>>>>>>>> up with a design also will share here in the thread and we can get comments
>>>>>>>> in the meeting.
>>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Inzemamul Haq
>>>>>>>>
>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>>>> people who said they'd like to be involved.
>>>>>>>>>
>>>>>>>>> I have a few tasks that I think may suit this group and then we
>>>>>>>>> can share back here on list and also hold a meeting on zoom in mid
>>>>>>>>> February.
>>>>>>>>> Feb 16th?
>>>>>>>>>
>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>
>>>>>>>>> Proposed Tasks:
>>>>>>>>> 1) Comment - is the document clear enough or where is there a gap
>>>>>>>>> in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>> --> also, scan the current wiki and find sections you think
>>>>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>>>>> great.
>>>>>>>>> 2) Based on my comments above, create a mockup of the landing page
>>>>>>>>> (Meta Cyrus?)
>>>>>>>>> --> also, scan other Apache projects to find landing pages
>>>>>>>>> that you like
>>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence with
>>>>>>>>> links (james or ?)
>>>>>>>>>
>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>
>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>
>>>>>>>>> thanks
>>>>>>>>> James
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>>>
>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>
>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>
>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi James,
>>>>>>>>>> I am a good UI/UX and web developer who can Design and develop a
>>>>>>>>>> good user reliable website.
>>>>>>>>>> Where I can start??
>>>>>>>>>> Regards,
>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>
>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> All -
>>>>>>>>>>>
>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years
>>>>>>>>>>> since we did a clean sweep of it. We also have a front landing page at
>>>>>>>>>>> https://fineract.apache.org that could be better at
>>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>>> me?
>>>>>>>>>>>
>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>> ---
>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>
>>>>>>>>>>> - Add blog feed
>>>>>>>>>>> - Add feed to dev list
>>>>>>>>>>> - Include FAQ
>>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>>
>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should
>>>>>>>>>>> have a top level split on the main page as well, or perhaps a separate
>>>>>>>>>>> landing page for FineractCN.
>>>>>>>>>>>
>>>>>>>>>>> ---
>>>>>>>>>>> On the wiki - new suggested structure (figure out how to show
>>>>>>>>>>> two levels):
>>>>>>>>>>>
>>>>>>>>>>> - FAQ
>>>>>>>>>>> - About Fineract
>>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>>> - About FineractCN
>>>>>>>>>>> - TBD
>>>>>>>>>>> - Project Management
>>>>>>>>>>> - Quarterly reports to the Apache Board (this needs to be
>>>>>>>>>>> more prominent)
>>>>>>>>>>> - Community meetings organized by date (most recent at
>>>>>>>>>>> top)
>>>>>>>>>>> - Surveys
>>>>>>>>>>> - Release processes
>>>>>>>>>>> - How do I get involved?
>>>>>>>>>>> - Committer guides
>>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>>> - Standards
>>>>>>>>>>> - Documentation
>>>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>>>> documentation.
>>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc)
>>>>>>>>>>> ... all go to blog
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>
>>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> FINERACT
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> FINERACT CN
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> How-to articles
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> Meeting notes
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>> Sent from Gmail Mobile
>>>>>>>
>>>>>> --
>>> Sent from Gmail Mobile
>>>
>>
Re: Website and Wiki for Fineract updates
Posted by Javier Borkenztain <ja...@fiter.io>.
Hy Meta,
Great job; I like the enhancement of the visuals and aesthetic in general,
and it seems much more modern and suitable for the next stage of our
community.
My two cents:
- It is too linked with banks. Fineract has proved to be useful in other
areas of the industry, not just banks. We need to convey that Fineract is a
platform for many use cases. Using a mobile phone and a credit card as our
visuals will put us in the last 20 years of the industry, and *we are *in
*the next 20 years.* The images we need to use has to be conceptual, not
rigid on old paradigms.
- Fineract is a backend. Fineract will help the financial industry
transcend from the old paradigm of "save deposit boxes" to the new paradigm
of "Internet switches," allowing the users of financial institutions to
move their assets worldwide quickly and safely. All purchases are now
digital.
- Fineract is not Fineract CN, and Fineract CN can not have the same
exposure on our website as Fineract. Fineract CN it's still an experiment
while most of our community depends on and uses Fineract. This must be
clearly shown on the website and the real estate we dedicate to each one.
Fineract CN wasn't the project incubated originally, and Fineract CN is not
backward compatible with Fineract.
- The project we are proud of: I will only use the project part if we
get three Fortune 500 companies using Fineract. It will also open a new can
of worms on which project gets selected and which criteria we should use,
on top of getting the right set of approvals from them to be used as
projects.
- Last but not least, you used a template for the design. We need the
license of that template that allows us to use it without limitations, and
the template license is aligned with Apache 2.0.
Javier
On Mon, Feb 20, 2023 at 8:14 AM Meta Cyrus <in...@gmail.com> wrote:
> Hi James,
> Below is the drive link of complete page screenshot of APACHE FINERACT
> redesigned website. Please review and let me know if you have any questions
> or changes needed.
>
>
> https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
>
> Regards,
> Inzemamul Haq
>
> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
> wrote:
>
>> Hi Meta - Any updates from you on this?
>>
>>
>>
>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com> wrote:
>>
>>> Okay lemme begin the work.
>>>
>>>
>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> +1
>>>>
>>>>
>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>> I've been through the website and got it closely that what exact is
>>>>> there on the website. I'll create a static mockup for the website.
>>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>>> experienced first comes to the website got confused of what's happening and
>>>>> how things are going we can work upon it.
>>>>> Also I have a question are we going to implement blogger on
>>>>> that website? I have ability to work on static websites where the data
>>>>> comes from dynamic CMS.
>>>>> So I can work on tha too....
>>>>> Regards,
>>>>> Inzemamul Haq
>>>>>
>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Inzemamul Haq -
>>>>>>
>>>>>> Appreciate the response. This is revising our single page website
>>>>>> for the project, so not an app. The content needs to be largely static or
>>>>>> to pick up content we regularly post on blog. The current site is basic
>>>>>> html. Just making sure we’re talking about the same thing.
>>>>>>
>>>>>> Fineract.Apache.org
>>>>>>
>>>>>> Figma I associate w more complex flows. What’s needed is a design
>>>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>>>> audience and what’s their need when they land on the page.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> First I will create mockup using the figma where we can get a better
>>>>>>> Idea of what exactly has to be happen. By the 16th of Feb I'll come up with
>>>>>>> a design also will share here in the thread and we can get comments in the
>>>>>>> meeting.
>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>> Regards,
>>>>>>>
>>>>>>> Inzemamul Haq
>>>>>>>
>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>>> people who said they'd like to be involved.
>>>>>>>>
>>>>>>>> I have a few tasks that I think may suit this group and then we can
>>>>>>>> share back here on list and also hold a meeting on zoom in mid February.
>>>>>>>> Feb 16th?
>>>>>>>>
>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>
>>>>>>>> Proposed Tasks:
>>>>>>>> 1) Comment - is the document clear enough or where is there a gap
>>>>>>>> in content (Bruce, Tekle? - start a thread about this)
>>>>>>>> --> also, scan the current wiki and find sections you think
>>>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>>>> great.
>>>>>>>> 2) Based on my comments above, create a mockup of the landing page
>>>>>>>> (Meta Cyrus?)
>>>>>>>> --> also, scan other Apache projects to find landing pages that
>>>>>>>> you like
>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>> 4) Generate a new outline for the wiki and post on confluence with
>>>>>>>> links (james or ?)
>>>>>>>>
>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>
>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>
>>>>>>>> thanks
>>>>>>>> James
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>>
>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>
>>>>>>>>> Sent from my iPhone
>>>>>>>>>
>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi James,
>>>>>>>>> I am a good UI/UX and web developer who can Design and develop a
>>>>>>>>> good user reliable website.
>>>>>>>>> Where I can start??
>>>>>>>>> Regards,
>>>>>>>>> Inzemamul Haq
>>>>>>>>>
>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> All -
>>>>>>>>>>
>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years
>>>>>>>>>> since we did a clean sweep of it. We also have a front landing page at
>>>>>>>>>> https://fineract.apache.org that could be better at
>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>> me?
>>>>>>>>>>
>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>> ---
>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>
>>>>>>>>>> - Add blog feed
>>>>>>>>>> - Add feed to dev list
>>>>>>>>>> - Include FAQ
>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>
>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should
>>>>>>>>>> have a top level split on the main page as well, or perhaps a separate
>>>>>>>>>> landing page for FineractCN.
>>>>>>>>>>
>>>>>>>>>> ---
>>>>>>>>>> On the wiki - new suggested structure (figure out how to show two
>>>>>>>>>> levels):
>>>>>>>>>>
>>>>>>>>>> - FAQ
>>>>>>>>>> - About Fineract
>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>> - About FineractCN
>>>>>>>>>> - TBD
>>>>>>>>>> - Project Management
>>>>>>>>>> - Quarterly reports to the Apache Board (this needs to be
>>>>>>>>>> more prominent)
>>>>>>>>>> - Community meetings organized by date (most recent at
>>>>>>>>>> top)
>>>>>>>>>> - Surveys
>>>>>>>>>> - Release processes
>>>>>>>>>> - How do I get involved?
>>>>>>>>>> - Committer guides
>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>> - Standards
>>>>>>>>>> - Documentation
>>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>>> documentation.
>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc)
>>>>>>>>>> ... all go to blog
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The current high level structure:
>>>>>>>>>>
>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> FINERACT
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> FINERACT CN
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> How-to articles
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> Meeting notes
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>> Sent from Gmail Mobile
>>>>>>
>>>>> --
>> Sent from Gmail Mobile
>>
>
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Hi James,
Below is the drive link of complete page screenshot of APACHE FINERACT
redesigned website. Please review and let me know if you have any questions
or changes needed.
https://drive.google.com/file/d/1alQFhbfPF8J3_a1rTXpKXzqoV54zjasA/view?usp=drivesdk
Regards,
Inzemamul Haq
On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com> wrote:
> Hi Meta - Any updates from you on this?
>
>
>
> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com> wrote:
>
>> Okay lemme begin the work.
>>
>>
>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>>
>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>> I've been through the website and got it closely that what exact is
>>>> there on the website. I'll create a static mockup for the website.
>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>> experienced first comes to the website got confused of what's happening and
>>>> how things are going we can work upon it.
>>>> Also I have a question are we going to implement blogger on
>>>> that website? I have ability to work on static websites where the data
>>>> comes from dynamic CMS.
>>>> So I can work on tha too....
>>>> Regards,
>>>> Inzemamul Haq
>>>>
>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Inzemamul Haq -
>>>>>
>>>>> Appreciate the response. This is revising our single page website for
>>>>> the project, so not an app. The content needs to be largely static or to
>>>>> pick up content we regularly post on blog. The current site is basic html.
>>>>> Just making sure we’re talking about the same thing.
>>>>>
>>>>> Fineract.Apache.org
>>>>>
>>>>> Figma I associate w more complex flows. What’s needed is a design
>>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>>> audience and what’s their need when they land on the page.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>> First I will create mockup using the figma where we can get a better
>>>>>> Idea of what exactly has to be happen. By the 16th of Feb I'll come up with
>>>>>> a design also will share here in the thread and we can get comments in the
>>>>>> meeting.
>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>> Regards,
>>>>>>
>>>>>> Inzemamul Haq
>>>>>>
>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>> people who said they'd like to be involved.
>>>>>>>
>>>>>>> I have a few tasks that I think may suit this group and then we can
>>>>>>> share back here on list and also hold a meeting on zoom in mid February.
>>>>>>> Feb 16th?
>>>>>>>
>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>
>>>>>>> Proposed Tasks:
>>>>>>> 1) Comment - is the document clear enough or where is there a gap in
>>>>>>> content (Bruce, Tekle? - start a thread about this)
>>>>>>> --> also, scan the current wiki and find sections you think
>>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>>> great.
>>>>>>> 2) Based on my comments above, create a mockup of the landing page
>>>>>>> (Meta Cyrus?)
>>>>>>> --> also, scan other Apache projects to find landing pages that
>>>>>>> you like
>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>> 4) Generate a new outline for the wiki and post on confluence with
>>>>>>> links (james or ?)
>>>>>>>
>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>
>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>
>>>>>>> thanks
>>>>>>> James
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>
>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>
>>>>>>>> Sent from my iPhone
>>>>>>>>
>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi James,
>>>>>>>> I am a good UI/UX and web developer who can Design and develop a
>>>>>>>> good user reliable website.
>>>>>>>> Where I can start??
>>>>>>>> Regards,
>>>>>>>> Inzemamul Haq
>>>>>>>>
>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> All -
>>>>>>>>>
>>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years
>>>>>>>>> since we did a clean sweep of it. We also have a front landing page at
>>>>>>>>> https://fineract.apache.org that could be better at
>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>> me?
>>>>>>>>>
>>>>>>>>> PROPOSED CHANGES
>>>>>>>>> ---
>>>>>>>>> On the front "Landing" page:
>>>>>>>>>
>>>>>>>>> - Add blog feed
>>>>>>>>> - Add feed to dev list
>>>>>>>>> - Include FAQ
>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>
>>>>>>>>> As we hope to see a FineractCN release soon, I think we should
>>>>>>>>> have a top level split on the main page as well, or perhaps a separate
>>>>>>>>> landing page for FineractCN.
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>> On the wiki - new suggested structure (figure out how to show two
>>>>>>>>> levels):
>>>>>>>>>
>>>>>>>>> - FAQ
>>>>>>>>> - About Fineract
>>>>>>>>> - New top level functional descriptions
>>>>>>>>> - About FineractCN
>>>>>>>>> - TBD
>>>>>>>>> - Project Management
>>>>>>>>> - Quarterly reports to the Apache Board (this needs to be
>>>>>>>>> more prominent)
>>>>>>>>> - Community meetings organized by date (most recent at top)
>>>>>>>>> - Surveys
>>>>>>>>> - Release processes
>>>>>>>>> - How do I get involved?
>>>>>>>>> - Committer guides
>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>> - Standards
>>>>>>>>> - Documentation
>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>> documentation.
>>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc) ...
>>>>>>>>> all go to blog
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The current high level structure:
>>>>>>>>>
>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> FINERACT
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> FINERACT CN
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> Fineract Project Security Report
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> How-to articles
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> Meeting notes
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>> --
> Sent from Gmail Mobile
>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Bringing this back to top:
Task for Bruce, Tekle, John
See
https://fineract.apache.org/docs/current/
and also look at the current wiki and landing page in detail.
Proposed Tasks:
1) Comment - is the document clear enough or where is there a gap in
content (Bruce, Tekle? - start a thread about this)
--> also, scan the current wiki and find sections you think belong
being "brought over". compile a list of those pages. If none, great.
—-
To expand on this:
1. Review the /current/
2. Identify areas that need work, list out
3. Find wiki pages that could help fill those gaps, list those links
4. Email list w list and start to write text change PRs
Or…suggest some other approach.
On Sat, Feb 18, 2023 at 8:16 AM Meta Cyrus <in...@gmail.com> wrote:
> Yes I'll be sharing the scree recorded video here shortly. Then you can
> review.
>
> On Sat, 18 Feb, 2023, 9:42 pm James Dailey, <ja...@gmail.com>
> wrote:
>
>> We should review it before you make it live. Screenshots or graphics
>> here?
>>
>> On Sat, Feb 18, 2023 at 8:01 AM Meta Cyrus <in...@gmail.com>
>> wrote:
>>
>>> Hi James,
>>> I have done with the UI will be pushing the code in a day on the repo.
>>> Will it be okay??
>>>
>>>
>>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> Hi Meta - Any updates from you on this?
>>>>
>>>>
>>>>
>>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>>
>>>>> Okay lemme begin the work.
>>>>>
>>>>>
>>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi
>>>>>>> I've been through the website and got it closely that what exact is
>>>>>>> there on the website. I'll create a static mockup for the website.
>>>>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>>>>> experienced first comes to the website got confused of what's happening and
>>>>>>> how things are going we can work upon it.
>>>>>>> Also I have a question are we going to implement blogger on
>>>>>>> that website? I have ability to work on static websites where the data
>>>>>>> comes from dynamic CMS.
>>>>>>> So I can work on tha too....
>>>>>>> Regards,
>>>>>>> Inzemamul Haq
>>>>>>>
>>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Inzemamul Haq -
>>>>>>>>
>>>>>>>> Appreciate the response. This is revising our single page website
>>>>>>>> for the project, so not an app. The content needs to be largely static or
>>>>>>>> to pick up content we regularly post on blog. The current site is basic
>>>>>>>> html. Just making sure we’re talking about the same thing.
>>>>>>>>
>>>>>>>> Fineract.Apache.org
>>>>>>>>
>>>>>>>> Figma I associate w more complex flows. What’s needed is a design
>>>>>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>>>>>> audience and what’s their need when they land on the page.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>> First I will create mockup using the figma where we can get a
>>>>>>>>> better Idea of what exactly has to be happen. By the 16th of Feb I'll come
>>>>>>>>> up with a design also will share here in the thread and we can get comments
>>>>>>>>> in the meeting.
>>>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Inzemamul Haq
>>>>>>>>>
>>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>>>>> people who said they'd like to be involved.
>>>>>>>>>>
>>>>>>>>>> I have a few tasks that I think may suit this group and then we
>>>>>>>>>> can share back here on list and also hold a meeting on zoom in mid
>>>>>>>>>> February.
>>>>>>>>>> Feb 16th?
>>>>>>>>>>
>>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>>
>>>>>>>>>> Proposed Tasks:
>>>>>>>>>> 1) Comment - is the document clear enough or where is there a gap
>>>>>>>>>> in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>>> --> also, scan the current wiki and find sections you think
>>>>>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>>>>>> great.
>>>>>>>>>> 2) Based on my comments above, create a mockup of the landing
>>>>>>>>>> page (Meta Cyrus?)
>>>>>>>>>> --> also, scan other Apache projects to find landing pages
>>>>>>>>>> that you like
>>>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence
>>>>>>>>>> with links (james or ?)
>>>>>>>>>>
>>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>>
>>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>>
>>>>>>>>>> thanks
>>>>>>>>>> James
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>>
>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>
>>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi James,
>>>>>>>>>>> I am a good UI/UX and web developer who can Design and develop a
>>>>>>>>>>> good user reliable website.
>>>>>>>>>>> Where I can start??
>>>>>>>>>>> Regards,
>>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>>
>>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> All -
>>>>>>>>>>>>
>>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+
>>>>>>>>>>>> years since we did a clean sweep of it. We also have a front landing page
>>>>>>>>>>>> at https://fineract.apache.org that could be better at
>>>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>>>> me?
>>>>>>>>>>>>
>>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>>> ---
>>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>>
>>>>>>>>>>>> - Add blog feed
>>>>>>>>>>>> - Add feed to dev list
>>>>>>>>>>>> - Include FAQ
>>>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>>>
>>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should
>>>>>>>>>>>> have a top level split on the main page as well, or perhaps a separate
>>>>>>>>>>>> landing page for FineractCN.
>>>>>>>>>>>>
>>>>>>>>>>>> ---
>>>>>>>>>>>> On the wiki - new suggested structure (figure out how to show
>>>>>>>>>>>> two levels):
>>>>>>>>>>>>
>>>>>>>>>>>> - FAQ
>>>>>>>>>>>> - About Fineract
>>>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>>>> - About FineractCN
>>>>>>>>>>>> - TBD
>>>>>>>>>>>> - Project Management
>>>>>>>>>>>> - Quarterly reports to the Apache Board (this needs to
>>>>>>>>>>>> be more prominent)
>>>>>>>>>>>> - Community meetings organized by date (most recent at
>>>>>>>>>>>> top)
>>>>>>>>>>>> - Surveys
>>>>>>>>>>>> - Release processes
>>>>>>>>>>>> - How do I get involved?
>>>>>>>>>>>> - Committer guides
>>>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>>>> - Standards
>>>>>>>>>>>> - Documentation
>>>>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>>>>> documentation.
>>>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc)
>>>>>>>>>>>> ... all go to blog
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>>
>>>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> FINERACT
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> FINERACT CN
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> How-to articles
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>>>> -
>>>>>>>>>>>> Meeting notes
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>> Sent from Gmail Mobile
>>>>>>>>
>>>>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>> --
>> Sent from Gmail Mobile
>>
> --
Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Yes I'll be sharing the scree recorded video here shortly. Then you can
review.
On Sat, 18 Feb, 2023, 9:42 pm James Dailey, <ja...@gmail.com> wrote:
> We should review it before you make it live. Screenshots or graphics
> here?
>
> On Sat, Feb 18, 2023 at 8:01 AM Meta Cyrus <in...@gmail.com> wrote:
>
>> Hi James,
>> I have done with the UI will be pushing the code in a day on the repo.
>> Will it be okay??
>>
>>
>> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> Hi Meta - Any updates from you on this?
>>>
>>>
>>>
>>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>>> Okay lemme begin the work.
>>>>
>>>>
>>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>>
>>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>> I've been through the website and got it closely that what exact is
>>>>>> there on the website. I'll create a static mockup for the website.
>>>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>>>> experienced first comes to the website got confused of what's happening and
>>>>>> how things are going we can work upon it.
>>>>>> Also I have a question are we going to implement blogger on
>>>>>> that website? I have ability to work on static websites where the data
>>>>>> comes from dynamic CMS.
>>>>>> So I can work on tha too....
>>>>>> Regards,
>>>>>> Inzemamul Haq
>>>>>>
>>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Inzemamul Haq -
>>>>>>>
>>>>>>> Appreciate the response. This is revising our single page website
>>>>>>> for the project, so not an app. The content needs to be largely static or
>>>>>>> to pick up content we regularly post on blog. The current site is basic
>>>>>>> html. Just making sure we’re talking about the same thing.
>>>>>>>
>>>>>>> Fineract.Apache.org
>>>>>>>
>>>>>>> Figma I associate w more complex flows. What’s needed is a design
>>>>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>>>>> audience and what’s their need when they land on the page.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>> First I will create mockup using the figma where we can get a
>>>>>>>> better Idea of what exactly has to be happen. By the 16th of Feb I'll come
>>>>>>>> up with a design also will share here in the thread and we can get comments
>>>>>>>> in the meeting.
>>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Inzemamul Haq
>>>>>>>>
>>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>>>> people who said they'd like to be involved.
>>>>>>>>>
>>>>>>>>> I have a few tasks that I think may suit this group and then we
>>>>>>>>> can share back here on list and also hold a meeting on zoom in mid
>>>>>>>>> February.
>>>>>>>>> Feb 16th?
>>>>>>>>>
>>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>>
>>>>>>>>> Proposed Tasks:
>>>>>>>>> 1) Comment - is the document clear enough or where is there a gap
>>>>>>>>> in content (Bruce, Tekle? - start a thread about this)
>>>>>>>>> --> also, scan the current wiki and find sections you think
>>>>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>>>>> great.
>>>>>>>>> 2) Based on my comments above, create a mockup of the landing page
>>>>>>>>> (Meta Cyrus?)
>>>>>>>>> --> also, scan other Apache projects to find landing pages
>>>>>>>>> that you like
>>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>>> 4) Generate a new outline for the wiki and post on confluence with
>>>>>>>>> links (james or ?)
>>>>>>>>>
>>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>>
>>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>>
>>>>>>>>> thanks
>>>>>>>>> James
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>>>
>>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>>
>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>
>>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi James,
>>>>>>>>>> I am a good UI/UX and web developer who can Design and develop a
>>>>>>>>>> good user reliable website.
>>>>>>>>>> Where I can start??
>>>>>>>>>> Regards,
>>>>>>>>>> Inzemamul Haq
>>>>>>>>>>
>>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> All -
>>>>>>>>>>>
>>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years
>>>>>>>>>>> since we did a clean sweep of it. We also have a front landing page at
>>>>>>>>>>> https://fineract.apache.org that could be better at
>>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>>> me?
>>>>>>>>>>>
>>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>>> ---
>>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>>
>>>>>>>>>>> - Add blog feed
>>>>>>>>>>> - Add feed to dev list
>>>>>>>>>>> - Include FAQ
>>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>>
>>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should
>>>>>>>>>>> have a top level split on the main page as well, or perhaps a separate
>>>>>>>>>>> landing page for FineractCN.
>>>>>>>>>>>
>>>>>>>>>>> ---
>>>>>>>>>>> On the wiki - new suggested structure (figure out how to show
>>>>>>>>>>> two levels):
>>>>>>>>>>>
>>>>>>>>>>> - FAQ
>>>>>>>>>>> - About Fineract
>>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>>> - About FineractCN
>>>>>>>>>>> - TBD
>>>>>>>>>>> - Project Management
>>>>>>>>>>> - Quarterly reports to the Apache Board (this needs to be
>>>>>>>>>>> more prominent)
>>>>>>>>>>> - Community meetings organized by date (most recent at
>>>>>>>>>>> top)
>>>>>>>>>>> - Surveys
>>>>>>>>>>> - Release processes
>>>>>>>>>>> - How do I get involved?
>>>>>>>>>>> - Committer guides
>>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>>> - Standards
>>>>>>>>>>> - Documentation
>>>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>>>> documentation.
>>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc)
>>>>>>>>>>> ... all go to blog
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The current high level structure:
>>>>>>>>>>>
>>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> FINERACT
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> FINERACT CN
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> How-to articles
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>>> -
>>>>>>>>>>> Meeting notes
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>> Sent from Gmail Mobile
>>>>>>>
>>>>>> --
>>> Sent from Gmail Mobile
>>>
>> --
> Sent from Gmail Mobile
>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
We should review it before you make it live. Screenshots or graphics here?
On Sat, Feb 18, 2023 at 8:01 AM Meta Cyrus <in...@gmail.com> wrote:
> Hi James,
> I have done with the UI will be pushing the code in a day on the repo.
> Will it be okay??
>
>
> On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com>
> wrote:
>
>> Hi Meta - Any updates from you on this?
>>
>>
>>
>> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com> wrote:
>>
>>> Okay lemme begin the work.
>>>
>>>
>>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> +1
>>>>
>>>>
>>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>> I've been through the website and got it closely that what exact is
>>>>> there on the website. I'll create a static mockup for the website.
>>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>>> experienced first comes to the website got confused of what's happening and
>>>>> how things are going we can work upon it.
>>>>> Also I have a question are we going to implement blogger on
>>>>> that website? I have ability to work on static websites where the data
>>>>> comes from dynamic CMS.
>>>>> So I can work on tha too....
>>>>> Regards,
>>>>> Inzemamul Haq
>>>>>
>>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Inzemamul Haq -
>>>>>>
>>>>>> Appreciate the response. This is revising our single page website
>>>>>> for the project, so not an app. The content needs to be largely static or
>>>>>> to pick up content we regularly post on blog. The current site is basic
>>>>>> html. Just making sure we’re talking about the same thing.
>>>>>>
>>>>>> Fineract.Apache.org
>>>>>>
>>>>>> Figma I associate w more complex flows. What’s needed is a design
>>>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>>>> audience and what’s their need when they land on the page.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> First I will create mockup using the figma where we can get a better
>>>>>>> Idea of what exactly has to be happen. By the 16th of Feb I'll come up with
>>>>>>> a design also will share here in the thread and we can get comments in the
>>>>>>> meeting.
>>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>>> Regards,
>>>>>>>
>>>>>>> Inzemamul Haq
>>>>>>>
>>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>>> people who said they'd like to be involved.
>>>>>>>>
>>>>>>>> I have a few tasks that I think may suit this group and then we can
>>>>>>>> share back here on list and also hold a meeting on zoom in mid February.
>>>>>>>> Feb 16th?
>>>>>>>>
>>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>>
>>>>>>>> Proposed Tasks:
>>>>>>>> 1) Comment - is the document clear enough or where is there a gap
>>>>>>>> in content (Bruce, Tekle? - start a thread about this)
>>>>>>>> --> also, scan the current wiki and find sections you think
>>>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>>>> great.
>>>>>>>> 2) Based on my comments above, create a mockup of the landing page
>>>>>>>> (Meta Cyrus?)
>>>>>>>> --> also, scan other Apache projects to find landing pages that
>>>>>>>> you like
>>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>>> 4) Generate a new outline for the wiki and post on confluence with
>>>>>>>> links (james or ?)
>>>>>>>>
>>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>>
>>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>>
>>>>>>>> thanks
>>>>>>>> James
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>>
>>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>>
>>>>>>>>> Sent from my iPhone
>>>>>>>>>
>>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi James,
>>>>>>>>> I am a good UI/UX and web developer who can Design and develop a
>>>>>>>>> good user reliable website.
>>>>>>>>> Where I can start??
>>>>>>>>> Regards,
>>>>>>>>> Inzemamul Haq
>>>>>>>>>
>>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <
>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> All -
>>>>>>>>>>
>>>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years
>>>>>>>>>> since we did a clean sweep of it. We also have a front landing page at
>>>>>>>>>> https://fineract.apache.org that could be better at
>>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>>> me?
>>>>>>>>>>
>>>>>>>>>> PROPOSED CHANGES
>>>>>>>>>> ---
>>>>>>>>>> On the front "Landing" page:
>>>>>>>>>>
>>>>>>>>>> - Add blog feed
>>>>>>>>>> - Add feed to dev list
>>>>>>>>>> - Include FAQ
>>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>>
>>>>>>>>>> As we hope to see a FineractCN release soon, I think we should
>>>>>>>>>> have a top level split on the main page as well, or perhaps a separate
>>>>>>>>>> landing page for FineractCN.
>>>>>>>>>>
>>>>>>>>>> ---
>>>>>>>>>> On the wiki - new suggested structure (figure out how to show two
>>>>>>>>>> levels):
>>>>>>>>>>
>>>>>>>>>> - FAQ
>>>>>>>>>> - About Fineract
>>>>>>>>>> - New top level functional descriptions
>>>>>>>>>> - About FineractCN
>>>>>>>>>> - TBD
>>>>>>>>>> - Project Management
>>>>>>>>>> - Quarterly reports to the Apache Board (this needs to be
>>>>>>>>>> more prominent)
>>>>>>>>>> - Community meetings organized by date (most recent at
>>>>>>>>>> top)
>>>>>>>>>> - Surveys
>>>>>>>>>> - Release processes
>>>>>>>>>> - How do I get involved?
>>>>>>>>>> - Committer guides
>>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>>> - Standards
>>>>>>>>>> - Documentation
>>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>>> documentation.
>>>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc)
>>>>>>>>>> ... all go to blog
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The current high level structure:
>>>>>>>>>>
>>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> FINERACT
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> FINERACT CN
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> Fineract Project Security Report
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> How-to articles
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>>> -
>>>>>>>>>> Meeting notes
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>> Sent from Gmail Mobile
>>>>>>
>>>>> --
>> Sent from Gmail Mobile
>>
> --
Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Hi James,
I have done with the UI will be pushing the code in a day on the repo. Will
it be okay??
On Sat, 18 Feb, 2023, 9:27 pm James Dailey, <ja...@gmail.com> wrote:
> Hi Meta - Any updates from you on this?
>
>
>
> On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com> wrote:
>
>> Okay lemme begin the work.
>>
>>
>> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>>
>>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>> I've been through the website and got it closely that what exact is
>>>> there on the website. I'll create a static mockup for the website.
>>>> For the ui/ux part what I am saying is that whether anyone new or
>>>> experienced first comes to the website got confused of what's happening and
>>>> how things are going we can work upon it.
>>>> Also I have a question are we going to implement blogger on
>>>> that website? I have ability to work on static websites where the data
>>>> comes from dynamic CMS.
>>>> So I can work on tha too....
>>>> Regards,
>>>> Inzemamul Haq
>>>>
>>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Inzemamul Haq -
>>>>>
>>>>> Appreciate the response. This is revising our single page website for
>>>>> the project, so not an app. The content needs to be largely static or to
>>>>> pick up content we regularly post on blog. The current site is basic html.
>>>>> Just making sure we’re talking about the same thing.
>>>>>
>>>>> Fineract.Apache.org
>>>>>
>>>>> Figma I associate w more complex flows. What’s needed is a design
>>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>>> audience and what’s their need when they land on the page.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>> First I will create mockup using the figma where we can get a better
>>>>>> Idea of what exactly has to be happen. By the 16th of Feb I'll come up with
>>>>>> a design also will share here in the thread and we can get comments in the
>>>>>> meeting.
>>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>>> Regards,
>>>>>>
>>>>>> Inzemamul Haq
>>>>>>
>>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> All those that volunteered for this - thank you. We have four
>>>>>>> people who said they'd like to be involved.
>>>>>>>
>>>>>>> I have a few tasks that I think may suit this group and then we can
>>>>>>> share back here on list and also hold a meeting on zoom in mid February.
>>>>>>> Feb 16th?
>>>>>>>
>>>>>>> First, everyone involved should read (or skim) this document:
>>>>>>> https://fineract.apache.org/docs/current/
>>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>>
>>>>>>> Proposed Tasks:
>>>>>>> 1) Comment - is the document clear enough or where is there a gap in
>>>>>>> content (Bruce, Tekle? - start a thread about this)
>>>>>>> --> also, scan the current wiki and find sections you think
>>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>>> great.
>>>>>>> 2) Based on my comments above, create a mockup of the landing page
>>>>>>> (Meta Cyrus?)
>>>>>>> --> also, scan other Apache projects to find landing pages that
>>>>>>> you like
>>>>>>> 3) Provide a document outline of the high level functional
>>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>>> 4) Generate a new outline for the wiki and post on confluence with
>>>>>>> links (james or ?)
>>>>>>>
>>>>>>> Those that volunteered, please comment on this plan.
>>>>>>>
>>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>>
>>>>>>> thanks
>>>>>>> James
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>>
>>>>>>>> Yes I’d also like to participate in this
>>>>>>>>
>>>>>>>> Sent from my iPhone
>>>>>>>>
>>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi James,
>>>>>>>> I am a good UI/UX and web developer who can Design and develop a
>>>>>>>> good user reliable website.
>>>>>>>> Where I can start??
>>>>>>>> Regards,
>>>>>>>> Inzemamul Haq
>>>>>>>>
>>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> All -
>>>>>>>>>
>>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years
>>>>>>>>> since we did a clean sweep of it. We also have a front landing page at
>>>>>>>>> https://fineract.apache.org that could be better at
>>>>>>>>> communicating the project and community. Who wants to work on this with
>>>>>>>>> me?
>>>>>>>>>
>>>>>>>>> PROPOSED CHANGES
>>>>>>>>> ---
>>>>>>>>> On the front "Landing" page:
>>>>>>>>>
>>>>>>>>> - Add blog feed
>>>>>>>>> - Add feed to dev list
>>>>>>>>> - Include FAQ
>>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>>
>>>>>>>>> As we hope to see a FineractCN release soon, I think we should
>>>>>>>>> have a top level split on the main page as well, or perhaps a separate
>>>>>>>>> landing page for FineractCN.
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>> On the wiki - new suggested structure (figure out how to show two
>>>>>>>>> levels):
>>>>>>>>>
>>>>>>>>> - FAQ
>>>>>>>>> - About Fineract
>>>>>>>>> - New top level functional descriptions
>>>>>>>>> - About FineractCN
>>>>>>>>> - TBD
>>>>>>>>> - Project Management
>>>>>>>>> - Quarterly reports to the Apache Board (this needs to be
>>>>>>>>> more prominent)
>>>>>>>>> - Community meetings organized by date (most recent at top)
>>>>>>>>> - Surveys
>>>>>>>>> - Release processes
>>>>>>>>> - How do I get involved?
>>>>>>>>> - Committer guides
>>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>>> - Standards
>>>>>>>>> - Documentation
>>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>>> documentation.
>>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc) ...
>>>>>>>>> all go to blog
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The current high level structure:
>>>>>>>>>
>>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> FINERACT
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> FINERACT CN
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> Fineract Project Security Report
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> How-to articles
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> ApacheCON Fineract Track
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>>> -
>>>>>>>>> Meeting notes
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>> --
> Sent from Gmail Mobile
>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Hi Meta - Any updates from you on this?
On Wed, Feb 1, 2023 at 9:06 AM Meta Cyrus <in...@gmail.com> wrote:
> Okay lemme begin the work.
>
>
> On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com>
> wrote:
>
>> +1
>>
>>
>> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com> wrote:
>>
>>> Hi
>>> I've been through the website and got it closely that what exact is
>>> there on the website. I'll create a static mockup for the website.
>>> For the ui/ux part what I am saying is that whether anyone new or
>>> experienced first comes to the website got confused of what's happening and
>>> how things are going we can work upon it.
>>> Also I have a question are we going to implement blogger on
>>> that website? I have ability to work on static websites where the data
>>> comes from dynamic CMS.
>>> So I can work on tha too....
>>> Regards,
>>> Inzemamul Haq
>>>
>>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> Inzemamul Haq -
>>>>
>>>> Appreciate the response. This is revising our single page website for
>>>> the project, so not an app. The content needs to be largely static or to
>>>> pick up content we regularly post on blog. The current site is basic html.
>>>> Just making sure we’re talking about the same thing.
>>>>
>>>> Fineract.Apache.org
>>>>
>>>> Figma I associate w more complex flows. What’s needed is a design
>>>> lens, in my view. But, a good UIX process does start with who’s the
>>>> audience and what’s their need when they land on the page.
>>>>
>>>>
>>>>
>>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>> First I will create mockup using the figma where we can get a better
>>>>> Idea of what exactly has to be happen. By the 16th of Feb I'll come up with
>>>>> a design also will share here in the thread and we can get comments in the
>>>>> meeting.
>>>>> I'll start looking other apache websites and get an overall UI/UX
>>>>> Regards,
>>>>>
>>>>> Inzemamul Haq
>>>>>
>>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> All those that volunteered for this - thank you. We have four people
>>>>>> who said they'd like to be involved.
>>>>>>
>>>>>> I have a few tasks that I think may suit this group and then we can
>>>>>> share back here on list and also hold a meeting on zoom in mid February.
>>>>>> Feb 16th?
>>>>>>
>>>>>> First, everyone involved should read (or skim) this document:
>>>>>> https://fineract.apache.org/docs/current/
>>>>>> and also look at the current wiki and landing page in detail.
>>>>>>
>>>>>> Proposed Tasks:
>>>>>> 1) Comment - is the document clear enough or where is there a gap in
>>>>>> content (Bruce, Tekle? - start a thread about this)
>>>>>> --> also, scan the current wiki and find sections you think
>>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>>> great.
>>>>>> 2) Based on my comments above, create a mockup of the landing page
>>>>>> (Meta Cyrus?)
>>>>>> --> also, scan other Apache projects to find landing pages that
>>>>>> you like
>>>>>> 3) Provide a document outline of the high level functional
>>>>>> description aimed at a Business Leader (Dick Dickson?)
>>>>>> 4) Generate a new outline for the wiki and post on confluence with
>>>>>> links (james or ?)
>>>>>>
>>>>>> Those that volunteered, please comment on this plan.
>>>>>>
>>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>>
>>>>>> thanks
>>>>>> James
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>>
>>>>>>> Yes I’d also like to participate in this
>>>>>>>
>>>>>>> Sent from my iPhone
>>>>>>>
>>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hi James,
>>>>>>> I am a good UI/UX and web developer who can Design and develop a
>>>>>>> good user reliable website.
>>>>>>> Where I can start??
>>>>>>> Regards,
>>>>>>> Inzemamul Haq
>>>>>>>
>>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> All -
>>>>>>>>
>>>>>>>> We have a lot of good content on the wiki but it's been 3+ years
>>>>>>>> since we did a clean sweep of it. We also have a front landing page at
>>>>>>>> https://fineract.apache.org that could be better at communicating
>>>>>>>> the project and community. Who wants to work on this with me?
>>>>>>>>
>>>>>>>> PROPOSED CHANGES
>>>>>>>> ---
>>>>>>>> On the front "Landing" page:
>>>>>>>>
>>>>>>>> - Add blog feed
>>>>>>>> - Add feed to dev list
>>>>>>>> - Include FAQ
>>>>>>>> - Split FineractCN and Fineract
>>>>>>>>
>>>>>>>> As we hope to see a FineractCN release soon, I think we should have
>>>>>>>> a top level split on the main page as well, or perhaps a separate landing
>>>>>>>> page for FineractCN.
>>>>>>>>
>>>>>>>> ---
>>>>>>>> On the wiki - new suggested structure (figure out how to show two
>>>>>>>> levels):
>>>>>>>>
>>>>>>>> - FAQ
>>>>>>>> - About Fineract
>>>>>>>> - New top level functional descriptions
>>>>>>>> - About FineractCN
>>>>>>>> - TBD
>>>>>>>> - Project Management
>>>>>>>> - Quarterly reports to the Apache Board (this needs to be
>>>>>>>> more prominent)
>>>>>>>> - Community meetings organized by date (most recent at top)
>>>>>>>> - Surveys
>>>>>>>> - Release processes
>>>>>>>> - How do I get involved?
>>>>>>>> - Committer guides
>>>>>>>> - Links to JIRA and GitHUB
>>>>>>>> - Standards
>>>>>>>> - Documentation
>>>>>>>> - Replace with links to the new dynamically generated
>>>>>>>> documentation.
>>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc) ...
>>>>>>>> all go to blog
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Are there things we should keep or not keep?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The current high level structure:
>>>>>>>>
>>>>>>>> - FAQ (frequently asked questions)
>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> FINERACT
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> FINERACT CN
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> Fineract Project Security Report
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> How-to articles
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> ApacheCON Fineract Track
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>>> -
>>>>>>>> Meeting notes
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>> --
Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Okay lemme begin the work.
On Wed, 1 Feb, 2023, 10:34 pm James Dailey, <ja...@gmail.com> wrote:
> +1
>
>
> On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com> wrote:
>
>> Hi
>> I've been through the website and got it closely that what exact is there
>> on the website. I'll create a static mockup for the website.
>> For the ui/ux part what I am saying is that whether anyone new or
>> experienced first comes to the website got confused of what's happening and
>> how things are going we can work upon it.
>> Also I have a question are we going to implement blogger on that website?
>> I have ability to work on static websites where the data comes from dynamic
>> CMS.
>> So I can work on tha too....
>> Regards,
>> Inzemamul Haq
>>
>> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> Inzemamul Haq -
>>>
>>> Appreciate the response. This is revising our single page website for
>>> the project, so not an app. The content needs to be largely static or to
>>> pick up content we regularly post on blog. The current site is basic html.
>>> Just making sure we’re talking about the same thing.
>>>
>>> Fineract.Apache.org
>>>
>>> Figma I associate w more complex flows. What’s needed is a design lens,
>>> in my view. But, a good UIX process does start with who’s the audience and
>>> what’s their need when they land on the page.
>>>
>>>
>>>
>>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>> First I will create mockup using the figma where we can get a better
>>>> Idea of what exactly has to be happen. By the 16th of Feb I'll come up with
>>>> a design also will share here in the thread and we can get comments in the
>>>> meeting.
>>>> I'll start looking other apache websites and get an overall UI/UX
>>>> Regards,
>>>>
>>>> Inzemamul Haq
>>>>
>>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> All those that volunteered for this - thank you. We have four people
>>>>> who said they'd like to be involved.
>>>>>
>>>>> I have a few tasks that I think may suit this group and then we can
>>>>> share back here on list and also hold a meeting on zoom in mid February.
>>>>> Feb 16th?
>>>>>
>>>>> First, everyone involved should read (or skim) this document:
>>>>> https://fineract.apache.org/docs/current/
>>>>> and also look at the current wiki and landing page in detail.
>>>>>
>>>>> Proposed Tasks:
>>>>> 1) Comment - is the document clear enough or where is there a gap in
>>>>> content (Bruce, Tekle? - start a thread about this)
>>>>> --> also, scan the current wiki and find sections you think
>>>>> belong being "brought over". compile a list of those pages. If none,
>>>>> great.
>>>>> 2) Based on my comments above, create a mockup of the landing page
>>>>> (Meta Cyrus?)
>>>>> --> also, scan other Apache projects to find landing pages that
>>>>> you like
>>>>> 3) Provide a document outline of the high level functional description
>>>>> aimed at a Business Leader (Dick Dickson?)
>>>>> 4) Generate a new outline for the wiki and post on confluence with
>>>>> links (james or ?)
>>>>>
>>>>> Those that volunteered, please comment on this plan.
>>>>>
>>>>> Anyone else is welcome to join but please follow this thread.
>>>>>
>>>>> thanks
>>>>> James
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>>
>>>>>> Yes I’d also like to participate in this
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hi James,
>>>>>> I am a good UI/UX and web developer who can Design and develop a good
>>>>>> user reliable website.
>>>>>> Where I can start??
>>>>>> Regards,
>>>>>> Inzemamul Haq
>>>>>>
>>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> All -
>>>>>>>
>>>>>>> We have a lot of good content on the wiki but it's been 3+ years
>>>>>>> since we did a clean sweep of it. We also have a front landing page at
>>>>>>> https://fineract.apache.org that could be better at communicating
>>>>>>> the project and community. Who wants to work on this with me?
>>>>>>>
>>>>>>> PROPOSED CHANGES
>>>>>>> ---
>>>>>>> On the front "Landing" page:
>>>>>>>
>>>>>>> - Add blog feed
>>>>>>> - Add feed to dev list
>>>>>>> - Include FAQ
>>>>>>> - Split FineractCN and Fineract
>>>>>>>
>>>>>>> As we hope to see a FineractCN release soon, I think we should have
>>>>>>> a top level split on the main page as well, or perhaps a separate landing
>>>>>>> page for FineractCN.
>>>>>>>
>>>>>>> ---
>>>>>>> On the wiki - new suggested structure (figure out how to show two
>>>>>>> levels):
>>>>>>>
>>>>>>> - FAQ
>>>>>>> - About Fineract
>>>>>>> - New top level functional descriptions
>>>>>>> - About FineractCN
>>>>>>> - TBD
>>>>>>> - Project Management
>>>>>>> - Quarterly reports to the Apache Board (this needs to be
>>>>>>> more prominent)
>>>>>>> - Community meetings organized by date (most recent at top)
>>>>>>> - Surveys
>>>>>>> - Release processes
>>>>>>> - How do I get involved?
>>>>>>> - Committer guides
>>>>>>> - Links to JIRA and GitHUB
>>>>>>> - Standards
>>>>>>> - Documentation
>>>>>>> - Replace with links to the new dynamically generated
>>>>>>> documentation.
>>>>>>> - Move Comms related stuff (talks, opinion pieces, etc) ...
>>>>>>> all go to blog
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Are there things we should keep or not keep?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The current high level structure:
>>>>>>>
>>>>>>> - FAQ (frequently asked questions)
>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> FINERACT
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> FINERACT CN
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> Fineract Data, Credit Scoring, AI
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> Fineract Project Security Report
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> COMMS: Blogs, Talks, and Links
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> How-to articles
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> ApacheCON Fineract Track
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>>> -
>>>>>>> Meeting notes
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>> Sent from Gmail Mobile
>>>
>>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
+1
On Wed, Feb 1, 2023 at 8:57 AM Meta Cyrus <in...@gmail.com> wrote:
> Hi
> I've been through the website and got it closely that what exact is there
> on the website. I'll create a static mockup for the website.
> For the ui/ux part what I am saying is that whether anyone new or
> experienced first comes to the website got confused of what's happening and
> how things are going we can work upon it.
> Also I have a question are we going to implement blogger on that website?
> I have ability to work on static websites where the data comes from dynamic
> CMS.
> So I can work on tha too....
> Regards,
> Inzemamul Haq
>
> On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com>
> wrote:
>
>> Inzemamul Haq -
>>
>> Appreciate the response. This is revising our single page website for
>> the project, so not an app. The content needs to be largely static or to
>> pick up content we regularly post on blog. The current site is basic html.
>> Just making sure we’re talking about the same thing.
>>
>> Fineract.Apache.org
>>
>> Figma I associate w more complex flows. What’s needed is a design lens,
>> in my view. But, a good UIX process does start with who’s the audience and
>> what’s their need when they land on the page.
>>
>>
>>
>> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com>
>> wrote:
>>
>>> Hi,
>>> First I will create mockup using the figma where we can get a better
>>> Idea of what exactly has to be happen. By the 16th of Feb I'll come up with
>>> a design also will share here in the thread and we can get comments in the
>>> meeting.
>>> I'll start looking other apache websites and get an overall UI/UX
>>> Regards,
>>>
>>> Inzemamul Haq
>>>
>>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> All those that volunteered for this - thank you. We have four people
>>>> who said they'd like to be involved.
>>>>
>>>> I have a few tasks that I think may suit this group and then we can
>>>> share back here on list and also hold a meeting on zoom in mid February.
>>>> Feb 16th?
>>>>
>>>> First, everyone involved should read (or skim) this document:
>>>> https://fineract.apache.org/docs/current/
>>>> and also look at the current wiki and landing page in detail.
>>>>
>>>> Proposed Tasks:
>>>> 1) Comment - is the document clear enough or where is there a gap in
>>>> content (Bruce, Tekle? - start a thread about this)
>>>> --> also, scan the current wiki and find sections you think belong
>>>> being "brought over". compile a list of those pages. If none, great.
>>>> 2) Based on my comments above, create a mockup of the landing page
>>>> (Meta Cyrus?)
>>>> --> also, scan other Apache projects to find landing pages that you
>>>> like
>>>> 3) Provide a document outline of the high level functional description
>>>> aimed at a Business Leader (Dick Dickson?)
>>>> 4) Generate a new outline for the wiki and post on confluence with
>>>> links (james or ?)
>>>>
>>>> Those that volunteered, please comment on this plan.
>>>>
>>>> Anyone else is welcome to join but please follow this thread.
>>>>
>>>> thanks
>>>> James
>>>>
>>>>
>>>>
>>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>>
>>>>> Yes I’d also like to participate in this
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com> wrote:
>>>>>
>>>>>
>>>>> Hi James,
>>>>> I am a good UI/UX and web developer who can Design and develop a good
>>>>> user reliable website.
>>>>> Where I can start??
>>>>> Regards,
>>>>> Inzemamul Haq
>>>>>
>>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> All -
>>>>>>
>>>>>> We have a lot of good content on the wiki but it's been 3+ years
>>>>>> since we did a clean sweep of it. We also have a front landing page at
>>>>>> https://fineract.apache.org that could be better at communicating
>>>>>> the project and community. Who wants to work on this with me?
>>>>>>
>>>>>> PROPOSED CHANGES
>>>>>> ---
>>>>>> On the front "Landing" page:
>>>>>>
>>>>>> - Add blog feed
>>>>>> - Add feed to dev list
>>>>>> - Include FAQ
>>>>>> - Split FineractCN and Fineract
>>>>>>
>>>>>> As we hope to see a FineractCN release soon, I think we should have a
>>>>>> top level split on the main page as well, or perhaps a separate landing
>>>>>> page for FineractCN.
>>>>>>
>>>>>> ---
>>>>>> On the wiki - new suggested structure (figure out how to show two
>>>>>> levels):
>>>>>>
>>>>>> - FAQ
>>>>>> - About Fineract
>>>>>> - New top level functional descriptions
>>>>>> - About FineractCN
>>>>>> - TBD
>>>>>> - Project Management
>>>>>> - Quarterly reports to the Apache Board (this needs to be more
>>>>>> prominent)
>>>>>> - Community meetings organized by date (most recent at top)
>>>>>> - Surveys
>>>>>> - Release processes
>>>>>> - How do I get involved?
>>>>>> - Committer guides
>>>>>> - Links to JIRA and GitHUB
>>>>>> - Standards
>>>>>> - Documentation
>>>>>> - Replace with links to the new dynamically generated
>>>>>> documentation.
>>>>>> - Move Comms related stuff (talks, opinion pieces, etc) ...
>>>>>> all go to blog
>>>>>>
>>>>>>
>>>>>>
>>>>>> Are there things we should keep or not keep?
>>>>>>
>>>>>>
>>>>>>
>>>>>> The current high level structure:
>>>>>>
>>>>>> - FAQ (frequently asked questions)
>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>>> -
>>>>>> GETTING INVOLVED (commit, contribute)
>>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>>> -
>>>>>> FINERACT
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>>> -
>>>>>> FINERACT CN
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>>> -
>>>>>> Fineract Data, Credit Scoring, AI
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>>> -
>>>>>> Fineract Project Security Report
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>>> -
>>>>>> COMMS: Blogs, Talks, and Links
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>>> -
>>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>>> -
>>>>>> How-to articles
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>>> -
>>>>>> ApacheCON Fineract Track
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>>> -
>>>>>> Meeting notes
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>> Sent from Gmail Mobile
>>
>
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Hi
I've been through the website and got it closely that what exact is there
on the website. I'll create a static mockup for the website.
For the ui/ux part what I am saying is that whether anyone new or
experienced first comes to the website got confused of what's happening and
how things are going we can work upon it.
Also I have a question are we going to implement blogger on that website? I
have ability to work on static websites where the data comes from dynamic
CMS.
So I can work on tha too....
Regards,
Inzemamul Haq
On Wed, 1 Feb, 2023, 10:13 pm James Dailey, <ja...@gmail.com> wrote:
> Inzemamul Haq -
>
> Appreciate the response. This is revising our single page website for the
> project, so not an app. The content needs to be largely static or to pick
> up content we regularly post on blog. The current site is basic html. Just
> making sure we’re talking about the same thing.
>
> Fineract.Apache.org
>
> Figma I associate w more complex flows. What’s needed is a design lens,
> in my view. But, a good UIX process does start with who’s the audience and
> what’s their need when they land on the page.
>
>
>
> On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com> wrote:
>
>> Hi,
>> First I will create mockup using the figma where we can get a better Idea
>> of what exactly has to be happen. By the 16th of Feb I'll come up with a
>> design also will share here in the thread and we can get comments in the
>> meeting.
>> I'll start looking other apache websites and get an overall UI/UX
>> Regards,
>>
>> Inzemamul Haq
>>
>> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> All those that volunteered for this - thank you. We have four people
>>> who said they'd like to be involved.
>>>
>>> I have a few tasks that I think may suit this group and then we can
>>> share back here on list and also hold a meeting on zoom in mid February.
>>> Feb 16th?
>>>
>>> First, everyone involved should read (or skim) this document:
>>> https://fineract.apache.org/docs/current/
>>> and also look at the current wiki and landing page in detail.
>>>
>>> Proposed Tasks:
>>> 1) Comment - is the document clear enough or where is there a gap in
>>> content (Bruce, Tekle? - start a thread about this)
>>> --> also, scan the current wiki and find sections you think belong
>>> being "brought over". compile a list of those pages. If none, great.
>>> 2) Based on my comments above, create a mockup of the landing page (Meta
>>> Cyrus?)
>>> --> also, scan other Apache projects to find landing pages that you
>>> like
>>> 3) Provide a document outline of the high level functional description
>>> aimed at a Business Leader (Dick Dickson?)
>>> 4) Generate a new outline for the wiki and post on confluence with links
>>> (james or ?)
>>>
>>> Those that volunteered, please comment on this plan.
>>>
>>> Anyone else is welcome to join but please follow this thread.
>>>
>>> thanks
>>> James
>>>
>>>
>>>
>>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>>
>>>> Yes I’d also like to participate in this
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com> wrote:
>>>>
>>>>
>>>> Hi James,
>>>> I am a good UI/UX and web developer who can Design and develop a good
>>>> user reliable website.
>>>> Where I can start??
>>>> Regards,
>>>> Inzemamul Haq
>>>>
>>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> All -
>>>>>
>>>>> We have a lot of good content on the wiki but it's been 3+ years since
>>>>> we did a clean sweep of it. We also have a front landing page at
>>>>> https://fineract.apache.org that could be better at communicating
>>>>> the project and community. Who wants to work on this with me?
>>>>>
>>>>> PROPOSED CHANGES
>>>>> ---
>>>>> On the front "Landing" page:
>>>>>
>>>>> - Add blog feed
>>>>> - Add feed to dev list
>>>>> - Include FAQ
>>>>> - Split FineractCN and Fineract
>>>>>
>>>>> As we hope to see a FineractCN release soon, I think we should have a
>>>>> top level split on the main page as well, or perhaps a separate landing
>>>>> page for FineractCN.
>>>>>
>>>>> ---
>>>>> On the wiki - new suggested structure (figure out how to show two
>>>>> levels):
>>>>>
>>>>> - FAQ
>>>>> - About Fineract
>>>>> - New top level functional descriptions
>>>>> - About FineractCN
>>>>> - TBD
>>>>> - Project Management
>>>>> - Quarterly reports to the Apache Board (this needs to be more
>>>>> prominent)
>>>>> - Community meetings organized by date (most recent at top)
>>>>> - Surveys
>>>>> - Release processes
>>>>> - How do I get involved?
>>>>> - Committer guides
>>>>> - Links to JIRA and GitHUB
>>>>> - Standards
>>>>> - Documentation
>>>>> - Replace with links to the new dynamically generated
>>>>> documentation.
>>>>> - Move Comms related stuff (talks, opinion pieces, etc) ... all
>>>>> go to blog
>>>>>
>>>>>
>>>>>
>>>>> Are there things we should keep or not keep?
>>>>>
>>>>>
>>>>>
>>>>> The current high level structure:
>>>>>
>>>>> - FAQ (frequently asked questions)
>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>>> -
>>>>> GETTING INVOLVED (commit, contribute)
>>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>>> -
>>>>> FINERACT
>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>>> -
>>>>> FINERACT CN
>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>>> -
>>>>> Fineract Data, Credit Scoring, AI
>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>>> -
>>>>> Fineract Project Security Report
>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>>> -
>>>>> COMMS: Blogs, Talks, and Links
>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>>> -
>>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>>> -
>>>>> How-to articles
>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>>> -
>>>>> ApacheCON Fineract Track
>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>>> -
>>>>> Meeting notes
>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
> Sent from Gmail Mobile
>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
Inzemamul Haq -
Appreciate the response. This is revising our single page website for the
project, so not an app. The content needs to be largely static or to pick
up content we regularly post on blog. The current site is basic html. Just
making sure we’re talking about the same thing.
Fineract.Apache.org
Figma I associate w more complex flows. What’s needed is a design lens, in
my view. But, a good UIX process does start with who’s the audience and
what’s their need when they land on the page.
On Tue, Jan 31, 2023 at 8:06 PM Meta Cyrus <in...@gmail.com> wrote:
> Hi,
> First I will create mockup using the figma where we can get a better Idea
> of what exactly has to be happen. By the 16th of Feb I'll come up with a
> design also will share here in the thread and we can get comments in the
> meeting.
> I'll start looking other apache websites and get an overall UI/UX
> Regards,
>
> Inzemamul Haq
>
> On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com> wrote:
>
>> All those that volunteered for this - thank you. We have four people who
>> said they'd like to be involved.
>>
>> I have a few tasks that I think may suit this group and then we can share
>> back here on list and also hold a meeting on zoom in mid February.
>> Feb 16th?
>>
>> First, everyone involved should read (or skim) this document:
>> https://fineract.apache.org/docs/current/
>> and also look at the current wiki and landing page in detail.
>>
>> Proposed Tasks:
>> 1) Comment - is the document clear enough or where is there a gap in
>> content (Bruce, Tekle? - start a thread about this)
>> --> also, scan the current wiki and find sections you think belong
>> being "brought over". compile a list of those pages. If none, great.
>> 2) Based on my comments above, create a mockup of the landing page (Meta
>> Cyrus?)
>> --> also, scan other Apache projects to find landing pages that you
>> like
>> 3) Provide a document outline of the high level functional description
>> aimed at a Business Leader (Dick Dickson?)
>> 4) Generate a new outline for the wiki and post on confluence with links
>> (james or ?)
>>
>> Those that volunteered, please comment on this plan.
>>
>> Anyone else is welcome to join but please follow this thread.
>>
>> thanks
>> James
>>
>>
>>
>> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>>
>>> Yes I’d also like to participate in this
>>>
>>> Sent from my iPhone
>>>
>>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com> wrote:
>>>
>>>
>>> Hi James,
>>> I am a good UI/UX and web developer who can Design and develop a good
>>> user reliable website.
>>> Where I can start??
>>> Regards,
>>> Inzemamul Haq
>>>
>>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>
>>> wrote:
>>>
>>>> All -
>>>>
>>>> We have a lot of good content on the wiki but it's been 3+ years since
>>>> we did a clean sweep of it. We also have a front landing page at
>>>> https://fineract.apache.org that could be better at communicating the
>>>> project and community. Who wants to work on this with me?
>>>>
>>>> PROPOSED CHANGES
>>>> ---
>>>> On the front "Landing" page:
>>>>
>>>> - Add blog feed
>>>> - Add feed to dev list
>>>> - Include FAQ
>>>> - Split FineractCN and Fineract
>>>>
>>>> As we hope to see a FineractCN release soon, I think we should have a
>>>> top level split on the main page as well, or perhaps a separate landing
>>>> page for FineractCN.
>>>>
>>>> ---
>>>> On the wiki - new suggested structure (figure out how to show two
>>>> levels):
>>>>
>>>> - FAQ
>>>> - About Fineract
>>>> - New top level functional descriptions
>>>> - About FineractCN
>>>> - TBD
>>>> - Project Management
>>>> - Quarterly reports to the Apache Board (this needs to be more
>>>> prominent)
>>>> - Community meetings organized by date (most recent at top)
>>>> - Surveys
>>>> - Release processes
>>>> - How do I get involved?
>>>> - Committer guides
>>>> - Links to JIRA and GitHUB
>>>> - Standards
>>>> - Documentation
>>>> - Replace with links to the new dynamically generated
>>>> documentation.
>>>> - Move Comms related stuff (talks, opinion pieces, etc) ... all
>>>> go to blog
>>>>
>>>>
>>>>
>>>> Are there things we should keep or not keep?
>>>>
>>>>
>>>>
>>>> The current high level structure:
>>>>
>>>> - FAQ (frequently asked questions)
>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>>> -
>>>> GETTING INVOLVED (commit, contribute)
>>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>>> -
>>>> FINERACT
>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>>> -
>>>> FINERACT CN
>>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>>> -
>>>> Fineract Data, Credit Scoring, AI
>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>>> -
>>>> Fineract Project Security Report
>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>>> -
>>>> COMMS: Blogs, Talks, and Links
>>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>>> -
>>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>>> -
>>>> How-to articles
>>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>>> -
>>>> ApacheCON Fineract Track
>>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>>> -
>>>> Meeting notes
>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
Sent from Gmail Mobile
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Hi,
First I will create mockup using the figma where we can get a better Idea
of what exactly has to be happen. By the 16th of Feb I'll come up with a
design also will share here in the thread and we can get comments in the
meeting.
I'll start looking other apache websites and get an overall UI/UX
Regards,
Inzemamul Haq
On Wed, 1 Feb, 2023, 6:07 am James Dailey, <ja...@gmail.com> wrote:
> All those that volunteered for this - thank you. We have four people who
> said they'd like to be involved.
>
> I have a few tasks that I think may suit this group and then we can share
> back here on list and also hold a meeting on zoom in mid February.
> Feb 16th?
>
> First, everyone involved should read (or skim) this document:
> https://fineract.apache.org/docs/current/
> and also look at the current wiki and landing page in detail.
>
> Proposed Tasks:
> 1) Comment - is the document clear enough or where is there a gap in
> content (Bruce, Tekle? - start a thread about this)
> --> also, scan the current wiki and find sections you think belong
> being "brought over". compile a list of those pages. If none, great.
> 2) Based on my comments above, create a mockup of the landing page (Meta
> Cyrus?)
> --> also, scan other Apache projects to find landing pages that you
> like
> 3) Provide a document outline of the high level functional description
> aimed at a Business Leader (Dick Dickson?)
> 4) Generate a new outline for the wiki and post on confluence with links
> (james or ?)
>
> Those that volunteered, please comment on this plan.
>
> Anyone else is welcome to join but please follow this thread.
>
> thanks
> James
>
>
>
> On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
>
>> Yes I’d also like to participate in this
>>
>> Sent from my iPhone
>>
>> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com> wrote:
>>
>>
>> Hi James,
>> I am a good UI/UX and web developer who can Design and develop a good
>> user reliable website.
>> Where I can start??
>> Regards,
>> Inzemamul Haq
>>
>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>
>> wrote:
>>
>>> All -
>>>
>>> We have a lot of good content on the wiki but it's been 3+ years since
>>> we did a clean sweep of it. We also have a front landing page at
>>> https://fineract.apache.org that could be better at communicating the
>>> project and community. Who wants to work on this with me?
>>>
>>> PROPOSED CHANGES
>>> ---
>>> On the front "Landing" page:
>>>
>>> - Add blog feed
>>> - Add feed to dev list
>>> - Include FAQ
>>> - Split FineractCN and Fineract
>>>
>>> As we hope to see a FineractCN release soon, I think we should have a
>>> top level split on the main page as well, or perhaps a separate landing
>>> page for FineractCN.
>>>
>>> ---
>>> On the wiki - new suggested structure (figure out how to show two
>>> levels):
>>>
>>> - FAQ
>>> - About Fineract
>>> - New top level functional descriptions
>>> - About FineractCN
>>> - TBD
>>> - Project Management
>>> - Quarterly reports to the Apache Board (this needs to be more
>>> prominent)
>>> - Community meetings organized by date (most recent at top)
>>> - Surveys
>>> - Release processes
>>> - How do I get involved?
>>> - Committer guides
>>> - Links to JIRA and GitHUB
>>> - Standards
>>> - Documentation
>>> - Replace with links to the new dynamically generated
>>> documentation.
>>> - Move Comms related stuff (talks, opinion pieces, etc) ... all
>>> go to blog
>>>
>>>
>>>
>>> Are there things we should keep or not keep?
>>>
>>>
>>>
>>> The current high level structure:
>>>
>>> - FAQ (frequently asked questions)
>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>>> -
>>> GETTING INVOLVED (commit, contribute)
>>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>>> -
>>> FINERACT
>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>>> -
>>> FINERACT CN
>>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>>> -
>>> Fineract Data, Credit Scoring, AI
>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>>> -
>>> Fineract Project Security Report
>>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>>> -
>>> COMMS: Blogs, Talks, and Links
>>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>>> -
>>> ApacheCon EU 2016 Fineract Speaker's Notes
>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>>> -
>>> How-to articles
>>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>>> -
>>> ApacheCON Fineract Track
>>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>>> -
>>> Meeting notes
>>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>>
>>>
>>>
>>>
>>>
>>>
Re: Website and Wiki for Fineract updates
Posted by James Dailey <ja...@gmail.com>.
All those that volunteered for this - thank you. We have four people who
said they'd like to be involved.
I have a few tasks that I think may suit this group and then we can share
back here on list and also hold a meeting on zoom in mid February.
Feb 16th?
First, everyone involved should read (or skim) this document:
https://fineract.apache.org/docs/current/
and also look at the current wiki and landing page in detail.
Proposed Tasks:
1) Comment - is the document clear enough or where is there a gap in
content (Bruce, Tekle? - start a thread about this)
--> also, scan the current wiki and find sections you think belong
being "brought over". compile a list of those pages. If none, great.
2) Based on my comments above, create a mockup of the landing page (Meta
Cyrus?)
--> also, scan other Apache projects to find landing pages that you
like
3) Provide a document outline of the high level functional description
aimed at a Business Leader (Dick Dickson?)
4) Generate a new outline for the wiki and post on confluence with links
(james or ?)
Those that volunteered, please comment on this plan.
Anyone else is welcome to join but please follow this thread.
thanks
James
On Tue, Jan 31, 2023 at 2:39 AM Dick Dickson <d...@gwocu.com> wrote:
> Yes I’d also like to participate in this
>
> Sent from my iPhone
>
> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com> wrote:
>
>
> Hi James,
> I am a good UI/UX and web developer who can Design and develop a good user
> reliable website.
> Where I can start??
> Regards,
> Inzemamul Haq
>
> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com>
> wrote:
>
>> All -
>>
>> We have a lot of good content on the wiki but it's been 3+ years since we
>> did a clean sweep of it. We also have a front landing page at
>> https://fineract.apache.org that could be better at communicating the
>> project and community. Who wants to work on this with me?
>>
>> PROPOSED CHANGES
>> ---
>> On the front "Landing" page:
>>
>> - Add blog feed
>> - Add feed to dev list
>> - Include FAQ
>> - Split FineractCN and Fineract
>>
>> As we hope to see a FineractCN release soon, I think we should have a top
>> level split on the main page as well, or perhaps a separate landing page
>> for FineractCN.
>>
>> ---
>> On the wiki - new suggested structure (figure out how to show two
>> levels):
>>
>> - FAQ
>> - About Fineract
>> - New top level functional descriptions
>> - About FineractCN
>> - TBD
>> - Project Management
>> - Quarterly reports to the Apache Board (this needs to be more
>> prominent)
>> - Community meetings organized by date (most recent at top)
>> - Surveys
>> - Release processes
>> - How do I get involved?
>> - Committer guides
>> - Links to JIRA and GitHUB
>> - Standards
>> - Documentation
>> - Replace with links to the new dynamically generated
>> documentation.
>> - Move Comms related stuff (talks, opinion pieces, etc) ... all go
>> to blog
>>
>>
>>
>> Are there things we should keep or not keep?
>>
>>
>>
>> The current high level structure:
>>
>> - FAQ (frequently asked questions)
>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
>> -
>> GETTING INVOLVED (commit, contribute)
>> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
>> -
>> FINERACT
>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
>> -
>> FINERACT CN
>> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
>> -
>> Fineract Data, Credit Scoring, AI
>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
>> -
>> Fineract Project Security Report
>> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
>> -
>> COMMS: Blogs, Talks, and Links
>> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
>> -
>> ApacheCon EU 2016 Fineract Speaker's Notes
>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
>> -
>> How-to articles
>> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
>> -
>> ApacheCON Fineract Track
>> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
>> -
>> Meeting notes
>> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>>
>>
>>
>>
>>
>>
Re: Website and Wiki for Fineract updates
Posted by Dick Dickson <d...@gwocu.com>.
Yes I’d also like to participate in this
Sent from my iPhone
> On Jan 31, 2023, at 02:37, Meta Cyrus <in...@gmail.com> wrote:
>
>
> Hi James,
> I am a good UI/UX and web developer who can Design and develop a good user reliable website.
> Where I can start??
> Regards,
> Inzemamul Haq
>
>> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com> wrote:
>> All -
>>
>> We have a lot of good content on the wiki but it's been 3+ years since we did a clean sweep of it. We also have a front landing page at https://fineract.apache.org that could be better at communicating the project and community. Who wants to work on this with me?
>>
>> PROPOSED CHANGES
>> ---
>> On the front "Landing" page:
>> Add blog feed
>> Add feed to dev list
>> Include FAQ
>> Split FineractCN and Fineract
>> As we hope to see a FineractCN release soon, I think we should have a top level split on the main page as well, or perhaps a separate landing page for FineractCN.
>>
>> ---
>> On the wiki - new suggested structure (figure out how to show two levels):
>> FAQ
>> About Fineract
>> New top level functional descriptions
>> About FineractCN
>> TBD
>> Project Management
>> Quarterly reports to the Apache Board (this needs to be more prominent)
>> Community meetings organized by date (most recent at top)
>> Surveys
>> Release processes
>> How do I get involved?
>> Committer guides
>> Links to JIRA and GitHUB
>> Standards
>> Documentation
>> Replace with links to the new dynamically generated documentation.
>> Move Comms related stuff (talks, opinion pieces, etc) ... all go to blog
>>
>>
>> Are there things we should keep or not keep?
>>
>>
>>
>> The current high level structure:
>> FAQ (frequently asked questions)
>> GETTING INVOLVED (commit, contribute)
>> FINERACT
>> FINERACT CN
>> Fineract Data, Credit Scoring, AI
>> Fineract Project Security Report
>> COMMS: Blogs, Talks, and Links
>> ApacheCon EU 2016 Fineract Speaker's Notes
>> How-to articles
>> ApacheCON Fineract Track
>> Meeting notes
>>
>>
>>
>>
Re: Website and Wiki for Fineract updates
Posted by Meta Cyrus <in...@gmail.com>.
Hi James,
I am a good UI/UX and web developer who can Design and develop a good user
reliable website.
Where I can start??
Regards,
Inzemamul Haq
On Tue, 31 Jan, 2023, 7:23 am James Dailey, <ja...@gmail.com> wrote:
> All -
>
> We have a lot of good content on the wiki but it's been 3+ years since we
> did a clean sweep of it. We also have a front landing page at
> https://fineract.apache.org that could be better at communicating the
> project and community. Who wants to work on this with me?
>
> PROPOSED CHANGES
> ---
> On the front "Landing" page:
>
> - Add blog feed
> - Add feed to dev list
> - Include FAQ
> - Split FineractCN and Fineract
>
> As we hope to see a FineractCN release soon, I think we should have a top
> level split on the main page as well, or perhaps a separate landing page
> for FineractCN.
>
> ---
> On the wiki - new suggested structure (figure out how to show two levels):
>
> - FAQ
> - About Fineract
> - New top level functional descriptions
> - About FineractCN
> - TBD
> - Project Management
> - Quarterly reports to the Apache Board (this needs to be more
> prominent)
> - Community meetings organized by date (most recent at top)
> - Surveys
> - Release processes
> - How do I get involved?
> - Committer guides
> - Links to JIRA and GitHUB
> - Standards
> - Documentation
> - Replace with links to the new dynamically generated
> documentation.
> - Move Comms related stuff (talks, opinion pieces, etc) ... all go
> to blog
>
>
>
> Are there things we should keep or not keep?
>
>
>
> The current high level structure:
>
> - FAQ (frequently asked questions)
> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
> -
> GETTING INVOLVED (commit, contribute)
> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
> -
> FINERACT
> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
> -
> FINERACT CN
> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
> -
> Fineract Data, Credit Scoring, AI
> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
> -
> Fineract Project Security Report
> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
> -
> COMMS: Blogs, Talks, and Links
> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
> -
> ApacheCon EU 2016 Fineract Speaker's Notes
> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
> -
> How-to articles
> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
> -
> ApacheCON Fineract Track
> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
> -
> Meeting notes
> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>
>
>
>
>
>
Re: Website and Wiki for Fineract updates
Posted by Bruce <br...@gmail.com>.
Hello James
I am available to work with you on this.
kind regards
Bruce
On Tue, Jan 31, 2023, 4:53 AM James Dailey <ja...@gmail.com> wrote:
> All -
>
> We have a lot of good content on the wiki but it's been 3+ years since we
> did a clean sweep of it. We also have a front landing page at
> https://fineract.apache.org that could be better at communicating the
> project and community. Who wants to work on this with me?
>
> PROPOSED CHANGES
> ---
> On the front "Landing" page:
>
> - Add blog feed
> - Add feed to dev list
> - Include FAQ
> - Split FineractCN and Fineract
>
> As we hope to see a FineractCN release soon, I think we should have a top
> level split on the main page as well, or perhaps a separate landing page
> for FineractCN.
>
> ---
> On the wiki - new suggested structure (figure out how to show two levels):
>
> - FAQ
> - About Fineract
> - New top level functional descriptions
> - About FineractCN
> - TBD
> - Project Management
> - Quarterly reports to the Apache Board (this needs to be more
> prominent)
> - Community meetings organized by date (most recent at top)
> - Surveys
> - Release processes
> - How do I get involved?
> - Committer guides
> - Links to JIRA and GitHUB
> - Standards
> - Documentation
> - Replace with links to the new dynamically generated
> documentation.
> - Move Comms related stuff (talks, opinion pieces, etc) ... all go
> to blog
>
>
>
> Are there things we should keep or not keep?
>
>
>
> The current high level structure:
>
> - FAQ (frequently asked questions)
> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327&src=contextnavpagetreemode>
> -
> GETTING INVOLVED (commit, contribute)
> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318&src=contextnavpagetreemode>
> -
> FINERACT
> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT?src=contextnavpagetreemode>
> -
> FINERACT CN
> <https://cwiki.apache.org/confluence/display/FINERACT/FINERACT+CN?src=contextnavpagetreemode>
> -
> Fineract Data, Credit Scoring, AI
> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Data%2C+Credit+Scoring%2C+AI?src=contextnavpagetreemode>
> -
> Fineract Project Security Report
> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Project+Security+Report?src=contextnavpagetreemode>
> -
> COMMS: Blogs, Talks, and Links
> <https://cwiki.apache.org/confluence/display/FINERACT/COMMS%3A+Blogs%2C+Talks%2C+and+Links?src=contextnavpagetreemode>
> -
> ApacheCon EU 2016 Fineract Speaker's Notes
> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes?src=contextnavpagetreemode>
> -
> How-to articles
> <https://cwiki.apache.org/confluence/display/FINERACT/How-to+articles?src=contextnavpagetreemode>
> -
> ApacheCON Fineract Track
> <https://cwiki.apache.org/confluence/display/FINERACT/ApacheCON+Fineract+Track?src=contextnavpagetreemode>
> -
> Meeting notes
> <https://cwiki.apache.org/confluence/display/FINERACT/Meeting+notes?src=contextnavpagetreemode>
>
>
>
>
>
>