A lot of Hobbit users are using Linux-based packages. Some of us use
"commercial" systems, so we have to compile from source. I think Hobbit
would be hobbled if it were to become a Linux-oriented package, which
could happen if it were to start depending on a lot of extras that are
not easy to port to other operating systems. People use Hobbit for all
sorts of reasons, and in all sorts of environments.
GLH
-----Original Message-----
From: T.J. Yang [mailto:user-8e841282cda5@xymon.invalid] Sent: Thursday, January 24, 2008 7:32 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Future of Hobbit
From: "Hubbard, Greg L" <user-d970b5e56ec9@xymon.invalid>
Sent: Thursday, January 24, 2008 7:26 AM
To: <user-ae9b8668bcde@xymon.invalid>
Subject: RE: [hobbit] Future of Hobbit
So how will all of that translate to all of the platforms that Hobbit supports today?
Greg
I don't quite understand your question, please explain more.
tj
GLH
-----Original Message-----
From: T.J. Yang [mailto:user-8e841282cda5@xymon.invalid]
Sent: Thursday, January 24, 2008 6:16 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Future of Hobbit
4. Maybe a new website? [...] I know Henrik has said in the past that he is not a web or UI designer, so perhaps we can find volunteers to spruce things up.
Yes - please!
Are we talking about the website that hosting hobbit or the hobbit web
GUI ?
I think both areas have rooms for enhancements.
Followings are my ideas.
1. Hobbit website.
Gains for using Trac
1.1 Trac
1.1.1 ticket system
1.1.2 A wiki system
1.1.3 Roadmap
1.1.4 SCM(using subversion until mercurial backend is stable.)
Example: http://trac.edgewall.org/
1.2 Mercurial, lets use distributed SCM solution please.
2. hobbit web GUI
2.1 switching to YUI-EXT 2.0 as web GUI.
Example: http://extjs.com/
2.2 Need to have capacity to enclose custom logos/banner for your site.
tj