Hi,

Here's OpenSolaris Weekly News #9. As always feedback, or content [from
the missing represented communities] welcome.

Glynn

==

Jim Grisanzio posted [1] the meeting minutes of the latest OGB call, where
they discussions issues among others on project creation and naming, mailing 
list
management, and governance.

1. 
http://mail.opensolaris.org/mailman/private/cab-discuss/2006-April/000338.html

Phil Coleman asked [2] if it was possible to print out meaningful descriptions
from the errno variable in DTrace. Bryan Cantrill replied [3] that this had not 
yet been implemented as it overcrowded the printf format character. Both Jarod 
Jenson and Brendan Gregg followed up with their own cheesy [4] hacks [5]. Cheese
was also a theme when Dan Mick asked [6] if it was possible to list available
DTrace providers - suffice to say, it was logged as an RFE.

2. http://mail.opensolaris.org/pipermail/dtrace-discuss/2006-April/001466.html
3. http://mail.opensolaris.org/pipermail/dtrace-discuss/2006-April/001468.html
4. http://mail.opensolaris.org/pipermail/dtrace-discuss/2006-April/001471.html
5. http://mail.opensolaris.org/pipermail/dtrace-discuss/2006-April/001479.html
6. http://mail.opensolaris.org/pipermail/dtrace-discuss/2006-April/001484.html

Chris Quenelle asked [7] for feedback on how Sun Studio might be properly
integrated into Solaris, based on thoughts he laid out in his blog [8]. Keith
Wesolowski argued [9] that if each release wasn't a major one, breaking
compatability, it would much easier to release and integrate it synchronously 
with the core operating system. Ian Collins pointed out [10] that gcc was
already currently installed by default, and that the Studio team should aim 
for a similar goal. Chris followed up [11] pointing out some inconsistency
with integration points, along with a request for pointers to configuration
scripts which are expected to work with all Studio products.

7.  http://mail.opensolaris.org/pipermail/tools-discuss/2006-April/000403.html
8.  
http://blogs.sun.com/roller/page/quenelle?entry=sun_studio_and_solaris_integration
9.  http://mail.opensolaris.org/pipermail/tools-discuss/2006-April/000410.html
10. http://mail.opensolaris.org/pipermail/tools-discuss/2006-April/000413.html
11. http://mail.opensolaris.org/pipermail/tools-discuss/2006-April/000423.html

Eric Lowe announced [12] the start of the Muskoka project, an open repository
for technical content, with the intention that all technical discussion should
be directed at the moderated opensolaris-code list [13]. Dave Miner 
proposed [14] the Live Media project, to support the creation of OpenSolaris 
distributions which run well on CD, DVD, or flash memory devices. Jim 
Grisanzio mailed [15] with the current list of proposed communities and 
projects, asking for updates on their progress.

12. 
http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-April/000121.html
13. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-April/015593.html
14. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-April/015637.html
15. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-April/015585.html

Jim Grisanzio followed up [16] with a wiki link [17] for the Google Summer of 
Code
and a request that project ideas should be added to that page.

16. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-April/015614.html
17. http://www.genunix.org/wiki/index.php/Summer_of_Code

Erast Benson suggested [18] the use of Launchpad [19] as a way to share 
resources
involved in OpenSolaris and related development, including bug tracking, project
management, and bounties. Moinak Ghosh replied [20] with an agreement that there
may be many areas of collaboration, and registered BeleniX.

18. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-April/015569.html
19. http://www.launchpad.net/
20. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-April/015627.html


_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to