Apache Allura™

All our tools, including code repos, prohibit underscores since we use the "mount point" value in subdomains (e.g. for email notifications). Changing that would be a fairly big architectural change, so its not feasible, sorry.

I'm not familiar with Gerrit but it seems like it should be able to synchronize each repo with a remote repo individually, and specify the (different) name for the each remote.

• Description has changed:

Diff:

--- old
+++ new
@@ -4,6 +4,6 @@

 >We run our own source code repositories and we replicate to sourceforge. Basically we just publish code on sourceforge, we don't actually work off of sourceforge. (We use gerrit as it's a code review system for git and SF doesn't have gerrit right now.) Think of it like rsyncing from one server to another, you can change the server name and root path, but the directories with in are expected to be identical or it'll think it's different. It's not really feasible for us to change our repository names to dashes either or we'd have to notify all the developer to change their machines and other people who have replicated their servers etc.

->As for criticallity, it's critical but not urgent. Since we use or own source code repository this means it's had no effect on our daily working. It just means SF has not had any of our updates in the last few days. That's no big deal to daily working (but more of a deal in the spirit of publishing open source code as our code isn't as available). We specifically choose this project because it's low usage and can suffer for a bit with no real complaints. We're actually part of the other project "oscarmcmaster" which is much more critical. This was more of a dry-run for migrating that project, that one would be more problemmatic if it failed.
+    >As for criticallity, it's critical but not urgent. Since we use or own source code repository this means it's had no effect on our daily working. It just means SF has not had any of our updates in the last few days. That's no big deal to daily working (but more of a deal in the spirit of publishing open source code as our code isn't as available). We specifically choose this project because it's low usage and can suffer for a bit with no real complaints. We're actually part of the other project "oscarmcmaster" which is much more critical. This was more of a dry-run for migrating that project, that one would be more problemmatic if it failed.

 Is that possible? If not, is there an alternative we can suggest?

• status: open --> closed
• milestone: limbo --> forge-nov-30

Originally by: tedleung

not quite, think of it as being rsync.

effectively what's happenning is you're rsyncing 2 servers and all of a sudden one of the servers decides to change all the subdirectories with underscores in their names to dashes. You can imagine how rsync would now fail and that anyone trying to read from the synced server would no longer retrieve what was on the original server.

It's a pretty serious thing to have to tell anyone with a git repository with underscores that they have to go to every single synced and replicated computer and change all their repository names, note this includes developer machines so if there's 10 synching server (for which sourceforge is just one) and 10 developers work off of each of their servers, then it's like a tree of people you have to track down, some of which you don't directly work with. Think about linux and the distributed repositories and how each distribution has their own server which then has their own set of developers and set of associated servers like build servers etc.

• status: closed --> open
• Milestone: forge-nov-30 --> forge-may-03

We are reconsidering this. ML thread http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201304.mbox/%3CCAEMb8zVHx2CJW3Qizgc2cgpCgs-bh8ibr1f6HY%2BKvySeAgq6rQ%40mail.gmail.com%3E

• Size: --> 4

• Milestone: forge-may-03 --> forge-may-17

• Milestone: forge-may-17 --> forge-may-03

• status: open --> in-progress
• assigned_to: Tim Van Steenburgh

• status: in-progress --> code-review

forge:tv/5332
forge-classic:tv/5332

Test installing repo tools, other tools, and subprojects with legal and illegal mount point names.

• QA: Dave Brondsema

• status: code-review --> in-progress

{{tool.app.relaxed_mount_points and 'true' or 'false'}} is hard for me to read. How about this? {{'true' if tool.app.relaxed_mount_points else 'false'}}

make_safe_path_portion is used in migrate.py several places for repos, but that doesn't use the relaxed restrictions. Example output: https://sf-dbrondsema-9030.sb.sf.net/p/cygwin-ports/_list/git

Should re_path_portion be renamed to reflect it's usage just for project/user names? (If that's correct). The new re_tool_mount_point and re_relaxed_tool_mount_point names are clear to me, but re_path_portion is not.

Also the mount point labels shouldn't be munged like this mount_label=repo['repo_name'].replace('-', ' ').title() Probably want to make our special names code/git/hg/svn/cvs be specially labelled too so they aren't lowercase labels.

• status: in-progress --> code-review

Changes on forge and forge-classic. And for the record, I totally agree with you about that jinja expression...dunno what I was thinking. :)

SourceForge has a max length for subproject names. If you try to register one that's too long it errors with "SFXBadRequest: Error status 400 Project unix name too long". That's fine, only problem is the contextual help said up to 63 chars would be fine, so that's misleading.

• status: code-review --> closed