Closed mmcky closed 4 years ago
@sayaikegawa please let me know if you are available to help with this task. Thanks.
Hi @mmcky , I'm happy to do this.
thanksk @sayaikegawa
Hi @mmcky , When I make PR, do you think that it is good idea to remove the names of all lectures's rst file for 1 PR? or removing a name of each rst file for each PR?
hi @sayaikegawa I think in this case it would be ok to do a single PR that removes them all across the files. I think it is unlikely to cause merge conflicts with other work as they are usually on a single line. If a conflict arises I can help resolve it.
Thank you @mmcky , then I will make a single PR.
Hi @jstac and @mmcky , would it be ok to remove author of lectures and codes like below as well? And should I wait making PR until the split finishes?
would it be ok to remove author of lectures and codes like below as well?
hi @sayaikegawa good question. I think removal of all names (code and rst) is the way to go. Good find.
And should I wait making PR until the split finishes?
how far along are you? Feel free to keep going on this task as I can merge in the changes to the split repositories later on.
Thank you @mmcky , I think I can finish this by tomorrow evening at the latest.
Thanks @sayaikegawa. Names are to be removed everywhere, as @mmcky says.
By the way, could you please keep a list of the names that you remove? Then we can try to make sure that these people are recognized for their contribution in some way.
Thank you @jstac . I'll make the list.
As part of the transfer to new license we need to check all
rst
files and removeco-author
statements. Presentations are varied so will require going through the first ~10% of each lecturerst
file looking for statements like:pandas_panel.rst
containsMost of this lecture was created by Natasha Watkins
This will resolve item 2 in #946