> Depending on how much trouble this might cause, you probably shouldn't
> upload it anywhere. Even a "private" repository on GitHub/BitBucket might
> be too risky.
I don't think that he was talking about using BitBucket to host your malware
repo. Probably more along the lines of projects that aid in the downloading of
possibly copyrighted music/videos (for example). It's a legal grey area because
you really don't know if your are on the wrong side of a law until a court
makes a decision since there is no clear-cut way to know.
Some other examples:
1. You want to keep track of your dotfiles that you use at work. In general,
this may be ok to put public, but it may contain work-specific stuff
(hostnames, configurations, etc) that might get you in trouble for publishing
publicly. For example, my work shell config has aliases that include connection
information (sans password) to internal databases.
2. Resumes and/or cover letters. If you update your resume to say that you're
looking for work, or looking for work in another area, this could give info to
your current employer that you don't want to hand out. You might also want to
keep your cover letters in version control if you use something like LaTeX or
have specfic parts that you want to be boilerplate (e.g. description of
yourself and/or your exerience). If you keep this in public, then everyone
knows when/where you are applying for work, which may not be desirable even if
your employer doesn't care.
Some other examples:
1. You want to keep track of your dotfiles that you use at work. In general, this may be ok to put public, but it may contain work-specific stuff (hostnames, configurations, etc) that might get you in trouble for publishing publicly. For example, my work shell config has aliases that include connection information (sans password) to internal databases.
2. Resumes and/or cover letters. If you update your resume to say that you're looking for work, or looking for work in another area, this could give info to your current employer that you don't want to hand out. You might also want to keep your cover letters in version control if you use something like LaTeX or have specfic parts that you want to be boilerplate (e.g. description of yourself and/or your exerience). If you keep this in public, then everyone knows when/where you are applying for work, which may not be desirable even if your employer doesn't care.