Ankur did help out with some development for a while, but I don't think he's been around much lately. If you can code, by all means send an email to Etienne (tiennou7). I'm sure he'd be glad of the contributions, and he really would be the one to talk to if you want an orientation to the code.
As for the rest of us around here, Howard Melman (hmelman) is the author of the unofficial user guide, and Howard and I moderate this group together. Aside from Etienne and the occasional code contributor, we are all just users helping users. Alcor hasn't released the code for all the plugins, but has indicated that he is willing to release the code for individual plugins when requested. So if you want to work on improving a plugin, you can email him about it. Also, note that there are actually two Google Code pages related to Quicksilver. http://code.google.com/p/blacktree-quicksilver/ is really just a bug tracker. http://code.google.com/p/blacktree-alchemy/ is where the real stuff happens. On Jul 25, 9:10 pm, Joshua Bronson <[email protected]> wrote: > Thanks for the info. I'm not familiar with the alcor and etienne you speak > of, but I take it alcor was a core developer who left the project to work > onhttp://code.google.com/p/qsb-mac/, and that ettiene is the real name > ofhttp://code.google.com/u/tiennou7/(whose activity > onhttp://code.google.com/p/blacktree-quicksilver/is apparent enough)? If you > feel like providing a bit more of the Who's Who In Quicksilver (including > yourself!), would be interested to know. :) > I just stumbled acrosshttp://lipidity.com/apple/cleaning-up-quicksilver/, > and it seems like this Ankur is another player in this, or at least was... > The most recent post,http://lipidity.com/apple/the-state-of-quicksilver/, > is dated > 11/28/08. Judging by the comments on his blog though, there seems like > sufficient community interest in contributing code and/or money > to keep the project going. Would be happy to contribute some or both myself! > > Could anyone provide a bit more insight into Quicksilver's roadmap, so that > e.g. someone interested in getting started contributing could have a sense > of what needs to get done first to move the project forward? Or if it's a > case of Just pick something > onhttp://code.google.com/p/blacktree-quicksilver/issues/listand have at it, > fair enough. > > One thing I volunteer to do straight away if there is interest on the part > of the project owners is to add some "Interested in contributing? Here's > how..." mojo to the project's wiki. Once I figure that out. :) > > Thanks, > Josh > > > > On Fri, Jul 24, 2009 at 2:14 PM, nontoppo <[email protected]> wrote: > > > Trunk is largely dead IIUC - alcor went off to work on QSB, and > > etienne is maintaining B5X over trunk - though I noticed etienne > > recently commiting lots to crucible, which is the new core library > > that was going to go into QS trunk. > > > B5X has substantial fixes for Leopard (triggers etc.), folded in lots > > of changes made to reduce memory use and "bloat". But etienne only has > > partial access to plugin code so can only do so much; alcor still > > hasn't released some of the plugin code. Some fixed plugins are > > available here: > > >http://code.google.com/p/blacktree-elements-public/downloads/list > > > etienne is the only real person working on code at the moment, > > including fixing things up for snow leopard etc.
