{"issue":{"created_at":"2011-12-14T14:59:38Z","state":"open","updated_at":"2011-12-14T20:57:30Z","comments":3,"user":{"gravatar_id":"4677d4c5787dcef72e251c0e6813fbf5","id":108359,"url":"https://api.github.com/users/publickeating","login":"publickeating","avatar_url":"https://secure.gravatar.com/avatar/4677d4c5787dcef72e251c0e6813fbf5?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"As per the proposal in #649, the current `table` framework needs to be fixed or removed.  I proposed there to remove it and I propose here to bring in the apparent best version and make it an official SproutCore sub-project as `sproutcore/table_view`.\r\n\r\nThis is a rough draft of how I see the official process to occur:\r\n\r\nAs an official sub-project, it will get its own Project Owners, Reviewers and Committers.  It will also get its own README.md and github pull request and issue list.  The README should include at least a standard boilerplate that all sub-project frameworks could share on how to include it within a SproutCore app.\r\n\r\nSub-projects will be reviewed by the main SproutCore project Project Owners between releases.  This proposal could be considered part of the 1.7 release, so the next review would be before version 1.8.  At that time, If the sub-project has too many outstanding issues to be considered stable, or is not compatible with the upcoming release and doesn't show enough support from its team to address these issues, it will need to be removed and live externally again.","assignee":null,"id":2552350,"labels":[{"name":"proposal","color":"02d7e1","url":"https://api.github.com/repos/sproutcore/sproutcore/labels/proposal"}],"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":652,"title":"Bring @endash TableView into official SproutCore sub-project","html_url":"https://github.com/sproutcore/sproutcore/issues/652","closed_at":null,"url":"https://api.github.com/repos/sproutcore/sproutcore/issues/652","milestone":null},"action":"created","comment":{"created_at":"2011-12-14T20:57:30Z","updated_at":"2011-12-14T20:57:30Z","user":{"gravatar_id":"9ae10fb335ecc73d5625a8ffe218b1c4","id":825487,"url":"https://api.github.com/users/workmanw","login":"workmanw","avatar_url":"https://secure.gravatar.com/avatar/9ae10fb335ecc73d5625a8ffe218b1c4?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"We've been using the table for our own application. We've made several performance enhancements and bug fixes, but it's still in rough shape (no offense to @Endash). Amoung other things, could use more unit tests. The endash table makes use of the collection fast path stuff and often requires a little more finis to get working correctly.\r\n\r\nMy fork is here if anyone is intersted: https://github.com/workmanw/endash","id":3149426,"url":"https://api.github.com/repos/sproutcore/sproutcore/issues/comments/3149426"}}