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

announce "this project is not maintained anymore" #639

Open
timaschew opened this Issue Jun 21, 2015 · 8 comments

Comments

Projects
None yet
7 participants
@timaschew
Member

timaschew commented Jun 21, 2015

@componentjs/owners
I think it's obvious that component is not maintained anymore.
We should put a note in the readme of this repo, not just because it's not maintained, but also component has several issues:

  • endpoint only for GitHub and BitBucket
    • rate limit, even if you use an auth token example
  • maintain an extra file: component.json
    • need to fork a module when it doesn’t exist
  • plugins can only be used via the API
  • annoying to update remote dependencies in all locals example
  • it’s not maintained anymore, see contributors

@jonathanong wrote a post after he rewrote component:
http://www.jongleberry.com/the-future-of-component.html
After nearly a year he wrote this:
http://www.jongleberry.com/the-story-of-normalize.html

In particular, the more I learn about Webpack, the more amazed I am and its features, especially hot reloading.

We're using component at our company and realize in the last week a drop-in replacement for webpack, it's working fine.
The biggest work was to fix all the component repositories where a package.json was configured wrong or didn't exist.

@clintwood

This comment has been minimized.

Show comment
Hide comment
@clintwood

clintwood Jun 21, 2015

Contributor

@timaschew, first off thank you for all your amazing work on componentjs!

In the early days component was amazing but for myself the writing on the wall with respect to it's future was when key people began talk of webcomponents and es6 modules. To that end I have looked to other 'component' packaging, bundling and development mechanisms including jspm, webpack, Polymer as well as switched to es6 for iojs/node side stuff using babel, esperanto and rollup. To be honest it's been a time consuming switch but necessary to stay in the game! Thanks!

Contributor

clintwood commented Jun 21, 2015

@timaschew, first off thank you for all your amazing work on componentjs!

In the early days component was amazing but for myself the writing on the wall with respect to it's future was when key people began talk of webcomponents and es6 modules. To that end I have looked to other 'component' packaging, bundling and development mechanisms including jspm, webpack, Polymer as well as switched to es6 for iojs/node side stuff using babel, esperanto and rollup. To be honest it's been a time consuming switch but necessary to stay in the game! Thanks!

@pirxpilot

This comment has been minimized.

Show comment
Hide comment
@pirxpilot

pirxpilot Jun 22, 2015

Thanks @timaschew and thanks to everyone who made component possible. Probably stating the obvious here: many components (as opposed to the component builder and tools) are probably still used in the wild. I'll keep an eye on a few I am still using. Let's wind it down gently.

Thanks @timaschew and thanks to everyone who made component possible. Probably stating the obvious here: many components (as opposed to the component builder and tools) are probably still used in the wild. I'll keep an eye on a few I am still using. Let's wind it down gently.

@AaronNGray

This comment has been minimized.

Show comment
Hide comment
@AaronNGray

AaronNGray Jun 22, 2015

Is this just component or the whole of componentjs ?

On 22 June 2015 at 01:48, Damian Krzeminski notifications@github.com
wrote:

Thanks @timaschew https://github.com/timaschew and thanks to everyone
who made component possible. Probably stating the obvious here: many
components (as opposed to the component builder and tools) are probably
still used in the wild. I'll keep an eye on a few I am still using. Let's
wind it down gently.


Reply to this email directly or view it on GitHub
#639 (comment)
.

Is this just component or the whole of componentjs ?

On 22 June 2015 at 01:48, Damian Krzeminski notifications@github.com
wrote:

Thanks @timaschew https://github.com/timaschew and thanks to everyone
who made component possible. Probably stating the obvious here: many
components (as opposed to the component builder and tools) are probably
still used in the wild. I'll keep an eye on a few I am still using. Let's
wind it down gently.


Reply to this email directly or view it on GitHub
#639 (comment)
.

@vendethiel

This comment has been minimized.

Show comment
Hide comment
@vendethiel

vendethiel Jun 22, 2015

well, the individual components should still work fine, so long they have a bower.json / package.json / something else to be used

well, the individual components should still work fine, so long they have a bower.json / package.json / something else to be used

@lvivier lvivier referenced this issue Jun 22, 2015

Merged

Remove component dependency #52

3 of 3 tasks complete
@AaronNGray

This comment has been minimized.

Show comment
Hide comment
@AaronNGray

AaronNGray Jun 22, 2015

So ComponentJS itself is being scrapped ?

On 22 June 2015 at 21:05, ven notifications@github.com wrote:

well, the individual components should still work fine, so long they have
a bower.json / package.json / something else to be used


Reply to this email directly or view it on GitHub
#639 (comment)
.

So ComponentJS itself is being scrapped ?

On 22 June 2015 at 21:05, ven notifications@github.com wrote:

well, the individual components should still work fine, so long they have
a bower.json / package.json / something else to be used


Reply to this email directly or view it on GitHub
#639 (comment)
.

@lvivier lvivier referenced this issue Jun 23, 2015

Open

Remove component #1

0 of 2 tasks complete
@timaschew

This comment has been minimized.

Show comment
Hide comment
@timaschew

timaschew Jun 23, 2015

Member

Of course component and its modules (component-builder, component-resolver, component-remotes ,..) - actually everything in the componentjs organisation - will still available on npm and on GitHub, but the development will stop for new features and bugfixes.

And of course all the components like commponent-dom and domify, everything in the component organisation will still work, as long the modules have a component.json file. They even work for other tools like browserify, webpack and jspm if they provide a package.json

Member

timaschew commented Jun 23, 2015

Of course component and its modules (component-builder, component-resolver, component-remotes ,..) - actually everything in the componentjs organisation - will still available on npm and on GitHub, but the development will stop for new features and bugfixes.

And of course all the components like commponent-dom and domify, everything in the component organisation will still work, as long the modules have a component.json file. They even work for other tools like browserify, webpack and jspm if they provide a package.json

@darsain

This comment has been minimized.

Show comment
Hide comment
@darsain

darsain Jun 29, 2015

Seeing as component is being deprecated, but component spec is still used by duo, webpack, and maybe others, wouldn't it be a good idea to use component.io for description of a spec (similar to json.org), along with component discovery? That way other tools like the ones mentioned would be able to just point to this to specify how to create & find components.

And component discovery could use some upgrade. Instead of relying on one huge wiki page that none really edits, search and list all github repos with component.json in the root. Is this doable?

darsain commented Jun 29, 2015

Seeing as component is being deprecated, but component spec is still used by duo, webpack, and maybe others, wouldn't it be a good idea to use component.io for description of a spec (similar to json.org), along with component discovery? That way other tools like the ones mentioned would be able to just point to this to specify how to create & find components.

And component discovery could use some upgrade. Instead of relying on one huge wiki page that none really edits, search and list all github repos with component.json in the root. Is this doable?

@lvivier lvivier referenced this issue Jul 10, 2015

Closed

Needs a package.json #5

6 of 6 tasks complete
@netpoetica

This comment has been minimized.

Show comment
Hide comment
@netpoetica

netpoetica Jul 11, 2015

Contributor

@timaschew Thanks for all your hard work on component amigo. I agree with you that it is the right time for this announcement. I have not had my hands in every nearly as many modules of componentjs as you have and I certainly don't think I would be capable of maintaining this project - especially to the quality it has been maintained by you - without you.

I am still open to being pinged for Bitbucket remote-related issues if they are business-/originzation-crucial, but I do not think this portion of component has been heavily utilized.

Let me know if there is anything you need from me. It's been fun working on the small slices of component that I've had a chance to be involved in - hopefully one day we'll run into each other at a conference!

Cheers,
Keith

Contributor

netpoetica commented Jul 11, 2015

@timaschew Thanks for all your hard work on component amigo. I agree with you that it is the right time for this announcement. I have not had my hands in every nearly as many modules of componentjs as you have and I certainly don't think I would be capable of maintaining this project - especially to the quality it has been maintained by you - without you.

I am still open to being pinged for Bitbucket remote-related issues if they are business-/originzation-crucial, but I do not think this portion of component has been heavily utilized.

Let me know if there is anything you need from me. It's been fun working on the small slices of component that I've had a chance to be involved in - hopefully one day we'll run into each other at a conference!

Cheers,
Keith

sindresorhus added a commit to sindresorhus/awesome-nodejs that referenced this issue Jul 16, 2015

remove `Component`
as it's not maintained anymore: componentjs/component#639

ghinda added a commit to ghinda/css-toggle-switch that referenced this issue Nov 18, 2015

ghinda added a commit to ghinda/css-toggle-switch that referenced this issue Nov 19, 2015

Merge branch 'material'
* material: (24 commits)
  More bower.json tweaks.
  Tweak bower.json.
  Tweak package.json.
  Fix failing tests caused by the grunt config.
  Fix all failing tests because of switch-light markup change. Add new tests for the Material theme and switch-toggle with 6 options.
  Changelog tweaks.
  Update the bootstrap docs. Tweak the line-height so the light switch works better with bootstrap classes.
  Update the Foundation docs.
  Tweaks to the README.
  Add the new material theme to the docs homepage, and some tweaks.
  component(1) is dead, so stop supporting it. componentjs/component#639
  Update changelog with the material theme details. Add more example to the docs site homepage header.
  Complete the new material design theme, with ripples and everything, all still css. Material design toggle switches will look like custom radios, still from material design.
  Make the new material design theme work with the new switch-light markup.
  Fix the ios theme to work with the new markup. Tweaks to the iOS theme to make it look a bit better.
  Nesting CSS was a bad idea. Fix the Holo theme to work with the new switch-light markup.
  Remove the nasty `switch-X` classes used with `switch-toggle` for number of items. More fixes to the `candy` theme to support the new markup.
  New markup for the `switch-light` component and begin adapting the `candy` theme for the new markup.
  Begin work on the new `material` theme.
  Use partials for the top menus and the footer credits.
  ...

CtrlC-Root added a commit to jgallen23/routie that referenced this issue Jan 29, 2016

Component is no longer maintained and deprecated (see componentjs/com…
…ponent#639). This removes the component.json file and moves the component depency on assert to a node dependency.

mbostock added a commit to d3/d3 that referenced this issue Feb 13, 2016

Remove component.json.
Component is not maintained anymore, per componentjs/component#639.

lehni added a commit to paperjs/paper.js that referenced this issue Jul 9, 2016

@timaschew timaschew closed this Sep 13, 2016

@timaschew timaschew reopened this Sep 13, 2016

simison added a commit to simison/human-interval that referenced this issue Jul 31, 2017

Delete component.json
Component hasn't been maintained since 2015: componentjs/component#639
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment