[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
Excellent Karl, initiatives like this is what makes open source so much fun... -GTG On 8/26/07, Karl Swedberg <[EMAIL PROTECTED]> wrote: > > > > On Aug 26, 2007, at 2:55 AM, Stephan Beal wrote: > > > On Aug 26, 5:23 am, Karl Swedberg <[EMAIL PROTECTED]> wrote: > >> It's seems a shame not to use what looks like a > >> nice tool. > > > > i agree 100%, and i think it would help if the plugin developers > > started directing people to the bug db. The bug db has a higher > > barrier to entry than the list does (one has to create an account on > > the web site), though, so that might keep some people away (most list- > > goers have a Google account already). > > Okay then. If anyone would like to report a bug or add a feature > request for the clueTip plugin, you may do so here: > http://jquery.com/plugins/node/add/project_issue/cluetip/bug > or here: > http://jquery.com/plugins/node/add/project_issue/cluetip/feature > > :-) > > >> As I've been working on the clueTip plugin, one of the hardest things > >> for me has been to keep track of what people want out of it and what > >> they're finding wrong with it. > > > > If memory serves me properly, most people report bugs to you via this > > list or your blog. > > yeah. multiple threads, multiple blog entries. and personal email. > and IM. :-) Hard to keep track of. > Just to be clear -- I'm not complaining, and I'm not suggesting that > it's anyone's fault but my own. > I'm just seeking guidance for managing this stuff and wondering if > there was a flaw in the plugin repository's tools or if people > weren't using them for some other reason. > Sounds like you and Ganeshji think there's nothing inherently wrong > with those tools, but other factors, such as force of habit, path of > least resistance, etc. are the (de-)motivating factors. > > I really appreciate the input, Stephan. And Ganeshji. > > > >> Okay, sorry, I'm rambling. > > > > i think you've brought a very useful topic to the surface. A summary > > of my stance is: it's a problem of education - the developers should > > get in the habit of "teaching" the users to file bug reports by simply > > requesting them to "please file a bug report at http://..."; That may > > be overkill for trivial reports which you know you can fix in a few > > minutes, but for bugs which won't/can't be fixed immediately, i feel > > it's a good solution. > > Excellent suggestion. I think I'll start doing that. Thanks again! > > --Karl >
[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
On Aug 26, 2007, at 2:55 AM, Stephan Beal wrote: On Aug 26, 5:23 am, Karl Swedberg <[EMAIL PROTECTED]> wrote: It's seems a shame not to use what looks like a nice tool. i agree 100%, and i think it would help if the plugin developers started directing people to the bug db. The bug db has a higher barrier to entry than the list does (one has to create an account on the web site), though, so that might keep some people away (most list- goers have a Google account already). Okay then. If anyone would like to report a bug or add a feature request for the clueTip plugin, you may do so here: http://jquery.com/plugins/node/add/project_issue/cluetip/bug or here: http://jquery.com/plugins/node/add/project_issue/cluetip/feature :-) As I've been working on the clueTip plugin, one of the hardest things for me has been to keep track of what people want out of it and what they're finding wrong with it. If memory serves me properly, most people report bugs to you via this list or your blog. yeah. multiple threads, multiple blog entries. and personal email. and IM. :-) Hard to keep track of. Just to be clear -- I'm not complaining, and I'm not suggesting that it's anyone's fault but my own. I'm just seeking guidance for managing this stuff and wondering if there was a flaw in the plugin repository's tools or if people weren't using them for some other reason. Sounds like you and Ganeshji think there's nothing inherently wrong with those tools, but other factors, such as force of habit, path of least resistance, etc. are the (de-)motivating factors. I really appreciate the input, Stephan. And Ganeshji. Okay, sorry, I'm rambling. i think you've brought a very useful topic to the surface. A summary of my stance is: it's a problem of education - the developers should get in the habit of "teaching" the users to file bug reports by simply requesting them to "please file a bug report at http://..."; That may be overkill for trivial reports which you know you can fix in a few minutes, but for bugs which won't/can't be fixed immediately, i feel it's a good solution. Excellent suggestion. I think I'll start doing that. Thanks again! --Karl
[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
On Aug 26, 11:04 pm, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > You can use Google Code just like jQuery does. And in contrast to > sourceforge.net, your project creation request isn't delayed or denied > on some random basis. Thanks for that tip. :) What services do they provide? i'm poking around code.google.com and can find absolutely zero info about what services they provide to hosted projects. i know i could find out by creating a new project, but i don't want to create a project just to find out what they offer.
[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
Ganeshji Marwaha schrieb: > your site is hosted on hostmonster > (same as mine), and they run apache 1.x, which doesn't have the > necessary apache modules for hosting an svn server. yup, that is true :-( . You can use Google Code just like jQuery does. And in contrast to sourceforge.net, your project creation request isn't delayed or denied on some random basis. -- Jörn
[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
> your site is hosted on hostmonster > (same as mine), and they run apache 1.x, which doesn't have the > necessary apache modules for hosting an svn server. yup, that is true :-( . -GTG On 8/26/07, Stephan Beal <[EMAIL PROTECTED]> wrote: > > > On Aug 26, 7:29 pm, "Ganeshji Marwaha" <[EMAIL PROTECTED]> wrote: > > What, i was trying to convey was, although my plugins are listed there, > i am > > not motivated to effectively use the plugin web site for issue tracking > and > > feature requests because, i don't have the actual code in the repo. > > Ah, that's a good point. But the plugins page allows you to add a link > to your own repo (obviously, most people don't have a publicly- > accessible repo, though). IIRC, your site is hosted on hostmonster > (same as mine), and they run apache 1.x, which doesn't have the > necessary apache modules for hosting an svn server. > >
[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
On Aug 26, 7:29 pm, "Ganeshji Marwaha" <[EMAIL PROTECTED]> wrote: > What, i was trying to convey was, although my plugins are listed there, i am > not motivated to effectively use the plugin web site for issue tracking and > feature requests because, i don't have the actual code in the repo. Ah, that's a good point. But the plugins page allows you to add a link to your own repo (obviously, most people don't have a publicly- accessible repo, though). IIRC, your site is hosted on hostmonster (same as mine), and they run apache 1.x, which doesn't have the necessary apache modules for hosting an svn server.
[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
>> You don't need it - anyone can submit a plugin to the plugin web site, >> which is independent of the svn tree. You just need to create an >> account on the plugins site, then you're all set to go. I am aware of that... coz, i have my plugins already listed there. What, i was trying to convey was, although my plugins are listed there, i am not motivated to effectively use the plugin web site for issue tracking and feature requests because, i don't have the actual code in the repo. -GTG On 8/26/07, Stephan Beal <[EMAIL PROTECTED]> wrote: > > > On Aug 26, 9:03 am, "Ganeshji Marwaha" <[EMAIL PROTECTED]> wrote: > > For starters, i don't know if i have write access to the jquery svn > > repository to checkin my plugin. > > You don't need it - anyone can submit a plugin to the plugin web site, > which is independent of the svn tree. You just need to create an > account on the plugins site, then you're all set to go. > > > Third, the main jquery page still points to the docs.jquery.com/pluginswiki > > instead of the plugin page. Many people are still using that. > > Someone posted a few weeks ago saying that they would install a > redirect on the plugins page "soon". When... i don't remember. > > > And, as Stephan says it is both a problem of education and the barrier > to > > entry. > > Perhaps we can get the webmasters to allow anonymous posts to the bug > db (assuming that the underlying framework allows it, which i'm not > sure about at all). > > :) > >
[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
On Aug 26, 9:03 am, "Ganeshji Marwaha" <[EMAIL PROTECTED]> wrote: > For starters, i don't know if i have write access to the jquery svn > repository to checkin my plugin. You don't need it - anyone can submit a plugin to the plugin web site, which is independent of the svn tree. You just need to create an account on the plugins site, then you're all set to go. > Third, the main jquery page still points to the docs.jquery.com/plugins wiki > instead of the plugin page. Many people are still using that. Someone posted a few weeks ago saying that they would install a redirect on the plugins page "soon". When... i don't remember. > And, as Stephan says it is both a problem of education and the barrier to > entry. Perhaps we can get the webmasters to allow anonymous posts to the bug db (assuming that the underlying framework allows it, which i'm not sure about at all). :)
[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
For starters, i don't know if i have write access to the jquery svn repository to checkin my plugin. Once i know that i already have it or not, or if i am given one, then i might be more interested in tracking bugs and enhancements from the plugin page itself. Second, the plugin site is fairly new, and as u know we faced quite a few issues using that in the first place... So, it is just a matter of time before both developers and users get confidence in the repo. Third, the main jquery page still points to the docs.jquery.com/plugins wiki instead of the plugin page. Many people are still using that. And, as Stephan says it is both a problem of education and the barrier to entry. But, these are expected from the users to get quality extensions from any open source software. Yet, it has to solved. Again, i guess i am just rambling... -GTG On 8/25/07, Karl Swedberg <[EMAIL PROTECTED]> wrote: > > Hey folks, > > I was looking through the plugins at jquery.com/plugins/ and noticed that, > even though the project pages have bug-report and feature-request tools > built right in, hardly any of the plugins have anything entered for any of > it. Kelvin Luck's plugins are the only ones I saw from a cursory skim > through the list that are taking advantage of them. > > > So, I'm curious. What do more seasoned plugin developers recommend for > tracking bugs and feature requests? Why is hardly anyone using these on the > plugin pages? Is there something better out there that others are using? > It's seems a shame not to use what looks like a nice tool. But before I jump > in and start using it for my own plugin, I thought I'd seek the perspective > of others. > > > As I've been working on the clueTip plugin, one of the hardest things for > me has been to keep track of what people want out of it and what they're > finding wrong with it. I think it would be nice to have a centralized > location where I could monitor this stuff for my own plugins, and it would > also be cool to be able to look at other plugin pages and check on their > progress. > > > Any thoughts on this? How about not just from plugin *developers*, but > from plugin *users* as well? People out there using these plugins -- would > you find it helpful to be able to look at these plugin pages at the > jquery.com plugin repository and check on their status? > > Okay, sorry, I'm rambling. > > > > > --Karl > _ > Karl Swedberg > www.englishrules.com > www.learningjquery.com > > > > > >
[jQuery] Re: Plugin Repository - Report New Bugs and Request New Features?
On Aug 26, 5:23 am, Karl Swedberg <[EMAIL PROTECTED]> wrote: > Why is hardly anyone using > these on the plugin pages? "The path of least resistance." They all post here instead. And the developers here normally say either "won't fix that" or "I just posted an update," which means no long-term tracking is needed. :/ > It's seems a shame not to use what looks like a > nice tool. i agree 100%, and i think it would help if the plugin developers started directing people to the bug db. The bug db has a higher barrier to entry than the list does (one has to create an account on the web site), though, so that might keep some people away (most list- goers have a Google account already). > As I've been working on the clueTip plugin, one of the hardest things > for me has been to keep track of what people want out of it and what > they're finding wrong with it. If memory serves me properly, most people report bugs to you via this list or your blog. > Okay, sorry, I'm rambling. i think you've brought a very useful topic to the surface. A summary of my stance is: it's a problem of education - the developers should get in the habit of "teaching" the users to file bug reports by simply requesting them to "please file a bug report at http://..."; That may be overkill for trivial reports which you know you can fix in a few minutes, but for bugs which won't/can't be fixed immediately, i feel it's a good solution. :)
