With introduction of "Shared Folders", can we have a "public" share option?

[pyroballpcs]

With the introduction of Shared Folders in 9.5.0, sharinga single library of parts for a project between a private group of developers has become easy and manageable.

For open source projects like the ones I generally work on, however, that functionality still requires that I email-invite anyone who wishes to contribute or spin off their own development using my parts library. I wish to be able to either specify the library as "public" so anyone with the link to it can acquire it, or to allow the full functionality of a managed library to be compatible with git/github or other such development platforms where version tracking is important.

Ideally, I'd like the managed library to live in the same Eagle project folder with my other project files, rather than in a separate folder, while still maintaining the "managed library" functionality of 3D models that can be pushed to Fusion360.

[jorge_garcia]

Hello @pyroballpcs,

I hope you're doing well. Thank you for your suggestion, this is something we are working on. Getting the managed libraries to their current level took a lot of work, we are continuing to work on these features and your suggestion is a logical next step.

I don't have an ETA for it, but it is something we want to do.

Let me know if there's anything else I can do for you.

Best Regards,

[pyroballpcs]

That's great news! I figured it might be in the works, but it never hurts to ask.

As a related question, is it possible to share the current .lbr file I have with someone else in a way that the assigned 3D models also carry over?

Also, mind if I keep this post unsolved til it's implemented?

[jorge_garcia]

Hi @pyroballpcs,

You can totally share your managed library with someone else and maintain the 3D models. Just invite them to your managed folder and they can use the library without issue.

Let me know if there's anything else I can do for you.

Best Regards,

[pyroballpcs]

Sorry for the necro thread, but the proposed solution isn't really what I'm going for.

Other Autodesk applications allow sharing "Public Links" to a project file, which allows users to download the latest iteration without requiring any login or "walled garden" situations. Since I update my parts library which is tied to an open source project, I'd like to be able to do the same with this library, rather than having to send invitations to anyone else who might want access.

[kadah.coba]

When managed libraries originally came out (wasn't that like 3 years ago now?), it seemed like public sharing was either already a thing or soon would be just by the how library.io look on the surface. However there wasn't even sharing within a team on a commercial license at that point, let alone with anyone else. In general, managed libs have been quite disappointing, like >10 minutes to commit a single change on a lib with fewer than 100 parts for example. 

+1 for .lbr being able to support 3d models. I too would have liked having that ability share and commit fully functional part libs to git with their projects. My past OSH projects would benefit from this (new and future revisions of projects have been migrated away from Eagle due to its numerous limitations).