[FreeNX-kNX] Wiki, Docs and Homepage

[lewis schmidt]

if and when you choose a cms please consider a wiki and if possible a
deki-wiki.
it's cleaner, easier and will allow more control on the documentation.
thankyou
L

On Mon, May 12, 2008 at 1:00 AM, Jeremy Wilkins <wjeremy at shaw.ca> wrote:

>
> Hey Fabian, I suggest that we use Bounty Source as our source hosting
> provider.  They support SVN for open source projects and make it available
> for users to post bounties for feature requests and fixes if they want a
> feature bad enough.  Someone can pickup the bounty and run with it.  It
> also
> has an amazing bug tracking system that could improve project tracking and
> feature and bug management.  We also don't have to suffer the overload of
> advertising that exists on sourceforge. (Most of which I might add is
> Microsoft ads)  There is also a wiki and CMS on there.  It lacks some user
> friendliness to get started, but once you get past that it is great!
>
> https://www.bountysource.com/
>
> I also wouldn't mind giving access to create a wiki and CMS as a subdomain
> of datakeylive.com on my server space.  I can give accounts to those that
> need it.  I have 1TB of transfer and 100GB of space that could be made
> available for it.
>
>
> Fabian Franz wrote:
> >
> > Hello all,
> >
> > I got used to berlios, but as their services seem to degrade in quality
> > (wiki not writable) and our homepage is not current anyway, I give out
> the
> > following "jobs":
> >
> > - Website manager:
> >
> > Your task is to manage the FreeNX website possibly with a CMS in
> > background so that changes can be easily done by editors.
> >
> > - Docs manager:
> >
> > Your task is to write new docs and look into old docs if they are
> current.
> > It seems tan is doing that quite well already, but he might need help.
> >
> > It also seems that classic bugtracking via berlios did not work out.
> >
> > I also would like to change to git for version control with a central
> svn
> > repository as master branch, so we can have several branches and I can
> > more easily pull from a tree or get Signed-Off patches that I can easily
> > apply or change.
> >
> > So any ideas where we can move, where we have a SVN, a very basic
> > bugtracking tool for reporting bugs with ML interface and a Wiki?
> >
> > Perhaps we could also use a TRAC for HP and Wiki and Bugs and Tickets
> and
> > leave the rest at berlios for now, while decreasing the amount of
> services
> > used from berlios.
> >
> > Is anyone willing to setup something like that for like freenx.org? (We
> > could point to your IP then ...)
> >
> > I think I am at a good stage for managing a stable version that is
> > changing, but still very stable. Also with RL management of 3 months.
> >
> > But the overall other things I would like to hear is what you think we
> can
> > do for managing the docs, HP and Wiki part more lively?
> >
> > So a very basic plan is:
> >
> > - Setup trac for wiki and bugs.
> > - Setup git via github (free).
> > - Use berlios only for SVN and file releases.
> >
> > Or you have better ideas? Please tell me!
> >
> > Best Wishes,
> >
> > Fabian
> > ________________________________________________________________
> >      Were you helped on this list with your FreeNX problem?
> >     Then please write up the solution in the FreeNX Wiki/FAQ:
> >   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
> >          Don't forget to check the NX Knowledge Base:
> >                  http://www.nomachine.com/kb/
> >
> > ________________________________________________________________
> >        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
> >       https://mail.kde.org/mailman/listinfo/freenx-knx
> > ________________________________________________________________
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Wiki%2C-Docs-and-Homepage-tp17083498p17181551.html
> Sent from the freenx-knx mailing list archive at Nabble.com.
>
> ________________________________________________________________
>     Were you helped on this list with your FreeNX problem?
>    Then please write up the solution in the FreeNX Wiki/FAQ:
>  http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>         Don't forget to check the NX Knowledge Base:
>                 http://www.nomachine.com/kb/
>
> ________________________________________________________________
>       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>      https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20080512/6ec611d4/attachment.html>