Mulgara
The two most important elements of Mulgara.org are now running: Mailing lists and Subversion.I've discovered that Yum is not the way to install Mailman on Fedora Core 4. It isn't integrated with any MTA which means that it needs a lot of manual configuration. After getting it working with Exim, I discovered that it wouldn't send any messages due to a problem with Sendmail. Moving from Exim to Postfix fixed the problem, but involved reconfiguring Mailman. Overall, a frustrating experience. I'm very grateful to Jesse for his help.
Jesse is the official administrator of mulgara.org, but like me he has other work to get done. Since I'm the one who's actually developing for Mulgara, he was more than happy to give me sudo and let me install the things I needed. The only problem is that he knows what he's doing, and I don't. :-)
Services
So where are we? We have:- Subversion.
- A Mulgara-general mailing list for announcements, user enquiries, and general discussions.
- A Mulgara-dev mailing list for developer discussion
- A web page stub.
Still to do:
- The web page is currently just a place holder. We need to come up with content, and we need to move all the documentation over to it.
- From a development point of view, we need to move all the
org.kowaripackages over toorg.mulgara. This would be easier with the refactoring tools in Eclipse, but these won't use the required svn mv command. Much of the first round will be a simple search/replace, so I may just be dusting off my perl/sed skills. To anyone with suggestions on how to do this more intelligently, please get in touch! - The site needs a signed certificate. Thawte and GoDaddy both have certificates for under $100, but I should check out with other what we really need. I'm guessing we only need the bare minimum.
- We need a Wiki and bug reporting system. Herzum Software has offered to provide licensed copies of Atlassian's Jira and Confluence for use by the project. I'll have to ask Jesse to install these, as I have no idea about either of them.
Feel free to write to me with any questions, advice or complaints. I'll answer, accept, and listen, respectively.
2 comments:
Paul, a couple of quick comments. 1) IntelliJ will do moving of files and the required svn/cvs commands automatically for you upon refactoring, so the move you're considering making would be a one second operation in it (literally, but then you have network and svn lag time). I believe Eclipse does the same thing, well it does for CVS anyway, but you can get svn plugins (subclipse?) that will probably do the same thing. 2). Atlassian will do Confluence and Jira free for open source projects, get in touch with them, they seem *really* good, we're just about to use Confluence at work and it seems great. Good stories about service too.
Hi Tom,
Since posting I discovered that while Herzum deals in Atlassian's software, the best approach is to ask Atlassian directly, as an open source project. I put the request in on Friday afternoon (CDT) and I'm waiting to hear back from them. They said that it can take 2 weeks to get a response. :-(
I already know about Confluence and Jira as we use them at work. I haven't done much with Jira (except receive emails from it), but Confluence is certainly one of the better Wikis I've used.
Thanks for the tips on IntelliJ. I'll try it out. I've been reluctant to use Subclipse as it still seems to be in early development. In particular, I don't know if a package name change will do an "svn mv", which is what we need if we want to keep the histories of all the files.
The other thing is that I've never been really happy with the say that Kowari interacts with Eclipse. It's better now that the jar files are flat, but it's still tough to configure correctly.
Post a Comment