<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-text-html" lang="x-unicode"> Is anyone interested in
a Grok sprint at the upcoming Plone conference. <br>
<br>
Oct 14=16 2015<br>
Bucharest, Romania<br>
<a class="moz-txt-link-freetext" href="https://2015.ploneconf.org/">https://2015.ploneconf.org/</a><br>
The sprints are the 17th and 18th.<br>
<br>
What should the sprint do? Here are my proposals. <br>
<br>
1. Update Grok.project. Grok.Project works great, but its age
scares off new Grok developers. <br>
It should not be that hard to update it to use the most recent
releases of the various packages. <br>
<br>
2. Fix the SSL certificates on Apache server on the zope.org mail
server. I have sudo permission. <br>
But I am too busy to do it right now. If anyone has done this
before we could do it very quickly. Or you could even walk me
through it over Skype. <br>
<br>
3. Make ZODB into a JSON server out-of-the-box. Define your
python classes, and their interfaces, <br>
and it just works. In particular, one could do CRUD using JSON on
individual objects, and trees of objects. Also
zope.securitypolicy would work. Maybe do a simple tutorial. The
whole corporate marketplace (Where the consulting money is) has
moved to single-page web apps. Grok needs to evolve from a
hunting Mammoths Tutorial to serving JSON tutorial or suffer the
fate of the Neanderthals.<br>
<br>
4. Paleolithic Diet Sprint. <em style="color: rgb(0, 0, 0);
font-family: serif; font-size: 14.4px; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 1;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(204, 188, 89);">It seems that perfection
is achieved not when there is nothing more to add, but when
there is nothing more to take away.</em><span style="color:
rgb(0, 0, 0); font-family: serif; font-size: 14.4px; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important;
float: none; background-color: rgb(204, 188, 89);"><span
class="Apple-converted-space"> </span></span><small
style="color: rgb(0, 0, 0); font-family: serif; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(204, 188,
89);">— Antoine de Saint-Exupéry: Terre des hommes</small> <br>
<a class="moz-txt-link-freetext"
href="http://www.simple-is-better.org/">http://www.simple-is-better.org/</a><br>
<br>
I would love to see grok go on a diet. The publishing process
uses zope.publisher, grok.view.publish, zope.app.publish, and
grok.traversal. Understanding it all is very difficult. If we
could simplify and compress it, that would help both existing
developers and new developers. <br>
<br>
5, Eliminate component registration for widgets. What I did in my
application is that every zope.schema <br>
field has a default widget. In just a few cases, I give it the
name of a widget to look up. Way way<br>
easier than registering all the widgets. Of course if a widget is
registered, then that can be used. <br>
<br>
What would you like to see improved during a Grok Sprint? <br>
<br>
I think the name "Paleolithic Diet Sprint" is really cute.<br>
<br>
Chris<br>
<br>
<br>
</div>
</body>
</html>