---This is splitted from the 'pre-announcing collective.newsletter' thread.---
This has probably been brought up several times; I've tried searching, but no sigar. In the 'pre-announcing collective.newsletter' threads we went a bit offtopic regarding the location of collective products. Martin wrote on his blog<http://www.martinaspeli.net/articles/the-naming-of-things-package-names-and-namespaces> that the collective namespace comes from the Collective subversion repository. Therefore code using that namespace, *should* live in that repository. I notice several packages on github using the collective namespace, which by itself is no problem. But... "The namespace implies community ownership and invites anyone with Collective commit access (i.e. anyone who wants it) to collaborate and help maintain it" according to Martin. I have some practical problems there. I have collective svn access, but I can't access the github repos with that account. I cannot just open the repos and fix some code, nor take control if the owner has left the project. Yes, I know I can request merge and stuff like that, but the ownership is not with the community this way. Please do not read this as an attack, but as a way to ensure collective ownership and code in the future. tl;dr Why can we just say: if you're using the collective namespace, you *have* to use the collective svn repository? -- Roel Bruggink http://www.fourdigits.nl/mensen/roel-bruggink Four Digits BV http://www.fourdigits.nl Willemsplein 44, 6811 KD, Arnhem tel: +31(0)26 4422700 fax: +31(0)84 2206117 KVK 091621370000 BTW 8161.22.234.B01
_______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
