[mochikit] Re: Activity
> > Desparately short sighted: if you leave a web site > > untouched for a year, most people will assume its > > dead and move on. In discussions about JS client > > frameworks I've already seen several comments suggesting > > that MK development is dead. > > > How hard can it be to tag the repository and > > update a couple lines of text on a web page? > > It's enough of a hassle. Honestly, I don't care if anyone uses > MochiKit or anything else, they should pick whatever works for them. > MochiKit is not a marketing exercise, I don't do consulting and I'm > not terribly interested in speaking about JavaScript at conferences > right now. We use it, it works great for us. I'd like to do a release, > but I care a lot more about what my company is actually working on > right now. MochiKit hasn't changed much lately because we got it to > the point where it does what we want it to do and we haven't needed a > whole lot else from it. The big mistake that I made was accepting a > bunch of functionality that we had no intention of using internally, > which is what's holding up the release because it doesn't pass quality > control as far as code audit and docs go. I'm not really comfortable > tagging what's in there as a release in its current state. I guess I would argue that looking like a dead project is bad, as it causes people to eliminate perfectly good software from consideration. You may be maintaining it and slowly adding well-considered expansions, but that is not at all apparent to someone looking at frameworks. In short, the web site is misleading. As to the state of the current main trunk - that's up to the maintainers: if it still needs to bake a while, don't tag.But I see that as a separate issue from the 'liveliness' of the web-site. Even if you were to just post some text once a quarter saying "Hey we're still here and working on the next release", it would be a huge improvement. Ross --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Activity
Wouldn't the solution just be to update mochikit.com to indicate that the project is stable, maintained silently in the background and isn't seeking to do active, steady releases due to already fulfilling its original function? A lot of software projects end up growing out of control after too many contributions, and one reason that I personally stick with MochiKit is that it's not constantly being reinvented as something bigger, better, more encompassing. It's also not advertised in the same way as Prototype, et al. In fact, I was more of a fan of MochiKit's "identity" when I first discovered it and the tagline was something to the effect of "MochiKit helps you get shit done, fast"; it sounded more efficient and DIY when compared to the alternatives, and frankly exuded more confidence than "makes javascript suck less". I'd rather get shit done faster than just suck a little bit less. -Kevin --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Activity
On 10/3/07, scipio <[EMAIL PROTECTED]> wrote: > How hard can it be to tag the repository and > update a couple lines of text on a web page? Do you need any specific functionality that isn't in place in MochiKit? At least for me, MK is doing what I need it to do, and as long as there are bugfixes and at least someone responsible for making decisions I'm happy. So I agree with Bob and I think he and the other maintainers are doing a fine job. This discussion pops up here regularly. Why aren't there realeases? People think MK is not stable etc. etc. IMNSHO MochiKit is a relatively small component of webapps and most folks only use specific parts of it - so determining if it's stable in the context of your project is not that hard. Bob, about accepting stuff into MK that you're not comfortable with giving a realease "ok" on, I guess the Selector module is one of those. Unfortunately I haven't had the time to refine it since I started my MSc studies this fall and still doing my day-job. I'm happy to review patches though. As a side note, I'll admit that I find myself looking towards JQuery more often now. Not because I find MK is lacking but because JQuery is good also. Arnar --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Activity
On 10/3/07, scipio <[EMAIL PROTECTED]> wrote: > > > > On Aug 18, 11:59 am, Beau Hartshorne <[EMAIL PROTECTED]> wrote: > > On 18-Aug-07, at 8:44 AM, Lee Connell wrote: > > > > > Mochikit hasn't seen any activity in the revision history at least > > > since 06, is mochikit fading? > > > > We're pretty busy with our own projects, and haven't had much time to > > tag a release. /trunk is very stable, and is updated with features > > and bugfixes regularly: > > > > http://trac.mochikit.com/browser/mochikit/trunk > > Desparately short sighted: if you leave a web site > untouched for a year, most people will assume its > dead and move on. In discussions about JS client > frameworks I've already seen several comments suggesting > that MK development is dead. > > How hard can it be to tag the repository and > update a couple lines of text on a web page? > It's enough of a hassle. Honestly, I don't care if anyone uses MochiKit or anything else, they should pick whatever works for them. MochiKit is not a marketing exercise, I don't do consulting and I'm not terribly interested in speaking about JavaScript at conferences right now. We use it, it works great for us. I'd like to do a release, but I care a lot more about what my company is actually working on right now. MochiKit hasn't changed much lately because we got it to the point where it does what we want it to do and we haven't needed a whole lot else from it. The big mistake that I made was accepting a bunch of functionality that we had no intention of using internally, which is what's holding up the release because it doesn't pass quality control as far as code audit and docs go. I'm not really comfortable tagging what's in there as a release in its current state. If someone is truly interested in being the release manager for MochiKit they can step up and I'd be more than happy to give them full reign. I'll even give them a job (interview, anyway) if they want to move to San Francisco and do front-end work for us also :) -bob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Activity
On Aug 18, 11:59 am, Beau Hartshorne <[EMAIL PROTECTED]> wrote: > On 18-Aug-07, at 8:44 AM, Lee Connell wrote: > > > Mochikit hasn't seen any activity in the revision history at least > > since 06, is mochikit fading? > > We're pretty busy with our own projects, and haven't had much time to > tag a release. /trunk is very stable, and is updated with features > and bugfixes regularly: > > http://trac.mochikit.com/browser/mochikit/trunk Desparately short sighted: if you leave a web site untouched for a year, most people will assume its dead and move on. In discussions about JS client frameworks I've already seen several comments suggesting that MK development is dead. How hard can it be to tag the repository and update a couple lines of text on a web page? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Activity
On Aug 19, 1:59 am, Beau Hartshorne <[EMAIL PROTECTED]> wrote: > On 18-Aug-07, at 8:44 AM, Lee Connell wrote: > > > Mochikit hasn't seen any activity in the revision history at least > > since 06, is mochikit fading? > > We're pretty busy with our own projects, and haven't had much time to > tag a release. /trunk is very stable, and is updated with features > and bugfixes regularly: > > http://trac.mochikit.com/browser/mochikit/trunk Yes, I follow trunk for my own projects, but sometimes it makes it hard to convince people you work with that a project is stable enough to use. Tagging a release would be really helpful, it would allow some of us to make a better case for using it (some people consider mochikit abandonware nowdays after looking at the website) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Activity
On 18-Aug-07, at 8:44 AM, Lee Connell wrote: > Mochikit hasn't seen any activity in the revision history at least > since 06, is mochikit fading? We're pretty busy with our own projects, and haven't had much time to tag a release. /trunk is very stable, and is updated with features and bugfixes regularly: http://trac.mochikit.com/browser/mochikit/trunk --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---