Hi Gunnar On Mon, 2007-01-08 at 09:15 +0100, Gunnar Wagenknecht wrote: > Hi! > > Kristis Makris wrote: > > http://bugzilla.mkgnu.net/show_bug.cgi?id=821 > > I wonder if it's possible to host the project on an open source hosting > platform? I can't signup on that Bugzilla for watching issues.
I don't mind giving people accounts on the existing Bugzilla system. I simply don't want anyone to sign-up at will, and worry about the security implications. If you and I exchanged a few words, just ask and I'll create an account. This goes for anyone on this list. I'll create an account for you, Gunnar. I am not willing to move the project on an open source hosting platform. E.g. sourceforge was inacessible for quite a while, causing people all sorts of kinds of problems. I'd rather have some control over the problems that arise (...and cause them myself!) > When this bug is implemented there should be also an option to obtain > the project name from the SCM. For example, some SCMs do have the > meaning of product/project names and in Subversion this could be > implemented using a property. What will be the convention ? What is the property name ? It could be implemented using a property, but there's no standard for it yet by Subversion. When one is put in place, we could implement it, sure. The problem, especially in Subversions case, is that some repository configuration information (like a product name), can't be specified in "the best possible way" yet. See http://bugzilla.mkgnu.net/show_bug.cgi?id=876 I plan on addressing this. > BTW, what is the overall strategy for hosting multiple products in one > repository? I'm installing a new Subversion repository for our company > and after some discussion and suggestions I do not want to create > multiple repositories for the different products but one repository for > the whole company (like ASF uses one repository for all it's projects). Indeed, if you have a look at: http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-18-3/manual/html-single/manual.html#VERIFICATION-CHECKS-VALID-PRODUCT-NAME ...you'll note that you could have multiple product names in the repository, just like you describe below, and they will be autodetected > The structure would be similar to: > > /productname/[trunk|tags|branches] > /classification/productname/[trunk|tags|branches] > /classification/productname/[trunk|tags|branches]/component > /some/other/dir/productname/[trunk|tags|branches] > > > Also, what's the functional requirement behind the product name? Must it > be the same name as in Bugzilla? Actually, the single identifier is the > bug id so I wonder why do I need product names on the SCM side? Yes, it should be the same name as in Bugzilla. The product names are needed on the SCM side in case the user enters the wrong bug id: a bug id that belongs to another project. It's an additional verification check. _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
