Peter Westwood 9:46 pm on September 24, 2009
Tags: agenda ( 995 )

Suggest agenda items for Oct 1st dev cha…

Suggest agenda items for Oct 1st dev chat

#agenda

Beau 9:25 pm on September 26, 2009

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?
- Jeffro 9:13 pm on September 27, 2009
  
  Interesting development considering Magpie support in WordPress was being phased out due to the lack of development in favor if SimplePie.
  - Matt 9:14 pm on September 27, 2009
    
    WordPress inclusion is kiss of death for RSS parsers.
  - Peter Westwood 9:17 pm on September 27, 2009
    
    So which one should we choose to kill of next 😉
    
    Anyone got any ideas!
  - Millan 2:36 pm on September 29, 2009
    
    Automattic can take over development of SimplePie maybe. No reason to search for other and better parser.
- Dion 11:06 pm on September 27, 2009
  
  SimplePie will most likely live on, Ryan McCue has stated that he’ll attempt to keep bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.-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 patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. 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..
- Otto 6:03 pm on September 28, 2009
  
  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. 😀
- nanochrome 8:42 pm on September 28, 2009
  
  Automattic should fork it and make it rsspress. 🙂
- Andreas Nurbo 8:57 pm on September 28, 2009
  
  I’d say you stick with SimplePie. I don’t think there are any good alternatives really. GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ is really good for this kind of stuff so you might as well do a wp fork if hehe.
- Ryan McCue 4:26 am on September 29, 2009
  
  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 GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/’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.
  - Matt 7:04 am on September 29, 2009
    
    I’m happy to donate domain registration and free hosting.
  - Ryan McCue 9:39 am on September 29, 2009
    
    Thanks Matt. I’ve sent an email to Ryan Parman about maintaining the project officially.
  - Ryan Parman 5:09 pm on September 29, 2009
    
    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.
  - Ryan McCue 12:47 pm on September 30, 2009
    
    Matt, I’ve sent you an email regarding this.
Pingback: WordPress RSS Parsor SimplePie Ceases Development
sc0ttkclark 5:17 pm on September 30, 2009

How about a discussion about what WP / Automattic can do to make the PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party 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.
- Matt 7:41 pm on September 30, 2009
  
  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.
  - Jonathan 7:44 pm on September 30, 2009
    
    +1
    
    also to discuss linking methods within description, installation, FAQ, and help pages for the plugins.
    
    NOTE: to talk about how external links are handled
- Jeffro 8:01 pm on September 30, 2009
  
  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.
Denis 7:05 pm on September 30, 2009

https://core.trac.wordpress.org/ticket/10882

Your patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to the bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. 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.
demetris 8:51 pm on September 30, 2009

I’d like to propose for discussion the idea of a page (in the adminadmin (and super 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-betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. development versions of WP and it could help pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party 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:

http://spreadsheets.google.com/ccc?key=0AhDAjUtXxC-5cnN6Nk1odEdkU0tMcDdWdWMza0FKTFE

Cheers!
Pingback: SimplePie Entwicklung gestoppt – bueltge.de [by:ltge.de]
Matt 8:30 pm on October 1, 2009

As suggest by Jane I am adding IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. Ops to the discussion again, perhaps as more of a task than a discussion.
Pingback: SimplePie Ceases Development

Comments are closed.

Welcome!

Communication

Suggest agenda items for Oct 1st dev cha…

Welcome!

Communication

Share this: