Roadmap for 1.0.0, 2.0.0 and beyond

[0x6a68]

hello together! since i am a big fan of kss and node, i have asked @hughsk to help him out as a contributor. as you have noticed i closed several issues and moved most of them into this list:

• Example Update, SASS projects
• HTML Entities Update Handlebars.js to resolve HTML entities problem #30
• Multiline Description for Modifiers Multi-line Modifier Descriptions #25
• Compass Sprite Compass Sprite imports break KSS parsing #24
• Support for functions and mixins Support for preprocessor functions and mixins #22

if you have any features, which are not listed above, just leave a note here and we can discuss them. thanks and bye!

[r4j4h]

Thank you for helping to continue to maintain this! I will try to help out where I can, as this is one of the best CSS documenters I have been able to find.

[dotherightthing]

Hi, one for the wishlist: could you please add support for non-numeric styleguide ordering:

https://github.com/kneath/kss/blob/master/SPEC.md#the-styleguide-section

from

kneath/kss#75

Thanks,
Dan

[gefangenimnetz]

I think @dotherightthing 's request is the same as #37 , right?

[badsyntax]

hey, is this project still being maintained? will you accept pull requests?

[snorripall]

crickets

[JohnAlbin]

I've given a few conference presentations talking up the benefits of kss-node. I'd really like to see this project better maintained.

@hughsk May I suggest transferring ownership of this repository to a GitHub organization? That way several of us can maintain the project and we won't be solely reliant on a single individual. Maintaining open source code is hard! I went ahead and created a kss-node organization at https://github.com/kss-node and added you and @johannestroeger as owners. I know I'm being presumptuous, but I want to see movement in this issue queue. Please don't feel any obligation; it's just a suggestion I'd like to see and you are free to disagree.

Getting back to the original purpose of this thread: I think we should release a 1.0 with all of the current features + bug fixes; IMO, the code is stable, so we may as well designate that using semantic versioning and mark it as 1.0.0. Then we can add new features post 1.0.

Looking even further into the future to 2.x, I've been using a task builder (Gulp.js) in my front-end workflow and like the architecture of streaming different modular Gulp plugins together to form a complex task. I'd love to see the core of Kss-node shrunk to a very small set of features with the additional features added via plugin or Gulp.js task. This modularity would allow developers to create Gulp tasks that add in their own features without patching the core functionality.

[hughsk]

Sorry for the radio silence!

@JohnAlbin nice, that sounds perfect. I've transferred the repo to the organisation. Feel free to add additional contributors from this thread as you see fit!

kss-node could definitely do with a full rewrite, and I agree 100% that it would be better broken up into small pieces. 👍 for making 1.0.0 a stable release too. My only suggestion would be to keep module(s) build-tool-agnostic, and wrap it up in a separate gulp plugin for ease of use. That aside, you and the others are welcome to steer the project in whatever direction feel is best – it's been a long time since I've been invested in the project and I'm sure that with multiple maintainers things will move in the right direction. Thanks for taking the initiative and giving me another nudge to transfer :)

[JohnAlbin]

If you look at https://github.com/kss-node/kss-node/issues?milestone=1, you'll see they are all closed (except for this issue.)

There's 3 issues I think would be fine for a future 1.x release: https://github.com/kss-node/kss-node/issues?milestone=3

But, I think we can tag a 1.0.0 release. It requires Node.js 0.10.x. If you required Node.js 0.6 or 0.8, you can you the v0.4.0 release I tagged earlier today.

All other issues are marked for a 2.x release. The 2.x road map is simple: 1.0.0 + removal of stylesheet compilation + some minor features. I don't want to support 1.x for very long; I want the stylesheet compilation out ASAP.

Any major re-write can happen for the 3.x release at our leisure.

[JohnAlbin]

1.0.0 has been tagged: https://www.npmjs.org/package/kss

[JohnAlbin]

1.1.0 has been tagged: https://www.npmjs.org/package/kss

That completes the issues marked for the 1.x milestone. https://github.com/kss-node/kss-node/issues?q=milestone%3A1.x+is%3Aclosed

I'm creating a branch called 1.x to handle any additional bugfixes/features for the 1.x branch. The master branch is now open for 2.x work. https://github.com/kss-node/kss-node/milestones/2.x