Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wikiki project no longer exists, 17 out of 29 advertised extensions aren't actually available. #3976

Open
dtbullock opened this issue Apr 2, 2025 · 15 comments

Comments

@dtbullock
Copy link

Takes the wind out of Bulma's sails a bit. If someone has code/fork of the previous repos, can't they be uploaded to a side project?

@dtbullock
Copy link
Author

Oh, and17 links at https://bulma.io/extensions/ lead to a 404.

@guest20
Copy link

guest20 commented Apr 2, 2025

Maybe these projects (or their cdn versions, at least) can be recovered from archive.org?

@dtbullock
Copy link
Author

Might be available at https://app.unpkg.com/bulma-extensions@6.2.7 ... but how to download them all quickly?

@dtbullock
Copy link
Author

OK, looks like npm can download them. So we have sources and minified outputs, but no build files. It's a start. Will have to examine licences if available, then put up a github repo. Do you think, being 6 years old, the previous repo simply got archived in recent Github cleanups? Would they not have kept an archive that can be retrieved?

@dtbullock
Copy link
Author

The licence is MIT. We don't have any build-files and we don't have any doco. Being so old, there is likely a modernisation effort required as well.

@dtbullock
Copy link
Author

And there's an email address for the original author in the package.json.

@dtbullock
Copy link
Author

And it's the same address as is in the README for the 5 @CreativeBulma extensions, which are also 'on ice' looking for a maintainer (these particular extensions aren't part of the 29 listed on the bulma.io/extensions/ page).

@dtbullock
Copy link
Author

So it might be possible to get the wikiki sources with the build scaffolding too.

@gaetan-hexadog
Copy link

Bulma-Calendar extension is now maintained by @michael-hack in this repo : https://github.com/michael-hack/bulma-calendar

List of found Forks:

@Log1x seems to have forked some repos 8 years ago: https://github.com/Log1x?tab=repositories&q=bulma-&type=&language=&sort= to adapt to stylus (maybe it can be used as base)

but it seems there is no build tool included except for CreativeBulma extensions and bulma-switch (maybe we can use them too as base for build)

@gaetan-hexadog
Copy link

gaetan-hexadog commented Apr 5, 2025

And I downloaded the entire bulma-extensions package (https://www.npmjs.com/package/bulma-extensions), which I’ve made available as a ZIP here: https://limewire.com/d/NDXB7#dfRiuUnFLz

So I think by using the code from this ZIP and trying to recreate the build setup from bulma-calendar from @michael-hack which was forked from wikiki repo so build process used should be more up to date.

And if some of the extensions in bulma-extensions are outdated, we can manually install them via npm to get the latest sources and try to use the bulma-calendar build process with them.

@michael-hack
Copy link

michael-hack commented Apr 6, 2025

Hi everyone,

it's a great pity that Wikiki has now apparently stopped altogether and even deleted its account. This just shows again that open source and collaborative work is mostly done on the shoulders of a few.

When I took over the Bulma calendar repo from him years ago, he was already looking for new maintainers for almost all projects. Too bad, if I had known that, I would have just taken over all the repos back then, even if I wouldn't have had time for further development. At least the repos wouldn't have been deleted.

Regarding the Bulma calendar, the repo is the current and official version. The build process should also be relatively clean, but there has also been some work accumulated over the last six months that I unfortunately haven't found the time for yet.

Oh, and it's not forked, he gave me the ownership for the repo.

@michael-hack
Copy link

Oh no, I just saw that he also deleted the NPM account and thus the projects there.

Unfortunately, he wasn't able to give me the package there. I'll see what I can do on Monday.

@gaetan-hexadog
Copy link

gaetan-hexadog commented Apr 6, 2025

I've contributed to the CreativeBulma repositories and had them reopened so anyone can request a transfer of ownership by opening an issue. Personally, I don't have time to maintain them.

I also retrieved access to CreativeBulma npmjs account so I can transfer it to anyone who would like to maintain CreativeBulma's extensions.

Unfortunately, CreativeBulma doesn't seem to have forked the wikiki repositories :-(

@gaetan-hexadog
Copy link

gaetan-hexadog commented Apr 6, 2025

I've contributed to the CreativeBulma repositories and had them reopened so anyone can request a transfer of ownership by opening an issue. Personally, I don't have the time to maintain them, so I won't be taking them.

I also retrieved access to CreativeBulma npmjs account so I can transfer it to anyone who would like to maintain CreativeBulma's extensions.

Unfortunately, CreativeBulma doesn't seem to have forked the wikiki repositories :-(

After some research we were able to find out a draft rework of bulma-carousel extension (forked from wikiki's original repo at the time). I uploaded it to new repo in my account here: https://github.com/gaetan-hexadog/bulma-carousel

I also created a repo with bulma-extensions downloaded from NPM - There is no build process in sources but it can be useful to recreate packages : https://github.com/gaetan-hexadog/bulma-extensions

I WON'T MAINTAIN THEM. I just put them in my github so someone can take it back. Contact me if you want me to transfer them to you.

@michael-hack
Copy link

A short info, I have now requested the ownership for the bulma-calendar package from NPM Support. But this may take some time until the request has been processed.

Good luck with the other packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants