[
https://issues.apache.org/jira/browse/COMDEV-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799334#comment-16799334
]
Dave Brondsema commented on COMDEV-307:
---
Hi [~dilshandilip] I'd recomm
[
https://issues.apache.org/jira/browse/COMDEV-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782498#comment-16782498
]
Dave Brondsema commented on COMDEV-307:
---
[~nayanagamuhandiram] you should join
[
https://issues.apache.org/jira/browse/COMDEV-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782126#comment-16782126
]
Dave Brondsema commented on COMDEV-306:
---
[~Abhism] you should join the dev mai
Dave Brondsema created COMDEV-308:
-
Summary: GSoC - Allura - importers / sync for Bitbucket and Gitlab
Key: COMDEV-308
URL: https://issues.apache.org/jira/browse/COMDEV-308
Project: Community
Dave Brondsema created COMDEV-307:
-
Summary: GSoC - Allura - responsive web pages
Key: COMDEV-307
URL: https://issues.apache.org/jira/browse/COMDEV-307
Project: Community Development
Issue
[
https://issues.apache.org/jira/browse/COMDEV-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brondsema updated COMDEV-306:
--
Component/s: GSoC/Mentoring ideas
> GSoC - Allura - Convert to pytho
Dave Brondsema created COMDEV-306:
-
Summary: GSoC - Allura - Convert to python 3
Key: COMDEV-306
URL: https://issues.apache.org/jira/browse/COMDEV-306
Project: Community Development
Issue
[
https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399542#comment-16399542
]
Dave Brondsema commented on COMDEV-256:
---
Hi Nirmal,
I would recommend you writ
[
https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379465#comment-16379465
]
Dave Brondsema commented on COMDEV-256:
---
[https://forge-allura.apache.org/
[
https://issues.apache.org/jira/browse/COMDEV-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379455#comment-16379455
]
Dave Brondsema commented on COMDEV-255:
---
Hi,
We have documentation about Allur
[
https://issues.apache.org/jira/browse/COMDEV-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379453#comment-16379453
]
Dave Brondsema commented on COMDEV-254:
---
Hi,
We have documentation about Allur
[
https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372992#comment-16372992
]
Dave Brondsema commented on COMDEV-256:
---
You can subscribe by sending a mail to
[
https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372205#comment-16372205
]
Dave Brondsema commented on COMDEV-256:
---
Hi Nirmal,
On [https://f
Dave Brondsema created COMDEV-256:
-
Summary: Allura - importers / sync for Bitbucket and Gitlab
Key: COMDEV-256
URL: https://issues.apache.org/jira/browse/COMDEV-256
Project: Community Development
Dave Brondsema created COMDEV-255:
-
Summary: Allura - merge request improvements
Key: COMDEV-255
URL: https://issues.apache.org/jira/browse/COMDEV-255
Project: Community Development
Issue
Dave Brondsema created COMDEV-254:
-
Summary: Allura - personal dashboard
Key: COMDEV-254
URL: https://issues.apache.org/jira/browse/COMDEV-254
Project: Community Development
Issue Type: New
anguages and skills and I
> am even familiar with these so I would like to work for APACHE.
>
> Not only because of the above reasons I want to work under APACHE but
> moreover its projects are interesting and suitable up to my knowledge of
> work and I am quite experienced with i
be better if we do migrate all non-empty
projects (rather than make projects do it). That way no projects are left
behind and disappear from the internet.
Followup work could be tasked to the individual projects to handle. This would
include moving Google Code landing page content into either a description or
wiki page. And setting up the redirect info on the Google Code project.
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
lready under
> control of the PMC.
>
With my SourceForge hat on, you can request a rename to get rid of the ".mirror"
part. And a redirect from sf.net/projects/oooextras.mirror/ to
sf.net/projects/oooextras/ may be possible if needed. You can contact support
via https://sourcefor
ourceForge, so we would need
>> to rename them.
>>
>> That leaves us with a few questions:
>> Does ComDev want us to migrate:
>> a) all 350
>> b) only the projects that are original at Apache Extras
>> c) only the projects at Apache Extras that are original and actually have
>> content - and if c) - please provide a list.
>>
>> What would ComDev like to rename the projects where naming collisions are in
>> place?
>>
>> --David
>
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
n maintaining an
Allura installation.
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
signature.asc
Description: OpenPGP digital signature
it. SourceForge's
docs about it are at
https://sourceforge.net/p/forge/documentation/Google%20Code%20Importer/
Note: these importers currently choke on the extra "/a/apache-extras.org" in the
URL. I'm sure that would be easy enough for us to fix if anyone wanted to
procee
s-2-0 May be a useful entry
point if you want to pursue or encourage such a talk at ApacheCon.
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
23 matches
Mail list logo
