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

Materialize Classified "Abandoned" #6438

Closed
mckenzieja opened this issue Aug 22, 2019 · 53 comments
Closed

Materialize Classified "Abandoned" #6438

mckenzieja opened this issue Aug 22, 2019 · 53 comments

Comments

@mckenzieja
Copy link

With outstanding pull requests with mostly no feedback from project members it's safe to say this project is now abandoned.

@unguul
Copy link

unguul commented Aug 23, 2019

Certainly looks like it.

@DanielRuf
Copy link
Contributor

It is not. See the current branches.

@unguul
Copy link

unguul commented Aug 26, 2019

@DanielRuf Indeed. There's activity around but no releases for almost 1 year now and the PRs and issues are just piling up. axios is in a similar situation. Tough world this open source thing.

Since other people have asked about this in #6319 and @Dogfalo is saying the main contributors are taking a break, maybe we should put a big fat message in the readme saying "We're on a break, stop asking if the project is abandoned!" 😄

@DanielRuf
Copy link
Contributor

Also if people need a release they can support the project and often also fund it. There is https://materializecss.com/support-us.html

@Dogfalo
Copy link
Owner

Dogfalo commented Aug 27, 2019

It's true that we haven't released in a while, but we are not abandoning the project. We will figure out a dev/release schedule that works well for us to continue delivering updates

@Pierstoval
Copy link
Contributor

@Dogfalo
image

Are these releases only available for your backers on Patreon offering you $2,160 per month?

@DanielRuf
Copy link
Contributor

@Pierstoval you have to substract the costs / fees from this number.

As you can see there is some progress on the current branches.

I think at the moment others things are more important than this.

@Pierstoval
Copy link
Contributor

Yep, indeed about the fees.

However, about this:

As you can see there is some progress on the current branches.

I'm sorry but I must disagree: the commit activity graph tells me otherwise. Latest commit is 38e1fc5 (Date: 2020-02-24 17:51:24 -0800) and this doesn't really seem like "recent activity", especially when considering the fact that most of the latest commits in other branches (notably gh-pages) are unrelated to any bugfix/fixtures, and the latest commit related to a PR is cb1f7b7 (#6471) which was like six months ago.

I really don't want to seem displeasant, and if I do, I sincerely apologize.

I mostly speak for the voice of the many people that await a new release, not only for features but mostly for fixes, since PRs are not merged. And since the package is not declared abandoned, people are quite not confident in making a fork and maintain it.

There's the solution for "seeking contributors" announcements in order to give some people the right to merge PRs and create releases, like Impress.js did a couple of years back when Bartaz declared not to want to maintain the lib anymore, or change the ownership. Or declare it abandoned.

I totally understand there are more important things than the state of Materialize, I know what it is to be a maintainer. It's just that the future about the project is quite unclear, and some clarifications could be really helpful for the community, and maybe lead the path for a fork that wouldn't move too far from Materialize's spirit in the first place :)

As said, I don't want to rush, I'm asking questions, I hope the team is doing well :)

@DanielRuf
Copy link
Contributor

There's the solution for "seeking contributors" announcements in order to give some people the right to merge PRs and create releases, like Impress.js did a couple of years back when Bartaz declared not to want to maintain the lib anymore, or change the ownership. Or declare it abandoned.

Well, @tomscholz and me had some rights a while ago but since this is hosted under the private account of one of the maintainers there will not happen much in the near future I guess.

@acburst @Dogfalo please let's move this to an org, invite all past contributors and give them rights to do reviews and some should also be able to merge PRs (I could help with that like I did in the past).

https://github.com/materialize

@DanielRuf
Copy link
Contributor

If there will be no change in the next two weeks I will go ahead, create a new org and do all the required steps to bring materialize forward.

@Pierstoval
Copy link
Contributor

🎉

@DanielRuf
Copy link
Contributor

If there will be no change in the next two weeks I will go ahead, create a new org and do all the required steps to bring materialize forward.

There you go: https://github.com/materializecss/materialize

Who wants to join?

@Dogfalo
Copy link
Owner

Dogfalo commented May 2, 2020

Thank you @DanielRuf for helping bring the project forward.

Lets try a different approach here, if we can get 5 people to post here who are interested in helping out with the project and we have that we can create a team in the official org instead of trying to divide the existing community.

@DanielRuf
Copy link
Contributor

Lets try a different approach here, if we can get 5 people to post here who are interested in helping out with the project and we have that we can create a team in the official org instead of trying to divide the existing community.

At least me.

@DanielRuf
Copy link
Contributor

I think @Pierstoval and @doughballs too.

@Pierstoval
Copy link
Contributor

Yup 👍

@doughballs
Copy link

Hey 😀

@ecoztas
Copy link

ecoztas commented May 3, 2020

Yeah 👍

@DanielRuf
Copy link
Contributor

@tomscholz what about you? Would you like to help again?

@doughballs
Copy link

@Dogfalo is 5 a deal breaker? Or could we proceed with 4?

@aeris-alex
Copy link

I'm a new to this project (using it for a project at work) but would be happy to help where I can.

@Dogfalo
Copy link
Owner

Dogfalo commented May 21, 2020

Yea it does not have to be 5, although it is definitely preferred that it is someone who has contributed before

@doughballs
Copy link

I understand. I think it would be wise to get things moving and not let the opportunity pass - start to build confidence, stop any more users dropping off - even small changes/announcements at this stage would send out a good signal. I haven't contributed previously but I'm very willing and I'm already helping the community in whatever ways that I can.

It would be great to know if there is a plan (and if not, let's make one!)

@Pierstoval
Copy link
Contributor

First: let's fix the XSS issues in autocomplete (and some others), I guess 😉

@DanielRuf
Copy link
Contributor

@Pierstoval still, this would be breaking changes. Nothing that we should do in a patch release.

My statement still stands. If you accept user input you should ensure to sanitize it. Because if we fix this we have to introduce a new attribute which allows unsanitized input / does not apply the changes (like dangerouslySetInnerHTNL of react).

@doughballs
Copy link

This is why we need a plan of action - is @Dogfalo going to lead? Like any other project, it will work better if someone leads and we have a clear vision.

@doughballs
Copy link

I think a good starting point is the documentation. The main thing cropping up on Gitter and Stack Overflow is the undefined options variable in every vanilla JS init. If people copy and paste, the code doesn’t work - this is not good. The examples need fleshing out too.

@Pierstoval
Copy link
Contributor

@doughballs I didn't encounter this for a while now, do you think you can create/copy an issue for this onto the new repo? 😉

@OliverwengFiltered
Copy link

@DanielRuf @Dogfalo

any updates? wanted to get this CSS framework rolling again.

I have some polyfills for some of the js function to push up if needed.

Thanks

@DanielRuf
Copy link
Contributor

@OliverwengFiltered you are very welcome to contribute to https://github.com/materializecss/materialize when you find some time.

@ecoztas
Copy link

ecoztas commented Jul 17, 2020

I think Materialize's team is not continue this project. So @DanielRuf, @Pierstoval, @doughballs, @OliverwengFiltered and me can create new project based on Materialize v1.

Roadmap:

  • New name
  • New logo
  • New domain & website
  • Rebuild project structure
  • Remove jQuery
  • Update depencies (waves, normalize, animejs etc.)
  • Solve issues

We can create new version in a short time!

If you agree with me, let's start!
(write me on skype: emrecanoztas)

@DanielRuf
Copy link
Contributor

  • New name

not needed, this is a fork which will continue the work

  • New logo

not needed, this is a fork which will continue the work

  • New domain & website

work in progress

  • Rebuild project structure

not sure what you mean

  • Remove jQuery

already happened in materialize 1.0.0 ;-)

  • Update depencies (waves, normalize, animejs etc.)

on our roadmap

  • Solve issues

on our roadmap

Please see https://github.com/materializecss/materialize =) PRs and issues are very welcome. You can already contribute.

@ecoztas
Copy link

ecoztas commented Jul 17, 2020

Hey @DanielRuf,

  • New name
    Like semantic-ui -> fomantic-ui

  • New logo
    Like semantic-ui -> fomantic-ui

  • Rebuild project structure
    Create a new project structure. For example; development of Bower does not continue.

  • Remove jQuery
    Materialize v1.0.0 is still support jQuery ;)

  • Please see https://github.com/materializecss/materialize =https://github.com/materializecss/materialize) PRs and issues are very welcome. You can already contribute.
    It's your project and does not appeal to us! Only contributer you in there.

@occirol
Copy link

occirol commented Jul 17, 2020

Hey @ecoztas,

It's your project and does not appeal to us! Only contributer you in there.

There is 5 members in the org as for now. We are still in the organization process, yet. So @DanielRuf may be the only contributor as for now but as stated, you are very welcome to already contribute.

@DanielRuf
Copy link
Contributor

  • New name
  • New logo

No, no need, we keep the name, it will be probably the org name + materialize - we want to make the switch as easy as possible. We do not want to reinvent the wheel and allow people to easily switch back if needed.

The goal is to fix the open bugs and keep everything else (name, logo and so on) as far as possible.

  • Create a new project structure. For example; development of Bower does not continue.
    Not the goal of the fork. We will probably remove the bower.json file in the far future. Nothing that has to be done now.
  • Materialize v1.0.0 is still support jQuery ;)

Not a short-term goal of the fork.

  • It's your project and does not appeal to us! Only contributor you in there.

Not sure what you mean. Everyone is possible to create issues at https://github.com/materializecss/materialize/issues and open PRs at https://github.com/materializecss/materialize/pulls, this is a normal fork =)

Contributor is everyone, collaborators are these with more rights (members of the org - see the small label on each comment, I'm the owner of the org with all needed rights). You can fork the fork, change things and open PRs, like with every normal repo - this is the normal contribution process.

@DanielRuf
Copy link
Contributor

Also I'm not the only active contributor. I have merged some of the open PRs like you can see in the commits at https://github.com/materializecss/materialize/commits/v1-dev and in the compare view at v1-dev...materializecss:v1-dev

Like already mentioned: goal is to get the open PRs merged / closed as far as possible. And also the open issues. This is the short-term goal to release a maintained version with fixes for known issues.

@Pierstoval
Copy link
Contributor

As I'm mentioned as a contributor, please know that I'm mostly here for code reviews, as I don't (yet?) have the time to work on it quickly. I might have some time in the upcoming year, but I have a lot of other projects to work on, so I'm in the new org for discussion, architecture and review, and I'd be really glad to help any willing contributor to go further :)

@DanielRuf
Copy link
Contributor

No worries. Even reviews are contributions and every contribution is very welcome.

@doughballs
Copy link

As for me, I can probably spend a bit of time most days, but I haven't contributed before, so not sure how useful I can be, beyond suggesting improvements and solutions to current issues. Happy to learn the ropes but would need some guidance.

@tomscholz
Copy link
Contributor

@tomscholz what about you? Would you like to help again?

Hi :)

I know it's a little bit late to the party, but not responding at all seemed rude.
I'm no longer doing that much frontend work and haven't used materialize in over 2 years, so my answer is unfortunately no :(

I wish you all the very best and hope the development on the project comes back to life. The move to fork the project was definitely the right choice.

-Tom

@DanielRuf
Copy link
Contributor

@tomscholz no problem. And thanks for your feedback.

@assistcontrol
Copy link

MaterializeCSS is a great project, and it's made the frontend development world a better place. But it's been YEARS since @Dogfalo et al. intended to continue development, and they've been actively soliciting donations this whole time with a duplicitous assertion that they'll use it for development. "Any amount would help support and continue development on this project"

It calls Alvin Wang and Alan Chang's integrity into question. Stop begging for money, or at least be honest about what you intend to do with it. I hate to sound cruel, but you two have done a disservice to your supporters by not being forthcoming.

@MaximBalaganskiy
Copy link
Contributor

Cut the losses, switch to MDC from Google.

@DanielRuf
Copy link
Contributor

@assistcontrol @MaximBalaganskiy see https://github.com/materializecss/materialize which is a fork which will bring a new release in the near future.

@LuckyRon88
Copy link

It's true that we haven't released in a while, but we are not abandoning the project. We will figure out a dev/release schedule that works well for us to continue delivering updates

Could you also make a note on your paid themes that you're no longer providing support/answering emails for the paid themes? Seems rather poor taste to claim that there is support when there isn't.

@subhasishdas159
Copy link

Abandoned project. Sadly no support.

@Pierstoval
Copy link
Contributor

@subhasishdas159 This repo indeed seems abandonned, that's why the community has made a fork with a new org in order to maintain it: https://github.com/materializecss/materialize

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