GSoC project

[Ralf Habacker]

Am 08.03.20 um 16:43 schrieb aryan jangid:
> Hi,
>
Hi Shubham,

thanks for your interest.

> Ralf, I have read about the ktoblzcheck project and successfully build
> the project from source. I have also tested its command line utility
> to see how it actually works. But I have a few questions.
>
> 1. Inside the ktoblzcheck source tree, under bankdata directory, I see
> multiple bankdata and blzcheck files. Why does bankdata.py generates
> multiple output

ktoblzcheck supports multiple bank data files because bank data can have
a limited life time and ktoblzcheck supports reading multiple bank data
files.

When migrating to a sqlite database, this support should also be
migrated by adding from/to date columns that specify the valid date
range. For example, if a bank is included in the current SQLLite
database and not in the file being imported, it should be marked as
unavailable from the current date. If a bank is not contained in the
sqlite database but in the current blz file, it should be marked as
available from today. If there is no from/to entry in the database for a
specific bank, it is available without restrictions.

> 2. This project is not hosted over github, so how do we submit the
> revisions (Pull Requests)?
> Through mail?

Because for historical reasons the project is hosted at sf.net.

It provides merge requests by forking the ktoblzcheck git repo similar
to github and then you can create a merge request from the personal repo.

It might be possible to migrate the project to the KDE infrastructure
(invent.kde.org, websites) as part of the GSOC project, but it would
have to be considered if this makes sense, as this project is intended
for KDE projects like KMyMoney, Skrooge, but also for non-KDE projects
like GnuCash, aqbanking and others.

One example: I can imagine to make the SQLite database available online
in the future. KDE uses the KDE Store for this purpose, but as far as I
know at the moment it only provides a  KDE based API
(https://api.kde.org/frameworks/knewstuff/html/), which excludes other
projects like aqbanking, because this project uses a standard c++
implementation and only optionally includes Qt.

> 3. Can you point to a small bug fix which is required, so I get a hang
> of its source code?
I will take a look at this and answer in this mailing list
>
> BTW regarding me, I am a KDE developer for past 1.5 years and a
> successful previous year GSoC student for KDE community.
> My phabricator profile: https://phabricator.kde.org/p/shubham/
>
> Regards,
> Shubham

Regards

Ralf

>
> On Fri, Feb 28, 2020 at 12:41 AM Ralf Habacker
> <ralf.habacker at freenet.de <mailto:ralf.habacker at freenet.de>> wrote:
>
>     Am 27.02.20 um 19:54 schrieb aryan jangid:
>>     Thanks Ralf.
>>     I understood most of the things.
>>     1. We need to generate SQLite DB from the bankdata text file.
>>     2. Use that DB in the calling API and command line tools.
>>     3. Write the unit-tests and documentation.
>>
>>     But I have a couple of questions. 
>>     1. These changes would be done in kmymonkey or should we
>>     integrate it inside ktoblzcheck itself?
>     in ktoblzcheck to be usable by any finance application
>>     2. I see SQLite DB already being created
>>     here https://cgit.kde.org/kmymoney.git/tree/kmymoney/plugins/ibanbicdata/germany/germany.py?h=4.8.
>     This should be moved to ktoblzcheck and could be used as base.
>>
>>     I would appreciate your reply.
>>
>     BTW:: Please subscribe to
>     https://mail.kde.org/mailman/listinfo/kde-finance-apps for further
>     communications, which should be public according to GSOC rules.
>
>     Regards
>
>     Ralf
>
>>
>>     On Sun, Feb 23, 2020 at 4:55 PM Ralf Habacker
>>     <ralf.habacker at freenet.de <mailto:ralf.habacker at freenet.de>> wrote:
>>
>>         Am 22.02.20 um 08:57 schrieb aryan jangid:
>>         > Hi Ralf,
>>
>>         Hi Aryan,
>>
>>         > I am interested in doing GSoC this summer. The project
>>         KtoBlzCheck
>>         > interests me. Can you please tell me a bit about it and
>>         some resources?
>>
>>         See http://ktoblzcheck.sourceforge.net/ for informations
>>         about the
>>         project.  The actual gsoc project covers:
>>
>>         1. integrate generating sqlite database from
>>         https://cgit.kde.org/kmymoney.git/tree/kmymoney/plugins/ibanbicdata/germany?h=4.8
>>
>>
>>         2. replace the code, which uses the bank data text file with
>>         code that
>>         uses the new sqlite database
>>
>>         3. write/refactor unit tests for the new code
>>
>>         4. It may required to refactor/simplify the cmake build
>>         system while
>>         working on it
>>
>>         5. add additional countries to the generated sqlite database (see
>>         https://cgit.kde.org/kmymoney.git/tree/kmymoney/plugins/ibanbicdata?h=4.8)
>>
>>         6. extend ktoblzcheck code to use  the additional countries
>>
>>         7. write/refactor unit tests for the new code
>>
>>         8. update ktoblzcheck documentation
>>
>>         You should subscribe
>>         https://mail.kde.org/mailman/listinfo/kde-soc for
>>         getting in contact with the project and study
>>         https://google.github.io/gsocguides/student/.
>>
>>         Regards
>>
>>         Ralf
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-finance-apps/attachments/20200310/560e3eb4/attachment.html>