2. Version 2011-10-15 (Gold)

4. A new Windows installer

5. Playing nice with the StarOffice legacy ecosystem

6. Developers, developers, developers

7. Windows as a “vendor” I guess Microsoft will not join TDF but...

9. Build customized and branded versions of LibreOffice

10. Offer support and convenient way to distribute and update it

11. Marketing about their product and that includes LibO

12. Have dedicated developers working in LibreOffice fixing bugs and add new features their customers want

13. This model works very well

16. No companies are migrating Windows users to LibO

18. No real FOSS / collaboration culture

19. Lack of proper channels to canalize this support (“I am a company and I want to support the Windows build, how can I do it?”)

22. An umbrella where small and big companies can feel at home

23. Bugs, feature requests

24. Marketing

25. A small company migrating Windows desktops can't afford to have a dedicated developer, but maybe 20 companies can.

26. Make it very easily for companies with no FOSS culture to join the effort

28. We have already won the Linux/BSD market

29. The StarOffice legacy ecosystem will concentrate on Windows and (probably MacOS X too)

30. We need to clearly show the outside world that we do really care and we are serious about it

31. We also need to clearly show that the other platforms are still very important and they always be

32. A new Windows installer... If it works why do we have to change it?

34. Why are we leaving temporal files in the desktop?

35. Not optimal for large deployments in corporations

36. On Windows the installer is the first impression you get of an application

37. UTF-8 stuff, etc.

38. But... I think there's a more compelling reason...

40. We need a new nice, good-looking and friendly installer to differentiate LibO from the other legacy products

41. We need to involve all the community and especially the design team

42. It will be send a hint to the outside world than we do care about the Windows users and we are working in the right way for them

43. Playing nice with the StarOffice legacy ecosystem Because we are not alone

45. But there's a chance that they do

46. Products will not be installable side by side on Windows

48. Application Ids (COM+ and OLE stuff)

49. Common registry keys

50. File associations (bad clean up code, backup, etc)

53. Let the others be the “bad” guys

54. Some things are trivial to fix

56. Other products will have the same problems

57. But.... let's be the nice guys of the ecosystem

58. Developers, developers, developers (No need to comment about this one)

59. Developers, developers, developers

61. “Dude, where's the Visual Studio project to compile LibreOffice?”

62. Cross-compilation is good, but we have to continue to support the native Windows tools

64. Newest Microsoft SDKs, etc

65. Properly detect all the tools and dependencies, etc.

68. Extensions builder for Visual Studio

69. Known languages for Windows developers to write extensions: C#, Visual Basic, etc

71. Find out more at http://conference.libreoffice.org