+1 for me!
I dont like the current mix between nhibernate and hibernate on one site
because its often hard to figure out where nhibernate ends and hibernate
begins. And then i think the Hibernate page is not a good example for
clearness and easy webdesign.
I am also suggest to discard the current forum and integrate the user
mailing list as forum as the mono project it did:
http://www.go-mono.com/forums/ .
Then there is only one place for questions and every user can decide
which communication type he prefer.
By, Steve
Fabio Maulo schrieb:
> Hi friends.
>
> We are thinking to have our own site based on NH with our knowledge base,
> our wiki, committers and users blog, How to, FAQ and so on.
> The fact is that so far .NET peoples don't like so much look&feel +
> usability of www.hibernate.org
>
> The proposal for our site is: Cuyahoga (it work using NH), SubText,
> Screwturn Wiki
>
> At the moment it is only an idea and first of all I would like to hear
> opinions of the team.
>
> If we have a good response we can check the response of the community on
> nhusers forum.
>
> Waiting opinions....
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Nhibernate-development mailing list
> Nhibernate-...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nhibernate-development
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nhibernate-development mailing list
Nhibernate-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nhibernate-development
I am also suggest to discard the current forum and integrate the user
mailing list as forum as the mono project it did:
http://www.go-mono.com/forums/ .
Then there is only one place for questions and every user can decide
which communication type he prefer.
What's the current involvement of JBoss with NHibernate?
Do they still support NHibernate?
Or do they 'own' something like names or trademarks?
If not, I think it's alright to have our own site.
I can help setting this up. For example, we already have a Screwturn
Wiki user provider @Cuyahoga for single sign-on.
Does NHibernate get any funding or sponsoring at the moment? This could
be useful for hosting etc.
I like the idea of a separate site for NHibernate.
The only tiny issue is that NH projs still don't have their own documentation, corresponding Hibernate projs documentation is used instead which is offerred on the Hibernate website.
For a lot users, documentation is the first thing they will try to find on the projects website...
I have a few IIS servers sitting in datacenter I lease from if we need hosting.
Great, just thought I’d offer.
I have a few IIS servers sitting in datacenter I lease from if we need hosting.
I am going to take care of hosting it, so that is not an issue.
Of course.
From:
nhibernate-deve...@lists.sourceforge.net
[mailto:nhibernate-deve...@lists.sourceforge.net] On Behalf Of Fabio
Maulo
Sent: Friday, June 20, 2008 8:58 AM
To: the NHibernate development list
Subject: Re: [NHibernate-development] NH site
2008/6/20 Sean Fuhrmann <t...@agentimediaservices.com>:
This is kind of like before NHibernate moved to hibernate.org. We had a separate forum which was better than the current one since we could create sub sections and organize it like we wanted.
Aside that, we have to think of what value there is in moving out? - Blogging? Is anybody interesting in creating/moving his blog to nhibernate.org/blogs/ ? - Documentation (How to, Faq...): Well, I would highly prefer any documentation be inside the official one (in docbook format) since that one can be compiled and released for online access/printing/whatever. Now, I know that it is quite restrictive (since it is docbook), and that's why we have this page: http://www.hibernate.org/365.html Maybe we could ressucitate the wiki that we had a while ago...
By the way, if we decide to create a new forum, it is highly important to export the current one (even if it isn't reorganized) because it contains a lot of information that should stay available (without having to juggle between two websites).
So, overall, I fear that it might be not be worth the effort. But I could be wrong if you have any specific ideas.
Oh, and about JBoss, let's not be unfair: They did pay Sergey to work full time on NHibernate for about a year and it is in that time frame that NHibernate 1.0 was released (which required a lot of clean up, organization and proper documentation). I think that they stopped supporting NHibernate simply because it wasn't profitable enough and too much "out of line" (since they focus on Java). And does RedHat really "owns" anything? We should be able to take back nhibernate.org if we want to...
Pierre Henri.
|
From: Fabio Maulo <fabio...@gmail.com> |
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php |
This is kind of like before NHibernate moved to hibernate.org.
We had a separate forum which was better than the current one since we could create sub sections and organize it like we wanted.
Aside that, we have to think of what value there is in moving out?
- Blogging? Is anybody interesting in creating/moving his blog to nhibernate.org/blogs/ ?
- Documentation (How to, Faq...):
Well, I would highly prefer any documentation be inside the official one (in docbook format) since that one can be compiled and released for online access/printing/whatever. Now, I know that it is quite restrictive (since it is docbook), and that's why we have this page: http://www.hibernate.org/365.html
Maybe we could ressucitate the wiki that we had a while ago...
By the way, if we decide to create a new forum, it is highly important to export the current one (even if it isn't reorganized) because it contains a lot of information that should stay available (without having to juggle between two websites).
So, overall, I fear that it might be not be worth the effort. But I could be wrong if you have any specific ideas.
Oh, and about JBoss, let's not be unfair: They did pay Sergey to work full time on NHibernate for about a year and it is in that time frame that NHibernate 1.0 was released (which required a lot of clean up, organization and proper documentation).
I think that they stopped supporting NHibernate simply because it wasn't profitable enough and too much "out of line" (since they focus on Java).
And does RedHat really "owns" anything? We should be able to take back nhibernate.org if we want to..
--
Jokin
* Fabio Maulo <fabio...@gmail.com> [20.06.2008]:
> We are thinking to have our own site based on NH with our knowledge base,
> our wiki, committers and users blog, How to, FAQ and so on.
> The fact is that so far .NET peoples don't like so much look&feel +
> usability of www.hibernate.org
>
> The proposal for our site is: Cuyahoga (it work using NH), SubText,
> Screwturn Wiki
>
> Waiting opinions....
are you determined to use Windows/.NET based software? We are currently
working on a collaboration platform based on well-known OSS tools like
moinmoin (wiki), svn, Bugzilla (bugtracking) and other components as
they are required (blog, forum, mailinglists). We aim to build a system
similar to trac, but with much more powerful components. This esp. holds
true for the bugtracker and wiki. It was one of the main reasons, not
to use trac. We too have a timeline and try to integrate the separate
components as tight as possible (though we will not reach the level of
integration of trac in the near future). The software stack is linux
based to ease hosting and adminsitration. So if linux/unix is a
show-stopper for you, don't read further... :)
We use this system already in various internal .net projects and have
integration of nant/cruise control build events for the project
timelines (the timeline lists project related events similar as trac
does, eg. svn commits, changes in the wiki, in the bug database etc.)
and more. The system (it is named Liaison) is designed to be easily
extended and adjusted for project specific needs.
Liaison is now self-hosting for several months. We plan to make Liaison
public on July (this year :) ) and it'll be of course open source. We
will release demo images for vmware player or VirtualBox as well, so if
this sounds interesting for you, let me know.
Cheers,
- Thorsten