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 w
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 PROTECTE
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
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 P
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
>
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 Goog
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 h
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
Mike,
it would be great to an overview of the features the new repository
would have, and what would get dropped. Also the migration strategy
and the technology you'd use for the new application would be
interesting.
And while it didn't get much attention in the discussion: If we build
a custom a
Thanks for your feedback Rey! Your description of what is done on AMO is a
great one, and it certainly helped me sharpen my vision for the plugin
repository.
I think there is a general consensus that trying to do the "Project
Management" on http://plugins.jquery.com is no longer a good idea. I
w
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 criter
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.
W
I believe the problem is Drupal as well. As I mentioned, when this
project was envisioned, we had no idea it would grow to this level.
I'm a big fan of Drupal in other areas, I think it's a good CMS, but
as a plugin repository site, we have long ago surpassed it's limits.
For the sake of discuss
Hi, sorry didn't read any of the previous posts but here are my 2
cents!
- My one gripe about the plugin page is the search results... too
confusing... more titles, less descriptions/comments please! :)
- I'm pretty sure someone suggested that "standard" plugins be adopted
because there are so ma
That sounds very good to me! Releases usually consist of a download, a
version number and a changelog. Thats all the repository should touch
in terms of project hosting - thats also what for example
addons.mozilla.com provides. Defining a convention to provide these
via Google Code or a Wordpress b
That would make sense because drupal is very poor and every plugin
I've ever come across has its own homepage hosted elsewhere. Maybe
plugins.jquery.com should focus on being a community for users - not
developers of jQuery - allowing users to...
- 'watch' their favourite plugins
- discuss/get hel
+1 get out of the plugin project hosting business. make the plugin
site a way to list/find/promote plugins, not a place to manage them.
On Tue, Oct 14, 2008 at 2:34 AM, Diego A. <[EMAIL PROTECTED]> wrote:
> Hi guys,
> I agree with all the points raised by Yehuda and Jorn, but unfortunately
> Mik
On Oct 14, 2008, at 12:34 PM, Diego A. wrote:
> In a nutshell :-
> - The navigation is shocking
> - Issue management is long winded and painfully time-consuming
Agreed. On top of that I did not even know there were submitted issues
with Jeditable until I one day was browsing plugins.jquery.co
I think both official and promoted plugins are good ideas.
--
Ariel Flesler
http://flesler.blogspot.com/
On Oct 14, 6:16 am, "Jörn Zaefferer" <[EMAIL PROTECTED]>
wrote:
> The biggest pain point is the unmoderation. Search for
> "autocomplete":http://plugins.jquery.com/search/node/autocomplete+t
On Tue, Oct 14, 2008 at 6:21 AM, Jörn Zaefferer <
[EMAIL PROTECTED]> wrote:
> Thats an interesting point. The repository isn't good at project
> managmenet, and that never was the focus.
Even if that wasn't the focus, maybe a lot of users would benefit from that.
And maybe that's what they expec
Thats an interesting point. The repository isn't good at project
managmenet, and that never was the focus. Maybe we should take that a
step further, strip everything related to that (recommend google code
instead) and focus on presenting plugins for plugin users. That would
make it much easier to w
The best working plugin site I know of is Mozilla's addon site:
https://addons.mozilla.org/en-US/firefox/
Maybe worth taking a deeper look at it, I'll ask Rey to share his
experience as community manager.
Jörn
On Tue, Oct 14, 2008 at 11:34 AM, Diego A. <[EMAIL PROTECTED]> wrote:
> Hi guys,
> I a
Hi guys,
I agree with all the points raised by Yehuda and Jorn, but unfortunately
Mike, the biggest problem of all is Drupal.
In a nutshell :-
- The navigation is shocking
- Issue management is long winded and painfully time-consuming
- So is uploading new files / creating new releases
I feel Yeh
The biggest pain point is the unmoderation. Search for "autocomplete":
http://plugins.jquery.com/search/node/autocomplete+type%3Aproject_project
You'll get 10 results of which at least 50% are crap. But there is no
way to tell, ratings aren't even displayed in the results, most
plugins have only on
>From my perspective, the biggest issue has to do with the inability to
automate getting plugins out of the repository. I'd like to be able to ask
the repo for version X.y of some specific plugin, and be able to get it.
I think that'd be pretty easy to add in; instead of just dumping the files
into
25 matches
Mail list logo
