On Dec 16, 2007 6:20 AM, Jan Zerebecki jan.wine@zerebecki.de wrote:
For me with this renaming is important that at least from the description it should then be absolutely clear what goes into a component and what not (for a developer).
On Sat, Dec 15, 2007 at 09:27:52PM -0700, Vitaliy Margolen wrote:
What's happened to the proposal to remove the wine- prefix from bugzilla components and have the components represent the dlls they belong to?
I didn't want to remove the wine- prefix without also getting most of the other wanted changes done in the same go. But those require that someone gets a list of the exact changes posted and agreed upon on. I didn't have time for that yet... but if none of the other admins get it done I can probably find the time to make the changes in such a list.
I think such a list would need: old name (empty for new components); new name; description (should list other names that are associated with the component or things contained in the component, list of source files that this component contains with bash style globs).
We can also change the default assignee (currently wine-bugs@winehq.org for all components) and/or default cc list (AFAIK currently empty for all components).
Possibly bad example: wine-directx-dshow; directx-dshow; DirectShow ( dlls/{quartz,msdmo,qcap}/ ); dshow-hacker@test.test; dshowhacker2@test.test, dhowhacker3@test.text;
If we want to move all the bugs from one component to other components we can delete the component after it doesn't contain any bugs anymore:
wine-foo; deprecated-foo; Bugs in this component should be moved to bar or misc.
This would be really nice, however not sure how much work will it take. Don't think bugzilla supports renaming of the components. Might need some custom converter.
Bugzilla supports renaming components.
Ok, I'll start off the list. This is a first draft, open to changes and discussion. Entries with a (?) means I'm not sure.
Components:
test -> wine-advapi32 -> advapi32 wine-atl -> atl wine-binary -> wine-comctl32 -> comctl32 wine-console -> console (?) wine-crypt32 -> crypt32 wine-dbghelp -> dbghelp wine-debug -> wine-directx* -> directx* (?) wine-documentation -> documentation wine-dos -> dos wine-dotnet -> (?) I have a feeling this should be a keyword wine-files -> wine-gdi-(printing) -> wine-gdi32 wine-gdiplus -> gdiplus wine-gui -> wine-help -> hhctrl. the remaining wine-help bugs should be user32 if they're not hhctrl. wine-ipc -> wine-kernel -> kernel32 wine-loader ->loader wine-misc -> misc or default wine-msi -> msi wine-msvcrt -> msvcrt wine-msxml -> msxml(3) wine-multimedia -> wine-net -> wine-ole -> ole wine-opengl -> opengl keyword (?) wine-patches -> wine-ports -> wine-programs -> programs (might want to keep it wine-programs to not confuse users) wine-quartz -> quartz Wine-Rebar -> bugs moved to comctl32 wine-resources -> wine-richedit -> richedit wine-setupapi -> setupapi wine-shdocvw -> shdocvw wine-shell32 -> shell32 wine-sspi -> (?) I prefer individual modules with a security or sspi keyword, but it's not up to me wine-tools -> (?) wine-urlmon -> urlmon wine-user -> user32 wine-usp10.dll -> usp10 wine-winelib -> wine-x11driver -> x11driver -> wininet -> wintrust -> secur32 -> advpack -> hhctrl -> imagehlp -> shlwapi