Re: [myhdl-list] Keep hierarchy in VHDL conversion

[Jan D. <ja...@ja...>]

All - thanks for the feedback.

I think a consensus is growing: stay with hg,
but move to bitbucket for development, because
it should improve the process: public forks
to demonstrate features, and pull requests
instead of patches and bundles.

I'm all for it - as a trial, I've imported
the main repo on bitbucket already and this
seems to work fine. (jandecaluwe/myhdl).

Jan


On 04/15/2013 02:48 AM, Christopher Felton wrote:
> On 4/14/13 2:28 PM, Jan Decaluwe wrote:
>> On 04/14/2013 06:02 PM, Angel Ezquerra wrote:
>>
>>> Oscar,
>>>
>>> if you have never used mercurial and need some help drop me a line. I
>>> am very active in TortoiseHg development (and a bit on mercurial as
>>> well) so I think I could help bring you up to speed if you need it
>>
>> Interesting.
>>
>> Perhaps I should ask a more general question: should we
>> consider to move MyHDL development to github?
>>
>> This is not a technical question. Many Pythonistas probably
>> have a slight preference for Python-based mercurial.
>> Professionally, I use both and I am happy with either one.
>>
>> The point is that "everyone" seems to be at github. So
>> perhaps this is good for visibility.
>>
>> It may also be good for development. I like the way
>> Oscar presented his work: it shows commitment to
>> maintain the feature, and everyone can try/follow
>> it without requiring my assistance. Much better
>> than getting patches/bundles out of the blue that
>> I am supposed to review/check/integrate before others
>> can (easily) do so.
>>
>> Of course, for this to work, all development should
>> be on the same system.
>>
>> Jan
>>
>
> As Jan eluded, there are two features:
>
>      1) Improved work-flow:
>         a) pull requests (largest impact)
>         b) simplified interfaces (click buttons on webpages)
>         c) default public (mods not local on private machine)
>
>      2) Visibility (popular social thing)
>
> If we feel #2 holds a lot of weight then github is the answer. If
> visibility is important but not the most important then I would
> suggest we stay with hg and use bitbucket (like pypy, sphinx,
> cherrpy, ...).
>
> For me a move to git vs. hg would be disruptive.  Not because
> of some huge technical short-coming but because all my work has
> been with hg and bitbucket.  If we move to git and github my
> work flow and existing projects will not be compatible with the
> new work flow (i.e. git and github).
>
> Other than not being as popular I don't know of any technical
> limitations of bitbucket vs. github.
>
> It will be interesting to here back from Oscar, why he chose
> github over bitbucket being myhdl uses hg.
>
> My vote is to stay with hg and utilize bitbucket but I am not
> adamantly opposed to git and github.  I do think it is important
> that we start using bitbucket or github and pull requests.
>
> Regards,
> Chris
>
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
>


-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
     Python as a HDL: http://www.myhdl.org
     VHDL development, the modern way: http://www.sigasi.com
     World-class digital design: http://www.easics.com