[kdewebdev-site] First draft of www.kdewebdev.org vision statement - feedback requested

[Eric Laffoon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 06 April 2004 12:43 pm, Bill Chmura wrote:
> On Tuesday 06 April 2004 05:21 am, Chris Hornbaker wrote:
> > On Monday 05 April 2004 03:13, David Joham wrote:
> > > Hello all,
> >
> > Hey,
> > Overall, this sounds fine, so there's just a few things I would like to
> > comment/question on.
> >
> > [snip]
> >
> > > kdewebdev.org;
> > > DEVELOPMENT STRATEGY
> > >
> > > The development of kdewebdev.org can be broken down into two phases:
> > >
> > > Phase I will be the development of a www.kdewebdev.org “umbrella” site
> > > as well as a “brochure-ware” site for each component in the
> > > kdewebdev.org family. When completed, these sites will serve to educate
> > > visitors about the tools and technology we offer as well as present a
> > > consistent, professional image that conveys confidence and trust.
> > >
> > > Phase II will be the development of an infrastructure that encourages
> > > interactive contributions to the kdewebdev.org community. These
> > > contributions will include things like Kommander scripts, Javascript
> > > code, templates and contributions to the core tools themselves.
> >
> > Here I can see a potential for problems. A Terms of Use/Privacy will be
> > needed to keep us out of liability.
>
> This could probably be handled pretty easily with both a sitewide policy
> linked from the bottom of each page, and something simple on the submission
> page basically saying what they can expect (and a link to the privacy
> page).

This is even easier to handle than that. I must have been half asleep when I 
read Chris' email because it didn't register until now. ;-) All submissions 
will be handled through a database interface. The simple way to deal with 
this is to require a license be selected to upload. I don't think it makes 
any sense to expose not just us, but others to vagaries like ambiguous 
licensing that can come back and bite you. If you look at the script area of 
Quanta it has a field for the license of the script you're providing. This is 
completely covered in the application of this, though we need to look at the 
mechanism for templates and such.
>
> > Also, I'd hate to see some 13-year-old learn about copyright law the
> > "hard way." How will licensing work?
>
> This is going to be a sticky one.  I know Eric talked about keeping it as
> open as possible, but if for example, he wrote a book on Quanta he would
> want to be able to include submitted code.  Which gets into a whole sticky
> area of profit and such.   I don't have a clear idea, but this can probably
> noted and deferred to such a time we get as far as that.  If the decision
> has been made that it will be allowable to anyone to submit, then the rules
> are moot until we are able to (unless of course the rules will be so
> draconian that no one will in which case, making the function would be
> pointless).  I would find out what the current policy is (if there is one).
>  The thing to remember is that contracts and policies are not for when you
> are all getting along, its for when you are not.  :)

The issues involving future work on a book and being able to reproduce parts 
of the site are relevent only to the site proper. Submitted content would be 
governed by it's license. All of this is covered at 
kittyhooch.com/kdewebdev.php with the idea that it would be unfortunate if my 
efforts to produce a book to promote Quanta and extend our sponsorship 
efforts left me unable to reprint some portion of the site in the book. I 
have no intention of converting the site to book form and I can already 
imagine how poorly that would be received from a publisher. ;-)

Eric
>
> > > This document will concentrate on Phase I, but will touch on Phase II
> > > as well.
> > >
> > >
> > > PHASE I Details
> >
> > I'm assuming there's no design for this yet. Wasn't someone working on a
> > design?
>
> Last we left our heros, the intention was to get a basic nav down so we
> could get the design at least underway.  The design person (graphics I
> assume you are talking about) is Americo and he is on the list here
> somewhere.
>
> I think we had a good navigation worked out, but for the sake of speed was
> not doing it out the nth degree and defering the navigation for the user
> and developer support sections.  I think I met resistance on that, so YMMV.
> Personally I think with the size team you have, biting off and executing on
> small pieces is the way to go - at least until you have a good idea on how
> everything and everybody is going to be working together.
>
> Huzzah
>
> > [snip]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAcxg3SiV5TqRTAEsRAkNkAJ9U6bv1R/cUnKfjp70v8DjVOYAb1ACgn1rQ
j2SaPYYxy5PIOE0JvDOkS1I=
=lEnO
-----END PGP SIGNATURE-----