<html>
<head>
<meta content="text/html; charset=windows-1255"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Micha,<br>
We discussed what VM docs to write in our daily IRC meeting today,
and agreed that we would only want 1 VM doc.<br>
<br>
It is important to note the importance of keeping docs concise
because it is less words to read, it is easier to manage review
and translation, and it is easier to translate.<br>
<br>
Could you please:<br>
1. Move vmdk_quickstart into virtualbox_quickstart.<br>
2. The old virtualbox_quickstart text is to be deprecated<br>
3. Combine elements of virtualization_quickstart into the new
virtualbox_quickstart<br>
4. Any extra text you wish to keep to be moved into a wiki page
and referenced<br>
<br>
Feel free to try catching one of us on
<a class="moz-txt-link-freetext" href="irc://freenode.net#osgeolive">irc://freenode.net#osgeolive</a> if you wish to discuss.<br>
<br>
On 30/07/2012 5:08 AM, Micha Silver wrote:<br>
</div>
<blockquote cite="mid:50158A2E.2000509@arava.co.il" type="cite">
<meta content="text/html; charset=windows-1255"
http-equiv="Content-Type">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
Hi Cameron:<br>
<br>
On 07/29/2012 03:25 AM, Cameron Shorter wrote:
<blockquote cite="mid:501482DC.6090602@gmail.com" type="cite">Thanks
Micha, <br>
I've had a quick first pass over the virtualization_quickstart
and vmdk_quickstart. <br>
The vmdk quickstart looks good. I'll have a few relatively minor
comments to make when I do a full review (in ~ 24 hours). <br>
<br>
What I suggest is: <br>
* We should only have one quickstart for VMs. <br>
* So virtualization quickstart and vmdk quickstart should be
combined into one. <br>
* And we should deprecate the vitualbox quickstart. <br>
* Actually, I think we should all 3 quickstarts should be
renamed virtualbox quickstart, so that we have some history
consistency, and it will be easier to track what has/has not
been translated over versions of osgeolive. <br>
<br>
</blockquote>
<br>
Alex mentioned adding a page describing Parallels, and Hamish
wanted another showing how to build a VM on Linux using libvirt.
So I've left it with the one *short* intro document, and the link
at the bottom to the details. It looks cleaner and more concise
this way. And what's more, we can decide whether or not to add
detailed pages for other VM platforms in the future. I don't see
the problem with additional, separate pages? Those interested will
look deeper. And casual users will make do with the brief
overview.<br>
<br>
If it still looks too split up, let me know and I'll merge the two
pages into one.<br>
<br>
Regards,<br>
Micha <br>
<br>
<blockquote cite="mid:501482DC.6090602@gmail.com" type="cite"> <br>
On 28/07/12 19:48, Micha Silver wrote: <br>
<blockquote type="cite">On 07/28/2012 01:11 AM, Cameron Shorter
wrote: <br>
<blockquote type="cite">Micha, <br>
Are you still good for your offer to write a VM Howto? <br>
We were discussing this in our daily IRC meeting and agreed
that it would be good to have one. <br>
<br>
</blockquote>
<br>
I'll give it a shot over this weekend. <br>
Your guidelines seem fine. As I mentioned, I'll put together a
VM overview, covering only the "why" and machine requirements.
Then it will have links to: <br>
<br>
* your current page <br>
* setting up a virtualbox VM straight from the *.vmdk version
of the <br>
Live DVD. <br>
* the VM wiki page <br>
<br>
That should be an improvement. <br>
<br>
<br>
Thanks, <br>
<br>
Micha <br>
<br>
<br>
<blockquote type="cite">What I suggest is: <br>
1. Try to ensure that the doc is concise, so there is less
to translate. (The current VM that I wrote is too long). <br>
2. Describe how to set up a VM for only one VM. Our
quickstarts should be quick, (and easy to maintain), and
shouldn't confuse users by asking them to decide on which VM
to use. <br>
3. I'm open to suggestions re which VM you think you should
write to. I'd guess you would select the easiest, or most
widely used Open Source VM, but this will probably be your
call. <br>
4. Finish with a link to an OSGeo-Live-VM wiki page. The
wiki page can include much more detail, including how to
install multiple versions of VMs. <br>
<br>
Lastly, I'm being really bad by hoping to get some docs
within a day or 2 - which will be required if we are to give
translators enough time to translate it. (I'm also hoping to
review it for you). <br>
<br>
I've created an issue to track this here: <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://trac.osgeo.org/osgeo/ticket/966">https://trac.osgeo.org/osgeo/ticket/966</a>
<br>
<br>
On 25/07/12 12:28, Hamish wrote: <br>
<blockquote type="cite">Cameron wrote: <br>
<blockquote type="cite"> I suggest that we should: <br>
1. Describe one way to create a VM inside OSGeo docs <br>
2. Describe one way to create an ISO inside OSGeo docs
<br>
<br>
Point to wiki pages where we can describe multiple
ways for <br>
creating ISO/VMs. <br>
</blockquote>
or perhaps just describe what a VM is, how it works, and
what you need <br>
to run one on the disc, + the link to the rich mediawiki
howtos pages. <br>
Similar for booting off persistent USB sticks which may be
a new concept <br>
to some conference goers. <br>
<br>
<br>
2c, <br>
Hamish <br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Micha Silver
GIS Consultant, Arava Development Co.
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.surfaces.co.il">http://www.surfaces.co.il</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254
Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
<a class="moz-txt-link-freetext" href="http://www.lisasoft.com">http://www.lisasoft.com</a>
</pre>
</body>
</html>