#301 Make Neighborhoods namespaces

v1.0.0
closed
Dave Brondsema
ghosting (2) sf-8 (45)
General
nobody
2015-08-20
2010-07-07
Anonymous
No

Originally created by: sf-overlords

Allow projects with the same name to exist, as long as they are in separate neighborhoods. We'll need to find and check every place we look up a project by name. Here are a few known

  • Project lookup needs to query by neighborhood_id (not just shortname) e.g. NeighborhoodController._lookup
  • Probable changes to constructing & parsing URLs, email addresses, tool_data.sfx.unix_group_name etc to include the neighborhood prefix
    • with special knowledge of 'p' being default for sfx unix_group_name and doesn't need to be specified
  • update forge-classic name_taken() to include neighborhood
  • Shortlink.from_links matches the current neighborhood

An alternative approach (for mirroring at least) would be to use the u/ prefixing that user projects do to avoid namespace collisions.

Related

Tickets: #2194

Discussion

  • Mark Ramm - 2011-02-16
    • Description has changed:

    Diff:
    • milestone: limbo --> mar-03
     

  • Dave Brondsema

    Dave Brondsema - 2011-02-24
    • Description has changed:

    Diff:

    --- old 
+++ new 
@@ -3,3 +3,8 @@
 Assigned to:nobody

 Allow projects with the same name to exist, as long as they are in separate neighborhoods. 
+
+* Project lookup needs to query by neighborhood_id (not just shortname) e.g. NeighborhoodController._lookup
+* Existing user projects' shortnames should be changed from "u/foo[/bar]" to "foo[/bar]"
+* Probable changes to constructing & parsing URLs, email addresses, tool_data.sfx.unix_group_name etc to include the neighborhood prefix
+    * with special knowledge of 'p' being default for sfx unix_group_name and doesn't need to be specified
    • milestone: backlog --> mar-10
     

  • Dave Brondsema

    Dave Brondsema - 2011-03-28
    • Description has changed:

    Diff:

    --- old 
+++ new 
@@ -8,3 +8,4 @@
 * Existing user projects' shortnames should be changed from "u/foo[/bar]" to "foo[/bar]"
 * Probable changes to constructing & parsing URLs, email addresses, tool_data.sfx.unix_group_name etc to include the neighborhood prefix
     * with special knowledge of 'p' being default for sfx unix_group_name and doesn't need to be specified
+* update forge-classic name_taken() to include neighborhood
     

  • Dave Brondsema

    Dave Brondsema - 2011-06-28

    --init-- projects already exist within each neighborhood.

    If we do implement namespacing, how will artifact references work? E.g. [allura:#123] may need to be further qualified with a neighborhood name

     

  • Dave Brondsema

    Dave Brondsema - 2011-08-10
    • status: wont-fix --> open
    • milestone: apr-21 --> limbo
     

  • Dave Brondsema

    Dave Brondsema - 2011-08-10

    Reopening this, since several things require it (e.g. moving empty projects to a different neighborhood)

     

  • Dave Brondsema

    Dave Brondsema - 2011-11-10
    • labels: --> ghosting
    • milestone: someday --> dir-nov-18
     

  • Dave Brondsema

    Dave Brondsema - 2011-11-11
    • Description has changed:

    Diff:

    --- old 
+++ new 
@@ -1,11 +1,9 @@
-Created by: mramm
-Created date: 2010-04-25 19:32:38.794000
-Assigned to:nobody
-
-Allow projects with the same name to exist, as long as they are in separate neighborhoods. 
-
+Allow projects with the same name to exist, as long as they are in separate neighborhoods.  We'll need to find and check every place we look up a project by name.  Here are a few known 
+
 * Project lookup needs to query by neighborhood_id (not just shortname) e.g. NeighborhoodController._lookup
-* Existing user projects' shortnames should be changed from "u/foo[/bar]" to "foo[/bar]"
 * Probable changes to constructing & parsing URLs, email addresses, tool_data.sfx.unix_group_name etc to include the neighborhood prefix
     * with special knowledge of 'p' being default for sfx unix_group_name and doesn't need to be specified
 * update forge-classic name_taken() to include neighborhood
+* Shortlink.from_links matches the current neighborhood
+
+An alternative approach (for mirroring at least) would be to use the u/ prefixing that user projects do to avoid namespace collisions.
     

  • Anonymous - 2011-11-11

    Originally by: scoop

    • size: 0 --> 8
     

  • Dave Brondsema

    Dave Brondsema - 2011-11-11
    • status: open --> in-progress
    • assigned_to: Dave Brondsema
     

  • Dave Brondsema

    Dave Brondsema - 2011-11-18
    • status: in-progress --> code-review
    • qa: Kyle Adams
     

  • Dave Brondsema

    Dave Brondsema - 2011-11-18

    forge-classic:db/301, allura:db/301

    • code review several commits on both branches
    • create a project in /p and in /adobe with the same short names. Do various things that might select the wrong project.
     

  • Kyle Adams - 2011-11-22
    • status: code-review --> in-progress
     

  • Kyle Adams - 2011-11-23
    • status: in-progress --> closed
     

  • Kyle Adams - 2011-11-23

    Looks good, merged to dev.

     

Log in to post a comment.