Open orbeckst opened 12 months ago
Quick note for working on this repository: If you are just touching files in the blender
directory or do minor fixes in the READMEs then you don't need to wait for a review. Just make your changes. If you're modifying someone else's stuff, do a PR + wait for a review (just ping someone like @fiona-naughton (who is in charge of hackathon things) @jennaswa (for overall organizational things) @orbeckst (if you just need someone quickly) or ask on discord).
In your outline I saw that you're also preparing a video for participants to watch in advance to get set up. I think that's a great idea. Can you raise a separate issue for that?
We would just put videos up on YouTube in the (very tiny) MDAnalysis channel.
@orbeckst could I get write access to put some info into the blender README?
@BradyAJohnston I added you to the repo with write access.
@yuxuanzhuang we are planning to send out instructions to attendees on Monday - are there any further changes you wish to make ahead of this?
just waiting for the YouTube link and I think it's good to go!
I've added some more notes on explaining data flow, and will add some more in the next day or two as well, will hopefully help people get started interfacing with Blender.
@BradyAJohnston - for the sake of ensuring we don't have things go out of synch across multiple editors, could you please commit via PR rather than directly to the main branch?
@IAlibay just fyi when we started work on the repo I gave the guideline above https://github.com/MDAnalysis/UGM2023/issues/12#issuecomment-1714766299 to make sure things were moving along quickly.
@orbeckst that's fair, sorry I didn't see that. However, given how close we are to the UGM, could we reconsider this policy?
Sure, just communicate to everyone who’s working on the repo.Am 9/24/23 um 09:08 schrieb Irfan Alibay @.***>: @orbeckst that's fair, sorry I didn't see that. However, given how close we are to the UGM, could we reconsider this policy?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
I've added branch protection so folks shouldn't be able to commit directly unless they force it.
On Sun, Sep 24, 2023, 18:14 Oliver Beckstein @.***> wrote:
Sure, just communicate to everyone who’s working on the repo.Am 9/24/23 um 09:08 schrieb Irfan Alibay @.***>: @orbeckst that's fair, sorry I didn't see that. However, given how close we are to the UGM, could we reconsider this policy?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/MDAnalysis/UGM2023/issues/12#issuecomment-1732623071, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC7CAXNFP5UFV6MFPNWK4RDX4BS7FANCNFSM6AAAAAA4UBYK64 . You are receiving this because you were mentioned.Message ID: @.***>
Yep apologies @IAlibay was following earlier instructions, will ensure it goes via PR.
@yuxuanzhuang started planning the Molecular Nodes/MDAnalysis Blender hackathon session in discord: #project-proposals: MDA/MN Collaboration
Add necessary materials to the hackathon/blender directory. You can also rename it from blender to MolecularNodes but then you need to change links in README.md file(s).