Displaying 1 To 10 Of 10 Comments New WordPress Resource – Patches Welcome Thanks for the link Jeff. At the moment “Patches Welcome” is a personal experiment. I’d love to get more people involved and I specifically didn’t buy a domain for this project but just started a WP.com blog because I agree if it takes off it probably belongs somewhere on the much expanded WP.org site. Once we have seen how it plays our and how 3.org plays out I wouldn’t be surprised to see the content move elsewhere and continue to grow. » Posted By westi On July 26, 2010 @ 1:43 PM Is A Plugin Validation Team A Pipe Dream? This is something I have been musing for a while and don’t think it is something that should necessarily be a centralised thing which is done by a team. I think we need to build into the work-flow more social/community features so that: It is really easy to report an issue to the person that can fix it – i.e. the plugin author I would like to have the time to review more plugin code as I think the best way the community of developers can learn and the code quality can improve is constructive feedback and best practise documentation. In my wildest dreams I would like to dedicate as much of my time as possible on making plugins better – but some things, like $dayjob and earning money, get in the way! » Posted By westi On October 1, 2009 @ 3:43 PM Supported Legacy Branches For WordPress.org? In my experience I don’t think the coloured update system will ever work. A long time ago before WordPress had built in notification or upgrade support there was a similar type of worm going round and lots of people hadn’t upgraded. At the time, as a community member, it saddened me and I did something positive to try and help the situation – http://blog.ftwr.co.uk/archives/2005/06/27/wordpress-version-check/ I created a plugin to provide an update notification and that plugin had a colour coded update message and even pointed you to the codex page about alpha code being not supported if you were brave enough to be running trunk. The things I learnt: Colour coding and flashing beacons don’t make people upgrade quicker – they just create noise and make you complacent when it isn’t red and flashing. » Posted By westi On September 23, 2009 @ 4:17 PM Who’s Responsible For Keeping Your WordPress Site Up To Date? @Jeffro – Unfortunately not! Just some snarky humour. If only we could remote upgrade everyone … » Posted By westi On September 16, 2009 @ 10:13 AM Of course it should be matt. He should just click the one sekrit upgrade all button and upgrade every WordPress install in existence. </snark> » Posted By westi On September 16, 2009 @ 8:04 AM Ideas To Improve The WordPress Release Strategy Regarding the concept of a WordPress Threat Level – This is something really hard to define. It is rare that a security fix is so cut and dry that you can make one of these level based statements – and if you do prepare to be shown by the ingenuity of the crackers themselves that you were wrong – it is very hard to identify all the ways in which a security bug that is fixed can be exploited! » Posted By westi On September 16, 2009 @ 5:26 PM Does Scheduling Posts Freak You Out? @Oliver Schlöbe – This enhancement will be in 2.9. » Posted By westi On September 2, 2009 @ 3:10 AM Here you go Jeff – no more freaking out for you: http://core.trac.wordpress.org/changeset/11897 Will now display: (Page|Post) scheduled for: Sep 23, 2009 @ 22:12. Preview post » Posted By westi On September 1, 2009 @ 5:16 PM A canonical plugin would be a plugin maintained by the community which would effectively be the recommended solution for whatever the plugin provided a solution to. These plugins would be tested alongside new WordPress releases to ensure that they are compatible. This allows for new chunks of functionality to be developed that are wanted by a section of the community without impacting the users who don’t want this functionality. It will also allow for those plugins to be updated on a different release cycle if required. » Posted By westi On July 8, 2009 @ 2:29 AM TalkPress bbPress Domain Dilemma Firstly bbPress and TalkPress are explicitly different things. It was an unfortunate mistake IMHO to name the hosted WordPress solution WordPress.com, a large portion of people just don’t see or understand the difference between WordPress.com and WordPress.org and support questions get sent the wrong way for both. It is good to see the seperation in branding between install it yourself (bbPress) and hosted (TalkPress). While I agree is is good practise to try and get all the relevant domains for your brand there are other issues at stake here too. The bbPress name fits well into the *Press family. » Posted By westi On May 28, 2009 @ 5:18 PMComments Posted By westi
It is really easy to keep track of the developments on a plugin – there are feeds etc which can be leveraged (http://blog.ftwr.co.uk/archives/2009/09/10/feeding-on-feedback-and-progress/) but it would be nice for this to be even easier.
People still ignore the update messages – There are people out there still running my plugin in WordPress 1.5.2 installs – now that is what I call ignoring upgrade messages
«« Back To Stats Page