On Wed, Mar 10, 2010 at 5:37 AM, Dave Grijalva <[email protected]> wrote:
> I'd be willing to try to pickup the torch from pieter and help keep things > moving, even if i can't contribute much code right away. > Great! > Here are some of the ideas I have to tidy up the work on the project: > - Let's move the website and docs into github pages > - We should be able to use the github downloads feature in conjunction with > gh pages to handle the sparkle feed > - Tickets? Move to github? Takeover the lighthouse project? Other? > - Releases. We need more of them. It might be worthwhile to take a page > from textmate and have a "bleeding edge" and a "stable" feed and let users > choose. > I'd second the GitHub pages idea. I've seen projects make good use of that and hosting the Sparkle feed on GitHub downloads has worked fine for me in the past. On Lighthouse vs GitHub pages, this really depends on the fork we decide to start with. If we go with Pieter's, the Lighthouse project would seem to be a good choice. If we start from Nathan's fork, the Lighthouse project would need a fair bit of updating to reflect all the changes. Another thing to consider here is the ease of the tool. It seems a lot of the projects I've looked into on GitHub prefer Lighthouse. I've no experience with GitHub Tickets so I can't comment further there. Regarding the bleeding edge vs stable thing, this can be done with a single feed. If the user has the option for bleeding edge releases turned off, those items are just skipped when parsing the feed. I'd second this as well though. > There are many divergent forks. We need to do some consolidation. Should > we start from pieter's master and pull in others or is there a better one? > I'll nuke my master and start fresh from whichever one we decide is best. > If you have work that you feel should go into the mainline, please send me > a patch or a pull request. I'll create a bunch of tickets from there so we > can start the discussion. > Let's decide on the fork before asking for patches or pull requests. Once we know where we're starting, we can start integrating the various bits and bobs that are missing. Kevin
