As I&#39;ve been demoing forge, I&#39;ve been pitching that one of the most elegant aspects of the git-plugin command is that it automatically sets you up with source code to hack on. After experimenting with a plugin tonight, I realized that while the final artifact gets put in ~/.forge/plugins, the repository is hidden away in a cryptic directory in my temporary folder. I think behavior should be changed to make it more welcoming for developers to contribute back.<div>

<br></div><div>I propose one of the following two locations, though feel free to choose a more flexible option:</div><div><br></div><div>~/.forge/plugin-repos</div><div>~/forge/plugins</div><div><br></div><div>...or read an option from .forge/config. Perhaps prompt the user where to stick the source even.</div>

<div><div><br></div><div>-Dan<br clear="all"><br>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>

<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>
</div></div>