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 project logos c/o Albel Derais #1845

Closed
wants to merge 1 commit into from
Closed

Conversation

ReubenBond
Copy link
Member

More of bel's work can be found here: https://www.behance.net/Albel

@jdom
Copy link
Member

jdom commented Jun 16, 2016

This is great, although let's not check in binaries in the master branch. Once in there it will be on the repository history for ever.
We could either have a separate branch or a separate repo for this kind of things

@ReubenBond
Copy link
Member Author

Should I drop all but the svg, then?

@veikkoeeva
Copy link
Contributor

@jdom, @ReubenBond I didn't notice this, but I dropped a few lines in Gitter that we could make use of large file storage and convert existing files (old ones can be purged too from the history, but that's basically a rebase on master and a bit painful).

@sergeybykov
Copy link
Contributor

We have https://github.com/dotnet/orleans/tree/gh-pages/Images and https://github.com/dotnet/orleans/tree/gh-pages/Icons for binary images. I suspect we'll end up with more than one PNG, for different sizes, etc.

So I suggest we put PNGs to gh-pages for now. If we later decide to move away from gh-pages, we'll reconsider.

@jdom
Copy link
Member

jdom commented Jun 16, 2016

@sergeybykov

So I suggest we put PNGs to gh-pages for now. If we later decide to move away from gh-pages, we'll reconsider.

I assume you meant that we put all image assets (PNG, SVG, and all) in that branch, correct? I would not treat this SVG as a special case just because it ended up being small this time around.

@sergeybykov
Copy link
Contributor

Fine with me.

@veikkoeeva
Copy link
Contributor

If I may chime in to clear any potential confusion (for anyone following the chatter here and elsewhere), the SVG file is XML and if not large, there might not be a problem otherwise than making a policy on how to treat asset files, large files and binary files. I think I for one are on somewhat on the same line as @jdom.

As for specifically SVG, a point of note that due to its nature, it's usually not edited by hand, like md files, so this is a case some prefer using a binary diff. With some searching, this issue elsewhere has nice looking discussion about.

@sergeybykov
Copy link
Contributor

sergeybykov commented Jun 17, 2016

@ReubenBond Let's put the assets to the gh-pages branch for now. As we refactor how the docs are built, we'll move things around if necessary.

@ReubenBond
Copy link
Member Author

I've opened #1873 to pull into the gh-pages branch instead.

@ReubenBond ReubenBond closed this Jun 25, 2016
@jdom jdom deleted the ReubenBond-patch-1 branch June 25, 2016 01:47
@github-actions github-actions bot locked and limited conversation to collaborators Dec 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants