Encryptr isn't being actively developed #203

Closed
opened 2017-03-22 12:23:21 +00:00 by trosel · 4 comments
trosel commented 2017-03-22 12:23:21 +00:00 (Migrated from github.com)

https://github.com/SpiderOak/Encryptr/issues/286

I don't think this should be featured on the site.

https://github.com/SpiderOak/Encryptr/issues/286 I don't think this should be featured on the site.
dnguyen01 commented 2017-03-22 14:37:09 +00:00 (Migrated from github.com)

The last commit was in July 19, 2016 (https://github.com/SpiderOak/Encryptr/commits/master) and that was to update the README.md file. I checked the App Store (iOS) and last release was in Dec 19, 2015; Play Store in December 7, 2015. Looks like development for the password manager is secretly dropped. Probably a good note to remove software that isn't actively developed and not been given the silent treatment.

The last commit was in July 19, 2016 (https://github.com/SpiderOak/Encryptr/commits/master) and that was to update the README.md file. I checked the App Store (iOS) and last release was in Dec 19, 2015; Play Store in December 7, 2015. Looks like development for the password manager is secretly dropped. Probably a good note to remove software that isn't actively developed and not been given the silent treatment.
trosel commented 2017-03-22 16:04:52 +00:00 (Migrated from github.com)

Same with some other Spider Oak tools.

I think there should be a threshold for activity, but also for how many developers contribute.

No one should be recommending a tool that only has 1 contributor, either.

Same with some other Spider Oak tools. I think there should be a threshold for activity, but also for *how many developers contribute*. No one should be recommending a tool that only has 1 contributor, either.
kewde commented 2017-04-07 13:30:25 +00:00 (Migrated from github.com)

As a note that shares some relevance to this issue, I don't think inactivity of development in itself is a reason to drop a project unless there are outstanding security issues. If a tool is secure as is and it works as expected, then I don't see an issue with discontinued development as long as there is a commitment to fixing upcoming security issues (which isn't the case in this example so the removal is okay imo).

As a note that shares some relevance to this issue, I don't think inactivity of development in itself is a reason to drop a project unless there are outstanding security issues. If a tool is secure as is and it works as expected, then I don't see an issue with discontinued development as long as there is a commitment to fixing upcoming security issues (which isn't the case in this example so the removal is okay imo).
ghost commented 2017-04-07 13:42:37 +00:00 (Migrated from github.com)

Depends on the kind of tool.

Depends on the kind of tool.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#203
No description provided.