Move Parapara animation git repository to Mozilla's github

RESOLVED FIXED

Status

RESOLVED FIXED
7 years ago
6 days ago

People

(Reporter: birtles, Assigned: wenzel)

Tracking

Details

(Reporter)

Description

7 years ago
Mozilla Japan have developed the Parapara Animation tool.

  http://parapara.mozlabs.jp/
  http://brian.sol1.net/svg/2012/01/27/parapara-animation/

At the recent DML2012 event there was significant interest in this tool. Many people want to use this tool around the world. Also the Popcorn team want to incorporate it into the Popcorn maker.

However, its source currently lives in my github account:

  https://github.com/birtles/parapara

It seems more appropriate that it live under the mozilla github account.

Can we move it across? What are the requirements for doing so?

For example, I don't think we have any clear license statement attachment to the source yet, so perhaps we need to add that first?
Not IT, re-assigning.
Assignee: server-ops → nobody
Component: Server Operations → Webdev
QA Contact: phong → webdev
(Assignee)

Comment 2

7 years ago
(In reply to Brian Birtles (:birtles) from comment #0)
> It seems more appropriate that it live under the mozilla github account.
> 
> Can we move it across? What are the requirements for doing so?

Give me the github usernames of people you want to allow accessing this repository. 

After I add a group for you, I think you can then move the repo to Mozilla. Or you can make me an admin for this repository on your account and I'll move it for you.

> For example, I don't think we have any clear license statement attachment to
> the source yet, so perhaps we need to add that first?

That's a good idea, please do.
(Assignee)

Updated

7 years ago
Assignee: nobody → fwenzel
(Assignee)

Comment 3

7 years ago
Also, can you add some information information as to what this project is to your README, as well as the github tag line (currently: パラパラアニメーションエデイタ)? A sentence or two is good.
(Assignee)

Updated

7 years ago
Assignee: fwenzel → birtles
(Reporter)

Comment 4

7 years ago
(In reply to Fred Wenzel [:wenzel] from comment #2)
> (In reply to Brian Birtles (:birtles) from comment #0)
> > It seems more appropriate that it live under the mozilla github account.
> > 
> > Can we move it across? What are the requirements for doing so?
> 
> Give me the github usernames of people you want to allow accessing this
> repository. 

Sorry for the delay! (I forgot I stopped getting mail notifications when I am the bug reporter).

The usernames are:
birtles
dadaa
moccow

> After I add a group for you, I think you can then move the repo to Mozilla.
> Or you can make me an admin for this repository on your account and I'll
> move it for you.

I'm just going to hold off for a moment because I think we might want to split the repository into two first but I need to talk to the other developer first.

> > For example, I don't think we have any clear license statement attachment to
> > the source yet, so perhaps we need to add that first?
> 
> That's a good idea, please do.

Ok, will do (but this will take a little time).

(In reply to Fred Wenzel [:wenzel] from comment #3)
> Also, can you add some information information as to what this project is to
> your README, as well as the github tag line (currently: パラパラアニメーションエデイタ)? A
> sentence or two is good.

Done.
(Reporter)

Comment 5

7 years ago
(In reply to Brian Birtles (:birtles) from comment #4)
> > Give me the github usernames of people you want to allow accessing this
> > repository. 
> 
> ...
> 
> The usernames are:
> birtles
> dadaa
> moccow

Do these people need to have signed the Committer's Agreement? I (birtles) have, but I'm not sure about the others. Or is that only for hg?
(Assignee)

Comment 6

7 years ago
It's not technically a requirement for the github repositories, but I think generally code contributors to Mozilla should sign a Committer's Agreement, yes.
(Reporter)

Comment 7

7 years ago
Ok, I've split the repository into two and one of the repositories is nearly ready to move (just waiting on approval to re-license one code snippet as MPL 2.0).

I'm happy to do the move (I'm thinking of, rather than doing a fork, creating a new repo on mozilla and then copying the history across so that the one on mozilla becomes the "master" so to speak--i.e. the place everyone will fork from in future).

I guess we will want two repos under the mozilla account:

  parapara-workshop
  parapara-editor

For the usernames, just the following two should be sufficient for now:

  birtles
  dadaa
(Assignee)

Comment 8

7 years ago
(In reply to Brian Birtles (:birtles) from comment #7)
> I'm happy to do the move (I'm thinking of, rather than doing a fork,
> creating a new repo on mozilla and then copying the history across so that
> the one on mozilla becomes the "master" so to speak--i.e. the place everyone
> will fork from in future).

You can do that, yes, or you go into "admin" on your own repository and move it to into mozilla's space. Then you can fork it again into your own space. (You'll lose commit access to the "donated" repo for a short time until I fix the groups).

> I guess we will want two repos under the mozilla account:
> 
>   parapara-workshop
>   parapara-editor
> 
> For the usernames, just the following two should be sufficient for now:
> 
>   birtles
>   dadaa

Right on. I created a group for you.
(Reporter)

Comment 9

7 years ago
(In reply to Fred Wenzel [:wenzel] from comment #8)
> (In reply to Brian Birtles (:birtles) from comment #7)
> > I'm happy to do the move (I'm thinking of, rather than doing a fork,
> > creating a new repo on mozilla and then copying the history across so that
> > the one on mozilla becomes the "master" so to speak--i.e. the place everyone
> > will fork from in future).
> 
> You can do that, yes, or you go into "admin" on your own repository and move
> it to into mozilla's space. Then you can fork it again into your own space.
> (You'll lose commit access to the "donated" repo for a short time until I
> fix the groups).

Oh, I didn't know you could do that! That's better. I'll try to coordinate with you on IRC so we can minimise that window.

> Right on. I created a group for you.

Great, thanks Fred!
(Reporter)

Comment 10

7 years ago
(In reply to Fred Wenzel [:wenzel] from comment #8)
> You can do that, yes, or you go into "admin" on your own repository and move
> it to into mozilla's space. Then you can fork it again into your own space.
> (You'll lose commit access to the "donated" repo for a short time until I
> fix the groups).

Ok, I transferred the repositories, 'parapara' and 'parapara-editor' to mozilla. Please add birtles and dadaa as admins of the repo (or whatever it is you do!)

Also, if possible, can you rename 'parapara' to 'parapara-workshop'? If it's not possible, it's no big deal.

Thanks!
(Assignee)

Comment 11

7 years ago
Done (both the rename, and adding your group as admins of those two repos). moccow is member of that group too, or did you not want that? Let me know.

Closing for now :) Have fun!
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Assignee)

Updated

7 years ago
Assignee: birtles → fwenzel
(Reporter)

Comment 12

7 years ago
(In reply to Fred Wenzel [:wenzel] from comment #11)
> Done (both the rename, and adding your group as admins of those two repos).
> moccow is member of that group too, or did you not want that? Let me know.
> 
> Closing for now :) Have fun!

Thanks Fred, that's great!

Updated

6 days ago
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.