New CMS/Wiki ?

[Mark Guertin]

Hey all

Not sure if anyone has mentioned this yet, but I came across this _amazing_
system last night that I think would suit our needs very well, it can be
found at:

http://tikiwiki.sourceforge.net/

Mark

[Jon Nall]

I absolutely second this suggestion. tikiwiki looks really great.

nall.

Post by Mark Guertin
Hey all
Not sure if anyone has mentioned this yet, but I came across this _amazing_
system last night that I think would suit our needs very well, it can be
http://tikiwiki.sourceforge.net/
Mark
_______________________________________________
Zynaut mailing list
http://lists.zynot.org/mailman/listinfo/zynaut

[Mark Bainter]

Post by Jon Nall

Post by Mark Guertin
Hey all
Not sure if anyone has mentioned this yet, but I came across this _amazing_
system last night that I think would suit our needs very well, it can be

I absolutely second this suggestion. tikiwiki looks really great.
nall.

I'm also very impressed with this. In fact, the channel had
a virtual love-in over this thing last night. We should definately
give converting to this some careful consideration.

[Zach Welch]

Post by Jon Nall

On Tue, 2003-07-08 at 11:22, Mark Guertin wrote: Hey all
Not sure if anyone has mentioned this yet, but I came across this
_amazing_ system last night that I think would suit our needs

I absolutely second this suggestion. tikiwiki looks really great.
nall.

I'm also very impressed with this. In fact, the channel had a
virtual love-in over this thing last night. We should definately
give converting to this some careful consideration.

Okay, having only glanced at it, I can be sold on it as well. If this
is our current consensu, I will bring it up on jupiter instead of the
new version of moinmoin wiki I was working to install; there may be some
pain converting to the new format, but I think such a switch would be
worthwhile.

Another possibility suggested on the wiki (that may be orthagonal to
this) is the Request Tracker software, found at:

http://www.bestpractical.com/rt/

Because we have not yet established an incident reporting system, I
think now is the time for us to consider alternative tools to Bugzilla
as well.

Cheers

Zach

[jesse]

Post by Zach Welch
Another possibility suggested on the wiki (that may be orthagonal to
http://www.bestpractical.com/rt/
Because we have not yet established an incident reporting system, I
think now is the time for us to consider alternative tools to Bugzilla
as well.

can we associate rt "tickets" with bugid's in bzilla easily ?

[Mark Guertin]

Post by jesse

Post by Zach Welch
Another possibility suggested on the wiki (that may be orthagonal to
http://www.bestpractical.com/rt/
Because we have not yet established an incident reporting system, I
think now is the time for us to consider alternative tools to Bugzilla
as well.

can we associate rt "tickets" with bugid's in bzilla easily ?

Tikiwiki also has a (limited) capacity for tracking bugs, etc. Look at the
demo under the tracking menu option. This might be enough until we can get
a solid bugzilla up and running.

Mark

[Josiah Ritchie]

Post by jesse

Post by Zach Welch
Another possibility suggested on the wiki (that may be orthagonal to
http://www.bestpractical.com/rt/
Because we have not yet established an incident reporting system, I
think now is the time for us to consider alternative tools to Bugzilla
as well.

can we associate rt "tickets" with bugid's in bzilla easily ?

I don't know, but If we're using rt why work with bzilla? We don't need to
convert between the two, but I do have a connection that is moving from BugZilla
to RT and is interested in providing his work to the OSS community if for some
reason we are interested in this.

[Gareth Buxton]

Post by Zach Welch
Another possibility suggested on the wiki (that may be orthagonal to
http://www.bestpractical.com/rt/
Because we have not yet established an incident reporting system, I
think now is the time for us to consider alternative tools to Bugzilla
as well.

I like Bugzilla but another one to consider is this:

http://scarab.tigris.org/

I've not used it but if nothing else... I like the tigris website :)

[Zach Welch]

Post by Gareth Buxton

Post by Zach Welch
Another possibility suggested on the wiki (that may be orthagonal
http://www.bestpractical.com/rt/
Because we have not yet established an incident reporting system, I
think now is the time for us to consider alternative tools to
Bugzilla as well.

http://scarab.tigris.org/
I've not used it but if nothing else... I like the tigris website :)

Okay, to confuse the issue further, there is also mantis:

http://mantisbt.sourceforge.net/

Ideally, we want *one* tool for everything. Tikiwiki seems the best
thing so far, and I would rather see the community throw its weight
behind one tool than a number of them. I even know the bugzilla
configuration process and internal code base and would rather sacrifice
that in the short term for the long term ease of use.

In that regard, it seems that we could cut back significantly on
independent services using tikiwiki, so it still seems like the best
total solution for our needs. Thoughts?

Cheers,

Zach

[Mark Guertin]

Post by Zach Welch
Ideally, we want *one* tool for everything. Tikiwiki seems the best
thing so far, and I would rather see the community throw its weight
behind one tool than a number of them. I even know the bugzilla
configuration process and internal code base and would rather sacrifice
that in the short term for the long term ease of use.
In that regard, it seems that we could cut back significantly on
independent services using tikiwiki, so it still seems like the best
total solution for our needs. Thoughts?

I have a bit of reservation on using tikiwiki for bug tracking as well in
the long term. I have yet to see a system that has adequate bug tracking
for a large project AND is usable for other things.

For now I think it would be fine stand alone, but if/when bugs start rolling
in I think it may be unavoidable to go with a full blown Mozilla setup. I
guess time will tell, but I'm sure we will outgrow the capabilities in
tikiwiki once things are rolling.

There is a great bugzilla for large projects talk at OLS, so maybe we'll
have to schedule that one into things ;)

Mark

[Josiah Ritchie]

Post by Mark Guertin

Post by Zach Welch
Ideally, we want *one* tool for everything. Tikiwiki seems the best
thing so far, and I would rather see the community throw its weight
behind one tool than a number of them. I even know the bugzilla
configuration process and internal code base and would rather sacrifice
that in the short term for the long term ease of use.
In that regard, it seems that we could cut back significantly on
independent services using tikiwiki, so it still seems like the best
total solution for our needs. Thoughts?

I have a bit of reservation on using tikiwiki for bug tracking as well in
the long term. I have yet to see a system that has adequate bug tracking
for a large project AND is usable for other things.
For now I think it would be fine stand alone, but if/when bugs start rolling
in I think it may be unavoidable to go with a full blown Mozilla setup. I
guess time will tell, but I'm sure we will outgrow the capabilities in
tikiwiki once things are rolling.
There is a great bugzilla for large projects talk at OLS, so maybe we'll
have to schedule that one into things ;)

I'll toss in another option Request Tracker [http://www.bestpractical.com/rt/]
is used by corporate sites to track bugs or issues and I get the impression that
it's very flexible and could maybe be integrated into tikiwiki. It can be
authenticated off of Apache who can authenticate off of LDAP like tikiwiki. I
expect our devs could easily make it a seamless integration.

flickerfly

[Zach Welch]

Post by Mark Guertin
I have a bit of reservation on using tikiwiki for bug tracking as
well in the long term. I have yet to see a system that has adequate
bug tracking for a large project AND is usable for other things.
For now I think it would be fine stand alone, but if/when bugs start
rolling in I think it may be unavoidable to go with a full blown
Mozilla setup. I guess time will tell, but I'm sure we will outgrow
the capabilities in tikiwiki once things are rolling.
There is a great bugzilla for large projects talk at OLS, so maybe
we'll have to schedule that one into things ;)

Well, your comments basically underscored my own concerns, so we're back
to several possibilities for a problem tracking system. Certainly,
Bugzilla has a lot of favor from myself; however, I want us to continue
exploring other options until we absolutely must deploy a system.

At this point, we can't deploy a new physical server until Monday, so it
would be nice to know what system we want to use by then.

In the mean time, I will get tikiwiki set up for testing.

Cheers,

Zach

[Mark Guertin]

Post by Zach Welch
Well, your comments basically underscored my own concerns, so we're back
to several possibilities for a problem tracking system. Certainly,
Bugzilla has a lot of favor from myself; however, I want us to continue
exploring other options until we absolutely must deploy a system.

Agreed. I've just not really used a system aside from bugzilla that was
really adequate in handling any kind of volume stuff...

Post by Zach Welch
At this point, we can't deploy a new physical server until Monday, so it
would be nice to know what system we want to use by then.
In the mean time, I will get tikiwiki set up for testing.

Woohoo! and the zynaughts cheer wildly ... Hehe

Mark

[Josiah Ritchie]

Post by Mark Guertin
Agreed. I've just not really used a system aside from bugzilla that was
really adequate in handling any kind of volume stuff...

What features/needs are there for a system to handle the volume in your opinion?
I can't say I've had a wide breadth of experience, just hear and read stuff.

Post by Mark Guertin

Post by Zach Welch
In the mean time, I will get tikiwiki set up for testing.

Woohoo! and the zynaughts cheer wildly ... Hehe

second that

[Gareth Buxton]

Whilst collaboration tools are in the melting pot I just noticed this on
newsforge.

http://www.opengroupware.org/en/index.html

http://www.opengroupware.org/screens/webui/index.html

http://www.opengroupware.org/en/users/faq/index.html

Looks very interesting. The benefit of using groupware like this is that
you can plug in the tools you prefer or work with the provided web
interface (which looks rather good though it'd be better on Mozilla no
doubt...). It might be a good answer to the 'project management' issue
of working do tight schedules for releases, groups and subgroups etc...
Or maybe I'm just getting excited about something I newly discovered :)

- Galik

[Mark Guertin]

Post by Gareth Buxton
Whilst collaboration tools are in the melting pot I just noticed this on
newsforge.
http://www.opengroupware.org/en/index.html
http://www.opengroupware.org/screens/webui/index.html
http://www.opengroupware.org/en/users/faq/index.html
Looks very interesting. The benefit of using groupware like this is that
you can plug in the tools you prefer or work with the provided web
interface (which looks rather good though it'd be better on Mozilla no
doubt...). It might be a good answer to the 'project management' issue
of working do tight schedules for releases, groups and subgroups etc...
Or maybe I'm just getting excited about something I newly discovered :)
- Galik

It is _brutally_ painful to get setup and running, I spent much of the day
yesterday fighting with it. Very very fussy, no real configure scripts,
lots of hacking Makefiles, etc.

Also It's more catered to a business working environment, calendars and such
so I'm not sure how well it would apply here. It doesn't cover a lot of the
bases that we need.

Mark

[Dima Diall]

Post by Mark Guertin
Hey all
Not sure if anyone has mentioned this yet, but I came across this _amazing_
system last night that I think would suit our needs very well, it can
http://tikiwiki.sourceforge.net/
Mark

I support the idea of using Tiki for everything it is suitable enough...
Actually, I am evaluating it for deployment on my company's network for the
"perfect" WikiWiki I was looking. I like TWiki (http://twiki.org) too, as it
has lots of Wiki features/pluggins (particularly, it supports inline
image/drawing editing), but it store everything in the filesystem and it's
written in Perl (I find PHP a better tool for this particular job, even if
you're using mod_perl).

When I saw MoinMoin as our Wiki, I confess I was a little disapointed...
It's good, but I really think there are better options and am happy that the
community stepped forward and is considering a change! Wow, that's
openness... (Yeah, as a user I like Gentoo, but I always felt there was
something wrong in there - this project is so much different :-)

Besides the a well featured Wiki, Tiki has the following things I find
relevant for Zynot's webservices:
- HTML and Dynamic HTML Pages (ie: Live Updates!)
- CMS (Articles and Submissions)
- RSS Feeds (linking news from other relevant sites?)
- Editable Drawings and Figures (for quick design sketching on the Wiki, and
maybe more)
- File/Image Galleries (accessible from Wiki and other places)
- Weblogs/Journals
- Trackers (surely not up to par with RT, Bug/Issuezilla or Scarab, see more
below...)
- FAQs
- Comments
- Polls/Surveys/Quizzes (useful to gather opinions...)
- Forums (I guess it could replace phpBB, not sure if there is an import
mechanism)
- Web Chat/Internal Messaging (IRC and bots may be a better for this)
- Newsletters
- Calendar (community events, for instance)
- Webmail (for @zynot.org addresses maybe)
- User Tasks/Notepad/Files (not sure if appropriate or relevant)
- Links Directory (a dmoz-like categorized link directory... may be useful)
- and more...

(I'm good and copying & pasting ;-)

Last, but not least, a feature in the forthcomming release 1.7 (scheduled
for mid-July) there will be a (guess what...) full-fledged *WORKFLOW*
engine! I'm not sure yet, but this maybe be a great plus for managing things
like distribution release readiness cycles and a lot of other
business/development processes within Zynot.

Another thing I don't know is if this kind of tool could be useful for a
issue/bug/request/etc tracking system... But maybe a specifically tailored
solution for this stuff is better (RT, Bugzilla, Issuezilla or Scarab).
Comments anyone?

/dima

[Michael Martucci]

What does MoinMoin not have that is required?
Twiki (http://twiki.org/) is another mature wiki engine.

Michael.

Once upon a time (Tue, 08 Jul 2003 12:22:38 -0400)
Mark Guertin <***@brucemaudesign.com> tapped upon the
keyboard...

Post by Mark Guertin
Hey all
Not sure if anyone has mentioned this yet, but I came across this
_amazing_ system last night that I think would suit our needs very
http://tikiwiki.sourceforge.net/
Mark
_______________________________________________
Zynaut mailing list
http://lists.zynot.org/mailman/listinfo/zynaut

[Mark Guertin]

Post by Michael Martucci
What does MoinMoin not have that is required?
Twiki (http://twiki.org/) is another mature wiki engine.
Michael.

There's quite a bit of features it has that the current one doesn¹t...
Proper access control, an integrated blog, integrated 'ticket' watching,
i.e. Bugs, a forum, etc. It can pull all our needs into one environment
mostly.

Mark