[oi-dev] Paid change request aka Bounty

[gemelen]

Sorry to jump into, but I'd like to comment on the Till's suggestion - this is exactly the
kind of solutions that, in my opinion, should be weed out:
paying for all problematic tech solution to a bigtech company instead of waging 
it to a person, that might be in a need to pay for the life supporting needs.

That's up to the Reginald in this case and to a person in need of a problem to be solved,
in general, but I believe we want a community here first of all?

In order to provide an alternative, if nobody would vouch themselves, I'd rather do the
requested change myself, even if I've never looked into the Audacity beyond occasional
use.

On Tue Sep 22, 2026 at 2:00 PM -03, Till Wegmüller wrote:
> Hi Reginald
>
> Considering modern Tooling that I have tested recently the price for an individual Package is far less than this.
> 200 Dollar gets you access to a Tool from either China or the US that can read the documentation and make that package and have Usage leftover to handle maintenance of X11 in the background, port a simple driver to rust run and test it over SSH. In the process accidentally cross compile said module and install and test it.
>
> I am currently testing how well an independent GPU runnable version can do this but at current speed, that capability is only a couple of months out. If we could get this with a clean conscience that would be the best but it is what it is. There is a real risk of spam, but give it a high quality description what to do (best an onboarding guide like our docs) and perform rigorous local QA and it will produce good output. 
>
> With 200 dollar I would grab a Codex subscription and make the package based on the newest Audacity which has a lot of improvements.
>
> At this moment the project needs people that continuously keep a set of packages maintained and if that is with Automation thats ok. Contributors are more likely to not feed the docs to their AI and then the AI get the package wrong but simply feed the Computer the docs and it works. 
>
> Spam and low quality will be handled but I am not preventing needed automation and helping out new automation efforts.
>
> -Till
>
>> On 21 Sep 2026, at 00:07, Reginald Beardsley via oi-dev <oi-dev at openindiana.org> wrote:
>> 
>> I find the audacity link failure intolerable.
>> 
>> I should like for someone sufficiently familiar with the repository code to implement a filter which prevents deposition in the repositories of packages which have run time linker issues. And also purge the repositories of packages which fail to link. 
>> 
>> For the work I propose a payment via the OI cooperative  of $200 USD to whomever performs the task.  
>> 
>> For OI to survive it needs to develop a gig economy.  This is a first stumble at doing it.
>> 
>> Have Fun!
>> Reg
>> _______________________________________________
>> oi-dev mailing list
>> oi-dev at openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev


-------------- next part --------------
A non-text attachment was scrubbed...
Name: D79C930A5F78FC5C.asc
Type: application/pgp-keys
Size: 891 bytes
Desc: not available
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20260922/24124cb5/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 265 bytes
Desc: not available
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20260922/24124cb5/attachment-0001.bin>