On Tue, Mar 13, 2012 at 11:22 AM, George Rosamond <span dir="ltr"><<a href="mailto:george@ceetonetechnology.com">george@ceetonetechnology.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 03/13/12 11:19, Matthew Story wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Tue, Mar 13, 2012 at 11:16 AM, George Rosamond<<br>
<a href="mailto:george@ceetonetechnology.com" target="_blank">george@ceetonetechnology.com</a>> wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On 03/13/12 11:14, Matthew Story wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Mon, Mar 12, 2012 at 8:49 PM, George Rosamond<<br>
<a href="mailto:george@ceetonetechnology.com" target="_blank">george@ceetonetechnology.com</a>> wrote:<br>
<br>
On 03/12/12 18:57, Eitan Adler wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
On Mon, Mar 12, 2012 at 11:10 AM, Matthew Story<<a href="mailto:matthewstory@gmail.com" target="_blank">matthewstory@gmail.com</a>><br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
wrote:<br>
<br>
Wanted to put out a feeler about doing some meetings on the benefits<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
and<br>
pitfalls of porting *BSD software to non-BSD systems. And the various<br>
reasons why projects choose to do this, or to support alternate<br>
distributions of their software that provide optional *BSD software.<br>
<br>
<br>
</blockquote>
Perhaps this list could be updated too?:<br>
</div><a href="https://en.wikipedia.org/w/****index.php?title=List_of_**" target="_blank">https://en.wikipedia.org/w/***<u></u>*index.php?title=List_of_**</a><<a href="https://en.wikipedia.org/w/**index.php?title=List_of_**" target="_blank">ht<u></u>tps://en.wikipedia.org/w/**<u></u>index.php?title=List_of_**</a>><br>
products_based_on_FreeBSD<<u></u>http**s://<a href="http://en.wikipedia.org/w/index.**" target="_blank">en.wikipedia.org/w/<u></u>index.**</a><br>
php?title=List_of_products_**<u></u>based_on_FreeBSD<<a href="https://en.wikipedia.org/w/index.php?title=List_of_products_based_on_FreeBSD" target="_blank">https://en.<u></u>wikipedia.org/w/index.php?<u></u>title=List_of_products_based_<u></u>on_FreeBSD</a>><div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
</blockquote>
<br>
<br>
Well, if we hosted it as a project, we would do all the BSDs, and<br>
</div></blockquote><div class="im">
include<br>
products with relevant libraries (android), OpenSSH, etc., I would think.<br>
<br>
Maybe a few fields:<br>
<br></div>
product/manufacturer/software/<u></u>****role/submitter/<u></u>verification<div class="im"><br>
<br>
<br>
<okan sharpening knife as I dream up new online apps. . .><br>
<br>
</div></blockquote><div class="im">
<br>
<br>
You're suggesting a NYC*BUG curated list of projects that make use of BSD<br>
software from any of the projects on www.?<br>
<br>
<br>
<br>
</div></blockquote><div class="im">
Yes. A central repository for anyone to upload. The problem is<br>
verification, IMHO.<br>
</div></blockquote><div class="im">
<br>
<br>
Could kill 2 birds with one stone on the verification, ask posters to<br>
provide a list of components, and the location of those components in the<br>
project ... that way we could solve the wikipedia problem of ... "where<br>
does android use extensive freebsd software" (my guess on that is that<br>
sandbox makes extensive use of jail(8) ... but haven't actually gone diving<br>
into the source).<br>
</div></blockquote>
<br>
See above in field listing.<br></blockquote><div><br></div><div>gotcha, sorry I missed that the first time around.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The question is how to implement what is essentially an organizational solution for technical verification.<br></blockquote><div><br></div><div>As long as we collected some contact information (as suggested by the submitter field above) so that we could reach out for clarification, it seems like this could be solved by verification volunteers. I'd be happy to volunteer for verification work.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I assume we'd have a staging/upload area, then have others verify based on submitted fields.</blockquote><div><br></div><div> Makes sense to me.</div></div>