Difference between revisions of "Free Software Directory:Import"
(link to the input and output. ask for someone to help with the next step) |
|||
| Line 1: | Line 1: | ||
| − | + | We have begun the process of importing packages from the main area on Debian GNU/Linux. Right now the process is three steps: | |
| − | the | ||
| − | |||
| − | |||
| − | == | + | * We have a tool (to be published on savannah shortly) that collects package metadata and outputs a JSON file. |
| + | * By hand we clean-up the JSON file, such as removing parts of the description that are Debian-specific and whatnot. | ||
| + | * We then generate a set of wiki files that are then imported into the Directory using a simple import script. | ||
| + | |||
| + | See [[Free_Software_Directory:Import/Debian-2013-03-20|Debian-2013-03-20]] for statistics on our first round of importing from Debian. | ||
| + | |||
| + | |||
| + | == Further work on importer == | ||
* The first challenge is to figure out what trisquel projects correspond to which FSD projects, and which ones have no match in the other database. | * The first challenge is to figure out what trisquel projects correspond to which FSD projects, and which ones have no match in the other database. | ||
| Line 19: | Line 23: | ||
* If/when the flagged revs plugin is installed, then those updates can be approved on a case-by-case basis, to make sure that things match, and nothing is broken. | * If/when the flagged revs plugin is installed, then those updates can be approved on a case-by-case basis, to make sure that things match, and nothing is broken. | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 14:29, 29 March 2013
We have begun the process of importing packages from the main area on Debian GNU/Linux. Right now the process is three steps:
- We have a tool (to be published on savannah shortly) that collects package metadata and outputs a JSON file.
- By hand we clean-up the JSON file, such as removing parts of the description that are Debian-specific and whatnot.
- We then generate a set of wiki files that are then imported into the Directory using a simple import script.
See Debian-2013-03-20 for statistics on our first round of importing from Debian.
Further work on importer
- The first challenge is to figure out what trisquel projects correspond to which FSD projects, and which ones have no match in the other database.
- I've written a program that takes lines of tab-separated fields and returns info about approximate matches. Once the output is generated, people need to go through it and select the correct choice. You can get the input i used and the output it generated in an attachement to the directory-discuss mailing list.
- We need someone to make a javascript interface that lets people choose what they think a correct match is. We'll save those result for the steps below.
- Then, a program needs to read from the Trisquel package database, to gather all of the info.
- malberts was talking on irc about a program (the appnr api used by appnr.com) that downloads apt package info from a repository and then adds the info into a sql database, and offers an api for working with the data.
- Then a program needs to be written to automatically update FSD entries based on the Trisquel data.
- If/when the flagged revs plugin is installed, then those updates can be approved on a case-by-case basis, to make sure that things match, and nothing is broken.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.