Thanks

Sun May 22 19:20:59 UTC 2005

> Zbiggy, ok a few thoughts on your requests/comments
>
> Take this as a personal veiw, I'm not an active dev and haven't
> been in more than a year.
>
> First, it is questionable whether modules even qualify as copyrighted
> works. Copyright specifically excludes 'listings of ingredients or
> contents'. That is a pretty good description of most modules.

I mean author rights. If I explained it wrong - sorry. Lunar is LGPLv2 
licensed so modules and other pieces of digital work in it.

> (And where it isn't a good description, i.e. where significant /bin/sh
> logic/scripting is implemented in a module I would consider that to
> be a failing either on the part of the lunar core design or of the
> source authors -- bash scripting inside modules should be the exception
> and usually results in hard-to-maintain modules.)

Programms installed by modules scripts have their own licenses. Lunar tools 
also have author credits inside. If I post piece of code expect the part of 
code I send with credits to be included with credits. Otherwise my code have 
someones else credits.

> Second 'MAINTAINER's come and go. Where we have maintainers recorded in
> the modules at all, often (mostly?) they are out of date and therefore
> not very useful.

If I find old module first drop a message to author becuse the author know the 
best how to update module. If he/she do not have time or does not exist then 
I have right to fix/update module. In this right way works 99% of linux 
community. Asking for update overloaded developers is nonsense they have more 
important work to do. I have no idea why in lunar, developers do such simple 
work as incrementing module version from 0.0.0.1 to 0.0.0.2 . This is work 
for power contributors who knows how correctly build and update modules.

> Now, to give credit where credit is due is a good thing, however if
> you assert that a software team has a responsibility to credit your
> authorshio, perhaps you should think about what this entails ... not
> all contributors have the same wishes, do you really want the team
> spending it's time on this?

The MAINTAINER line in DETAILS file is not required - its optional. If you 
know the module is correct and have time to take care of it you fill this 
line. Otherwise the lunar developers will take care. If the maintainer line 
is stripped by developer - contributor know what does it mean: "you are too 
stupid to maintain this module".

> I would argue that by default stripping the MAINTAINER field of
> contributors is the correct procedure, handling all contributors'
> different desires, let alone the tendency of people to come and go
> simply seems to be more work than it's worth.

The maintainer line is optional. Who have time to take care - fill this line 
with own address. If not he/she removes maintainer line and lunar community 
will take care.

> If you really want credit for your modules, why not simply add your
> email to the 'LONGDESC' field of the module DETAILS file?

Because this is place to descibe programm not author. According to Lunar's 
module SDK the only right place to do this is maintainer line. BTW: The 
maintainer line should have not only e-mail address but also name. We do not 
want to get mails begginig with "Hey you"

zbiggy

> elaine
>
> On Sun, 22 May 2005 00:57:12 +0200
>
> Zbigniew _uszpi_ski <zbiggy at o2.pl> did inscribe thusly:
> > Hi!
> >
> > Thanks for importing 2 (of 7 sent by me) modules to lunar in May. Thanks
> > also for importing the -freorder-blocks patch I sent earlier. I would be
> > very grateful if you stop removing my name and/or e-mail address from
> > pieces of work I send.
> >
> > The name of the author and his e-mail address is very important part of
> > source code or modules. It allows users to contact directly author if
> > they have some questions or bug reports. Thanks to this forums or
> > bugreports are not junked and other people are not bothered. The reaction
> > is also faster because the e-mails are read more often than forum
> > messages.
> >
> > Everything I do for lunar is made in free time as a kind of hobby. I only
> > have satisfaction, nothing more. Making my work anonymous you are simply
> > demotivating me and make me sad.
> >
> > Please remember about copyrights. If something is free in using/copying
> > etc. does not mean that nobody make it.
> >
> > I can not understand why removing author's address or name, e.g. the
> > maintainer address in modules is to help development, it should not be
> > removed - this is not obstacle. I can not understand why it takes so long
> > importing new modules to moonbase. Everything I sent was complete and
> > working, posted in form expected by developers.
> >
> > I see that many modules in lunar are made by anonymous people. I browse
> > Internet looking for updates and could drop a mail to maintainer if I
> > have known maintainer's e-mail address usually displayed by lvu
> > maintainer <module> command.
> >
> > Please do not flame this post. I try to improve things which look wrong
> > in my opinion. If there is special reason for anonymizing lunar tell me
> > because now I have no idea.
> >
> > greetings,
> > zbiggy
>
> _______________________________________________
> Lunar mailing list
> Lunar at lunar-linux.org
> http://foo-projects.org/mailman/listinfo/lunar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://foo-projects.org/pipermail/lunar/attachments/20050522/632b346b/attachment.bin