Wolfi
Replies: 1 comment 1 reply
-
|
@gdonval @jelmer @sil2100 @dannf can you per-chance look at PRs at https://github.com/wolfi-dev/os/pulls/gdonval and let me know if they seemed to be non-malicious and on the right track to integrate all of these things? And then we can look into rebasing them and landing them. |
Beta Was this translation helpful? Give feedback.
-
|
SSSD is more of a RedHat than a Samba/AD thing, and not really something I'm familiar with. It integrates with samba/is built on some of the same tech. |
Beta Was this translation helpful? Give feedback.
-
Changes I've contributed are being marked as staled, having been there doing nothing for 3 months.
As I have voiced before here, allowing this kind of thing to happen (I contributed other packages too) does not help in considering Wolfi as anything but dead, untrustworthy and useless. If external contributions cannot be reviewed (I appreciate staff may be busy with what they have to do already), then they should absolutely not be allowed because, again, it makes your project look dead, untrustworthy and useless.
What I see now is that I spent time learning melange and apko, spending time to craft minimal packages for exactly nothing. Such is life. But what if I discover a bug or problem with compilation/package split, or God forbids, try to contribute a useful package like SSSD to make (enterprise) LDAP work for us at work, start using Wolfi and buy support? Well in such a case, I learned those contributed changes are being marked as stale and will be closed soon. So no enterprise deal and no trust whatsoever on the platform.
So as per title: for your own future, if you are too busy reviewing and accepting public contributions, just don't or it won't end up well for you because the techies who understand the point of what you do to push it to management are also the ones whose trust you can lose the easiest.
Beta Was this translation helpful? Give feedback.
All reactions