[git] open an "admin" link doesn't works

older
Re: [boost] [Boost-users] [1.55.0]...

Vicente J. Botet Escriba

30 Oct 2013 30 Oct '13

8:08 p.m.

Hi, I tried to gain write access to a particular Boost library but the link *open an "admin"* issue https://github.com/boostorg/admin/issues in https://svn.boost.org/trac/boost/wiki/ModAdmin . doesn't works for me. Could someone help me? Vicente

Show replies by date

Daniel Pfeifer

30 Oct 30 Oct

9:32 p.m.

2013/10/30 Vicente J. Botet Escriba :

...

Hi, I tried to gain write access to a particular Boost library but the link *open an "admin"* issue https://github.com/boostorg/admin/issues in https://svn.boost.org/trac/boost/wiki/ModAdmin .

doesn't works for me.

Could someone help me?

The repository boostorg/admin did not exist. I created both the repository and the team as described at that page. Cheers, Daniel

Vicente J. Botet Escriba

11:18 p.m.

Le 30/10/13 22:32, Daniel Pfeifer a écrit :

...

2013/10/30 Vicente J. Botet Escriba :

...
Hi, I tried to gain write access to a particular Boost library but the link *open an "admin"* issue https://github.com/boostorg/admin/issues in https://svn.boost.org/trac/boost/wiki/ModAdmin .

doesn't works for me.

Could someone help me? The repository boostorg/admin did not exist. I created both the repository and the team as described at that page.

Maybe I misunderstood this page. I would like to have access to the libraries I maintain. The message in tis page is: "To gain write access to a particular Boost library, open an "admin" issue https://github.com/boostorg/admin/issues. " Vicente

Ahmed Charles

31 Oct 31 Oct

3:58 a.m.

...

Le 30/10/13 22:32, Daniel Pfeifer a écrit :

...
2013/10/30 Vicente J. Botet Escriba :

...
Hi, I tried to gain write access to a particular Boost library but the link *open an "admin"* issue https://github.com/boostorg/admin/issues in https://svn.boost.org/trac/boost/wiki/ModAdmin .

doesn't works for me.

Could someone help me? The repository boostorg/admin did not exist. I created both the repository and the team as described at that page.

Maybe I misunderstood this page. I would like to have access to the libraries I maintain.

The message in tis page is: "To gain write access to a particular Boost library, open an "admin" issue https://github.com/boostorg/admin/issues. "

1. Go to https://github.com/boostorg/admin/issues 2. Log into github (create an account if you don't have one). 3. Click on the green 'New Issue' button in the upper right (it's below the 'watch', 'star' and 'fork' buttons). 4. Type in the title and put a comment (requesting access to the libraries you own and saying who you are). 5. Click the green 'Submit new issue' button below the comment box. (I'm assuming this is sufficient, but since I don't own a library, I didn't actually submit an issue.)

Daniel Pfeifer

5:16 a.m.

2013/10/31 Vicente J. Botet Escriba :

...

Le 30/10/13 22:32, Daniel Pfeifer a écrit :

...
2013/10/30 Vicente J. Botet Escriba :

...
Hi, I tried to gain write access to a particular Boost library but the link *open an "admin"* issue https://github.com/boostorg/admin/issues in https://svn.boost.org/trac/boost/wiki/ModAdmin .

doesn't works for me.

Could someone help me?

The repository boostorg/admin did not exist. I created both the repository and the team as described at that page.

Maybe I misunderstood this page. I would like to have access to the libraries I maintain.

The message in tis page is: "To gain write access to a particular Boost library, open an "admin" issue https://github.com/boostorg/admin/issues. "

Yes, I think you understood that correctly. The link was broken. It is fixed now.

Daniel Pfeifer

5:58 a.m.

Beman, Dave, Eric, Should we attend admin issues now or wait until after the final switchover to git? Advantage of starting now: Authors can experiment with their libraries inside boostorg. Disclaimer: They even can push their changes, but need to keep in mind that Boost2Git continuously recreates the whole repository structure based on the SVN contents. Advantage of doing it when Boost2Git job is switched off: Avoid surprises that commits get deleted/overridden. -- Daniel 2013/10/31 Daniel Pfeifer :

...

2013/10/31 Vicente J. Botet Escriba :

...
Le 30/10/13 22:32, Daniel Pfeifer a écrit :

...
2013/10/30 Vicente J. Botet Escriba :

...
Hi, I tried to gain write access to a particular Boost library but the link *open an "admin"* issue https://github.com/boostorg/admin/issues in https://svn.boost.org/trac/boost/wiki/ModAdmin .

doesn't works for me.

Could someone help me?

The repository boostorg/admin did not exist. I created both the repository and the team as described at that page.

Maybe I misunderstood this page. I would like to have access to the libraries I maintain.

The message in tis page is: "To gain write access to a particular Boost library, open an "admin" issue https://github.com/boostorg/admin/issues. "

Yes, I think you understood that correctly. The link was broken. It is fixed now.

Eric Niebler

6:03 p.m.

On 10/30/2013 10:58 PM, Daniel Pfeifer wrote:

...

Beman, Dave, Eric,

Should we attend admin issues now or wait until after the final switchover to git?

Advantage of starting now: Authors can experiment with their libraries inside boostorg. Disclaimer: They even can push their changes, but need to keep in mind that Boost2Git continuously recreates the whole repository structure based on the SVN contents.

Advantage of doing it when Boost2Git job is switched off: Avoid surprises that commits get deleted/overridden.

My $0.02: Couldn't hurt to grant folks access when they ask for it. When we close the admin issues, we should make it clear that any changes made to the repos before the switch-over will be overwritten. -- Eric Niebler Boost.org http://www.boost.org

Beman Dawes

1 Nov 1 Nov

5:50 p.m.

On Thu, Oct 31, 2013 at 2:03 PM, Eric Niebler wrote:

...

On 10/30/2013 10:58 PM, Daniel Pfeifer wrote:

...
Beman, Dave, Eric,

Should we attend admin issues now or wait until after the final switchover to git?

Advantage of starting now: Authors can experiment with their libraries inside boostorg. Disclaimer: They even can push their changes, but need to keep in mind that Boost2Git continuously recreates the whole repository structure based on the SVN contents.

Advantage of doing it when Boost2Git job is switched off: Avoid surprises that commits get deleted/overridden.

My $0.02: Couldn't hurt to grant folks access when they ask for it. When we close the admin issues, we should make it clear that any changes made to the repos before the switch-over will be overwritten.

I don't see how we can test Boost2Git without letting authors experiment with their libraries, including pushing to the public repo. An attempt to push was how the https vs git protocol issue came up, and I expect more testing by more developers to raise more issues. Remember, some developers have very little experience with git, and others have little or no experience with sub-modules. Testing will will help bring people up to speed. We can limit granting write access to those who acknowledge that they understand that changes will be overwritten until Boost2Git job is switched off. --Beman

Rene Rivera

8:47 p.m.

On Fri, Nov 1, 2013 at 12:50 PM, Beman Dawes wrote:

...

On Thu, Oct 31, 2013 at 2:03 PM, Eric Niebler wrote:

...
On 10/30/2013 10:58 PM, Daniel Pfeifer wrote:

...
Beman, Dave, Eric,

Should we attend admin issues now or wait until after the final switchover to git?

Advantage of starting now: Authors can experiment with their libraries inside boostorg. Disclaimer: They even can push their changes, but need to keep in mind that Boost2Git continuously recreates the whole repository structure based on the SVN contents.

Advantage of doing it when Boost2Git job is switched off: Avoid surprises that commits get deleted/overridden.

My $0.02: Couldn't hurt to grant folks access when they ask for it. When we close the admin issues, we should make it clear that any changes made to the repos before the switch-over will be overwritten.

I don't see how we can test Boost2Git without letting authors experiment with their libraries, including pushing to the public repo.

An attempt to push was how the https vs git protocol issue came up, and I expect more testing by more developers to raise more issues.

Remember, some developers have very little experience with git, and others have little or no experience with sub-modules. Testing will will help bring people up to speed.

We can limit granting write access to those who acknowledge that they understand that changes will be overwritten until Boost2Git job is switched off.

I would agree with that. And I have a suggestion.. There are a number of developers, myself included, who already have their libraries in github (and at least in my case already in the appropriate structure). It would seem that giving the authors with those libraries permission to directly push their existing repos to the Boost canonical ones would be the most beneficial way to test. Especially since it would remove the git->svn->git translation that is already going on. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

Dave Abrahams

3:54 a.m.

I vote for waiting. Sent from my illudium Q-36 explosive space modulator

...

On Oct 30, 2013, at 10:58 PM, Daniel Pfeifer wrote:

Beman, Dave, Eric,

Should we attend admin issues now or wait until after the final switchover to git?

Advantage of starting now: Authors can experiment with their libraries inside boostorg. Disclaimer: They even can push their changes, but need to keep in mind that Boost2Git continuously recreates the whole repository structure based on the SVN contents.

Advantage of doing it when Boost2Git job is switched off: Avoid surprises that commits get deleted/overridden.

-- Daniel

2013/10/31 Daniel Pfeifer :

...
2013/10/31 Vicente J. Botet Escriba :

...
Le 30/10/13 22:32, Daniel Pfeifer a écrit :

...
2013/10/30 Vicente J. Botet Escriba :

...
Hi, I tried to gain write access to a particular Boost library but the link *open an "admin"* issue https://github.com/boostorg/admin/issues in https://svn.boost.org/trac/boost/wiki/ModAdmin .

doesn't works for me.

Could someone help me?

The repository boostorg/admin did not exist. I created both the repository and the team as described at that page.

Maybe I misunderstood this page. I would like to have access to the libraries I maintain.

The message in tis page is: "To gain write access to a particular Boost library, open an "admin" issue https://github.com/boostorg/admin/issues. "

Yes, I think you understood that correctly. The link was broken. It is fixed now.

Vladimir Prus

31 Oct 31 Oct

1:14 p.m.

On 31.10.2013 00:08, Vicente J. Botet Escriba wrote:

...

Hi, I tried to gain write access to a particular Boost library but the link *open an "admin"* issue https://github.com/boostorg/admin/issues in https://svn.boost.org/trac/boost/wiki/ModAdmin .

Maybe I misunderstand this page, but would not it be better to give each component maintainers admin access to corresponding git repository, so that further access rights can be given without involving boost admins? - Volodya

4027

Age (days ago)

4029

Last active (days ago)

List overview

Download

10 comments

8 participants

participants (8)

Ahmed Charles
Beman Dawes
Daniel Pfeifer
Dave Abrahams
Eric Niebler
Rene Rivera
Vicente J. Botet Escriba
Vladimir Prus