<story><title>LLama.cpp now has a web interface</title><url>https://github.com/ggerganov/llama.cpp/pull/1998</url></story><parent_chain><item><author>mk_stjames</author><text>I&amp;#x27;m always wondering about the, I don&amp;#x27;t even know what to call this, etiquette? of proposing PR&amp;#x27;s to projects like these that add a feature or a demo or whatnot to the main branch of a very focused project by adding something that is very different in interface, language, set and setting etc.&lt;p&gt;So in this case, Tobi made this awesome little web interface that uses minimal HTML and JS as to stay in line with llama.cpp&amp;#x27;s stripped-down-ness.  But it is still a completely different mode of operation, it&amp;#x27;s a &amp;#x27;new venue&amp;#x27; essentially.&lt;p&gt;What if GG didn&amp;#x27;t want such a thing?  When is something like this better for a separately maintained repo and not a main merge?  How do you know when it is OK to submit a PR to add something like this without overstepping (or is it always?)&lt;p&gt;I see this with a few projects on github that really &amp;#x27;blow up&amp;#x27; and everyone starts working on.  They get a million PR&amp;#x27;s from people hacking things on it in their domain of knowledge, expanding the complexity (and potentially difficulty to maintain quality). Sometimes it gets weird feeling watching from the outside at least (I&amp;#x27;m not a maintainer on any public FOSS).&lt;p&gt;Just curious what others think because those are my thoughts that came to mind when I saw this.</text></item></parent_chain><comment><author>ggerganov</author><text>My POV is that llama.cpp is primarily a playground for adding new features to the core ggml library and in the long run an interface for efficient LLM inference. The purpose of the examples in the repo is to demonstrate ways of how to use the ggml library and the LLM interface. The examples are decoupled from the primary code - i.e. you can delete all of them and the project will continue to function and build properly. So we can afford to expand them more freely as long as people find them useful and there is enough help for maintaining them. Still, we try to keep the 3rd party dependencies to a minimum so that the build process is simple and accessible&lt;p&gt;There was a similar &amp;quot;dilemma&amp;quot; about the GPU support - initially I didn&amp;#x27;t envision adding GPU support to the core library as I thought that things will become very entangled and hard to maintain. But eventually, we found a way to extend the library with different GPU backends in a relatively well decoupled way. So now, we have various developers maintaining and contributing to the backends in a nice independent way. Each backend can be deleted and you will still be able to build the project and use it.&lt;p&gt;So I guess we are optimizing for how easy it is to delete things :)&lt;p&gt;Note that the project is still pretty much a &amp;quot;big hack&amp;quot; - it supports just LLaMA models and derivatives, therefore it is easy atm. The more &amp;quot;general purpose&amp;quot; it becomes, the more difficult things become to design and maintain. This is the main challenge I&amp;#x27;m thinking how to solve, but for sure keeping stuff minimalistic and small is a great help so far&lt;p&gt;&amp;gt; What if GG didn&amp;#x27;t want such a thing? When is something like this better for a separately maintained repo and not a main merge? How do you know when it is OK to submit a PR to add something like this without overstepping (or is it always?)&lt;p&gt;I try to explain my vision for the project in the issues and the discussion. I think most of the developers are very well aligned with it and can already tell what is a good addition or not</text></comment>
<story><title>LLama.cpp now has a web interface</title><url>https://github.com/ggerganov/llama.cpp/pull/1998</url></story><parent_chain><item><author>mk_stjames</author><text>I&amp;#x27;m always wondering about the, I don&amp;#x27;t even know what to call this, etiquette? of proposing PR&amp;#x27;s to projects like these that add a feature or a demo or whatnot to the main branch of a very focused project by adding something that is very different in interface, language, set and setting etc.&lt;p&gt;So in this case, Tobi made this awesome little web interface that uses minimal HTML and JS as to stay in line with llama.cpp&amp;#x27;s stripped-down-ness.  But it is still a completely different mode of operation, it&amp;#x27;s a &amp;#x27;new venue&amp;#x27; essentially.&lt;p&gt;What if GG didn&amp;#x27;t want such a thing?  When is something like this better for a separately maintained repo and not a main merge?  How do you know when it is OK to submit a PR to add something like this without overstepping (or is it always?)&lt;p&gt;I see this with a few projects on github that really &amp;#x27;blow up&amp;#x27; and everyone starts working on.  They get a million PR&amp;#x27;s from people hacking things on it in their domain of knowledge, expanding the complexity (and potentially difficulty to maintain quality). Sometimes it gets weird feeling watching from the outside at least (I&amp;#x27;m not a maintainer on any public FOSS).&lt;p&gt;Just curious what others think because those are my thoughts that came to mind when I saw this.</text></item></parent_chain><comment><author>LawnGnome</author><text>I generally think it&amp;#x27;s fine to do this sort of thing for your own benefit and open a PR as long as you&amp;#x27;re really 100% fine with &amp;quot;no, I&amp;#x27;m not interested in merging this&amp;quot; being the answer.&lt;p&gt;Where the problems tend to arise (in my experience, at least) is when people hack on something expecting that it will be merged, get invested in it, and then get upset when the maintainer(s) aren&amp;#x27;t interested.&lt;p&gt;Checking in before starting to work on something is important if your goal is to have it merged, not just to do the work. The problem is that a lot of people start in the first category, but then move into the second category as they get invested in their project.</text></comment>