> On Mon, 02 Mar 2015 18:38:46 +0100 > Ladislav Slezak <[email protected]> wrote: > > [...] > > I have some example topics/projects which we could try: > > > > - Improve Yast README files (as discussed in a separate thread) > > > > - Fix yardoc documentation comments. Many Yast modules print > > warnings when building the docs, usually there are typos > > (@return vs. @returns), obsoleted/missing parameters, typos in type > > names... which can be easily fixed without any knowledge of the > > module. > > > > - Convert old tests to RSpec > > > > - Use coveralls for code coverage status > > > > - Use rubocop for checking the code
On Mon, Mar 02, 2015 at 06:46:43PM +0100, Josef Reidinger wrote: > I think it is great idea. Also some bug squashing would be nice to > organize for modules with huge bugzilla queue. ( bug squashing does not > mean fixing bug, just try to reproduce it on the latest distro and if > so, then try to fix it or provide your test env for developer of module Yes, all good ideas. Let's start with the readmes. -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
signature.asc
Description: Digital signature
