Hi all,
The last project I personally know of that was using MonticelloCVS (as opposed to Monticello's native versioning) has finally been migrated to the new(er) system, which leads me to wonder if there are any MonticelloCVS users left. Anyone? If so, please speak now - otherwise, I will declare it officially unsupported, and probably remove it from SqueakMap to avoid confusion.
Cheers, Avi
Il gio, 2004-10-07 alle 21:10, Avi Bryant ha scritto:
Hi all,
The last project I personally know of that was using MonticelloCVS (as opposed to Monticello's native versioning) has finally been migrated to the new(er) system, which leads me to wonder if there are any MonticelloCVS users left. Anyone? If so, please speak now - otherwise, I will declare it officially unsupported, and probably remove it from SqueakMap to avoid confusion.
Hi Avi,
we still use MonticelloCVS for our tool, XPSwiki (http://www.agilexp.org/xpswiki). We use it for the files in our xpswiki/ subdirectory.
A couple of months ago I also asked you on IRC if it was possible to extend Monticello to manage external resources.
Giovanni
Avi Bryant wrote:
Hi all,
The last project I personally know of that was using MonticelloCVS (as opposed to Monticello's native versioning) has finally been migrated to the new(er) system, which leads me to wonder if there are any MonticelloCVS users left. Anyone? If so, please speak now - otherwise, I will declare it officially unsupported, and probably remove it from SqueakMap to avoid confusion.
I was once thinking to establish something like "SqueakForge" based on GForge <www.gforge.org> for hosting various projects. There's already support for CVS in it so I thought there would be a place for MonticelloCVS. Anyhow, there is SqueakSource now, though it is yet far away from GForge regarding features/capabilities.
Speaking about development, I still miss a single place where VM development is hosted. MS Windows' version is being kept on SourceForge which doesn't like openness of Squeak. SqueakFoundation doesn't have CVS as promised before 3.7 release.
I have a possibility to place a server on 1GBit line here in local university. But I'm still looking for some spare hardware. I will let you know if something new will happen with this.
SqueakSource is a kind of SourceForge. Why don't you participate to ssqueaksource the code is there? And you could add what miss you.
Stef
On 8 oct. 04, at 08:54, Kamil Kukura wrote:
Avi Bryant wrote:
Hi all,
The last project I personally know of that was using MonticelloCVS (as opposed to Monticello's native versioning) has finally been migrated to the new(er) system, which leads me to wonder if there are any MonticelloCVS users left. Anyone? If so, please speak now - otherwise, I will declare it officially unsupported, and probably remove it from SqueakMap to avoid confusion.
I was once thinking to establish something like "SqueakForge" based on GForge <www.gforge.org> for hosting various projects. There's already support for CVS in it so I thought there would be a place for MonticelloCVS. Anyhow, there is SqueakSource now, though it is yet far away from GForge regarding features/capabilities.
Speaking about development, I still miss a single place where VM development is hosted. MS Windows' version is being kept on SourceForge which doesn't like openness of Squeak. SqueakFoundation doesn't have CVS as promised before 3.7 release.
I have a possibility to place a server on 1GBit line here in local university. But I'm still looking for some spare hardware. I will let you know if something new will happen with this.
-- Kamil
stéphane ducasse wrote:
SqueakSource is a kind of SourceForge. Why don't you participate to ssqueaksource the code is there? And you could add what miss you.
Stef
I will take a look as it is published as project itself, which is cool. Looking at URL parameters (after www.squeaksource.com - funny it's not .org or .net TLD that I would expect) I wonder what version of Seaside does it use? Also, is there any backend being used? I'm thinking of adding some issue tracking capabilities, but idea of having bugs and their comments stored in memory/image only is somehow distracting.
On Oct 11, 2004, at 1:31 PM, Kamil Kukura wrote:
stéphane ducasse wrote:
SqueakSource is a kind of SourceForge. Why don't you participate to ssqueaksource the code is there? And you could add what miss you.
Stef
I will take a look as it is published as project itself, which is cool. Looking at URL parameters (after www.squeaksource.com - funny it's not .org or .net TLD that I would expect) I wonder what version of Seaside does it use?
2.3.2, I believe. I know they were working on updating it to 2.5, but that work's not done yet.
Avi
It would be good to have a kind of Mantis application to track bugs. Please start and you will be famous :) and you can use the back end you want.
For Squeaksource, they use the file system I guess.
Stef On 11 oct. 04, at 13:31, Kamil Kukura wrote:
stéphane ducasse wrote:
SqueakSource is a kind of SourceForge. Why don't you participate to ssqueaksource the code is there? And you could add what miss you.
Stef
I will take a look as it is published as project itself, which is cool. Looking at URL parameters (after www.squeaksource.com - funny it's not .org or .net TLD that I would expect) I wonder what version of Seaside does it use? Also, is there any backend being used? I'm thinking of adding some issue tracking capabilities, but idea of having bugs and their comments stored in memory/image only is somehow distracting.
-- Kamil
Just for information: I'm developing a requirement, issue and task management system in Squeak. Take a look at http://www.tideland.de/products/rms/ and http://wiki.tideland.de/wiki/TidelandRequestManagementSystem for information about the development process.
mue
It would be good to have a kind of Mantis application to track bugs. Please start and you will be famous :) and you can use the back end you want.
For Squeaksource, they use the file system I guess.
Stef On 11 oct. 04, at 13:31, Kamil Kukura wrote:
stéphane ducasse wrote:
SqueakSource is a kind of SourceForge. Why don't you participate to ssqueaksource the code is there? And you could add what miss you.
Stef
I will take a look as it is published as project itself, which is cool. Looking at URL parameters (after www.squeaksource.com - funny it's not .org or .net TLD that I would expect) I wonder what version of Seaside does it use? Also, is there any backend being used? I'm thinking of adding some issue tracking capabilities, but idea of having bugs and their comments stored in memory/image only is somehow distracting.
-- Kamil
Just for information: I'm developing a requirement, issue and task management system in Squeak. Take a look at http://www.tideland.de/products/rms/ and http://wiki.tideland.de/wiki/TidelandRequestManagementSystem for information about the development process.
I like the slogan :) The only constant is change. nice
Now have you look at Mantis and how do you compare in few words.
Just for information: I'm developing a requirement, issue and task management system in Squeak. Take a look at http://www.tideland.de/products/rms/ and http://wiki.tideland.de/wiki/TidelandRequestManagementSystem for information about the development process.
I like the slogan :) The only constant is change. nice
Now have you look at Mantis and how do you compare in few words.
I don't know Mantis right now. But I'm working with trouble ticket systems since the early 90s. After a company change in 1997 my new employer had no such system. So I've developed a first interims solution as a Perl CGI with PostgreSQL as DBMS. And you know the story: Interims solutions allways live longer than expected.
With my next job changes the system got more requirements management features. And now it is time for a complete reimplementation - in Squeak. It will be a complete environment for the management of software development projects.
So one can define a project, add use cases to it, add requirements and link them to the use cases and can add todos and link them to the requirements. Also if issues occur they can be added and for them again todos. Those todos will then be linked to users.
Seems that I have to write more information on our web site. Currently I'm documenting the technical part in our wiki. Everyone who is interested in our way should take a look here. On the Recentchanges pages is also an RSS link.
mue
ok have a look at Mantis because this is only a bug tracking system but a good one.
Stef On 13 oct. 04, at 12:09, Frank Mueller wrote:
Just for information: I'm developing a requirement, issue and task management system in Squeak. Take a look at http://www.tideland.de/products/rms/ and http://wiki.tideland.de/wiki/TidelandRequestManagementSystem for information about the development process.
I like the slogan :) The only constant is change. nice
Now have you look at Mantis and how do you compare in few words.
I don't know Mantis right now. But I'm working with trouble ticket systems since the early 90s. After a company change in 1997 my new employer had no such system. So I've developed a first interims solution as a Perl CGI with PostgreSQL as DBMS. And you know the story: Interims solutions allways live longer than expected.
With my next job changes the system got more requirements management features. And now it is time for a complete reimplementation - in Squeak. It will be a complete environment for the management of software development projects.
So one can define a project, add use cases to it, add requirements and link them to the use cases and can add todos and link them to the requirements. Also if issues occur they can be added and for them again todos. Those todos will then be linked to users.
Seems that I have to write more information on our web site. Currently I'm documenting the technical part in our wiki. Everyone who is interested in our way should take a look here. On the Recentchanges pages is also an RSS link.
mue
-- ** ** Frank Mueller / Oldenburg / Germany ** ** frank@mweb.de http://www.mweb.de **
It would be good to have a kind of Mantis application to track bugs. Please start and you will be famous :) and you can use the back end you want.
I wish I could find some time for this. For sake of survival I need to willy-nilly work on stuff that has nothing to do with Squeak :(
Moreover, I find I tend to spend more time on *studying* what is this and that in Squeak and trying to catch-up with all those things like SqueakMap, Monticello, SAR files, update streams... It then leaves feeling like being non-competent to touch anything.
For Squeaksource, they use the file system I guess.
I would try bet on GOODS. It seems to be most used backend when mentioning Seaside2 applications.
On Oct 28, 2004, at 6:53 PM, Kamil Kukura wrote:
For Squeaksource, they use the file system I guess.
I would try bet on GOODS. It seems to be most used backend when mentioning Seaside2 applications.
SqueakSource does use the filesystem, but yes, GOODS is an increasingly common choice among Seaside users. Though I've also been involved with Seaside apps that use OmniBase, Postgres, MySQL, SQLite... the constraints on persistence seem to vary more than almost anything else from project to project.
squeak-dev@lists.squeakfoundation.org
-
Avi Bryant -
Frank Mueller -
Giovanni Corriga -
Kamil Kukura -
stéphane ducasse