Hi all, during our "Kill YCP" hackweek project [1] we found out that there are many obsoleted modules which are not developed anymore but still have some code in the master branch. This is confusing and might result in unnecessary extra work like - translators might still translate the texts (well, I don't know the process exactly so maybe not...) - refactoring can be harder - you may not remove old function Foo() defined in other module because it seems to be used there, changing a function might require more changes in other modules, etc. - grep in all Yast modules is slower as it has to check also the obsoleted files (well, actually it's that bad...) We marked such modules as "dropped" in our overview table [2]. So if you maintain such a module simply remove all files and put there a README.md file describing the state and the reason for removal. (Create a new branch before removing all files so the last state is available if somebody is interested in it.) If the code is still maintained in SLE11 mention that in the README file. You can look at bluetooth[3] and uml[4] modules to see how it could be done. Thanks! [1] : https://github.com/SUSE/hackweek/wiki/Kill-YCP-by-Mechanical-Translation [2] : https://docs.google.com/spreadsheet/ccc?key=0AqkGTJzxGJv8dFBKQ1JPeU96NWUxMWZ... [3] : https://github.com/yast/yast-bluetooth [4] : https://github.com/yast/yast-uml -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org