31–40 of 74 posts
Earlier quoted context omitted.
can you speak more to how this is built - even if its just at a high level?
Someone came up with a design. Someone else implemented the backend. We iterated on it for a bit and shipped it internally. Then we figured out the CDN situation, setup logging and metrics, and shipped it genpop today.
With Skitch completely screwing their latest release, hosting issue related files (screenshots, doodles...) was painful to say the least. Dropbox did an ok job at it but did not let me embed pictures in the thread (the file URLs change randomly). Pretty awesome that the guys at Github got that covered.
With Skitch completely screwing their latest release, hosting issue related files (screenshots, doodles...) was painful to say the least. Dropbox did an ok job at it but did not let me embed pictures in the thread (the file URLs change randomly). Pretty awesome that the guys at Github got that covered.
Obviously a non-issue now, but what about something like http://imgur.com/ ?
Hosted all of my images for our GitHub Game Off entry[1] README file there. Always a solid solution if you want any sort of image hosting.
This goes towards the space allotment given to each user right? If so, I'm going to limit the number of attachments I use. No memes for you.
I would love to hear why the github team waited so long to bring this feature into existence? I am sure there is a good reason (or maybe not) but it would be awesome if a member of the team would stop by and post the details.
We don't have roadmaps or a prioritized backlog, so we weren't exactly "waiting" to implement this. Someone got fed up with the image workflow, figured out a solution, grabbed some other people to help, and shipped it.
I'll take the downvotes. it was worth it
Earlier quoted context omitted.
We don't have roadmaps or a prioritized backlog, so we weren't exactly "waiting" to implement this. Someone got fed up with the image workflow, figured out a solution, grabbed some other people to help, and shipped it.
Now I know github doesn't have a typical roadmap or backlog but I guess what I was looking for was how someone decides what feature they are "fed up" with not having.
I imagine the conversation internally went something like, "Man, attaching an image to an issue is really annoying. Let's make it not suck." An issue and pull request followed, internally shipped it to test it, and today rolled it out to you all.
That's literally how 99.99% of features happen on GitHub. :)
This goes towards the space allotment given to each user right? If so, I'm going to limit the number of attachments I use. No memes for you.
Meme freely!
Can anyone advise from experience how long this may take to filter through to Github:Enterprise?
In a perfect world: the next release (usually a few months apart). But software has a way of coming up with unexpected problems, so let's call that a goal :) We've spent a lot of time this year ensuring Enterprise has feature parity to every new feature we ship on dotcom, and this was no exception.
The best answer is: when it's ready, but not before.
Earlier quoted context omitted.
Someone came up with a design. Someone else implemented the backend. We iterated on it for a bit and shipped it internally. Then we figured out the CDN situation, setup logging and metrics, and shipped it genpop today.
Can you tell me a bit about the CDN situation, especially what specific issue did you run into?