Package Management - was: Translations / styles

[bolverk]

My point of view on this:

• We want a package management in the ACP through which you can browse, install, uninstall and update packages
• There needs to be an open source implementation and an interface definition for package repositories
• By default the phpbb.com repository is used
• The user should be able to add any number of custom repositories
• The user should be able to remove the phpbb.com repository
• The fact that a package has been audited on phpbb.com should still be highlighted in some form, so a concerned user can stick to those ones, maybe a warning should be displayed for other packages
• Package contents should be signed and verified - afterall they contain executable code

Would someone volunteer to write down on the wiki what the consensus is here and then point out which areas we should discuss further?

Also agree 100%

[ToonArmy]

if someone *really* wants to do so they always can: after all, this is GPL, and anyone can take the code and do with it whatever they want (within the license stipulations)

We don't want to be in the position that people need to modify code/hack the database to adjust phpBB to how they want, however removing the phpBB (not MODS/Styles) repository should be a special case and probably handled with a specific are you sure.

[bobtheman]

are/will we require plugin devs to follow certain guidelines? any guidelines at all? if we want any form of validation, any accountability, if we require the plugin must be GPL or what ever license... etc etc... as soon as we allow admins to use other repos all these guidelines and criteria go out the window.

Why would a developer follow our guidelines when they can just incentivise admins/users to use a diff repo.. We should be encouraging the devs to submit there plugin to the repo for validation... in order to give the best support, and consistency this is a must.

not to mention this could.. and probably will be confusing to users/admins new to the phpbb forum software.

[DavidIQ]

As it is now, MOD authors should be following our guidelines if they expect their MODs to be validated into the MODDB. I don't expect this to change with phpBB4. And you just gave another reason to show a notice/warning about the MOD/Customisation not being validated by the phpBB Team.

[ToonArmy]

are/will we require plugin devs to follow certain guidelines? any guidelines at all? if we want any form of validation, any accountability, if we require the plugin must be GPL or what ever license... etc etc... as soon as we allow admins to use other repos all these guidelines and criteria go out the window.

We cannot require anybody to follow anything (except the GPL) this is GPL software.

[bobtheman]

are/will we require plugin devs to follow certain guidelines? any guidelines at all? if we want any form of validation, any accountability, if we require the plugin must be GPL or what ever license... etc etc... as soon as we allow admins to use other repos all these guidelines and criteria go out the window.

We cannot require anybody to follow anything (except the GPL) this is GPL software.

again, we can require that for a plugin/addon to be listed on the phpbb repro it must follow said guidelines/ pass validation etc etc...

[ToonArmy]

are/will we require plugin devs to follow certain guidelines? any guidelines at all? if we want any form of validation, any accountability, if we require the plugin must be GPL or what ever license... etc etc... as soon as we allow admins to use other repos all these guidelines and criteria go out the window.

We cannot require anybody to follow anything (except the GPL) this is GPL software.

again, we can require that for a plugin/addon to be listed on the phpbb repro it must follow said guidelines/ pass validation etc etc...

Yes of course, my point was we cannot prevent anyone doing anything with the software within the GPL.