The detailed plan can be kept in the original project idea task itself which can be modified as per discussions with mentors. Move over the contents of the proposal task to the project idea task as well to keep everything in the same place.

I don't quite understand. Shouldn't it be the other way round, if required? If we want to keep everything in the same place and we want this place to be the original project idea task, why create subtasks under the proposal task? Also, @01tonythomas proposed in T130585#2238405 that we reduce the notification count by sticking to the proposal, then why lead to these extra notifs by constantly modifying the project idea along with the proposal task, too?

In T133647#2241381, @darthbhyrava wrote:

The detailed plan can be kept in the original project idea task itself which can be modified as per discussions with mentors. Move over the contents of the proposal task to the project idea task as well to keep everything in the same place.

I don't quite understand. Shouldn't it be the other way round, if required? If we want to keep everything in the same place and we want this place to be the original project idea task, why create subtasks under the proposal task?

The proposal task is your root to track all tasks done as part of GSoC. It is quite possible that the work done as part of GSoC might not be sufficient to resolve the project idea, and some work might be needed to be done outside the scope of GSoC. So this is a measure to keep the scope of GSoC separate from the project idea itself.

Also, @01tonythomas proposed in T130585#2238405 that we reduce the notification count by sticking to the proposal, then why lead to these extra notifs by constantly modifying the project idea along with the proposal task, too?

Modifying the project idea entails having the basic objectives/workflow there to keep it updated for those not associated with GSoC. I think people can bear with some extra notifications at the cost of updated information on the task.

@Sumit - that answers up my doubts. Thanks for clearing it up! :D

@Sumit @01tonythomas, I've removed myself from a bunch of tickets but feel free to add me back if need be. Trying to cut down on notification noise.

Now we have 8/8 tasks here! Yay!

@Sumit Hi, I have some doubts on the bonding process:

1. What's the difference between the "detailed plan" mentioned above and the detailed plan stated in my proposal? Shall I create projects and tasks (or sub-tasks) in Phabricator for the GSoC project once I confirm the plan with my mentor?

2. How should I publish a bonding period report? May I create a task for it, or something else?

@Lethexie for the report, the method of reporting and so on is mentioned at Life_of_a_successful_project in the Community bonding period > Reporting section.

@AbdealiJK Thank you , And how about the second Phabricator project created? Should I create new task in Phabricator for the GSoC project?

In T133647#2255827, @Lethexie wrote:

@AbdealiJK Thank you , And how about the second Phabricator project created? Should I create new task in Phabricator for the GSoC project?

We recommend projects go into separate phab projects, but this one is a special case :D (kinda fitting in the parent task) . Please start a Conpherence with your mentors asking whether your task can be merged with MediaWiki-Codesniffer , or should go as a separate one. You can ask that in a phabricator task too, adding your mentors as subscribers.