os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add GNOME, Xorg, ZFSGuru, and Python reports.

Browse source
This commit is contained in:
Warren Block 2014-10-07 22:24:47 +00:00
parent 430d51715b
commit d50526cd99
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=45740
1 changed files with 242 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

243
en_US.ISO8859-1/htdocs/news/status/report-2014-07-2014-09.xml
View file

@ -607,7 +607,7 @@
distro based on mfsbsd. After boot fai looks for
"bootfile-name" parameter from DHCP server which tell fai
where bsdinstall script located is. Fai supports mac-based
config or default, if mac-based file doesn't exist.</p>
config or default, if mac-based file does not exist.</p>
</body>
<sponsor>
@ -622,4 +622,245 @@
</task>
</help>
</project>
<project cat='ports'>
<title>GNOME/FreeBSD</title>
<contact>
<person>
<name>
<common>FreeBSD GNOME Team </common>
</name>
<email>gnome@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://www.freebsd.org/gnome" />
<url href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" />
<url href="http://marcuscom.com/downloads/marcusmerge" />
</links>
<body>
<p>GNOME is a desktop environment and graphical user interface
that runs on top of a computer operating system. GNOME is part
of the GNU Project and can be used with various Unix-like
operating systems, including FreeBSD.</p>
<p>The MATE ports were updated to the 1.8 versions.</p>
<p>Now that cairo was updated to 1.12 the merge of GNOME 3 has
started. Currently we are doing test builds to find ports
broken by the update and pruning ports that do not build
any more because of incompatible updates.</p>
<p>Gustau Perez started preliminary work on the next development
version of GNOME in MC, to be ready for GNOME 3.15. We will
skip 3.14 entirely.</p>
</body>
<help>
<task>
Finish GNOME 3.12 merge, and start tracking GNOME 3.15
(development series).
</task>
</help>
</project>
<project cat="ports">
<title>The Graphics Stack on &os;</title>
<contact>
<person>
<name>
<common>FreeBSD Graphics team</common>
</name>
<email>x11@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</url>
<url href="http://trillian.chruetertee.ch/ports/browser/trunk">Graphics stack ports-related development repository</url>
<url href="http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-October/000096.html">Removal of legacy X.Org announcement</url>
<url href="http://wiki.x.org/wiki/Events/XDC2014/">XDC 2014</url>
</links>
<body>
<p>The newest graphics stack (that is, ports behind the
WITH_NEW_XORG knob) was enabled on all architectures. The
only regression is for users of Intel GPUs and &os; 8.X or
9.0. Those releases lack the required kernel driver and
therefore <tt>xf86-video-intel</tt> will not work (the last
UMS-aware version does not work with xserver 1.12). Users can
still use <tt>xf86-video-vesa</tt> if they cannot or do not
want to update their &os; workstation. Owners of Radeon GPUs
can use <tt>xf86-video-ati-ums</tt> 6.14.6 with
<tt>xserver</tt> 1.12 if the KMS driver is not available (that
is, before FreeBSD 9.3).</p>
<p>The old graphics stack will be removed with the next update
to these ports. See the announcement in the Links
section.</p>
<p>Hardware context support was added to the i915 driver in both
HEAD and 10.1-RELEASE. This will allow us to update libglapi,
libGL, dri, libEGL and libglesv2 ports to a newer version of
Mesa. The latest version is already available from our
development ports tree (see the links section).</p>
<p>Cairo was updated to 1.12. This will allow the FreeBSD GNOME
team to upgrade pango and Gtk+ 3. Unfortunately, the update
also revealed that xf86-video-intel 2.7.1 was in a much worse
state than previously assumed.</p>
<p>We will attend XDC 2014 (X.Org Developer's Conference) from
October 8th through 10th in Bordeaux, France. The goal is to
reconnect with graphics stack developers, mostly working with
Linux these days. We will give a presentation on the current
state of this stack on &os;. See the XDC website in the Links
section for the program and live streaming.</p>
</body>
<help>
<task>
See the "Graphics" wiki page for up-to-date information.
</task>
</help>
</project>
<project cat='proj'>
<title>ZFSGuru</title>
<contact>
<person>
<name>
<given>Jason</given>
<common>Edwards</common>
</name>
<email>sub.mesa@gmail.com</email>
</person>
</contact>
<links>
<url href="http://zfsguru.com" />
<url href="http://zfsguru.com/news/stateoftheproject/2014" />
<url href="http://zfsguru.com/forum/zfsgurudevelopment/876" />
</links>
<body>
<p>ZFSguru is a multifunctional server appliance with a strong
emphasis on storage. ZFSguru began as simple web-interface
frontend to ZFS, but has since grown into a &os; derivative
with its own infrastructure. The scope of the project has
also grown with the inclusion of add-on packages that add
functionality beyond the traditional NAS functionality found
in similar product like FreeNAS and NAS4Free. ZFSguru aims to
be a true multifunctional server appliance that is extremely
easy to set up and can unite both novice and more experienced
users in a single user interface. The modular nature of the
project combats the danger of bloat, whilst still allowing
extended functionality to be easily deployed.</p>
<p>The development work in Q3 focused heavily on the new build
infrastructure. This allows the ZFSguru project to release
new system images together with addon services at much higher
frequency and with much less manual intervention. This should
free up a lot of development time to be spent on the core of
the project: the web-interface.</p>
<p>Furthermore, a new website and forum is being worked at,
replacing the old-fashioned website that offers only limited
functionality. The new website will be linked to the server
database, providing real-time updates about the project.</p>
<p>In addition, a new platform for collaborated development is
in the works. A service addon has been created for the GitLab
project, which is a drop-in replacement of the popular GitHub
website. The choice was made to host our own solution and not
rely on GitHub itself. In retrospect this appears to have
been a good decision. The recent development where GitHub
removed projects after DCMA-takedowns being sent is
incompatible with the philosophy of free-flow-of-information,
of which the ZFSguru project is a strong proponent. By
hosting our own solution, we have avoided any dependency on
third party projects.</p>
<p>The next task will be to introduce a new remote database
structure, dubbed GuruDB. This will speed up the
web-interface as well as introduce Service Bulletins which
address important notifications to our users, as well as
announce new releases.</p>
<p>After GuruDB, the Migration Manager is one of the last
remaining features still missing in the web-interface. This
functionality provides an easy way to upgrade the current
system by performing a new clean installation, but migrate all
relevant configuration to the new installation. It also
allows users to 'backup' all system configuration in a single
file to be stored on a different machine should things go
awry.</p>
<p>A longer version of the 2014 development progress of the
ZFSguru project and information specific to the newly-released
10.1-002 system image can be found in the Links section.</p>
</body>
</project>
<project cat='ports'>
<title>FreeBSD Python Ports</title>
<contact>
<person>
<name>
<given>FreeBSD</given>
<common>Python Team</common>
</name>
<email>python@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="https://wiki.FreeBSD.org/Python">The FreeBSD Python Team Page</url>
<url href="irc://freebsd-python@irc.freenode.net">IRC channel</url>
</links>
<body>
<p>The FreeBSD Python team continued to improve the overall
experience with Python-based software on FreeBSD.</p>
<p>During the last quarter, the <tt>bsd.python.mk</tt> bits of
the ports infrastructure were converted to the more modern
<tt>USES</tt> format. Several options, such as support for
<tt>easy_install</tt>, were deprecated or removed to make the
infrastructure easier to maintain and less complex for
maintainers.</p>
<p>The Python ports were refactored and simplified to improve
maintenance and to get rid of long-standing issues due to the
previously complex and error-prone build process.</p>
<p>The Python 2 branch was updated to Python 2.7.8 and
<tt>setuptools</tt> to 5.5.1.</p>
<p>With the availability of pkg 1.3, installing Python packages
and modules for different Python versions is now supported in
the package management infrastructure. This allows us to
remove the previously required port duplicates for Python 2
and Python 3.</p>
</body>
<help>
<task>Retire the Python 3 specific port duplicates</task>
<task>Convert ports to the new <tt>USES</tt> syntax</task>
<task>More tasks can be found on the team's wiki page (see
Links).</task>
<task>To get involved, interested people can say hello on IRC
and let us know their areas of interest!</task>
</help>
</project>
</report>