Private profiles are now generally available on GitHub
github.blog
github.blog
https://news.ycombinator.com/item?id=31115642 ("GitHub: Private Profiles beta", April 2022, 125 comments)
> By clicking "Add Successor" below, I acknowledge that I am the owner of the @ttmc account, and am authorizing GitHub to transfer content within that account to my GitHub Successor, designated below, in the event of my death. I understand that..."
I understand the reasoning for a clear path of succession of the latter. I do not believe that the former should carry on after our deaths. Our personas should die with us.
Haven't tried it yet, though.
But you will need to self host it, the included dependency checks in GitLab are paid.
However renovate has a free hosted version for GitHub.
https://github.com/renovatebot/renovate/blob/main/license
> Renovate versions 12.0.0 (released 2018-04-09) and onwards are released under the GNU Affero General Public License.
The dependabot-gitlab project mentioned above is MIT, for comparison
Renovate is indeed AGPL, but if you're just running it as a CLI, do you think there's anything to "watch out for"? It does not make any project you run it against AGPL, that's for sure.
Also you should be aware that dependabot-core, which dependabot-gitlab wraps, is not technically Open Source at all: https://github.com/dependabot/dependabot-core/blob/main/LICE... Wrapping a non-open source project in another project which claims to be MIT licensed does not change the underlying license. I'm not a lawyer but question the validity of them doing this without larger disclaimers.
However, I think that it's likely not something to "watch out for" either. Likely both licensing approaches were intended as a way to forbid or discourage competing services and each project welcomes people self-hosting.
In short I don't think that the license of Renovate or Dependabot is likely material for anyone planning to run it for themselves.
As for the "watch out," I apologize if that came across as scolding or whatever, but in my company, and likely quite a few others, AGPL software is forbidden. Thus, maybe I have said "be aware" instead of "watch out," so I'll try to choose more neutral advisory language next time
Your "but it's just a CLI" is the nuance of the AGPL that I don't want to pay lawyers to disambiguate since this very thread was about running a GitLab bot, over the network, or in CI which is hosted on runners that connect over the network
Maybe I just need to stay out of these threads and let people do their own license homework, but I certainly do get value when someone else makes me aware so I can dismiss the tooling. No good deed goes unpunished, I guess
If you're referring to Renovate, there's no such paid option.
If you're referring to GitLab paid features, I'm not sure how that's any different between tools.
Or does copilot not work like other ML projects and actually copies sections of code?
https://github.com/settings/profile
``` Contributions & Activity
Make profile private and hide activity
Enabling this will hide your contributions and activity from your GitHub profile and from social features like followers, stars, feeds, leaderboards and releases.
Include private contributions on my profile
Your contribution graph, achievements, and activity overview will show your private contributions without revealing any repository or organization information. Read more. ```
From https://github.blog/changelog/2022-04-21-private-profiles/)
> Private profiles are in public beta
Good thing cloudflare still has free Cloudflare pages support for private GitHub pages.
The only related thing I found was that free accounts are limited to one user that can trigger deploys in private repos, while anyone can trigger deploys in public repos (assuming I understood the announcement correctly).
They recently changed the policy for Organization-owned repos. The continuous deployment for organization-owned private repos is no longer allowed in the free plan.
But personal account's public and private repos are still part of the free plan.
Unless you care about centralization, then you might still use GitHub Pages or Vercel.
That all having been said, I do not disagree that in most cases, the "social coding" thing is a misnomer. GitHub's main contribution, in my opinion, was actually just putting source control and source code at the forefront of the project forge concept. Sourceforge felt like a nice website for projects to organize, but code storage felt at best like an afterthought. GitHub's forks and pull requests are what really make it shine, and the rest is mostly either bonus or noise.
Not like, 3k vs 8k, but like 200 vs 0... help me understand if this is this a hobby project someone wrote and abandoned in a few days.
Fair point.
Your comment contains no substance that couldn’t have been conveyed by saying “I hate it”. If you don’t like it, don’t use it. That’s what I do. Is there an actual reason that the mere existence of social networking features is harmful to those of us who choose not to bother with them?
So many people with so much talent, wasting it on some really meaningless stuff.
For example, thanks to the norms fostered on GitHub, you can no longer expect the average programmer to file good bug reports or to just interact in an appropriate way with the bugtracker.
We can't really talk about "wikis", either, without confusion about what a wiki even is—again, thanks to GitHub.
Was it done properly? I suspect that average programmer just didn't report anything, instead of create new GitHub issue. It's annoying to sign up each ML or bugzilla.
I don't know, as the "social coding" platform never claimed to be anything different.