Recommend Establishing Dedicated Working Group for External Contributions

If something like gtihub.freebsd.org that its accounts are managed by FreeBSD project and/or FreeBSD foundation, without sharing my account info with GitHub.com, is possible, I'll be happy to register and keep on contributing.

I thought FreeBSD's github was independent of "Microsoft's" GitHub.com?
 
And M$ can stop providing GitHub service whenever they consider it not enough worth providing WRT their benefits. This is (not limited with by M$) the largest concern using third party's free services as the infrastructure.
I saw too many free web servers for personal users dissappeared (not used any myself, though). And discontinued services by Google etc.

But can it be that hard to get an independent github-server?
Not sure about its licenses (not as the service, but the code itself).
And not sure how resource-intensive it is.
 
But can it be that hard to get an independent github-server?
I'd say probably not that hard. Lots of businesses (and individuals) self host a server (gitlab community edition or git).

to me, "github" is just a "freely available public thing that someone else is paying for". It's nice because it makes things visible to everyone, lets individuals make things visible to everyone.

I'm with T-Aoki on this: right now MS is paying for everyone to use github.com for free, just like Google is paying for everyone to use gmail.com for free. At some point they may simply say "No more" and then what? github.com needs physical assets like servers and network, that costs real money. I look at how many news things have put stuff behind paywalls: Do they really make money off it or just lose readers?

In theory, the headline from the OP seems reasonable because every Open Source project runs into the "how do we incorporate feedback from the users" (patches to base, ports, etc) at some point. To me it often comes down to manpower and time. I can clone a ports tree, patch something, generate a pull request, write a bug thing with code diff attached, but I cannot actually make the port maintainer look at all that and do something even to tell me "go away you suck". Toss in "I made all that available yesterday and it's been 20 hrs why has nothing been done" and I wind up at "Now what". In an opensource project I can't force anyone else to do anything.

Having a specific working group trying to address this issue is not a bad thing, but will it take away from other things?
 
Applying "sayings" to selfish interests is not spreading wisdom.
Obviously you've never read Eric Raymond's Unix Koans.
Maybe that is a common saying from the low grounds of fast food restaurants, while in the kitchens of haute cuisine a brigade of skilled cooks is doing an outstanding work.
If that's an insult based on my background, you aren't aware of my corporate place back then.

In any case, the saying outlines a potential problem. Your opinion that throwing people at this situation might only muddy the waters rather than solve anything. Look at all the people working on Linux and look at all the issues that occur with every new release or upgrade or new feature.
 
These are examples how it goes on Bugzilla and Phablicator.
But Bugzilla is still useful for reporters that cannot provide codes / patches to review.
Judging from past job experience, this is rather tame and ordered :D
 
Let's not derail the OP's discussion with the "Microsoft is evil" topic. Where the git is hosted is a minor issue.

I agree with Sir Dice that this forum is not a sensible place for a discussion of the development process. There are a few developers here, but most people here are users, with no influence on the process. It's not clear to me what the correct venue for addressing their concern would be, given that FreeBSD development doesn't have a clear management structure, or a BDFL.
 
Let's not derail the OP's discussion with the "Microsoft is evil" topic. Where the git is hosted is a minor issue.

I agree with Sir Dice that this forum is not a sensible place for a discussion of the development process. There are a few developers here, but most people here are users, with no influence on the process. It's not clear to me what the correct venue for addressing their concern would be, given that FreeBSD development doesn't have a clear management structure, or a BDFL.
As already noted, I don't want no more (not yet provided after the moment I've registered MS-DOS license) info to M$, but the largest concern is not there. Relying upon free public service by profit-based companies that is not promised to be contributed is dangerous, as it can easily dissappear.

And AFAIK, GitHub pull requests are started to be used, but not yet an official way (trial phase). If I'm not wrong, officially announced way is Bugzilla (as the successor of ancient send-pr database), and Phablicator to help proceeding code review in conjunction with it. Both are under freebsd.org domains (bugzilla.freebsd.org and review.freebsd.org, respectively).
I'm basically filing PR on Bugzilla, and when I have ready-to-be-reviewed patch, additionally open a review on Phablicator. The exception is modifications that doesn't visible to official pkg users like build structure changes. An example: D50142.
 
Let's not derail the OP's discussion with the "Microsoft is evil" topic. Where the git is hosted is a minor issue.

I agree with Sir Dice that this forum is not a sensible place for a discussion of the development process. There are a few developers here, but most people here are users, with no influence on the process. It's not clear to me what the correct venue for addressing their concern would be, given that FreeBSD development doesn't have a clear management structure, or a BDFL.
But its an interesting topic for the FreeBSD community at large, I appreciate the op sharing that on the forum and I agree with more transparency:
It's not clear to me what the correct venue for addressing their concern would be, given that FreeBSD development doesn't have a clear management structure, or a BDFL.

I think the forum is also the right place for sharing this. its just the 'off topic' that might be ruff for such an inquiries. maybe the forum could create a new section ?
 
Didn't see that. I can understand your concern. I also wouldn't want to contribute to this.
But can it be that hard to get an independent github-server?
FreeBSD's authoritative (primary) git server is a write-only server. It is used for developer commits only. It is replicated to a number of geolocated git replicas (cgit.freebsd.org).

The repositories are also replicated to github. What you see on github is a read-only replica. Commits are replicated to it. Closing Github would not affect FreeBSD developer workflow. People may create pull requests. However our pull request process does not use the Github commit function. We fetch pull requests to our local repos and push them to the authoritative git repo. You can read about the process in the FreeBSD Committers Guide.
 
No one likes lengthy and boring meetings. I don’t believe anyone watches the 5-6 hour meeting videos FreeBSD uploads on YouTube—I certainly don’t. But as external contributors, we need to get feedback. That’s also one of the important reasons why quarterly reports are crucial: we want the community to understand the progress and status of our projects.

Also, to be honest, I’d rather have someone actively blocking me than be endlessly ignored until I give up on my own.
How about getting ahold of the process, figuring out what's actively being worked on, what the priorities are?

How about filling out the Bugzilla tickets properly? Tickets with incomplete info get ignored, y'know.

How about reading the Developer's Handbook and Architecture Handbook ? Your submissions need to reflect pretty thorough familiarity with that. The development process for FreeBSD - it does have standards. If your comments betray a lack of knowledge of even that, expect to get ignored. It's just not worth the time and effort to pay attention to someone who doesn't know a thing about how things work. Harsh, I know. But if I tried to get people into more meetings just to show that progress is being made - I'd be getting either blowback or a complete lack of response. There's good and bad ways to go about getting info and getting things done.
 
People think that github is the only place where git trees live.
Indeed. The last batch of junior CVs I went through tended to list GitHub in their skills section rather than Git. Its strange because they don't list p4d or Helix Core rather than Perforce. I suppose GitHub does some fantastic marketing.
 
The last batch of junior CVs I went through tended to list GitHub in their skills section rather than Git
You don't need to be able to use git in order to use github. Just like you don't to be able to use git in order to finish a project from scretch to release on GitLab or Azure Devops.

If someone popped up over here with Github skills on his CV I'd assume he's referencing to github's workflow models, devops, marketplaces, codespaces, compliance strategies, [...], but I'd dig into it nevertheless if I was leading the interview, as most CVs are AI generated these days.
 
I wonder where people get the notion that FreeBSD uses Github for its main repositories? This is not documented anywhere. How do people conclude this?
The people who don't know a lot about how software development works, they just take a look at the very minimal information that is presented to them. All they see is that FreeBSD's source code is available on GitHub. When people don't know anything about software development, they assume that this little bit of information is the whole story.

It's like telling financially illiterate people that the bank is where the money comes from. The fact that there's a lot more to know about money and how much it can buy - that just flies over their heads as information overload.

Those who know at least a bit about how software development works, both in theory and in practice, they would make comments and conclusions that reflect that knowledge. Those who don't have the knowledge - they make comments and conclusions that reflect that lack of knowledge. 😑

My take is, lack of knowledge is actually OK - if one owns up to it. Pretending to know something - that's a reason to be ignored.
 
I wonder where people get the notion that FreeBSD uses Github for its main repositories? This is not documented anywhere. How do people conclude this?
A lot of people have such an extreme hate for big tech (in particular for Microsoft and Google) that the mere mention of any word that starts with "git" makes them go into conspiracy theory mode.
 
most CVs are AI generated these days.
PSA: so are some interviews. Can't find the source right now but if it is remote, make them pick their nose or something. It screws the AI filter. Case in point was a guy claiming to be from Poland, didn't know a word of polish.

Edit: Source
 
You don't need to be able to use git in order to use github. Just like you don't to be able to use git in order to finish a project from scretch to release on GitLab or Azure Devops.
That's unlikely what they were trying to express. As a software engineer role, I would recommend putting "Git" on there as priority of the core VCS technology.
 
I wonder where people get the notion that FreeBSD uses Github
In my post #26 - if you had read it - I say:
I thought FreeBSD's github was independent of "Microsoft's" GitHub.com?
So, after
The URL https://github.com/freebsd indicates it's M$'s GitHub.com.
I was not sure anymore. "Maybe this was changed since my last info?" But it was just a simple misunderstandiung, that's already cleared.
I also thanked cy@ for his explanation in post #36 which cleared that.

After that some of you guys seem to start bashing "the unkown stupid." And maybe I'm mistaken, or oversensitive, but I cannot help the feeling that includes me.
So, let me clear up two additional things, before I leave:
I wonder where people get the notion that FreeBSD uses Github for its main repositories?
(most)...
People think that github is the only place where git trees live.
Yes. But that answers only half the question, and induces the next one:
Why do they think that?
Because everywhere and always it's only "github", "github this", "github that", and "github", only: "pull from github!", "I pulled from github" Even here.
You have to search for statements relativize source code sources, and git usage besides GitHub.

To know there is not only github.com where git trees can live you have to learn yourself; e.g. maybe read the developer's handbook, which I don't (yet), because I'm neither a developer, nor will become one in the near future, or you have to think of setting up your own version control system, which I did, deal with the idea to set up your own server with your repo to learn git is usable independently from GitHub.
But this is no proof to know then where FreeBSD's git repos lives (currently, and in the future.)
Again, thanks cy@ for your clear words!
A lot of people have such an extreme hate for big tech (in particular for Microsoft and Google) that the mere mention of any word that starts with "git" makes them go into conspiracy theory mode.
Maybe so.
But maybe that's at least partially their own fault.
Anybody who was not completely asleep since the mid 1990s are aware of it, if not witnessed what "big tech", above all Microsoft, and Google (et al), all actually did, and currently do.
I know, at this point there is a need to name at least one or two examples to not be accused of being a conspiracy theory moron fishing in fog, but not only I want to keep this post as short as possible (and not want to start several side discussions on details on those) there is enough stuff - no "conspiracy BS", real stuff, with evidence, court judgments, and everything - to be found quickly you could write a (large) book of the topic "The Dirty Tricks Microsoft Pulled, and the laws they simply gave a fuck laughing at" alone (plus another, similar one for Google.)

One may also say:
Microsoft is the core and main reason for OpenSource as we have today.

And if you eventually understood how capitalistic economies of companies quoted on stock exchange work (and you better shall know with both Microsoft, and Google that is the case), so understood such a company is not paying even a single cent without seeing any return of investment for it. Bill Gates may do charity as a private person from his own personal assets, but for sure not the company.
And if you finally knew Microsoft paid 7.5 billion (10^9 - nine) for GitHub you don't need to be a paranoid conspiracy theory crackpot from outerspace to understand, that's not for "charity".
That's to get control over the vast majority of open source.

Some may remember: In the late 1990s, early 2000s Microsoft was attacking OpenSource, if not trying to destroy but at least stifle, and badmouth it, above all Linux. They were really afraid to lose serious amounts of customers if Linux actually became the success the Linux community stated their project with trombones in public.
Now they are completely relaxed. In contrary they cooperate. They learned: There is no danger. Linux is nothing a common computer user ever touches freely. Besides Linux is a playground for some few computer nerds it settles market niches Microsoft don't need to care about. Plus once in a while something useful drops out of there. So they not engage it anymore. They support it. Among other things with GitHub.
For the OpenSource (Linux) community it's perfect (bait was a conspiracy theory): A powerful, professional maintainded central hub where all open source projects may live. For free. By now. Some may remember open source community experienced such things like SourceForge. Finally they wanted to make profit from it, regardless what was promised. To accuse Microsoft similar motives must be a conspiracy theory, of course. I know you have to register to GitHub. And I also know most of those "free" services sooner or later also want your real, and validated e-mail address, your real name, and eventually your phone number. I don't want to explain that (length of post), but that's the end of free usage.
Until then, if anything useful to Microsoft appears on GitHub, they can pick it. I see no problem in that in general. Many open source developers work for exactly that: Hope to be found, and get real money for their work.
For Microsoft it's more comfortable to have it all centralized on their own machines instead to crawl the internet for it.
In my eyes that's one point why GPL is like it is: "If you want to make money with it, pay the developers." But I neither want to start any license debate, again. (Personally I'm with BSD, and MIT.)
But on the other hand they have the control over it. Conspiracy theory: Maybe one day they simply proclaim all the licenses the GitHub users put their software under were invalid, and only Microsoft's licenses are now valid - "didn't you read the last terms of usage change? But you singed it anyway." According to what we've seen in the last thirty years that was something not completely from outside this universe.
And I read several blog entries from GitHub dropouts, range from warning to open boycott. But of course I cannot really judge that. So this must be rated as conspiracy theory.

But what I'm convinced about nevertheless is if they can, and will block anything occurs on GitHub that may endanger their revenue.
Just as an thought experiment: Imagine on GitHub a complete turn key operating system is published for free usage: core features: runs on any typical end-users computer hardware, completely foolproof autodetecting, autoinstalling, and autoconfiguring all hardware, internet access, etc. comes up with a windowslike (or even better) desktop environment (a lot of noisy and colorful blinking fiddle-faddle crap), but above all: capable to install and run any Windows software as you were running Windows itself. Maybe some turnkey Linux distro with some sophisticated Wine implementation (It's not my point here to discuss if this can be really done, or how exactly.)
What do you think will happen?
Must be a conspiracy theorie based on irrational hate against those "evil big tech" to accuse Microsoft would close the according GitHub repository.


All I wanna say is, you may produce conspiracy theories about the details of what, when, why, and how,
but for sure not for not blindly trust GitHub totally, unconditionally in full, but being careful what you place there, have some independent, primary server (what we've learned FreeBSD has), and anyway always stay guard to preserve your independency.

If history told us one thing, it's always better to be precautious in the first place, than to whine afterwards about breach of trust, and look for justice with court trials, which you may win for sure but will have no use of it, because "evil big tech" still earns millions with it, and simply laughs at you, while you spend many ten thousands of dollars to finally get to your right, which after several years became worthless.

Peace out.
 
Back
Top