For me, it's important for it to be really easy to call out people who aren't using the public API. I agree with Michael that trying to go insane with the naming conventions might produce serious irritation, but I feel strongly that slices be released as merb_slice_authorization. That way it's easy to automate the searching and listing of Merb slices. In general, merb-foo means that it's officially maintained, while merb_foo means that it's a community plugin.
-- Yehuda On Mon, Oct 13, 2008 at 8:51 AM, Michael Klishin < [EMAIL PROTECTED]> wrote: > > 2008/10/13 Ahsan Ali <[EMAIL PROTECTED]>: > > 1 Should that be part of merbunity? github? or a separated site? - > Github, > > keep it simple. Easy to clone, easy to update, and (probably) easy to > > install. Maybe a blog/feed for announcements ? > > Both github an merbunity, if you ask me. Github is for repository > itself, merbunity for plugin pages like agilewebdevelopment.com > plugins section. > > > 2- what features are you thinking of? ratings? comments? - Docs, docs, > and > > docs :) I like the README.textile way in github repositories. Comments ? > We > > can comment on the github source. Ratings ? Not required. I've seen these > > features on several rails plugin sites, and there are only a handful of > > ratings per plugin - even for the popular ones ! > > Some have 200+ ratings but completely outdated. What we need is example > application for each slice, with tests and such. This is the best way > to rate a slice, see how easily it can (or can't) be used. > > -- > MK > > > > -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
