DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=fW7NP5ZFtwkVPl1thuevySbuEZKNVFJck5C/g0yo/E0iUbp/wGLW75uzgpmrNi2/nG
         nPxxiQJAba05TmuIbehiEoJ3oqYmnT2GtHBBvPOvoRm0wXgIUWhawwqlSY7oRzdnJCEV
         1cOBsBplls/9dZtP03WP9lep6f9gB8b5JGkEg=
Precedence: list
MIME-Version: 1.0
Date: Thu, 21 Apr 2011 01:01:04 +0200
Message-ID: <BANLkTikD1Y=0ZL8-wT7=4+v73V0OSncWPg@mail.gmail.com>
Subject: [alpine-devel] Alpine Linux - Small Simple Secure
From: Carlo Landmeter <clandmeter@gmail.com>
To: Alpine-devel <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset=ISO-8859-1

Hello Alpine Linux users / fans

While we are nearing a final 2.2 release, we have also worked on
creating a new website which we want to launch at the same time.
It is made with Drupal 7.x and runs on Lighttpd with Postgresql as
database and of course on Alpine Linux.

This new website will be used for the following:

* News
* Downloads
* Package browser
* Additional information (links to other services)
* Blog(s) maybe per developer (something like Planet Alpine
* And more...

Note:we keep documentation on our wiki

Most of the content is generated with Drupal and contrib modules found
on Drupal.org except for one, which is the package browser.
While I know its far from perfect, it currently does its job which is
fetch package information from our repo's and import it into Drupal as
nodes (content).
With the help of Drupal Views we are now able to browse our packages.
I made a simple template to display an individual package, it is
currently limited because we recently added extra fields to our
packages to help display related information. A list of the current
variables we can use are:

Package: Name, Checksum, Version ,Size, Installed size, Description,
URL, License,
Origin, Build date, Commit hash, Maintainer ,Dependencies, Install If,
Architecture, Repository

Things we currently have on our todo (from my memory) are:

* Link the package to the actual commit.
* Link the package to the maintainer which is a Drupal user

When mapping packages to maintainer it will be easier for each
developer to see which packages belong to him, while our users will be
able to flag packages our of date.
For this linking to work, we will need all developers to register an
account and have a matching email address in their profile to match to
the maintainer field in aports.

As for the layout/theme of our site, it is based on Drupal Pixture
Reloaded theme. We use this as base because we do not have any artwork
specialists in our team. We have tried with a bit of tweaking to
provide a simple and clean website which focus on easy access of
information without too much bloat. This is also one of the items
which can be improved if somebody has those skills.

We would like everyone to take a sneak peak and provide us with
input/ideas so we can try to implement/fix them before we go live with
our 2.2 release. Because its not yet online you will need to make a
change to you hostfile (or router/dns) so www.alpinelinux.org will
point to the correct server. The entry should be:

81.175.82.11 www.alpinelinux.org

Hosts file in linux is located here /etc/hosts
On Windows this should be Windows\System32\drivers\etc\hosts

All the code/artwork has been stored on our git repo:

http://git.alpinelinux.org/cgit/clandmeter/alpine_drupal_settings.git/
http://git.alpinelinux.org/cgit/clandmeter/alpine_drupal_theme.git/
http://git.alpinelinux.org/cgit/clandmeter/apk_browser.git/

P.S. is the slogan catchy enough?

-carlo


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---