Search results

Almost all FreeBSD developers are volunteers. They look at whatever social media sites suit them. There are far too many to participate in them all.

I was reading this while watching TV and eating a sandwich, and even so, it was a complete waste of my time. (cracauer's and cy's as well.) There is a reason why I do not often visit the forums, and this thread is an excellent example. Sigh.

When the only thing the _volunteers_ get is negative feedback, it is completely demotivating. For paid employees, it's different. I agree that regressions are bad and I spend some of my own free time trying to highlight them in Bugzilla. But I am just one contributor.

(with respect to forth) It had gotten to the point where very few developers wanted to work with forth. There was indeed discussion about including lua in the base system, but the compromise was to restrict that minimal version lua to base system only, thus avoiding the constant problems with...

> I will not be surprised if 16.0 adds some sort of Flatpak-type system, or Wayland, or a systemd-style init nightmare. This is simply FUD. All you are doing is demotivating people who are doing the heavy lifting. For myself, I can either spend time (like this) trying to correct...

"someone" was wrong. perl was removed over a decade ago. It became too complicated to try to keep perl-in-base up to date w/rt our release schedules.

Hello! Would you be able to accomodate guests? Say, for ... 3,5 years? :) (Sorry, I just had to ask. Looks like a lovely place.)

The last time I wrote down some notes about conversations on Documentation / Wiki were: https://wiki.freebsd.org/MarkLinimon/WikiGoals

We have two ACLs, the DevelopersGroup and the ContributorsGroup. The differences between the two are really minor (maybe, like editing the front page?) We do have hundreds of people in ContributorsGroup, and membership is open to community members.

I do not have a summary of the ideas that have been kicked around on the Discord, sorry. This is exactly the type of thing where someone new needs to pick up the baton.

We have never gotten a consensus on how exactly it should read, and whether the overall project Code of Conduct should apply to it. We also never spelled out what the terms for making contributions are. Back N years ago when the wiki was started, such things were not as important as they are...

The FreeBSD Bugzilla has over 10,000 PRs in it. We are trying to improve our throughput of the ones that do have patches. Most of the others are true "bug reports". Historically, feature requests have simply been buried in the noise. We successfully deal with almost none of them. As I...

Simply: backlog. We have gotten closer to steady-state on the number of ports PRs in Bugzilla, but around 20 come in per day. Over the past 365 days, 6662 ports PRs have arrived and 6934 have been closed, leaving us at a total of 3352. (Of course, some PRs are much easier than others). See...

The best way to understand that is probably https://docs.freebsd.org/en/books/handbook/x11/#x-graphic-card-drivers .

Sigh. The next time someone asks me why I am not active on the forums, I am going to point them to this thread.

From personal experience, portmgr has traditionally been one of the most over-committed groups within FreeBSD. I usually try to be diplomatic but after the last 2 weeks fighting a flame war, I'm instead going to say: the passive-agressive use of the italics is counterproductive.

https://www.freebsd.org/internal/code-of-conduct/

The problem, of course, is how to balance this vs. "we only want to see germane discussions". I am not familiar with the forums framework so I'm not the right person to comment.

In my experiece in watching Bugzilla, most of the company-related things are either a) related to support of their products (hardware or software), or b) bugs in the base system. I do not know of any commercial company specifically funding ports work. I really don't think this idea would work...

Our particular one aims to be better. It varies between channels. I only run one of them (#project-infrastructure); in the others, I am at best an interested observer. A few years ago I personally had to cut back on FreeBSD social media/mailing lists/etc. There is simply too much for one...