We can't actually.  ASF project source code _must_ reside on ASF
infrastructure.  Any other locations that you might see are mirrors of the
ASF canonical location(s).

Maybe you might have been thinking Gitlab over GitHub?  But even then,
GitHub isn't an option either due to the infrastructure requirement.
On Aug 2, 2015 7:02 PM, "Dishant Anand" <[email protected]>
wrote:

> You can consider moving to gitlab , which is a better option over git.
>
> It has much more social coding style approach , plus code reviews are lot
> more better.
> https://about.gitlab.com/features/
>
> Regards,
> Dishant Anand
> On 03/08/2015 01:57, Brian Demers wrote:
>
>> +1 i've been thinking about suggesting it too.
>>
>>
>> On Sun, Aug 2, 2015 at 8:36 PM, Kalle Korhonen <[email protected]> wrote:
>>
>> That's a bit harsh to subversion. I know plenty of organizations, big and
>>> small, that still use svn. That said, I've been thinking about suggesting
>>> the same so here's my +1.
>>>
>>> Kalle
>>> On Aug 2, 2015 4:58 PM, "Les Hazlewood" <[email protected]> wrote:
>>>
>>> I don't know anyone that still uses Subversion for source control.
>>>>
>>>> Any objections to moving Shiro to an ASF git repo asap?
>>>>
>>>> https://git-wip-us.apache.org/docs/switching-to-git.html
>>>>
>>>> Cheers,
>>>>
>>>> Les
>>>>
>>>>
> --
>         Dishant Anand
>
> Software Engineer
>
>         Tel: +91 124 4548383 Ext- 1005
> UK: +44 845 0047 142 Ext- 5115
>
>         TBS Website <http://www.techbluesoftware.co.in>
>         Techblue Software Pvt. Ltd
> The Palms, Plot No 73, Sector 5, IMT Manesar,
> Gurgaon- 122050 (Hr.)
>
> www.techbluesoftware.co.in <http://www.techbluesoftware.co.in>
>
>
>         TBS Facebook <
> https://www.facebook.com/pages/Techblue-Software-Limited/441777369284888>
> TBS Twitter <https://twitter.com/TechbluSoftware> TBS Google+ <
> https://plus.google.com/+TechblueSoftwareCoIn> TBS Linked In <
> https://www.linkedin.com/company/techblue-softwares-pvt-ltd>
>
> TBS Branding <http://www.techbluesoftware.co.in>
>
>
>            Confidentiality Notice: This e-mail is intended solely for
>            the use of the individual to whom it is addressed and may
>            contain information that is privileged, confidential or
>            otherwise exempt from disclosure. If the reader of this
>            e-mail is not the intended recipient or the employee or
>            agent responsible for delivering the message to the intended
>            recipient, you are hereby notified that any dissemination,
>            distribution, or copying of this communication is strictly
>            prohibited. If you have received this communication in
>            error, please immediately notify us by replying to the
>            original message at the listed email address. Thank You.
>
>

Reply via email to