-
Notifications
You must be signed in to change notification settings - Fork 14
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
Comments
HOLD ON. The repository is way bigger, actually. Half a gig, that's huge. O__o |
I think, it’s because there are a lot of pictures in it.
|
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). |
I think that it's a great idea to have a shared image directory. Jen Diamond On Tue, Nov 4, 2014 at 7:02 AM, alicetragedy notifications@github.com
|
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 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 Re: presentations: Galway and Ticino, for example, have separate folders just for slides. The rest of the pdfs in the What's also really big (200MB) is the pack file ( |
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. |
Maybe we can make a materials repo?
|
<3 hahah yess! didn't think about that. Linda www.lindaliukas.fi On Wed, Nov 5, 2014 at 5:41 PM, Ute Mayer notifications@github.com wrote:
|
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? |
yes :) nerdbabe Personal Contact Information
|
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? |
Go ahead! We have 10 private repos of which only one are in use :) Linda www.lindaliukas.fi On Thu, Nov 6, 2014 at 7:10 PM, Kay notifications@github.com wrote:
|
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. (: |
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!]
The text was updated successfully, but these errors were encountered: