Skip to content

Project seems unmaintained #430

Open

Description

@joscmw95

angular2-materialize has been extremely useful for those who were using Angular/AngularJS that migrated to Angular, with Materialize CSS.

However, the project seems to be unmaintained.
There are at the moment 117 issues and PRs for bug fixes that are ignored.

I have an Angular project that uses Materialize and there is a need for me to upgrade to Angular 6.
So I updated the dependencies and created an Angular library.

For those who are interested, feel free to check out ng-materialize.

Activity

  1. rubyboy commented on May 27, 2018

    @rubyboy
    Contributor

    @joscmw95 is ng-materialize a copy of this repo? The more appropriate way to improve this repo is by forking or branching.

    angular2-materialize is an open source. Anyone can and is encouraged to contribute to it.
    You are more than welcome to contribute to angular2-materialize with PRs. If you are interested in becoming a maintainer let us know - we are looking for people to help maintain and improve it.

  2. joscmw95 commented on May 27, 2018

    @joscmw95
    CollaboratorAuthor

    @rubyboy Hi, yes it is a copy of this repo with updated dependencies and some sidetrack logic to disable the directives gracefully in server-side rendering. I'm super glad you replied here, I actually wanted to contact you but not sure how.

    As you can see there are more than a hundred issues and some PRs right now so I assumed that you're no longer maintaining the repo. I would happily attempt to maintain the repo but I'm not 100% sure of the process yet.

    Since you're looking for people to maintain this repo, I'll remove ng-materialize.

  3. rubyboy commented on May 27, 2018

    @rubyboy
    Contributor

    @joscmw95 cool, thanks so much for offering. @Dakayl also offered to contribute if someone else is on board (See here: #411).

    I've given both of you write permissions on the repo. Please let me know if you haven't received the invite email.

    The changes process is quite simple. @luketn and I use the usual semantic release (https://github.com/semantic-release/semantic-release) and commitizen (https://github.com/commitizen/cz-cli) plugins exactly as described in this excellent Egghead course: https://egghead.io/courses/how-to-write-an-open-source-javascript-library :
    image

    Again, thanks for the offer to help and please do not hesitate to ask @luketn or me anything. Even though we have little time to maintain the repo we would love to still be involved and potentially help when possible...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions