Folks,
I think I'm down to having two 30 minute holes.
The schedule should now be starting to be visible here: https://fosdem.org/2014/schedule/track/wine/
Pipelight and a 'user focused topic' are going to go in until 11:30.
I've got mingw-64 going in from 3:30 until 4:10 or so.
That leaves me a 30 minute gap in the morning, and a 40-50 minute gap in the afternoon.
Vincent was willing to be made to do a Mono talk again, but I think it'd be a mistake to make that more than a few minute cry for help.
So, anyone have an itch?
I was thinking of doing a brief make test / winetestbot review for 30 minutes. Anyone willing to lead that?
Michael, you've got to be able to do something funny and fun about being a janitor, right?
Austin, anyone, want to talk about bugs or appdb?
Cheers,
Jeremy
On 01/08/2014 01:53 PM, Jeremy White wrote:
Folks,
I think I'm down to having two 30 minute holes.
The schedule should now be starting to be visible here: https://fosdem.org/2014/schedule/track/wine/
Pipelight and a 'user focused topic' are going to go in until 11:30.
I've got mingw-64 going in from 3:30 until 4:10 or so.
That leaves me a 30 minute gap in the morning, and a 40-50 minute gap in the afternoon.
Vincent was willing to be made to do a Mono talk again, but I think it'd be a mistake to make that more than a few minute cry for help.
So, anyone have an itch?
I was thinking of doing a brief make test / winetestbot review for 30 minutes. Anyone willing to lead that?
Michael, you've got to be able to do something funny and fun about being a janitor, right?
I would prefer to have a discussion session with the Wine package maintainers of the different distributions out there.
Austin, anyone, want to talk about bugs or appdb?
bye michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 2014-01-08 13:53, schrieb Jeremy White:
That leaves me a 30 minute gap in the morning, and a 40-50 minute gap in the afternoon.
We could have a flamewar about formatting fixes. I think we should just bite the bullet and unify the entire codebase. The basic premise: How often do we run git blame vs how often does a potential contributor have problems due to plain formatting issue.
However I don't know if that would be a particularly appealing discussion for the general public.
On Wed, Jan 8, 2014 at 7:26 AM, Stefan Dösinger stefandoesinger@gmx.at wrote:
... We could have a flamewar about formatting fixes. I think we should just bite the bullet and unify the entire codebase. The basic premise: How often do we run git blame vs how often does a potential contributor have problems due to plain formatting issue.
However I don't know if that would be a particularly appealing discussion for the general public.
I can't make it this year (the conference is coincident with one I need to attend for work), but I'd like to chime in and say it would be nice to have a git pre-commit script that we could offer to people that properly formats patches. I'd say it's at least a good candidate to fill a hole, I know that I'd be interested in tuning in to it once it's available online ;)
Best, Erich
On Wed, 08 Jan 2014 06:53:51 -0600 Jeremy White jwhite@codeweavers.com wrote:
Austin, anyone, want to talk about bugs or appdb?
I could give an earful of AppDB problems, but whether anyone would be interested is highly questionable.
On Wed, 8 Jan 2014, Jeremy White wrote: [...]
So, anyone have an itch?
I was thinking of doing a brief make test / winetestbot review for 30 minutes. Anyone willing to lead that?
If there's interest I can give a short TestBot status update. Maybe talk about how to automate running WineTest on one's Linux/Windows computer.
But looking at the WineTest results may be too depressing...
If there's interest I can give a short TestBot status update. Maybe talk about how to automate running WineTest on one's Linux/Windows computer.
But looking at the WineTest results may be too depressing...
I have added you to this talk that I entered: https://fosdem.org/2014/schedule/event/wine_test/
I thought I would start with a brief overview of the Wine unit tests, purportedly for non Wine folks, and then sound a cry for help.
It struck me that the most constructive thing that could come out of this topic would be people fixing tests on WineTestBot. Seem fair?
Feel free to suggest that I twist it another direction.
Cheers,
Jeremy