Some newer RfCs that you ought to know about, mostly draft-ish and in progress. Please comment on their talkpages.
* https://www.mediawiki.org/wiki/Requests_for_comment/SOA_Authentication "With many more entry points and the need for inter-service authentication, a service-oriented architecture requires a stronger authentication system." * https://www.mediawiki.org/wiki/Requests_for_comment/Debugging_at_production_... "Sometimes we have to debug on production wiki, but don't want to show internal information to normal users..." * https://www.mediawiki.org/wiki/Requests_for_comment/Unfragmented_ZERO_design "In order to significantly reduce varnish fragmentation and reduce the complexity, Zero team would like to unify HTML served to all Zero partners's users...."
Also: I've heard feedback that the RfC process ought to move faster, and that we ought to have more people from more disciplines take a look at changes that users will visually notice. Sounds good to me. So:
* I'm going to add more IRC discussion hours that will be more for *discussing* specific RfCs and getting general community feedback, rather than asking for go/no-go decisions. These will be in addition to the weekly decision-oriented meetings. It seems like people get a lot out of having these real-time conversations in addition to the option to comment onwiki and onlist, so this is a way to push the most complex topics forward. This will also allow us to have more chats that suit different timezones. We will also sometimes piggyback them onto the videostreamed Tech Talks, with simultaneous Etherpad notes + IRC.
* I'm going to make more of an effort to invite specific people from diverse disciplines to RfC discussions, e.g., QA people for debugging stuff, design/product people for user-visible changes, etc. I've been doing this but I'll be more systematic. Please help me out by spreading the word to people whom you think will be interested.
* https://www.mediawiki.org/wiki/Requests_for_comment/SOA_Authentication "With many more entry points and the need for inter-service authentication, a service-oriented architecture requires a stronger authentication system." This is literally the same thing as AuthStack except more generic and without any code or plan for implementation.
Also, on the same note, I was told previously that the AuthStack RFC was too big and needed to be split up, because I tackled both authentication/authorization *and* session management and logout in the same proposal. Since this RFC has the same problem, it should be split up accordingly.
-- Tyler Romeo 0xC86B42DF
On Mon, Jun 2, 2014 at 5:58 PM, Sumana Harihareswara sumanah@wikimedia.org wrote:
- I'm going to make more of an effort to invite specific people from
diverse disciplines to RfC discussions, e.g.,
[...]
design/product people for user-visible changes
I suggest also inviting actual users for user-visible changes. Not to disrespect Design or Product, but some things are easy to overlook if you're not involved in the day-to-day usage of things.
wikitech-l@lists.wikimedia.org