FOSS Factory projects

sdfafgdsagsdfa
Need a project that functions exactly like Seedio for iOS

Seedio is basically an iOS app that allows an iPhone to play music and at the same time sync with other phones that play the same song in sync.. you are encouraged to download Seedio to see what I'm talking about.

- important things to keep in mind:

1. stay away from GKSession.. it's simply not good enough for this project.. you must use bonjour services for networking

2. i strongly advise you to use audio units (ie rather than audio queue..) you will need to have a very fine grained control over your audio

3. more detailed instructions will be provided in the subprojects

Are you able to get Ubuntu fully working on a Samsung 900X3C?

There is one "minor" issue left that needs to be solved, Hibernation and Suspend.

See here:

http://blog.nonobis.nl/?p=11

https://help.ubuntu.com/community/SamsungSeries9

Solve it with a robust solution and we will send you a free copy of your solution along with the Samsung 900X3C-A01NL worth 1300 dollars.

Or 1000 dollars in cash.
The idea is to ignore the hard problems of high-level language interpretation and focus on the ones we CAN solve easily.  For example, given an API of say 100 functions that have to do with drawing shapes, we should easily be able to map English-text commands like "Draw a circle of radius 5 at 100, 200".   And I didn't have to study any manual to figure that out.

Basically the Architecture will consist of all the parts needed to build the following demo:

(1) User is presented with a text command terminal, with several adjacent panes.  

(2) The user can type in questions or commands that will typically be one line.

(3) Fuzzy matching of the input string against 1000's languages will determine what the output script should be.

(4) If the match is exact (one and only one context language was matched), then the output code is run.

    If the match is fuzzy, then the user is displayed with the likely candidates based on probability and language metrics.

    If their is no fuzzy match, we could increase the maximum fuzzy distance of the search, display options to the user for specifying correct output, etc.

(5) The above might include connecting to a User Software repository and running the user's search on the server.

The way of doing interpretation should be left open and will probably depend on domain.  But we will provide the means of specifying these languages and mapping input strings to output code.  For the purpose of getting a demo running quick, I've come up with an obvious N-gram search of automata, but other methods exist like Levenshtein-Automata: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.16.652 .

Right now I'm working on a D implementation.  

Notes on the command-line demo

===============================

+ Text is a limiting feature but our language-handling methods should be applicable to general data.
Enhance an open-source OpenAL implementation to produce a stereo signal for headphones/earbuds based on head position reported from one of a number of libraries, preferably using a cross-platform API.

See also:

* http://alternativeto.net/software/trackir/

* http://en.wikipedia.org/wiki/OpenAL

* https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/1024607

Aptitude includes a highly configurable, interactive problem resolver which finds solutions to package dependency problems.  This project is for development of the problem resolver, including fixing some of the usability issues it currently has.

The aptitude resolver works well in some situations, and in others it is completely broken.  In some situations where the apt resolver finds a very simple solution, the aptitude resolver will find no solution, or find only a very complex solution.

There are also areas where the resolver could be enhanced in useful ways.

Sub-projects will be added here based on interest for particular tasks.  Please make your suggestions in the forum.

More information about aptitude, including any general requirements for submissions, can be found at the general development task:

http://www.fossfactory.org/project/p306

Source code for the problem resolver is mostly contained in this tree:

http://anonscm.debian.org/gitweb/?p=aptitude/aptitude.git;a=tree;f=src/generic/problemresolver
This is a container project for general development work on the aptitude package manager.

Aptitude is an APT front end with many features useful for beginner and advanced users.  It is primarily used in the Debian operating system and it's many derivatives.

http://packages.debian.org/unstable/aptitude

http://aptitude.alioth.debian.org/

There are a number of major outstanding issues, as well as many interesting and challenging development opportunities.  Anybody planning to work on these should subscribe to the developers mailing list:

http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

It is recommended to seek advice before commencing serious work.

HH
A low latency Telepresence system specialized for use in the concert industry, facilitating either interactive remote performances, or expanded seating capacity, by piping a live event through the internet into a remote venue to either interact with remote performers, or to be viewed by remote audiences, via extra-large video projection screens.

A Wormhole node allows performers located at multiple locations to interact with each other in real time, creating a single �virtual� stage out of many remote stages. When used in a non-interactive context, Wormhole acts as a simulcasting platform, providing live, HD audio and video feeds to a remote location which can act as overflow seating, or simply remote seating- anywhere in the world.

Each Wormhole node is to be designed entirely out of commodity hardware, and will ultimately consist of a standard 19" rack-mounted unit suitable for withstanding the rigors of concert touring (Currently, Dell offers a half-depth, 1U server called the Poweredge R210 which appears suitable for use as a starting point in the design of a 19" rack-mounted unit).

The overall design of each node will be open-source, and made available from the project's website as a DIY project to any prospective event participant. The DIY project's website will include a database of various equipment one might want to use with their own node, and will present a table/database including information regarding the inherent latencies of various peripheral I/O devices such as video projectors. A best practices whitepaper will be developed detailing various strategies for reducing latency between venues.

A cloud-based feed coordination system will manage connecting audio & video feeds between venues which have registered themselves as participants at any given event.

The project's central servers will also provide an electronic ticketing system, which will embed into any event promoter's website, allowing them to sell electronic tickets to customers who wish to obtain a private audio/video feed which can be viewed through a home theater system, or just on the computer.

A similar project called 'Scenic' (http://scenic.sat.qc.ca/en/Scenic) has developed software which could be forked to serve as a starting point for the software acpect of a Wormhole node.

In the event that latency issues make it necessary to develop a PCIe card for the purpose of offloading audio/video processing, its design will also be open-source.
The goal of this project is to create a peer-to-peer digital wallet able to manage the user's digital currencies according to the user's wishes.

The main innovation points of this software design compared to existing digital wallets:

* multiple currencies are transparently handled

* the user can favor the currencies they trust most

* currency conversions are transparently handled during payments

* the wallet value may increase as the software carries out currency exchanges for other peers (thanks to  conversion fees and sometimes favorable exchange rates)

Rationale:

In addition to Bitcoin, a number of digital currencies are arising, giving people a range of options regarding digital currencies.  However this should not result in more difficult transactions.  This project intends to ameliorate this, by providing a distributed network of digital money changers, operating transparently and at minimum cost on behalf of the user.

Required functionality:

* The program should be able to determine the current currency exchange rates from the peers

* The user should be able to adjust the exchange rates for the currencies

* The user should be able to reserve part of their digital currency reserves for other peers to carry out currency exchanges, with a configurable fee.

* The user should be able to easily pay to and request payments from other peers.

* The software should have a simple but possibly captivating web interface.

* The software should at minimum support Bitcoin and any other digital currency having an RPC-interface compatible with Bitcoin.

The goal of this project is to have the documented[1] table inheritance caveats fixed and released.

As of version 9.1, three caveats are documented as follows. "Cities" is the parent (inherited) table and "capitals" is the child (inheriting) table:

> If we declared cities.name to be UNIQUE or a PRIMARY KEY, this would not stop the capitals table from having rows with names duplicating rows in cities. And those duplicate rows would by default show up in queries from cities. In fact, by default capitals would have no unique constraint at all, and so could contain multiple rows with the same name. You could add a unique constraint to capitals, but this would not prevent duplication compared to cities.

> 

> Similarly, if we were to specify that cities.name REFERENCES some other table, this constraint would not automatically propagate to capitals. In this case you could work around it by manually adding the same REFERENCES constraint to capitals.

> 

> Specifying that another table's column REFERENCES cities(name) would allow the other table to contain city names, but not capital names. There is no good workaround for this case.

> 

CONDITIONS:

a. To consider the project completed, the fix or fixes must be present in a PostgreSQL release as part of the core (as opposed to being part of contrib). -- This is to make sure it got through the PostgreSQL review process.

b. If other caveats are found to be documented in the manual before the fixed version (in whatever section that corresponds to the current 5.8.1 section), those must be fixed too. For example, if version 9.2 is not the fixed version but its manual documents a fourth caveat, it must be fixed too for the project to be considered fulfilled.

c. Submitted commit messages in patches must: 1) reference this project (a code like "FIX-INHERIT" is enough), 2) document the intention of the code (what the new code is supposed to do) and 3) if removing code, why was it wrong. -- This is to make the commits easily searchable.

d. Enough documentation must be published (and kept public, see e.) for others to understand the fixes and support them in the future. -- This is to allow the person not to get tied by e) alone.

e. A commitment must be made to support the fixes and its documentation for the rest of the major release and one more major release.

REFERENCES:

[1] http://www.postgresql.org/docs/9.1/static/ddl-inherit.html
The Checkmail plugin for the open source ResourceSpace digital asset management web application expands its capacities with support for the emailing of resources.  This is more than a matter of great convenience; it also allows iOS devices and other platforms the ability to contribute digital assets to the system.  The plugin is very robust, with advanced configuration options and the ability to handle a wide range of email types.

* With the Checkmail plugin, ResourceSpace can receive resources as file attachments from any email account with IMAP support

* Limit access to specified email addresses, coupled with sanctified ResourceSpace user accounts

* Multiple attachments are grouped into a collection

* Makes it easy to take pictures with your phone and upload to ResourceSpace using existing standards -- no special "apps"

* Configure the Subject and Body of the email to be inserted as custom metadata into specific metadata fields

* Confirmation emails notify you that your attachments have been uploaded

* Delete the emails after receiving them, or leave them on the account for record-keeping or reprocessing

* Accepts both HTML and plain text emails

* Accepts all variations of MIME parts and character sets

* Accepts regular and inline attachments

* Emails are uploaded to a default status and access, so it supports a review process

* Resource types designated by file extension automatically
A headless daemon facilitating lossless webradio broadcasts originating from either studio or live event sites.

Project goals / features (In order of priority):

1. The app is to be headless.

2. The server(s) will cluster and loadbalance between themselves to accomodate high load.

3. The cluster will accept and broadcast a live feed from a show site.

4. The preferred audio format for the stream is .flac, however a sub-project which introduces a new, more suitable lossless format to the industry is acceptable, however it would be preferable to not have to undertake such an effort.

5. The app will be written to take advantage of paralellism, such that it can be set to utilize a set number of CPU cores, as defined during installation.

6. The server(s) need to be able to create and play a playlist whose files are located on multiple SMB shares.

6a. This since the pool of files from which the server will be choosing files to play will one day exceed 2TB easily, and as such will likely be distributed across multiple file servers.

7. The server plays multiple playlists, and treats a playlist as if it were a file in a larger, overall sequence of what gets played. Each playlist will contain its own specification as to whether it plays itself in order or at random, before moving on to the next playlist in the sequence.

7a. For example, 'Playlist 1' contains a list of files, and specifies that these files will be played in order before the playlist exits and the system moves on to 'Playlist 2', which specifies that its list of files be played at random, once each, before the system moves on to 'Playlist 3', which has its own parameters.

8. Each file in a playlist will have a parameter to define whether it has a gap of (definable x.xx) seconds at the beginning &/or end of the file.

9. There will be two primary streams offered to listeners, the lossless stream, and another .mp3 stream broadcasting at a slightly above average bitrate.

9a. This so that listeners can experience the contrast between the lossy & lossless audio, and so that a live spectral analysis visualization can be featured on the website, allowing users to see what's missing from the lossy stream.

An added benefit of offering a simultaneous .mp3 stream is that the station can then qualify to be listed on popular webradio directories, and will presumably draw the attention of audiophiles, and highlight the lossless mission of the station by featuring a show whose title includes the word 'lossless' on a directory whose content is all lossy.

10. The server will provide a secondary stream in the .aac format, suitable for use on mobile devices such as Blackberry, which will be able to play the stream in the browser, such as what SomaFM provides.

11. The app will produce a realtime spectral analysis visualization contrasting the lossy & lossless streams, which will be featured on the website in order for users to see the difference between the frequency response in each of the 2 primary streams.

12. The spectral analysis will do it's thing preferably without the use of client-side scripting such as java or flash.

12a. This so people such as myself who use NoScript won't have to create exceptions to use the site, and so browsers not supporting scripting can display the page- not to mention that it'll facilitate super-quick page loads.

13. A feature to make whatever's currently playing fade out at a prespecified time, and begin a certain playlist.

13a. This so that the day's programming can be going on as normal, and a featured event, be it a certain recording, or a live show's feed can be begun at a previously advertised time.

14. The app will be written to run in a Debian environment, and there will be a software repo created that's fit for inclusion in a Debian distribution, based on their standards.

15. There will be a .deb package created that's installable with dpkg which will automate the installation of the repo and its GPG keys so users can easily install the app with package managers such as Synaptic.

16. A listener queue so people who want to listen can be placed in line during periods when the available bandwidth is already in use by other listeners.

I found the PERL script below which generates a TOC from headers in a HTML file.  Problem is that it reads ALL the headers.  I want only these three headers in my generated TOC:  <H1 class="title-head">  and  <H2 class="chapter-head">  and  <H3 class="section-head">

I want the script to be easy enough to modify for future differences in the header classes I might use.

#! D:\perl\bin\perl.exe

###############################################################################

###############################################################################

#

# To add a table of contents, based on its headings, to an HTML page.

#

#			Version 2

#

#	by Andrew Hardwick, http://duramecho.com, 2002/3/22

#

#	Released under GNU Public Licence.

#

###############################################################################

###############################################################################

#

# How To Use

#

# Run from a command line with the source file name as arguement.

# If it finds an existing table of contents from this program then it will

#  replace it, otherwise it will add a new table at the top of the HTML body

#  (if you move this, be sure to move the '<!--TableOfContentsAnchor:...-->'

#  markers as well so that, if you need the table of contents updated, this

#  program can tell where you want the table of contents to be).

#

###############################################################################

#

# Known Deficiencies

#

# It ignores commenting out of HTML sections so it may find spurious headings.

# It does not check that the anchors it puts in and the HTML the comments it

#  puts in the HTML to mark the bits it has inserted don't duplicate existing

#  ones.

#

###############################################################################

###############################################################################

# Include libraries

use Cwd;		# To find current directory

use strict;		# Disenable automatic variables

# Global Variables

my @HeadingCount;

my @HeadingTexts;

my @HeadingLevels;

my @HeadingLabels;

###############################################################################

# Main rountine

###############################################################################

{	my ($c,$d);

	# Get data from file

	my $From=cwd().'/'.$ARGV[0];

	open(FILETOPROCESS,'<'.$From)||

			die("Cannot open $From to read.");

	my $Html;

	read FILETOPROCESS,$Html,-s $From;

	close FILETOPROCESS;

	# Remove any old anchors

	$Html=~s/<!--TableOfContentsAnchor:Begin-->

			.*?

			<!--TableOfContentsAnchor:End-->

			//gsx;

	# Find all headings & mark them with anchors

	$Html=~s/<H(\d)(.*?)>(.*?)<\/H\1>/

			'<H'.$1.$2.'><!--TableOfContentsAnchor:Begin--><A NAME="'.

			MarkHeading($3,$1).

			'"><\/A><!--TableOfContentsAnchor:End-->'.

			$3.'<\/H'.$1.'>'/gise;

	# Avoid jumping down more than one level at a time by adding null headings

	for($c=0;$c<scalar(@HeadingTexts)-1;$c++)

	{	if($HeadingLevels[$c]<$HeadingLevels[$c+1]-1)

		{	splice(@HeadingLevels,$c+1,0,$HeadingLevels[$c]+1);

			splice(@HeadingTexts,$c+1,0,'');

			splice(@HeadingLabels,$c+1,0,'');}}

	# Start HTML table of contents

	my $Toc="<!--TableOfContents:Begin-->\n<UL>\n";

	my $PreviousHeadingLevel=1;

	# Add in contents lines

	for($c=0;$c<scalar(@HeadingTexts);$c++)

	{	# Indent/outdent contents line

		for($d=$PreviousHeadingLevel;$d<$HeadingLevels[$c];$d++)

		{	$Toc=~s/^(.*)<\/LI>(.*?)$/$1<UL>$2/s;}

		for($d=$PreviousHeadingLevel;$d>$HeadingLevels[$c];$d--)

		{	$Toc.="<\/UL><\/LI>\n";}

		# Write a contents line

		$Toc.='<LI><A HREF="#'.$HeadingLabels[$c].'">'.

				$HeadingTexts[$c]."<\/A><\/LI>\n";

		$PreviousHeadingLevel=$HeadingLevels[$c];}

	# Outdent fully

	for($d=$PreviousHeadingLevel;$d>1;$d--)

		{	$Toc=~s/^(.*)<\/LI>(.*?)$/$1<\/UL>$2/s;}

	# Remove null links

	$Toc=~s/<A HREF=\"#\"><\/A>//g;

	# Finish off table of contents

	$Toc.="<\/UL>\n<!--TableOfContents:End-->\n";

	# Replace old table of contents with new, or put at top if no old one

	if(!($Html=~s/<!--TableOfContents:Begin-->\n

			.*?

			<!--TableOfContents:End-->\n

			/$Toc/sx))

	{	$Html=~s/(<BODY.*?>)/$1\n$Toc/is;}

	# Write data back to the file

	open(FILETOPROCESS,'>'.$From)||

			die("Cannot open $From to write.");

	print FILETOPROCESS $Html;

	close FILETOPROCESS;}

###############################################################################

# MarkHeading

###############################################################################

# This works out a heading number for a heading, adds the heading to a 

#  list and creates an anchor in the heading

###############################################################################

# Parameters

#  1: The text of the heading.

#  2: The level (1-9) of the heading.

# Returns

#  A label to use for the HTML anchor.

###############################################################################

sub MarkHeading

{	my ($HeadingText,$HeadingLevel)=@_;

	# Paranoia

	$HeadingLevel=1 if($HeadingLevel<1);

	$HeadingLevel=9 if($HeadingLevel>9);

	# Work out heading number (add at current level & trim after)

	$HeadingCount[$HeadingLevel-1]++;

	@HeadingCount[$HeadingLevel..8]=(0)x9;

	my $HeadingNumber=join('.',@HeadingCount[0..($HeadingLevel-1)]);

	# Create a label

	my $Label='Section_'.$HeadingNumber;

	# Remove any HTML tags from the heading text

	$HeadingText=~s/<.*?>//gis;

	# Store the results

	push(@HeadingTexts,$HeadingText);

	push(@HeadingLevels,$HeadingLevel);

	push(@HeadingLabels,$Label);

	# Display progress on screen

	print '-'x$HeadingLevel." $HeadingText\n";

	return $Label;}

###############################################################################
This feature is required for making the mail list in Mozilla Thunderbird contain multiple lines per e-mail (Ex: Sender and date on line 1 and e-mail subject on line 2) like most other e-mails clients are capable of.

See more at:

https://bugzilla.mozilla.org/show_bug.cgi?id=441414
A GUI for Octave.
This is a program as a human mind.
I'd like to have the Archos 5 Internet Tablet code accepted in Linux Kernel mainline development tree.

That means:

* complete Hardware support minus the sgx-powervr part.
We don't really need buttons that commit changes or any of that nonsense, we have a console for that.  What we really need is to have intelligent feedback from Gedit about what's going on with Git, something that's always there for us to see but can be comfortably ignored too.  We can use the console to DO Git things, but why not be AWARE of more things while coding?  Let's improve our workflow by getting Super Git Senses.

Goals:

1. Mark changed lines since the last commit so we can instantly find the code we're working on, just like this: http://1dan.org/gedit-plugins/highlight-edited-lines/ except aware of Git commits.  2. Mark changed files in the file explorer tab too, if possible.

Considerations:

- Remember that undoing or reverting a line back to its original state must unmark the line, unlike the highlight-edited-lines plugin.

- What should happen when we commit in our console then come back to Gedit?

- Perhaps we should also mark changes since the last but one commit (with another colour)?

Does anyone have any further suggestions?  Would you like to see this plugin come to life?  Why not add a few dollars to the bounty?  Or just code the plugin and claim the bounty :)

An extension giving the user an option to skip synchronising the INBOX for an IMAP account in Mozilla Thunderbird.
Get Autocad >=2010 to run in Ubuntu through Wine and fix the related bugs (http://bugs.winehq.org/buglist.cgi?quicksearch=autocad)
integrate the FOSS code review tool called review board to foss factory

for more info about review board:

http://en.wikipedia.org/wiki/Review_Board

http://www.reviewboard.org/news/2010/09/30/review-board-15-released/
The existing GNU/Hurd code should undergo code analysis and formal verification.

http://www.gnu.org/software/hurd/open_issues/code_analysis.html

http://www.gnu.org/software/hurd/open_issues/formal_verification.html

The Related Projects box on the upper right shows a list of sub-projects.

Any contributions to the GNU/Hurd sub-projects are subject to the general

rules/review process.  For certain projects this also includes assigning the

copyright of your changes to the Free Software Foundation.
There are lots of things to be done on the GNU Hurd itself...

http://www.gnu.org/software/hurd/tag/open_issue_hurd.html

The Related Projects box on the upper right shows a list of sub-projects.

Any contributions to the GNU/Hurd sub-projects are subject to the general

rules/review process.  For certain projects this also includes assigning the

copyright of your changes to the Free Software Foundation.
GNU Mach is the microkernel that the GNU/Hurd system is based on.  It's showing its age and could do with some care.

http://www.gnu.org/software/hurd/tag/open_issue_gnumach.html

The Related Projects box on the upper right shows a list of sub-projects.

Any contributions to the GNU/Hurd sub-projects are subject to the general

rules/review process.  For certain projects this also includes assigning the

copyright of your changes to the Free Software Foundation.

Resolve issues uncovered by Perl's test suite, and enabling Hurd-specific features.

First, make the language functional, have its test suite pass without errors.

Next, Hurd-specific features can be added.  Add an interface to the

language/environment for being able to do RPC calls, in order to program

translators natively in Perl.

http://www.gnu.org/software/hurd/open_issues/perl.html

Any contributions to the GNU/Hurd sub-projects are subject to the general

rules/review process.  For certain projects this also includes assigning the

copyright of your changes to the Free Software Foundation.
Make the Google Go programming language available on GNU/Hurd in its GCC gccgo implementation, and enable Hurd-specific features.

First, make the language functional, have its test suite pass without errors.

Next, Hurd-specific features can be added.  Add an interface to the

language/environment for being able to do RPC calls, in order to program

translators natively in the Google Go programming language.

http://www.gnu.org/software/hurd/open_issues/gccgo.html

Any contributions to the GNU/Hurd sub-projects are subject to the general

rules/review process.  For certain projects this also includes assigning the

copyright of your changes to the Free Software Foundation.
Resolve issues uncovered by Python's test suite, and enabling Hurd-specific features.

First, make the language functional, have its test suite pass without errors.

Next, Hurd-specific features can be added.  Add an interface to the

language/environment for being able to do RPC calls, in order to program

translators natively in Python.

http://www.gnu.org/software/hurd/open_issues/python.html

Any contributions to the GNU/Hurd sub-projects are subject to the general

rules/review process.  For certain projects this also includes assigning the

copyright of your changes to the Free Software Foundation.

Make the Ada programming language available on GNU/Hurd in its GCC GNAT implementation, and enable Hurd-specific features.

First, make the language functional, have its test suite pass without errors.

Next, Hurd-specific features can be added.  Add an interface to the

language/environment for being able to do RPC calls, in order to program

translators natively in Ada.

http://www.gnu.org/software/hurd/open_issues/gnat.html

Any contributions to the GNU/Hurd sub-projects are subject to the general

rules/review process.  For certain projects this also includes assigning the

copyright of your changes to the Free Software Foundation.

The goal of this project is to encourage and reward the work towards solving 7-piece chess endgames and making the solution freely accessible to the community.

Currently this project is in the design stage. The structure and requirements are being drafted and discussed by the community, so no submissions will be accepted at this moment. You are welcome to join the design efforts at the EGTB Forum:

EGTB Forum: http://kirill-kryukov.com/chess/discussion-board/viewforum.php?f=6

Project summary: http://kirill-kryukov.com/chess/discussion-board/viewtopic.php?f=6&t=5815

General Discussion: http://kirill-kryukov.com/chess/discussion-board/viewtopic.php?f=6&t=5811

If you are sure that this project will benefit you, feel free to already contribute funds.
I'm looking to modify the Postie plugin for Wordpress specifically to handle an attached Image to work with my particular theme. To work with my theme I need the attached image to be set to the "Featured Image."

Postie plugin for Wordpress is a method to create wordpress posts via email. At this time I'm only looking to modify the way image attachments are handled.

FOSS Factory projects

test

open source version of seedio

Ubuntu on Samsung 900X3C

JULIA: Jim's Ultimate Language Interpreter Architecture

OpenAL Head Tracking support

Aptitude package manager: problem resolver

Aptitude package manager: general development

Wormhole

Pocket bank

PostgreSQL: Fix table inheritance caveats.

ResourceSpace Checkmail Plugin

FLAC Cast

Modify a PERL script that generates a TOC

Rich Content in XUL Treerows (Mozilla bug #441414)

GUI for Octave

Auto system improvement plugin

Archos 5 Internet Tablet

Super Git Senses (Gedit Plugin)

Skip IMAP Inbox in Thunderbird

get Autocad >=2010 to run in Ubuntu

integrate review board to ff

GNU/Hurd: container for code analysis, formal verification work

GNU/Hurd: container for general GNU Hurd work

GNU/Hurd: container for general GNU Mach work

GNU/Hurd: foster Perl programming

GNU/Hurd: enable Google Go programming (GCC: gccgo)

GNU/Hurd: foster Python programming

GNU/Hurd: enable Ada programming (GCC: GNAT)

7-piece Chess Endgame Analysis - Tools, Tables, Infrastructure

Postie Plugin Wordpress Hack