Siddhartha Gairola writes: > I would like to work on Postorius issue 127 - > https://gitlab.com/mailman/postorius/issues/127. > > I would be grateful if someone could tell me how to start solving this.
You start by starting. ;-) "Claiming" the issue and posting here was a good start. :-) First, check with Nitish Kumar Dwivedi (https://gitlab.com/nitishkd) that s/he is not currently working on the issue to ensure no conflict over your contribution.[1] You don't need to wait for an answer to start working; it won't be useless duplication for a couple more steps. Now tell me[2] what you think you should do next. (Coding != developing. Developers are engineers who solve problems. We will help you when you get stuck, but you have to solve the problem. Don't worry, we'll wait. :-) Steve Footnotes: [1] No, 7 months silence != issue abandoned. Conflicts over credit are rare in Mailman; we are a pretty flexible, friendly and conscientious group in that respect. On the other hand, we do care about keeping each other in the loop. And it's possible that Nitish has a nearly complete solution in a private branch. If so, your work would likely be redundant -- if Nitish is in no hurry to work on it, try negotiating for joint credit: get that branch MR'ed, and then do the remaining work to integrate. [2] On the issue or on this list -- I will IGNORE personal mail if it doesn't have a reference to a public channel!! so check your headers before sending mail, this list does NOT munge Reply-To. I've assigned the issue to myself so I will get notifications. _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9