celix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pnol...@apache.org
Subject [3/3] celix-site git commit: Updates CMS system to Hugo
Date Tue, 26 Jun 2018 19:12:25 GMT
Updates CMS system to Hugo


Project: http://git-wip-us.apache.org/repos/asf/celix-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/celix-site/commit/d212e764
Tree: http://git-wip-us.apache.org/repos/asf/celix-site/tree/d212e764
Diff: http://git-wip-us.apache.org/repos/asf/celix-site/diff/d212e764

Branch: refs/heads/asf-site
Commit: d212e76484d974b3afee61b07222c7857a34c520
Parents: 38b596b
Author: Pepijn Noltes <pepijnnoltes@gmail.com>
Authored: Tue Jun 26 21:11:41 2018 +0200
Committer: Pepijn Noltes <pepijnnoltes@gmail.com>
Committed: Tue Jun 26 21:11:41 2018 +0200

----------------------------------------------------------------------
 .gitmodules                                     |   3 -
 README.md                                       |  32 +-
 archetypes/default.md                           |  22 +
 build.py                                        | 166 -------
 celix                                           |   1 -
 config.toml                                     |   5 +
 content/_index.html                             |  35 ++
 content/community/boardreports.md               | 464 +++++++++++++++++++
 content/community/contributing.md               |  27 ++
 content/community/index.md                      |  34 ++
 content/community/releasing.md                  | 233 ++++++++++
 content/downloads/index.md                      |  50 ++
 content/support/_index.md                       |  22 +
 content/support/issuetracking.md                |  38 ++
 content/support/mailinglist.md                  |  41 ++
 docTableIndex.xml                               |  28 --
 src/bottom.html                                 |   6 -
 src/markdown/boardreports.md                    | 445 ------------------
 src/markdown/community.md                       |  14 -
 src/markdown/contributing.md                    |   8 -
 src/markdown/downloads.md                       |  30 --
 src/markdown/index.md                           |  17 -
 src/markdown/issuetracking.md                   |  16 -
 src/markdown/mailinglist.md                     |  19 -
 src/markdown/releasing.md                       | 214 ---------
 src/markdown/support.md                         |  10 -
 src/noprocess/favicon.ico                       | Bin 2082 -> 0 bytes
 src/noprocess/import/friendly.css               |  69 ---
 src/noprocess/import/javascript.js              |  16 -
 src/noprocess/import/style.css                  | 368 ---------------
 src/noprocess/media/Apache_Feather.png          | Bin 1994 -> 0 bytes
 src/noprocess/media/Apache_Feather.svg          |  88 ----
 src/noprocess/media/Apache_PoweredBy.png        | Bin 72953 -> 0 bytes
 src/noprocess/media/Apache_full.png             | Bin 5144 -> 0 bytes
 src/noprocess/media/Apache_full.svg             | 125 -----
 src/noprocess/media/Chevron.gif                 | Bin 121 -> 0 bytes
 src/noprocess/media/ChevronOverlay.png          | Bin 310 -> 0 bytes
 src/noprocess/media/IconHome.gif                | Bin 549 -> 0 bytes
 src/noprocess/media/celix.png                   | Bin 9225 -> 0 bytes
 src/noprocess/media/celix_notext.png            | Bin 25443 -> 0 bytes
 src/noprocess/media/celix_notext_20px.png       | Bin 2082 -> 0 bytes
 src/noprocess/media/forkmeongithub.png          | Bin 9438 -> 0 bytes
 src/noprocess/media/forkmesmall.png             | Bin 6982 -> 0 bytes
 src/noprocess/media/githubIcon.png              | Bin 4701 -> 0 bytes
 src/noprocess/media/memory_pools.png            | Bin 74273 -> 0 bytes
 src/noprocess/media/shadow.png                  | Bin 1698 -> 0 bytes
 src/noprocess/media/shiro_bullet_24x24.png      | Bin 1645 -> 0 bytes
 src/top.html                                    | 100 ----
 themes/celix/layouts/404.html                   |   0
 themes/celix/layouts/_default/baseof.html       |  55 +++
 themes/celix/layouts/_default/list.html         |  25 +
 themes/celix/layouts/_default/single.html       |  19 +
 themes/celix/layouts/index.html                 |   3 +
 .../celix/layouts/partials/top_level_menu.html  |  88 ++++
 themes/celix/static/favicon.ico                 | Bin 0 -> 2082 bytes
 themes/celix/static/import/friendly.css         |  85 ++++
 themes/celix/static/import/javascript.js        |  32 ++
 themes/celix/static/import/style.css            | 384 +++++++++++++++
 themes/celix/static/media/Apache_Feather.png    | Bin 0 -> 1994 bytes
 themes/celix/static/media/Apache_Feather.svg    |  88 ++++
 themes/celix/static/media/Apache_PoweredBy.png  | Bin 0 -> 72953 bytes
 themes/celix/static/media/Apache_full.png       | Bin 0 -> 5144 bytes
 themes/celix/static/media/Apache_full.svg       | 125 +++++
 themes/celix/static/media/Chevron.gif           | Bin 0 -> 121 bytes
 themes/celix/static/media/ChevronOverlay.png    | Bin 0 -> 310 bytes
 themes/celix/static/media/IconHome.gif          | Bin 0 -> 549 bytes
 themes/celix/static/media/celix.png             | Bin 0 -> 9225 bytes
 themes/celix/static/media/celix_notext.png      | Bin 0 -> 25443 bytes
 themes/celix/static/media/celix_notext_20px.png | Bin 0 -> 2082 bytes
 themes/celix/static/media/forkmeongithub.png    | Bin 0 -> 9438 bytes
 themes/celix/static/media/forkmesmall.png       | Bin 0 -> 6982 bytes
 themes/celix/static/media/githubIcon.png        | Bin 0 -> 4701 bytes
 themes/celix/static/media/memory_pools.png      | Bin 0 -> 74273 bytes
 themes/celix/static/media/shadow.png            | Bin 0 -> 1698 bytes
 .../celix/static/media/shiro_bullet_24x24.png   | Bin 0 -> 1645 bytes
 75 files changed, 1885 insertions(+), 1765 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/.gitmodules
----------------------------------------------------------------------
diff --git a/.gitmodules b/.gitmodules
deleted file mode 100644
index 0e2e52d..0000000
--- a/.gitmodules
+++ /dev/null
@@ -1,3 +0,0 @@
-[submodule "celix"]
-	path = celix
-	url = git://git.apache.org/celix.git

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index 119540e..c8f140c 100644
--- a/README.md
+++ b/README.md
@@ -1,35 +1,23 @@
 # Apache Celix website
 
+The update celix website is still under construction and not yet live.
+
 This is the website for [Apache Celix](https://celix.apache.org/), hosted at:
 
     https://celix.apache.org/
 
-### Repository Structure
+## Content Management System
 
-This repository contains:
+The Celix website uses the Hugo content management system. See [Hugo](https://gohugo.io) for more info and for details how to install hugo
 
-1. `src/`: the source of the site, including markdown files containing the bulk of the content
-1. `build.py`: generates `site/` directory, which contains the celix website
-1. `celix/`: the celix sourcecode
+## Run the website locally
 
-### Cloning this repo
-This repository can be cloned as usual. Because the website is using the offical celix repository as submodule, some extra commands need to be executed. Run this after cloning and the 'celix' directory will be initialized:
-```bash
-$ git submodule init
-$ git submodule update
-```
+On the root dir, run: `hugo server -D`. The -D is provided to also host draft pages.
 
-More about submodules can be found [here](https://git-scm.com/book/en/v2/Git-Tools-Submodules)
+## Generate the status website
 
-# Server build instructions
+To generate the static website run: `hugo`. The resulting public dir should contain a updated static website.
 
-### building
-```bash
-cd path/to/build.py
-./build.py
-```
-A test-server will run on [localhost:8000](https://localhost:8000/)
+## Initialize celix git submodule
 
-### installing 
-1. install [python](https://www.python.org/) (tested versions: 2.7.10)
-1. install [markdown2](https://github.com/trentm/python-markdown2/blob/master/README.md#install)
+TODO

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/archetypes/default.md
----------------------------------------------------------------------
diff --git a/archetypes/default.md b/archetypes/default.md
new file mode 100644
index 0000000..67d0b89
--- /dev/null
+++ b/archetypes/default.md
@@ -0,0 +1,22 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+title: "{{ replace .Name "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+---
+

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/build.py
----------------------------------------------------------------------
diff --git a/build.py b/build.py
deleted file mode 100755
index 13f5f53..0000000
--- a/build.py
+++ /dev/null
@@ -1,166 +0,0 @@
-#!/usr/bin/env python
-
-#    Licensed to the Apache Software Foundation (ASF) under one or more
-#    contributor license agreements.  See the NOTICE file distributed with
-#    this work for additional information regarding copyright ownership.
-#    The ASF licenses this file to You under the Apache License, Version 2.0
-#    (the "License"); you may not use this file except in compliance with
-#    the License.  You may obtain a copy of the License at
-#
-#       http://www.apache.org/licenses/LICENSE- 2.0
-#
-#    Unless required by applicable law or agreed to in writing, software
-#    distributed under the License is distributed on an "AS IS" BASIS,
-#    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-#    See the License for the specific language governing permissions and
-#    limitations under the License.
-
-__author__ = "Edwin Smink"
-__copyright__ = "Copyright 2011 The Apache Software Foundation"
-__license__ = "Apache-2.0"
-__version__ = "1.0.0"
-
-import os, inspect, markdown2, shutil, sys, xml.etree.ElementTree as ET
-
-#define urls
-markdown = 'src/markdown'
-copy = 'src/noprocess'
-snippets = 'src'
-out = 'site'
-docIndex = 'docTableIndex.xml'
-
-#combines two paths to files from a common root directory
-#to a path from the parent directory of file one to file two
-def combinePaths(one, two):
-	if(one is two):
-		return ""
-	one = one.split('/')
-	two = two.split('/')
-	i = 0
-	segment = ""
-	#detect how much of the paths are equal then start writing the new path
-	while(len(one) > i and len(two) > i and one[i] == two[i]):i += 1
-	for x in one[i:-1]: segment += "../"
-	for x in two[i:]: segment += x + '/'
-	return segment[:-1]
-
-# tries removing all the ../ in a path
-def normalizePath(path):
-	path = path.split('/')
-	answer = ""
-	for x in path:
-		if(x == '..'):answer = answer[0:answer.rfind('/')]
-		else:answer += '/' + x
-	return answer[1:len(answer)]
-
-#copy to out
-if os.path.exists(out):
-	shutil.rmtree(out)
-shutil.copytree(copy, out)
-if not os.path.exists(out):
-	os.makedirs(out)
-
-# read index document
-root = ET.parse(docIndex).getroot()
-for title in root:
-	for fl in title:	
-		fl.append(ET.fromstring('<dest>' + out + '/doc/' + (title.attrib['name'] + '/' + fl.attrib['name']).replace(' ', '_') + '.html</dest>'))
-
-# create doctable
-docT = '<table id=docTable class=shadowed>'
-for title in root:
-	docT += '\n\t<tr><th>' + title.attrib['name'] + '</th></tr>'
-	for fl in title:
-		docT += '\n\t<tr><td><a href=/' + fl.find('dest').text[len(out) + 1:] + '>' + fl.attrib['name'] + '</a></td></tr>'
-docT = docT.replace('/index.html', '/') + '\n</table>\n'
-
-#register site markdown
-md = ''
-for f in os.listdir(markdown):
-	md += '<file><path>' + markdown + '/' + f + '</path><dest>site/' + f[:-3].replace(' ', '_') + '.html</dest></file>'
-root.append(ET.fromstring('<markdown>' + md + '</markdown>'))
-root.append(ET.fromstring('<importurl></importurl>'))
-
-imported = []
-for title in root:
-	for fl in title:
-		imported.append(fl.find('path').text)
-
-# write documents
-for title in root:
-	for fl in title:
-		try:os.makedirs(fl.find('dest').text[0:fl.find('dest').text.rfind('/')])
-		except: IOError
-		with open(fl.find('path').text) as f:file = f.read()
-		o = open(fl.find('dest').text, 'w')
-
-		# import url
-		i = 0
-		if(fl.find('dest').text.startswith('site/doc/')):
-			while True:
-				i = file.find('[', i)
-				if(i == -1):break
-				i2 = file.find('(', i)
-				if(i2 == -1):break
-				i3 = file.find(')', i2)
-				if(i3 == -1):break
-				if(file.find('\n', i, i3) != -1 or file.startswith('(http', i2)):
-					i += 3
-					continue
-
-				url = normalizePath(fl.find('path').text[fl.find('path').text.find('/'):fl.find('path').text.rfind('/') + 1] + file[i2 + 1:i3])
-				if('celix' + url not in imported):
-					imported.append('celix' + url)
-					# found new url
-					try:
-						with open('celix' + url) as src:
-							# add url to markdown processing
-							if(url[-3:len(url)] == '.md'):
-								root.find('importurl').append(ET.fromstring('<file><path>celix' + url + '</path><dest>site/doc/noIndex' + url[0:-3] + '.html</dest></file>'))
-								file = file[0:i2 + 1] + '/doc/noIndex' + url[0:-3] + '.html' + file[i3:len(file)]
-							# add url to files
-							else:
-								try:os.makedirs('site/doc/noIndex' + url[0:url.rfind('/')])
-								except: IOError
-								with open('site/doc/noIndex' + url, 'w') as dest:dest.write(src.read())
-								file = file[0:i2 + 1] + '/doc/noIndex' + url + file[i3:len(file)]
-					except IOError:
-						print('ERROR: could not find file: "celix' + url + '" referenced in file: ' + fl.find('path').text)
-				i = i3
-
-		# import other files
-		if fl.find('url'):
-			i = 0
-			url = fl.find('url').text.split('url')
-			while True:
-				i = file.find(url[0], i)
-				if(i == -1):break
-				i2 = file.find(url[1], i)
-				if(i2 == -1):break
-				f2 = open(key[:key.rfind('/') + 1] + file[i + len(url[0]):i2])
-				file = file[:i] + f2.read() + file[i2 + len(url[1]):]
-				f2.close()
-				i = i2 + 2
-
-			# correct markdown links
-			file = file.replace(combinePaths(fl.find('path').text,fl2.find('path').text), combinePaths(fl.find('dest').text, fl2.find('dest').text))
-
-		# convert markdown to html, also add top and bottom html files
-		file = markdown2.markdown(file, extras=["markdown-in-html", "break-on-newline", "fenced-code-blocks"])
-		if(title.tag != 'markdown'):
-				file = docT + '<div id=docContent>\n' + file + '\n</div>'
-		with open(snippets + '/top.html') as top:
-			file = top.read() + file
-		with open(snippets + '/bottom.html') as bottom:
-			file = file.encode('utf8') + bottom.read()
-
-		o.write(file)
-		o.close()
-
-# run test-server
-print('attempting to start a test-server on "http://localhost:8000/"')
-os.chdir(out)
-if sys.version_info[0] < 3:
-	os.system('python -m SimpleHTTPServer 8000')
-else:
-	os.system('python -m http.server 8000')

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/celix
----------------------------------------------------------------------
diff --git a/celix b/celix
deleted file mode 160000
index 95c06ab..0000000
--- a/celix
+++ /dev/null
@@ -1 +0,0 @@
-Subproject commit 95c06ab789fa82e8dbeccbad0324ec5d44437960

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/config.toml
----------------------------------------------------------------------
diff --git a/config.toml b/config.toml
new file mode 100644
index 0000000..221ff09
--- /dev/null
+++ b/config.toml
@@ -0,0 +1,5 @@
+baseURL = "http://celix.apache.org/"
+languageCode = "en-us"
+title = "Apache Celix"
+theme = "celix"
+

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/content/_index.html
----------------------------------------------------------------------
diff --git a/content/_index.html b/content/_index.html
new file mode 100755
index 0000000..a00a168
--- /dev/null
+++ b/content/_index.html
@@ -0,0 +1,35 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+---
+<div markdown='1' id="banner">
+<img class="bannerImage shadowed" src="/media/celix_notext.png">
+<div class="bannertext">
+<h1>Apache Celix</h1>
+Apache Celix is an implementation of the OSGi specification adapted to C and C++. It is a provides a framework to develop (dynamic) modular software applications using component and/or service-oriented programming.
+
+Apache Celix is primarily developed in C and adds an additional abstraction, in the form of a library, to support for C++.
+</div></div><div class="container"><div class="item">
+<h3>How to install</h3>
+</div><div class="item">
+<h3>Documentation</h3>
+</div><div class="item">
+<h3>Tips</h3>
+</div><div class="item">
+<h3>Contributing</h3>
+</div><iframe style="padding:0;height:250px;min-width:440px;max-width:500px;" class="item" src="http://tylerlh.github.io/github-latest-commits-widget/?username=Apache&repo=Celix&branch=develop&limit=15" scrolling="no" frameborder="0" allowtransparency="true">
+</iframe></div>

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/content/community/boardreports.md
----------------------------------------------------------------------
diff --git a/content/community/boardreports.md b/content/community/boardreports.md
new file mode 100644
index 0000000..042fcee
--- /dev/null
+++ b/content/community/boardreports.md
@@ -0,0 +1,464 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+title: Board Reports
+---
+# Board Reports
+
+To monitor incubator project, the Apache Software Foundation board holds monthly meetings.
+For these meetings a board report must be delivered to the Incubator PMC.
+
+On this page the reports for Celix are shown.
+
+## [2013-10](http://wiki.apache.org/incubator/October2013)
+
+= Celix =
+
+Celix is an OSGi like implementation in C with a distinct focus on interoperability between Java and C.
+
+Celix has been incubating since 2010-11-02.
+
+Three most important issues to address in the move towards graduation:
+
+  1. Grow the community
+  2. Find more committers
+  3. Publish a new release
+
+Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
+aware of?
+
+None
+
+How has the community developed since the last report?
+
+Several new people are working on additional code for the project. One person is working on a GSoC project, someone else is working on a new remote services protocol and is actively communicating over the list and using jira to post patches. Overall this is an increase in activity. 
+The Native-OSGi project is still progressing, but rather slow. So there isn't anything new on that end. Celix is still the reference implementation, so I still expect this to be a great drive for Celix, for the code as well as the committers.
+
+How has the project developed since the last report?
+
+As mentioned above, a student is working on a GSoC project and has implemented an Event Admin which will be included in Celix. Also a additional Remote Services implementation based on shared memory is being made.
+Work for a new release is still ongoing, the focus is slightly changing, one of the main users has requested a release. Since they don't use Win32, Win32 support can be stripped from the release plan and postponed to a later release.
+
+Date of last release: 
+
+  * 16-12-2012
+
+When were the last committers or PMC members elected?
+
+  * 2013-01-07 Roman Shaposhnik joins as a mentor.
+  * 2012-03-20 Pepijn elected as committer.
+
+## [2013-07](http://wiki.apache.org/incubator/July2013)
+
+= Celix =
+
+Celix is an OSGi like implementation in C with a distinct focus on interoperability between Java and C.
+
+Celix has been incubating since 2010-11-02.
+
+Three most important issues to address in the move towards graduation:
+
+  1. Grow the community
+  2. Find more committers
+  3. ...
+
+Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
+None.
+
+
+How has the community developed since the last report?
+Activity on the mailing list is still a bit slow, but there is still progress. But more importantly, the Native-OSGi effort has taken a few big steps. The most important one is the publication of an RFP at the OSGi Alliance [ 1 ]. The purpose of this RFP is to standardise OSGi for native (C and C++) languages. After the RFP is finalised work will be started on a RFC, this will be done in conjunction with writing a reference implementation. For this purpose Apache Celix will be used. This also means that C++ will be introduced in the Celix project. Most likely large parts of C++ code will be donated by 2 participants of the Native-OSGi project. This gives us a great opportunity to add extra committers and increase the diversity of Celix.
+
+How has the project developed since the last report?
+As mentioned above, to be able to write a reference implementation for Native-OSGi the scope of Celix will be extended to also include C++. Details of this extension still need to be worked out. But for continuity the current (C) code base will (for now) remain the same. So any work related to Native-OSGi will (for now) be done independently from the current implementation.
+Also work is underway to make a second release. Whereas the first release focused primarily on the releasing itself, this second release will focus on the actual implementation. Important points are:
+
+  * API consistency
+  * Win32 support
+  * APR usage
+
+More details can be found in [ 2 ]
+
+A (Mini) Hackathon for Apache Celix was organised at June the 30th. There where 4 people present on the hackathon (2 committers) and focus for the hackathon was the remote services implementation. The hackathon was received well and we like to do this more often to encourage community growth of Apache Celix.
+
+Apache Celix is now also involved the Google Summer of Code for 2013. Erik Jansman is doing a project on the Event Admin for Apache Celix and Pepijn Noltes is mentoring him. The idea is to discuss the result on the mailing list. This is a new experience for Apache Celix and we hope that helps the community and also provide technical progress.
+
+Date of last release: 
+16-12-2012
+
+[ 1 ] https://www.osgi.org/bugzilla/show_bug.cgi?id=165
+
+[ 2 ] http://incubator.markmail.org/thread/fza43iypjutcw2rm
+
+## [2013-04](http://wiki.apache.org/incubator/April2013)
+
+= Celix =
+
+Celix is an OSGi like implementation in C with a distinct focus on interoperability between Java and C.
+
+Celix has been incubating since 2010-11-02.
+
+Three most important issues to address in the move towards graduation:
+
+  1. Grow a community
+  2. Find more committers
+  3. ..
+
+Celix is maintained by 2 committers and a small group of users. Questions to the mailing list are (most of the time) answered quickly. We are also trying to give talks on Celix or related stuff on conferences.
+We see and recognise the problem of the small community, but are also confident that Celix and its community will grow. 
+
+Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
+None.
+
+How has the community developed since the last report?
+There is no active growth, but there is currently one students doing his intership with Apache Celix and we are trying hoping to get some projects in the Google Summer of Code 2013. We hope that this will lead in more activity on the mailing-list and hopefully to extra committers.
+
+How has the project developed since the last report?
+Technically progress has been slow the last months. There was a hackaton organized for remote services in Java [ 1 ], which although not directly related to Apache Celix, should eventually work together with the Apache Celix and as result the committers of Apache Celix where present. We also expect an increase in contributions the coming months because of the student intership / GSoC activities.
+
+[ 1 ] http://lists.amdatu.org/pipermail/dev/2013-March/000020.html
+
+## [2013-01](http://wiki.apache.org/incubator/January2013)
+
+= Celix =
+
+Celix is an OSGi like implementation in C with a distinct focus on interoperability between Java and C.
+
+Celix has been incubating since 2010-11-02.
+
+Three most important issues to address in the move towards graduation:
+
+  1. Grow a community
+  2. Find more committers
+  3. ..
+
+Celix is maintained by 2 committers and a small group of users. Questions to the mailing list are (most of the time) answered quickly. We are also trying to give talks on Celix or related stuff on conferences.
+We see and recognise the problem of the small community, but are also confident that Celix and its community will grow. Especially the Native-OSGi work might be important for this (see below).
+
+Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
+None.
+
+How has the community developed since the last report?
+
+There is no active growth, but in the past few months talks have been given on Native-OSGi. Native-OSGi is an effort to standardise C/C++ implementations of OSGi. The goal of this is to be able to reuse bundles from other OSGi like implementations. Also working together might attract more users/committers. The talks are attended by a good group of people, and reactions are positive.
+
+How has the project developed since the last report?
+
+A first release has been made. After struggling with several problems, consensus has been reached to solve these in a next release.
+On a technical note, Celix now also compiles and runs on Win32 platforms.
+
+## [2012-10](http://wiki.apache.org/incubator/October2012)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C. 
+
+Celix entered incubation on November 2, 2010. 
+
+Over the last months we have focused on creating a first release for Celix.
+As is mentioned in the graduation plan [1] we hope that a release will create
+more community.
+We have prepared the code base and website for release and we are very close to making a release.
+
+The previous report [2] mentioned that we are working on a "Native-OSGi", which could attract more community.
+This discussion continued in Juli on the mailling, but got quiet after that. There will be a talk about Native-OSGi for ApacheCon EU and EclipseCon EU and we expect that this will create attention for Celix.
+
+- Most important issues to address before we can graduate: 
+Make a first release, growing the community and attracting more committers.  
+
+- Any issues the Incubator PMC or ASF board need to be aware of: 
+None at this time 
+
+- How has the community developed since the last report: 
+There has been a small decrease on activity on the mailing list, hopefully this is a temporary decrease due to the holidays. We did receive patches from a contributor. 
+
+- How has the project developed since the last report: 
+We are still working towards a first release. The code base has been prepared for release and the website got some attention
+based on the shepherd's view from last report. 
+
+[1]: http://celix.apache.org/community/boardreports/boardreports.html#2012-04
+[2]: http://celix.apache.org/community/boardreports/boardreports.html#2012-07
+
+Signed off by mentor: marrs
+
+## [2012-07](http://wiki.apache.org/incubator/July2012)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C.
+
+Celix entered incubation on November 2, 2010.
+
+Over the last months we have started working on "Native-OSGi" which is an effort to make a specification for a C and C++ bases OSGi implementation. As detailed in the graduation plan [1] in the previous report we hope to attract more community members with this move.
+Details for Native-OSGi can be found at [2].
+
+Also the donation of the Device Access code has been finished and committed to the SVN repository. This has been a good experience from both a technical and a process point of view.
+
+Furthermore there has been a slight increase on the mailing list, hopefully this is a trend that will continue in the coming months.
+
+* Most important issues to address before we can graduate
+
+  Make a first release and grow a larger community. It is also needed to attract some more committers, there are currently 2. We are in the process of cleaning up the code and project structure so a first release can be made.
+
+* Any issues the Incubator PMC or ASF board not te be aware of
+
+  None at this time
+
+* How has the community developed since the last report
+
+  There has been an increase on the mailing list, furthermore with the start of the Native-OSGi project we hope this will increase in the coming months.
+
+* How has the project developed since the last report 
+
+  From a technical point of view, we are working towards a first release. The build files have been updated to support a more modular project structure.
+Since the implementation is moving forward (al be it slowly), the community growth is the biggest concern for Celix.
+
+[1]: http://celix.apache.org/community/boardreports/boardreports.html#2012-04
+[2]: https://github.com/abroekhuis/NativeOSGi
+
+Signed off by mentor:
+
+Shepherd: Matt Franklin
+
+## [2012-04](http://wiki.apache.org/incubator/April2012)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C.
+
+Celix entered incubation on November 2, 2010.
+
+The last month we received or first large code donation, the code still has to be added to the project. This code is an implementation of the OSGi Device Access specification for Celix and has been made by Thales Netherlands. Together with this donation a new committer (Pepijn Noltes) is accepted. Pepijn has developed and will maintain the Device Access code.
+
+We have also been working on a graduation plan which is included below.
+
+Most important issues are:
+
+    Improve robustness (APR, error handling etc), resulting in a first release
+    Update/Implement remote services for interoperability with Java OSGi (Apache Felix)
+    Generate awareness and grow a community!
+
+Graduation Plan
+
+Celix is in incubation since November 2010. During the first one and a half year talks where given at several conferences (EclipseCon, ApacheCon, OSGi User Group meetings, etc).
+Even though there seems to be an interest in the project, two important questions keep coming up:
+
+- What is the state of the project?
+- Why no support for C++?
+
+Trying to answer/solve these two questions might make it able to attract more community members. So this plan will focus mostly on these two items.
+
+= State of the project
+
+== Releases
+
+Celix entered incubation in its early stage. There was only a proof of concept, but no complete implementation. 
+This is an important reason for people to hold back and not yet use/improve Celix, on the other hand,  being hesitant also keeps Celix from growing towards a more stable/robust solution.
+To be able to use Celix the implementation has to reach, at least, a more stable state. Over the past year lots of effort has been put into this.
+Within the next half year a release has to be made of the core component of Celix. Hopefully this will attract more users/testers (and potentially committers).
+Since a formal release takes quite some effort, it might also make sense to provide snapshots (with documentation) to be able to reach more people.
+
+== Committers
+
+During the last months there has been an interest from Thales Netherlands to use Celix in its middleware. In a research project they are working on an implementation of the Device Access specification. This implementation is donated to Celix, and the main developer has expressed the intention to maintain the code base. Via this path a new committer has been added to Celix [1][2].
+But to be able to have a diverse community more committers are needed.
+Having a release makes it easier for people to use and improve Celix. This is one step towards more committers.
+
+[1]: http://markmail.org/thread/hfwuspl3swoisenq
+[2]: http://markmail.org/message/q4n7562jvngd33s5
+
+== Technical state
+
+One of the important aspects of Celix is interoperability with Java OSGi through remote services. Currently Celix has basic support for Celix to Celix remote services, following the Remote Service Admin specification of OSGi. This implementation has to be improved and extended to comply better to the specification. Also a Java OSGi implementation has to be made which can interact with the Celix implementation. Some existing opensource solutions are available, but are either to large for our intended target platforms or rely on to many other libraries (for example XML handling etc). To be able to have an implementation which fits the environment ((de)serialization and protocol) it makes sense to implement a simple solution ourselves.
+Having functional remote services makes it easier to use Celix in a mixed Java/C environment. This solution can also be positioned as an alternative to JNI with the benefit that the Java and C components are separate processes. If either one crashes the other part is kept running, resulting in a more robust solution.
+ 
+= C++ Support
+
+== Technical Scope
+
+Currently Celix is limited to C only. This was a deliberate choice since Celix tries to target  embedded/constrained platforms. But during talks people also seem to be interested in C++ support. Extending the technical scope of the project might attract more users and committers.
+Over the next half year we will work out a plan how C++ support can be added without impacting the current supported platforms. A start with the discussions has been made on the mailinglist, see [2] for more information.
+
+[3]: http://markmail.org/thread/a3qltqhsocmrnerd
+
+== Cooperate with existing C++ OSGi like implementations
+
+In [3] a list of similar projects is mentioned. Reaching out to these projects and trying to find a common ground on requirements/API etc could benefit Celix (and those projects as well). 
+To see if there is a common ground we need to contact those projects and plan a meeting.
+
+Signed off by mentor:
+
+## [2012-01](http://wiki.apache.org/incubator/January2012)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C.
+
+Celix entered incubation on November 2, 2010.
+
+Over the last few months lots of work has been put into integrating APR and updating the Celix code base to the proposed code style. This code style has partially been documented on [1]. Also some effort has been put into updating the source for Visual Studio, even though not yet finished some interesting and helpful patches where submitted and applied.
+
+In Oktober an event was held to create more awareness for services, OSGi and Celix in the Dutch embedded community. The attendance was great, and a follow-up will be planned. Also, in November a talk was given at the ApacheCon.
+
+As listed below, one of the most important issues is the slow growth of the Celix community. With the current discussion about poddlings and how long a poddling is in the incubator, we are discussing a plan how we can move to a more diverse community and be able to graduate. This plan will be included in the next board report.
+
+Most important issues are:
+
+    Improve robustness (APR, error handling etc), resulting in a first release
+    Generate awareness and grow a community!
+
+
+Signed off by mentor: marrs
+
+[1]: http://celix.apache.org/documentation/mapping.html
+
+## [2011-10](http://wiki.apache.org/incubator/October2011)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C.
+
+Celix entered incubation on November 2, 2010.
+
+In the code not much has changed during the past few months, mostly due to vacations. Some (reported) bugs have been fixed, and some interesting examples have been added. These example where donated by a user, and follow the OSGi in Action book. This makes them a great addition to Celix.
+Furthermore, some work has been done to make testing from CMake easier, and we are also looking into a method for mocking services to be able to test only one service without all its dependencies.
+
+On the community site, Luminis and Thales are organizing an event (in Dutch) to introduce embedded/distributed companies to OSGi. During this event OSGi will be explained, Celix and PojoSR will be introduced. Also a small introduction in Apache and the "Apache Way" will be given, with the goal to invite people to use/join Celix.
+Also, in november a talk and demo will be given at the ApacheCon.
+
+Most important issues are:
+
+    Improve robustness (APR, error handling etc)
+    Generate awareness and grow a community!
+
+Signed off by mentor:
+
+## [2011-07](http://wiki.apache.org/incubator/July2011)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C.
+
+Celix entered incubation on November 2, 2010.
+
+Over the past few months work has been done on integration and usage of the Apache Portable Runtim (APR) in Celix.
+The work has mostly focusses on stability and robustness of the codebase, but some new features were added:
+  
+    Log Service and Writer: for logging and reading the log
+    Service Factories: needed for the log service
+
+Also, in March, a talk was given to the OSGi User Group France. There is a lot interest in the project, but people seem to be waiting for a more stable version.
+For community building it might be interesting to work towards a release later this year to make it easier to download and use Celix.
+A talk on Celix has also been accepted for the ApacheCon in November, which is a good opportunity to show Celix to the world.
+Also parts of Celix have been ported to Windows. Mostly the utils used by the framework, and not yet the framework itself. This is a lengthy job because Celix is using C99, and Windows (Visual Studio) only support C89/C90.
+
+Most important issues are:
+
+    Improve robustness (APR, error handling etc)
+    Generate awareness and grow a community!
+
+Signed off by mentor:
+
+## [2011-04](http://wiki.apache.org/incubator/April2011)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C.
+
+Celix entered incubation on November 2, 2010.
+
+During the EclipseCon a talk was given over Celix, also spoke with several OSGi 
+people who are interested in the progress, especially related to Universal OSGi 
+(which details specification and requirements for OSGi in other languages).
+During the last few weeks work has been done to get rid of memory leaks and null 
+pointers.
+Currently we are looking at the requirements/details for bundle deployment and 
+updating, possibly in combination with Apache Ace.
+
+Most important issues are:
+
+    Define a status overview of what is and isn't working.
+    Move all "sub" project to the new structure.
+    Use APR for all file handling, threading etc.
+    Generate awareness and grow a community
+
+Signed off by mentor:
+
+## [2011-02](http://wiki.apache.org/incubator/February2011)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C.
+
+Celix entered incubation on November 2, 2010.
+
+A new structure for the project has been used for the framework. In this structure public and private files are 
+separated. This structure has not yet been applied to all "sub" project in Celix.
+We are also looking at Apache APR for OS abstraction. Using APR would involve replacing all file handing, threading 
+etc with APR functions.
+
+Finally, work is being done for the talk on the EclipseCon.
+
+Most important issues are:
+
+Add more information to the wiki (ongoing process)
+Move all "sub" project to the new structure.
+Use APR for all file handling, threading etc.
+
+Signed off by mentor:
+
+## [2011-01](http://wiki.apache.org/incubator/January2011)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C.
+
+Celix entered incubation on November 2, 2010.
+
+Currently the source tree is being cleaned and correct header information is being added. We are also looking at the 
+project structure and how it can be changed to get a better/simpler overview. Most important aspect is separating the 
+actual framework from the additional bundles.
+
+Additionally, last December a proposal for a Celix talk was sent to, and accepted by the EclipseCon/OSGi DevCon. This 
+provides a great opportunity to increase awareness and build a community.
+
+Most important issues are:
+
+    Add more information to the wiki (ongoing process)
+    Cleanup project, rearrange structure
+    Generate awareness and grow a community!
+
+Signed off by mentor: marrs 
+
+## [2010-12](http://wiki.apache.org/incubator/December2010)
+
+= Celix =
+
+Celix is an implementation of the OSGi Specification in C.
+
+Celix entered incubation on November 2, 2010.
+
+As we are just accepted into the Incubator, startup is in progress. The donated code has been committed to 
+SVN, and the project site is being created.
+
+Most important issues are:
+
+    Get everything (Jira, SVN, Website etc) up and running
+    Cleanup code
+    Generate awareness and grow a community.
+
+Signed off by mentor: marrs

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/content/community/contributing.md
----------------------------------------------------------------------
diff --git a/content/community/contributing.md b/content/community/contributing.md
new file mode 100644
index 0000000..da57faa
--- /dev/null
+++ b/content/community/contributing.md
@@ -0,0 +1,27 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+title: Contributing
+---
+# Contributing
+
+The Celix community is open for everyone to participate in. Discussions are done over the 
+[mailing lists](/support/mailinglist.html), and [issues](/support/issuetracking.html) can be created and 
+seen by everyone.
+
+If you would like to join the Celix community, a good start would be to follow the mailing list and participate in the 
+discussions, use Celix and report bugs you find, possibly with patches.

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/content/community/index.md
----------------------------------------------------------------------
diff --git a/content/community/index.md b/content/community/index.md
new file mode 100644
index 0000000..8d17839
--- /dev/null
+++ b/content/community/index.md
@@ -0,0 +1,34 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+title: Community
+menu: main
+---
+# Celix Community
+
+Celix is a community driven project, where everyone is free to download and use it. Besides using Celix we encourage 
+everyone to participate in the development. This can be as simple as providing feedback and reporting bugs but could as 
+well mean bug fixes and code contributions.
+
+- [Contribute](/community/contributing/contributing.html)
+
+While Celix was in incubation at the Apache Incubator, the status had to be reported to the Incubator PMC. These
+reports are also available on this site.
+
+- [Board Reports](/community/boardreports/boardreports.html)
+
+

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/content/community/releasing.md
----------------------------------------------------------------------
diff --git a/content/community/releasing.md b/content/community/releasing.md
new file mode 100644
index 0000000..77fbe98
--- /dev/null
+++ b/content/community/releasing.md
@@ -0,0 +1,233 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+title: Releasing
+---
+# Releasing Apache Celix
+
+Note: This information is only of use to Apache Celix Release Managers!
+
+Steps to follow:
+
+  - Create signing KEYs
+  - Update release related files
+  - Compile and test
+  - Create SVN tag
+  - Create, sign and publish artefacts
+  - Run the vote
+  - Post the vote results
+  - Roll out the release artefacts
+  - Announce the release
+
+Interesting links:
+
+ - [Apache Release Guide](http://www.apache.org/dev/release.html)
+ - [Apache Release Signing](http://www.apache.org/dev/release-signing.html)
+ - [Apache RAT](http://creadur.apache.org/rat/apache-rat/index.html)
+ - [Apache OpenPGP Howto](http://www.apache.org/dev/openpgp.html)
+
+## Create signing KEYs
+Each Release Manager must have his own signing keys. Information about and instruction for the generation of these keys can be found on the
+[Signing Releases page](http://www.apache.org/dev/release-signing.html#generate) and [How To OpenPGP](http://www.apache.org/dev/openpgp.html#generate-key). Be sure to follow the information provided on that site and its references.
+
+The generated key can be uploaded to the [MIT PGP Public Key Server](http://pgp.mit.edu).
+
+Next, the public key signature must be added to the KEYS file. Again, read the [Signing Releases page](http://www.apache.org/dev/release-signing.html#keys-policy)
+for more information. This updated file needs to be uploaded to SVN, be sure to upload it to:
+
+  - [Apache Celix release development area KEYS](https://dist.apache.org/repos/dist/dev/incubator/celix/KEYS)
+  - [Apache Celix release distribution area KEYS](https://dist.apache.org/repos/dist/release/incubator/celix/KEYS)
+
+## Update release related files
+For every release the related files must be updated. The following files are relevant:
+
+  - CHANGES.md
+
+     Add a list of fixed issues which can be created using Jira.
+
+  - RELEASE_NOTES
+
+     Add additional notes regarding this release, eg known short comings.
+
+  - BUILDING
+
+     Even though the BUILDING file doesn't have any specific release information, it should be verified before making a release.  
+
+  - NOTICE
+
+     If needed, add any new license related information to this file.
+  
+Besides this information, the version needs to be bumped. Even though every bundle has its own version, a release is made with one overall version. This version
+is defined in the top-level CMakeLists.txt file.
+Update the following pieces:
+
+    SET(CELIX_MAJOR "X")
+    SET(CELIX_MINOR "Y")
+    SET(CELIX_MICRO "Z")
+
+Note: The DEFAULT_VERSION property is used as default version for new bundles and as such does not need to be updated when making a release.
+  
+## Compile and test
+Before creating a branch, be sure that the source compiles and tests run successfully. If there are any known shortcomings, make sure they are listed in the 
+RELEASE_NOTES. Details for compiling and testing are available in the BUILDING file.
+
+Also verify that the provides examples work as expected. If needed ask other committers to test parts.
+
+After verifying the build, run Apache RAT to check for any licensing problems. If Apache RAT is configured in the CMake build the "rat" target can be used to run
+the check.
+
+    // From the celix-build directory
+    // Run CMake to set the APACHE_RAT library (path to the JAR file).
+    > ccmake ../celix
+    // Configure location of the apache-rat jar
+    > make rat
+
+Apache RAT should not raise any concers, if there are, check the source files for 
+a license header. If it is a false positive update the rat-excludes.txt file in the root of the project. Be sure it is a false positive! If in doubt, ask the 
+mailing list! Third party licenses may need to be mentioned in the NOTICE file.
+
+## Git commit ID
+After changing all files a git commit ID can be used for the new release must be made. Before doing so, make sure all changed files are committed.
+
+Note: Make sure there are no new changes made on release branch while working on the release.
+
+## Create, sign and publish artefacts
+Since Celix only releases source artefacts, creating the artefact is simple and straightforward
+
+    // Create a release artefact using git archive
+    > git archive --format tar.gz --prefix celix-<release number>/ <commit ID> > celix-<release number>.tar.gz
+
+After creating the artefact, the file has to be signed. More information about signing can be found at (http://www.apache.org/dev/release-signing.html).
+
+    // Generate MD5 checksum
+    > md5 celix-X.Y.Z.tar.gz > celix-X.Y.Z.tar.gz.md5
+    // Generate SHA512 checksum
+    > gpg --print-md SHA512 celix-X.Y.Z.tar.gz > celix-X.Y.Z.tar.gz.sha
+    // Generate ASCII signature
+    > gpg --armor --output celix-X.Y.Z.tar.gz.asc --detach-sig celix-X.Y.Z.tar.gz
+
+Copy the archive of the source to the [Apache Celix release development area](https://dist.apache.org/repos/dist/dev/celix) (using SVN).
+
+See the [Apache Release Guide](http://www.apache.org/dev/release.html#host-rc) for more information.
+
+## Run the vote
+Before a release is official a vote has to be held. More information on voting can be found on [Apache Voting Process](http://www.apache.org/foundation/voting.html).
+
+The first vote has to be done on the public mailinglist of the project itself (dev@celix.apache.org). The following template must be used for this vote:
+
+================================================================================================================
+> To: dev@celix.apache.org  
+> Subject: [VOTE] Release Celix version X.Y.Z
+
+> This is the release vote for Apache Celix, version X.Y.Z.
+
+> Source files:  
+> https://dist.apache.org/repos/dist/dev/celix/celix-X.Y.Z/
+
+> The commit ID to be voted upon:  
+> <commit ID>
+> https://github.com/apache/celix/tree/<commit ID>
+
+> Celix's keys can be found at:  
+> https://dist.apache.org/repos/dist/dev/incubator/celix/KEYS
+
+> Information for voting on a release can be found at http://www.apache.org/dev/release.html#approving-a-release
+
+> Please vote to approve this release:
+
+> [ ] +1 Approve the release  
+> [ ] -1 Disapprove the release (please provide specific comments)
+
+> This vote will be open for at least 72 hours.
+
+================================================================================================================
+
+After this first vote the results must be posted to the "dev" list, see below for more information.
+
+================================================================================================================
+
+Note: Be sure to use the [VOTE] tag, this is used by the automated vote tracking system to keep track of outstanding vote threads.
+
+## Post the vote results
+As mentioned before, after each vote the results must be posted to the corresponding list. This "Result" vote contains the number of votes made, including 
+wether a vote is binding or not. For a successful vote the following template can be used.
+
+================================================================================================================
+> To: dev@celix.apache.org  
+> Subject: [RESULT][VOTE] Release Celix version X.Y.Z
+
+> The vote has passed with the following result:
+
+> +1 Name of Approver (apache ID) (binding|not binding)  
+> +1 Name of Approver (apache ID) (binding|not binding)  
+> ...
+
+> {include additional details if needed}
+
+> The released artifact will be moved to the release area for mirroring. After the mirroring period the release will be announced.
+
+> Thanks for voting.
+
+================================================================================================================
+
+Note: Be sure to post the vote result with the same topic as the original message. Also prepend the subject with [RESULT]. This is, again, needed to be able to keep track
+of vote threads. 
+
+## Roll out release artefacts
+If the vote is passed successfully the release can be moved from the "dev" area to "release". The automated svnpubsub will move the artifact to the correct 
+server for mirroring. Mirroring typically can take up to 24 hours.
+
+Besides uploading the new release, the old release should be archived. Since archiving is already automated, it is only needed to delete the previous version from the release
+area. See the [Apache Release Guide](http://www.apache.org/dev/release.html#when-to-archive) for more information.
+
+See the [Apache Release Guide](http://www.apache.org/dev/release.html#upload-ci) for more information.
+
+After these 24 hours the release can be announced.
+
+## Announce the release
+Update website's [News](http://celix.apache.org/index.html) and [Download](http://celix.apache.org/download.html) sections to include the new release.
+
+On the "Download" page, the old release can be replaced with the new one, there is no need to keep a link to archived versions. The "News" section can simply be extended
+with an additional entry.
+
+Additionally it is a good idea to post a message to "announce@apache.org" and "dev@celix.apache.org". (note: the from address must be a ...@apache.org address).
+
+The following template must be used:
+
+================================================================================================================
+> To: announce@apache.org, dev@celix.apache.org  
+> Subject: [ANNOUNCE] Apache Celix X.Y.Z released
+
+> The Apache Celix team is pleased to announce the release of Celix X.Y.Z.
+
+> Celix is an implementation of the OSGi specification adapted to C. It will follow the API 
+> as close as possible, but since the OSGi specification is written primarily for Java, there 
+> will be differences. An important aspect of the implementation is interoperability between 
+> Java and C. This interoperability is achieved by porting and implementing the Remote 
+> Services specification in Celix.
+
+> This new release focusses on .... {add additional information for this release}
+
+> The release is available here:  
+> http://celix.apache.org/download.cgi
+
+> We welcome your help and feedback. For more information on how to report problems, 
+> and to get involved, visit the project website at http://celix.apache.org/
+
+> The Apache Celix Team
+
+================================================================================================================

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/content/downloads/index.md
----------------------------------------------------------------------
diff --git a/content/downloads/index.md b/content/downloads/index.md
new file mode 100755
index 0000000..15f971e
--- /dev/null
+++ b/content/downloads/index.md
@@ -0,0 +1,50 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+title: Download
+menu: main
+---
+# Download Celix
+
+Celix is an implementation of the OSGi specification adapted to C.
+
+
+## Releases
+
+Apache Celix only releases source distributions, information about building and running van be found inside the release tarball.
+
+### Mirrors
+
+The currently selected mirror is **[preferred]**. If you encounter a problem with this mirror, please select another mirror. If all mirrors are failing, there are *backup* 
+mirrors (at the end of the mirrors list) that should be available. 
+<form action="[location]" method="get" id="SelectMirror">Other mirrors:
+    <select name="Preferred">
+        [if-any http] [for http]<option value="[http]">[http]</option>[end] [end] 
+        [if-any ftp] [for ftp]<option value="[ftp]">[ftp]</option>[end] [end] 
+        [if-any backup] [for backup]<option value="[backup]">[backup] (backup)</option>[end] [end]
+    </select>
+    <input type="submit" value="Change"></input>
+</form>
+
+You may also consult the [complete list of mirrors](http://www.apache.org/mirrors/).
+
+### Downloads
+
+- Source: [celix-2.0.0.tar.gz]([preferred]/celix/celix-2.0.0/celix-2.0.0.tar.gz)
+[PGP](http://www.apache.org/dist/celix/celix-2.0.0/celix-2.0.0.tar.gz.asc)
+[MD5](http://www.apache.org/dist/celix/celix-2.0.0/celix-2.0.0.tar.gz.md5)
+[SHA1](http://www.apache.org/dist/celix/celix-2.0.0/celix-2.0.0.tar.gz.sha)

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/content/support/_index.md
----------------------------------------------------------------------
diff --git a/content/support/_index.md b/content/support/_index.md
new file mode 100644
index 0000000..c6bf84b
--- /dev/null
+++ b/content/support/_index.md
@@ -0,0 +1,22 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+title: "Support"
+menu: 
+  main:
+    identifier: "support"
+---

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/content/support/issuetracking.md
----------------------------------------------------------------------
diff --git a/content/support/issuetracking.md b/content/support/issuetracking.md
new file mode 100644
index 0000000..1b2dfd6
--- /dev/null
+++ b/content/support/issuetracking.md
@@ -0,0 +1,38 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+title: "Issues"
+menu:
+  main:
+    parent: "support"
+---
+# Issue Tracking
+
+Celix uses Jira for bug reports, feature requests, enhancements and tasks of all kind.
+
+Anyone can use Jira to report bugs. But before doing so, please make sure that:
+
+- the bug isn't already reported,
+- the problem is actually a bug (the [mailing list](/support/mailinglist.html) can be used for support),
+- you attach enough information to replicate the bug (preferably a unit test)
+
+If you have fixed a bug, the patch can be attached to a bug report.
+
+The Celix Jira Issue Tracker can be found at:
+
+ - <https://issues.apache.org/jira/browse/celix>
+  

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/content/support/mailinglist.md
----------------------------------------------------------------------
diff --git a/content/support/mailinglist.md b/content/support/mailinglist.md
new file mode 100644
index 0000000..45a204c
--- /dev/null
+++ b/content/support/mailinglist.md
@@ -0,0 +1,41 @@
+---
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+# 
+#   http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+title: "Mailing list"
+menu:
+  main:
+    parent: "support"
+---
+# Mailing List
+
+Celix users and developers can be reached using mailing lists. Currently there is only one list for development and 
+support questions.
+
+- [Celix Developers Mailing List](mailto:dev@celix.apache.org)
+    - [Subscribe](mailto:dev-subscribe@celix.apache.org)
+    - [Unsubscribe](mailto:dev-unsubscribe@celix.apache.org)
+    - [Archives](http://mail-archives.apache.org/mod_mbox/celix-dev/)
+    
+If the Celix community grows, and there is a need for a dedicated users mailing list, it will be created.
+
+There is a second mailing list which is used to publish changes from the 
+[Issue Tracker](/support/issuetracking.html).
+
+- [Celix Commits Mailing List](mailto:commits@celix.apache.org)
+    - [Subscribe](mailto:commits-subscribe@celix.apache.org)
+    - [Unsubscribe](mailto:commits-unsubscribe@celix.apache.org)
+    - [Archives](http://mail-archives.apache.org/mod_mbox/celix-commits/)

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/docTableIndex.xml
----------------------------------------------------------------------
diff --git a/docTableIndex.xml b/docTableIndex.xml
deleted file mode 100644
index 3efd473..0000000
--- a/docTableIndex.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version="1.0"?>
-<!--
-possible arguments:
-path: the sourcepath for this file (required)
-dest: destination where the path is to be placed (defaults out/doc/titlename/filename.html)
-import: configure how a file to be imported is signified in a file. "url" is where the import url should be in the actual file.
-mdHtml: set true to parse the document from markdown to html (defaults true)
--->
-<root>
-	<title name="one">
-		<file name="main">
-			<path>README.md</path>
-			<dest>site/doc/index.html</dest>
-		</file>
-		<file name="file one">
-			<path>celix/documents/intro/readme.md</path>
-			<import>{{url}}</import>
-		</file>
-	</title>
-	<title name="two">
-		<file name="file two">
-			<path>celix/documents/getting_started/creating_a_simple_bundle.md</path>
-		</file>
-		<file name="file three">
-			<path>celix/documents/getting_started/readme.md</path>
-		</file>
-	</title>
-</root>

http://git-wip-us.apache.org/repos/asf/celix-site/blob/d212e764/src/bottom.html
----------------------------------------------------------------------
diff --git a/src/bottom.html b/src/bottom.html
deleted file mode 100755
index 8063802..0000000
--- a/src/bottom.html
+++ /dev/null
@@ -1,6 +0,0 @@
-</div><div id="foot">
-<div id="footText">
-Copyright © 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
-Apache Celix, Celix, Apache, the Apache feather logo and the Apache Celix logo are trademarks of The Apache Software Foundation. 
-</div></div>
-<script src='/import/javascript.js'></script>


Mime
View raw message