What, if any, issues currently make it harder for you to contribute?
zimluura: just recently the freeform car models list has made it drastically easier for me to contribute. so i'm very happy atm. something that could be good is to code a way to mirror suspension .car setups from l -> r would make for a briefer .car file, and less chance of bugs creeping in the data entry side
thelusiv: lately, data formats have been changing a lot and my branch gets out of sync with what's in the data repository.
Venzon: besides lack of time, lack of (up-to-date) prioritized bug/task list
What, if any, changes would make it easier for you to contribute?
thelusiv: do more branching. whenever new major features or refactoring is done, make a branch, and also branch the data repository at the same time.
_nan_: i think i should stop working on mulltiple things at once, but the temptation is great and the resistance is low
Venzon: an issue tracker would be nice, although maintaining it can be a pain, which is why i stopped maintaining it... maybe what would help is better integration between our SVN repos and the issue tracker so we can automatically make issues or update issues from checkin notes
What is the best way to encourage contributors to continue?
thelusiv: remove any barriers which are hindering their work or making it less enjoyable for them.
zimluura: you're going to hate me...but for _nan_ to keep implementing new cool features that break the old data.
_nan_: adress/prioritize their issues
There was some side discussion here:
_nan_: i am the source of the issues, i gues i abstain
Venzon: well, by making it easier for zim you made it harder for thelusiv :-)
thelusiv: _nan_: i don't blame you. we don't have a way to deal with data format changes easily right now. this has been a problem before too
Venzon: thelusiv, did you branch the data repo when you started your branched code?
thelusiv: Venzon: as far as i know, the data repo has never been branched.
