You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-dev@apache.org by sebb <se...@gmail.com> on 2017/03/09 11:08:57 UTC
Re: svn commit: r1786095 - /infrastructure/site/trunk/content/dev/infra-contact.mdtext
On 9 March 2017 at 03:26, <gs...@apache.org> wrote:
> Author: gstein
> Date: Thu Mar 9 03:26:40 2017
> New Revision: 1786095
>
> URL: http://svn.apache.org/viewvc?rev=1786095&view=rev
> Log:
> * svn2git is now self-serve. add some HOWTO notes.
> * adjust contact address for Infra
>
> Modified:
> infrastructure/site/trunk/content/dev/infra-contact.mdtext
>
> Modified: infrastructure/site/trunk/content/dev/infra-contact.mdtext
> URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/dev/infra-contact.mdtext?rev=1786095&r1=1786094&r2=1786095&view=diff
> ==============================================================================
> --- infrastructure/site/trunk/content/dev/infra-contact.mdtext (original)
> +++ infrastructure/site/trunk/content/dev/infra-contact.mdtext Thu Mar 9 03:26:40 2017
> @@ -58,7 +58,7 @@ a ticket, or a custom webapp. Note that
> | <!-- TODO: status.a.o is sorted by physical name; would be useful to explain that asomewhere, but not here in the bulleted list --> anyone | report that a **service is down** (and <http://status.apache.org/> doesn't show that) | [Hipchat](http://infra.chat/) channel | Hipchat preferred, email to `users@infra.apache.org` is an acceptable alternative. The [infrabot twitter feed](http://twitter.com/infrabot/) may contain information about current outages and maintenances. |
> | a **newly-invited committer** | ask a question about your committership | private@${project}.apache.org, for the project that invited you to become a committer | |
> | a committer | regain **access to your account**; [resetting your password](https://id.apache.org/reset/enter) didn't work | See ["Regaining account access"](#regain-account), below. | If commits fail, double-check that you are using https:// (not http://). |
> -| a **supplier** (you donate or sell hardware or services to Apache) | anything | infrastructure-private@apache.org | Passwords should be [encrypted](https://home.apache.org/keys/group/infrastructure-root.asc) or sent by other means (to be coordinated) |
> +| a **supplier** (you donate or sell hardware or services to Apache) | anything | private@infra.apache.org | Passwords should be [encrypted](https://home.apache.org/keys/group/infrastructure-root.asc) or sent by other means (to be coordinated) |
> | **submitted an ICLA** in the past | change your contact details of record | secretary@apache.org | Fax or snail mail are possible too; see <https://www.apache.org/foundation/contact> |
> | prospective official download mirror | **request being listed** as an official download **mirror** | see [the "new mirror" documentation](/info/how-to-mirror) | Please email `mirrors@apache.org` if you have any questions. |
> | existing official download mirror | ask a question **concerning your mirror** | mirrors@apache.org | Questions not suitable for public discussion may be sent to `apmirror@apache.org` (currently an alias with limited distribution). |
> @@ -72,7 +72,7 @@ a ticket, or a custom webapp. Note that
> | a committer or PMC | add/remove mailing list **moderators** | email apmail@apache.org | Feel free to follow up via [Hipchat](http://infra.chat/) channel or file a Jira ticket if no reply after 48 hours or so |
> | a committer or PMC | change **Jenkins** (nee Hudson) build settings | email builds@apache.org | Some tasks can be done by project members having [`hudson-jobadmin` karma](http://wiki.apache.org/general/Jenkins); ask your dev@ list |
> | a PMC | request Infrastructure to **do** something | [create a JIRA ticket](https://issues.apache.org/jira/browse/INFRA) | See ["On Requests"](#requesting-action) and ["Providing needed information"](#what-we-need-to-know), below. |
> -| an **Officer** of the ASF | ask an organizational question (as opposed to technical) | VP Infrastructure, or infrastructure-private@apache.org | The target audience for this item is the Apache Board of Directors, the VP Fundraising, etc. |
> +| an **Officer** of the ASF | ask an organizational question (as opposed to technical) | VP Infrastructure, or private@infra.apache.org | The target audience for this item is the Apache Board of Directors, the VP Fundraising, etc. |
> | posted to an Apache mailing list | edit the **mail archives** | [Public Forum Archive Policy](/foundation/public-archives) | Virtually all requests are denied. |
> | anyone | **discuss** something publicly with the Team | infrastructure-dev@apache.org | Archives: <http://mail-archives.apache.org/mod_mbox/www-infrastructure-dev/> |
> | anyone | ask Infra a **question** | users@infra.apache.org | The infra@ mailing list should be considered a semipublic list as many Apache committers --- not only Team members --- are subscribed. |
> @@ -267,7 +267,7 @@ involving infra at all.
> | Create a **confluence wiki** | wiki name, destination for commit mails, and confluence usernames of two+ community members - volunteer space admins | |
> | Set up your project on [**Review Board**](https://reviews.apache.org/) | Project name, which svn/git branches to support | |
> | Create a **JIRA project** | Key name (e.g., `INFRA`), JIRA usernames of 1-2 project members - volunteer project admins, mailing list address to which JIRA notifications should go | The INFRA JIRA you will file **must** use the "[New JIRA Project](https://issues.apache.org/jira/servicedesk/customer/portal/1/create/6)" issue type. |
> -| Migrate your project's **SVN to Git** | project unix name, project layout, portions of svn tree to leave writable (e.g. ASF CMS site sources) | |
> +| Migrate your project's **SVN to Git** | n/a | Please use [reporeq](https://reporeq.apache.org) to create your intended Git repo(s). Run svn2git locally using this [authors file](https://git-wip-us.apache.org/authors.txt) and push once the conversion result is confirmed. File an INFRA ticket to mark your SVN repository readonly. Optionally, file a ticket to temporarily disable commit emails for when you push your converted clone. |
Would it not be safer to mark SVN read-only *before* doing the conversion?
[If users want to experiment with svn2git first they can use a
temporary local git repo.]
> | Grant a committer **SSH access to a `puppet`-ed VM** | committer's availid (username), VM hostname | The committer *must* [add his key to id.a.o](freebsd-jails#grant-ssh-access) beforehand. |
> | Grant a committer **root access to a `puppet`-ed VM** | committer's availid (username), VM hostname | The committer *must* already have SSH access, and *must* [set up OPIE](freebsd-jails#opie) beforehand. |
>
> @@ -314,7 +314,7 @@ archive.apache.org. **This is only inte
> that must be handled at once, even if that means waking people up in the middle
> of the night or having them miss their flight.**
>
> -Normally, pinging `#asfinfra` or emailing `root@` or `infrastructure-private@`
> +Normally, pinging `#asfinfra` or emailing `root@` or `private@infra`
> suffices. Pinging people privately (via email, Hipchat, or twitter) is generally
> discouraged as then only a single person is aware of a request. . If all of these
> have been exhausted, or are not sufficiently timely, the last resort is to look
>
>
Re: svn commit: r1786095 - /infrastructure/site/trunk/content/dev/infra-contact.mdtext
Posted by Greg Stein <gs...@gmail.com>.
On Thu, Mar 9, 2017 at 5:59 AM, sebb <se...@gmail.com> wrote:
> On 9 March 2017 at 11:20, Greg Stein <gs...@gmail.com> wrote:
>
>...
> > Could an svn commit arrive, while a contributor is working through the
> > conversion process, and verifying its result? Sure. But they can' just
> > re-run their conversion.
>
> They can, if they notice that SVN has been updated.
>
> But if they don't notice, or the commit mail gets delayed or lost and
> they don't recheck the SVN version manually, then the Git repo is
> broken.
>
> This process used to be undertaken by infra staff who should be well
> aware of the potential for lost updates.
>
> The average committer who now has to do the task may not have
> considered such possibilities.
>
> That is why it is safer to mark SVN read-only first.
>
Sure, fair point. I'd like to assume the communities know their stuff, but
you're right that not everybody knows about the edge cases.
"used to be undertaken by the infra staff" is precisely what we're stepping
away from. Infra does not have a unique access/skill in this area. In fact,
it is the community that can best determine whether the conversion outcome
is appropriate. Infra can only run a command, but has no ability to
determine if the result is successful.
>...
> > Your thoughts on wording is most welcome.
>
> I thought I already commented ...
>
> > This is kind of a big change
> > around what Infra will help people with on svn->git. A good description
> of
> > the new position would be welcome!
>
> No idea what you mean by that.
>
Oh, just a simple ask for better words. As you noted, Infra used to do
this. We're looking to PMCs to do that now, so gotta craft text to that
effect. I'm just asking for your to help fix the page.
Cheers,
-g
Re: svn commit: r1786095 - /infrastructure/site/trunk/content/dev/infra-contact.mdtext
Posted by sebb <se...@gmail.com>.
On 9 March 2017 at 11:20, Greg Stein <gs...@gmail.com> wrote:
> On Thu, Mar 9, 2017 at 5:08 AM, sebb <se...@gmail.com> wrote:
>>
>> On 9 March 2017 at 03:26, <gs...@apache.org> wrote:
>> > Author: gstein
>> > Date: Thu Mar 9 03:26:40 2017
>> > New Revision: 1786095
>> >
>> > URL: http://svn.apache.org/viewvc?rev=1786095&view=rev
>> > Log:
>> > * svn2git is now self-serve. add some HOWTO notes.
>> > * adjust contact address for Infra
>> >
>> > Modified:
>> > infrastructure/site/trunk/content/dev/infra-contact.mdtext
>
>>...
>>
>> > +| Migrate your project's **SVN to Git** | n/a | Please use
>> > [reporeq](https://reporeq.apache.org) to create your intended Git repo(s).
>> > Run svn2git locally using this [authors
>> > file](https://git-wip-us.apache.org/authors.txt) and push once the
>> > conversion result is confirmed. File an INFRA ticket to mark your SVN
>> > repository readonly. Optionally, file a ticket to temporarily disable commit
>> > emails for when you push your converted clone. |
>>
>> Would it not be safer to mark SVN read-only *before* doing the conversion?
>>
>> [If users want to experiment with svn2git first they can use a
>> temporary local git repo.]
>
>
> "Safer" ? ... nah. Nothing is getting broken.
>
> Could an svn commit arrive, while a contributor is working through the
> conversion process, and verifying its result? Sure. But they can' just
> re-run their conversion.
They can, if they notice that SVN has been updated.
But if they don't notice, or the commit mail gets delayed or lost and
they don't recheck the SVN version manually, then the Git repo is
broken.
This process used to be undertaken by infra staff who should be well
aware of the potential for lost updates.
The average committer who now has to do the task may not have
considered such possibilities.
That is why it is safer to mark SVN read-only first.
> And yes: the intent is that a PMC/community uses a "temporary local git
> repo". Running through conversion tests on the live new/empty Git repo is
> just... nonsensical.
I did not mean to suggest that the user would push the result of
running svn2git until they were happy with it.
> Your thoughts on wording is most welcome.
I thought I already commented ...
> This is kind of a big change
> around what Infra will help people with on svn->git. A good description of
> the new position would be welcome!
No idea what you mean by that.
> Thx,
> -g
>
Re: svn commit: r1786095 - /infrastructure/site/trunk/content/dev/infra-contact.mdtext
Posted by Greg Stein <gs...@gmail.com>.
On Thu, Mar 9, 2017 at 5:08 AM, sebb <se...@gmail.com> wrote:
> On 9 March 2017 at 03:26, <gs...@apache.org> wrote:
> > Author: gstein
> > Date: Thu Mar 9 03:26:40 2017
> > New Revision: 1786095
> >
> > URL: http://svn.apache.org/viewvc?rev=1786095&view=rev
> > Log:
> > * svn2git is now self-serve. add some HOWTO notes.
> > * adjust contact address for Infra
> >
> > Modified:
> > infrastructure/site/trunk/content/dev/infra-contact.mdtext
>
>...
> > +| Migrate your project's **SVN to Git** | n/a | Please use [reporeq](
> https://reporeq.apache.org) to create your intended Git repo(s). Run
> svn2git locally using this [authors file](https://git-wip-us.
> apache.org/authors.txt) and push once the conversion result is confirmed.
> File an INFRA ticket to mark your SVN repository readonly. Optionally, file
> a ticket to temporarily disable commit emails for when you push your
> converted clone. |
>
> Would it not be safer to mark SVN read-only *before* doing the conversion?
>
> [If users want to experiment with svn2git first they can use a
> temporary local git repo.]
>
"Safer" ? ... nah. Nothing is getting broken.
Could an svn commit arrive, while a contributor is working through the
conversion process, and verifying its result? Sure. But they can' just
re-run their conversion.
And yes: the intent is that a PMC/community uses a "temporary local git
repo". Running through conversion tests on the live new/empty Git repo is
just... nonsensical.
Your thoughts on wording is most welcome. This is kind of a big change
around what Infra will help people with on svn->git. A good description of
the new position would be welcome!
Thx,
-g