<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>[pmwiki-users] Sourceforge project for cookbook recipes?</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText57641 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Big support from me for
getting the plug-in recipes under source control. I'm not really worried
what tool is used however would recommend, for simplicity, that you have one
sourceforge wrapper project for them all.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>My only concern is that we
favour recipe authors over recipe users - sounds like a philosophy I read
recently ;-). It would be suboptimal if authors were deterred from
contributing recipes to such a great product because it was too much hassle to
publish.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>-Steve.</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> pmwiki-users-bounces@pmichaud.com on
behalf of chr@home.se<BR><B>Sent:</B> Sun 25/09/2005 17:47<BR><B>To:</B>
pmwiki-users@pmichaud.com<BR><B>Subject:</B> [pmwiki-users] Sourceforge project
for cookbook recipes?<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Hi<BR><BR>What do people on this list think about starting a
sourceforge project for<BR>cookbook recipes? I think the pmwiki engine
should be kept in its own<BR>project, but normal recipes could be added to this
project (called<BR>pmwiki-recipes or pmwiki-cookbook) on a strictly voluntary
basis.<BR><BR>Here are some of the advantages I can see:<BR>* We can have
version control of the recipes<BR>* If each recipe is kept as it's own module,
we can still check out<BR> recipes individually<BR>* Using CVS modules, we
can check out sets of recipes in one go<BR>* It'd be possible to update the
whole cookbook/ with one command<BR>* Patrick doesn't have to be involved if a
recipe uses a file that's<BR> larger than whatever his server is limited
to.<BR>* We could have a wiki (or several wiki fields) that's dedicated
to<BR> testing the various recipes.<BR><BR>Thoughts? Any one
interested in this? Are there any
drawbacks?<BR><BR>/Christian<BR><BR>--<BR>Christian Ridderström, +46-8-768 39
44
<A
href="http://www.md.kth.se/~chr">http://www.md.kth.se/~chr</A><BR><BR><BR><BR>_______________________________________________<BR>pmwiki-users
mailing list<BR>pmwiki-users@pmichaud.com<BR><A
href="http://host.pmichaud.com/mailman/listinfo/pmwiki-users">http://host.pmichaud.com/mailman/listinfo/pmwiki-users</A><BR></FONT></P></DIV>
</BODY>
</HTML>