On Tue, 16 Oct 2007, Klaas Freitag wrote:
on behalf of Adrian I am happy to annouce our roadmap for the upcoming openSUSE Buildservice development here:
http://en.opensuse.org/Build_Service/Roadmap
It outlines the development targets until Q4 2008.
We're happy to get your feedback,
One very essential thing I missed in your roadmap. This is i18n and l10n. - How to handle translations? - Will it be possible to add translations for SPEC files, package descriptions, ...? - When openSUSE moved to BS servcie completely, how will the suse translation effor be integrated? - How can Buildservice translation (if they come) be integrated with upstream translations. - How to forward translations upstream ... I already had some trouble regarding this topic with main distribution and my own packages so I know this is a major topic. Currently the buildservice is not 1.0, so I accept many things, but a final product also needs a nearly 100% translation support. - All buildservice parts must be translatable. - All packages must be translatable if supported upstream. - All packahe meta information must be translatable. A sidenote: It seems rpmlint has translation problems at the moment as well. It seems it checks only current language entries. To get it right, it needs to check every included language. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org