-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding subchapters in the leadership #1553
Conversation
❌ Deploy Preview for the-turing-way failed.
|
Today I fixed tiny problems, so the chapter in this branch renders. The Figure in leadership.md is not rendering correctly and I still need to figure out why. I need to continue fine-tuning leadership-building.md next. |
Next time I have a chance at working on this I need to:
|
What about having a section with "other leadership models" with the long description of "prevalent, exclusive practices in open source /data science communities". In addition to BDFL it could include self-appointed committees with fixed membership clinging to power, basically acting as BDFL. And maybe also the "lab run" open source/data science project might also fit, e.g. when one has to be affiliated with an institute to be part of the project (the approach is all legit of course, but not as a way to lead an inclusive project). |
That would be great, Brigitta! |
For review, would you prefer an inline review on the PR or comments on the draft hackmd? I can start adding a skeleton for the section and drafting it out. |
Great! |
@pherterich I have updated this branch here. Let me know if you face any error editing files in this chapter. |
I have created a placeholder for the notes @aleesteele took at yesterday's discussion led by Patricia, and maybe a place to also add notes from March's Fireside discussion: Emergent Roles in Research Infrastructure & Technology | Noor, Esther, Borhane, Beth, Arielle | Video | Etherpad: https://pad.sfconservancy.org/p/ttw-fireside-chat-mar2022 |
Some thoughts/doubts/input suggestions about the 'What to avoid in leadership' subchapter:
|
Plan: Free |
Images automagically crushed by Crush.pics ✨
Plan: Free |
Images automagically crushed by Crush.pics ✨
Plan: Free |
Images automagically crushed by Crush.pics ✨
Plan: Free |
Quite a merge conflict 😄. Is this because of images being compressed? @bsipocz I've never been great at this kind of merge, where you are asked about 'LOCAL' and 'REMOTE'. I suppose the answer here is to always choose 'REMOTE'? When you do that, there are still problems with paths to images which don't exist and some |
Images automagically crushed by Crush.pics ✨
Plan: Free |
Images automagically crushed by Crush.pics ✨
Plan: Free |
Hey @JimMadge, sorry for jumping in like this! I was just having a chat with Mavika in the chat, and it looks like fixing the conflicts with the images might require quite a bit of work. However, Mavika mentioned (correct me if I'm wrong, Mavika) that she doesn't mind losing the commit history by simply copying and pasting the files (including the images) for the leadership chapter, images, references, and table of contents. As far as I understand, the changes in the workshops folder are unrelated to this PR. So, what do you think? Would you recommend creating a new branch and new PR (with copy/pasting) the files? Or do you think it would be easier to just tackle the image conflicts? Feel free to tackle it either ways (Malvika correct me I am wrong)! |
@BatoolMM yes, sometimes getting your workspace correct, stage, commit and let git worry about the diff is an easier way to get the same product. I think that is legitimate. It is a shame to loose the individual commits and authors. Luckily we have other ways to recognise the contributors 👍. We shouldn't let some git workflow orthodoxy prevent good contributions to the book. |
Images automagically crushed by Crush.pics ✨
Plan: Free |
I am giving up. will create a new branch with the files. Thank you all! |
Ok, created another one manually on GitHub: #3136 |
My week was way busier than I was expecting it, and now that the follow-up PR is merged, is this still relevant? |
No worries Brigitta. This PR is not relevant anymore. I will close this. |
Summary
Fixes #1224
List of changes proposed in this PR (pull-request)
What should a reviewer concentrate their feedback on?
Acknowledging contributors