IMHO, it's better to just set up a thin, core website, and leave most of the NHForge content in a backup somewhere. Most of it is very old, and even if it's relevant, the very age of the content is bad publicity. The first page has a prominent "follow us on Twitter" button. I don't think we want people to click it, The latest tweet was three years ago,
/G 2014-10-03 13:04 GMT+02:00 Jeffrey Becker <[email protected]>: > I've been checking into this and nothing seems to be turning up. There > don't seem to be all that many pages in the existing wiki. Maybe a manual > conversion is a better bet? > > On Monday, September 29, 2014 3:51:34 PM UTC-4, Alexander Zaytsev wrote: >> >> Hi Jeffrey, >> >> You can help with styling and with investigation of how to export wikis >> from communityserver (2008 I believe), and with proposal >> how to import wikis (structure, platform, etc). >> >> And, of cource, you can help with testing. >> >> Best Regards, >> Alexander >> 30.09.2014 6:44 пользователь "Jeffrey Becker" <[email protected]> >> написал: >> >> Is there anything I can do to help or does this require people who >>> already have access to nhforge etc? >>> >>> On Monday, September 29, 2014 12:26:37 AM UTC-4, Alexander Zaytsev wrote: >>>> >>>> Hi guys, >>>> >>>> I've managed to export blog posts from nhforge.org. The very first >>>> alpha preview of the new github-pages based website is available at >>>> http://nhibernate.github.io/ >>>> >>>> What needs to be done: >>>> >>>> 1. Apply theme >>>> 2. Copy comments to disqus (any alternatives?) and enable them on a blog >>>> 3. Migrate wiki to github >>>> 4. Move over to a new domain. >>>> >>>> Please contribute >>>> >>>> Best Regards, >>>> Alexander >>>> >>>> >>>> 2014-08-26 7:00 GMT+12:00 Oskar Berggren <[email protected]>: >>>> >>>>> We seem to have repeated issues with nhforge being comparatively >>>>> difficult to update, and right now it seems everyone is locked out. Though >>>>> it's not too bad it could also do with a facelift. >>>>> >>>>> We might look into migrating this to Github. As I understand it we >>>>> could have static content in Github Pages (as a organization-level >>>>> repository), for which anyone can suggest an update using a pull request. >>>>> There is also Github Wiki. >>>>> >>>>> I've never really used Github Pages or Wiki so cannot evaluate so far. >>>>> Maybe others have thoughts? >>>>> >>>>> Anyway, such a migration could be done by a volunteer who would like >>>>> to help without digging deep into NHibernate source code. >>>>> >>>>> /Oskar >>>>> >>>>> -- >>>>> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "nhibernate-development" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "nhibernate-development" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > > --- > You received this message because you are subscribed to the Google Groups > "nhibernate-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
