Feb 13 14:04:52 Welcome to this TC meeting by IRC Feb 13 14:05:25 let's start with the infrastructure issues Feb 13 14:05:51 ** Git: Mirroring status and Git@OW2 discussion Feb 13 14:05:51 ** XWiki migration Feb 13 14:05:51 ** Cloudbees support Feb 13 14:05:51 ** New Bamboo Status Feb 13 14:05:51 ** OW2.org wiki updates (dashboard & services updates) Feb 13 14:05:51 ** New download service Feb 13 14:06:02 OK Feb 13 14:06:04 Christophe, status of Git mirroring? Feb 13 14:06:07 I start for git Feb 13 14:06:18 git mirroring is currently running since christmas Feb 13 14:06:40 I developed some nodejs based runtime which handle the mirroring stuff Feb 13 14:06:57 for now we mirror 3 projects Feb 13 14:07:03 - https://github.com/ow2-compatibleone Feb 13 14:07:03 - https://github.com/ow2-sirocco Feb 13 14:07:03 - https://github.com/ow2-xlcloud Feb 13 14:07:23 tests are ok, we can extend to other projects Feb 13 14:08:14 I will update instructions on the wiki and contact mature projects leaders to suggest to use mirroring Feb 13 14:08:37 any question on this point? Feb 13 14:08:38 fine as we're on github we're interesting too Feb 13 14:08:59 the mirroring works OW2 Git -> Github only, right Christophe? Feb 13 14:09:05 yes Feb 13 14:09:36 @florentgarin yes you are on github you can not use the mirror Feb 13 14:09:51 the goal is to 'promote' OW2 projects on github Feb 13 14:10:31 note that developers still have to push their code to OW2 Feb 13 14:10:47 ok Feb 13 14:10:54 is the reverse planned ? Feb 13 14:11:01 no Feb 13 14:11:25 this is not the goal Feb 13 14:11:48 other OW2 projects are also on github as their primary scm (xwiki e.g.) Feb 13 14:12:10 @florentgarin if you want to completely move to git@OW2 you can do it by hand ;) Feb 13 14:12:19 I told about an OW2 umbrella on github Feb 13 14:12:22 We told Feb 13 14:12:46 unfortunately, github does not support being under several umbrellas Feb 13 14:12:59 so we have opened ow2-xxx for each xxx OW2 project Feb 13 14:13:07 yes Feb 13 14:13:10 for those we mirror Feb 13 14:13:18 this is easier to manage Feb 13 14:13:31 but yes, it would be nice if github could "tag" OW2 projects Feb 13 14:13:35 and we avoid having tens of repositories under the same organisation Feb 13 14:14:02 @alefebvr it is not available for now, I am still waiting for this tag feature Feb 13 14:14:27 OK Feb 13 14:14:29 for now the only way to do is to have an ow2-XXX org Feb 13 14:14:45 about Git@OW2, the next point is the Gitorious replacement Feb 13 14:14:49 @florentgarin you can prefix your organisation on github at least Feb 13 14:15:06 yes Feb 13 14:15:48 about Gitorious, we need to find a replacement (it has become open core) Feb 13 14:16:05 :-( Feb 13 14:16:08 we had looked at Gitlab and Gitblit, but none has the "group" feature Feb 13 14:16:22 where we can manage rights on a project by project basis Feb 13 14:16:26 y don't we fork the earlier gitorious Feb 13 14:16:30 hi Jeremy! Feb 13 14:16:33 Hi all Feb 13 14:16:48 no no @esdaniel we haven't got the resources to do so Feb 13 14:16:50 however Feb 13 14:17:04 @esdaniel did you remember our last fork? ie gforge :$ Feb 13 14:17:29 there seems to be a alternative which would be stash http://www.atlassian.com/software/stash/overview Feb 13 14:17:41 atlasssian FTW again Feb 13 14:18:24 Stash provides all the features github provides Feb 13 14:18:27 @cescoffier WDYT? Feb 13 14:18:45 yes it is Atlassian again, so what ;) Feb 13 14:18:45 I've tried stash for my own purpose, I was not really convinced Feb 13 14:18:50 politically, we already use atlassian stuff so we can't throw the baby out with the bathwater on this one Feb 13 14:18:50 argh Feb 13 14:19:02 I generally like Atlassian product, but found that one a bit behind Feb 13 14:19:06 the main point is to find something that fits our needs Feb 13 14:19:08 especially behind github Feb 13 14:19:27 also, gitorious has been causing problem to our OW2 infrastructure lately Feb 13 14:19:27 we will never find something better than github guys Feb 13 14:19:32 ;) Feb 13 14:19:36 cescoffier -> when u say behind github, do you mean solely in terms of repo functionality Feb 13 14:19:54 in term of velocity, integration, and features Feb 13 14:20:04 when did you tested it? Feb 13 14:20:23 one month ago (just after christmas) Feb 13 14:20:36 argh s*** :) Feb 13 14:20:44 I abandoned it, and installed my own gitlab. Feb 13 14:20:46 thats recent enough then.... our main challenge is ldap integration isn't it, Jeremy? Feb 13 14:20:57 @esdaniel no Feb 13 14:21:02 yes, but gitlab does not provide rights management at the project level, right? Feb 13 14:21:04 as it's atlassian, it's not ldap but crowd Feb 13 14:21:09 the main challenge is having somthing which rocks Feb 13 14:21:23 no it does not, but was outside of my feature set I needed Feb 13 14:21:48 ok, ok, I understand Feb 13 14:21:55 maybe we can give it a try Feb 13 14:22:01 stash you mean? Feb 13 14:22:05 it can(t be worst as gitorious Feb 13 14:22:17 chamerling / alefebvr / everyone - so we need to go back and review all choices again and then propose best, rather than debate it all now? Feb 13 14:22:46 @esdaniel we have already gone through reviewing the choices. There are none. Feb 13 14:22:55 at the moment Feb 13 14:23:05 AFAIK Feb 13 14:23:08 yes Feb 13 14:23:17 sorry all, i've taken my eye off this ball recently :-( Feb 13 14:23:27 can we give stash a try Feb 13 14:23:33 just to have an idea Feb 13 14:23:45 OK, should we then decide that we get to Atlassian, obtain a licence for stash and give it a try? Feb 13 14:23:54 should be easy to install Feb 13 14:24:18 easy to say before we've done it :-) Feb 13 14:24:32 Hi guys, sorry to be late Feb 13 14:24:41 @JeremyC can you install it somewhere? Feb 13 14:24:43 hi Feb 13 14:24:44 ! Feb 13 14:25:32 @JeremyC ? Feb 13 14:26:19 let's move to next item, Action for @JeremyC to install stash on our server soon Feb 13 14:26:44 next was the xwiki project migration Feb 13 14:27:10 http://jira.ow2.org/browse/TCACTIONS-10 Feb 13 14:27:14 Xwiki scripts are ok http://jira.ow2.org/browse/TCACTIONS-10 Feb 13 14:27:34 wunderbar! Feb 13 14:27:43 http://jira.ow2.org/browse/TCACTIONS-9 "http://jira.ow2.org/secure/ViewProfile.jspa?name=lefebval to announce project migration on the TC ML." Feb 13 14:27:52 let's do it then! Feb 13 14:28:02 my action I suppose Feb 13 14:28:06 What's the timeframe ? Feb 13 14:28:29 yes I can, we just have to ask atlassaian for licence (i.e. cedric have do to that, because he have to revalidate his atlassaian account) Feb 13 14:28:45 timeframe was 15 January 2013 ;-) Feb 13 14:28:58 lol, we missed the line ;) Feb 13 14:29:02 thanks @JeremyC Feb 13 14:29:22 so @sauthieg I'll send a message to the projects with the links which are in TCACTIONS-10 Feb 13 14:29:41 due date? Feb 13 14:29:42 @JeremyC, how many old XWikis do we have to migrate now ? Feb 13 14:29:58 due date this Friday for the e-mail ? Feb 13 14:30:01 When do we cut the ols wikis off ? Feb 13 14:30:25 I guess cutting the old wikis off should be done upon decision of the project after migration, right? Feb 13 14:30:32 yes Feb 13 14:30:40 yes, please don't set a deadline Feb 13 14:30:50 if there are no deadlines, there will be no chnages Feb 13 14:30:55 @sauthieg look at the Apache CMS migration. it's terrible. Feb 13 14:31:02 :S Feb 13 14:31:03 whats the ow2 cost per se? is sooner better for ow2 resource cost Feb 13 14:31:11 as usual, we do that at the last minute ... Feb 13 14:31:12 @sauthieg then let's say 1 year Feb 13 14:31:56 @esdaniel I do not think the issue is the OW2 cost here, but rather the comfort for OW2 projects to ues a less prehistorical instance of xwiki Feb 13 14:32:00 I don't really care, I did migrate the jonas wiki some months ago :) Feb 13 14:32:26 done on this one (project wiki migration)? Feb 13 14:32:30 yes Feb 13 14:32:36 next: Cloudbees support Feb 13 14:32:42 so, what's the decision? Feb 13 14:32:50 deadline: 1 year ? Feb 13 14:32:59 yes end of this year Feb 13 14:33:05 sounds fair Feb 13 14:33:08 if so, I would like to have monthly reminders for projects Feb 13 14:33:20 decision: I send e-mail, project migrate, and we set them a deadline initially April (if we want it to be for the end of the year, the deadline has to be April initially ;-)) Feb 13 14:33:26 maybe more frequent the last 6 months Feb 13 14:34:24 re. Cloudbees offering: OW2 Management Office is still to ask for a quote from CloudBees Feb 13 14:34:24 +1 to stress projects :)) Feb 13 14:34:47 I sent Cedric all the details about that point Feb 13 14:34:48 however, we need some data to ask for a quote (stats from our current Bamboo) Feb 13 14:34:56 still? what's reason for delay, does MO need TC support? Feb 13 14:35:16 @alefebvr quota Feb 13 14:36:07 I suggest that Cedric asks what is possible, and what is the price Feb 13 14:36:08 I mean, to ask Cloudbees for a quote (devis), we need to tell them for how much volume, don't we? Feb 13 14:36:21 OK, let us start without it and see what they say Feb 13 14:36:29 yes easier Feb 13 14:36:41 I have already reminded Cedric (who is on holiday this week). I'll put some pressure on him Feb 13 14:36:53 on our side we have to develop some services to integrate with cloudbees Feb 13 14:36:58 especially oauth Feb 13 14:37:08 I started to develop it Feb 13 14:37:10 OK Feb 13 14:37:23 and what I need is LDAP information from @JeremyC Feb 13 14:37:42 ie how to get users and authenticate Feb 13 14:37:43 and @JeremyC was supposed to take a look at how to integrate crowd and Oauth Feb 13 14:37:54 chamerling: can't you get an image of our LDAP to use as a mock? Feb 13 14:38:04 did you manage to take a look @JeremyC? Feb 13 14:38:13 @esdaniel yes I will do it like that Feb 13 14:38:31 but I need this image, or any other information Feb 13 14:38:40 still waiting for @JeremyC inputs Feb 13 14:39:12 ok Feb 13 14:39:15 all the other modules are ready, just need this Feb 13 14:39:24 @JeremyC? Feb 13 14:39:43 Action for jeremy Feb 13 14:39:49 one more :) Feb 13 14:40:25 ok Feb 13 14:40:47 next Feb 13 14:41:02 - New Bamboo Status Feb 13 14:41:03 next on the agenda was a "new bamboo status" Feb 13 14:41:22 so, how is it doing? @sauthieg? Feb 13 14:41:29 we did some tests before christmas Feb 13 14:41:47 ie tests with crowd/LDAP Feb 13 14:41:49 Yes I have to export an image of your ldap Feb 13 14:41:57 I started to migrate some of my own plans (Shelbie / Utilities) Feb 13 14:42:01 Shelbie's done Feb 13 14:42:10 Utilities, a lot of modules remains ... Feb 13 14:42:16 Migrating is not a problem Feb 13 14:42:21 have you started running on the new Bamboo. Feb 13 14:42:21 the problem is user management Feb 13 14:42:22 ? Feb 13 14:42:29 anyway, that's a per-project process ... Feb 13 14:42:52 wait wait wait Feb 13 14:43:04 are you @chamerling talking about user management for the new bamboo? Feb 13 14:43:11 yes Feb 13 14:43:11 ah yes, we had some issues with permissions on the new bamboo Feb 13 14:43:17 :-( Feb 13 14:43:30 let me explain what is the problem Feb 13 14:43:52 it looks like, even if bamboo is connected to crowd, which is connected to our LDAP Feb 13 14:44:10 users are not available in the bamboo instance Feb 13 14:44:16 and groups also Feb 13 14:44:40 even if a user is already registered in our LDAP, he cannot login to the new bamboo Feb 13 14:44:42 hmmm Feb 13 14:44:53 we did many tests Feb 13 14:44:53 so does he need to create a new account? Feb 13 14:45:13 and finally we did not understand how we were able to login Feb 13 14:45:18 we sometimes have the problem with JIRA already (Forge accounts sometimes do not work on JIRA) Feb 13 14:45:23 after X manipulations of crowd etc etc Feb 13 14:45:27 what is the secret? Feb 13 14:45:41 @alefebvr I don't know Feb 13 14:45:56 @JeremyC had to do more tests Feb 13 14:46:16 http://jira.ow2.org/browse/TCACTIONS-3?focusedCommentId=20501&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20501 Feb 13 14:46:18 would be great to have a minimal mirror of our infra for testing, kinda like staging Feb 13 14:46:34 just saying Feb 13 14:46:58 @esdaniel not sure we can have N instances of atlassian products for staging Feb 13 14:47:13 OK, so I understand: the new Bamboo is not usable at the moment because of the login/rights issue Feb 13 14:47:26 @alefebvr yes Feb 13 14:47:28 if it helped atlassian with bug fixing i'm sure they'd place nice, they're not dumb Feb 13 14:47:37 at least, not for those you haven't found a magic way of logging in ;-) Feb 13 14:48:06 so the issue os still pending Feb 13 14:48:07 @esdaniel are you suggesting we should ask Atlassian for help? Feb 13 14:48:08 is Feb 13 14:48:27 seems like a good idea Feb 13 14:48:49 for attlassian login troubles, maybe it's caused by our licence type (we have users limitations) Feb 13 14:48:58 do we really? Feb 13 14:49:13 yes, so we have to do some more tests, write results and ask atlassian for support Feb 13 14:49:29 on the other hand, if they provide open source friendly licences, it is in their interest that things work fine Feb 13 14:49:34 OK Feb 13 14:49:40 next was "OW2.org wiki updates (dashboard & services updates)" Feb 13 14:49:51 (not sure what you had in mind @chamerling ;-)) Feb 13 14:50:14 ok Feb 13 14:50:29 so the idea was just to check if all our pages are up to date Feb 13 14:50:47 especially, do we have all the information about services Feb 13 14:51:01 I do not remember which ones were missing Feb 13 14:51:30 since last time, info was added for Sonar and FOSSology on this page http://www.ow2.org/view/IT_Infrastructure/Overview Feb 13 14:51:30 and the idea is also to list somewhere which services are connected to LDAP, Feb 13 14:51:57 because new users are a bit lost Feb 13 14:52:16 this is a good idea Feb 13 14:52:37 since we still have several (too many) logins/identifiers, yes, this information would be valuable Feb 13 14:52:53 listing all services and their description on a single page will be better Feb 13 14:52:54 I'm writing it down as an action for @JeremyC and myself, to document this Feb 13 14:53:19 ok Feb 13 14:53:44 we could enrich a bit http://www.ow2.org/view/IT_Infrastructure/Overview to provide a bit more information (without trying to put all information which is on individual pages for each service) Feb 13 14:53:49 this should include authent info Feb 13 14:53:54 yes Feb 13 14:54:05 and say what is automatically created or not Feb 13 14:54:07 lol, this one seems out of date: http://ow2.org/view/Community/Technology_Council Feb 13 14:54:48 @esdaniel you are right, this page is obsolete... Feb 13 14:54:55 real page is http://ow2.org/view/Technology_Council/ Feb 13 14:55:44 next was the new download service Feb 13 14:56:15 as a reminder, the idea is to provide a friendlier alternative to the GForge "files" service Feb 13 14:56:23 for binary hosting Feb 13 14:56:40 @cescoffier, what do they use at Apache? Feb 13 14:56:56 well, we just changed Feb 13 14:57:00 and? Feb 13 14:57:05 now we're using SVN to host our releases Feb 13 14:57:14 and actually, it's simple and powerful Feb 13 14:57:21 so when we do have a new release Feb 13 14:57:31 we upload the new files on this SVN, and that's it Feb 13 14:57:38 wow Feb 13 14:57:55 but for OW2, I think using a maven repo is the way to go Feb 13 14:58:15 (before on apache we just add a special folder populated using SSH) Feb 13 14:58:21 what about projects which are not on maven? Feb 13 14:58:40 (folder with SSH, that's what we had in mind) Feb 13 14:58:50 SSH and webdav Feb 13 14:58:51 ;) Feb 13 14:58:58 you should still be able to deploy on a maven repo without having maven using nexus or whatever Feb 13 14:59:09 OK Feb 13 14:59:25 the main issue with the SSH directory: it was really error prone Feb 13 14:59:37 with svn we can quickly rollback Feb 13 15:00:06 sounds good Feb 13 15:00:33 SVN could be OK for some, but not those who cannot svn connect to OW2 Feb 13 15:00:44 +1 Feb 13 15:00:51 hum no, that's just the beginning Feb 13 15:00:53 (I'm thinking of people behind complicated firewall systems) Feb 13 15:00:56 still have this old SVN+SSH issue Feb 13 15:00:59 exact Feb 13 15:01:02 then we have a hook Feb 13 15:01:10 that retrieve all artifacts and serve them Feb 13 15:01:11 but, if we also offer Maven, that could be OK ? Feb 13 15:01:28 we should have only one way Feb 13 15:01:32 @cescoffier so this service is deprecated on apache http://www.apache.org/dyn/closer.cgi ? Feb 13 15:02:13 or is it backed by SVN? Feb 13 15:02:19 "we should have only one way" Feb 13 15:02:28 that would be nice Feb 13 15:02:40 so why not Nexus since we already have it? Feb 13 15:02:43 @chamerling yes it is Feb 13 15:03:04 @chamerling backed by svn Feb 13 15:03:08 http://repository.ow2.org/nexus/index.html Feb 13 15:03:29 nexus would give the statistics of people using maven to download the artifacts Feb 13 15:04:37 Does nexus allows to pusblish binaries without maven ie from the webapp? Feb 13 15:04:44 that's the main point Feb 13 15:04:45 yes it does Feb 13 15:05:14 http://repository.ow2.org/nexus/index.html#staging-upload Feb 13 15:05:40 I do not have enough rights on nexus Feb 13 15:05:53 seems we've got another update as well to do Feb 13 15:05:58 UPGRADE AVAILABLE: Nexus Professional 2.2 is now available. https://support.sonatype.com/entries/20673111-how-do-i-download-nexus-professional Feb 13 15:06:00 yes Feb 13 15:06:11 we are running v2.0.3 Feb 13 15:06:17 and 2.2 is available Feb 13 15:06:28 @alefebvr can you add new action also to update it? Feb 13 15:06:34 +1 Feb 13 15:06:36 yes Feb 13 15:07:04 I guess @sauthieg or @JeremyC should be able to sort out the rights? Feb 13 15:07:12 yes please Feb 13 15:08:07 OK Feb 13 15:09:14 next Feb 13 15:09:20 before we move to the next item, information: OW2 has decided to hire a sysadmin, following limited availability of @JeremyC Feb 13 15:09:34 if you know somebody, please tell us Feb 13 15:09:53 @alefebvr please send us the 'fiche de poste' Feb 13 15:09:54 :) Feb 13 15:10:09 draft profile is: Feb 13 15:10:23 OW2 is looking for its Systems Administrator / Forge Administrator Feb 13 15:10:23 The OW2 Consortium has open the position of a Systems Administrator / Forge Administrator (m/f) Feb 13 15:10:23 This is a high-visibility position for a Systems Administrator / Forge Administrator / Developer with experience or with high potential. . The successful applicant is supposed to have a degree in computer sciences, engineering subjects or related fields from a University or higher ranking. In special cases, applicants without such a degree, but having appropriate education and standing work experience will also be considered. Feb 13 15:10:23 The position includes software maintenance of servers and applications forming the technology infrastructure of the OW2 Consortium. The environment currently include Linux-based servers, a forge, a mailing list system, a wiki system, an LDAP server, a cloud environment as well as state of the art developers tools. Feb 13 15:10:23 The successful applicant will also be entrusted in improving the environment by integrating new tools and by developing small applications as requested by either the community or the management of this open source consortium. Feb 13 15:10:23 Spoken and written English absolutely necessary: daily email exchanges with the community are to be expected. Feb 13 15:10:23 Location of the position is France preferably but the function can be executed remotely. The successful applicant will report to the CTO of the Consortium. The compensation package will be provided either by the OW2 Consortium or by one of its Strategic Members. This is initially a part-time (50%) position. Feb 13 15:11:02 so, next was Projects Feb 13 15:11:11 can we start sending it? Feb 13 15:11:11 Nanoko vote is under way, closing tonight Feb 13 15:11:22 you can start talking about it around you, yes Feb 13 15:11:40 and forwarding it to people you know Feb 13 15:11:45 alefebvr: lets get a page up on ow2 re: sysadmin and we can send the link out to the wider net Feb 13 15:12:31 @esdaniel yes, it's up to Cedric to validate it first Feb 13 15:12:50 about nanoko, I already had a talk at human talks yesterday evening (about h-ubu, one of the main component) Feb 13 15:12:52 in the mean time, if you know someone, please go ahead Feb 13 15:13:24 everyone seems fairly excited (positively) about nanoko Feb 13 15:13:38 (at least, I am, Romain is ;-)) Feb 13 15:13:41 yes, I also had nice talk with Romain yesterday Feb 13 15:13:48 and I Feb 13 15:13:49 alefebvr: was thinking it's a nice opportunity to give to south american, india, chinese members Feb 13 15:14:04 I am really pleased to have a JS project at OW2 Feb 13 15:14:15 this will be really good for us Feb 13 15:14:52 i was hoping to hear from jean-paul smets with his opinion, what with him being a javascript guru too, no word yet Feb 13 15:15:08 @esdaniel: this has been advertised at the Board in January, so all members are aware, and it is in the Board minutes on the website Feb 13 15:15:55 chamerling: do you see lots of obvious synergies with nanoko for now/future? Feb 13 15:16:09 Actually, while we were on infrastructure, let us bring the point raised by @asaval about finer rights management for SVN Feb 13 15:16:31 oops sorry @esdaniel Feb 13 15:16:38 np, happens all the time ;-) Feb 13 15:16:46 maybe @cescoffier can tell us about the nanoko synergies? Feb 13 15:17:23 @esdaniel yes, I will personally look at it and suggest nanoko for some projects we have Feb 13 15:17:25 there is synergies with all projects doing web stuff so a lot Feb 13 15:17:47 OK Feb 13 15:17:51 there is several aspect Feb 13 15:18:06 first about the build / quality : nanoko provide a maven plugin for web project Feb 13 15:18:19 not only javascript, but less, coffesscript ... Feb 13 15:18:37 it support a set of quality tools (CSSLint, JSLint, JSHhint...) Feb 13 15:18:50 we will have the Play2 maven plugin too soon Feb 13 15:19:14 which propose a way to build play framework 2 applications with Maven Feb 13 15:19:22 @cescoffier sounds nice Feb 13 15:19:39 more on the runtime level, the nanoko proposals is really close to OSGi / COTS paradigm Feb 13 15:19:58 so synergies are obvious with all projects doing components Feb 13 15:20:00 this build aspect is very appealing having studied the project a wee bit recently Feb 13 15:20:18 (it's actually, pretty close to OSGi/iPOJO for a good reason ;-)) Feb 13 15:20:20 a differentiator that other frameworks might adopt in the future as a best practice so good for ow2 Feb 13 15:21:04 so it gets my (unofficial) vote ;-) Feb 13 15:21:12 there is no other framework close to what nanoko propose in term of runtime (will come to the build time after) Feb 13 15:21:29 the closer would be twitter flight Feb 13 15:21:54 most of the client-side frameworks are made to handle the dom (angular, knckout, flight...) Feb 13 15:22:07 some give architectural patterns : backbone, angular Feb 13 15:22:16 nanoko let you use whatever you want Feb 13 15:22:54 it's really a component model, you component can use any library / framework Feb 13 15:23:08 nanoko does not ease dom manipulation, it is not the purpose Feb 13 15:23:23 @cescoffier you should give many details about that on your website, not sure it is clear enough Feb 13 15:23:36 and samples!!! Feb 13 15:23:37 :) Feb 13 15:23:38 actually, it's even a feature because you can use nanoko on server-side using rhino or node.js Feb 13 15:24:18 @chamerling: http://nanoko-project.github.com/h-ubu/snapshot/ Feb 13 15:24:33 about the buiilt time Feb 13 15:24:47 there is a couple of tools existing. The most famous is grunt Feb 13 15:24:51 (this conversation would be an awsome starting point for the TC blog ;-)) Feb 13 15:25:03 (http://gruntjs.com/) Feb 13 15:25:42 the main issue I have with grunt is the CI integration (bamboo / jenkins...) Feb 13 15:25:48 nanoko app are built with maven Feb 13 15:26:04 using a simple maven build doing the maven stuff, as maven user / lover expect Feb 13 15:26:51 so it's like grunt + bower together Feb 13 15:27:06 yes, we have strated writing some stuff Feb 13 15:27:38 cool Feb 13 15:27:55 will be nice to have it, we will speak about that later Feb 13 15:28:01 can we move to the next item Feb 13 15:28:02 ? Feb 13 15:28:06 on the CI front has anyone seen/know of similar to Thoughtworks Go environment on the FOSS side Feb 13 15:28:20 - SVN rights Feb 13 15:28:37 @asaval can you explain us what do you need? Feb 13 15:29:11 There are more than 15 members on the WebLab project Feb 13 15:29:41 The main reason behind this number is the way the WebLab is split Feb 13 15:29:57 It has webservices, portlets, a core and so on Feb 13 15:30:14 Each member has their own speciality Feb 13 15:30:31 asaval: member synonomous with 'sub-project' ? Feb 13 15:30:42 In fact, we have several sub projects insinde our project yes Feb 13 15:31:42 We would like to have a way to separate commit rights betweens members Feb 13 15:32:06 for now our forge does not allow that Feb 13 15:32:08 could we not flatten the hierarchy thhen? Feb 13 15:32:32 we have one project on the forge which is linked to the SVN Feb 13 15:32:38 as each project will share namespaces Feb 13 15:33:10 and all of this is created with scripts Feb 13 15:33:14 ... Feb 13 15:33:48 the question is: Do we have to investigate on how to do it on our forge/SVN Feb 13 15:34:06 or will it be better that you switch to git? :p Feb 13 15:34:10 better/easier Feb 13 15:34:23 Well, this finer rights managment is not mandatory for us, but it could really help to manage the team behavior Feb 13 15:34:24 for us at least Feb 13 15:34:53 I will say that this is a team management problem Feb 13 15:35:03 (thinking) Feb 13 15:35:04