[sldev] Open source meeting call for agenda and info on my first agenda item.

[Robin Cornelius]

Anyone have any items for the agenda for Tonights/This afternoons meeting:-

https://wiki.secondlife.com/wiki/Open_Source_Meeting/Agenda

I have added one item that i would like to hear a little more about 
LLMozLib, i may have added it a bit late for Rob to get Callum involved 
(sorry .. again.. Rob for being so late with my item) . I would detail 
some of the questions here rather that fill the wiki or try to get them 
all out in world, as i have quite a few sub issues on the one topic:-

*) We are seeing the released llmozlib slip behind the version used to 
build released secondlife clients, and even the released secondlife 
source code is requiring newer llmozlibs than we have code for.
- Is there anything that can be done about this?
- Any chance of keeping the llmozlib svn in closer sync with internal 
svn, no idea about your internal svn structure but llmozlib should 
hopefully be nowhere near the server code etc so can it just be kept up 
todate with out too much worring about releasing things you should not.
- Would it be better to host llmozlib on sourceforge etc, so that the 
current version is always in the "wild"

*) Version control
- Can we possible update the version string in llmozlib when its 
updated, it seems to be stuck at 1.1.1
- Any chance of numbering releases instead of using a date as the version
- Can we release a source tarball when things change and a new viewer is 
out and requires it?
- Can we use sonames, eg when you change the library and have ABI 
breakage change from llmozlib0 to llmozlib1 (again the build environment 
should look after the fine details of this, you just need to declare the 
soname version number and remember to increment it where necessary).

*) Build environment
- Are you going to use cmake for llmozlib, a while back i was going to 
look into this myself but still have not had time and don't really want 
to expend effort if you have already done this or its not really wanted.
- Can we have a build environment, currently its a set of instructions 
(again i have previously given example of a autotools build env for linux)

*) Shared library
- Can we build llmozlib as a shared library instead of statically 
linking it as we currently do? (yes it can be done, i do it)
- Can we try to use XULRunner where possible instead of pulling apart 
mozilla trees.

*) Bug tracker
- Is it worth having llmozlib as a component on the bug tracker or even 
have its own bug tracker (if moved to sourceforge for example). I see 
people using the ubrowser mailing list who are playing with llmozlib for 
non secondlife projects

*) Ubrowser.com
- Looks like a project that stopped being worked on in 2006
- May be should link to llmozlib svn and any bug tracker?

Sorry if it sounds like i am going on but these issues I believe all 
need addressing at some point.


Thanks

Robin