Hey Suhail, I was thinking about having a conversation in a guix-devel email thread itself.
>From my understanding, debbugs issues are meant for technical features or issues pending implementation, while guix-devel threads are meant for discussions surrounding Guix and possible features. This is why I had linked the relevant mailing list thread in my blog post as well. Regards, Sarthak. On Wed, Aug 21, 2024, 12:25 Suhail Singh <suhailsingh...@gmail.com> wrote: > Sarthak Shah <shahsarth...@gmail.com> writes: > > > I think starting a debbugs issue could be a good idea once everyone's > > onboard with getting this patch merged! > > I'm not sure I agree that consensus has to be a pre-requisite for > creating an issue. > > > Right now, from what I gather, there are some more important > conversations > > to be had, mainly with the Guix maintainers, as merging this patch could > > lead to a sharp, unexpected increase in complexity if we do not have > proper > > guidelines and procedures in place for parameterization. > > Creation of an issue doesn't imply that the patch (series) has to be > merged (in its current form or otherwise). On the other hand, creation > of an issue allows for feedback to be gathered in one place. In fact, I > would argue that there's value in creating an issue even before any code > towards a patch has been written (by, say, submitting a feature request > to <bug-g...@gnu.org>). > > If not on an issue, where do you intend to have the conversations you > alluded to above? > > -- > Suhail >
