Skip to content
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

Add compiler architecture presentation for Feb. 28 meeting #20

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

0xdaryl
Copy link
Contributor

@0xdaryl 0xdaryl commented Mar 1, 2018

Also, impose a directory structure in this repo for such materials.

Signed-off-by: Daryl Maier maier@ca.ibm.com

Also, impose a directory structure in this repo for such materials.

Signed-off-by: Daryl Maier <maier@ca.ibm.com>
@0xdaryl
Copy link
Contributor Author

0xdaryl commented Mar 5, 2018

Ping @mstoodle @charliegracie

@charliegracie
Copy link
Contributor

Hmmm I have been thinking about these types of files and where to best store them. While this is "relatively" small I feel like the repo will grow significantly in size pretty quickly. I do not have a better solution right now but it is something I am thinking about.

@mstoodle
Copy link
Contributor

mstoodle commented Mar 5, 2018

We had some private conversation about these materials before.

The content we're going to put here is created by the Eclipse OMR community, so I think it's very reasonable that this material should share the same licensing as the rest of the project (i.e. we shouldn't dump it in some Box or Youtube or other account where its license is less clear). Does Eclipse have any other large file storage facilities?

They shouldn't pollute the main development repository. The only remaining (existing) choice is this website repository. But I suppose maybe the web site may not always be the right place for them either, so maybe we should ask Eclipse to create another repo for them.

I just worry we'll end up creating a whole whack of content that nobody can find unless they grub through some repo that has "omr" in its name but few other connections.

@charliegracie
Copy link
Contributor

My concern is not that we are putting them in this repo (well sort of), but rather with storing binary files. For meeting minutes I think having them stored in mark-down actually makes a lot of sense. If the file is in mark-down other people can review the minutes, suggest changes during the review and also make changes in future PRs.

@mstoodle
Copy link
Contributor

mstoodle commented Mar 6, 2018

Ah, good point. I agree, it does seem like a more directly editable medium would be better for things like meeting minutes. Also, it doesn't seem like pdf is a format GitHub naturally works well with.

@0xdaryl
Copy link
Contributor Author

0xdaryl commented Mar 9, 2018

Yes, minutes will use markdown. It's the collateral (like presentations, graphics, meeting recordings) that need to be kept somewhere. I suppose until we have a better solution I can upload slide PDFs to SlideShare and recordings of meetings to our YouTube channel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants