Hi Lucas,
Thank you for bringing up the idea of Debian applying for the OpenAI
Open Source Fund. I appreciate you taking the initiative to explore
potential funding opportunities that could benefit DDs who might decide
freely to profit from it or not.
Since you've asked for DPL approval, I hereby
> > All of the above are closed-source solutions.
>
> Not Codex CLI
Indeed, I guess I need to try it out now to evaluate it.
> > I have been playing
> > around with the fully open https://aider.chat/ for well over a year
> > and I would recommend it instead. I hope to some day write a blog post
>
On 11/06/25 at 22:10 +0300, Otto Kekäläinen wrote:
> Hi!
>
> > > > OpenAI has an Open Source fund. Maybe Debian should apply[1] for a grant
> > > > so that Debian contributors could get hands-on experience on how this
> > > > could help their Debian activities?
> > >
> > > or maybe Debian should n
Hi!
> > > OpenAI has an Open Source fund. Maybe Debian should apply[1] for a grant
> > > so that Debian contributors could get hands-on experience on how this
> > > could help their Debian activities?
> >
> > or maybe Debian should not.
>
> Maybe. Honestly, I don't know.
I still think it would be
Hi,
On Fri, 2025-06-06 at 10:51 +, Holger Levsen wrote:
> On Fri, Jun 06, 2025 at 12:48:11PM +0200, Ansgar 🙀 wrote:
> > > Also they contribute massivly to burning down our only planet
> > > faster.
> > So do in-person conferences, rebuilding software just to observe
> > that
> > no changes hap
On Fri, Jun 06, 2025 at 12:48:11PM +0200, Ansgar 🙀 wrote:
> > Also they contribute massivly to burning down our only planet faster.
> So do in-person conferences, rebuilding software just to observe that
> no changes happen,
horseshit. those things dont require dozens of entire powerplants...
Hi,
On Fri, 2025-06-06 at 10:33 +, Holger Levsen wrote:
> On Fri, Jun 06, 2025 at 12:03:32PM +0200, Lucas Nussbaum wrote:
> > > or maybe Debian should not.
> > Maybe. Honestly, I don't know.
>
> I'd rather not take their offer based on moral grounds: they stole
> and
> steal from everyone an
On Fri, Jun 06, 2025 at 12:03:32PM +0200, Lucas Nussbaum wrote:
> > or maybe Debian should not.
> Maybe. Honestly, I don't know.
I'd rather not take their offer based on moral grounds: they stole and
steal from everyone and want to make that normal. And for that, they
offer some breadcrumbs to th
On 05/06/25 at 11:38 +, Holger Levsen wrote:
> On Wed, Jun 04, 2025 at 05:04:34PM +0200, Lucas Nussbaum wrote:
> > OpenAI has an Open Source fund. Maybe Debian should apply[1] for a grant
> > so that Debian contributors could get hands-on experience on how this
> > could help their Debian activ
On Wed, Jun 04, 2025 at 05:04:34PM +0200, Lucas Nussbaum wrote:
> OpenAI has an Open Source fund. Maybe Debian should apply[1] for a grant
> so that Debian contributors could get hands-on experience on how this
> could help their Debian activities?
or maybe Debian should not.
--
cheers,
Hi,
On 11/01/25 at 19:13 -0800, Otto Kekäläinen wrote:
> ...
> > Debian should consider allocating some budget like several hundred USD
> > per month for the LLM API calls for all members and new-comers' usage.
>
> I don't think Debian should as an organization pay for LLMs. On the
> contrary I w
On Tue, Jan 14, 2025 at 08:52:39AM +0100, Philip Hands wrote:
> I'd really like to know how it is possible for one to use an LLM to make
> a contribution to a permissively licensed project (e.g. Expat) without
> in effect stealing the code from one's own tribe of Copyleft authors.
>
> Can one even
"M. Zhou" writes:
> On Sun, 2025-01-12 at 16:56 +, Colin Watson wrote:
>>
>> (I have less fixed views on locally-trained models, but I see no very
>> compelling need to find more things to spend energy on even if the costs
>> are lower.)
>
> Locally-trained models are not practical in the cu
On Sat, Jan 11, 2025 at 11:25:20AM -0500, M. Zhou wrote:
> On Sat, 2025-01-11 at 13:49 +0100, Fabio Fantoni wrote:
> >
> > Today trying to see how a new person who wants to start maintaining new
> > packages would do and trying to do research thinking from his point of
> > view and from simple s
On 2025-01-12 at 18:03 +, Andrew M.A. Cater wrote:
> Watching other people find and fix bugs, even in code they
> have written or know well, I can't trust systems built on modern
> Markov chains to do better, no matter how much input you give them, and
> that's without crediting LLMs as able to
On Sun, 2025-01-12 at 16:56 +, Colin Watson wrote:
>
> (I have less fixed views on locally-trained models, but I see no very
> compelling need to find more things to spend energy on even if the costs
> are lower.)
Locally-trained models are not practical in the current stage. State-of-the-art
On Sun, Jan 12, 2025 at 04:56:15PM +, Colin Watson wrote:
> On Sat, Jan 11, 2025 at 07:13:58PM -0800, Otto Kekäläinen wrote:
> > I don't think Debian should as an organization pay for LLMs. On the
> > contrary I would expect LLM providers to offer API keys for free to
> > Debian Developers just
On Sat, Jan 11, 2025 at 07:13:58PM -0800, Otto Kekäläinen wrote:
> I don't think Debian should as an organization pay for LLMs. On the
> contrary I would expect LLM providers to offer API keys for free to
> Debian Developers just like we have other perks listed at
> https://wiki.debian.org/MemberBe
...
> Debian should consider allocating some budget like several hundred USD
> per month for the LLM API calls for all members and new-comers' usage.
I don't think Debian should as an organization pay for LLMs. On the
contrary I would expect LLM providers to offer API keys for free to
Debian Devel
On Sat, 11 Jan 2025 18:04:15 +0500, Andrey Rakhmatullin wrote:
> Yeah, not sure if that's your point but I think everyone agrees that we
> need a good new packager document and while there were some attempts in
> the past (see links on https://mentors.debian.net/intro-maintainers/ )
> there is sti
Hi!
(cross-posting to mentors as they have most experience on what is
wrong with our current docs)
...
> Even if somebody in Debian community has enough time to overhaul everything
> and create a new documentation, it will become the situation described
> in XKCD meme "standards": xkcd.com/927/ -
On Sat, Jan 11, 2025 at 11:25:20AM -0500, M. Zhou wrote:
> Opinion against this post will include something about hallucination.
> In the case LLM write something that does not compile at all, or write
> some non-existent API, a human is intelligent enough to easily notice
> that build failure or l
Il 11/01/2025 16:38, Ahmad Khalifa ha scritto:
On 11/01/2025 12:49, Fabio Fantoni wrote:
Write on Google "Debian create new package" and first result:
https:// wiki.debian.org/HowToPackageForDebian
It points to various parts but mainly the more probable start point
seems https://wiki.debian.o
On Sat, Jan 11, 2025 at 03:38:10PM +, Ahmad Khalifa wrote:
> > Write on Google "Debian create new package" and first result: https://
> > wiki.debian.org/HowToPackageForDebian
> >
> > It points to various parts but mainly the more probable start point
> > seems https://wiki.debian.org/Packagin
On Sat, 2025-01-11 at 13:49 +0100, Fabio Fantoni wrote:
>
> Today trying to see how a new person who wants to start maintaining new
> packages would do and trying to do research thinking from his point of
> view and from simple searches on the internet I found unfortunately that
> these parts a
On 11/01/2025 12:49, Fabio Fantoni wrote:
Write on Google "Debian create new package" and first result: https://
wiki.debian.org/HowToPackageForDebian
It points to various parts but mainly the more probable start point
seems https://wiki.debian.org/Packaging/Intro
To point to git and gbp see
Le 2025-01-11 13:49, Fabio Fantoni a écrit :
What would be the best, easiest and fastest procedure (especially for
newcomers) to create a new package from scratch, aiming to use git,
salsa, salsa-ci, gbp and DEP14 from the beginning?
It Depends™. As in, it really depends on what you are pack
On Sat, Jan 11, 2025 at 01:49:33PM +0100, Fabio Fantoni wrote:
> I don't know if I've managed to explain well what I mean, but from what I've
> seen over the years, most of the people I've seen trying to approach
> packaging have had difficulty finding documentation and help (even on
> mentors, alt
There has been a lot of talk about attracting and helping new
maintainers, some improvements have been made "here and there", the
documentation of gbp (the most used tool) has been improved, salsa,
salsa-ci have been improved, there is discussion about DEP18, accepting
DEP14 etc...
Having mos
29 matches
Mail list logo
