btw, what just happened again with the array to string RFC is exactly one of the top thing I want to implement, block edition during voting phases and add notification if modifications are done afterwards, so we know what has changed and can prevent bad changes to land in the core based on a biased RFC, after it was accepted. The 2nd thing is to ensure the minimum discussion period between its announce and the votes, making the wiki sends the mail to internals, on demand, by the author, when he considers it ready to be announced as well as a fixed period for the voting phase. All these steps should be done from the wiki to ensure that nobody screws the whole thing by playing with the rules.
But if some of you like to do it already, please go ahead, as I won't do it unless I get the data to double checks everything with production data. On Thu, Mar 19, 2015 at 11:55 PM, Peter Cowburn <[email protected]> wrote: > > > On 19 March 2015 at 12:13, Pierre Joye <[email protected]> wrote: >> >> >> On Mar 19, 2015 6:28 PM, "Peter Cowburn" <[email protected]> wrote: >> > >> > >> > >> > On 19 March 2015 at 10:56, Pierre Joye <[email protected]> wrote: >> >> >> >> >> >> On Mar 19, 2015 5:39 PM, "Peter Cowburn" <[email protected]> >> >> wrote: >> >> > >> >> > Moved discussion to webmaster list. >> >> > >> >> > On 18 March 2015 at 01:30, Pierre Joye <[email protected]> wrote: >> >> >> >> >> >> hi, >> >> > >> >> > >> >> > <snip> >> >> > >> >> >> Now, to be able to actually implement the little technical measure >> >> >> to >> >> >> ensure that everyone follows the same rules, I ask you one more time >> >> >> to provide the data of the current wiki so patches, changes etc can >> >> >> be >> >> >> implemented in a safer way. You know where to reach me to provide >> >> >> it. >> >> >> Thanks for your cooperation. >> >> > >> >> > >> >> > It sounds like you want to work on the wiki, great! >> >> > >> >> > However, I don't really understand why you need "the data of the >> >> > current wiki". Could you elaborate a little on why you need that, rather >> >> > than running your own local wiki copy with your own pages, etc.? >> >> >> >> To valid changes with existing data, especially in the RFCs, votes and >> >> related codes. >> >> >> >> It takes time to create prod-like data and be sure everything works >> >> fine. >> > >> > It takes 5 minutes to copy a few pages' content from the production >> > wiki. 5 more to set up users/admin access in your dev wiki. >> > >> > Then you're ready to run through whatever you're looking at doing: >> > simulating some votes, improving the registration process, improving the >> > patch vs plugin problem, ... >> > >> > Surely that's better than waiting (more than a year!!) for someone to >> > needlessly (IMO) deliver you a copy of the files from production? >> >> It is not about implementing but testing, more intensively or efficiently. > > Fair enough. Testing with production (or production-like) data is a good > idea after all. >> >> Anyway, I am not going to argue endlessly about that. Right now we have no >> way to get a hand on that box or the data without requesting, if not >> begging, for it. > > How else, other than requesting it, would anyone (without previously > arranged direct access) get a hand on that box or data? The problem isn't > that we have to ask other people who do have the privilege of access to > machines/data, the problem is a lack of people with those privileges (i.e. > *able* to help) and who are *willing* to help. > > In this case, the list of people able to help is very small to start with > which is being further hampered by an unwillingness to help. I can only see > one solution: give more people access to the machine. Being blocked because > one person can't (i.e. they got run over by a bus) or isn't willing (as in > this case?) to help out, is pathetic. We're all volunteers and want to get > stuff done! > >> >> I have enough of that. Let me know when things are sorted out and I can >> actually begin. Until then, I have other things to do. Not really your fault >> and I am in no way blaming you but someone having numerous personal issues >> about either the wiki, RFC or myself is getting in the way to get things >> done as we always do. >> >> > That said, it certainly sounds like we are running low on volunteers to >> > manage the more website infrastucture related things; such as looking after >> > the wiki website, as in this case. What can we do about this? >> >> And it won't get better if most of systems cannot even provide that. >> >> And seriously I won't do anything until I get what I asked. > > It sounds like you're willing to help, but throwing the baby out with the > bath water (as the saying goes) isn't going to help anyone. If you have > something that needs to get fixed/improved with the wiki; either get on with > that, or delegate to someone else, or at least bring it up for discussion. > Stamping your feet and refusing to do *anything* (which is what looks to be > happening here) isn't helping anyone, you know that. > >> >> >> >> In any case, it has been more than a year now that I asked for that. >> >> Given that I and Lukas introduced the wiki, the RFCs and co to increase >> >> cooperation and reduce conflicts, I find the current situation amazingly >> >> disturbing. This is not acceptable. >> >> >> >> Cheers, >> >> Pierre >> > >> > > > > So, who all does have access to the wiki machine?.. The wiki only lists > Hannes, and Pål-Kristian (machine provider). > -- Pierre @pierrejoye | http://www.libgd.org -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
