Confirmed users
210
edits
Websites/Plugincheck: Difference between revisions
→Ideas On Improving PluginCheck
Espressive (talk | contribs) mNo edit summary |
Espressive (talk | contribs) |
||
| Line 61: | Line 61: | ||
3) When the bug is created, the list of people who can update the plugins DB, as well as the QA person, is automatically CC'd via email. | 3) When the bug is created, the list of people who can update the plugins DB, as well as the QA person, is automatically CC'd via email. | ||
4) Over time, as more users reach a certain trust level, we can add more people to the CC list who can then act on those bugs. | 4) Over time, as more users reach a certain trust level, we can add more people to the CC list who can then act on those bugs. | ||
== Plugin Announcements via Email == | |||
Another idea that was discussed was plugin release notifications via email. | |||
1) Emails would be sent, in a specified format, from the vendors directly to a dedicated email address. | |||
2) From there a cron would process the mailbox ever say 8 hours | |||
3) If new mail exists, it would be picked up and the data in the mail would be transformed into a format that is required for the DB. | |||
4) This data would be inserted into a kind of sandboxed table | |||
5) There would then be a simple Django based admin interface, behind LDAP, that a user can log-in and approve these sandboxed announcements | |||
6) At this point it would be moved to the live plugins database. | |||
With the above there was security concerns raised around the email portion of this solution and, I believe, after some discussion, this has largely been abandoned. | |||
== Plugin Data as an Open Service == | |||