Thanks, @parthibd and welcome! We'd love to learn more about you and your projects so please Introduce yourself here! - #1233 by Neko_Acedia when you have a moment.
I responded in Slack but I also want to share a bit about the process here. The best way to start contributing is to pick up a smaller issue so you can learn our processes and we can all start getting to know how we best collaborate.
In the case of submission edits and deletion, there are lots of technical and user experience questions to answer. For example:
- Where should submission editing be accessed by a user?
- Should submission editing always be available or should it be e.g. opt-in by server or project or form?
- Which user roles should get edit privileges? Should new roles be added?
- How should submission history be displayed to the user?
- Given that the ODK XForms spec involves building a linked list of edited submissions with the
deprecatedIdattribute (see docs here), what kind of index should be used to identify a logical submission and all of its history?
Our process for something like this would be to write release criteria and discuss them with the technical advisory board. You can see examples of release criteria in the release posts. This repository has more information about project governance.