[Seaside] Use of examples from Hasso-Plattner-Institut's tutorial

Miguel Cobá m.coba.m at gmail.com
Thu Nov 15 16:33:50 UTC 2007


On Nov 15, 2007 4:10 AM, Michael Haupt <mhaupt at gmail.com> wrote:

> Hi Miguel,
>
> On Nov 15, 2007 6:23 AM, Miguel Enrique Cobá Martínez
> <m.coba.m at gmail.com> wrote:
> > I refer only to the code and not to the text. As I understand it, if you
> > buy a book about data structures in C, for example, you can use the
> > techniques in it because it is meant to learn the language or the
> > techniques. The same logic applies to the code and techniques you read
> > in a forum on the web. The code in the forum's threads are for learning
> > and is common to use the code verbatim or with little modifications in
> > your own project. You get my point.
> >
> > Can you, please, clarify this point?
>
> here is the position you are asking for.
>
> Of course you can use idioms from the ToDo application to demonstrate
> how certain things work. We'd be happy if you could give appropriate
> credit and point to the tutorial for reference. As long as you don't
> reuse entire parts of the application, there is no problem. If you do,
> you will require express permission from us to do so.
>

Ok, that's enough for me. In no way have I the intention of verbatim copy or
reuse sections of your application. I just wanted to know that it is ok to
use the ideas and techniques. They are very useful because it is very hard
to find examples in the net about, for example, how to do a login system or
how to integrate with GOODS in a full app. Of course, that is just a way to
do it, but an implementation shows you not only a working example about how
to solve a particular problem but also it opens your mind about the ways you
could do it in a different way without using the original code. It is a sort
of bootstrap for your app. That way you can begin your app and concentrate
in your app's very own functionality and later, when you feel more
confortable or have more experience, you can return to the code and recode
it in a different way, in your own style and with better integration to your
app. In fact that kind of development style is encouraged by Smalltalk.


> As for the tutorial *text*, any reuse of existing material is subject
> to express permission from the authors.


Yeah, that is the way almost all understand it. The text is copyrighted.


>
> This is how things are for now. We are sorting out licensing details
> but have not yet come to a conclusion.
>
I hope you can reach an agreement where the text is copyrighted but the code
is available to anyone (MIT license or public domain) because:
1. It would reach a wider audience
2. It would be most useful to people learning Seaside
3. It would help to promote Seaside (something we all here want)
4. It should be in the spirit of the academy, with the learning and
knowledge diffusion as the foremost objective.

>
> I hope this clarifies things.
>
Yes, a lot, thank you.

>
> Best,
>
> Michael


Regards,
Miguel Cobá

>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20071115/b5a8964c/attachment.htm


More information about the seaside mailing list