Closed Bug 772546 Opened 8 years ago Closed 8 years ago

Move primary TBPL development out of a user repo and into https://hg.mozilla.org/webtools/tbpl/

Categories

(Tree Management Graveyard :: TBPL, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

Attachments

(1 file)

TBPL development is currently all done in http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/

jhammel asked if there were any plans to move this to a proper repo, so filing this to seek consensus.

Are we all happy to do this & if so, under which of the following would people prefer?
https://hg.mozilla.org/automation/
https://hg.mozilla.org/webtools/
https://hg.mozilla.org/build/

Each contains a few items that seem related enough to TBPL to warrant it's inclusion there, so I don't really know which is best.

Also: /tinderboxpushlog/ or /tbpl/ ?

CCing anyone who has committed to the repo recently.
Kibitzing, but since people aren't going to be typing these URLs very often (at least not if they're doing it right and using shell history, awesomebar, etc.), using the full name seems preferable to me.

Oh, for what it's worth,

http://yellow.bikeshed.com/
> Are we all happy to do this & if so, under which of the following would people prefer?

I like /webtools because it matches the Bugzilla product; helps me remember.

> Also: /tinderboxpushlog/ or /tbpl/ ?

I slightly prefer the shorter version, but either is fine.
Is there a real benefit in doing this?  I think quite a few people know the location of the old repo and this would just be confusing to them.
(In reply to Jeff Walden [:Waldo] (busy, try to prefer other reviewers if possible) from comment #1)
> Kibitzing, but since people aren't going to be typing these URLs very often
> (at least not if they're doing it right and using shell history, awesomebar,
> etc.), using the full name seems preferable to me.
> 
> Oh, for what it's worth,
> 
> http://yellow.bikeshed.com/

Disagree. http://hotpink.bikeshed.com/

'tbpl' is preferable to 'tinderboxpushlog' because tbpl is a floating acronym in need of a home -- it no longer has anything to do with tinderbox. And although it should really be renamed to something more meaningful, for now I will just silently think TaterBotPoopList to myself.
(In reply to Ehsan Akhgari [:ehsan] from comment #3)
> Is there a real benefit in doing this?  I think quite a few people know the
> location of the old repo and this would just be confusing to them.

One benefit is that it can't get accidentally deleted (eg, mstange doing it by accident, or his account getting removed for some reason).

I would suggest that hg.m.o/build is *not* the right place for, but anywhere else should be fine.
(In reply to Steve Fink [:sfink] from comment #4)
> > Oh, for what it's worth,
> > 
> > http://yellow.bikeshed.com/
> 
> Disagree. http://hotpink.bikeshed.com/

Chastened, enlightened, presumed objection withdrawn.

Unless you can backronym your way to success, I'm pretty sure TBPL is always going to expand to tinderboxpushlog.  Or you could rename it to avoid the matter if you wanted.  (I feel like I should mention http://hotpink.bikeshed.com/ now, although I have *no* *idea* *why* I might be thinking that.)
Unless there are any significant objections (and to save any more bikeshedding) I propose we:
* Move the repo to https://hg.mozilla.org/webtools/tbpl/
  -> Matches the bugzilla component
  -> 'tbpl' matches the domain name and gives future opportunity for backronyming
* 301 redirect http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/* to https://hg.mozilla.org/webtools/tbpl/*
* Check that IT have updated the 'tbpl-prod update' script
* Update all TBPL wiki pages/in-tree docs
* Post in dev.platform after the move, advising as to the new location
* Email anyone who has committed to the repo in the last year or two, with the same content as the dev.platform post

Sound ok?
Does hg know how to handle 301 redirects?
(In reply to Ehsan Akhgari [:ehsan] from comment #8)
> Does hg know how to handle 301 redirects?

No idea; Google hasn't turned up anything.

So few people hack on tbpl, I don't think we need to worry too much (given the steps in comment 7).
(In reply to comment #9)
> (In reply to Ehsan Akhgari [:ehsan] from comment #8)
> > Does hg know how to handle 301 redirects?
> 
> No idea; Google hasn't turned up anything.

(We have the source code.  ;-)
(Note that I don't really care that much about this.)
Blocks: 789495
mstange, seeing as it is your user repo under discussion, any objections? :-)
Summary: Move primary TBPL development out of a user repo and under hg.m.o/{automation,webtools,build} → Move primary TBPL development out of a user repo and into https://hg.mozilla.org/webtools/tbpl/
No objections at all. Take it wherever it makes sense. :-)
Depends on: 807008
For clarity / more appropriate component, have filed bug 807008 for the mechanics of the move; this bug will track the updating of docs, posting to newsgroups & emailing recent contributors.
Assignee: nobody → bmo
Status: NEW → ASSIGNED
Email sent to the ~35 people who have commits in the repo.
README.txt in the repo needs to be updated, too.
Attached patch Update READMEsSplinter Review
(In reply to Ed Morley [UTC+0; email:edmorley@moco] from comment #18)
> Created attachment 692018 [details] [diff] [review]
> Update READMEs

https://hg.mozilla.org/webtools/tbpl/rev/c1575ac02e10
Posted to dev.platform:
https://groups.google.com/d/msg/mozilla.dev.platform/ZmyDuZ3ojoE/KdYdM_i0eQAJ

All done here now :-)
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.