Thanks. This info is very helpful. On Wednesday, May 20, 2015 at 7:40:50 PM UTC-5, Taylor Savage wrote: > > Hey all, > > Following up here. This was really good feedback to get, and our new > "element product line" organization model helps us form roadmaps like this > for each set of elements. > > We've added Roadmaps now to the READMEs of our major product lines - > iron-elements > <https://github.com/PolymerElements/iron-elements/blob/master/README.md> > and paper-elements > <https://github.com/PolymerElements/paper-elements/blob/master/README.md>. > If you have specific element requests, or there are elements that aren't > listed in the roadmap that you're wondering about, please do file an issue > on the iron-elements or paper-elements meta repo and we'll look to address > them. > > Hope this helps, and again, appreciate the feedback! > > Taylor > > On Sun, May 17, 2015 at 1:46 PM, Anders Holmgren <[email protected] > <javascript:>> wrote: > >> Yes thanks Taylor. +1 for any info on the un-migrated components (i.e. >> what is the plan for them) >> >> >> On Sunday, 17 May 2015 10:34:30 UTC+10, emmanuel buah wrote: >>> >>> Thanks Taylor and for the team for all their hard work. We really >>> appreciate your response. I have been keeping an eye on the migration >>> proces through Chuckh's tool <http://chuckh.github.io/road-to-polymer/> >>> and I think its great. What's missing is information about elements that >>> wont make the migration since a status of "no" or "n/a" via Chuckh's >>> tool <http://chuckh.github.io/road-to-polymer/> can be integrated as >>> >>> 1. Component hasn't be migrated yet >>> 2. Component will not be migrated. >>> >>> It looks like the team is still working through what needs to or might >>> migrate now. Hopefully, once the 0.9 components settle in post migration, >>> users of 0.5 component can go ahead with comp migration. >>> >>> >>> On Saturday, May 16, 2015 at 4:25:20 PM UTC-5, Taylor Savage wrote: >>>> >>>> Hi Anders and Emmanuel, >>>> >>>> Thank you for the questions. Here are a couple specific answers: >>>> >>>> 1. Are core-elements going away or will they be migrated >>>>> >>>> >>>> The core-elements largely have become the iron-elements. The blog post >>>> <https://blog.polymer-project.org/announcements/2015/05/14/updated-elements/> >>>> explains >>>> in more detail the impetus for this change - largely the "core" name was >>>> just the wrong thing to call the old set, so we took the opportunity with >>>> the big 0.5=>0.8+ migration to set up a system for naming element "product >>>> lines" that will last for the long haul. >>>> >>>> Most of the old core-elements have already been migrated to 0.9, and >>>> are available in the PolymerElements >>>> <https://github.com/polymerelements> organization. >>>> >>>> >>>>> 2. How does the new iron-elements in 0.8+ relate to components from >>>>> 0.5. What's the mapping if any? >>>> >>>> >>>> Early on into the port, chuckh <https://github.com/chuckh> created a >>>> really neat tool for following element port status here: >>>> http://chuckh.github.io/road-to-polymer/ >>>> <http://chuckh.github.io/road-to-polymer/> - it's been so good we've >>>> been using this within the team. The "Polymer Elements Converted" section >>>> shows old name => new name mappings. >>>> >>>> In general, we're trying to keep the same suffix name for each of the >>>> elements wherever it makes sense, so that the mapping is straightforward >>>> as >>>> possible. >>>> >>>> We really need a migration guide for the elements too.... Plus a >>>>> status page for the port. >>>> >>>> >>>> Chuckh's tool <http://chuckh.github.io/road-to-polymer/> is so good >>>> that it's our go-to for this. For most elements, the API is largely >>>> consistent, so the bulk of migration should be covered just in the >>>> differences between 0.5 and 0.8+ which is documented on the Polymer >>>> site. <https://www.polymer-project.org/0.9/docs/migration.html> >>>> >>>> We're also working on a brand new way to view element documentation, >>>> that will be live very shortly - we'll update when this is the case! >>>> >>>> Thanks again for bearing with us here - it's a big transition with some >>>> definite rough edges, but one that we think will put the project on a >>>> great >>>> trajectory for the long-term. >>>> >>>> Please let me know if you have any additional questions, >>>> >>>> Taylor >>>> >>>> On Fri, May 15, 2015 at 3:41 PM, emmanuel <[email protected]> wrote: >>>> >>>>> I agree. They just publish a blog post ( >>>>> https://blog.polymer-project.org/announcements/2015/05/14/updated-elements/) >>>>> >>>>> on migration with explanation. I partially get the name change which >>>>> personally is just semantics but we still don't know what core elements >>>>> might not get migrated, if any. Its probably too early to trouble them >>>>> with >>>>> this but its would be nice. I will just wait till the dust settles and if >>>>> there are elements left out of the core, I might just have to migrate >>>>> them >>>>> myself. That's the best we can do for now. >>>>> >>>>> On Fri, May 15, 2015 at 4:40 PM Anders Holmgren <[email protected]> >>>>> wrote: >>>>> >>>>>> I agree. We really need a migration guide for the elements too. >>>>>> >>>>>> Plus a status page for the port. In particular I'm interested in the >>>>>> status of core-list >>>>>> >>>>>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>>>>> --- >>>>>> You received this message because you are subscribed to a topic in >>>>>> the Google Groups "Polymer" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/polymer-dev/9uopgVmWxuk/unsubscribe >>>>>> . >>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> [email protected]. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/polymer-dev/85372ce5-aa62-42ab-a083-cd6bd19bb247%40googlegroups.com >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Polymer" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/polymer-dev/CAH%2BOMnyH8MshqAugMEaunsZxZvxcQZcrEbdcjRmdZStJ%2BMBifw%40mail.gmail.com >>>>> >>>>> <https://groups.google.com/d/msgid/polymer-dev/CAH%2BOMnyH8MshqAugMEaunsZxZvxcQZcrEbdcjRmdZStJ%2BMBifw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >> --- >> You received this message because you are subscribed to the Google Groups >> "Polymer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/27983475-a4d9-4d84-9b10-54cad8875c08%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/27983475-a4d9-4d84-9b10-54cad8875c08%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > >
Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/376e65a8-881a-4f29-9659-387e530064c6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
