Abstract:
OpenLex is a Free Software project for the management of judicial files, mainly oriented to its use in private law firms, but it can also be implemented in public organizations.
The main reason for the development of this tool is the lack of free or open source software that provides a comprehensive solution adaptable to the specific needs of users. And the majority alternatives are oriented to the Anglo-Saxon world, far away from adapting to a Latin American context.
Now, one of the pending problems to be solved, and to which I propose as a participant for this instance of Google Summer of Code, will consist of two axes:
1- A complete migration from Python 2 to Python 3, since, given the deprecated status of the second main version of Python, the long-term scalability of this project is very limited.
2- Migration from Web2Py to Py4Web, also with the purpose of expanding the possibility of a long-term scalability.
Proposal Timeline:
Before June 6 (Before the official coding time):
1- Familiarization process with the OpenLex environment, knowing its functionalities and the logic present in them.
2- Intensive practice with the Python programming language.
3- Comparison of the differences between version 2 and 3 of the Python language.
4- Familiarization with relational databases.
5- Familiarization with Py4Web.
6- Familiarization with the Git and Github tool.
7- Work in close and permanent contact with my mentor and the community, in order to exchange help.
Throughout this stage, I will be intensively learning new development tools, as well as the social skills necessary for proper teamwork. With all that, I aspire to be better defining the potential objectives for this entire process.
June 7 -- August 16 (Coding Period):
1- Establishment of fixed and routine times for myself as well as for my team and my mentor. This will allow for better time efficiency.
2- Survey of all Python code files that exist within the project. Based on this survey, plan the code migration stages.
3- Once the language differences between its two versions have been understood, migrate based on the order established in the previous step, and test the changes.
4-
- On July 12 we will evaluate ourselves within the team, we will review everything we have achieved, and the expectations for the end. From this stage on, we will be able to coordinate with greater confidence and fluency.