If we look at recent history, we see that my old mate @bangpound has quietly dropped off the (Drupal) planet.
( @bangpound collaborated with @mlncn, @catch and myself a full decade ago, on a fascinating academic Drupal project )
Drupal.org account (and twitter) have been withdrawn, and although some activities continue elsewhere, they are not continuing here.
I won't delve further into those decisions further than that here, but I think we can read it as a goodbye for now.
BUT, I do have some affection for oEmbed module, and oEmbed as a web content strategy in general. I've tried to use and nudge it along where possible in the past, though not to any great effect.
I have some experience, and a lot of opinions on how embedding can be made easier for editors, at the same time as making it more resilient to future API changes and archiving needs, and I think that (richly annotated) oEmbed is a large part of that strategy.
Previous work in this field (half sandboxes for client work)
We can see that no currently active Drupal.org community member has touched this module for 3 years, and there is weekly interest from the community.
The D8 code I have reviewed so far looks like it's got a huge amount of the structure sitting there and *almost* working. I feel that "the back has been broken" on the upgrade work here, but there are a number of edge cases to be ironed out.
I am volunteering to take on maintainer-ship of this module - at least for an evaluation period of a few months. I'd need to be able to confidently address the obvious issues and get it to a point where it was more approachable for users. I can't make a strong commitment to an ongoing 'stable' state yet, as I can't say if there are good reasons for this to have been abandoned, but I'm optimistic .... and also want to welcome any collaborators.
I'm still considering the implications, and time commitment for this, but would welcome feedback/endorsement at this stage, and would push this request through the process If I still feel confident about this in a week or so.
Comments
Comment #2
dman CreditAttribution: dman as a volunteer and at Sparks Interactive commentedComment #3
dman CreditAttribution: dman as a volunteer and at Sparks Interactive commentedComment #4
dman CreditAttribution: dman as a volunteer and at Sparks Interactive commentedComment #5
dman CreditAttribution: dman as a volunteer and at Sparks Interactive commentedComment #6
manarth CreditAttribution: manarth commented+1 for transferring maintainership of the module to dman.
Dman actively maintains a number of Drupal modules, and would be a good steward for taking this module forward.
Comment #7
ugintl CreditAttribution: ugintl commented+1
Comment #8
mglaman+1, I just had to custom implement this. Using
"alb/oembed": "^1.1"
and an adjusted version of the filter, it "just works" for Filter plugin.Comment #9
ugintl CreditAttribution: ugintl commented@mglaman Can you please explain a little what your code actually does?
Comment #10
mglaman@ugintl it's a Filter plugin that provides oEmbed functionality. It's the current port's filter using a different library which is actively supported.
When using
"alb/oembed": "^1.1",
I had full migration support of oEmbed from D7 -> D8 in my personal blog using that filter, also found https://github.com/mglaman/glamanate.com/blob/master/web/modules/custom/....This module could easily have an 8.x beta by just changing to a supported library.
Comment #11
adam-delaney CreditAttribution: adam-delaney at The University of Iowa commentedDo we have an update on this?
+1 for transferring maintainership of the module to dman.
Comment #12
DamienMcKennaIt has been almost a year since the offer was first made, the official policy for dealing with abandoned projects says to wait two weeks and then transfer the issue to the Project Ownership queue.
Comment #13
joseph.olstadthis could use a tagged release for the various branches, DMan are you still interested?
Comment #14
apadernoThe project link is https://www.drupal.org/project/oEmbed. I am changing status, waiting for a response from @dman.
Comment #15
apadernoI also sent a message to the user who is the current project owner.
Notice that, while I asked to reply within two weeks, that doesn't mean any action will be taken right when two weeks are passed.
Comment #16
apadernoI apologize for the delay in replying here. I got an email message as reply to mine, and I read it right today, after setting back my email client.
If there are other users who are interested, let me know it. I don't see any reply from dman, so I am not sure he wants to be maintainer of the module.
Comment #17
dman CreditAttribution: dman as a volunteer and commentedI’ve not been active doing Drupal stuff for a year. On hiatus, and largely without any development machines.
I plan to get back to / continue with Drupal eventually, but cannot commit to any proper maintenance support of this module at this time. Still following with interest.
Sorry.
Comment #18
apadernoLet's see if there are users who will to being the new maintainers. If there aren't volunteers, I think the module should be marked as not supported.
Comment #19
joseph.olstadIf you can't find anyone else I will take maintainership of oembed and see what I can help push along.
just don't expect miracles for the next 4 months because I am very committed until April 1st.
Comment #20
apadernoI am setting this issue as postponed until April first, 2019.
Comment #21
apaderno@joseph.olstad Is your offer still valid?
Comment #22
joseph.olstadya sure I'll take ownership of it. I have a D7 client right now using media.
Thanks in advance
Comment #23
apadernoI changed ownership as requested.