[Vtigercrm-developers] Documentation for open source, taken down? (wiki.vtiger.com)

[nilay khatri]

I was myself a part of Vtiger and was involved in vtiger 5.4 and 6 versions
development.

To start with we would like to add patches for some security updates and
framework changes to override core files.

On Tue, Jun 11, 2019, 2:05 PM nilay khatri <nilay.spartan at gmail.com> wrote:

> Definitely!
>
> On Tue, Jun 11, 2019, 2:00 PM Tony Sandman <tonysandman999 at gmail.com>
> wrote:
>
>> I suggest three or more individuals / companies to manage a new
>> repository. We have here few guys heavily involved in code for over many
>> years.
>> New contribution rules may give it a good kick.
>>
>> T
>>
>>
>>
>> On Tue, Jun 11, 2019 at 3:03 PM nilay khatri <nilay.spartan at gmail.com>
>> wrote:
>>
>>> Automate SMB would like to take this initiative.
>>>
>>> Our proposal:
>>>
>>>  - Take the latest code from code.vtiger.com,  release it with new
>>> minor version.
>>>
>>> - Create a GitHub repository.
>>>
>>> - Define Technical documentation on Wiki page.
>>>
>>> - Use Linkedin as a platform for discussions on use cases, new extension
>>> releases and general discussions.
>>>
>>> The community should be responsible to take the latest code releases
>>> from Vtiger repository and migrate it to the Community managed Source Code (*suggest
>>> a name!*).
>>>
>>> FYI summary of my discussion with Vtiger Team about Vtiger trademark
>>> usage and SEO harvesting:
>>> - do not have any urls containing Vtiger  keyword
>>> - they also mentioned that Google might also come behind you if you have
>>> Vtiger in urls
>>> - this is to avoid mis-representation of the product
>>>
>>>
>>> Votes and opinions welcome!
>>>
>>>
>>> -Nilay
>>> _______________________________________________
>>> http://www.vtiger.com/
>>
>> _______________________________________________
>> http://www.vtiger.com/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20190611/328ff50c/attachment.html>