On Sun, Mar 8, 2009 at 1:01 AM, Jonathan B <[email protected]> wrote:
> > Hi all, > > > On Mar 5, 7:23 pm, Yarko Tymciurak <[email protected]> wrote: > > one advantage to a web2py wiki: we can dump (csv) contents in prep for > > sphinx integration / work. > > Yes, that is an advantage, although I'm sure we could implement this > feature for any open source Wiki software without too much trouble. I'm not convinced.... > > I think the main advantage of using web2py would be hosting > requirements. We can run a web2py Wiki on a free GAE account, such as > http://web2py.appspot.com (where we currently have Reddish). This is another, separate, and potentially serious problem: - 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. When his disk drive died, the current Reddish died with it. The beginnings of it are all that's on the appliances link; - 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. We need an update to the appliances appliance to solve this, as well as a test suite to run to validate that an application runs (in the appliances gallery) - or "last tested under" marking on it. Non-running appliances are bad advertising... - 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. (I suspect there might be some class project / assignment type of issues at play here...) > > As an alternative, we could run an existing Wiki software off of > Massimo's university hosting, but I don't like the current setup. We > don't need HTTPS (except perhaps for login), and the expired self- > signed certificate is problematic. Can the HTTPS be removed? This is up to Massimo & DePaul. We can host elsewhere too. I think Massimo has his hands full, and would probably be happier to see us offload this... > > > We can easily put the manual's Sphinx/RST code into Bitbucket or > Launchpad, so free hosting is already available for that. Bitbucket, Launchpad, or github... Same for important appliances... > > > > On Mar 5, 9:45 pm, Francisco Gama <[email protected]> wrote: > > > I personally have a very bad experience with MoinMoin. It's visual UI > > is very weak > > This is my main complaint regarding MoinMoin as well. When I tried it > some 8 years back, it was virtually unusable. 8 years is a long time; but Ok - then forget moin-moin for the moment... > > > honestly I believe it's not hard to make something with a better base > > design from scratch in very little time. > > I must disagree here. It's surprisingly difficult to reinvent the > wheel. If we go ahead and try using a brand new web2py Wiki for real > work, we *will* have some problems--problems that we will avoid if we > use mature software. Well - designing redditt is not the same as cloning it. For wiki's, we (in a major worldwide corp) use a commercial wiki (languishes) and an open source one (really gets a lot of traction). Let's clone Twiki (from design structure), and make the rendering reST (or optionally markdown). This can be done incrementally; the features organized; at least it's better than "making up your own" from scratch (better to start w/ something and incrementally improve). > > > Being a WiKi engine a web application and being web2py a framework for > > web app development, it makes sense even for capabilities > > demonstration to show off what it can do. > > I agree, but that doesn't mean we must use a web2py Wiki right away... > this can be the plan for Phase 2. Ok - then what do we use for Phase 1? Trac does wiki in reST... but that makes me want to throw in w/ a web2py wiki... > > > Sincerely, > > --Jonathan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
