From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SFtuO-0006p7-M3 for garchives@archives.gentoo.org; Thu, 05 Apr 2012 21:07:57 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 49A48E05ED for ; Thu, 5 Apr 2012 21:07:56 +0000 (UTC) Received: from mail-pb0-f53.google.com (mail-pb0-f53.google.com [209.85.160.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 0DA7DE0B48 for ; Thu, 5 Apr 2012 20:08:27 +0000 (UTC) Received: by pbcuo1 with SMTP id uo1so2281801pbc.40 for ; Thu, 05 Apr 2012 13:08:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=8fKJAYgh9NKuEuSzlve4MJq4yPsNg2TDmsH10ogYNKw=; b=L0snAWWA2ExCphmeVbYGjtdEEA0Wqs+yRS5FVSerpowzxClo1hVdCF4YAMgDmTz58w HBoTxh72ZbrJi5/rq6QuuLS0wLT65HC7mlp18E5t2kxCt87GXrN5nBGwgpQsQT53zBBm eS6niPjedh6nJOpPbsJ5HLt9iyEJbDgmrt/E8Ifxikbn6TrR3FVklO3ZpJAiaNdRO0KE elyVU47F5NDV4EmewXGA+CdVvlqsauLVx2d4tjiWAKykSJfcgJmPhjdeBX8QkpUMNok1 AHjRcVLNWr4dhbjnSX2dsaDzy4z87pyfmabF2m/6IEQpwQ60i0j4VFXNuzf4HBSSjzuF YrSA== Received: by 10.68.203.65 with SMTP id ko1mr9842705pbc.3.1333656507132; Thu, 05 Apr 2012 13:08:27 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org MIME-Version: 1.0 Received: by 10.68.136.197 with HTTP; Thu, 5 Apr 2012 13:08:05 -0700 (PDT) In-Reply-To: <4F7DF084.5050104@gentoo.org> References: <4F7DF084.5050104@gentoo.org> From: Gaurish Sharma Date: Fri, 6 Apr 2012 01:38:05 +0530 Message-ID: Subject: [gentoo-soc] Re: [GSOC 2012] Recruiting Webapp idea To: =?UTF-8?Q?Petteri_R=C3=A4ty?= Cc: gentoo-soc@lists.gentoo.org, Joachim Bartosik Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlgw/S+X7k14OjiyB6s+KFTGEvpvq18LTYW54/DFuIqiukB0wnEofNP2UyYXm/RRCcJ0AoC X-Archives-Salt: 060b4856-34ae-40a7-a19d-c9e5f202b6cd X-Archives-Hash: a478621d9554a402fb8d24084c77f092 Hi, Kindly read the replies inline: On Fri, Apr 6, 2012 at 12:50 AM, Petteri R=C3=A4ty = wrote: > On 04.04.2012 21:18, Gaurish Sharma wrote: > > >> b) the User interface is old, dated & just boring. We need a fresh theme= . > > CSS work is nice as long as we don't spend too much time on it. > Usability is more important than looking good. In some situations they > of course go hand in hand. --> I suggest that we switch to responsive design based on twitter bootstrap[1], so that webapp is accessible from all mobile,tablets & desktop browsers[1]. The toolkit has pretty good styling & is usable by default, however. I would customize according our needs. > >> 2) updating to Rails 3.0: >> Sure, I can do it. Why not update to latest version of rails v3.2.3, >> any specific reason to stick with 3.0? >> > > The hobo plugin we used currently only has a stable release out for > rails 3.0. There does seem to be work going for 3.1 so we could target > that instead after checking the hobo timetable for getting 1.4 out > (which is needed for rails 3.1). ---> v3.0 vs v3.1 -- There are a few backwards-incompatible changes in Rails 3.1 which affect the future upgrade path if we choose to develop in 3.0 only. rincipal among these are a new convention for the placement of images, stylesheets, and JavaScript files=E2=80=94collectively known as assets=E2=80=94and a change in the default JavaScript library from Prototype to jQuery. Further, 3.1 has cool features like Asset pipeline,Reversible migrations which we would miss out we stick with 3.0. However, With every new Rails release, there is a time delay while the rest of the ecosystem catches up. Now, hebo severely lagging behind. so I propose, we dump hobo & we writte the app as per the requirement while importing existing data on latest version of rails. The reason I want to dump hobo is: 1) it is lagging behind in support for latest releases 2) It is not core rails. 3) Hobo is good for protying but for apps that are required to go into production like recruiting app, traditional development model is preffered I hope this makes sense. > You should scope the draft proposal so that you yourself think there's > enough work to fill the whole GSoC for you. If think the items listed so > far are not enough for that feel free to ask for more ideas. --> Sure, please let know what more than I can do --Gaurish Sharma [1] http://twitter.github.com/bootstrap/