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