[WebComponents] Consider exporting components from gaia for use by third parties



4 years ago
8 months ago


(Reporter: kgrandon, Assigned: kgrandon)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [systemsfe])


(1 attachment)



4 years ago

It is well known that gaia components can provide a huge benefit to third parties and the open web. There are many hurdles to doing this well if we make the canonical component repositories not inside of gaia itself. I think long term it absolutely makes sense to have the element repositories be outside of gaia, but there may be a short-term option that we have not yet thought of.

This bug is not to debate the value of components in external repositories, I believe that's valuable and should be the long term goal. This is only a potential stepping stone to get there, while we solve the bugs necessary to move forward.

Comment 1

4 years ago
Created attachment 8444004 [details]
Exported Repository Experiment

This is an experiment which takes the current gaia custom elements and syncs them all to an external organization. Third party developers may then take these components and do whatever they like with them. They are free to use bower (example provided), npm, or any other solution to install these components.

I believe this will allow third party developers and gaia engineers to effectively start using the same components today easily, without waiting for our internal infrastructure to catch up.
Whiteboard: [systemsfe]

Comment 2

8 months ago
Firefox OS is not being worked on
Last Resolved: 8 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.