[ubuntu-us-mi] Generic ID owns application files or individual ID

[gib]

Do you typically use generic ID file ownership when you develop applications or do you
have the source files owned by individual developers?
____________________________________________________________
Online Trading
Online Stock Trading - Straightforward pricing. Powerful tools. Click here!
http://thirdpartyoffers.juno.com/TGL2131/c?cp=dXPCr766pMqNCP5y_xVsVAAAJz2--cgXcJlMV69yYQJtgPtjAAYAAAAAAAAAAAAAAAAAAADNAAAAAAAAAAAAAAAAAAADaAAAAAA=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-us-mi/attachments/20100128/9a0a76b2/attachment.htm

[Robert Citek]

Post by gib
Do you typically use generic ID file ownership when you develop applications
or do you have the source files owned by individual developers?

Can you give some more context or a use-case example?

If you are worrying about the uid on source code, you may want to
reevaluate how you are developing the application. Usually, the
source files are managed by some kind of version control, e.g. cvs,
svn, git, bzr, etc. So it doesn't matter what the uid is on the
files.

Regards,
- Robert

[gib]

Well, so that was a big part of the question. Does it matter if the files on the Linux system are owned by a specific ID? If one developer leaves and some of the files are owned by that one ID then do you have a problem?

---------- Original Message ----------
From: Robert Citek <robert.citek at gmail.com>
To: Ubuntu Michigan Local Community Team <ubuntu-us-mi at lists.ubuntu.com>
Subject: Re: [ubuntu-us-mi] Generic ID owns application files or individual ID
Date: Thu, 28 Jan 2010 17:17:25 -0500

Post by gib
Do you typically use generic ID file ownership when you develop applications
or do you have the source files owned by individual developers?

Can you give some more context or a use-case example?

If you are worrying about the uid on source code, you may want to
reevaluate how you are developing the application. Usually, the
source files are managed by some kind of version control, e.g. cvs,
svn, git, bzr, etc. So it doesn't matter what the uid is on the
files.

Regards,
- Robert
--
ubuntu-us-mi mailing list
ubuntu-us-mi at lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-mi

____________________________________________________________
Love Spell
Click here to light up your life with a love spell!
http://thirdpartyoffers.juno.com/TGL2131/c?cp=LU2nd6RgKynoA_eWV7sulAAAJz2--cgXcJlMV69yYQJtgPtjAAYAAAAAAAAAAAAAAAAAAADNAAAAAAAAAAAAAAAAAAAARwAAAAA=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-us-mi/attachments/20100129/6bf6ba65/attachment-0001.htm

[Robert Citek]

Well, so that was a big part of the question.? Does it matter if the files
on the Linux system are owned by a specific ID?? If one developer leaves and
some of the files are owned by that one ID then do you have a problem?

Yes, but the uid is not the problem. For that just ask the sysadmin
to chown -R all the source files to some other user.

The problem with a specific uid is that it means that no one else will
have copies of the source, which means there was no code review, which
means no one else really understands how the code works, which means
no one else has a clue of where bugs could be, which is a bigger
problem than having a specific uid on the source code.

Regards,
- Robert