You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Gary <ga...@wandisco.com> on 2012/03/08 18:36:13 UTC
Getting involved and installation pages
On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
> Out of curiosity, do we have a "how to get involved" or "beginner's
> guide to Bloodhound" wiki page or document anywhere? It'd be useful
> to codify these kinds of steps into something we can point newcomers
> to.
>
> -Hyrum
Good idea.
Meanwhile I have added a few pages relating to installation to the wiki at:
* https://issues.apache.org/bloodhound/wiki/BloodhoundInstall
* https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation
I will look at writing something about getting involved very soon unless
someone else wants to look at that.
Cheers,
Gary
Re: Getting involved and installation pages
Posted by Joachim Dreimann <jo...@wandisco.com>.
I have now also added a section on how to get involved in the
UI/Design process (other than code as such).
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing#ContributingDesigns
Any feedback appreciated.
- Joe
On 13 March 2012 11:08, Gary <ga...@wandisco.com> wrote:
> Hi,
>
> Just changed the installer to supply a logger object for virtualenv when it
> is missing.
>
> Cheers,
> Gary
>
>
> On 03/13/2012 10:55 AM, gjm@apache.org wrote:
>>
>> Author: gjm
>> Date: Tue Mar 13 10:55:14 2012
>> New Revision: 1300071
>>
>> URL: http://svn.apache.org/viewvc?rev=1300071&view=rev
>> Log:
>> maintain compatibility with older versions of virtualenv, fixing #4
>>
>> Modified:
>> incubator/bloodhound/trunk/installer/installer.py
>
>
> On 03/12/2012 10:25 AM, Gary wrote:
>>
>> Hi Antony,
>>
>> Thanks for that.
>>
>> OK, I would prefer not to have to specify a minimum version of virtualenv
>> that is newer than that available for the default version of a major linux
>> distribution. So we can either resort to calling virtualenv through
>> subprocess or we can do to the following:
>>
>> if not hasattr(virtualenv, 'logger'):
>> virtualenv.logger =
>> virtualenv.Logger([(virtualenv.Logger.LEVELS[-1],
>> sys.stdout)])
>>
>>
>> Cheers,
>> Gary
>>
>>
>> On 03/10/2012 12:36 PM, Antony Semonella wrote:
>>>
>>> Hello,
>>>
>>> I managed to set up a bloodhound development environment on Debian 6.0
>>> following the instructions at:
>>>
>>> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
>>>
>>> You may want to update the wiki to highlight the following dependency I
>>> encountered:
>>>
>>> The version of virtualenv in the repo for Debian squeeze is: 1.4.9-3;
>>> this
>>> version of virtualenv results in:
>>>
>>> NameError: global name 'logger' is not defined
>>>
>>> When running bloodhound/installer/installer.py.
>>>
>>> logger is defined only in main() for this version of virtualenv.
>>>
>>> This issue has been resolved by:
>>>
>>> https://github.com/pypa/virtualenv/commit/ea1786
>>>
>>> Using the latest version of virtualenv (1.7.1.2) resulted in no NameError
>>> and so the bloodhound dev. environment was setup ok for me.
>>>
>>> I therefore suggest a version of virtualenv>=1.7.1.2 be listed as a
>>> dependency.
>>>
>>> Cheers!
>>>
>>> Antony
>
>
Re: Getting involved and installation pages
Posted by Gary <ga...@wandisco.com>.
Hi,
Just changed the installer to supply a logger object for virtualenv when
it is missing.
Cheers,
Gary
On 03/13/2012 10:55 AM, gjm@apache.org wrote:
> Author: gjm
> Date: Tue Mar 13 10:55:14 2012
> New Revision: 1300071
>
> URL: http://svn.apache.org/viewvc?rev=1300071&view=rev
> Log:
> maintain compatibility with older versions of virtualenv, fixing #4
>
> Modified:
> incubator/bloodhound/trunk/installer/installer.py
On 03/12/2012 10:25 AM, Gary wrote:
> Hi Antony,
>
> Thanks for that.
>
> OK, I would prefer not to have to specify a minimum version of
> virtualenv that is newer than that available for the default version
> of a major linux distribution. So we can either resort to calling
> virtualenv through subprocess or we can do to the following:
>
> if not hasattr(virtualenv, 'logger'):
> virtualenv.logger =
> virtualenv.Logger([(virtualenv.Logger.LEVELS[-1],
> sys.stdout)])
>
>
> Cheers,
> Gary
>
>
> On 03/10/2012 12:36 PM, Antony Semonella wrote:
>> Hello,
>>
>> I managed to set up a bloodhound development environment on Debian 6.0
>> following the instructions at:
>>
>> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
>>
>> You may want to update the wiki to highlight the following dependency I
>> encountered:
>>
>> The version of virtualenv in the repo for Debian squeeze is: 1.4.9-3; this
>> version of virtualenv results in:
>>
>> NameError: global name 'logger' is not defined
>>
>> When running bloodhound/installer/installer.py.
>>
>> logger is defined only in main() for this version of virtualenv.
>>
>> This issue has been resolved by:
>>
>> https://github.com/pypa/virtualenv/commit/ea1786
>>
>> Using the latest version of virtualenv (1.7.1.2) resulted in no NameError
>> and so the bloodhound dev. environment was setup ok for me.
>>
>> I therefore suggest a version of virtualenv>=1.7.1.2 be listed as a
>> dependency.
>>
>> Cheers!
>>
>> Antony
Re: Getting involved and installation pages
Posted by Gary <ga...@wandisco.com>.
Hi Antony,
Thanks for that.
OK, I would prefer not to have to specify a minimum version of
virtualenv that is newer than that available for the default version of
a major linux distribution. So we can either resort to calling
virtualenv through subprocess or we can do to the following:
if not hasattr(virtualenv, 'logger'):
virtualenv.logger =
virtualenv.Logger([(virtualenv.Logger.LEVELS[-1],
sys.stdout)])
Cheers,
Gary
On 03/10/2012 12:36 PM, Antony Semonella wrote:
> Hello,
>
> I managed to set up a bloodhound development environment on Debian 6.0
> following the instructions at:
>
> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
>
> You may want to update the wiki to highlight the following dependency I
> encountered:
>
> The version of virtualenv in the repo for Debian squeeze is: 1.4.9-3; this
> version of virtualenv results in:
>
> NameError: global name 'logger' is not defined
>
> When running bloodhound/installer/installer.py.
>
> logger is defined only in main() for this version of virtualenv.
>
> This issue has been resolved by:
>
> https://github.com/pypa/virtualenv/commit/ea1786
>
> Using the latest version of virtualenv (1.7.1.2) resulted in no NameError
> and so the bloodhound dev. environment was setup ok for me.
>
> I therefore suggest a version of virtualenv>=1.7.1.2 be listed as a
> dependency.
>
> Cheers!
>
> Antony
>
>
>
> On 9 March 2012 14:48, Antony Semonella<as...@gmail.com> wrote:
>
>> Cool, I'll give the docs a read (as a newcomer) and provide some feedback
>> :)
>>
>>
>> On 9 March 2012 14:35, Gary<ga...@wandisco.com> wrote:
>>
>>> Hi everyone,
>>>
>>> We now have https://issues.apache.org/**bloodhound/wiki/**
>>> BloodhoundContributing<https://issues.apache.org/bloodhound/wiki/BloodhoundContributing>
>>>
>>> As always, this definitely needs some expanding upon and improving but I
>>> hope it can serve as a reasonable starting point - we definitely need to
>>> discuss other ways of helping like contributing to documentation and
>>> reporting bugs. And there are definitely a lot of documentation tasks to be
>>> done as we get new features in.
>>>
>>> Cheers,
>>> Gary
>>>
>>>
>>> On 03/08/2012 06:00 PM, Antony Semonella wrote:
>>>
>>>> That sounds great.
>>>>
>>>> Cheers,
>>>>
>>>> Antony
>>>>
>>>> On 8 March 2012 17:36, Gary<ga...@wandisco.com> wrote:
>>>>
>>>> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>>>>> Out of curiosity, do we have a "how to get involved" or "beginner's
>>>>>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>>>>>> to codify these kinds of steps into something we can point newcomers
>>>>>> to.
>>>>>>
>>>>>> -Hyrum
>>>>>>
>>>>>> Good idea.
>>>>> Meanwhile I have added a few pages relating to installation to the wiki
>>>>> at:
>>>>> * https://issues.apache.org/****bloodhound/wiki/****BloodhoundInstall<https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall>
>>>>> <https://**issues.apache.org/bloodhound/**wiki/BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
>>>>> * https://issues.apache.org/****bloodhound/wiki/**<https://issues.apache.org/**bloodhound/wiki/**>
>>>>> BloodhoundDetailedInstallation**<https://issues.apache.org/**
>>>>> bloodhound/wiki/**BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>>>>> **>
>>>>>
>>>>>
>>>>> I will look at writing something about getting involved very soon unless
>>>>> someone else wants to look at that.
>>>>>
>>>>> Cheers,
>>>>> Gary
>>>>>
>>>>>
>>>>>
Re: Getting involved and installation pages
Posted by Antony Semonella <as...@gmail.com>.
Hello,
I managed to set up a bloodhound development environment on Debian 6.0
following the instructions at:
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
You may want to update the wiki to highlight the following dependency I
encountered:
The version of virtualenv in the repo for Debian squeeze is: 1.4.9-3; this
version of virtualenv results in:
NameError: global name 'logger' is not defined
When running bloodhound/installer/installer.py.
logger is defined only in main() for this version of virtualenv.
This issue has been resolved by:
https://github.com/pypa/virtualenv/commit/ea1786
Using the latest version of virtualenv (1.7.1.2) resulted in no NameError
and so the bloodhound dev. environment was setup ok for me.
I therefore suggest a version of virtualenv >=1.7.1.2 be listed as a
dependency.
Cheers!
Antony
On 9 March 2012 14:48, Antony Semonella <as...@gmail.com> wrote:
> Cool, I'll give the docs a read (as a newcomer) and provide some feedback
> :)
>
>
> On 9 March 2012 14:35, Gary <ga...@wandisco.com> wrote:
>
>> Hi everyone,
>>
>> We now have https://issues.apache.org/**bloodhound/wiki/**
>> BloodhoundContributing<https://issues.apache.org/bloodhound/wiki/BloodhoundContributing>
>>
>> As always, this definitely needs some expanding upon and improving but I
>> hope it can serve as a reasonable starting point - we definitely need to
>> discuss other ways of helping like contributing to documentation and
>> reporting bugs. And there are definitely a lot of documentation tasks to be
>> done as we get new features in.
>>
>> Cheers,
>> Gary
>>
>>
>> On 03/08/2012 06:00 PM, Antony Semonella wrote:
>>
>>> That sounds great.
>>>
>>> Cheers,
>>>
>>> Antony
>>>
>>> On 8 March 2012 17:36, Gary<ga...@wandisco.com> wrote:
>>>
>>> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>>>>
>>>> Out of curiosity, do we have a "how to get involved" or "beginner's
>>>>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>>>>> to codify these kinds of steps into something we can point newcomers
>>>>> to.
>>>>>
>>>>> -Hyrum
>>>>>
>>>>> Good idea.
>>>>
>>>> Meanwhile I have added a few pages relating to installation to the wiki
>>>> at:
>>>> * https://issues.apache.org/****bloodhound/wiki/****BloodhoundInstall<https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall>
>>>> <https://**issues.apache.org/bloodhound/**wiki/BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
>>>> >
>>>> * https://issues.apache.org/****bloodhound/wiki/**<https://issues.apache.org/**bloodhound/wiki/**>
>>>> BloodhoundDetailedInstallation**<https://issues.apache.org/**
>>>> bloodhound/wiki/**BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>>>> **>
>>>>
>>>>
>>>> I will look at writing something about getting involved very soon unless
>>>> someone else wants to look at that.
>>>>
>>>> Cheers,
>>>> Gary
>>>>
>>>>
>>>>
>>
>
Re: Getting involved and installation pages
Posted by Antony Semonella <as...@gmail.com>.
Cool, I'll give the docs a read (as a newcomer) and provide some feedback :)
On 9 March 2012 14:35, Gary <ga...@wandisco.com> wrote:
> Hi everyone,
>
> We now have https://issues.apache.org/**bloodhound/wiki/**
> BloodhoundContributing<https://issues.apache.org/bloodhound/wiki/BloodhoundContributing>
>
> As always, this definitely needs some expanding upon and improving but I
> hope it can serve as a reasonable starting point - we definitely need to
> discuss other ways of helping like contributing to documentation and
> reporting bugs. And there are definitely a lot of documentation tasks to be
> done as we get new features in.
>
> Cheers,
> Gary
>
>
> On 03/08/2012 06:00 PM, Antony Semonella wrote:
>
>> That sounds great.
>>
>> Cheers,
>>
>> Antony
>>
>> On 8 March 2012 17:36, Gary<ga...@wandisco.com> wrote:
>>
>> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>>>
>>> Out of curiosity, do we have a "how to get involved" or "beginner's
>>>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>>>> to codify these kinds of steps into something we can point newcomers
>>>> to.
>>>>
>>>> -Hyrum
>>>>
>>>> Good idea.
>>>
>>> Meanwhile I have added a few pages relating to installation to the wiki
>>> at:
>>> * https://issues.apache.org/****bloodhound/wiki/****BloodhoundInstall<https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall>
>>> <https://**issues.apache.org/bloodhound/**wiki/BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
>>> >
>>> * https://issues.apache.org/****bloodhound/wiki/**<https://issues.apache.org/**bloodhound/wiki/**>
>>> BloodhoundDetailedInstallation**<https://issues.apache.org/**
>>> bloodhound/wiki/**BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>>> **>
>>>
>>>
>>> I will look at writing something about getting involved very soon unless
>>> someone else wants to look at that.
>>>
>>> Cheers,
>>> Gary
>>>
>>>
>>>
>
Re: Getting involved and installation pages
Posted by Gary <ga...@wandisco.com>.
Hi everyone,
We now have https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
As always, this definitely needs some expanding upon and improving but I
hope it can serve as a reasonable starting point - we definitely need to
discuss other ways of helping like contributing to documentation and
reporting bugs. And there are definitely a lot of documentation tasks to
be done as we get new features in.
Cheers,
Gary
On 03/08/2012 06:00 PM, Antony Semonella wrote:
> That sounds great.
>
> Cheers,
>
> Antony
>
> On 8 March 2012 17:36, Gary<ga...@wandisco.com> wrote:
>
>> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>>
>>> Out of curiosity, do we have a "how to get involved" or "beginner's
>>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>>> to codify these kinds of steps into something we can point newcomers
>>> to.
>>>
>>> -Hyrum
>>>
>> Good idea.
>>
>> Meanwhile I have added a few pages relating to installation to the wiki at:
>> * https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
>> * https://issues.apache.org/**bloodhound/wiki/**
>> BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>>
>> I will look at writing something about getting involved very soon unless
>> someone else wants to look at that.
>>
>> Cheers,
>> Gary
>>
>>
Re: Getting involved and installation pages
Posted by Antony Semonella <as...@gmail.com>.
That sounds great.
Cheers,
Antony
On 8 March 2012 17:36, Gary <ga...@wandisco.com> wrote:
> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>
>> Out of curiosity, do we have a "how to get involved" or "beginner's
>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>> to codify these kinds of steps into something we can point newcomers
>> to.
>>
>> -Hyrum
>>
>
> Good idea.
>
> Meanwhile I have added a few pages relating to installation to the wiki at:
> * https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
> * https://issues.apache.org/**bloodhound/wiki/**
> BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>
> I will look at writing something about getting involved very soon unless
> someone else wants to look at that.
>
> Cheers,
> Gary
>
>