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

Repository "bloat" #567

Closed
keikoro opened this issue Nov 4, 2014 · 13 comments
Closed

Repository "bloat" #567

keikoro opened this issue Nov 4, 2014 · 13 comments

Comments

@keikoro
Copy link
Contributor

keikoro commented Nov 4, 2014

Cloning the repository for the Rails Girls website on a new machine, I noticed it's become awfully large. It's at almost 200MB [edit: 500MB] with some chapters using a lot of space for unnecessarily huge image files (many instances of the full 2MB GitHub Octocat png?) or presentations. (Looking at you, RG Galway! Imo, 16+MB is really a lot for simple event listing.)

I know it's not a problem right now where the GH repo is concerned, but wouldn't it be preferable if the repository weren't such a monster?

Any ideas on how to make organisers aware or remind them that a small png will do the job just as nicely as the 2MB version? Any ideas on how to deal with avoiding multiples of files that are used by a lot of chapters? Should there be something like a shared Speakerdeck profile for slides so they don't need to be made available as (huge) direct downloads? [edit: forgot about the presentations repo!]

@keikoro
Copy link
Contributor Author

keikoro commented Nov 4, 2014

HOLD ON. The repository is way bigger, actually. Half a gig, that's huge. O__o

@nanoparsec
Copy link
Member

I think, it’s because there are a lot of pictures in it.

Am 04.11.2014 um 15:29 schrieb Kay notifications@github.com:

HOLD ON. The repository is way bigger, actually. Half a gig, that's huge. O__o


Reply to this email directly or view it on GitHub #567 (comment).

@alicetragedy
Copy link
Member

I think @nerdbabe is right.. and also, there are probably some logos for sponsors that are used by several chapters. Maybe we could somehow mention that in the organisers' guide, so images/logos can be reused somehow.. I have never added a new chapter so I am not sure what would be the best way to update it all (I'm thinking broken links if we do some cleanup and move shared logos into a separate folder, which might be a little bit of a tragedy).
As for the shared Speakerdeck profile.. hm when I cleaned up the presentations repo (some months ago), I noticed that most presentations were actually linking to speakerdeck slides on the speaker's own profile. Or are you talking about other slides @kerstin?

@jendiamond
Copy link
Member

I think that it's a great idea to have a shared image directory.

Jen Diamond
323-363-0002
thejendiamond@gmail.com
@jendiamond
http://goog_1577702335
https://github.com/jendiamond

On Tue, Nov 4, 2014 at 7:02 AM, alicetragedy notifications@github.com
wrote:

I think @nerdbabe https://github.com/nerdbabe is right.. and also,
there are probably some logos for sponsors that are used by several
chapters. Maybe we could somehow mention that in the organisers' guide, so
images/logos can be reused somehow.. I have never added a new chapter so I
am not sure what would be the best way to update it all (I'm thinking
broken links if we do some cleanup and move shared logos into a separate
folder, which might be a little bit of a tragedy).
As for the shared Speakerdeck profile.. hm when I cleaned up the
presentations repo (some months ago), I noticed that most presentations
were actually linking to speakerdeck slides on the speaker's own profile.
Or are you talking about other slides @kerstin
https://github.com/kerstin?


Reply to this email directly or view it on GitHub
#567 (comment)
.

@keikoro
Copy link
Contributor Author

keikoro commented Nov 4, 2014

It's different files, but yes, mostly image files and also (some) presentations.

The posters (which I hadn't realised where in the repo) eat up a lot of space, which is to be expected as they are for print, alright. But there are also a lot of chapter-branded materials in the assets folder which cannot (easily) be reused by other chapters (e.g. Cologne has its own folder full of materials). Though maybe this was/is intended? Can or should everyone use the repository as storage space for their own materials? I don't know, it just never would have occured to me to upload .psd and similar files that are huge (for print) and for local use only to the shared repo. @lindaliukas ?

I also don't have a good solution for the duplicate sponsor logos problem. /: When I created our new Vienna event, it was impossible to find our old logos without looking them up in the source code of the old page (the images folder is big and super messy as there's no naming scheme), so I did what some other chapters had done before: I created a separate folder for Vienna images so we always know where our images are when we need them again. The only "system" I can think of would consist of a page that alphabetically lists all sponsors (sponsor names + logos + file names that could be easily copy/pasted), which everyone would have to have a look at before adding new pictures. Wouldn't solve the problem for all other image files though.

Re: presentations: Galway and Ticino, for example, have separate folders just for slides. The rest of the pdfs in the files folder seem to be scans of Finnish newspaper articles (I hadn't had a look at them before).

What's also really big (200MB) is the pack file (.git/objects/pack), but I don't know anything about reducing its size - save for what I just googled/Stackoverflowed... :P

@lindaliukas
Copy link
Member

Ahh - yep this might be my fault originally, I used the repository pretty liberally in the early days to store all sorts of things. I don't think we have the resources to set up an S3 or other entity, unless someone knows a good way to distribute the credentials (billing I can figure out!). Dropbox might be an interim solution, but most likely everything becomes broken after awhile.

With regards to the Finnish materials, let me just remove the stuff from the /press page :D It belongs to another era and doesn't really represent Rails Girls today.

@nanoparsec
Copy link
Member

Maybe we can make a materials repo?

Am 05.11.2014 um 14:41 schrieb Linda notifications@github.com:

Ahh - yep this might be my fault originally, I used the repository pretty liberally in the early days to store all sorts of things. I don't think we have the resources to set up an S3 or other entity, unless someone knows a good way to distribute the credentials (billing I can figure out!). Dropbox might be an interim solution, but most likely everything becomes broken after awhile.

With regards to the Finnish materials, let me just remove the stuff from the /press page :D It belongs to another era and doesn't really represent Rails Girls today.


Reply to this email directly or view it on GitHub #567 (comment).

@lindaliukas
Copy link
Member

<3 hahah yess! didn't think about that.

Linda

www.lindaliukas.fi
Tel: +358 41 51 434 05
Skype: linda.liukas
Twitter: lindaliukas

On Wed, Nov 5, 2014 at 5:41 PM, Ute Mayer notifications@github.com wrote:

Maybe we can make a materials repo?

Am 05.11.2014 um 14:41 schrieb Linda notifications@github.com:

Ahh - yep this might be my fault originally, I used the repository
pretty liberally in the early days to store all sorts of things. I don't
think we have the resources to set up an S3 or other entity, unless someone
knows a good way to distribute the credentials (billing I can figure out!).
Dropbox might be an interim solution, but most likely everything becomes
broken after awhile.

With regards to the Finnish materials, let me just remove the stuff from
the /press page :D It belongs to another era and doesn't really represent
Rails Girls today.


Reply to this email directly or view it on GitHub <
https://github.com/railsgirls/railsgirls/issues/567#issuecomment-61807993>.


Reply to this email directly or view it on GitHub
#567 (comment)
.

@keikoro
Copy link
Contributor Author

keikoro commented Nov 6, 2014

Ah, you mean for all things that don't go on the site directly or are just meant to be downloaded by the organisers (like poster templates etc.), @nerdbabe?

@nanoparsec
Copy link
Member

yes :)
one repo for the website and one for materials.


nerdbabe

Personal Contact Information
Email: mail@nerdbabe.de mailto:mail@nerdbabe.de
Website: nerdbabe.de http://nerdbabe.de/
Twitter: nerdbabe https://mail.google.com/mail/ca/u/0/https//:twitter.com/nerdbabe
Github: NerdBabe https://github.com/NerdBabe

Am 06.11.2014 um 02:06 schrieb Kay notifications@github.com:

Ah, you mean for all things that don't go on the site directly or are just meant to be downloaded by the organisers (like poster templates etc.), @nerdbabe https://github.com/nerdbabe?


Reply to this email directly or view it on GitHub #567 (comment).

@keikoro
Copy link
Contributor Author

keikoro commented Nov 6, 2014

Sounds like a good idea!

I guess its realisation is also dependent on how many leftover private repos Rails Girls has. What do you think, @lindaliukas?

@lindaliukas
Copy link
Member

Go ahead! We have 10 private repos of which only one are in use :)

Linda

www.lindaliukas.fi
Tel: +358 41 51 434 05
Skype: linda.liukas
Twitter: lindaliukas

On Thu, Nov 6, 2014 at 7:10 PM, Kay notifications@github.com wrote:

Sounds like a good idea!

I guess its realisation is also dependent on how many leftover private
repos Rails Girls has. What do you think, @lindaliukas
https://github.com/lindaliukas?


Reply to this email directly or view it on GitHub
#567 (comment)
.

@keikoro
Copy link
Contributor Author

keikoro commented Nov 6, 2014

Neat!

Okay then! While I won't have time to work on this properly until after 23 November - because of our own upcoming event next week and several exams at uni - I'll go ahead and create a repository.

I'll also write a quick mail to the mailing list so everyone is in the loop. Maybe others are able to give a hand too. (:

@keikoro keikoro closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
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

No branches or pull requests

5 participants