Greetings,
Again requesting you all to please review my proposal so that I can make
any final changes if needed.
On Wed, Mar 25, 2020 at 3:07 PM Harshit Jain <harshitjain1371999@gmail.com>
wrote:
Greetings!
I am Harshit Jain, a senior undergraduate student pursuing Electrical
Engineering at the Indian Institute of Technology Delhi. Being passionate
about software development, I now want to start contributing to open-source
and GSoC is indeed a great opportunity to embark upon this journey.
Upon going through the list of projects, I found the project regarding
implementing a Styles Inspector really interesting and would like to work
on this as a part of the GSoC project. I have already drafted a proposal on
the same and shared through the official GSoC portal. I request you all to
review my proposal and give any suggestions which may be required in my
proposal.
Link: https://1drv.ms/w/s!At4gk155x7NehSaCXzcJ67J13orQ?e=Kb24OW
As far as my contributions are concerned, I have just started contributing
easy patches to the libreoffice code and would like to become more active
and contribute more in the days to come. The details of the patch submitted
are as follows:
Status: Merged
Gerrit link: https://gerrit.libreoffice.org/c/core/+/90901
Bug link: https://bugs.documentfoundation.org/show_bug.cgi?id=124176
Again requesting you all to please review my proposal and suggest any
changes if needed.
Thanks,
Harshit Jain
Regards,
Harshit Jain
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.