pull request #1 was too ambitious; capture comments & cancel request
mobilemind opened this issue · comments
The original pull request was perhaps too ambitious, and a more limited (in terms of changes/scope) and focused "1.5.x" approach may be more practical, expeditious to specify, and more likely to be adopted.
This issue suggests the following approach:
- Cancel the original pull request, and instead capturing key comments as separate issues here.
- Issuing a new pull request on a new branch (tentatively)
draft-1.5
that contains only reformatting to markdown. - Track, discuss and and resolve the captured issue here via smaller, more focused, sets of comments and pull requests.
ORIGINAL PULL REQUEST 1 FOCUS (To be closed. Quoted here for reference)-
The PEN 2.0.0 revision focuses on four goals:
1. Package format updates: The addition of contemporary package formats such as xAPI and cmi5.
2. Batch or multi-package processing: Streamlining for the transfer and notification processing of multiple packages.
3. Permissions and security: More contemporary approaches to permissions, such as OAuth. Explicitly indicated preference for HTTPS in lieu of HTTP, and for SFTP in lieu of FTP.
4. Mobile-enabled alerts and notifications: Enabling modern mobile alerts and notifications such as SMS, Apple Push Notification Services (APNS), Firebase Cloud Messaging (FCM), and Google Cloud Messaging (GCM).
key facts of comments on PR #1 have been recast as issues. A "clean" draft of PENS 1.5.0 is yet to be prepared and submitted as a pull request. Watch for it next week.
Cancelled pull request. Creating new branch for a "PENS 1.5" that focuses on package format updates and minimal updates to require TLS for endpoints with PENS 1.5, and strongly recommend it for 1.0.0 implementations. Future pull request will be smaller in scope.