Websites/Plugincheck: Difference between revisions

Websites/Plugincheck (view source)

6 bytes removed , 7 May 2014

m

Confirmed users

210

edits

@@ Line 66: / Line 66: @@
 Another idea that was discussed was plugin release notifications via email.
-) Emails would be sent, in a specified format, from the vendors directly to a dedicated email address.
+# Emails would be sent, in a specified format, from the vendors directly to a dedicated email address.
-) From there a cron would process the mailbox ever say 8 hours
+# From there a cron would process the mailbox ever say 8 hours
-) 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.
+# 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.
-) This data would be inserted into a kind of sandboxed table
+# This data would be inserted into a kind of sandboxed table
-) There would then be a simple Django based admin interface, behind LDAP, that a user can log-in and approve these sandboxed announcements
+# There would then be a simple Django based admin interface, behind LDAP, that a user can log-in and approve these sandboxed announcements
-) At this point it would be moved to the live plugins database.
+# 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.