[wp-trac] [WordPress Trac] #56858: Blogger Importer: Undefined (dynamic) properties

[WordPress Trac]

#56858: Blogger Importer: Undefined (dynamic) properties
-------------------------------+----------------------------
 Reporter:  ironprogrammer     |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  WordPress.org
Component:  Import             |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  needs-patch php82  |     Focuses:
-------------------------------+----------------------------

Comment (by jrf):

 > Per https://core.trac.wordpress.org/ticket/49143#comment:4, importers
 are still under the Core Trac umbrella, which seems confirmed with their
 WordPress GitHub org consolidation via
 https://meta.trac.wordpress.org/ticket/5550.
 >
 > But yes, addressing importer issues does feel like an upstream matter.

 @ironprogrammer I see... It just feels like more noise while the issue
 cannot be solved in Core, but should be solved in the plugin repo.

 > However, given the near invisibility of those repos, and lack of
 attention they're likely to get on their own, it seems appropriate to
 continue to report and track these issues here (and the community appears
 to feel the same).

 Which actually highlights a much more pertinent problem, for which it may
 be a good idea to have a discussion on Make: **there are quite a few repos
 in the WP GitHub organisation which do not seem to have a dedicated
 maintainer(s) attached to it.**

 All Core committers do have commit rights to those repos AFAIK and
 occasionally some of them (us) use those rights to merge things, but it
 seems like, for the most part, these repos are unmaintained and even when
 something does get merged, there is often no CI/QA in place, there is no
 documented release process and nobody takes responsibility....

 Considering the code of some of these packages ships with Core and/or is
 actively promoted by Core, like the Importer plugins, it is my opinion
 that this needs to change.

 In a lot of cases, the maintenance burden will be small, once the initial
 backlog (no CI, no CS, no tests) has been addressed and will mostly
 consist of keeping up with PHP changes, keeping the CI running and passing
 etc, but having someone take "ownership" for each of those projects would
 help and clarify communication lines as well.

 /cc @dd32 @ocean90 (as I seem to remember I've seen both of you active in
 some those repos on occasion)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/56858#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform