<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi everybody,<br>
<br>
I made what necessary for z3c.soap to comply with the zope project
policy (used zope.repositorypolicy) and incindentally to work with
Zope 2.13.19, what is the process now so it is migrated to Github?<br>
<br>
Thank you and have a nice day,<br>
<br>
<div class="moz-signature">
<table style="page-break-before: always; page-break-inside:
avoid" cellpadding="4" cellspacing="0">
<tbody>
<tr valign="TOP">
<td style="border: none; padding: 0cm" width="200">
<p><img src="cid:part1.03050201.06010904@imio.be"
name="images1" height="79" align="BOTTOM" border="0"
width="191"></p>
</td>
<td style="border: none; padding: 0cm">
<pre class="western">Gauthier Bastien
Support IMIO - CommunesPlone
rue de la Vieille Sambre 34
5190 Mornimont
Tél: +32(0)71 780979</pre>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 10px; color: grey;">
Disclaimer
<br>
<br>
Les informations contenues dans ce courrier électronique
(annexes incluses) sont confidentielles et réservées à
l'usage exclusif des destinataires repris ci-dessus. Si
vous n'êtes pas le destinataire, soyez informé par la
présente que vous ne pouvez ni divulguer, ni reproduire,
ni faire usage de ces informations pour vous-même ou
toute tierce personne. Si vous avez reçu ce courrier
électronique par erreur, vous êtes prié d'en avertir
immédiatement l'expéditeur et d'effacer le message
e-mail de votre ordinateur.
<br>
<br>
De informatie in deze e-mail, bijlagen inbegrepen, is
vertrouwelijk en is als dus danig voorbehouden voor
exclusief gebruik door de hierboven vermelde
bestemmeling(en). Indien u niet de bestemmeling bent,
willen wij u erop wijzen dat u deze informatie niet mag
aanwenden voor eigen gebruik noch verspreiden aan
derden. Indien u deze e-mail per ongeluk hebt ontvangen,
gelieve de afzender onmiddellijk te verwittigen en deze
e-mail van uw computer te verwijderen.
<br>
<br>
The information contained in this e-mail and the annexed
documents is confidential and exclusively available to
the here above mentioned addressee(s).Should you not be
the addressee, please be informed that you may neither
disclose nor reproduce this e-mail, nor may the
information contained in this e-mail and its eventually
annexed documents be used by yourself or by a third
party. If you erroneously received this e-mail, could
you kindly and immediately inform the addresser and
delete the message on your computer.
</td>
</tr>
</tbody>
</table>
</div>
Le 11/01/13 16:42, Jim Fulton a écrit :<br>
</div>
<blockquote
cite="mid:CAPDm-Fj9BkEhzeOA1u9r3eNW9dqG7HtzV_es6e9M4yJfzYa9FA@mail.gmail.com"
type="cite">
<pre wrap="">On Fri, Jan 11, 2013 at 10:34 AM, Tres Seaver <a class="moz-txt-link-rfc2396E" href="mailto:tseaver@palladion.com"><tseaver@palladion.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/10/2013 06:10 PM, Matthew Wilkes wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Tres Seaver wrote:
</pre>
<blockquote type="cite">
<pre wrap="">What is needed is not scripts, but eyeballs: we need people who
know the various packages and*care* about getting them migrated to
github to step up. Softwward which doesn't have a champion willing
to do the work should stay behind on SVN.
</pre>
</blockquote>
<pre wrap="">
The community as a whole cares about having them all migrated to
github. I'm sure this will happen the next time there's a sprint, just
like lots of them got migrated (and subsequently deleted) at the zope4
sprint in San Francisco a few years back.
</pre>
</blockquote>
<pre wrap="">
The communite as-a-whole demonstrably does *not* care about many of the
projects on svn.zope.org. E.g.:
<a class="moz-txt-link-freetext" href="https://mail.zope.org/pipermail/zope-tests/2013-January/070977.html">https://mail.zope.org/pipermail/zope-tests/2013-January/070977.html</a>
</pre>
<blockquote type="cite">
<pre wrap="">We need man-hours, sure, but not champions. Being blocked on working
on the code because you're the first one to care about a package and
subsequently have to learn how to do the migration is a crazy way of
doing things.
</pre>
</blockquote>
<pre wrap="">
The foundation agreed to support moving projects to github, but that
isn't a blank check. For instance, if there is substantial interest in
having the projects pulled in by the current Plone buildout moved, make a
list of them, and recruit the folks to step up and help with the
migration for them. The effort requires includes doing the conversion,
checking the results *by hand*, landing the repository, and fixing
anything that breaks once you do (including stuff that breaks in projects
you otherwise don't care about).
Any project that can't find somebody willing to do that work (that is
what I meant by a "champion") is better off staying on SVN: we don't do
ourselves favors by carrying all the unmaintained baggage of fifteen
years worth of development forward, just for "purity" / completeness /
whatever.
</pre>
</blockquote>
<pre wrap="">
+1
BTW (speaking of cruft), as someone who used/abused svn.zope.org as a
generic open-source hosting service (when I should have used something
like code.google.com, or bitbucket, or whatever), I wonder if there
should be a process for petitioning to remove projects from the ZF
repositories. (Maybe this only applies to me :)
Jim
</pre>
</blockquote>
<br>
</body>
</html>