[jira] [Commented] (COMDEV-288) Request "Projects Directory" migration to GIT
[
https://issues.apache.org/jira/browse/COMDEV-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426532#comment-16426532
]
Hervé Boutemy commented on COMDEV-288:
--
FYI, see discussion
https://lists.apache.org/thread.html/3efa0dbbab20417ad0b89961aed49012698f1a2476771164f4b70756@%3Cdev.community.apache.org%3E
> Request "Projects Directory" migration to GIT
> -
>
> Key: COMDEV-288
> URL: https://issues.apache.org/jira/browse/COMDEV-288
> Project: Community Development
> Issue Type: SVN->GIT Migration
> Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> Dear all,
> is it possible for you to plan SVN to GIT migration for "Projects Directory"
> project ?
> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/{color}]
> Thank you,
> Regards.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-287) Projects Directory About. Link broken
[
https://issues.apache.org/jira/browse/COMDEV-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426531#comment-16426531
]
Hervé Boutemy commented on COMDEV-287:
--
oh no, links to Jira components like
https://issues.apache.org/jira/browse/COMDEV/component/${component id} have
been disabled during Jira upgrades
thanks for the report, since I have such links in a lot of locations, not only
on projects.apache.org...
does anybody know if this is a purely removed feature or if it can be enabled?
And is there a recommended new link template to have equivalent pointer to open
issues of a component?
> Projects Directory About. Link broken
> -
>
> Key: COMDEV-287
> URL: https://issues.apache.org/jira/browse/COMDEV-287
> Project: Community Development
> Issue Type: Bug
> Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> On "About" Projects Directory page : [https://projects.apache.org/about.html]
> Link "{color:#0066cc}COMDEV Jira issue in the "Projects" component{color}" is
> broken.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT
yes, they are not mergeable at Git level (since it will be read-only)
but they are mergeable at svn level, the same way that we merge patches
attached to Jira issues (when people take time to create such patches and
attach, which nowadays does not happen much): every GitHub PR can be seen as a
patch or diff (I don't remember if one is best suited than the other)
example:
PR: https://github.com/apache/maven-wagon/pull/47
patch: https://github.com/apache/maven-wagon/pull/47.patch
diff: https://github.com/apache/maven-wagon/pull/47.diff
not as convenient for the Comdev team as if we fully switch to Git, but like
explained to Sebb, svn2git mirror is a necessary first step that lowers impact
before thinking about doing next steps or not.
For the team, it really behaves as if we totally stay with svn: this Git
mirror is just a new source of patches that are easier for contributors to
create and submit (through Pull Requests)
But for sure, fully switching to Git to get Git-mergeable Pull Requests for
the team can be useful in the future: we'll see that later, seeing also other
side impacts (on hosts for example)
Regards,
Hervé
Le jeudi 5 avril 2018, 03:00:40 CEST Maxim Solodovnik a écrit :
> The PRs created for read-only hit are not "mergeable"
>
> WBR, Maxim
> (from mobile, sorry for the typos)
>
> On Thu, Apr 5, 2018, 05:34 Hervé BOUTEMY wrote:
> > there is a little misunderstanding: I'm not talking about fully switching
> > from
> > svn to git
> > I'm talking about keeping svn as canonical repository but adding a
> > read-only
> > git mirror like done on many svn repositories [1]
> >
> > This does not change anything to the host configuration, but adds a GitHub
> > mirror for external people to contribute through GitHub Pull Requests,
> > which
> > are so much easier to submit than svn patch attached to a Jira issue: this
> > will give a chance to get more contributions.
> >
> > Later on, we can decide to switch to Git (with gitwcsub acting like
> > currently
> > svnwcsub), but that will be another choice to do in another time.
> >
> > Regards,
> >
> > Hervé
> >
> > [1] http://git.apache.org/
> >
> > Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> > > On 4 April 2018 at 07:09, Hervé BOUTEMY wrote:
> > > > What about creating a Git/GitHub svn2git mirror for
> >
> > projects.apache.org?
> >
> > > > This would be our first Git repo for community/comdev: I don't know
> >
> > which
> >
> > > > prefix we should use...
> > > >
> > > > Any objection?
> > >
> > > What are the benefits to using Git over SVN?
> > > Do they outweigh the costs?
> > > Who gets the benefit, and who pays the costs?
> > >
> > > ==
> > >
> > > Note that projects.a.o actually updates its own code repo using a role
> > > account. I don't know if that can be done in Git.
> > > It took quite a bit of work to ensure that the updates did not result
> > > in a locked workspace.
> > > (This used to happen regularly at the beginning)
> > >
> > > Also, the projects.a.o and reporter.a.o hosts share the same VM.
> > > They would need to move together.
> > >
> > > And of course the VM puppet definition will need to be updated.
> > > It's more complicated than a simple pubsub operation.
> > >
> > > > Perhaps we can do the same for the 3 other locations in svn
> > > > https://projects.apache.org/project.html?comdev-community_development
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> > > >> Vincent Tuybens created COMDEV-288:
> > > >> --
> > > >>
> > > >> Summary: Request "Projects Directory" migration to GIT
> > > >>
> > > >> Key: COMDEV-288
> >
> > > >> URL:
> > https://issues.apache.org/jira/browse/COMDEV-288
> >
> > > >> Project: Community Development
> > > >>
> > > >> Issue Type: SVN->GIT Migration
> > > >> Components: Projects Tool
> > > >>
> > > >> Reporter: Vincent Tuybens
> > > >>
> > > >> Dear all,
> > > >>
> > > >> is it possible for you to plan SVN to GIT migration for "Projects
> > > >> Directory" project ?
> > > >>
> > > >> [{color:#0066cc}
> >
> > https://svn.apache.org/repos/asf/comdev/projects.apache.o
> >
> > > >> rg/ {color}]
> > > >>
> > > >> Thank you,
> > > >>
> > > >> Regards.
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> This message was sent by Atlassian JIRA
> > > >> (v7.6.3#76005)
> > > >>
> > > >> -
> > > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > >> For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apach
Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT
Le jeudi 5 avril 2018, 00:42:57 CEST sebb a écrit :
> On 4 April 2018 at 23:34, Hervé BOUTEMY wrote:
> > there is a little misunderstanding: I'm not talking about fully switching
> > from svn to git
> > I'm talking about keeping svn as canonical repository but adding a
> > read-only git mirror like done on many svn repositories [1]
>
> The JIRA said otherwise...
yes, external people nowadays just think "switch to Git" et voilà.
But I have a long experience on Maven (more than 5 years to to the near full
migration [2]), and I know that it does not happen like this: there are steps
to have the team find advantages along the journey, letting time to learn and
do progressive adoption
This is how I naturally transformed the initial typical request: into the
typical first step
[2] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>
> > This does not change anything to the host configuration, but adds a GitHub
> > mirror for external people to contribute through GitHub Pull Requests,
> > which are so much easier to submit than svn patch attached to a Jira
> > issue: this will give a chance to get more contributions.
>
> OK, fine.
>
> > Later on, we can decide to switch to Git (with gitwcsub acting like
> > currently svnwcsub), but that will be another choice to do in another
> > time.
>
> That will be a lot of work.
We'll see it later: for sure, it's more impact, then requires to be prepared.
svn 2 git mirror is a good first step, that is required if we do the next steps
or not
>
> > Regards,
> >
> > Hervé
> >
> > [1] http://git.apache.org/
> >
> > Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> >> On 4 April 2018 at 07:09, Hervé BOUTEMY wrote:
> >> > What about creating a Git/GitHub svn2git mirror for
> >> > projects.apache.org?
> >> > This would be our first Git repo for community/comdev: I don't know
> >> > which
> >> > prefix we should use...
> >> >
> >> > Any objection?
> >>
> >> What are the benefits to using Git over SVN?
> >> Do they outweigh the costs?
> >> Who gets the benefit, and who pays the costs?
> >>
> >> ==
> >>
> >> Note that projects.a.o actually updates its own code repo using a role
> >> account. I don't know if that can be done in Git.
> >> It took quite a bit of work to ensure that the updates did not result
> >> in a locked workspace.
> >> (This used to happen regularly at the beginning)
> >>
> >> Also, the projects.a.o and reporter.a.o hosts share the same VM.
> >> They would need to move together.
> >>
> >> And of course the VM puppet definition will need to be updated.
> >> It's more complicated than a simple pubsub operation.
> >>
> >> > Perhaps we can do the same for the 3 other locations in svn
> >> > https://projects.apache.org/project.html?comdev-community_development
> >> >
> >> > Regards,
> >> >
> >> > Hervé
> >> >
> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> >> >> Vincent Tuybens created COMDEV-288:
> >> >> --
> >> >>
> >> >> Summary: Request "Projects Directory" migration to GIT
> >> >>
> >> >> Key: COMDEV-288
> >> >> URL: https://issues.apache.org/jira/browse/COMDEV-288
> >> >>
> >> >> Project: Community Development
> >> >>
> >> >> Issue Type: SVN->GIT Migration
> >> >> Components: Projects Tool
> >> >>
> >> >> Reporter: Vincent Tuybens
> >> >>
> >> >> Dear all,
> >> >>
> >> >> is it possible for you to plan SVN to GIT migration for "Projects
> >> >> Directory" project ?
> >> >>
> >> >> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apach
> >> >> e.o
> >> >> rg/ {color}]
> >> >>
> >> >> Thank you,
> >> >>
> >> >> Regards.
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> This message was sent by Atlassian JIRA
> >> >> (v7.6.3#76005)
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> >> For additional commands, e-mail: dev-h...@community.apache.org
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> > For additional commands, e-mail: dev-h...@community.apache.org
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT
The PRs created for read-only hit are not "mergeable"
WBR, Maxim
(from mobile, sorry for the typos)
On Thu, Apr 5, 2018, 05:34 Hervé BOUTEMY wrote:
> there is a little misunderstanding: I'm not talking about fully switching
> from
> svn to git
> I'm talking about keeping svn as canonical repository but adding a
> read-only
> git mirror like done on many svn repositories [1]
>
> This does not change anything to the host configuration, but adds a GitHub
> mirror for external people to contribute through GitHub Pull Requests,
> which
> are so much easier to submit than svn patch attached to a Jira issue: this
> will give a chance to get more contributions.
>
> Later on, we can decide to switch to Git (with gitwcsub acting like
> currently
> svnwcsub), but that will be another choice to do in another time.
>
> Regards,
>
> Hervé
>
> [1] http://git.apache.org/
>
> Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> > On 4 April 2018 at 07:09, Hervé BOUTEMY wrote:
> > > What about creating a Git/GitHub svn2git mirror for
> projects.apache.org?
> > > This would be our first Git repo for community/comdev: I don't know
> which
> > > prefix we should use...
> > >
> > > Any objection?
> >
> > What are the benefits to using Git over SVN?
> > Do they outweigh the costs?
> > Who gets the benefit, and who pays the costs?
> >
> > ==
> >
> > Note that projects.a.o actually updates its own code repo using a role
> > account. I don't know if that can be done in Git.
> > It took quite a bit of work to ensure that the updates did not result
> > in a locked workspace.
> > (This used to happen regularly at the beginning)
> >
> > Also, the projects.a.o and reporter.a.o hosts share the same VM.
> > They would need to move together.
> >
> > And of course the VM puppet definition will need to be updated.
> > It's more complicated than a simple pubsub operation.
> >
> > > Perhaps we can do the same for the 3 other locations in svn
> > > https://projects.apache.org/project.html?comdev-community_development
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> > >> Vincent Tuybens created COMDEV-288:
> > >> --
> > >>
> > >> Summary: Request "Projects Directory" migration to GIT
> > >>
> > >> Key: COMDEV-288
> > >> URL:
> https://issues.apache.org/jira/browse/COMDEV-288
> > >>
> > >> Project: Community Development
> > >>
> > >> Issue Type: SVN->GIT Migration
> > >> Components: Projects Tool
> > >>
> > >> Reporter: Vincent Tuybens
> > >>
> > >> Dear all,
> > >>
> > >> is it possible for you to plan SVN to GIT migration for "Projects
> > >> Directory" project ?
> > >>
> > >> [{color:#0066cc}
> https://svn.apache.org/repos/asf/comdev/projects.apache.o
> > >> rg/ {color}]
> > >>
> > >> Thank you,
> > >>
> > >> Regards.
> > >>
> > >>
> > >>
> > >> --
> > >> This message was sent by Atlassian JIRA
> > >> (v7.6.3#76005)
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > >> For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>
Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT
On 4 April 2018 at 23:34, Hervé BOUTEMY wrote:
> there is a little misunderstanding: I'm not talking about fully switching from
> svn to git
> I'm talking about keeping svn as canonical repository but adding a read-only
> git mirror like done on many svn repositories [1]
The JIRA said otherwise...
> This does not change anything to the host configuration, but adds a GitHub
> mirror for external people to contribute through GitHub Pull Requests, which
> are so much easier to submit than svn patch attached to a Jira issue: this
> will give a chance to get more contributions.
OK, fine.
> Later on, we can decide to switch to Git (with gitwcsub acting like currently
> svnwcsub), but that will be another choice to do in another time.
That will be a lot of work.
> Regards,
>
> Hervé
>
> [1] http://git.apache.org/
>
> Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
>> On 4 April 2018 at 07:09, Hervé BOUTEMY wrote:
>> > What about creating a Git/GitHub svn2git mirror for projects.apache.org?
>> > This would be our first Git repo for community/comdev: I don't know which
>> > prefix we should use...
>> >
>> > Any objection?
>>
>> What are the benefits to using Git over SVN?
>> Do they outweigh the costs?
>> Who gets the benefit, and who pays the costs?
>>
>> ==
>>
>> Note that projects.a.o actually updates its own code repo using a role
>> account. I don't know if that can be done in Git.
>> It took quite a bit of work to ensure that the updates did not result
>> in a locked workspace.
>> (This used to happen regularly at the beginning)
>>
>> Also, the projects.a.o and reporter.a.o hosts share the same VM.
>> They would need to move together.
>>
>> And of course the VM puppet definition will need to be updated.
>> It's more complicated than a simple pubsub operation.
>>
>> > Perhaps we can do the same for the 3 other locations in svn
>> > https://projects.apache.org/project.html?comdev-community_development
>> >
>> > Regards,
>> >
>> > Hervé
>> >
>> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
>> >> Vincent Tuybens created COMDEV-288:
>> >> --
>> >>
>> >> Summary: Request "Projects Directory" migration to GIT
>> >>
>> >> Key: COMDEV-288
>> >> URL: https://issues.apache.org/jira/browse/COMDEV-288
>> >>
>> >> Project: Community Development
>> >>
>> >> Issue Type: SVN->GIT Migration
>> >> Components: Projects Tool
>> >>
>> >> Reporter: Vincent Tuybens
>> >>
>> >> Dear all,
>> >>
>> >> is it possible for you to plan SVN to GIT migration for "Projects
>> >> Directory" project ?
>> >>
>> >> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.o
>> >> rg/ {color}]
>> >>
>> >> Thank you,
>> >>
>> >> Regards.
>> >>
>> >>
>> >>
>> >> --
>> >> This message was sent by Atlassian JIRA
>> >> (v7.6.3#76005)
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> >> For additional commands, e-mail: dev-h...@community.apache.org
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> > For additional commands, e-mail: dev-h...@community.apache.org
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-288) Request "Projects Directory" migration to GIT
[
https://issues.apache.org/jira/browse/COMDEV-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426275#comment-16426275
]
Hervé Boutemy commented on COMDEV-288:
--
Let's start by adding a svn2git read-only mirror, like those visible on
http://git.apache.org/
You'll be able to propose PRs (that committers will have to merge to canonical
svn repo)
> Request "Projects Directory" migration to GIT
> -
>
> Key: COMDEV-288
> URL: https://issues.apache.org/jira/browse/COMDEV-288
> Project: Community Development
> Issue Type: SVN->GIT Migration
> Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> Dear all,
> is it possible for you to plan SVN to GIT migration for "Projects Directory"
> project ?
> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/{color}]
> Thank you,
> Regards.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT
there is a little misunderstanding: I'm not talking about fully switching from
svn to git
I'm talking about keeping svn as canonical repository but adding a read-only
git mirror like done on many svn repositories [1]
This does not change anything to the host configuration, but adds a GitHub
mirror for external people to contribute through GitHub Pull Requests, which
are so much easier to submit than svn patch attached to a Jira issue: this
will give a chance to get more contributions.
Later on, we can decide to switch to Git (with gitwcsub acting like currently
svnwcsub), but that will be another choice to do in another time.
Regards,
Hervé
[1] http://git.apache.org/
Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> On 4 April 2018 at 07:09, Hervé BOUTEMY wrote:
> > What about creating a Git/GitHub svn2git mirror for projects.apache.org?
> > This would be our first Git repo for community/comdev: I don't know which
> > prefix we should use...
> >
> > Any objection?
>
> What are the benefits to using Git over SVN?
> Do they outweigh the costs?
> Who gets the benefit, and who pays the costs?
>
> ==
>
> Note that projects.a.o actually updates its own code repo using a role
> account. I don't know if that can be done in Git.
> It took quite a bit of work to ensure that the updates did not result
> in a locked workspace.
> (This used to happen regularly at the beginning)
>
> Also, the projects.a.o and reporter.a.o hosts share the same VM.
> They would need to move together.
>
> And of course the VM puppet definition will need to be updated.
> It's more complicated than a simple pubsub operation.
>
> > Perhaps we can do the same for the 3 other locations in svn
> > https://projects.apache.org/project.html?comdev-community_development
> >
> > Regards,
> >
> > Hervé
> >
> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> >> Vincent Tuybens created COMDEV-288:
> >> --
> >>
> >> Summary: Request "Projects Directory" migration to GIT
> >>
> >> Key: COMDEV-288
> >> URL: https://issues.apache.org/jira/browse/COMDEV-288
> >>
> >> Project: Community Development
> >>
> >> Issue Type: SVN->GIT Migration
> >> Components: Projects Tool
> >>
> >> Reporter: Vincent Tuybens
> >>
> >> Dear all,
> >>
> >> is it possible for you to plan SVN to GIT migration for "Projects
> >> Directory" project ?
> >>
> >> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.o
> >> rg/ {color}]
> >>
> >> Thank you,
> >>
> >> Regards.
> >>
> >>
> >>
> >> --
> >> This message was sent by Atlassian JIRA
> >> (v7.6.3#76005)
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
Help with task: How do I edit the site?
I would like to help out with the task listed at https://helpwanted.apache.org/task.html?60e13b6e
Help with task: How do I edit the site?
I would like to help out with the task listed at https://helpwanted.apache.org/task.html?60e13b6e
Re: Request the permissions of using name and logo of ServiceComb in the Meetup
Thank you, Zen. The logo is fine. You are good to go. --Sally [from the mobile; kindly forgive typos, brevity] On Wed, Apr 4, 2018 at 0:43, Sally Khudairi wrote: Thank you, Zen. Yes, I will be happy to check the images when I am back in the office later today. Kind regards, Sally [from the mobile; kindly forgive typos, brevity] On Wed, Apr 4, 2018 at 0:29, Zen Lin wrote: Hi Sally, thanks, it is so nice of you to give the instructions. The "Powered By" image is just have been designed yesterday after I gone through the doc of press-kit[1]. We still have not updated to the Servicecomb website[2] because it has not been checked by ASFMarketing & Publicity. I just shared the images google drive through your email, could you help to do a check about wheather the image is specific to the Apache Incubator press-kit[1]? [1] https://incubator.apache.org/ guides/press-kit.html[2] http://servicecomb.incubator.apache.org/ Zen Lin 2018-04-03 19:31 GMT+08:00 Sally Khudairi : Thank you, Zen. I appreciate your reaching out. Overall, this looks fine. We will also need signoff from ASF Brand Management (tradema...@apache.org). I've copied them here for their review. Also, please ensure that the "Powered By" images are specific to the Apache Incubator https://incubator.apache.org/ guides/press-kit.html :-) Please let me know once you have signoff and I'll be happy to add the event to the "Community Notices" section of the Apache Weekly News Round- ups https://blogs.apache.org/ foundation/entry/the-apache- news-round-up64 Warm regards, Sally - - - Vice President Marketing & Publicity The Apache Software Foundation Tel +1 617 921 8656 Skype sallykhudairi On Tue, Apr 3, 2018, at 01:16, Zen Lin wrote: > Hi ASF Marketing & Publicity, > > In order to promote ServiceComb and its community, ServiceComb are > planning to hold a mini meetup as a Co-located Event in LC3 2018 Asia.> > The Proposal for holding the mini meetup have been approved with the > PMCs of ServiceComb [1] .> > I have gone through the docs of Approval of small Apache-related > events[2] and Apache branding rules[3], this mail is to describe > some details of the planning event and ask for using the name logo of > Apache ServiceComb(incubating) in the event. Further advices are > welcomed.> > Some details of the idea/plan, > 1. Name of the event: Apache ServiceComb(incubating) Meetup > Hosted/Presented by Huawei PaaS> 2. Event organizer: PMCs of ServiceComb >project > 3. Estimated attendees: 60~100 > 4. Where/When/How: As a Co-located Event in LC3 Asia, June 25-27, > 2018, China National Convention Center, Beijing, China> 5. Possible >topics: user pratices/technologies/ ecosystem sharing > > We are requsting two permissions, > 1. Use the name of "Apache ServiceComb Incubating Meetup > Hosted/Supported by Huawei PaaS"> 2. Use the "Powered By" Apache Incubator >logo of ServiceComb. > > > [1] https://www.mail-archive.com/ d...@servicecomb.apache.org/ msg03298.html> > [2] http://community.apache.org/ events/small-events.html > [3] http://www.apache.org/ foundation/marks/events.html > > > > Thanks very much, > > Zen Lin
Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT
On 4 April 2018 at 07:09, Hervé BOUTEMY wrote:
> What about creating a Git/GitHub svn2git mirror for projects.apache.org?
> This would be our first Git repo for community/comdev: I don't know which
> prefix
> we should use...
>
> Any objection?
What are the benefits to using Git over SVN?
Do they outweigh the costs?
Who gets the benefit, and who pays the costs?
==
Note that projects.a.o actually updates its own code repo using a role account.
I don't know if that can be done in Git.
It took quite a bit of work to ensure that the updates did not result
in a locked workspace.
(This used to happen regularly at the beginning)
Also, the projects.a.o and reporter.a.o hosts share the same VM.
They would need to move together.
And of course the VM puppet definition will need to be updated.
It's more complicated than a simple pubsub operation.
> Perhaps we can do the same for the 3 other locations in svn
> https://projects.apache.org/project.html?comdev-community_development
>
> Regards,
>
> Hervé
>
> Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
>> Vincent Tuybens created COMDEV-288:
>> --
>>
>> Summary: Request "Projects Directory" migration to GIT
>> Key: COMDEV-288
>> URL: https://issues.apache.org/jira/browse/COMDEV-288
>> Project: Community Development
>> Issue Type: SVN->GIT Migration
>> Components: Projects Tool
>> Reporter: Vincent Tuybens
>>
>>
>> Dear all,
>>
>> is it possible for you to plan SVN to GIT migration for "Projects Directory"
>> project ?
>>
>> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/
>> {color}]
>>
>> Thank you,
>>
>> Regards.
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v7.6.3#76005)
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
