- Start building the 2014Q1 status report with a report on Chromium
Submitted by: rene
This commit is contained in:
parent
aaa88f895a
commit
41d58f222b
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=44348
2 changed files with 93 additions and 0 deletions
|
@ -64,6 +64,7 @@ XMLDOCS+= report-2013-05-devsummit
|
|||
XMLDOCS+= report-2013-07-2013-09
|
||||
XMLDOCS+= report-2013-09-devsummit
|
||||
XMLDOCS+= report-2013-10-2013-12
|
||||
XMLDOCS+= report-2014-01-2014-03
|
||||
|
||||
XSLT.DEFAULT= report.xsl
|
||||
|
||||
|
|
|
@ -0,0 +1,92 @@
|
|||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" "http://www.FreeBSD.org/XML/share/xml/statusreport.dtd" >
|
||||
<!-- $FreeBSD$ -->
|
||||
<report>
|
||||
<date>
|
||||
<month>January-March</month>
|
||||
|
||||
<year>2014</year>
|
||||
</date>
|
||||
|
||||
<section>
|
||||
<title>Introduction</title>
|
||||
|
||||
<p>This report covers &os;-related projects between January and
|
||||
March 2014. This is the first of four reports planned for 2014.</p>
|
||||
|
||||
<!-- XXX: Add introduction -->
|
||||
|
||||
<!-- XXX: Keep the number of entries updated -->
|
||||
<p>Thanks to all the reporters for the excellent work! This report
|
||||
contains 1 entry and we hope you enjoy reading it.</p>
|
||||
|
||||
<p>The deadline for submissions covering between April and
|
||||
June 2014 is July 7th, 2014.</p>
|
||||
</section>
|
||||
|
||||
<category>
|
||||
<name>ports</name>
|
||||
|
||||
<description>Ports</description>
|
||||
</category>
|
||||
|
||||
<project cat='ports'>
|
||||
<title>Chromium</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
<name>Chromium on &os; Team</name>
|
||||
<email>freebsd-chromium@FreeBSD.org</email>
|
||||
</person>
|
||||
</contact>
|
||||
|
||||
<links>
|
||||
<url href="http://www.chromium.org/Home">Chromium website</url>
|
||||
<url href="https://github.com/gliaskos/freebsd-chromium">Development repository on GitHub</url>
|
||||
<url href="https://wiki.freebsd.org/Chromium">Chromium on &os; wiki</url>
|
||||
</links>
|
||||
|
||||
<body>
|
||||
<p>Over the last four years the Chromium team has been busy with
|
||||
porting Chromium to &os;. This involves patching the browser so
|
||||
that it runs on &os;, tracking and documenting security updates,
|
||||
and merging patches back upstream.</p>
|
||||
|
||||
<p>While there are already several browsers available for &os;,
|
||||
advantages of Chromium are:</p>
|
||||
|
||||
<ul>
|
||||
<li>Quick response from upstream to security issues, resulting
|
||||
in approximately bi-weekly updates.</li>
|
||||
|
||||
<li>A testbed for security features of &os;, like Capsicum.
|
||||
While support for this capability and sandbox framework is
|
||||
currently not included in the browser, a proof-of-concept
|
||||
implementation for an early version of Chromium was realized
|
||||
within a single weekend.</li>
|
||||
</ul>
|
||||
|
||||
<p>George Liaskos and &a.rene; are currently busy with submitting
|
||||
the remaining patches specific to &os; back upstream. Apart from
|
||||
making future updates easier, it sometimes also improves the
|
||||
overall code quality.</p>
|
||||
|
||||
<p>&a.jonathan; recently updated the Capsicum patches for Chromium
|
||||
and is talking to upstream about them.</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
<task>Advocate &os;. While patches are getting accepted by both
|
||||
humans and bots, it is not an official platform so attitude varies
|
||||
from developer to developer. While &a.rene; thinks it is a bit
|
||||
early, it might be fruitful to investigate what is required to
|
||||
make &os; (and possibly OpenBSD) an official platform in terms
|
||||
of both hardware and procedures.</task>
|
||||
|
||||
<task>If you feel comfortable with large source trees, you can try
|
||||
to build the Git version of Chromium on &os;. If you are also
|
||||
comfortable with signing Googles Contributor License Agreement,
|
||||
you can join testing and submitting patches upstream.</task>
|
||||
</help>
|
||||
</project>
|
||||
</report>
|
Loading…
Reference in a new issue