[oi-dev] oi_151a9 roadmap & planning

[ken mays]

Joerg,

Just because I originated this thread...

oi_151a was based on a snapshot of the original 'snv_151' consolidation branches - excluding the 'fully closed' changesets for ON_151 (and other closed 'snv_151' binaries and IP) - predating the 'Solaris 11 Express' release.


You now have a hybrid or moreso - a spork based on specific collaborative efforts and backports.


The Illumos effort is only a 'kernel-based' code drop based on the ON_147 snapshot. What a distro provider implements for their distro is not a consideration of Illumos as a whole. A provider can maintain the original kernel source and cherrypick changesets from the Illumos project - or any other project - to enhance the kernel or distro in its entirety.

Are we still of a mindset that a little leaven leaveneth the whole lump? Some would say to 'pluck out' that which offends you and utilize the good parts. For others, toss out the whole thing into the abyss... and use something else...


The people/businesses that use Illumos use this model to accept changesets into their own distros. I can only grasp that you may want to do the same.


~ Ken Mays

P.S. (off topic) - Alcohol is a multipurpose poisonous drug consumed and accepted by BILLIONS of people. Therefore, some poisons are both good and bad - it just depends on the 'when and how' upon application...





________________________________
 From: Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de>
To: oi-dev at openindiana.org 
Sent: Tuesday, September 3, 2013 5:11 AM
Subject: Re: [oi-dev] oi_151a9 roadmap & planning
 

Ray Arachelian <ray at arachelian.com> wrote:

> > Since oi_151a9 was scheduled for release this month, some initial

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+

> > thoughts:
> >
> > 1. bump illumos to b02c4a353739 
> > 2. bump oi-jds to ee8cf112eec2 (hg.opensolaris.cz/oi-jds)
> > 3. Nvidia 304.108 video driver 
> > 4. Xnv_161 integration (Alasdair ?)
> >
> Can we add USB 3.0 support, and SATA 6GB support? Please?

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:joerg at schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
      js at cs.tu-berlin.de                (uni)  
      joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20130903/f324c2a6/attachment-0005.html>