Two more easy patches are awaiting commit, for those hunting for top RESLOVED/FIXED position: bugs 33494 and 33496.
Also, with the upcoming migration go GIT, I have a suggestion for another access group: /Skins. I do not really consider the skins/ directory to be part of core or extensions, as skins only relate to the client side.
For that matter, perhaps /Client would be another option, whouch would include both skins/ and resources/; all client-side components of MediaWiki.
On 01/03/2012 05:12 PM, Erwin Dokter wrote:
Two more easy patches are awaiting commit, for those hunting for top RESLOVED/FIXED position: bugs 33494 and 33496.
I'm still on vacation but I have to chime in -- now that those bugs are resolved/fixed, there are 6 easy patches awaiting commit.
25909 Recent changes Add a drop-down list for the tags in Recentchanges and Newpages 10023 Parser Should return http status code 304 NOT MODIFIED appropriately when accessing a &action=raw page 28162 Installation Installer does not respect initial DBport declaration (PostgreSQL) 22770 CentralAuth wrap rights on GlobalGroupPermissions into a CSS class 17099 User interface Red-link “discussion” tab indicated by colour only (Accessibility) 29236 Collection Extension:Collection should copy the book title automatically to the stored "book page" input field
https://bugzilla.wikimedia.org/buglist.cgi?keywords=easy%2C%20patch%2C%20nee...
On Tue, 03 Jan 2012 14:12:52 -0800, Erwin Dokter erwin@darcoury.nl wrote:
...
Also, with the upcoming migration go GIT, I have a suggestion for another access group: /Skins. I do not really consider the skins/ directory to be part of core or extensions, as skins only relate to the client side.
For that matter, perhaps /Client would be another option, whouch would include both skins/ and resources/; all client-side components of MediaWiki.
Access group, what kind of access group are we talking about?
Individual non-core skins should be separate git repos just like extensions. All with their own individual access setup.
And I'm not aware of any way of adding access-restrictions within a git repository. Especially given the idea of a gated trunk I don't think there should be any sort of access restriction to any individual part of phase3's directory structure.
On 04-01-2012 07:27, Daniel Friesen wrote:
On Tue, 03 Jan 2012 14:12:52 -0800, Erwin Doktererwin@darcoury.nl wrote:
Access group, what kind of access group are we talking about?
Individual non-core skins should be separate git repos just like extensions. All with their own individual access setup.
And I'm not aware of any way of adding access-restrictions within a git repository. Especially given the idea of a gated trunk I don't think there should be any sort of access restriction to any individual part of phase3's directory structure.
By access group I meant commit access. I'm not at all up to speed with how git is going to manage commit access. But since I regularly have patches for skins and site CSS, I wouldn't need access to core if access to skins were seperated from core.
wikitech-l@lists.wikimedia.org