kmoore134
10-12-2005, 09:14 PM
Well folks, the PBI stuff has really taken off in the past few weeks, and it's time I hand it over so I can get back to working mainly on the OS again :) I've gone ahead and put together this proposal on how the PBI's should be inspected / administered here in the future.
-- PBI Approval Team --
The PBI Approval team will consist of about 5-7 people. These folks
will be given admin access to the PBIdir.com site, where they can add
/ remove various PBI's from the portal, as well as FTP access for uploading
these PBI's to the FTP mirrors. These people will also have the duty of
inspecting PBI's according to the following checklist, and communicating
with the developers who submit their PBI's for inspection.
PBI Approval Checklist
* Does the PBI file install / remove properly. (No Errors) (Y/N)
* Was it created with the most recent PBI creator (Within Reason) (Y/N)
* Does it modify the system unnecessarily in any way? (Y/N)
- I.E. Does the PBI.SetupScript.sh file copy any files to the filesystem outside of the PBI's home directory? Does it copy libraries to the system when they should be self-contained?
- Some programs *need* to modify the system, such as Drivers, or services like Apache, but regular user-land apps like XMMS or games probably don't have a reason to be modifying the system in any way. If the program is copying libraries anywhere on the box *be careful*, this is a problem waiting to happen.
* If the program copies or modifies files on the base system, does it clean them up when removed? (Y/N)
- I.E. Does the PBI.RemoveScript.sh file clean up anything that the PBI.SetupScript.sh file creates?
* Does the program install and operate on a *fresh* installation of PC-BSD? (Y/N)
- This is sometimes the only way to make sure the PBI has all the libraries it needs for operation.
* Does the program launch and run properly within reason? (Y/N)
- If the program works, great. If it works, but it's buggy, that can be fine also, since that's the nature of opensource beta (or release) products.
* Does the program violate any copyright(s)? (Y/N)
- If the program does not permit redistribution, please don't upload it!
People who wish to become apart of this team will need to have at least a bit of shell experience, and access to a system where they can test and break things :) If this is something you want to help out with, please e-mail me at kris@pcbsd.org, with a little bit of information about yourself, and I'll see about adding you to this group. Members of this team will also get a <username>@pcbsd.org e-mail address, so you look nice and official :)
-- PBI Approval Team --
The PBI Approval team will consist of about 5-7 people. These folks
will be given admin access to the PBIdir.com site, where they can add
/ remove various PBI's from the portal, as well as FTP access for uploading
these PBI's to the FTP mirrors. These people will also have the duty of
inspecting PBI's according to the following checklist, and communicating
with the developers who submit their PBI's for inspection.
PBI Approval Checklist
* Does the PBI file install / remove properly. (No Errors) (Y/N)
* Was it created with the most recent PBI creator (Within Reason) (Y/N)
* Does it modify the system unnecessarily in any way? (Y/N)
- I.E. Does the PBI.SetupScript.sh file copy any files to the filesystem outside of the PBI's home directory? Does it copy libraries to the system when they should be self-contained?
- Some programs *need* to modify the system, such as Drivers, or services like Apache, but regular user-land apps like XMMS or games probably don't have a reason to be modifying the system in any way. If the program is copying libraries anywhere on the box *be careful*, this is a problem waiting to happen.
* If the program copies or modifies files on the base system, does it clean them up when removed? (Y/N)
- I.E. Does the PBI.RemoveScript.sh file clean up anything that the PBI.SetupScript.sh file creates?
* Does the program install and operate on a *fresh* installation of PC-BSD? (Y/N)
- This is sometimes the only way to make sure the PBI has all the libraries it needs for operation.
* Does the program launch and run properly within reason? (Y/N)
- If the program works, great. If it works, but it's buggy, that can be fine also, since that's the nature of opensource beta (or release) products.
* Does the program violate any copyright(s)? (Y/N)
- If the program does not permit redistribution, please don't upload it!
People who wish to become apart of this team will need to have at least a bit of shell experience, and access to a system where they can test and break things :) If this is something you want to help out with, please e-mail me at kris@pcbsd.org, with a little bit of information about yourself, and I'll see about adding you to this group. Members of this team will also get a <username>@pcbsd.org e-mail address, so you look nice and official :)