Hi Vivek On 2016-02-25 16:25, Vivek Pal <vivekpal dtu gmail com> wrote:
… I am in junior year of my graduation and so I'll be graduating next year which is why I think sooner I get started into real-world development as soon as possible. Contributing and getting involved in open source communities is perfect place for students like me to get their hands dirty, learn new skills, improve existing skills and meet awesome people of different communities and GSoC is a great place to kick start this journey and continue beyond it ends. I don't want to limit my learning experience with GSoC and want to keep contributing after it ends. I've been an avid user of Gnome Operating system and honestly, I love it more than every desktop environment. I would love to contribute in its development! Please suggest me some tasks to get started.
Something that would be an interesting fix (and tour of the codebase) is a feature request to check the length of the filename when renaming files:
https://bugzilla.gnome.org/show_bug.cgi?id=742050File renaming is a big part of what EasyTAG does, and getting this right would be a big help to users. There was some code to check the length of a filename (ET_File_Name_Check_Length, which was removed as it was unused), and there are some calls to that which are commented out.
The interesting thing about solving this bug is to figure out the best approach to solve the problem. It is possible to query the maximum path length with a POSIX API (pathconf) and also to use MAX_PATH on Windows (https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath). You would have to think about whether to query the maximum filename length in advance, or whether to check for the ENAMETOOLONG errno and handle that appropriately. Luckily, there are only very few places where files are renamed (or generated), so the amount of code changed should be small.
Good luck! -- http://amigadave.com/
Attachment:
signature.asc
Description: Digital signature