Question about freelance PHP development

Hi there.

This might seem like a silly question to some, but anyways:

I have done a few freelance PHP projects, but am about to start one on a
more professional level (the previous ones have been either pro-bono or
paid jobs through a friend).

I was wondering what people's practices are for putting a sort of
'signature' commented out in their code.

for example

<?/* filename_here.php
--------------------------------------
Description of file's function etc etc
--------------------------------------
Coded by Nathan (c) etc etc
http://www.mywebsite.com
*/?>

At the top of each PHP file. Is this something I *should* be doing, or is
it best left out, or what?

Apologies if this is a dumb question but I'm curious to know what other
freelancers here do.

--
Nathan.

Nathan wrote:
> Hi there.
>
> This might seem like a silly question to some, but anyways:
>
> I have done a few freelance PHP projects, but am about to start one on a
> more professional level (the previous ones have been either pro-bono or
> paid jobs through a friend).
>
> I was wondering what people's practices are for putting a sort of
> 'signature' commented out in their code.
>
> for example
>
> <?/* filename_here.php
> --------------------------------------
> Description of file's function etc etc
> --------------------------------------
> Coded by Nathan (c) etc etc
> http://www.mywebsite.com
> */?>
>
> At the top of each PHP file. Is this something I *should* be doing, or is
> it best left out, or what?
>
> Apologies if this is a dumb question but I'm curious to know what other
> freelancers here do.
>

If it's your code, then you should. I think it can be good to include a
license in the top too, if you are selling things to otheres.


//Aho

J.O. Aho say...

> If it's your code, then you should. I think it can be good to include
> a license in the top too, if you are selling things to otheres.

Thanks. Was probably going to do it anyway, but was just curious

--
Nathan.
XBL Gamertag: Cowfield
http://www.cowfields.com
Bow to the Cow!

On Mon, 21 Jul 2003 01:47:22 +0000, Nathan <spamfourstomachs@hotmails.com>
wrote:

> J.O. Aho say...
>
>> If it's your code, then you should. I think it can be good to include
>> a license in the top too, if you are selling things to otheres.
>
> Thanks. Was probably going to do it anyway, but was just curious

It's worth doing, since anyone else maintaining the code might be
glad of being able to contact you. It also removes any ambiguity over
copyright (unless your contract with your client says differently).

Sam


---
Posted via news://freenews.netfront.net
Complaints to news@netfront.net

"Nathan" <spamfourstomachs@hotmails.com> wrote in message
news:Xns93BF1C6752650fourstomachsspamhotm@130.133. 1.4...
> J.O. Aho say...
>
> > If it's your code, then you should. I think it can be good to include
> > a license in the top too, if you are selling things to otheres.
>
> Thanks. Was probably going to do it anyway, but was just curious
>
The key work is if it's YOUR code... you need to be clear with your client
exactly what they are getting etc. For example many of my clients get no
access to the code for their PHP sites, they are aware I own the code for
which they pay me a yearly fee, they do have the option to buy the code
should they wish. If however one client were to pay me for a days work and
I did work and handed over a disk with the work on - is that my code or
theirs?

hth
nickyboy

On Fri, 25 Jul 2003 17:40:49 +0100, nickyboy wrote:

> The key work is if it's YOUR code... you need to be clear with your
> client exactly what they are getting etc. For example many of my clients
> get no access to the code for their PHP sites, they are aware I own the
> code for which they pay me a yearly fee, they do have the option to buy
> the code should they wish. If however one client were to pay me for a
> days work and I did work and handed over a disk with the work on - is that
> my code or theirs?
>
> hth
> nickyboy

How do you do that? To not let them have access to the php-code?
You set up the complete hosting and don't give them password?
or you compile the php in some way?
Can you please give me some more information?
I'm a student, and i'm building a sort of my own content management
system...and wouldn't like people for which i write sometimes a
-little- script...to have access to my whole cms...
but when writing the little script, i use (parts) of
the cms-code...(the cms is OOP so it's easy to reuse
some functionality of it)

thx in advance for your reply