I understand this completely and in fact this my pivoting point to work and take up on this project, since I am personally attracted to Tryton from a users perspective primarily.
We expect that you search on this forum
I will start exploring and scrutinizing from a fresh-pair of eyes and make sure I am writing down which I feel are important and necessary so that others can follow too, which can then be discussed and added to project deliverable’s.
We also want to change how our module documentation is structured
I’ll look into the discussion to decide docs structure and get hands on with the issue links provided by you.
Please I need help on how I can clone the documentation. I have finished setting up Sphinx on my system.
The example, given on How to Develop page is trying to clone every single thing in the app development, that I’m unable to figure out the documentation directory.
How can I find it or is there a different process?
But it is a little bit tricky to build the full documentation as we use submodules on readthedocs to include the documentation of each tryton component. I tried without success to find a way to mimic on a local environtment the readthedocs build process. Any help on this will be much welcomed!
If you want to focus just on the landing page you should only take care of following the same link structure as is currently done. Then the readthedocs system will build correctly all the components once the work is added to the repository.
Hello, greetings sir.
I just want to show a screenshot of what I’ve done on how the documentation page should look and for you to check if I really understand what the idea case is:
I actually created it for verification so that I don’t mess things up while trying to push it to the main repo. I believe this will be done after a thorough check and corrections have been made.
Meanwhile, I followed the individual links on the documentation to be able to come up with the complete file pages because the clone version gave me only a few files. I now group them in directories according to their related names. Nothing much actually changed except for the front page. I’ll enhance it as we proceed. I only came up with this for you to check if I am actually getting it right.
Here’s the file structure of the documentation (how I grouped):
In Tryton - How to Develop shouldn’t it be cd tryton-env and then cd trytond
Also I am working on docker and watching the video.
I was curious that should I develop a standalone read the docs?
Also how about putting this project on github ?
Moreover as I first step I had assigned a issue to myself and will submit a patch.
What all I need to do to get selected?
Hi.
I am José Segarra, I am a systems engineer at University of Cuenca in Ecuador. Currently, I work in research and software development projects and I have some experience in technical writing.
Formerly, I worked as a developer for a local accounting software company focused in small and medium-sized enterprises. In addition, I have some training in the field of accounting, inventories and administration as part of the curriculum of my career. For instance, I have worked with Odoo (formerly openERP). And I am familiar with the modules, documentation and common operation of business-related software.
I want to apply to this year edition of Google Season of Docs and the Tryton project seems to be a good fit for my profile. I am interested in the idea “3. Adding tool-tips on the application”. Since I know the importance of these elements (tool-tips) for offering a quick and simple guide to users, especially for newcomers. Users usually learn a new software through experimentation, so quick access documentation such as tool-tips, detailed error messages or links to specific documentation sections are extremely useful for them.
Please, let me you are still interested in that idea for Tryton and what should I be doing next in order to get involved in the project.
That is very good news, if you already have knowledge about an ERP system it will be easier for your to document Tryton.
Yes, we are interested on this idea. You can start getting familiar with the project by reading our contribution options. Once you get used to the process then you can pick any module from the list of pending and start working on it. Last and most important, make sure to include your proposal on the GSoD website so we can review it with the other candidates
How should I make a proposal for docker deployment project?
Should I make changes to the sphinx docs locally and put the screenshots over the proposal and write down the steps for newcomers on how to do that?
Okay, so in current sphinx documentation I would be creating a new section for docker deployment which will have the whole process as per the YouTube video instructions.
Sir, soon I will be producing multiple PRs for documentation on the opened issues and I will share my idea and draft proposal by opening up new discussion, is it fine for you?
May I know is the candidate already selected by you or you communicate it later?