Closed (fixed)
Project:
OpenPublish
Version:
7.x-1.0-beta7
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Sep 2013 at 07:39 UTC
Updated:
13 Dec 2013 at 15:46 UTC
Jump to comment: Most recent
Comments
Comment #1
Tran commentedI suspect the inactivity has something to do with Omega 4.
But it's really inconsiderate of Phase II to provide so little information and leave people in the dark.
OP was one of the most important Drupal distributions.
Comment #2
dakke commentedHas development/maintenance truly halted? For if so, I need to rebuild it myself and drop OP 7. Or are there alternatives?
It sure seems to be dead, as stated here.
Comment #3
spade commentedAs of November 14, 2013 there has been a new revision by febbraro, which actually has no changes to the previous:
https://drupal.org/node/323905/revisions
Looks like he wants to keep the project alive ...
Comment #4
kreynen commentedA minor change was made to the project page after a lot of discussion in https://groups.drupal.org/node/365788. The change was to the Maintenance status -> Minimally maintained and Development status -> Maintenance fixes only which is why you don't see any diffs.
Even that is misleading since the distribution itself still includes a now VERY insecure version of Drupal core and should not be used until that is correct. It is not even being minimally maintained.
As part of the D7 upgrade of Drupal.org, warnings are now added to all distributions that are abandoned like this so even if the maintainer isn't acting responsibly by add a message to the project page about the status, potential users are still warned of the potential security issues BEFORE installing it. There is still discussion about the actual wording of the message and what users should actually do about it if you'd like to provide more feedback...
[#8253713]
#2152637: Make it obvious to end-users what to do if a packaged release contains insecure code
It should be clear that you should not install the OpenPublish distribution or any other distribution w/ this warning unless you understand the security issues and plan address them yourself.
Comment #5
Anonymous (not verified) commentedSo much RED after installing and navigating to available updates. Ugh! Aren't Distros supposed to _save_ you time? Hand over the project to some devs that are interested in maintaining it if you aren't going to do it yourselves. It's terribly rude to squat a project to death that others want to patch and keep alive regardless of whether you originally built it or not.
Comment #6
febbraro commentedWe have someone working on upgrades this week if you look at the commits. He is not finished yet but is working toward it. Please save your efforts for more positive conversations.
Comment #7
febbraro commentedComment #8
macmladen commentedFebbaro, I believe you do not like the tone and neither do I but then again, there were first few very polite questions that went unnoticed.
And yet, you didn't take the opportunity to answer the question on the beginning but accepted the 'flame' in somewhat politically correct form.
I'd like you to take that minimum time needed and answer the question on the beginning, at least some general outline, policy as Open Publish is not in hands of some individuals but in Phase 2 as a company.
Sure it is open source and can be forked but that is not constructive nor community friendly approach. For some reason you have abandoned it (or it seams so) so the easy question on whole this discussion is: is it abandoned (being put on ice is the same) or not?
I personally am not dependent as I wished to build site upon but gave up as I was not convinced you will continue to develop it. But this is not a question for me or for you (as Phase 2), it is guideline for those that may jump in unaware that it will not be further developed and for those already in use but stalled as they are waiting for something that will not happen.