Twiki might be an ok workflow model, but the security problems got it pulled
from debian, so *don't* use the code as a reference :-)
I have a successful engineering intranet moinmoin, but primarily because it
is in python so it was dead easy to add plugins to link to our other systems
(vc, bugs, sales tracking.) It's had a lot of development in recent years.
(That said, I might go with trac if I were starting again.)
(I want a full scale web2py wiki some day - but I think it would be good to
get *something* up by pycon to capture any enthusiasm stirred up by the
fresh publicity...)
On Mar 8, 2009 6:45 AM, "Jonathan B" wrote:
Hi Yarko and all,
Thanks for the feedback.
If you agree, I think that we can get started now. The wiki located at
https://mdp.cti.depaul.edu/wiki is good enough as a starting point for
documenting web2py. We can get going on creating and publishing a
source code repository for the community manual. I'm going to start
reading up on Sphinx.
Hopefully over the next few months we can get the Wiki transferred to
a more suitable location, preferably one either without HTTPS or with
a valid certificate.
On Mar 8, 12:03 pm, Yarko Tymciurak wrote:
>- we don't have Reddish (!) --- you (apparently) can't get your app
>source back from appspot, and Massimo did not put this under revision >
repository anywhere
Wow, that really sucks. Unfortunately, it's true that on Google App
Engine you can't recover your source directly. And it doesn't look
like Google is planning on fixing this issue any time soon, either. On
the bright side, old versions are retained on GAE, so you should be
able to safely replace Reddish with other code (although make sure to
change the version number when you upload). Then if Google *does*
fix this issue in the future you can still (in theory) recover the
Reddish source.
>- which leads to the second problem: the appliances are not dated,
not
>versioned, many of them (?) archaic, e.g. not able to run under current
>versions.
I fully agree with you. And all of the appliances should be fully
documented as well.
>- This same problem is now w/ the wiki - that is, it's not archived in
a
>versioning system anywhere... if it's going to be used, it should be
visible >/ accessible
Yes, I was hoping we could get the source code for the Wiki.
> This is up to Massimo & DePaul. We can host elsewhere too. > I think
Massimo has his hands ful...
I would love to help with this, but I can't do anything "official"
since I don't have the keys to anything web2py. I don't have the Wiki
source code, and I can't affect what's on web2py.appspot.com or on
web2py.com. So right now my hands are tied.
> 8 years is a long time; but Ok - then forget moin-moin for the moment...
I took another look at MoinMoin today, and the UI seems greatly
improved. However, most of the community seems to have its heart set
on a web2py-based Wiki... The current version of the Wiki doesn't
have a lot of features, but it seems to have enough for us all to get
started.
> Well - designing redditt is not the same as cloning it. For wiki's, we
> (in a major worldwid...
I agree that Twiki is an awesome example to emulate. We used TWiki
internally where I used to work.
--Jonathan --~--~-~--~~~---~--~~ You
received this message because...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~--~~~~--~~--~--~---
