GitHub

Comments and changes to this ticket

• 

  David Chelimsky March 17th, 2008 @ 03:58 AM

  +1 for supporting linking to an external wiki. Should that be its own ticket?

• 

  Alex Coles March 17th, 2008 @ 06:40 AM

  Yes, probably. Go ahead and break it out into two if you'd like.

• 

  defunkt March 24th, 2008 @ 12:08 PM

  • → Assigned user changed from “defunkt” to “Tom Preston-Werner”
  • → State changed from “new” to “open”
• 

  Alex Coles March 24th, 2008 @ 12:36 PM

  @David Chellmskey: Created a separate ticket (#64) for external wiki.

• 

  Alex Coles March 24th, 2008 @ 12:37 PM

  @David Chellmsky: Created separate ticket #64 for external wiki (apologies for the misspelling)

• 

  defunkt March 24th, 2008 @ 01:01 PM

  Adding extra metadata, I think, should definitely happen. Especially links to "other" urls - perhaps the blog post announcing the project and the project's home page are distinct but important pages.

• 

  Alex Coles March 24th, 2008 @ 02:55 PM

  __With regards to linking to external wikis__:

  If the top-level tabs must also link to GitHub.com paths (as stated in

  ticket #64) then perhaps it could be possible to:

  1. disable the 'wiki' top-level tab (to avoid confusion)
  2. provide some form of customizable secondary level navigation based

  on the metadata fields.

  __With regards to what metadata should be available__:

  I am thinking primarily in terms of O/S projects here, but they

  generally have the following associated sites, parts of sites,

  microsites or addresses out there:

  1. homepage (or 'About this project' page)
  2. wiki
  3. blog
  4. issue tracking
  5. #irc channel

  For coherence sake (and because users may come across a project

  through GitHub itself), it would great to be able to link to these all

  through GitHub. Therefore, I would propose that unlimited URL/

  addresses be allowed for each project -- at least at a data model

  level (obviously, its not going to desirable or feasible to display

  100s of URLs without breaking the page layout).

  The above list could make up a standard, pre-defined list of URL/

  address types (#irc channels are not addresses, I know). Additional

  customizable URL/address types could be added on top of this list.

  I am not sure how well I've described that, and I have no idea how you

  implement your persistence/data storage level, but I would think that

  this would normally be accomplished with a polymorphic table design:

  project_id | url | url_type

• 

  Alex Coles March 24th, 2008 @ 04:09 PM

  An example of UI from LinkedIn, in case my previous post was unclear.

  • LinkedIn__My_Profile__Additional_Information.jpg 18.6 KB