Voting starts in March for the Drupal Association Board election.
(why the issue was filed, steps to reproduce the problem, etc.)
Because media_gallery can now support media 2.x but this is a patch buried in a long comment chain in issue "Make media_gallery work with media-7.x-2.x branch": http://drupal.org/node/1244204
I have provided step-by-step instructions on how to tie together the great efforts of those who made this happen, here, i.e. on how to get media gallery working with media 2.x, using the supplied patch in the same issue comments, here: http://drupal.org/node/1244204#comment-6678836 )
@bangpound suggested a new branch before I did, in comment 104 of the issue: http://drupal.org/node/1244204#comment-6708140 :-
I don't see how the same branch of this module can work with media 1.x and 2.x without making a mess of conditions and overrides. I think the code should be branched.
They also said:
I've updated the patch to use file_entity_access() instead of media_access() which is deprecated and also completely unsuitable for our purposes... one shouldn't need administrator access to view a media gallery's images.
From that I presume we're at a point where the media_gallery code would have to support both 1.x and 2.x media module APIs which would result in messy code difficult to maintain and add features to.
So, having a separate media_gallery 2.x branch for media 2.x *only* - then means that we can support only media 2.x without the legacy of 1.x. Keeps things separate, cleaner, easier to maintain and progress with.
(description of the proposed solution, the rationale behind it, and workarounds for people who cannot use the patch)
Make the media_gallery 2.x branch, so that at the Downloads section near the end/bottom of the drupal.org/project/media_gallery page, we see something like:
- 7.x-2.0-alpha1 (and later alpha2, alpha3, beta1 etc.)
(reviews needed, tests to be written or run, documentation to be written, etc.)
This would be: to actually create the branch.
User interface changes
(new or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text)
As per code in media_gallery 2.x whatever changes need to be made to support media 2.x
(API changes/additions that would affect module, install profile, and theme developers, including examples of before/after code if appropriate)
As per above, previous section.
Original report by [username]
// Text of original report here.
(for legacy issues whose initial post was not the issue summary)
Discussed previously in these places: