Should be full project

+1, please make this a full project!

+1, I agree

Are we ready for a full release? A List of release blocker would be useful...

Would love to see this as a full project as well.

Would also love to see this as a full project !

I agree, has there been any discussion with the Media module maintainers about including multiselect in the main module? I would be willing to become co-maintainer if this becomes a full module.

Anybody else interested in working on this?

Hi, Sorry for my absence from this. Sure, I wouldn't mind trying to make this into a real project, or trying to have it incorporated into Media itself (possible as a submodule within Media).

The approach taken in this module is a little bit hacky (in that it basically relies on the Media form-api things, and fiddles around with it endlessly) and was made to scratch an itch we had at the place I work. So many of the problems this sandbox have had (break when using other modules that alters the form-api arrays to achieve something) is because of this approach, which is why I've kept it as a proof-of-concept sandbox so far.

But since no one else seems to be coming up with any better ways of solving this problem, I guess this is the currently best feasible way of doing it. Has anyone here gone through the process before and can give useful hints?

Well I guess the journey starts here :https://drupal.org/node/1011698 Some reading up to do.
But the second step would be to get a discussion going with the media maintainers I think.

Okay, so the checklist before applying is the following:

1. Basic application checks
   1. Ensure your application contains a repository and project page link.
   2. Ensure your project is not a duplication.
   3. Ensure you don't have multiple applications.
2. Basic repository checks
   1. Ensure the repository actually contains code.
   2. Ensure you are working in a version specific branch. Just added a 7.x-1.x branch
   3. Ensure your project contains a minimum of handwritten code.
3. Security Review
   1. Ensure the project does not contain any security issues. I don't think it does - but if anyone is up for a review, that'll be nice
4. Licensing checks
   1. Ensure the repository does not contain a ‘LICENSE.txt’ file.
   2. Ensure the repository does not contain any 3rd party (non-GPL) code.
5. Documentation checks
   1. Ensure the project page contains detailed information.
   2. Ensure the repository contains a detailed README.txt.TODO
   3. Ensure the code contains a well-balanced amount of inline-comments.I don't know if there's enough..
6. Coding standards and style
   1. Run an automated review and ensure there are no major issues. I just ran coder, and fixed all issues
7. API and best practices Review
   1. Ensure you are using Drupals API correctly.

I have crossed out the items I think this sandbox already fulfils.

So a README.txt is outstanding, as well as a preliminary security-review from someone not me. That's not too bad.

@fangel Nice project! The remaining TODOs in #10 can be made into issues for better tracking & tagged as 'Stable release blocker', then the sandbox could be made into a full project without concern. Just ensure the release blockers are done before a stable release is created.

fangel, thank you for initializing and streamlining file uploads in D7 a reality. Drupal distributions are poised to make a major impact in enterprise and many other solutions that are end user intensive. I hope this module can be promoted at Drupalcon Austin with the Media folks and get this official. D7 needs this now, and D8 may not be battle tested until later in 2015. This fills a major UI need today!

Given the severity of media module changes which break this sandbox, for example, https://drupal.org/node/2187837 . . . I really think that this should be a sub-module of Media if at all possible.

I very much developed this proof-of-concept with the end-goal of having it (or more likely, something similar) put as a Media-submodule. Because trying to keep up to the always-slightly-changing Media API is quite a bit of work, and would be better done by the people that changes the API.
This implementation was always meant to work, but never intended to be pretty. It does a lot of unsavoury things with the Form API arrays to make it work, without duplicating too much code form Media. Unfortunately this means that it's very prone to breaking on small changes within Media.

I am busy writing my MSc thesis currently (and is from/living in Europe), so I can't personally be in Austin to promote the addition of this functionality as a submodule to Media - but I would be all for someone else doing it.
But someone should corner the Media guys and insist that they add multi-selection as a built-in (via submodule) functionality. It's been a while since I did this work, and a bit longer since I was up to speed with the Media development, but I would gladly share any inputs I have on how it can/should be done.

Congratulations for this module. This is really a must have!!! For me it works with current stable Media 7.x-1.4. I don't want to use Media 7.x-2.x on production sites while is not stable. I also wish this module reach full project status as soon as possible.

If someone still need multiple select/upload I think this patch should do it. Did not try it yet, but I will.

Greetings. Here's a quick README.md patch to help check off an item. I'll be using this on a project and would love to see it get promoted. Please let me know if you have any questions.

Helps if you upload a patch that has content, mark...

The README.txt file should wrap at 80 characters, like comments.