Suggest agenda items for Oct 1st dev chat
WordPress RSS Parsor SimplePie Ceases Development, Matt, demetris, and 14 others are discussing. Toggle Comments
Apparently SimplePie development is ceasing. This will (eventually) impact WordPress if someone doen’t keep SP alive somehow. Perhaps we want to be involved in that?
Interesting development considering Magpie support in WordPress was being phased out due to the lack of development in favor if SimplePie.
WordPress inclusion is kiss of death for RSS parsers.
So which one should we choose to kill of next 😉
Anyone got any ideas!
Automattic can take over development of SimplePie maybe. No reason to search for other and better parser.
SimplePie will most likely live on, Ryan McCue has stated that he’ll attempt to keep bug-fixes up to date time-providing, And I’d be surprised if someone else doesn’t step up to continue development..
Whilst i cant be sure since no-one knows.. I don’t see SP rotting away to nothing in the near future, Worst case scenario is that some WordPress folk might have to occasionally patch some bugs here or there, or add some much needed support for a feed-type.. Given its pretty well written and pretty stable atm, Its probably not going to need much work in the near future, And when(if) it does start dying, there’ll be another project poping up which will supersede it anyway..
Oh, that’s just lovely…
Well, SimplePie is used enough that somebody will probably pick it up and continue making improvements. However, if that doesn’t happen for a while, then we can just leave it be. It’s not really critical functionality, RSS and ATOM feed structures don’t change a whole heck of a lot anymore.
So, my vote is to just stick with the latest SimplePie, roll in security patches (if there are any), and other than that pretty much just leave it alone until some other project becomes the defacto.
Then we kill that one too. 😀
Automattic should fork it and make it rsspress. 🙂
I’d say you stick with SimplePie. I don’t think there are any good alternatives really. Github is really good for this kind of stuff so you might as well do a wp fork if hehe.
As one of the (ex) developers of SimplePie, I’ve started a fork at http://github.com/rmccue/SimplePie
I’ve fixed 2 bugs which might have been major for some people, as Geoffrey pointed out to me, and I’m in the process of transferring all the open bugs over to GitHub’s issue tracker.
That said, I don’t have a lot of time, so I’d appreciate any help.
I’m hopeful that I might be able to get the SP domain name from Ryan Parman in order to continue development, but I don’t currently have the money to renew the domain if needed, and my hosting would die if I hosted the site on my server.
I’m happy to donate domain registration and free hosting.
Thanks Matt. I’ve sent an email to Ryan Parman about maintaining the project officially.
I’d be happy to donate the domain name whomever wants to take over development. SimplePie is currently integrated into WordPress, Joomla, MODx, SilverStripe, DokuWiki, and a ton of other third-party projects. In an ideal world, I’d love to see at least a small investment of engineering resources from each of these projects toward giving SimplePie a future beyond Geoffrey and I.
If there’s any interest in this, please let me know. A few other folks have expressed interest in getting involved, but there’s needs to be a “point man” to maintain the long-term vision for SimplePie and coordinate efforts.
Ryan M. has stepped up, but he’s said he doesn’t have a lot of time. If anybody else has the time or resources to invest, please let me know so that we can put a plan together over the next few days/weeks.
Matt, I’ve sent you an email regarding this.
[…] The WordPress development team is well aware of this announcement and it looks like it may be a topic of discussion for this weeks WordPress development meeting. […]
How about a discussion about what WP / Automattic can do to make the Plugin Repository more secure, and help prevent insecure plugins from being installed? The bar seems like it’s been lowered far enough now that you can Add plugins directly from your self hosted WordPress site in a few clicks.
Whether is a solution going forward, or a retroactive solution, some sort of plans should probably be discussed.
Yes, I’d like to talk about a group of community members who could give plugins a once over before it is allowed to be added to the repo. See http://www.wptavern.com/is-a-plugin-validation-team-a-pipe-dream
This would also make sure that people couldn’t request hosting without intention of hosting on wp.org but for use as a placeholder, which I know developers who sell plugins do.
also to discuss linking methods within description, installation, FAQ, and help pages for the plugins.
NOTE: to talk about how external links are handled
I have a feeling that a topic like this could easily take up the entire hour and would probably be best discussed as an entirely separate meeting. But worth a shot.
Your patch to the bug you “fixed” the other day breaks quite a few of my plugins, and I fail to see why Andrew’s patch isn’t worth committing on the spot.
I’d like to propose for discussion the idea of a page (in the admin area, or in wp.org or in both) that credits all third-party projects used in WordPress. I think it’s something lacking from WordPress and it would be a nice gesture of acknowledgment to those whose work benefits WordPress. If other people like the idea, I’m willing to do the work for this.
There is a also the issue of properly crediting individual contributors to individual releases, but I think this should be a separate discussion, maybe in the context of trying to generally improve WP release notes.
Something else I was thinking about was a way to track compatibility of at least some prominent, popular plugins (and maybe themes?) with upcoming versions of WP. — This could be a resource maintained by a few users of pre-beta development versions of WP and it could help plugin authors to find out about issues with enough time to work on them.
I’ve made a spreadsheet in Google Docs to help me visualize the idea and to see whether this could be done in a simple, easy way:
[…] gibt es schon jetzt dazu, bis hin zur obligatorischen Namensänderung zu RssPress. So wie es in den Kommentaren zum DevBlog von WordPress aussieht, wird die Weiterentwicklung von Ryan McCue übernommen. Aber auch Ryan denkt […]
As suggest by Jane I am adding IRC Ops to the discussion again, perhaps as more of a task than a discussion.
[…] Ryan McCue, an ex developer of SimplePie, has created a new fork and he and Matt Mullenweg are trying to pick up the SimplePie domain name. (Mullenweg has offered […]
← September 24 dev chat agenda: -Plugin di…
Image Editor →
Subscribe to this blog and receive notifications of new posts by email.
Join 5,546 other subscribers