From: Krishna M <kri...@gm...> - 2006-09-18 11:01:18
|
I think your idea is good. keeping svn in plone collective is good idea. And how about grouping PloneSkype under "PloneCollective" product in sf site? -- Krishna M Giovani Spagnolo wrote: > hi all, > > what do you think of using SourceForge only for the mailing list and for code package distribution/release and use SVN from plone collective ?? > > more plone/python developers can help in that way. > > Instructions (from plone.org): > ------------------------------------------------ > If you would like to get write access to the Collective, please create an account here on plone.org, then file a ticket in the Plone ticketing system (https://dev.plone.org/plone.org/newticket) requesting Collective repository access. In your ticket, please include the following information: > > * Indicate that you are requesting access to the Collective repository. (Plone has several major code repositories, which have varying requirements for access.) > * Describe why you want to have commit access - do you have a new project to check in, a fix to contribute, etc. > * Set the ticket type to request > * Select commitaccess as component > > More details on Plone code repository access are available at: http://dev.plone.org/plone.org/wiki/SubversionAccess > > ----------------------------------- > (i did it already :-) > > and then use regularly svn.plone.org > > gs > > Giovani Spagnolo > --------------------------- > http://www.webyes.com.br/giovani/blog > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Ploneinvite-devel mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/ploneinvite-devel > > |