[asdf-devel] I'm too busy right now to be able to do a good job with ASDF
Hi, As you've all no doubt gathered, my time is hardly mine own these days and this looks to be a problem for at least the next six months. I've been living under the illusion that some personal stuff would be getting simpler sooner but I'm realizing that that is _not_ going to happen. sigh. So it's with regret that I need to say that I'm hardly the one to be doing ASDF maintenance and development right now. I'm happy to share the commit bit with those that would like it and hope to keep my hand in occasionally. I won't, however, be able to do anything at all far reaching. Enjoy! -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter
I volunteer for the commit bit. I won't do anything far-fetching with ASDF, but I will * merge the ECL patch * accept contribs outside of asdf.lisp itself (e.g. for TEST-OP and DOC-OP). * try to improve ASDF: * make it use a configuration file https://bugs.launchpad.net/asdf/+bug/485918 * make it able to upgrade itself https://bugs.launchpad.net/asdf/+bug/485687 * try to keep asdf.lisp itself small and recommend that unnecesary features should be put in contribs instead. * probably not work on anything but the above, so other maintainers with commit bit may be needed for these. I promise not to commit anything to the official repository that isn't positively reviewed by at least someone else on the list. I promise to not commit anything that is negatively reviewed, unless there's a rough consensus of positive reviews that says it should be done nonetheless. Good luck with your endeavours, and thanks for recognizing you don't have time as a maintainer. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The people cannot delegate to government the power to do anything which would be unlawful for them to do themselves. -- John Locke, "A Treatise Concerning Civil Government" 2009/11/27 Gary King <gwking@metabang.com>:
Hi,
As you've all no doubt gathered, my time is hardly mine own these days and this looks to be a problem for at least the next six months. I've been living under the illusion that some personal stuff would be getting simpler sooner but I'm realizing that that is _not_ going to happen. sigh.
So it's with regret that I need to say that I'm hardly the one to be doing ASDF maintenance and development right now. I'm happy to share the commit bit with those that would like it and hope to keep my hand in occasionally. I won't, however, be able to do anything at all far reaching.
I volunteer for the commit bit, as well, as back-up to Faré. I'm primarily focused on documentation right now, but have some pending patches (notably "clean-op") on the back-burner. I suggest we also solicit a git-wizard to own the commit bit, as well, in case we need to do some funky rebasing or something like that. Best, r
Faré wrote: ...
* try to keep asdf.lisp itself small and recommend that unnecesary features should be put in contribs instead.
Do we have a protocol for loading ASDF that ensures that by virtue of loading it "authorized" contribs (i.e., contribs distributed with ASDF) will also be loadable. One of the reasons I liked having asdf-binary-locations folded in is that it has been a pain to get all my colleagues to have this critical contrib. I'm happy to see asdf be kept slim, but not at the expense of having people need to pull a large number of different repositories or tarballs to get a full environment running. Similarly, I would prefer to have ASDF not fall into the SLIME trap. SLIME configuration seems to involve mastering an ever-changing number of contribs to get the features you really want.... [Hm. Now that I've typed all this, I wonder if I'm actually saying "I'd rather not work too hard to keep asdf itself small."] Best, r
Robert Goldman writes:
Similarly, I would prefer to have ASDF not fall into the SLIME trap. SLIME configuration seems to involve mastering an ever-changing number of contribs to get the features you really want....
Slime is not a good example of a contrib system for various reasons. Though it depends on what you see in a contrib system: I think it's an axis between not-officially-maintained addon code base and plugin architecture. Slime is very far on the left side. I suggest trying to get to the right side because it means that you really have to try to get layers right. -T.
Tobias C. Rittweiler wrote:
Robert Goldman writes:
Similarly, I would prefer to have ASDF not fall into the SLIME trap. SLIME configuration seems to involve mastering an ever-changing number of contribs to get the features you really want....
Slime is not a good example of a contrib system for various reasons. Though it depends on what you see in a contrib system: I think it's an axis between not-officially-maintained addon code base and plugin architecture. Slime is very far on the left side. I suggest trying to get to the right side because it means that you really have to try to get layers right.
Right. And what's appropriate for SLIME is not appropriate here. ASDF is baked deeply into many systems, so it has to be more conservative, and for it to serve its function it should work with as little configuration as possible (something not generally true of emacs ;-) ). best, r
participants (4)
-
Faré -
Gary King -
Robert Goldman -
Tobias C. Rittweiler