Hi Enock, I've written comments on your proposal below, but in writing them I had the broader realization that I don't think this project is actually particularly feasible for GSoC. I added it to the ideas list on the spur of the moment 2 years ago and never really considered what it would actually entail.
If you're interested, I've since come up with a related but probably much more doable project, which is to convert each type of rule into a written explanation. A lot of the code for that is already written, so the project would mainly be about figuring out how to best explain each part of the rules. You can see what the rules look like so far here: https://github.com/mr-martian/code2text-cg Going roughly in order through your document: I'm puzzled as to why your coding challenge uses a CSV reader. The goal was to do it for our XML morphological dictionaries, such as this one for English: https://github.com/apertium/apertium-eng/blob/main/apertium-eng.eng.dix Community bonding is actually the 3 1/2 weeks that precede the actual coding period. (https://developers.google.com/open-source/gsoc/timeline) I feel like your design and planning stage should ideally be a very rough mockup of what you have in mind in the proposal itself and then refine that plan as you go along (ideally based on feedback from multiple people, though realistically it'll probably just be your assigned mentors). Implementation being only 2 weeks is highly unrealistic. You haven't said much about the rules in your proposal, which makes it sound like you plan to do all of them, which creates problems since we have something like 10-15 different formats, and several of them would be essentially independent from one another in the context of this project. You can drop integration, since there's not much of anything to integrate the tool with. In fact you can probably even drop optimization - this is a debugging tool, so it's not crucial for it to run at maximum speed. Hope all that is helpful, Daniel On Fri, Mar 31, 2023 at 6:46 PM Enock Arthur <enock2004art...@gmail.com> wrote: > > Hi! I am Enock. I am excited to share with you my proposal for the Google > summer of Code(GSoC 2023) program this year. > > You can access my proposal from here - > https://docs.google.com/document/d/1YiZTSs7jHzlZwcSGYXAiXy4PDs4WmhVC3epheBPb09s/edit?usp=sharing. > > My proposal is focused on developing a rule visualization tool that will make > it easier to visualize how different rules will work. > > Your feedback is important to me, and I would be grateful for any suggestions > or comments that you may have. Thank you in advance for your time and > consideration. > > Best regards, > Enock > > _______________________________________________ > Apertium-stuff mailing list > Apertium-stuff@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/apertium-stuff _______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
