Incubator/Projects/kid3: Difference between revisions

From KDE Community Wiki
(Add description and manifest compliance plan)
No edit summary
Line 32: Line 32:


List the actions planned to get in compliance with the manifesto.  
List the actions planned to get in compliance with the manifesto.  
 
* Move bugs from https://sourceforge.net/p/kid3/bugs/ to bugs.kde.org
* Move features to invent.kde.org
* Move discussion to forum.kde.org
* Move website from https://kid3.sourceforge.io/ to kde.org (talk to web team?)
* Ponder mailing list for development?
=== Values ===
=== Values ===


Line 69: Line 73:
!  width=250 | Notes
!  width=250 | Notes
|-
|-
{{FeatureTodo|Project description|...}}
{{FeatureDone|Project description|see above}}
{{FeatureTodo|Project team|...}}
{{FeatureDone|Project team|Just Uri for now}}
{{FeatureTodo|Manifesto compliance plan|...}}
{{FeatureDone|Manifesto compliance plan|see above}}
|}
|}


Line 82: Line 86:
!  width=250 | Notes
!  width=250 | Notes
|-
|-
{{FeatureTodo|Repository and code available (in playground)|...}}
{{FeatureDone|Repository and code available (in playground)|...}}
{{FeatureTodo|Mailing list available|...}}
{{FeatureTodo|Mailing list available|...}}
{{FeatureTodo|Website available (if applicable)|...}}
{{FeatureTodo|Website available (if applicable)|...}}

Revision as of 17:33, 9 January 2020

Spectral

Sponsor: Jonathan Riddell

Kid3 is an audio tag editor supporting MP3, Ogg/Vorbis, FLAC, MPC, MP4/AAC, MP2, Opus, Speex, TrueAudio, WavPack, WMA, WAV and AIFF files. It allows you to easily edit meta data without typing the same information again and again and gives you full control over all tags (e.g. ID3v1, ID3v2 and APE in a MP3 files) and all frames contained in these tags.

Features include:

  • Edit ID3v1.1 tags
  • Edit all ID3v2.3 and ID3v2.4 frames
  • Convert between ID3v1.1, ID3v2.3 and ID3v2.4 tags
  • Edit tags in MP3, Ogg/Vorbis, DSF, FLAC, MPC, MP4/AAC, MP2, Opus, Speex, TrueAudio, WavPack, WMA, WAV, AIFF files and tracker modules (MOD, S3M, IT, XM)
  • Edit tags of multiple files, e.g. the artist, album, year and genre of all files of an album typically have the same values and can be set together.
  • Generate tags from filenames
  • Generate tags from the contents of tag fields
  • Generate filenames from tags
  • Rename and create directories from tags
  • Generate playlist files
  • Automatically convert upper and lower case and replace strings
  • Import from gnudb.org, TrackType.org, MusicBrainz, Discogs, Amazon and other sources of album data
  • Export tags as CSV, HTML, playlists, Kover XML and in other formats
  • Edit synchronized lyrics and event timing codes, import and export LRC files
  • Automate tasks using QML/JavaScript, D-Bus or the command-line interface

Team

  • Urs Fleisch <ufleisch at users.sourceforge.net>

Manifesto Compliance Plan

List the actions planned to get in compliance with the manifesto.

Values

Open Governance

Everyone is welcome to join.

Free Software

GPLv2+

Inclusivity

Currently the facilities at SourceForge are used for bug reports, feature requests and a help forum. Once the project is an active KDE project, transition to the corresponding KDE facilities is possible.

Innovation

Kid3 exists since 2003 and is constantly evolving. It is one of the most feature-complete tag editors. Behind the simple interface, there are features which are unique, for example the editor for synchronized lyrics and time events, support for audio book chapters, a play list editor and automatic batch import from various sources.

Common Ownership

The move to KDE projects is partly motivated by finding others to share ownership with.

End-User Focus

Since the first release in 2003, most features added to Kid3 were driven by requests from end users. It is also a goal of the project to keep a high quality and have the bug report count at zero. Not only Linux and KDE users are targeted, Kid3 is also available as a Linux version without KDE dependencies and for Windows, macOS and Android. As can be seen on the forum and bug trackers, questions and requests from end users are handled rapidly.

Candidate ready

Status Description Notes
DONE Project description see above
DONE Project team Just Uri for now
DONE Manifesto compliance plan see above

Incubating

Status Description Notes
DONE Repository and code available (in playground) ...
TO DO Mailing list available ... <{{{3}}}>
TO DO Website available (if applicable) ... <{{{3}}}>
TO DO Active community ... <{{{3}}}>
TO DO Manifesto compliance ... <{{{3}}}>