JerseyOrg on GitHub

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

JerseyOrg on GitHub

Paul Sandoz
Administrator
Hi,

Thanks to Imran's initial work on GitHub i have created the  
organization JerseyOrg:

   http://github.com/JerseyOrg

that contains the repository:

   http://github.com/JerseyOrg/jersey

This is forked from jersey/jersey repository Imran created. I think  
GitHub organizations are a little easier to manage than repositories  
directly associated with user accounts.

We are currently in the process of setting up a Hudson job to sync  
from the SVN to the repository at least once a day.

Paul.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: JerseyOrg on GitHub

Daniel Shaw
Paul,

You can convert a user to an organization relatively easily if you
want to keep /jersey/jersey:
http://storify.com/dshaw/converting-a-github-account-to-an-organization

Daniel Shaw
i: http://dshaw.com
c: http://linkedin.com/in/dshaw



On Tue, Oct 5, 2010 at 10:15 AM, Paul Sandoz <[hidden email]> wrote:

> Hi,
>
> Thanks to Imran's initial work on GitHub i have created the organization
> JerseyOrg:
>
>  http://github.com/JerseyOrg
>
> that contains the repository:
>
>  http://github.com/JerseyOrg/jersey
>
> This is forked from jersey/jersey repository Imran created. I think GitHub
> organizations are a little easier to manage than repositories directly
> associated with user accounts.
>
> We are currently in the process of setting up a Hudson job to sync from the
> SVN to the repository at least once a day.
>
> Paul.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: JerseyOrg on GitHub

Paul Sandoz-2
On Oct 5, 2010, at 5:37 PM, Daniel Shaw wrote:
> Paul,
>
> You can convert a user to an organization relatively easily if you
> want to keep /jersey/jersey:
> http://storify.com/dshaw/converting-a-github-account-to-an- 
> organization
>

Ah, i did not know that, thanks. Oh well... i am inclined to leave  
things as they are and delete the jersey/jersey repository.

What happens to the user account settings and ssh keys if one  
transforms a user into an organization?

The jersey user is actually rather useful in terms of being the  
identity we utilize to push stuff from SVN.

Paul.


> Daniel Shaw
> i: http://dshaw.com
> c: http://linkedin.com/in/dshaw
>
>
>
> On Tue, Oct 5, 2010 at 10:15 AM, Paul Sandoz <[hidden email]>  
> wrote:
>> Hi,
>>
>> Thanks to Imran's initial work on GitHub i have created the  
>> organization
>> JerseyOrg:
>>
>>  http://github.com/JerseyOrg
>>
>> that contains the repository:
>>
>>  http://github.com/JerseyOrg/jersey
>>
>> This is forked from jersey/jersey repository Imran created. I think  
>> GitHub
>> organizations are a little easier to manage than repositories  
>> directly
>> associated with user accounts.
>>
>> We are currently in the process of setting up a Hudson job to sync  
>> from the
>> SVN to the repository at least once a day.
>>
>> Paul.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: JerseyOrg on GitHub

Daniel Shaw
The organization just becomes a container and the organization members
do all the work (with their ssh keys).
/jersey/jersey/ would be the idiomatic url for the project and I'd be
concerned that github users will fork that source rather than
/jerseyorg/jersey/, or more likely, create forks of both.

If you'd rather not use PaulSandoz, you could always create an account
dedicated to Hudson push task with its own ssh keys. Perhaps
"JerseyBot" or "JerseyButler". You might just be able to rename the
accounts, renaming "jersey" to "jersey${cleverNameOfChoice}" and then
changing "jerseyorg" to "jersey", but I'd ping Rick Olson (
@technoweenie ) to make sure first.

Daniel Shaw
i: http://dshaw.com
c: http://linkedin.com/in/dshaw


On Tue, Oct 5, 2010 at 11:59 AM, Paul Sandoz <[hidden email]> wrote:

> On Oct 5, 2010, at 5:37 PM, Daniel Shaw wrote:
>>
>> Paul,
>>
>> You can convert a user to an organization relatively easily if you
>> want to keep /jersey/jersey:
>> http://storify.com/dshaw/converting-a-github-account-to-an-organization
>>
>
> Ah, i did not know that, thanks. Oh well... i am inclined to leave things as
> they are and delete the jersey/jersey repository.
>
> What happens to the user account settings and ssh keys if one transforms a
> user into an organization?
>
> The jersey user is actually rather useful in terms of being the identity we
> utilize to push stuff from SVN.
>
> Paul.
>
>
>> Daniel Shaw
>> i: http://dshaw.com
>> c: http://linkedin.com/in/dshaw
>>
>>
>>
>> On Tue, Oct 5, 2010 at 10:15 AM, Paul Sandoz <[hidden email]> wrote:
>>>
>>> Hi,
>>>
>>> Thanks to Imran's initial work on GitHub i have created the organization
>>> JerseyOrg:
>>>
>>>  http://github.com/JerseyOrg
>>>
>>> that contains the repository:
>>>
>>>  http://github.com/JerseyOrg/jersey
>>>
>>> This is forked from jersey/jersey repository Imran created. I think
>>> GitHub
>>> organizations are a little easier to manage than repositories directly
>>> associated with user accounts.
>>>
>>> We are currently in the process of setting up a Hudson job to sync from
>>> the
>>> SVN to the repository at least once a day.
>>>
>>> Paul.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Reorganized <was> Re: [Jersey] JerseyOrg on GitHub

Paul Sandoz-2
Hi,

I re-organized things as you suggest so the organization is:

   http://github.com/jersey

with the repository:

   http://github.com/jersey/jersey

and the followers are retained. I deleted JerseyOrg so there is only  
one location.

A jerseyrobot account was created for automated pushes.

Thanks,
Paul.

On Oct 5, 2010, at 7:15 PM, Daniel Shaw wrote:

> The organization just becomes a container and the organization members
> do all the work (with their ssh keys).
> /jersey/jersey/ would be the idiomatic url for the project and I'd be
> concerned that github users will fork that source rather than
> /jerseyorg/jersey/, or more likely, create forks of both.
>
> If you'd rather not use PaulSandoz, you could always create an account
> dedicated to Hudson push task with its own ssh keys. Perhaps
> "JerseyBot" or "JerseyButler". You might just be able to rename the
> accounts, renaming "jersey" to "jersey${cleverNameOfChoice}" and then
> changing "jerseyorg" to "jersey", but I'd ping Rick Olson (
> @technoweenie ) to make sure first.
>
> Daniel Shaw
> i: http://dshaw.com
> c: http://linkedin.com/in/dshaw
>
>
> On Tue, Oct 5, 2010 at 11:59 AM, Paul Sandoz  
> <[hidden email]> wrote:
>> On Oct 5, 2010, at 5:37 PM, Daniel Shaw wrote:
>>>
>>> Paul,
>>>
>>> You can convert a user to an organization relatively easily if you
>>> want to keep /jersey/jersey:
>>> http://storify.com/dshaw/converting-a-github-account-to-an-organization
>>>
>>
>> Ah, i did not know that, thanks. Oh well... i am inclined to leave  
>> things as
>> they are and delete the jersey/jersey repository.
>>
>> What happens to the user account settings and ssh keys if one  
>> transforms a
>> user into an organization?
>>
>> The jersey user is actually rather useful in terms of being the  
>> identity we
>> utilize to push stuff from SVN.
>>
>> Paul.
>>
>>
>>> Daniel Shaw
>>> i: http://dshaw.com
>>> c: http://linkedin.com/in/dshaw
>>>
>>>
>>>
>>> On Tue, Oct 5, 2010 at 10:15 AM, Paul Sandoz <[hidden email]>  
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Thanks to Imran's initial work on GitHub i have created the  
>>>> organization
>>>> JerseyOrg:
>>>>
>>>>  http://github.com/JerseyOrg
>>>>
>>>> that contains the repository:
>>>>
>>>>  http://github.com/JerseyOrg/jersey
>>>>
>>>> This is forked from jersey/jersey repository Imran created. I think
>>>> GitHub
>>>> organizations are a little easier to manage than repositories  
>>>> directly
>>>> associated with user accounts.
>>>>
>>>> We are currently in the process of setting up a Hudson job to  
>>>> sync from
>>>> the
>>>> SVN to the repository at least once a day.
>>>>
>>>> Paul.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]