Opened 7 years ago

Closed 6 years ago

Last modified 6 years ago

#11250 closed enhancement (fixed)

Move globe git to Tor's git?

Reported by: arma Owned by: isis
Priority: Medium Milestone:
Component: Internal Services/Service - git Version:
Severity: Keywords: globe
Cc: karsten, arma, arlolra, sherief, rndm, wfn, isis, phw, Sebastian Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I notice we are hosting a Globe and quickly making it one of our core services (including with some potential gsoc plans), but its source is still hosted on a proprietary (albeit popular and convenient) platform. Would we like to move it to Tor's git at some point?

Child Tickets

Change History (14)

comment:1 Changed 7 years ago by karsten

We should. And we even had a ticket for this (#10322) which somehow slipped through. rndm, do you have an LDAP account or PGP key signed by one or more Tor people?

comment:2 Changed 6 years ago by isis

Cc: arma arlolra sherief rndm wfn isis added
Component: GlobeService - git
Keywords: globe added
Status: newneeds_information

Did rndm disappear?

There's a person, Syrup-tan, in #tor-dev with some globe patches, and we are both rather confused if those patches should turn into pull requests to rndm's github repo or get merged to some official repo.

Can we make:

repo globe.git
    RW    isis
    R     @all

# (plus whatever gitweb configuration to make it public)

Could we also add RW for whoever else needs it? Maybe karsten or arma, if either of them are willing? Or hopefully some people who are more into Javascript development than me? sherief? arlolra? wfn?

Once that's done, we should push the current codebase from rndm's github repo to git.tpo, and probably move whatever issues lurk on the github tracker to our Trac.

comment:3 in reply to:  2 Changed 6 years ago by arlolra

Cc: phw added

Did rndm disappear?

I believe so.

karsten and phw were making progress with some new devs but that may have stalled,
https://lists.torproject.org/pipermail/tor-dev/2014-September/007469.html

rndm was working a version that didn't require javascript (on the client) that may be the way forward,
https://github.com/makepanic/globe-node

comment:4 Changed 6 years ago by karsten

Yes, rndm disappeared. So sad.

I know of two at least people working on an Atlas/Globe replacement called Navigator. I asked them how things are going a week ago, and they're still actively working on this. We should expect them to put out a first release in the next couple of weeks.

That being said, we shouldn't shut down Globe before we're convinced that Navigator can take over. Making small changes to the deployed Globe sounds like a very reasonable thing to me.

Isis, would you want to maintain Globe in a similar fashion as Philipp maintains Atlas? (He writes and reviews smaller patches to make sure it stays functional, but he doesn't write bigger enhancements.) If so, creating that Git repository sounds good. I'm fine not having RW permissions if you take care of pushing things to the repository. Also, you'll need permissions to deploy Globe, and I'll have to explain the five steps to do that to you.

comment:5 in reply to:  2 Changed 6 years ago by arma

Replying to isis:

Could we also add RW for whoever else needs it? Maybe karsten or arma, if either of them are willing?

I probably shouldn't be pushing to a repo that's in a language I don't know. Also I am a bad bottleneck these days. :)

comment:6 Changed 6 years ago by Sebastian

Cc: Sebastian added

Please come up with a decision and let us know when we should make it so. The git component here is not really for discussion of who should have access to what and why

comment:7 in reply to:  4 ; Changed 6 years ago by isis

Replying to karsten:

We should expect them to put out a first release in the next couple of weeks.

That being said, we shouldn't shut down Globe before we're convinced that Navigator can take over. Making small changes to the deployed Globe sounds like a very reasonable thing to me.

Isis, would you want to maintain Globe in a similar fashion as Philipp maintains Atlas?


Sure, I'll maintain it for a couple months, but I don't want to maintain it long term. I despise Javascript.

What are the five steps to deploy?

comment:8 in reply to:  6 Changed 6 years ago by isis

Owner: changed from rndm to isis
Status: needs_informationaccepted

Replying to Sebastian:

Please come up with a decision and let us know when we should make it so. The git component here is not really for discussion of who should have access to what and why

Please make

repo globe.git
    RW    isis
    R     @all

# (plus whatever gitweb configuration to make it public)

comment:9 Changed 6 years ago by isis

Status: acceptedassigned

Changing Globe tickets to be owned by isis.

comment:10 Changed 6 years ago by Sebastian

Description?

comment:11 in reply to:  10 Changed 6 years ago by isis

Replying to Sebastian:

Description?


JavaScript application to search and view details for Tor relays and bridges.

comment:12 Changed 6 years ago by Sebastian

Resolution: fixed
Status: assignedclosed

[x]

comment:13 Changed 6 years ago by arma

Thanks isis! I just made isis the owner of the globe trac component too.

(I'm sure there's some star trek reference here for when the cute alien thing sticks itself to isis, doesn't really come off easily, and everybody wonders what could go wrong.)

comment:14 in reply to:  7 Changed 6 years ago by karsten

Replying to isis:

Replying to karsten:

We should expect them to put out a first release in the next couple of weeks.

That being said, we shouldn't shut down Globe before we're convinced that Navigator can take over. Making small changes to the deployed Globe sounds like a very reasonable thing to me.

Isis, would you want to maintain Globe in a similar fashion as Philipp maintains Atlas?


Sure, I'll maintain it for a couple months, but I don't want to maintain it long term. I despise Javascript.

Wonderful. Thanks!

What are the five steps to deploy?

I'll deploy what's in master right now and send you the commands I used for that in private email (feel free to clean up these commands and add them to Git). Let's discuss permissions in a separate ticket.

Note: See TracTickets for help on using tickets.