Opened 7 years ago

Closed 6 years ago

#8941 closed (invalid)

Shared identity across all of the different Django community sites

Reported by: simon Owned by: ericholscher
Component: Uncategorized Version: 1.0
Severity: Keywords: djangocon
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Adrian and Jacob on stage at DjangoCon.

Change History (8)

comment:1 Changed 7 years ago by simon

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

E.g. you're a committer, and you've released code on Google Code, and you have snippets on Django Snippets, and you aggregate your stuff on Django Community, etc etc etc. Jacob says: "It would be really neat if we could have federation between all of these two social sites built around the Django community"

comment:2 Changed 7 years ago by rossp

I would like to be involved in this to integrate things from my end at djangosites.org.

Sites I think that should 'know' about each other include at least:

  • djangosites.org
  • djangopeople.net
  • djangosnippets.org

Others which I haven't thought about just yet...

OpenID support means the authentication isn't an issue, but the sites should know about each other at a lower level - a listing at djangosites should say "See this authors full profile at djangopeople, and see their code commits at djangosnippets/google code.".

comment:3 Changed 7 years ago by varikin

I would also suggest github along with google code. I prefer Git over svn, and I know some other do to. Or make it easy to generically add a link to another profile.

comment:4 Changed 7 years ago by ericholscher

I'm really interested in doing this stuff as well. Are we trying to have this data aggregated everywhere, or kind of combining it together in one main site? I'm thinking there is some really cool stuff we could write on top of this, and moving the data around wouldn't be too difficult with simple APIs. OAuth and OpenID make this pretty awesome, and as far as I know (not having implemented it), relatively easy.

This isn't really about Django or a problem w/ the framework, but more of the community. So should there also be a mechanism for this kind of stuff? Or is this the proper place?

comment:5 Changed 7 years ago by bryanveloso

I would also like to be involved about this. I told Jacob and Adrian that I would do whatever takes to get this to happen. Django Plugables would take the place of Google Code in Ross' example, since there is a growing number of repositories being created in places other than Google Code. GitHub for example.

I don't know if this could be done using only OAuth and OpenID, but I really liked Jacob's example of a "super-profile" (on say djangopeople) that would provide a cross-section of any given person in the Django community.

comment:6 Changed 7 years ago by joshuamckenty

From a (relative) newbies' perspective, having a simple way of navigating between the "pseudo-approved" DjangoNoun community sites would be really helpful. Anyone remember the old OSDN banner/bar that used to sit at the top of FreshMeat, Slashdot, etc.?

I'd love to push the use of micro-formats for the relationships between contributers, projects, repositories, etc.

comment:7 Changed 7 years ago by ericholscher

  • Owner changed from nobody to ericholscher
  • Status changed from new to assigned

Going to accept this ticket, and try to get some work done on this. Please e-mail me at eric@… if you are an owner of a site that is interested in helping with this. Also see http://ericholscher.com/blog/2008/nov/6/making-a-django-uber-community/ for a hashing out of my plans.

comment:8 Changed 6 years ago by jacob

  • Resolution set to invalid
  • Status changed from assigned to closed

This isn't really a ticket with Django per se, and now that Eric's started something elsewhere let's close this here.

Note: See TracTickets for help on using tickets.
Back to Top