[Libreoffice] minutes of tech. steering call ...

[Michael Meeks]

Present:
	+ Norbert, Rainer, Michael, Mitch, Andras, Cedric,
	  Thorsten, David, Bjoern, Petr, Kohei

+ Completed Action Items
        + write substance of what is needed wrt. the extensions
          & templates announce & send to Florian (Andreas)
        + New extensions website: publish / tdf blog (Florian)
	+ give website / commit rights out more diversly (Kohei)
	+ mail details for new repo setup (for libtextcat) to Michael (Caolan)

+ Pending Action Items
	+ create top-level libtextcat repo (Michael)
        + default to TM safe (non-TDF) branding (Thorsten)
        + enable on-line updates for QA for dailies ... (Kendy)
	+ publicise / aggregate our list of ODF proposals / extensions (Thorsten)

* Agenda items
	+ pending action items
	+ Calc row height / font metric change (Eike)
		+ Eike on holiday - postponed to the conference.
	+ openSUSE conf update (Michael)
AA:		+ get Jan's gcc cutting down script (Michael)
	+ Lightning talk brainstorming ... (Michael)
		+ python / debugging annotations (David Tardon)
		+ finding code from the user-interface ? (Kendy)
		+ removing unused code (Caolan)
		+ low hanging UNO performance wins (Thorsten)
		+ interacting with new developer (Michael)
		+ howto setup a tinderbox (Norbert)
		+ running subsequent tests (Bergmann)
		+ how to troll on IRC (Fridrich)
		+ how to find out what is going on (for beginners) (Bjoern)
		+ debugging gnumake effectively (Norbert)
		+ opening visio documents (Fridrich)
		+ writing good commit messages (Petr Mladek)
	+ release bits (Petr)
		+ Cor's regression bug fdo#40590
			+ came from merging a CWS calc-showstopper
			+ regression vs. 3.3, fixed in 3.5
		+ most people working on master
		+ no more fixes for 3.3 committed so no new release planned
	+ Documenting Extension guarentees (Stephan)
		+ currently no written rules on guarentees for extension
		  developers. Can create problems for both them and us.
		+ cf. unoapi.dll query this morning
		+ 2-3 things:
			+ clear story - do we want compat across
			  versions: major, minor, micro, etc.
			+ getting ext'n devs involved in the process
			+ and/or monitor / survey ext'ns closely
		+ problems monitoring non-open-source ext'ns (Norbert)
		+ have snippets for regression testing from ext'n devs (Thorsten)
		+ best sol'n for compat with ext'ns on Windows: re-use stlport
		  solution, distribute 3.4 sal, but not link to it (Fridrich)
		+ address on an ad-hoc basis, or be explicit ? (Stephan)
		+ writing rules not a very good approach (Michael, Norbert)
		+ discuss whether we want C++ components in 4.0+ (Michael)
		+ at conference - find who is using it, and why ? (Bjoern)
		+ defer to discussion in/post Stephan's talk at LibOCon.
	+ QA update (Rainer)
		+ nothing exciting to report
		+ bug reporting assistant going well
		  https://bugassistant.libreoffice.org/libreoffice/bug/bug.html
		+ can provide version + component from "Help->File bug"
		+ Lior moving javascript to 'website' git module ...
		+ filing bugs vs. master - is it a good idea
			+ regression bugs should be sent as E-mail to dev list (Fridrich)
			+ closing lingering bugs a problem otherwise (Bjoern)
		* Agreed - regression bugs in master vs. last-stable should
		  be sent to list with [regression] subject.
	+ when to run tests (Bjoern)
		+ how to reduce unit test time taken in incremental
		  developer builds
AA:		+ discuss this next time

-- 
 michael.meeks at novell.com  <><, Pseudo Engineer, itinerant idiot