Hey, I did do a search on the group at first, but for some reason this thread didn't come up, but I posted over here: http://groups.google.com/group/jquery-dev/browse_thread/thread/7db728c3481e58b5
However, having a look at this thread I agree with a lot of it, and I'm glad to see other people want to have the site updated too. I know for example that the AMO site is a bespoke site developed in CakePHP. I am pretty familair with it, but with Django as well. At the moment, the technology choices aren't really the issue though, but certainly planning a bespoke site these things should be considered. And AMO isn't a bad thing to aim to be like. I think it will also give a good chance to do a plugin audit and see what plugins are still valid and which have been orphaned. Remy Sharp and I are also working on the new Adobe AIR jQueryAPI browser (http://code.google.com/p/jquery-api-browser/) and I'd like to see some way of integrating the site into this too, such as a plugin browser, and maybe even a tool to submit plugins, with all the correct information. One other idea is to cut down the number of duplicate plugin types. Google Code did something to me recently which was when I picked a project name, it told me there was already a similar named project on SourceForge! The idea was that I might be doing something similar, and to contact the author. If we could build some clever search, then when a user submits a plugin, they can see if someone has already created one. Hopfully this would mean not having 10 different dialouge or menu plugins. Anyway, that's my 2p on the matter for now, so Mike let me know where you are on it and hopfully we can talk further. On Oct 21, 10:24 pm, "Ariel Flesler" <[EMAIL PROTECTED]> wrote: > Ok added a story. Will check again later. > > On Tue, Oct 21, 2008 at 7:01 PM, Jörn Zaefferer < > > [EMAIL PROTECTED]> wrote: > > I started the personae and userstory lists, still a lot of work to do > > to fill out the details. > > > Jörn > > > On Tue, Oct 21, 2008 at 10:22 PM, Mike Hostetler > > <[EMAIL PROTECTED]> wrote: > > > Ariel and Jörn have access. Thanks guys for filling this out so quickly! > > I > > > really appreciate it. > > > > Mike Hostetler > > >http://amountaintop.com > > > > On Tue, Oct 21, 2008 at 13:05, Ariel Flesler <[EMAIL PROTECTED]> wrote: > > > >> Access please, [EMAIL PROTECTED] :) > > > >> Thanks > > > >> On Tue, Oct 21, 2008 at 3:52 PM, Jörn Zaefferer > > >> <[EMAIL PROTECTED]> wrote: > > > >>> Yes, just contact Scott Jehl directly. Either he can handle it, or at > > >>> least he knows someone to delegate to. > > > >>> I'd like to get access to the planning document! > > > >>> Jörn > > > >>> On Tue, Oct 21, 2008 at 8:44 PM, Mike Hostetler > > >>> <[EMAIL PROTECTED]> wrote: > > >>> > Glen- > > > >>> > Thanks for your feedback. I've started a Google Document with this > > >>> > information, it's just a skeleton right now. It can be viewed > > publicly > > >>> > at: > > >>> >http://docs.google.com/Doc?id=dgv8xf4f_54fchbjkc3 > > > >>> > If anyone would like access, please contact me directly. > > > >>> > I currently have plans in my head for how to approach the development > > >>> > of the > > >>> > new site, and how to manage the migration process. I'm not sure how > > to > > >>> > communicate this, other then to just go ahead and do it, after we've > > >>> > finalized and agreed to the planning document. My approach reflects > > my > > >>> > own > > >>> > style and my goal of getting a quality product as fast as possible. > > >>> > I'm > > >>> > open to feedback on this. > > > >>> > One area where I know I will need a bit of help is in the graphical > > >>> > design > > >>> > arena. Should I connect with Scott Jehl, the guy who designed the > > main > > >>> > site? I fully plan on using the current Drupal theme, but the > > >>> > individual > > >>> > page designs, (CSS and Graphics) are not my best strength. I can > > >>> > certainly > > >>> > tackle them, and leave room for improvement, but I think that the > > >>> > jQuery > > >>> > community deserves and expects a certain level of quality here. > > >>> > Thoughts? > > > >>> > Mike Hostetler > > >>> >http://amountaintop.com > > > >>> > On Sun, Oct 19, 2008 at 13:47, Glen Lipka <[EMAIL PROTECTED]> > > wrote: > > > >>> >> Just a bit of "best practice" for designing a better experience: > > > >>> >> 1. Create personas. (1-2 hour) These are basically a list of the > > >>> >> people who matter and their different "types". > > >>> >> Example: New jQuery fan looking for a simple autocomplete. Name: > > >>> >> Chuck. What chucks wants: confidence the plugin is a good one. > > >>> >> options, comments, etc > > >>> >> Example 2: Advanced jQuery plugin author. Name: Sarah. What sarah > > >>> >> wants: SVN Access, simple updating, etc > > >>> >> There should be around 5 personas or so. (Less than 10) Give them > > >>> >> pictures. I swear to god, it makes the whole process easier. > > > >>> >> 2. Write down use cases (a.k.a. user stories). (2-6 hours) These are > > >>> >> REALLY helpful to manage the requirements. If your implementation > > can > > >>> >> achieve these use cases, then you know you didnt forget something > > >>> >> like. "Sarah needs to change her password for SVN". > > > >>> >> 3. Design the user experience in something simple/fast/cheap. I > > >>> >> suggest powerpoint, but it could be anything. Just so long as it is > > >>> >> the cheapest fastest possible way to show how the thing should be > > >>> >> built. > > > >>> >> 4. Eat your own young. Please don't get hung up on drupal or > > existing > > >>> >> ideas/systems. Redoing something ALWAYS is better than trying to > > >>> >> shoehorn an update. Starting from scratch is fun. Go for it! You > > >>> >> might end up choosing drupal again, but don't let a bad decision > > >>> >> before affect your decisions today. > > > >>> >> 5. Iterate. It's important to leave room for growth. Wouldn't it > > be > > >>> >> nice for people to vote for a plugin that doesn't exist? or to pay > > a > > >>> >> plugin author money to extend it? ideas are powerful. > > > >>> >> Anyway, I wish I had more time to devote to jQuery. :( So much > > >>> >> powerpoint these days. > > > >>> >> I'd be happy to help anyway I can. :) > > >>> >> Keep "pluggin" away! > > > >>> >> Glen > > > >>> >> On Oct 19, 12:27 pm, "Jörn Zaefferer" < > > [EMAIL PROTECTED]> > > >>> >> wrote: > > >>> >> > Thanks Rey for sharing ypur AMO experience! > > > >>> >> > Afaik doing away with hosting wasn't an option anyway, only > > project > > >>> >> > management doesn't fit the picture. > > > >>> >> > You're right that reviewing is a lot of work and requires > > resources > > >>> >> > we > > >>> >> > probably don't have. A less involved alternative would be to write > > >>> >> > down criteria that good plugins should adhere, and just check if > > >>> >> > those > > >>> >> > are met, and if so, highlight the plugin as such. This would cover > > >>> >> > aspects that a potential user would usually check before deciding > > to > > >>> >> > use a plugin, like presence and completeness of documentation. > > > >>> >> > Jörn > > > >>> >> > On Sat, Oct 18, 2008 at 5:31 AM, Rey Bango <[EMAIL PROTECTED]> > > >>> >> > wrote: > > > >>> >> > > Sorry for jumping so late into this discussion. Thanks for the > > >>> >> > > kudos > > >>> >> > > on > > >>> >> > > Mozilla AMO Joern. > > > >>> >> > > The AMO add-on site is pretty involved. While it looks very > > simple > > >>> >> > > on > > >>> >> > > the front-end, there's quite a bit going on on the back-end that > > >>> >> > > helps > > >>> >> > > us add, disable, review, approve, diff and version add-ons. > > > >>> >> > > While I like some of the ideas being thrown around, I'm not > > >>> >> > > convinced > > >>> >> > > that doing away with hosting is the answer. The fact that we > > have > > >>> >> > > a > > >>> >> > > central place for developers to come to to find plugins is a > > very > > >>> >> > > important advantage to the project. Although there are many > > >>> >> > > plugins > > >>> >> > > for > > >>> >> > > similar functionality, the fact that we have so many also needs > > to > > >>> >> > > be > > >>> >> > > viewed as a "positive" as it offers choice to our user base. > > >>> >> > > Having > > >>> >> > > lots > > >>> >> > > of choices does make things confusing but I'd rather have a > > little > > >>> >> > > confusion than nothing to offer at all. In addition, there have > > a > > >>> >> > > number > > >>> >> > > of cases of add-ons that have been seemingly abandoned in the > > repo > > >>> >> > > get > > >>> >> > > resurrected by a user who needed the functionality and took it > > >>> >> > > over. > > > >>> >> > > If anything, I would like to see a combination of both a hosting > > >>> >> > > scenario and directory listing. This would allow those > > developers > > >>> >> > > that > > >>> >> > > wanted to upload their plugin a place to house it while those > > that > > >>> >> > > don't > > >>> >> > > can simply point back to their site. > > > >>> >> > > I do think, as has been mentioned, that we need to get a better > > >>> >> > > system > > >>> >> > > in place to properly categorize the plugins. On AMO, for > > example, > > >>> >> > > we > > >>> >> > > have multiple categories but we also offer a recommended list of > > >>> >> > > top > > >>> >> > > add-ons (about 40 of them) and in addition, for each category, > > we > > >>> >> > > offer > > >>> >> > > a list of category recommended add-ons. This has been hugely > > >>> >> > > successful > > >>> >> > > and in fact, motivates many add-on developers to really improve > > >>> >> > > the > > >>> >> > > quality of their work. I can see the same thing being very > > >>> >> > > beneficial > > >>> >> > > to > > >>> >> > > the jQuery repo. So going with what Joern said, I think we need > > to > > >>> >> > > get > > >>> >> > > back to listing our official plugins the way that we used to and > > >>> >> > > also > > >>> >> > > create a recommended list of add-ons that we know are top-notch. > > > >>> >> > > In terms of reviewing add-ons, understand that it would be a > > VERY > > >>> >> > > big > > >>> >> > > task. On AMO, we struggle with that daily because of the number > > of > > >>> >> > > submissions as well as the time involved in reviewing the > > add-ons. > > >>> >> > > At > > >>> >> > > this point, I'm not sure if we're prepared to take on that task > > >>> >> > > unless > > >>> >> > > we were able to get a good group of volunteers to check the > > >>> >> > > plugins. > > >>> >> > > It's definitely a good idea and again, would help the community > > by > > >>> >> > > giving them feedback on improving their work. > > > >>> >> > > As for SVN, project management, etc, these are features that are > > >>> >> > > way > > >>> >> > > outside of the scope of a plugin repo. This is something that we > > >>> >> > > should > > >>> >> > > *NOT* do. We don't do this on AMO because of the complexity of > > >>> >> > > this. > > >>> >> > > On > > >>> >> > > AMO, we host the files necessary to install and add-on and > > that's > > >>> >> > > it. > > >>> >> > > The developers use other services for managing their project > > (eg: > > >>> >> > > MozDev.org or Google Code). > > > >>> >> > > I would say that in order to do this the right way, we would > > >>> >> > > probably > > >>> >> > > need to build our own custom system. At the moment, Drupal > > doesn't > > >>> >> > > seem > > >>> >> > > to provide the best way to find plugins and perhaps it's > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
