Ricardo Newbery wrote:
> I've been toying with buildout recipes lately and it occurs to me that
> working with recipes feels a bit like an insider's game.
>
> Recipes can't be found on Plone.org. You mostly find out about them
> from word-of-mouth or the occasional reference in some tutorial. You
> can find some of them via pypi's package index but you can't count on
> all the recipes usable with Plone to show up under the
> Framework::Plone category (e.g., plone.recipe.varnish).
You can find all buildout related packages under the Framework::Buildout
category at
http://pypi.python.org/pypi?:action=browse&show=all&c=512As most of them aren't Zope or Plone specific at all, they shouldn't
really get the Framework::Plone classifier. For me the framework
information tells a 'depends-on' or 'needs' relationship and not a 'can
be used with' or 'works with' relationship.
> Should Plone-relevant recipes be listed somewhere on Plone.org?
> Perhaps under a special category in the PSC?
Personally I try to put all packages into PyPi and only those on
plone.org which are in some definition of the word add-ons for Plone and
thus relevant for the end user. So far I trusted developers and
integrators to be able to search PyPi for any new development library.
> Also, related to this. I notice a shared issue tracker for collective
> buildout recipes at
>
>
https://bugs.launchpad.net/collective.buildout/I created that bug tracker, as at least the recipes I'm responsible for
have nothing to do with Plone itself. Some of them are Zope specific and
some are just Buildout specific, so it made sense to give them an
identity on their own.
> But again, not all the Plone-related recipes indicate that they use
> this tracker, or any tracker. Perhaps in some cases, this is just a
> documentation oversight. I realize that this is mostly a choice of
> whomever is doing the actual development but for those of use looking
> to add a new recipe or to join in the development of an existing one,
> perhaps we should provide some guidance?
I'm happy to see the collective.buildout launchpad bug tracker to be
used by any other buildout recipe found in the collective. It's up to
the maintainer of that package to update their README's accordingly, though.
Hanno
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers