-
Notifications
You must be signed in to change notification settings - Fork 4
/
proposal-goose-project-to-join-ascendos.html
91 lines (81 loc) · 5.29 KB
/
proposal-goose-project-to-join-ascendos.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
<!DOCTYPE html>
<html lang="en">
<head>
<title>The GoOSe Project — Proposal: GoOSe Project to join AscendOS</title>
<meta charset="utf-8" />
<link rel="profile" href="http://gmpg.org/xfn/11" />
<link rel="stylesheet" type="text/css" href="./theme/css/style.css" />
<link rel='stylesheet' id='oswald-css' href='http://fonts.googleapis.com/css?family=Oswald&ver=3.3.2' type='text/css' media='all' />
<style type="text/css">
body.custom-background { background-color: #f5f5f5; }
</style>
<link rel="alternate" type="application/atom+xml"
title="The GoOSe Project — Flux Atom"
href="./" />
<!--[if lte IE 8]><script src="./theme/js/html5shiv.js"></script><![endif]-->
</head>
<body class="home blog custom-background " >
<div id="container">
<div id="header">
<h1 id="site-title"> <a href=".">The GoOSe Project</a> <img src="./theme/images/goose-logo.png" /></h1>
<h2 id="site-description">A Community Enterprise Linux Rebuild</h2> </div><!-- /#banner -->
<div id="menu">
<div class="menu-navigation-container">
<ul id="menu-navigation" class="menu">
<li class="menu-item menu-item-type-post_type menu-item-object-page"><a href="./about.html">About</a></li>
<li class="menu-item menu-item-type-post_type menu-item-object-page"><a href="./community.html">Community</a></li>
<li class="active" class="menu-item menu-item-type-post_type menu-item-object-page"><a href="downloads.html">Download</a></li>
<li class="active" class="menu-item menu-item-type-post_type menu-item-object-page"><a href="news.html">News</a></li>
</ul>
</div> <!--/#menu-navigation-container-->
</div><!-- /#menu -->
<div class="page-title">
</div>
<div id="contents">
<div class="post type-post status-publish format-standard hentry category-general" id="post">
<div class="entry-meta">
<div class="date"><a href="./proposal-goose-project-to-join-ascendos.html">Thu 09 January 2014</a></div>
<span class="byline">By <a href="./author/clint-savage-herlo.html">Clint Savage (herlo)</a></span>
</div> <!-- /#entry-meta -->
<div class="main">
<h2 class="entry-title">
<a href="./proposal-goose-project-to-join-ascendos.html" title="Permalink to Proposal: GoOSe Project to join AscendOS" rel="bookmark">Proposal: GoOSe Project to join AscendOS</a>
</h2>
<div class="entry-content">
<p>This past Tuesday, January 7, Red Hat and CentOS announced jointly a new CentOS community. This community appears to allow CentOS use Red Hat's resources, to create a new and more expansive community. As you can understand, this may cause some concern, excitement and confusion among the existing EL rebuild communities.</p>
<p>After a rousing meeting today, there is some new movement inside of the GoOSe Project. It appears that due to the changes Red Hat and CentOS announced, it makes sense for there to be a new Special Interest Groups (SIGs) within the newly defined CentOS community. However, there are some external components as well.</p>
<div class="section" id="continuity-sig">
<h2>Continuity SIG</h2>
<p>The goals of the Continuity SIG would be as follows:</p>
<ul class="simple">
<li>Be able to take the SRPMs/SPECs as they were provided from upstream and rebuild without the CentOS infrastructure.</li>
<li>Document the process of tooling a rebuild.</li>
<li>Provide feedback and report bugs to ensure upstream improves packaging, QA, ISO building, etc.</li>
</ul>
</div>
<div class="section" id="ascendos-isos">
<h2>AscendOS ISOs</h2>
<p>In addition to the Continuity SIG described above, it seemed obvious that there is still a desire to keep a separate release. Because CentOS is now a Red Hat community project, it is important that there be a distribution that stands completely on its own, independent of the RHEL/CentOS buils. To accomplish the goals of the Continuity SIG, AscendOS ISOs will be generated for each major and minor release.</p>
</div>
<div class="section" id="mothballing-the-goose-project">
<h2>Mothballing The GoOSe Project</h2>
<p>As part of this effort, the GoOSe Project will retire its workload. Closing down its koji instance and a few other resources. Continuing on will be the github repositories, lookaside cache, documentation and this website. Each service will be evaluated to see which would work best.</p>
<p>There will be links pointing to the AscendOS project as our new base of operations.</p>
</div>
<div class="section" id="questions-and-comments">
<h2>Questions and Comments</h2>
<p>Because this is just a proposal, another meeting will be held to better define this proposal and clean up any language, descriptions and goals. An announcement will be made on the GoOSe Project mailing list as well as the AscendOS mailing list. Please drop by #gooseproject or #ascendos on irc.freenode.net if you have input or would like to discuss any of this proposal.</p>
<p>Cheers!</p>
<p>herlo</p>
</div>
</div> <!--/#entry-content-->
</div> <!--/#main-->
</div> <!--/#post-->
</div>
<div id="footer">
<p>Powered by <a href="http://pelican.readthedocs.org">Pelican</a>.</p>
</div><!-- /#footer -->
</div><!-- /#container -->
<div style="display:none"></div>
</body>
</html>