We can't stop them from forking it, sure. But just because the license allows it doesn't mean we have to enable the facilities to do it on the page.
We don't delete projects,we just ship them off to CurseForge land if we don't want them on WoWAce.
In any case, no fork has any chance of succeeding, imho. I will definitely not allow it on WoWAce (we do have a project acceptance policy in place here), and some Ace2 fork on CF does not stand much chance of being popular. Considering all projects still using Ace2 are pretty much abandoned, there isn't much chance of those projects actually using that fork, anyway.
People commiting fixes for Dewdrop but not complaining about big Ace2 breakage probably means it didnt just break, eh?
Anyhow, like people said before, it was previously tried to port Dewdrop to Ace3, and we kinda aggreed that a simple port would result in way too ugly code to be really a lib we would want on WoWAce.
If someone insists on writing a new Dropdown library for Ace3 options table, roughly based on Dewdrop if you must, but with clean code and good documentation, well, go for it.
Alternatively, one could also rip out the Ace2 options tables out of Dewdrop and only offer its manual dropdown building system in a seperate lib, i for one used that back in the day occasionally -- not that i'm missing it now.
Anyhow, the alpha builds didnt have many UI changes, it basically only started to be bigger diffs since they disabled addons. We'll just have to wait and see until they are enabled again.
On that note, i haven't seen many changes to the big parts that addons use, like templates, secure headers, and all that. Obviously talent addons and everything working with the guild pane or spellbook will need to be fixed/rewritten, but other then that .. not much yet.
If memory serve, DewDrop and AceOO are the two pieces that do not have replacement.
Indeed thats true. But AceOO really is not needed. If you really want OO, build it yourself with two metatables (or use one of those evil OO libraries).
For DewDrop, well. We wanted to get people into using proper configuration dialogs, and we succeeded. In the beginning, people asked about a successor for DewDrop, but then they just used proper Dialogs.
A Dropdown for a quick-access menu is fine, but that you can do with EasyMenu (or even the dropdown APIs directly) just fine.
It is unsupported, but not "officially" (and kinda still on life support). Announcing end-of-life would hopefully get all remaining authors to switch over and re-code their stuff.
Anyhow, i'm all for the official announcement. Its still long enough to 4.0 for authors to catch up, and addons that haven't been maintained in the last 2 years or so and are still stuck on Ace2 .. well, spring cleaning, i suppose!
In my mind we had this plan all along, but it wasn't really talked about for a while now.
Killing would mean officially announcing its death, what people do with its corpse is not our business then!
But like Torhal said, just don't worry about it anymore. If it breaks, it breaks. The project page gets a note that its EOL and not going to be fixed.