[07:54:12] hey, sfrisk, arschmitz had a few questions [07:55:45] geekman-rohit: hey how can i help? [07:56:33] okay, so sfrisk gave me a review on the list of features in themeroller, she suggested that a integration with adobe kuler, as in jquery-mobile's themeroller would be great [07:56:56] but adobe kuler is nor adobe color-cc and they have stopped providing API keys [07:57:21] geekman-rohit: right we were just saying something similar [07:57:27] though we do still have the mobile key [07:57:34] which we can use? [07:57:39] that would be awesome :) [07:58:04] I read on their blog that the service would continue running, just no more keys [07:58:37] I also found this : http://www.colourlovers.com/api [07:58:50] as a possible alternative [07:59:12] geekman-rohit: we would prefer something non deprecated i think :-) [07:59:48] arschmitz : an alternative would be http://www.colourlovers.com/ [07:59:54] geekman-rohit: im talking with someone from adobe about this right now [08:00:18] your friend, who made topcoat? :D [08:00:26] geekman-rohit: yup [08:01:05] geekman-rohit: also if you do the whole thing as an api endpoint and just a front end ui [08:01:13] the extensions become almost zero effort [08:01:33] you can reuse the entire ui and just put it into an extension [08:01:45] and do a replace on the stylesheets [08:01:58] exactly, I guess we are talking about the firefox/chrome extension ? [08:02:06] geekman-rohit: yes [08:03:22] I have given it a few days towards the end of timeline, the work would then just come to is packaging in appropriate form for the extensions [08:03:34] geekman-rohit: does colourlovers have an api? [08:03:40] yes [08:03:52] json/xml and no keys, available kind of like feeds [08:04:06] http://www.colourlovers.com/api [08:05:16] geekman-rohit: thank you [08:06:22] geekman-rohit: they also mentioned they had started working on a module to produce HWB color schemes to match the css4 spec [08:06:48] they as in adobe guys ? [08:09:58] him personally [08:10:05] but its dead at this point [08:10:49] understood [08:15:03] [css-chassis] arschmitz opened issue #58: Setup view.css-chassis.com http://git.io/hO8V [08:44:04] sfrisk: ping! [08:44:08] yes? [08:45:20] michaelarestad: what's up [08:45:21] RE: the typography.html location: I don't think it should be where it is either. Any idea where it should live until we get a pattern library going? [08:45:52] michaelarestad: Hey [08:46:19] arschmitz: Mornin. [08:46:33] michaelarestad: Hey i had a question for you [08:46:40] Shoot. [08:46:59] we could have a folder called pattern_library or docs [08:47:02] michaelarestad: you had said that was a work in progress, so were you looking for like a full review or just feedback on the actual visual or what? [08:47:08] where we put the visual output of various components [08:47:14] sfrisk: michaelarestad: or demos could make sense too [08:47:20] demos works too [08:47:39] arschmitz: Any running feedback is fine, but if I could label it, it would definitely be "in progress" [08:48:08] michaelarestad: sure i just didnt want to leave a bunch of nit pick comments if you were not looking for that sort of feedback [08:48:13] Okay, good to know [08:48:36] Yep. [08:49:28] Pretty to used keeping in progress PRs so others can take a look/comment as they progress. [08:50:13] We could probably use a few labels to that nature. We use these: https://cloudup.com/cZUbfxa3kMv [08:50:50] I can create something like that for PRs [08:51:24] I like making labels :-) [08:51:32] Rad. :) [08:52:05] Super sick today so I'm going to be offline for the meeting. Just wanted to clarify a few bits. :) [08:55:00] Okay, sounds good. Hope you feel better. [08:55:55] I busted my ankle this weekend, so it's been a big ball of not fun [08:56:03] michaelarestad: hope you feel better [08:56:36] michaelarestad: one thing i didn't comment but make sure you run grunt the tests will catch things for you :-) [08:56:41] Thanks. Will take a look at your comments later. [08:56:52] arschmitz: Like a pro I ran the linter after commit. [08:57:02] michaelarestad: and if you rebase master [08:57:09] the travis CI will work too [08:57:15] Awesome. [08:57:21] Will do. [08:57:34] Later! [08:57:34] it was busted when you did the pr but i since fixed it [08:57:40] michaelarestad: take care later! [10:00:57] Meeting time over in #jquery-meeting [11:11:48] sfrisk: geekman-rohit: we will have to look at colourlovers licensing that might be complicated [11:12:11] sfrisk: geekman-rohit: each palet has its own license and terms of use [11:12:34] blarg [11:13:23] Umm, I'll keep hunting [11:13:36] yeah like most forbid commercial use [11:13:42] we can always, just in case, worst case scenario, use the old kuler api key [11:13:59] Yeah [11:14:06] which our use would not be but the vast majority of people using the theme roller probably are [11:14:24] arschmitz, umm do they plan to close the api service? [11:14:29] adobe guys? [11:14:38] not that i know of [11:15:06] I'll look for more options, we can later start an issue and have a full discussion [11:15:34] and see if anyone else can suggest better options [11:20:47] geekman-rohit: license type is also not a search param or a result field [11:20:59] so its not even like we could display or filter then license type [11:21:05] yes, I was looking at just that [11:21:15] I don't see why they have an api then :P [11:21:25] yeah [11:21:51] i dont think there is any way we should use this its like asking users to violate the terms of something [11:22:14] that's annoying [11:23:43] yeah :/ [11:25:21] there is also the color picker to decide.. we can make, but theres a lot of cool ones available for jquery ui [11:27:28] I mean it looks like http://paletton.com/widget/ might let you add the Paletton.com engine to your site [11:27:35] but I thought you have to use their widget [11:27:38] think* [11:27:43] What makes me unconfortable, is creating theme, whithout chassis finalized and without some examples [11:31:40] Understandable. It's why creating the theme is very much tied into creating components that would be needed for a theme [11:31:48] also I would look at creating more of a starter theme [11:31:54] rather than a full out designed theme [11:32:25] what about this thing with 'design', is there anybody that could help us with this? [11:32:37] I could help you with design, and well as a few other people on the team [11:33:02] but the idea is for the CMS theme to be more of a starter theme [11:33:12] so it has our markup conventions, styling, etc in there [11:33:30] but it's still pretty bare bones so someone can build on top of it to really focus on design [11:34:36] For example, I used Bones (http://themble.com/bones/) as a starter theme [11:35:02] how do you think, when we will have basic element for creating a theme? [11:35:49] By the time you have to start coding, the typgoraphy, tables, forms, validation, and grid system should already be in place [11:36:39] basically stuff covered in phase one of the roadmap [11:36:55] so with the grid, and typography, you should be able to lay out a lot of the basics for the site [11:37:37] Then, you'll start styling more custom UI components, such as what a nav might look like [11:37:58] I was asking, maybe it's gonna be sooner [11:38:09] but ok [11:38:30] IF things are at a point earlier on that you could start working on a CMS sooner rather than later, you're more than welcome to do so [11:39:02] in your proposal I would include what elements you would need to create for a theme [11:40:02] maybe another question is: Drupal's currently stable version is 7. But the Drupal 8 is already BETA, and everybody stop contributing to Drupal 7 and are working on Drupal 8 [11:40:12] so the question: which version of Drupal? [11:41:09] Either or [11:41:25] Drupal seven will still be used for awhile, since Drupal 8 is still in beta [11:41:51] But having a theme for Drupal 8 ready to go will help with early adoption [11:42:27] sfrisk: yes. I also was thinking that it is more of a starter theme which will be flexible enough to contain new elements. [11:42:40] I'll discuss it with the company in which I'm doing the internship, and relate details/ideas here. [11:43:15] In general, if you're doing the CMS theme - I would have your theme be a starter theme [11:43:21] And since alexeiTruhin is working on Drupal I would be glad to take a look and apply for Wordpress [11:44:56] can anyone help me with installing chassis [11:45:53] kristijan: did you follow instructions at https://github.com/jquery/css-chassis ? [11:47:05] kristijan: what version of nodejs do you use? [11:47:32] yes I followed the isntructions [11:47:38] first I had problems with grunt [11:48:01] kristijan: which OS? [11:48:06] I installed it but told me that some files are missing I don't know why [11:48:20] Linux Ubuntu [11:48:34] do a sudo npm install -g grunt [11:48:48] I did that [11:48:57] check your nodejs version [11:49:00] node -v [11:49:15] v0.12.0 [11:49:18] if it's > 0.10.* .. then you should downgrade [11:49:25] downgrade it to 0.10.* [11:49:29] ok thx [12:16:59] I installe node v0.10.1 again errors [12:17:07] installed** [12:17:47] sfrisk, can I email you what I currently have for my proposal for a quick look to see if I'm on the right track [12:17:57] sure, I can get to it later today [12:18:04] I'm at work right now [12:18:28] yeah, no rush, that would be great. Thanks! [23:49:41] Hi all, I am a GSOC aspirant looking for a good project to contribute in, is it too late to start contributing in css-chassis, given the premise that I know all the prerequisites for making valuable contributions.