Re: CMF packages on svn.zope.org

Hi,

what's the reason for the CMF developers to not move to github as
canonical repository? (is it that they don't trust github? ok, that's
would be a valid reason.)

and, don't isn't the github/collective process of moving from svn to
github also valid for svn.zope.org migrations?
https://github.com/collective/collective.github.com/blob/master/old-svn.rst

cheers, johannes

On Thu, 2014-07-10 at 17:52 +0200, Timo Stollenwerk wrote:
> Hi,
> 
> just a quick update: I talked to two of the CMF developers, Charly Clark
> and Yvo Schubbe. They were both really nice and open.
> 
> They are ok with us "mirroring" the CMF packages on github. We would add
> a note to the repos, stating that the SVN version remain the canonical
> one and that changes there needs to be merged upstream.
> 
> Taking into account that there is almost no activity on CMF, I guess we
> can keep the repos in sync manually. Though, if anybody wants to work on
> a better solution, I'd be open for suggestions.
> 
> We probably can't mirror the packages under the Plone organisation on
> github, because we would risk that people commit there without having
> signed the Zope contributor agreement.
> 
> Looking at sources.cfg:
> 
> https://github.com/plone/buildout.coredev/blob/5.0/sources.cfg
> 
> The following packages are still hosted on svn.zope.org:
> 
> Products.CMFActionIcons
> Products.CMFCalendar
> Products.CMFCore
> Products.CMFDefault
> Products.CMFTopic
> Products.CMFUid
> 
> I'm not sure if these packages are considered part of CMF:
> 
> Products.DCWorkflow
> Products.ExternalEditor
> Products.PluggableAuthService
> Products.PluginRegistry
> 
> This z3c package also needs to be moved to github:
> 
> z3c.formwidget.query
> 
> Can anybody help with moving those Packages to github? This move would
> really make our CI/Dev setup a lot more reliable.
> 
> There is a howto, but it looks complicated:
> 
> https://gist.github.com/mgedmin/4944724
> 
> I'm still busy with moving our CI infrastructure to the new rackspace
> machines/Ubuntu 14.04 and with mentoring my GSoC student, so I won't
> have much time to work on this myself...
> 
> Cheers,
> Timo
> 
> Am 09.07.2014 19:13, schrieb Sean Upton:
> > On Wed, Jul 9, 2014 at 12:26 AM, Timo Stollenwerk <tisto-z4DKO/[email protected]> wrote:
> >> Hi,
> >>
> >> svn.zope.org seems to be down again, breaking our entire CI setup (not
> >> the first time). As far as I know all zope packages have been moved to
> >> github already. Though, it seems the CMF project made the decision not
> >> to move their packages to github. Which is totally fine. Though, since
> >> svn.zope.org is really unreliable, I think we have to find a solution
> >> that works for us.
> > 
> > Historical reference: http://www.gossamer-threads.com/lists/zope/cmf/234534
> > 
> >> Some of the CMF packages seems to be on github anyways, but they are not
> >> considered to be the canonical ones:
> >>
> >> https://github.com/zopefoundation/Products.GenericSetup/pull/3
> > 
> > Yuck.
> > 
> >> I haven't been involved into any discussion with the Zope or the CMF
> >> project, can anybody give me an update on the situation and the current
> >> status of the packages that we still use from CMF?
> > 
> > Is anyone using CMF outside of Plone anymore anyway?  If so, where; if
> > not, why not fork (or at least force the issue of getting Zope
> > contributors to move the development to github.com/zopefoundation)?
> > 
> >> If we are using our own branches anyways (not sure if this is the case),
> >> wouldn't it make sense to fork or at least mirror the packages that we
> >> need on github to get a more reliable setup?
> > 
> > Ideally host all packages on github.com/zopefoundation (or permanently
> > fork them to github.com/plone ?), then have some sort of off-github
> > git repository mirror (e.g. self-hosted backups or gitlab or
> > something) to make the all-eggs-in-one-basket worries (e.g. EvilCorp
> > sends DMCA notices, bye-bye repos) go away?
> > 
> >> This would also allow us to
> >> put post-commit hooks on the github repos, because so far Jenkins can
> >> not detect any changes from those packages, making it really hard to
> >> find possible regressions introduced by those packages.
> > 
> > Someone ought to put this on github somewhere, over the ideological
> > objections of the detractors -- the community of people using (and
> > potentially contributing to) CMF seems to have moved there.  Since git
> > is decentralized (assuming we have automated backups or a mirror), it
> > ought not to really be that controversial.
> > 
> > Sean
> > 
> 
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers

-- 
programmatic  web development
di(fh) johannes raggam / thet
python plone zope development
plone framework  team  member
mail: office-//[email protected]
web:  http://programmatic.pro
      http://bluedynamics.com

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEABECAAYFAlO/AgYACgkQW4mNMQxDgAfbXACgue/NyghIK5tB7iTflSaMbu7F
PZEAn0FG+FGh4lPZkzah61Ac8M9nQJ38
=+IEy
-----END PGP SIGNATURE-----