<div dir="ltr"><div class="gmail_default" style="font-size:large">Basically, we need to take one step back so we can move forward.<br><br></div><div class="gmail_default" style="font-size:large">the OpenSolaris community as it is has always been small from the start after Sun was swallowed by Oracle and all official development ceased<br>
<br>
</div><div class="gmail_default" style="font-size:large">we had to start over with illumos and OpenIndiana,<br>however, there has not been much collaboration outside of Nexenta and Joyent internal developement, and there is a general feeling of a hack and slash attitude within illumos and OpenIndiana circles, not very inviting to contributors as significant UNIX code-base inherited from Sun's Solaris core is shrinking while the bloat and half-baked code is growing<br>
<br></div><div class="gmail_default" style="font-size:large">I think people behind TribbliX, XStreamOS, DilOS, napp-it and OmniOS should get together with Schillix and OpenSXCE (previously MartUX) in re-creating the original code-base with significant code improvement plugged in, if any..<br>
<br></div><div class="gmail_default" style="font-size:large">another concern is the 3-Gigabyte download for live media!!! i remember there was a time when there was a light OpenSolaris LiveCD based on build 134 (700++ MB), which was easy to try and actually instantly install, from which additional packages can be added to build the system that's right for you.. even with fast internet connection a 3-GB media is too hard to swallow and a high barrier for would-be developers and casual slackers trying a modern UNIX-based system<br>
<br></div><div class="gmail_default" style="font-size:large">I haven't kept track how build 134 metamorphosed into build 151a9 today, since 2011 I was busy in developing Network Technologies and integrated solutions through Unified Communications and virtualization working with Cisco.com after my failed attempt at volunteering at Sun just when Oracle bought it, but i think it is never too late to take one step back and pick the pieces of our OpenSolaris community, as the only open source UNIX community<br>
<br></div><div class="gmail_default" style="font-size:large">a large-scale community collaboration of all OpenSolaris-based distribution is needed, and I am willing to do my part in bringing this together, hopefully people from the illumos Foundation can help, but the community must move forward with or without their stewardship, what we need is a massive de-duplication of efforts in our community focused on code-based development not dictated by corporate pragmatic decisions alone..<br>
<br></div><div class="gmail_default" style="font-size:large">we can start with a BitBucket or a GitHub repository to rehabilitate the OpenSolaris code and compile all significant improvements and replacements with minimal code-slashing and considerable code-review, this can be done incrementally<br>
</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Sincerely yours,<br><br></div><div class="gmail_default" style="font-size:large">Seth Nimbosa, your Brother and Comrade-in-Arms<br>
</div><div class="gmail_default" style="font-size:large"><div class="gmail_default" style="font-size:large;display:inline"></div><font size="1"><a href="http://twitter.com/nimbosa" target="_blank">http://twitter.com/nimbosa</a><br>
<a>FB.com/nimbosa</a></font><br>
<br clear="all"></div><div><div dir="ltr"><br><br> ---------- <font color="#ff0000" face="verdana, sans-serif" size="4"><b>* * *</b></font> ----------<br><br><font face="verdana, sans-serif"><i> Normal is getting dressed in clothes that you buy for work</i></font><div>
<font face="verdana, sans-serif"><i>and driving through traffic in a car that you are still paying for -</i></font></div><div><font face="verdana, sans-serif"><i>in order to get to the job you need to pay for the clothes and the car,<br>
and the house you leave vacant all day so you can afford to live in it. </i><br><br> - Ellen Goodman</font><br><br><br>____________________________________________________________<br><br><br><b style="line-height:normal;text-indent:0px;letter-spacing:normal;text-align:start;font-variant:normal;text-transform:none;font-style:normal;font-size:medium;white-space:normal;font-family:'Times New Roman';word-spacing:0px">Joerg Schilling</b><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;display:inline!important;font-weight:normal;float:none;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:'Times New Roman';word-spacing:0px"><span> </span></span><a href="mailto:oi-dev%40openindiana.org?Subject=Re%3A%20%5Boi-dev%5D%20oi_151a9%20roadmap%20%26%20planning&In-Reply-To=%3C5225a7ae.5JrfSQc1XVbnjQxv%25Joerg.Schilling%40fokus.fraunhofer.de%3E" title="[oi-dev] oi_151a9 roadmap & planning" style="font-family:'Times New Roman';font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank"><div class="gmail_default" style="font-size:large;display:inline">
</div>Joerg.Schilling at fokus.fraunhofer.de<span> </span></a><br style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:'Times New Roman';word-spacing:0px">
<i style="line-height:normal;text-indent:0px;letter-spacing:normal;text-align:start;font-variant:normal;text-transform:none;font-size:medium;white-space:normal;font-family:'Times New Roman';font-weight:normal;word-spacing:0px">Tue Sep 3 09:11:10 UTC 2013</i><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;display:inline!important;font-weight:normal;float:none;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:'Times New Roman';word-spacing:0px"></span><ul style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:'Times New Roman';word-spacing:0px">
<li>Previous message:<span> </span><a href="http://openindiana.org/pipermail/oi-dev/2013-September/002660.html" target="_blank">[oi-dev] oi_151a9 roadmap & planning</a></li><li>Next message:<span> </span><a href="http://openindiana.org/pipermail/oi-dev/2013-September/002661.html" target="_blank">[oi-dev] oi_151a9 roadmap & planning</a></li>
<li><b>Messages sorted by:</b><span> </span><a href="http://openindiana.org/pipermail/oi-dev/2013-September/date.html#2659" target="_blank">[ date ]</a><span> </span><a href="http://openindiana.org/pipermail/oi-dev/2013-September/thread.html#2659" target="_blank">[ thread ]</a><span> </span><a href="http://openindiana.org/pipermail/oi-dev/2013-September/subject.html#2659" target="_blank">[ subject ]</a><span> </span><a href="http://openindiana.org/pipermail/oi-dev/2013-September/author.html#2659" target="_blank">[ author ]</a></li>
</ul><hr style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:'Times New Roman';word-spacing:0px">
<pre style="line-height:normal;text-indent:0px;letter-spacing:normal;text-align:start;font-variant:normal;text-transform:none;font-style:normal;white-space:pre-wrap;font-weight:normal;word-spacing:0px">Ray Arachelian <<a href="http://openindiana.org/mailman/listinfo/oi-dev" target="_blank"><div class="gmail_default" style="font-size:large;display:inline">
</div>ray at arachelian.com</a>> wrote:
><i> > Since oi_151a9 was scheduled for release this month, some initial
</i>
Could someone explain why you udr 151a9?
- It is not based on onnv_151
- It is most likely not the 151th release for OI
- It is based like others on onnv_147+
><i> > thoughts:
</i>><i> >
</i>><i> > 1. bump illumos to b02c4a353739
</i>><i> > 2. bump oi-jds to ee8cf112eec2 (<a href="http://hg.opensolaris.cz/oi-jds" target="_blank">hg.opensolaris.cz/oi-jds</a>)
</i>><i> > 3. Nvidia 304.108 video driver
</i>><i> > 4. Xnv_161 integration (Alasdair ?)
</i>><i> >
</i>><i> Can we add USB 3.0 support, and SATA 6GB support? Please?
</i>
I am not sure whether you are aware about the fact that OpenSoaris has few
contributors and that Illumos is trying to frighten developers by not being a
sure partner you may trust.
Promising to include software causes people to spend time in creating a webrev,
but later not doing a code review causes at least this time to be wasted. This
finally ends up in not fulfilling a commitment and is toxic for Illumos
credibility.
Adding code with known bugs to Illumos even though it did not pass a
codereview, just because the code is from an animal that is more equal
than others destroys credibility.
Illumos also drives in a direction that is not what I understand by going the
Solaris (UNIX) way. Code is removed just because it is not of interest for
Nexenta or Joyent, continuing this way will at some time lower attractivity.
Ripping off troff from man(1) because "col -x" (as a result from a buggy
localization software in Illumos) does not pass japanese characters is a
strange response to a problem.
While points 1..4 are decisions that can be made by OI, your proposal is not
leading to a decision that could be made by OI.
You may hope that this at some time is handled by Illumos, but Illumos does not
cover all the skills that are needed. So my question to other OI members is:
are you 100% bound to Illumos?
I am currently underway with finishing the package collection for SchilliX
based on network loadable Svr4 packages that I made basically working in
February 2011. Now that SchilliX collects helpers, we expect to be in a state
to deliver a full desktop in a few weeks. After that, I will start to work
again on the OpenSolaris code base. As mentioned, a toxic person prevents
Illumos from being interested in collaboration, so we either end up in a
tattered OpenSolaris landscape or we find a way to pool changesets and let
distros decide how to compose their OpenSolaris base.
Are you interested in collaboration?
If yes, do you have an idea how this could be done?
Jörg
--
EMail:<a href="http://openindiana.org/mailman/listinfo/oi-dev" target="_blank"><div class="gmail_default" style="font-size:large;display:inline"></div>joerg at schily.isdn.cs.tu-berlin.de</a> (home) Jörg Schilling D-13353 Berlin
<a href="http://openindiana.org/mailman/listinfo/oi-dev" target="_blank"><div class="gmail_default" style="font-size:large;display:inline"></div>js at cs.tu-berlin.de</a> (uni)
<a href="http://openindiana.org/mailman/listinfo/oi-dev" target="_blank">joerg.schilling at fokus.fraunhofer.de</a> (work) Blog: <a href="http://schily.blogspot.com/" target="_blank"><div class="gmail_default" style="font-size:large;display:inline">
</div>http://schily.blogspot.com/</a>
URL: <a href="http://cdrecord.berlios.de/private/" target="_blank">http://cdrecord.berlios.de/private/</a> <a href="ftp://ftp.berlios.de/pub/schily" target="_blank">ftp://ftp.berlios.de/pub/schily</a>
<br>__________________________________<br><br><br>Gary Driggs <<a href="mailto:gdri...@gmail.com">gdri...@gmail.com</a>> wrote:
> On Aug 3, 2013, at 3:08 AM, Joerg Schilling wrote:
>
> It seems that we need to set up some kind of register about who is working
> on what for OpenSolaris
>
>
> Something more detailed than this?
> <a rel="nofollow" href="http://wiki.illumos.org/display/illumos/Distributions">http://wiki.illumos.org/display/illumos/Distributions</a>
</pre><div class="">
</div>
Sure!<br><br>This also does not seem to be correct, as it lists OnmiOS as an Illumos based <br>distro, but is this was true, Omnios did just have a broken od implementation <br>in /usr/bin instead of no od implementation.<br>
<br>As mentioned several times before, in November 2010, Illumos decided not to <br>collaborate with other developers and in addition ignored a rejected code <br>review for a broken od implementation that in turn was added to the illumos <br>
code base despite a known list of several bugs.<br><br>For this reasons, illumos failed to become the community OpenSolaris successor.<br>There are several similar disjunct continuation projects with different goals. <br>
<br>SchilliX-ON exists since Garret DAmore made obvious that he is not willing to <br>collaborate and after he added his buggy od.c sourcecode. SchilliX-ON among <br>others supports compressed SVr4 packages that can be directly installed from <br>
the network for Intel and Sparc since February 2011.<br><br>What OpenSolaris needs is a list of development activities that would allow <br>people to know what other people do and what probably could be taken from <br>others.<br>
<br><div class="gmail_default" style="font-size:large;display:inline"></div>Jörg<br><br>-- <br> <a href="mailto:EMail%3Ajo...@schily.isdn.cs.tu-berlin.de">EMail:jo...@schily.isdn.cs.tu-berlin.de</a> (home) <div class="gmail_default" style="font-size:large;display:inline">
</div>Jörg Schilling D-13353 Berlin<br> <a href="mailto:j...@cs.tu-berlin.de">j...@cs.tu-berlin.de</a> (uni) <br> <a href="mailto:joerg.schill...@fokus.fraunhofer.de">joerg.schill...@fokus.fraunhofer.de</a> (work) Blog: <br>
<a href="http://schily.blogspot.com/">http://schily.blogspot.com/</a><br> URL: <a href="http://cdrecord.berlios.de/private/">http://cdrecord.berlios.de/private/</a> <a href="ftp://ftp.berlios.de/pub/schily">ftp://ftp.berlios.de/pub/schily</a><br>
<br></div></div></div>
</div>