Rudra
So guys, I don't suppose there's anything we can do to get @rudra' s attention, is there?
22 Replies
he's still like alive
just very busy
this isn't much of a support post :sobmelt:
but the problem is currently we're pushing towards v5 instead of making big changes to v4
but it depends on what happens with v5
if it's taking a bit longer we might reevaluate
with school
and life
good to know, thanks. i think there are some issues that, I am guessing, are pretty minor developing-wise, but cannot be fixed w/o his unmediated attention
ﾑ丂ｲ乇尺ﾉ丂ズ received a thank you Jao!
maybe tending to those might alleviate some anxieties
you should leave those concerns on their respective gitlab repos
Yeah that’s not tied to a specific repo
I mean if there’s anything related to, say, akshara leave it there
what I am trying to say is that you told me that I should not bother filing a bug request, because you guys are already aware of the issue
We are in that case but if you have anything else leave it on gitlab
You implied there was more
Just not under blendOS/blendos
If your issue would go there put it on discord
There’s no point
that is the only burning issue that I got
okay
Any chance we could get him to have a look at this anytime soon please? This is absolutely crippling as far as I am concerned.
ihewf7rgyfgreuifer7ifgifgheryugfergfryufegyru
i can pester him later
Thanks!
Any luck getting through to him? 🤔
Christian.
The team have been relatively responsive, and kind as far as moderation goes, even allow this post(which is not an actual support post) to exist, let alone directly addressing your concerns..
This issue is not going to be resolved in a week, I wouldn't even expect V5 until 2026 - TBD.
(In my opinion)
This is a free project without any major financial backing, so everyone has their own responsibilities outside of blend that take priority.
This includes Rudra who's been relatively in-active for months.
(School and others things)
The team isn't going to give you day to day or weekly updates specifically on this issue or Rudra's exact whereabouts.
They've tracked the issue, and have already given you plenty of info.
Understand that patience is a virtue.
And please stop spamming the team about the issue they've already tracked to fix.
Thanks for replying. I certainly appreciate the team's responses, though, as far as I can tell, most issues that I have come across have been dealt with--following advice from the team--by way of
system.yaml workarounds and petty hacks rather than full frontal bona-fide fixes in the blendOS code base. As such, it is hard to ignore the strong whiff of abandonware that the blendOS project increasingly gives out, which, I am guessing, is not exactly the image that the team intends to project. Now, if this project has, indeed, been abandoned, I (and, I presume, many others who run blendOS as their daily driver) would certainly appreciate a heads up; at the very least, you guys should post a big warning on the project's main website to the effect that due to major commitments in everyday life, the project has paused development as of <date>, and no issues that require tampering with the code base will be addressed until further notice. Otherwise, I, for one, am quite willing to involve myself deeper in its development--should I be allowed to access the code innards, that is--to at least tend to my own grievances instead of whining all over the place. Or maybe the main developer should delegate other members of the current team to deal with relatively minor code changes and fixes.
As far as "tracking the issue(s)" goes, I would feel slightly more reassured if I saw them listed in the list of blendOS GitLab issues, which is why (and where) I offered to post them myself.
Finally, be assured that the above are simply innocent suggestions, hence please do not take my intervention the wrong way. I do appreciate the developers' commitment and time invested in what is ultimately a gift to the FOSS community. I could not be more thankful for their work and dedication.infantry32 received a thank you Jao!
there's no warning because the distro hasn't been abandoned, rather, the only individual with repo access has gone inactive
code modifications can still be made
and the gitlab issues are full of imported github crap and we don't currently have a way to create a nice issue board where we can keep track of everything
but regardless you can make an issue if you want
I'm working on making a full issue board people can look at
so @Christian you can make an issue on gitlab and I'll add it to the board
what exactly do you mean by "should I be allowed to access the code innards, that is"? the code is freely available on our gitlab, and is pretty simple, even building an iso is very easy
all i can think is that you mean write access to the code and the pacman repo
and as for that i'll just say we prefer zstd
also, regarding this
maybe the main developer should delegate other members of the current team to deal with relatively minor code changes and fixesif you mean pushing changes/updating the pacman repo, you have been told that rudra is the only one who can update the repo, and he's busy. if you mean updating the code itself, i am said team member, and i am busy as well. so, there's no reason you can't write code yourself, despite your complaining and "offer" to, and i am busy. so unless you're going to get my bachelor's for me, wait until i have the time, motivation, and functioning computer to work on this. additionally, you've been told that major changes will come in v5, and most of the issues we have would require pretty significant changes. the primary issues are that
/etc is ephemeral (per-rebuild), and that it's a complete reinstall every rebuild. the former would require either big changes or maybe a hacky workaround, and the latter requires major changes. there's also the issue(s?) where the installer won't boot, and we just don't have enough information, nor can we can't reproduce it.yes.
@i ♥ unnatural carnal copulation: "if you mean pushing changes/updating the pacman repo, you have been told that rudra is the only one who can update the repo, and he's busy." Which is precisely why it makes very much sense to not be the only one who can update the repo.
well you're not wrong, but that's also just not happening right now
i'd host my own alternative repo, but my server is far too unreliable, and is rather lacking in bandwidth
(i do actually host my own repo, but that's just for dev testing with my own versions of the packages)
get out of here jia tan
I already host a repo mirror
:)
If you wanna write code man make a MR I’ll update your project limit so you can fork
done :)